For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 3 voices, and was last updated 21 years, 6 months ago by
Riyad Kalla.
-
AuthorPosts
-
irisjackyMemberHi folk:
I am having the problems of booting up JBoss 3.0.8 when I upgrade MyEclipse to 3.8.2.
It was working fine under 3.8 beta 2. Today I decide to upgrade MyEclipse and have problems with it. Following is my upgrade procedure:
1. Uninstall the MyEclipse 3.8 beta 2.
2. Restart Eclipse and shutdown.
3. Install MyEclipse 3.8.2All views and perspectives are shown properly. But the JBoss 3.0.8 always fails when the booting procedure up to following line.
14:32:05,743 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/conf/jboss-service.xmlNote that there are a couple of EJB applications deployed in JBoss 3.0.8. However, with the same set of applications, I can boot up JBoss 3.2.5 successfully.
After spending an hour also, I switch back to 3.8 beta 2 and everything back to normal life. But I am very interested in the new features in 3.8.2.
Is there anyone able to help?
October 6, 2004 at 9:23 am #216990
Riyad KallaMemberVery strange… how do you know the startup fails? Do you get an exxception? If you do, what is it? Can you post the whole startup console log messages here for us to look at?
October 6, 2004 at 6:24 pm #217074
irisjackyMemberThank you for your reply.
I did get an exception. After exception, the JBoss 3.0.8 shut down automatically.
I didn’t copy the exception trace information. So I need to upgrade to 3.8.2 again to post the error log messages here. I will do it a bitter later.
October 6, 2004 at 8:02 pm #217077
Scott AndersonParticipantI believe this was caused by a change to update the JBoss 3 connector to support the new launch model in 3.2.5. I don’t suppose you can upgrade your JBoss version to the latest release of 3.2?
Actually, the change was only to use xerces instead of crimson in the default settings. So, if you open the connector and change the word “xerces” to “crimson” everywhere it occurs on the page, you should be fine again. To test that, I’d suggest you install Eclipse 3.0.1 and ME 3.8.2 in parallel to your current install, just to be sure it works ok for you.
October 6, 2004 at 8:44 pm #217088
irisjackyMemberHi scott:
Good analysis!! I just duplicate the error and following is the full jboss server log
11:15:07,770 INFO [Server] JBoss Release: JBoss-3.0.8 CVSTag=JBoss_3_0_8 11:15:07,786 INFO [Server] Home Dir: D:\jboss-3.0.8_tomcat-4.1.24 11:15:07,786 INFO [Server] Home URL: file:/D:/jboss-3.0.8_tomcat-4.1.24/ 11:15:07,786 INFO [Server] Library URL: file:/D:/jboss-3.0.8_tomcat-4.1.24/lib/ 11:15:07,786 INFO [Server] Patch URL: null 11:15:07,786 INFO [Server] Server Name: default 11:15:07,786 INFO [Server] Server Home Dir: D:\jboss-3.0.8_tomcat-4.1.24\server\default 11:15:07,786 INFO [Server] Server Home URL: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/ 11:15:07,786 INFO [Server] Server Data Dir: D:\jboss-3.0.8_tomcat-4.1.24\server\default\db 11:15:07,786 INFO [Server] Server Temp Dir: D:\jboss-3.0.8_tomcat-4.1.24\server\default\tmp 11:15:07,786 INFO [Server] Server Config URL: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/conf/ 11:15:07,786 INFO [Server] Server Library URL: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/lib/ 11:15:07,786 INFO [Server] Root Deployemnt Filename: jboss-service.xml 11:15:07,786 INFO [Server] Starting General Purpose Architecture (GPA)... 11:15:08,083 INFO [ServerInfo] Java version: 1.4.2_03,Sun Microsystems Inc. 11:15:08,083 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_03-b02,Sun Microsystems Inc. 11:15:08,114 INFO [ServiceController] Controller MBean online 11:15:08,192 INFO [MainDeployer] Creating 11:15:08,208 INFO [MainDeployer] Created 11:15:08,208 INFO [MainDeployer] Starting 11:15:08,208 INFO [MainDeployer] Started 11:15:08,224 INFO [JARDeployer] Creating 11:15:08,224 INFO [JARDeployer] Created 11:15:08,224 INFO [JARDeployer] Starting 11:15:08,224 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@39e5b5 11:15:08,224 INFO [JARDeployer] Started 11:15:08,239 INFO [SARDeployer] Creating 11:15:08,239 INFO [SARDeployer] Created 11:15:08,239 INFO [SARDeployer] Starting 11:15:08,239 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@bad8a8 11:15:08,255 INFO [SARDeployer] Started 11:15:08,255 INFO [Server] Core system initialized 11:15:08,270 INFO [MainDeployer] Starting deployment of package: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/conf/jboss-service.xml 11:15:08,302 ERROR [Server] start failed org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.NullPointerException) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:158) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:679) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221) at org.jboss.Main.boot(Main.java:148) at org.jboss.Main$1.run(Main.java:381) at java.lang.Thread.run(Thread.java:534) Caused by: java.lang.NullPointerException at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:629) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:130) ... 15 more org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.NullPointerException) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:158) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:679) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:591) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221) at org.jboss.Main.boot(Main.java:148) at org.jboss.Main$1.run(Main.java:381) at java.lang.Thread.run(Thread.java:534) Caused by: java.lang.NullPointerException at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:629) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:130) ... 15 more 11:15:08,317 INFO [Server] Undeploying all packages 11:15:08,317 INFO [MainDeployer] Undeploying file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/conf/jboss-service.xml 11:15:08,333 INFO [DeploymentInfo] Cleaned Deployment: file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/tmp/deploy/server/default/conf/jboss-service.xml/1.jboss-service.xml 11:15:08,333 INFO [MainDeployer] Undeployed file:/D:/jboss-3.0.8_tomcat-4.1.24/server/default/conf/jboss-service.xml 11:15:08,333 INFO [MainDeployer] Undeployed 1 deployed packages 11:15:08,333 INFO [Server] Shutting down all services Shutting down 11:15:08,333 INFO [ServiceController] Stopping 3 services 11:15:08,333 INFO [SARDeployer] Stopping 11:15:08,333 INFO [MainDeployer] Removing deployer: org.jboss.deployment.SARDeployer@bad8a8 11:15:08,333 INFO [SARDeployer] Stopped 11:15:08,333 INFO [JARDeployer] Stopping 11:15:08,333 INFO [JARDeployer] Stopped 11:15:08,333 INFO [MainDeployer] Stopping 11:15:08,333 INFO [MainDeployer] Stopped 11:15:08,333 INFO [ServiceController] Stopped 3 services 11:15:08,333 INFO [Server] Deleting server tmp/deploy directory 11:15:08,536 INFO [Server] Shutdown complete Shutdown complete Halting VMWe are migrating to JBoss 3.2.5. It could take a while to get rid of all dependencies on JBoss 3.0.8 because JBoss did a lot of changes for 3.2.5.
So, if you open the connector and change the word “xerces” to “crimson” everywhere it occurs on the page, you should be fine again.
Where is this connector? I just checked the JBoss 3 plugin package in MyExclipse installation folder. There is no such information.
October 6, 2004 at 8:47 pm #217089
Riyad KallaMemberClicking on the menu: Window > Preferneces > MyEclipse > Application Servers > JBoss 3, you’ll see two fields “XML Document Build Factory Class” and “SAX Parser Factory CLass”, they probably say something like “org.apache.xerces.blah.blahb.lah” what Scott was saying is that you can go in and change all the “xerces” to “crimson” and see if that fixes the problem.
October 6, 2004 at 9:02 pm #217094
irisjackyMemberCool, it works! Thanks a lot!
October 6, 2004 at 9:05 pm #217096
Riyad KallaMemberAwesome.
-
AuthorPosts
