[Beginners Corner] - Re: org.jboss.deployment.DeploymentException: url file:/C:/j
by prasanthijboss
hello
i installed jboss 4.0.3sp1 using eclipse when i deployed my war into jboss
it encounters an error which i cannot rectify Please help me see this
my error
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: Could not initialise deployment: file:/D:/jboss-4.0.3SP1/server/default/conf/jboss-service.xml; - nested throwable: (java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:785)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
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:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
at org.jboss.Main.boot(Main.java:187)
at org.jboss.Main$1.run(Main.java:438)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/ConcurrentReaderHashMap
at org.jboss.util.xml.JBossEntityResolver.(JBossEntityResolver.java:43)
at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:585)
at org.jboss.deployment.SARDeployer.init(SARDeployer.java:164)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:843)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:780)
... 21 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146441#4146441
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146441
18 years
[JNDI/Naming/Network] - updated jndi name can't refer to the hot deployed codes
by ywtsang
let me describe my situation with some simplification:
(jboss4.2.0.GA, ejb3)
1 ear (A.ear) with 1 session bean (ProductManagerBean) is deployed
jndi name = A.ear/ProductManagerBean
1 tomcat (tomcat 6.0.13) acts as a client and use the session bean remotely
now i updated the session bean code and hot-deployed to the jboss with the "jndi" name and ear name changed:
e.g.
A-1.ear
jndi name is changed to A-1.ear/ProductManagerBean
i can check that the deployment of the A-1.ear has no problem and it can shows correctly at the jmx console and also the jndi tree
and i go to shutdown the tomcat to deploy the updated client (to use A-1.ear and new jndi name) and start the app again
now the client app is still "pointing" to the old bean
(this is verified by:
i remove the A.ear from the jboss, it is supposed that will not affect the updated tomcat client, but it shows error like "A.ear unbounded", so the tomcat client is pointing to the old ear
but if i restart the jboss and tomcat again, no problem, i.e. it is pointing to the updated A-1.ear and ProductServiceBean
one more observation that may help:
when 2 ear is deployed and i view the jndi tree
the "productservicebean" appears below at 2 different roots (A.ear/A-1.ear), but the "proxy" name is the same, i.e. something like proxy1234
)
simply speaking, i want to deploy "multiple" versions of my application to the jboss and let different clients to reference to different versions at the same time
i guess this is conflicted at the same "class name" of the ejb?
any hint to solve my problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146438#4146438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146438
18 years
[JNDI/Naming/Network] - updated jndi name can't refer to the hot deployed codes
by ywtsang
let me describe my situation with some simplification:
(jboss4.2.0.GA, ejb3)
1 ear (A.ear) with 1 session bean (ProductManagerBean) is deployed
jndi name = A.ear/ProductManagerBean
1 tomcat (tomcat 6.0.13) acts as a client and use the session bean remotely
now i updated the session bean code and hot-deployed to the jboss with the "jndi" name and ear name changed:
e.g.
A-1.ear
jndi name is changed to A-1.ear/ProductManagerBean
i can check that the deployment of the A-1.ear has no problem and it can shows correctly at the jmx console and also the jndi tree
and i go to shutdown the tomcat to deploy the updated client (to use A-1.ear and new jndi name) and start the app again
now the client app is still "pointing" to the old bean
(this is verified by:
i remove the A.ear from the jboss, it is supposed that will not affect the updated tomcat client, but it shows error like "A.ear unbounded", so the tomcat client is pointing to the old ear
but if i restart the jboss and tomcat again, no problem, i.e. it is pointing to the updated A-1.ear and ProductServiceBean
one more observation that may help:
when 2 ear is deployed and i view the jndi tree
the "productservicebean" appears below at 2 different roots (A.ear/A-1.ear), but the "proxy" name is the same, i.e. something like proxy1234
)
simply speaking, i want to deploy "multiple" versions of my application to the jboss and let different clients to reference to different versions at the same time
i guess this is conflicted at the same "class name" of the ejb?
any hint to solve my problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146437#4146437
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146437
18 years
[EJB/JBoss] - Urgent Help Regarding Stateless Session Bean
by JKV
I am using EJB3 in JBoss 4.2.2. My standard-jboss.xml has the following standard configuration
<container-pool-conf>
100
</container-pool-conf>
for <container-name>Standard Stateless SessionBean</container-name>. I have as many as 7 Stateless Session Bean in my ear, one (Ex: SLSB-AA) of which is called remotely and others are called locally. I am calling the SLSB-AA as many as 70 times per second and there are local calls between SLSBs. My code outside JBoss which calls the SDSB-A run perfectly for 700 to 800 calls. After when I get the exception
Problem establishing socket connection for InvokerLocator [socket://xx.xx.xxx.xxx:3873/]
org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://10.11.145.156:3873/]
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:532)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
...................
...................
Caused by: java.net.SocketException: Can not obtain client socket connection from pool. Have waited 30015 milliseconds for available connection (51in use)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:862)
at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:525)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
at org.jboss.remoting.Client.invoke(Client.java:1634)
at org.jboss.remoting.Client.invoke(Client.java:548)
at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:107)
I increased the pool size
<container-pool-conf>
1000
</container-pool-conf>
even then I get this exception after calling my SLSB-A for 1200-1300 times. Any help is greatly appreciated
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146433#4146433
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146433
18 years