Hello oxygen-user, oXygen 8.1 is failing to start, it gives FATAL ERROR Cannot start <oXygen/> XML Editor Due to java.lang.reflect.InvocationTargetException I have tried re-running the oXygen installer, choosing 'repair', and I have tried running the java upddater, which took me from jre1.5.0_08 to jre1.6.0_01, but neither of these things has fixed the problem. I'm not sure what has caused this error to start happening. I attached a screenshot, and cc'ed George in case the list does not like attachments. If there is a log file somewhere with the complete error details I am happy to send that if told what to send. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Hello, Please select and copy the whole stack trace from the dialog and post it to the list. The lower part should contain a "caused by" stack trace and it is not visible in your screenshot. Regards, Sorin Chris Lilley wrote:
Hello oxygen-user,
oXygen 8.1 is failing to start, it gives
FATAL ERROR Cannot start <oXygen/> XML Editor Due to java.lang.reflect.InvocationTargetException
I have tried re-running the oXygen installer, choosing 'repair', and I have tried running the java upddater, which took me from jre1.5.0_08 to jre1.6.0_01, but neither of these things has fixed the problem.
I'm not sure what has caused this error to start happening. I attached a screenshot, and cc'ed George in case the list does not like attachments. If there is a log file somewhere with the complete error details I am happy to send that if told what to send.
On Tuesday, April 24, 2007, 9:12:36 AM, Sorin wrote: SR> Hello, SR> Please select and copy the whole stack trace from the dialog and post it SR> to the list. The lower part should contain a "caused by" stack trace and SR> it is not visible in your screenshot. Its truncated in the dialog, which is why I asked if there was some log file that I should post. Here is the contents of the dialog: Cannot start <oXygen/> XML Editor. Due to:java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at ro.sync.ui.application.ApplicationLauncher.A(Unknown Source) at ro.sync.ui.application.ApplicationLauncher.launch(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at ro.sync.exml.Oxygen.main(Unknown Source) Caused by: java.lang.NullPointerException at javax.swing.ImageIcon.<init>(Unknown Source) at javax.swing.ImageIcon.<init>(Unknown Source) at sun.swing.WindowsPlacesBar.<init>(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.updateUseShellFolder(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.installComponents(Unknown Source) at javax.swing.plaf.basic.BasicFileChooserUI.installUI(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.installUI(Unknown Source) at javax.swing.JComponent.setUI(Unknown Source) at javax.swing.JFileChooser.updateUI(Unknown Source) at javax.swing.JFileChooser.setup(Unknown Source) at javax.swing.JFileChooser.<init>(Unknown Source) at javax.swing.JFileChooser.<init>(Unknown Source) at ro.sync.ui.R.<init>(Unknown Source) at ro.sync.ui.F.<init>(Unknown Source) at ro.sync.ui.F.A(Unknown Source) at ro.sync.ui.application.L.<init>(Unknown Source) at ro.sync.exml.MainFrame.<init>(Unknown Source) at ro.sync.exml.MainFrame.<init>(Unknown Source) ... 11 more The "11 more" is literal text in the dialog SR> Chris Lilley wrote:
Hello oxygen-user,
oXygen 8.1 is failing to start, it gives
FATAL ERROR Cannot start <oXygen/> XML Editor Due to java.lang.reflect.InvocationTargetException
I have tried re-running the oXygen installer, choosing 'repair', and I have tried running the java upddater, which took me from jre1.5.0_08 to jre1.6.0_01, but neither of these things has fixed the problem.
I'm not sure what has caused this error to start happening. I attached a screenshot, and cc'ed George in case the list does not like attachments. If there is a log file somewhere with the complete error details I am happy to send that if told what to send.
SR> _______________________________________________ SR> oXygen-user mailing list SR> oXygen-user@oxygenxml.com SR> http://www.oxygenxml.com/mailman/listinfo/oxygen-user -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Hello, We got this error with a Java virtual machine 1.6.0 beta version but the Java 1.6.0 final version fixed the problem. What is the Java version reported by the following command? java -version You should try to run oXygen with a different version of Java virtual machine. If you start oXygen from the Start menu in order to change the Java virtual machine you have to set the home folder of the JVM that will run oXygen with a property like JRE Path=C:\path\to\JRE\home\folder added in the file [oXygen-install-folder]\oxygen8.1.ini, the section [Virtual Machine Parameters]. If you start oXygen using the oxygen.bat script you have to set the full path to java.exe in the java command inside this script. Other possibility is to install the Windows kit that includes a JVM because the included JVM was tested with oXygen before the release. Regards, Sorin Chris Lilley wrote:
On Tuesday, April 24, 2007, 9:12:36 AM, Sorin wrote:
SR> Hello,
SR> Please select and copy the whole stack trace from the dialog and post it SR> to the list. The lower part should contain a "caused by" stack trace and SR> it is not visible in your screenshot.
Its truncated in the dialog, which is why I asked if there was some log file that I should post. Here is the contents of the dialog:
Cannot start <oXygen/> XML Editor. Due to:java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at ro.sync.ui.application.ApplicationLauncher.A(Unknown Source) at ro.sync.ui.application.ApplicationLauncher.launch(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at ro.sync.exml.Oxygen.main(Unknown Source) Caused by: java.lang.NullPointerException at javax.swing.ImageIcon.<init>(Unknown Source) at javax.swing.ImageIcon.<init>(Unknown Source) at sun.swing.WindowsPlacesBar.<init>(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.updateUseShellFolder(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.installComponents(Unknown Source) at javax.swing.plaf.basic.BasicFileChooserUI.installUI(Unknown Source) at com.sun.java.swing.plaf.windows.WindowsFileChooserUI.installUI(Unknown Source) at javax.swing.JComponent.setUI(Unknown Source) at javax.swing.JFileChooser.updateUI(Unknown Source) at javax.swing.JFileChooser.setup(Unknown Source) at javax.swing.JFileChooser.<init>(Unknown Source) at javax.swing.JFileChooser.<init>(Unknown Source) at ro.sync.ui.R.<init>(Unknown Source) at ro.sync.ui.F.<init>(Unknown Source) at ro.sync.ui.F.A(Unknown Source) at ro.sync.ui.application.L.<init>(Unknown Source) at ro.sync.exml.MainFrame.<init>(Unknown Source) at ro.sync.exml.MainFrame.<init>(Unknown Source) ... 11 more
The "11 more" is literal text in the dialog
On Tuesday, April 24, 2007, 4:46:36 PM, Sorin wrote: SR> Hello, SR> We got this error with a Java virtual machine 1.6.0 beta version but the SR> Java 1.6.0 final version fixed the problem. What is the Java version SR> reported by the following command? SR> java -version $ java -version java version "1.6.0_01" Java(TM) SE Runtime Environment (build 1.6.0_01-b06) Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode, sharing) As mentioned in my original mail, I had updated to that version, was previously running jre 1.5.0_09, in case a new version of Java fixed the error. SR> You should try to run oXygen with a different version of Java virtual SR> machine. If you start oXygen from the Start menu in order to change the SR> Java virtual machine you have to set the home folder of the JVM that SR> will run oXygen with a property like SR> JRE Path=C:\path\to\JRE\home\folder SR> added in the file [oXygen-install-folder]\oxygen8.1.ini, the section SR> [Virtual Machine Parameters]. [Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jre1.5.0_09 or [Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jre1.5.0_08 or [Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jdk1.5.0_08 give me the same error. SR> If you start oXygen using the oxygen.bat script you have to set the full SR> path to java.exe in the java command inside this script. Other SR> possibility is to install the Windows kit that includes a JVM because SR> the included JVM was tested with oXygen before the release. I should point out that I have been successfully running oXygen, without the 'includes jvm' option, for some years. This particular machine has been running oXygen 8.1 for four months, since I got it. The errors started happening about a week ago, not clear why. This isn't an "I can't install oXygen" bug report. Its an "oXygen suddenly stopped working" bug report. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Hi Chris, From the stack trace the problem appears when oXygen tries to create the standard Java dialog for opening/saving files and it seems to get into problems loading an icon. Have you changed the Windows appearance? It may be some new theme or style that Java cannot find its icons for... Maybe one thing you can try is to reset the options by renaming the com.oxygenxml folder from your [user home directory]/Application Data and let us know if that changes things. Best Regards, George --------------------------------------------------------------------- George Cristian Bina - http://aboutxml.blogspot.com/ <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com Chris Lilley wrote:
On Tuesday, April 24, 2007, 4:46:36 PM, Sorin wrote:
SR> Hello,
SR> We got this error with a Java virtual machine 1.6.0 beta version but the SR> Java 1.6.0 final version fixed the problem. What is the Java version SR> reported by the following command?
SR> java -version
$ java -version java version "1.6.0_01" Java(TM) SE Runtime Environment (build 1.6.0_01-b06) Java HotSpot(TM) Client VM (build 1.6.0_01-b06, mixed mode, sharing)
As mentioned in my original mail, I had updated to that version, was previously running jre 1.5.0_09, in case a new version of Java fixed the error.
SR> You should try to run oXygen with a different version of Java virtual SR> machine. If you start oXygen from the Start menu in order to change the SR> Java virtual machine you have to set the home folder of the JVM that SR> will run oXygen with a property like
SR> JRE Path=C:\path\to\JRE\home\folder
SR> added in the file [oXygen-install-folder]\oxygen8.1.ini, the section SR> [Virtual Machine Parameters].
[Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jre1.5.0_09
or
[Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jre1.5.0_08
or
[Virtual Machine Parameters] JRE Path=C:\Program Files\Java\jdk1.5.0_08
give me the same error.
SR> If you start oXygen using the oxygen.bat script you have to set the full SR> path to java.exe in the java command inside this script. Other SR> possibility is to install the Windows kit that includes a JVM because SR> the included JVM was tested with oXygen before the release.
I should point out that I have been successfully running oXygen, without the 'includes jvm' option, for some years. This particular machine has been running oXygen 8.1 for four months, since I got it. The errors started happening about a week ago, not clear why.
This isn't an "I can't install oXygen" bug report. Its an "oXygen suddenly stopped working" bug report.
On Tuesday, April 24, 2007, 6:54:27 PM, George wrote: GCB> Hi Chris, Hi George. I have been uninstalling all the Java versions, and oXygen, and clearing the registry of oxygen and java stuff, and reinstalling; it hadn't helped. GCB> From the stack trace the problem appears when oXygen tries to create GCB> the standard Java dialog for opening/saving files and it seems to get GCB> into problems loading an icon. GCB> Have you changed the Windows appearance? It may be some new theme or GCB> style that Java cannot find its icons for... I had indeed uninstalled a theme manager (Stardock Windowblinds). Never thought it would be related; I had a couple of missing icons but though that was merely aesthetic. GCB> Maybe one thing you can try is to reset the options by renaming the GCB> com.oxygenxml folder from your [user home directory]/Application Data GCB> and let us know if that changes things. I did that, and it did not change things. However, I have now repaired the icon set so there are no missing icons, and oXygen now happily starts once more. Many thanks for the help, I would never have though it was a missing icon! -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Co-Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
participants (3)
-
Chris Lilley -
George Cristian Bina -
Sorin Ristache