-
1. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
nickarls Dec 6, 2012 11:07 AM (in response to cavi)More details required.
-
2. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
ctomc Dec 6, 2012 11:35 AM (in response to cavi)basicly none of them
AS7 works on JDK7.
but if you have issues, please provide more details as Nicklas said.
-
3. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
cavi Dec 7, 2012 4:24 AM (in response to nickarls)Acctually the scene is:
In eclipse, I am building my project with jdk 1.5, I am using jre 1.5 and it is working fine with jboss 4.2.3.GA (if i am using jboss runtime environment java 1.5)...My project is working perfectly....no issue
But the issue is:
As I am building the same project with jdk 1.7, I am using jre 1.7 and it is not working with jboss 7.1.Final (if i am using jboss runtime environment java 1.7)......It is showing me error
14:48:23,925 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."lb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."lb.war".INSTALL: Failed to process phase INSTALL of deployment "lb.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Thanks Nicklas
Thanks Tomaz
-
4. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
nickarls Dec 7, 2012 4:25 AM (in response to cavi)Any preceding errors? Sure the AS uses Java 7?
-
5. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
cavi Dec 7, 2012 5:56 AM (in response to nickarls)Yaa sure....Its using java 7.
I am pasting whole console description for jboss 7.1.1.Final here:
15:52:19,539 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
15:52:21,984 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
15:52:22,089 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
15:52:28,332 INFO [org.xnio] XNIO Version 3.0.3.GA
15:52:28,341 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
15:52:28,414 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
15:52:28,452 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
15:52:28,547 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
15:52:28,576 INFO [org.jboss.as.clustering.infinispan] JBAS010280: Activating Infinispan subsystem.
15:52:28,579 INFO [org.jboss.as.webservices] JBAS015537: Activating WebServices Extension
15:52:28,568 INFO [org.jboss.as.osgi] JBAS011940: Activating OSGi Subsystem
15:52:28,643 INFO [org.jboss.as.connector] (MSC service thread 1-24) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
15:52:28,565 INFO [org.jboss.as.security] JBAS013101: Activating Security Subsystem
15:52:28,564 INFO [org.jboss.as.configadmin] JBAS016200: Activating ConfigAdmin Subsystem
15:52:28,564 INFO [org.jboss.as.naming] JBAS011800: Activating Naming Subsystem
15:52:28,797 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
15:52:28,874 INFO [org.jboss.as.mail.extension] (MSC service thread 1-24) JBAS015400: Bound mail session [java:jboss/mail/Default]
15:52:28,869 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
15:52:28,798 INFO [org.jboss.as.security] (MSC service thread 1-9) JBAS013100: Current PicketBox version=4.0.7.Final
15:52:28,955 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-10.199.3.147-31300
15:52:29,675 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-26) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
15:52:30,960 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-19) JBoss Web Services - Stack CXF Server 4.0.2.GA
15:52:32,369 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-20) JBAS015012: Started FileSystemDeploymentService for directory /usrdata/chaudhaa/jboss-as-7.1.1.Final/standalone/deployments
15:52:32,402 INFO [org.jboss.as.remoting] (MSC service thread 1-30) JBAS017100: Listening on /127.0.0.1:49999
15:52:32,402 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/10.199.3.147:44447
15:52:32,379 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment lb.war
15:52:32,918 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:49990
15:52:32,968 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 14671ms - Started 133 of 208 services (74 services are passive or on-demand)
15:52:53,568 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found lb.war in deployment directory. To trigger deployment create a file called lb.war.dodeploy
15:52:53,706 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015876: Starting deployment of "lb.war"
15:53:08,300 WARN [org.jboss.as.ee] (MSC service thread 1-22) JBAS011006: Not installing optional component org.jboss.wsf.stack.jbws.EndpointServlet due to exception: java.lang.ClassNotFoundException: org.jboss.wsf.stack.jbws.EndpointServlet from [Module "deployment.lb.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_09]
at java.lang.Class.forName(Class.java:264) [rt.jar:1.7.0_09]
at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:79)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
15:53:19,623 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-22) Add Service
id=st.erpsapccn.bs.lb.admin.service.RefDataWebServiceHandler
address=http://localhost:31300/lb/RefData
implementor=st.erpsapccn.bs.lb.admin.service.RefDataWebServiceHandler
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName
portName
wsdlLocation=null
mtomEnabled=false
15:53:19,837 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-22) Add Service
id=st.erpsapccn.bs.lb.admin.service.IntranetPassportWebServiceHandler
implementor=st.erpsapccn.bs.lb.admin.service.IntranetPassportWebServiceHandler
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName
portName
wsdlLocation=null
mtomEnabled=false
15:53:20,040 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-22) Add Service
id=st.erpsapccn.bs.lb.admin.service.AdminPassportWebServiceHandler
implementor=st.erpsapccn.bs.lb.admin.service.AdminPassportWebServiceHandler
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName
portName
wsdlLocation=null
mtomEnabled=false
15:53:22,158 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-22) MSC00001: Failed to start service jboss.deployment.unit."lb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."lb.war".INSTALL: Failed to process phase INSTALL of deployment "lb.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:174)
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:96)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:113)
at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:74)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.lang.NullPointerException
at st.liotrox.WRequest.resolvePath(WRequest.java:1016)
at st.liotrox.WRequest.resolveApplicationScopeComponent(WRequest.java:1351)
at st.liotrox.LIOTROX.resolveApplicationScopeComponent(LIOTROX.java:141)
at st.liotrox.LIOTROX.getLog(LIOTROX.java:182)
at st.liotrox.LIOTROX.getSystemLog(LIOTROX.java:193)
at st.erpsapccn.bs.lb.admin.util.AdminWSLogger.<init>(AdminWSLogger.java:33)
at st.erpsapccn.bs.lb.admin.util.AdminWSLogger.getLogger(AdminWSLogger.java:41)
at st.erpsapccn.bs.lb.admin.service.RefDataWebServiceHandler.<init>(RefDataWebServiceHandler.java:38)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_09]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_09]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_09]
at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_09]
at java.lang.Class.newInstance0(Class.java:372) [rt.jar:1.7.0_09]
at java.lang.Class.newInstance(Class.java:325) [rt.jar:1.7.0_09]
at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:170)
... 10 more
15:53:23,452 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "lb.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"lb.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"lb.war\".INSTALL: Failed to process phase INSTALL of deployment \"lb.war\""}}
15:53:25,026 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015877: Stopped deployment lb.war in 1573ms
15:53:25,076 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."lb.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."lb.war".INSTALL: Failed to process phase INSTALL of deployment "lb.war"
15:53:25,228 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"lb.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"lb.war\".INSTALL: Failed to process phase INSTALL of deployment \"lb.war\""}}}}
-
6. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
nickarls Dec 7, 2012 6:06 AM (in response to cavi)What happens at
at st.erpsapccn.bs.lb.admin.service.RefDataWebServiceHandler.<init>(RefDataWebServiceHandler.java:38) ?
What libs are you including in the war lib dir?
-
8. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
nickarls Jan 9, 2013 3:09 AM (in response to cavi)Take out all jars. See what doesn't compile. If it's some EE API, add it only as a compile-time dependency.
Also, I'm note sure about the org.jboss.wsf stuff. Have you tried take working with the WS API only and let the server side CXF take care of the implementation?
-
9. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
cavi Jan 9, 2013 5:40 AM (in response to nickarls)I am not getting you Nicklas, plz..Can u explain again?
-
10. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
nickarls Jan 9, 2013 5:50 AM (in response to cavi)You have a lot of jars in your application. Some of these are just dead weight (two oracle driver jars). Others can confuse the classloder (jta.jar?). You also appear to pack axis.jars and other WS related jars that might interfere with the default WS-implementation on the server side (CXF). I suggest you try to remove as many of these extra jars as possible. And preferrably, use only the WS-API for your application and let CXF do the implementation part on the server side.
-
11. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
cavi Jan 11, 2013 2:12 AM (in response to nickarls)Hi Nicklas
First tel me about this error, Is there any problem with my web.xml?
B'coz This eror come after I put servlet & servlet-mapping in my web.xml....!!
==============================================================
12:23:20,074 WARN [org.jboss.as.ee] (MSC service thread 1-10) JBAS011006: Not installing optional component org.jboss.wsf.stack.jbws.EndpointServlet due to exception: java.lang.ClassNotFoundException: org.jboss.wsf.stack.jbws.EndpointServlet from [Module "deployment.lb.war:main" from Service Module Loader]
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]
at java.lang.Class.forName0(Native Method) [rt.jar:1.7.0_09]
at java.lang.Class.forName(Class.java:264) [rt.jar:1.7.0_09]
at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:79)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_09]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_09]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_09]
================================================================================
Thanks
cavi
-
12. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
sfcoy Jan 11, 2013 2:38 AM (in response to cavi)On top of everything else that Nicklas has said, org.jboss.wsf.stack.jbws.EndpointServlet is obsolete and you should not be using it anymore.
Are you deploying web services?
Are they implemented using JAX-WS or JAX-RPC?
-
13. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
cavi Jan 11, 2013 2:48 AM (in response to sfcoy)Hi, Stephen,
Thanks for reply
Yes, they implemented using .....JAX-RPC.
How can I remove this org.jboss.wsf.stack.jbws.EndpointServlet ?
Regards
cavi
-
14. Re: What are the issues, one can face while using JDK 1.7 and JBoss 7.1 both together ?
sfcoy Jan 11, 2013 6:55 AM (in response to cavi)I assumed that this was the servlet that you were adding into the web.xml.
Please show the web.xml that doesn't work.
In addition you should probably read the articles linked in this "Featured Discussion": JBoss AS7 - WebServices documentation.
If you have java code generated from a WSDL you will likely need to regenerate using AS 7 tooling.
(and you still need to get rid of the junk in your WEB-INF/lib directory)