[Installation, Configuration & Deployment] - Missing Jars in Jboss 405ga startup
by pmoran
I get the following erros when starting up jBoss on Ubuntu.
I have reinstalled with Jems and even downloaded and built from source all with the same missing files.
I see from other posts that the JEMS installer has issues and is being worked on but even the soure fails to get me there.
Any suggestions?
2006-11-29 00:32:16,893 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment (init step) of package at: file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb-impl.jar
| 2006-11-29 00:32:16,893 DEBUG [org.jboss.deployment.MainDeployer] Copying file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb-impl.jar -> /BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/tmp/deploy/tmp16844jaxb-impl.jar
| 2006-11-29 00:32:16,962 DEBUG [org.jboss.deployment.JARDeployer] No xml files found
| 2006-11-29 00:32:16,962 DEBUG [org.jboss.deployment.MainDeployer] using deployer org.jboss.deployment.JARDeployer@164dbd5
| 2006-11-29 00:32:16,962 DEBUG [org.jboss.deployment.JARDeployer] looking for nested deployments in : file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb-impl.jar
| 2006-11-29 00:32:17,485 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] Added url: file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/tmp/deploy/tmp16844jaxb-impl.jar, to ucl: org.jboss.mx.loading.UnifiedClassLoader3@1474ea{ url=file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/ ,addedOrder=12}
| 2006-11-29 00:32:17,488 DEBUG [org.jboss.deployment.MainDeployer] resolveLibraries: jaxb-api.jar activation.jar jsr173_1.0_api.jar jaxb1-impl.jar
| 2006-11-29 00:32:17,489 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jaxb-api.jar
| 2006-11-29 00:32:17,489 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is activation.jar
| 2006-11-29 00:32:17,490 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jsr173_1.0_api.jar
| 2006-11-29 00:32:17,497 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb-impl.jar references URL file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jsr173_1.0_api.jar which could not be opened, entry ignored
| 2006-11-29 00:32:17,509 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
| 2006-11-29 00:32:17,510 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
| 2006-11-29 00:32:17,510 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
| org.jboss.deployment.DeploymentException: url file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jsr173_1.0_api.jar could not be opened, does it exist?
| at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
| at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy6.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| 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:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy5.deploy(Unknown Source)
| at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
| at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
| at org.jboss.Main.boot(Main.java:200)
| at org.jboss.Main$1.run(Main.java:490)
| at java.lang.Thread.run(Thread.java:595)
| 2006-11-29 00:32:17,520 DEBUG [org.jboss.deployment.MainDeployer] new manifest entry for sdi at jaxb-impl.jar entry is jaxb1-impl.jar
| 2006-11-29 00:32:17,521 DEBUG [org.jboss.deployment.MainDeployer] The manifest entry in file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb-impl.jar references URL file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb1-impl.jar which could not be opened, entry ignored
| org.jboss.deployment.DeploymentException: url file:/BidSpec/applications/jboss-4.0.5.GA/server/BidSpec/deploy/jbossws.sar/jaxb1-impl.jar could not be opened, does it exist?
| at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:214)
| at org.jboss.deployment.MainDeployer.parseManifestLibraries(MainDeployer.java:1137)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:884)
| at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989816#3989816
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989816
18Â years, 2Â months
[Beginners Corner] - Porting standalone App to JBoss
by virtros
We have a functioning and fairly dynamic standalone client/server (we have a JINI client interface and a XML client interface) data translation application that is currently being used by several govt programs. We have had several requests to adopt a SOA. In particular, I'm interested in packaging my application up and deploying it as a JBoss service. How does this impact, if at all, my applications ability to open and utilize network socket connections for lan sniffing, RMI connections (specifically JINI) for some remote clients?
I am assuming that this will be a bit of an undertaking but see the potential payoff as a high return on investment. I have some older experience with weblogic in the early days of J2EE but for the past few years I've been out of that loop.
Any hints or direction would be welcome,
Noah
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989809#3989809
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989809
18Â years, 2Â months