Jboss 7.1 eap upgrade error

Latest response

Hi Guys.

Sub :- Jboss upgrade from Jboss 6.3 EAP to 7.1 EAP .

I am working on jboss7.1 upgrade (Jboss eap 6.3 to Jboss7.1 eap), while i am starting the server i am getting below error so could you some body please advise me.

10:35:23,474 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.as: org.jboss.msc.service.StartException in service jboss.as: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_121]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
Caused by: org.jboss.modules.ModuleLoadError: org.jboss.sasl
at org.jboss.modules.ModuleLoadException.toError(ModuleLoadException.java:74) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.Module.getPathsUnchecked(Module.java:1559) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.Module.loadModuleClass(Module.java:708) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) [jboss-modules.jar:1.6.0.Final-redhat-1]
at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.8.0_121]
at java.lang.ClassLoader.defineClass(ClassLoader.java:763) [rt.jar:1.8.0_121]
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:358) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.Module.loadModuleClass(Module.java:713) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) [jboss-modules.jar:1.6.0.Final-redhat-1]
at org.jboss.as.server.ServerService.addService(ServerService.java:242) [wildfly-server-3.0.13.Final-redhat-1.jar:3.0.13.Final-redhat-1]
at org.jboss.as.server.ApplicationServerService.start(ApplicationServerService.java:160) [wildfly-server-3.0.13.Final-redhat-1.jar:3.0.13.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
... 3 more

10:35:23,580 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1

Manay Thanks.

Gollapen

Responses

Nagaraju, It is better if you could change the title of the post, otherwise, it would fail to get noticed by the community.

You're right Sadashiva, the title lets assume it's spam. @Nagaraju : I suggest to change it to JBoss upgrade error. :)

Regards,
Christian

sorry for the misleading title.

No problem ... Thank you for having changed it - it looks much better now.
Let's hope that someone chimes in with a solution. I wish you good luck ! :)

Regards,
Christian