[JBoss JIRA] Created: (JBWS-2695) Setting a new config at runtime the properties are not available to RemotingConnectionImpl
by Darran Lofthouse (JIRA)
Setting a new config at runtime the properties are not available to RemotingConnectionImpl
------------------------------------------------------------------------------------------
Key: JBWS-2695
URL: https://jira.jboss.org/jira/browse/JBWS-2695
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.2.0
Using the following to replace the configuration for the client: -
((StubExt)port).setConfigName("Custom Client Config","descriptors/jaxws-client-config.xml");
Handlers are updated as required, however the properties that are processed by RemotingConnectionImpl still use the original values.
This is because the MessageContext obtains the config from the OperationMetaData as the custom config was not set when the MessageContext was created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (JBWS-2886) Error doing multiple calls to web service
by Marco Benuzzi (JIRA)
Error doing multiple calls to web service
-----------------------------------------
Key: JBWS-2886
URL: https://jira.jboss.org/jira/browse/JBWS-2886
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Environment: Linux Fedora 11 kernel 2.6.30.10-105
JBoss Application Platform 5.0.0.GA
Reporter: Marco Benuzzi
Priority: Critical
I'm testing JBossWS to access a remote web service.
Just for test I'm using a java console application; I run it with sun jdk 6.0.17 with classpath jboss-eap-5.0/jboss-as/client/*.jar (linux)
I've created stubs client classes with wsconsume.
If a make a single call all works fine.
MyWebServices service = new MyWebServices();
MYSOAPHandlerResolver handlerResolver = new MYSOAPHandlerResolver();
service.setHandlerResolver(handlerResolver);
MyWebServicesPT port = service.getMYWebServicesPort();
port.call1();
// OK
If a make more than one call, only the first ones works fine.
MyWebServices service = new MyWebServices();
MYSOAPHandlerResolver handlerResolver = new MYSOAPHandlerResolver();
service.setHandlerResolver(handlerResolver);
MyWebServicesPT port = service.getMYWebServicesPort();
port.call1();
// OK
port.call2();
// after 80 seconds I got an exception (please note that I don't see any network activity with wireshark)
javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:310)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:162)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:148)
at $Proxy15.commandCryptic(Unknown Source)
at it.celeweb.otagw.adapter.amadeus.test.AmadeusClient.main(AmadeusClient.java:77)
Caused by: java.io.IOException: Could not transmit message
at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:253)
at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:231)
... 4 more
Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker after 1 attempt(s)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:250)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:162)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167)
at org.jboss.remoting.Client.invoke(Client.java:1917)
at org.jboss.remoting.Client.invoke(Client.java:768)
at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:232)
... 7 more
Caused by: java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1072)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
at org.jboss.remoting.transport.http.HTTPClientInvoker.getResponseCode(HTTPClientInvoker.java:1269)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:351)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:232)
... 12 more
During the debugging of the problem, I found a strange workaround: putting a sleeb after each call.
MyWebServices service = new MyWebServices();
MYSOAPHandlerResolver handlerResolver = new MYSOAPHandlerResolver();
service.setHandlerResolver(handlerResolver);
MyWebServicesPT port = service.getMYWebServicesPort();
port.call1();
// OK
Thread.Sleep(5000);
port.call2();
// OK
Thread.Sleep(5000);
port.call3();
// OK
Thread.Sleep(5000);
port.call4();
I've tested the same web services using Axis2 as framework and all is working as expected without the need to use the sleep; so I'm sure the problem is on the JAXWS implemented in JBoss
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (JBWS-2742) Getting Classcast Exception Inconsistently with the WSAddressing Implemented Services
by vinoth kumar (JIRA)
Getting Classcast Exception Inconsistently with the WSAddressing Implemented Services
-------------------------------------------------------------------------------------
Key: JBWS-2742
URL: https://jira.jboss.org/jira/browse/JBWS-2742
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.0
Environment: Linux - Ubuntu
Reporter: vinoth kumar
We are using JBOSS 4.2.3 with JBOSSWS Native 3.1.0 deployed.
We had implemented WSAddressing for Our Services as per the Steps given in the link : http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide.
This WSAddressing implementation works fine without any issues if we give a single hit to the Services from the client for a given time. But if we have multiple simultaneous hits, we are getting the Classcast Exception inconsistently.
We had done the following changes in Client,
Code:
Service service = Service.create(wsdlURL, serviceName);
port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
BindingProvider bindingProvider = (BindingProvider)port1;
List<Handler> customHandlerChain = new ArrayList<Handler>();
customHandlerChain.add(new ClientHandler());
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
The Exception that we are getting is,
Code:
javax.xml.ws.WebServiceException:
java.lang.ClassCastException:
com.mobax.signage.ws.RemoveDeviceResponse cannot be cast to com.mobax.signage.ws.GetDeviceResponseRe
sponse
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at $Proxy103.removeDevice(Unknown Source)
at com.mobax.mashup.webserviceconsumer.SignageServiceConsumer.removeDevices(SignageServiceConsumer.j
ava:264)
at com.mobax.mashup.responsebuilder.EnablerResponseParser.removeDevice(EnablerResponseParser.java:14
89)
at com.mobax.mashup.servlet.signage.RemoveDevice.processRequest(RemoveDevice.java:60)
at com.mobax.mashup.servlet.signage.RemoveDevice.doGet(RemoveDevice.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
As per Our understanding,
We are invoking the method port1.getDeviceResponse() . Before receiving the response for this request, we are invoking another method port1.removeDevice() . The Proxy seems to be waiting for the Response for the second request removeDevice() . When it receives the Response for the first request getDeviceResponse(), the proxy tries to parse this response assuming that this response belongs to the Second request, thus Resulting in Classcast Exception.
We would like to know whether anybody have Successfully implemented the WSAddressing in their Services without having any issues.
Interestingly, we had find out a WORKAROUND for this issue. The workaround is to generate the following code for every Request. i.e., before calling any Requests, if we generate the following proxy every time newly, then the Exception does not Occurs.
Code:
port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
BindingProvider bindingProvider = (BindingProvider)port1;
List<Handler> customHandlerChain = new ArrayList<Handler>();
customHandlerChain.add(new ClientHandler());
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBWS-2460) wsconsume --verbose does not show full error trace
by Thomas Diesler (JIRA)
wsconsume --verbose does not show full error trace
--------------------------------------------------
Key: JBWS-2460
URL: https://jira.jboss.org/jira/browse/JBWS-2460
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: tools-jaxws
Affects Versions: jbossws-native-3.0.4
Environment: JBoss-5.0.0.GA
Reporter: Thomas Diesler
Hi Folks,
when I invoke plain wsconsume, I get
> wsconsume ws-humantask-api.wsdl
parsing WSDL...
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
Error: Could not import. (use --verbose to see full traces)
Error: WsImport invocation failed. Try the verbose switch for more information
When I use the verbose switch, I get
> wsconsume --verbose ws-humantask-api.wsdl
parsing WSDL...
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
Error: Could not import. (use --verbose to see full traces)
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
The (invalid) wsdl itself you can get from here
http://www.oasis-open.org/committees/download.php/27599/ws-humantask-1.1-...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] Created: (JBWS-2823) CLONE -NameAlreadyBoundException when more than one virtual host are specified in @WebContext(virtualHosts) annotation variable
by Daniele Ulrich (JIRA)
CLONE -NameAlreadyBoundException when more than one virtual host are specified in @WebContext(virtualHosts) annotation variable
-------------------------------------------------------------------------------------------------------------------------------
Key: JBWS-2823
URL: https://jira.jboss.org/jira/browse/JBWS-2823
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-metro
Affects Versions: jbossws-metro-3.0.4, jbossws-metro-3.0.5
Reporter: Daniele Ulrich
Assignee: Richard Opalka
Priority: Minor
Fix For: jbossws-metro-3.1.0
To reproduce this problem uncomment the jaxws/jbws981 test case in test-excludes-jboss50x files:
< 08:45:01,579 ERROR [AbstractKernelController] Error installing to Start: name=jboss.web.deployment:war=/jaxws-jbws981 state=Create mode=Manual requiredState=Installed
< org.jboss.deployers.spi.DeploymentException: URL file:/opt/svn/jbossas/tags/JBoss_5_0_0_CR2/build/output/jboss-5.0.0.CR2/server/default/tmp/deploy/jaxws-jbws981.jar8416-exp.war/ deployment failed
< at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
< at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:358)
< at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:144)
< at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:459)
< at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
< at org.jboss.web.deployers.WebModule.start(WebModule.java:96)
< 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:157)
< at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
< 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:668)
< at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
< at $Proxy35.start(Unknown Source)
< at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
< at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
< at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
< at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
< at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
< at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
< at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
< at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
< at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
< at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
< at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
< at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
< at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
< at org.jboss.system.ServiceController.doChange(ServiceController.java:672)
< at org.jboss.system.ServiceController.start(ServiceController.java:444)
< at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:146)
< at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:104)
< at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:45)
< at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
< at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
< at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
< at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285)
< at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003)
< at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1024)
< at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944)
< at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
< at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
< at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
< at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
< at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
< at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
< at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
< at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:627)
< at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
< at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:812)
< 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:157)
< at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
< 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:668)
< 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.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:270)
< 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:157)
< at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
< at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
< at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
< at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
< at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
< at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
< at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
< at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
< at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
< 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:157)
< at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
< 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:668)
< at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815)
< at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416)
< 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
< at sun.rmi.transport.Transport$1.run(Transport.java:153)
< at java.security.AccessController.doPrivileged(Native Method)
< at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
< at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
< at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
< at java.lang.Thread.run(Thread.java:595)
< Caused by: java.lang.RuntimeException: javax.naming.NameAlreadyBoundException
< at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:539)
< at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
< at org.apache.catalina.core.StandardContext.start(StandardContext.java:4365)
< at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:352)
< ... 100 more
< Caused by: javax.naming.NameAlreadyBoundException
< at org.jnp.server.NamingServer.bind(NamingServer.java:165)
< at org.jnp.interfaces.NamingContext.bind(NamingContext.java:593)
< at org.jnp.interfaces.NamingContext.bind(NamingContext.java:554)
< at org.jboss.web.tomcat.service.deployers.TomcatDeployment$EncListener.lifecycleEvent(TomcatDeployment.java:522)
< ... 103 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months