[jboss-jira] [JBoss JIRA] (WFLY-4047) SLSB with WebService Annotation generates duplicate endpoint when JMS transport used

Wojciech Oczkowski (JIRA) issues at jboss.org
Mon Nov 3 08:10:36 EST 2014 

     [ https://issues.jboss.org/browse/WFLY-4047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wojciech Oczkowski updated WFLY-4047:
-------------------------------------
    Description: 
When deploying Webservice with JMS transport as Stateless Session Bean, 2 endpoint's are published. One is ok JMSDefaultEndpoind and second is HTTPDefaultEndpoint which is treated as JMS endpoind somehow and fails to deploy with exception:

14:03:37,974 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "TestWSJMS-1.0-SNAPSHOT.jar"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72]
Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
	at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371)
	at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66)
	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251)
	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539)
	at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117)
	at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
	at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67)
	at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
	... 5 more
Caused by: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
	at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:115)
	at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:119)
	at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49)
	at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95)
	at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:895)
	at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131)
	at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362)
	... 13 more


> SLSB with WebService Annotation generates duplicate endpoint when JMS transport used
> ------------------------------------------------------------------------------------
>
>                 Key: WFLY-4047
>                 URL: https://issues.jboss.org/browse/WFLY-4047
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web Services
>    Affects Versions: 8.1.0.Final
>            Reporter: Wojciech Oczkowski
>            Assignee: Jason Greene
>
> When deploying Webservice with JMS transport as Stateless Session Bean, 2 endpoint's are published. One is ok JMSDefaultEndpoind and second is HTTPDefaultEndpoint which is treated as JMS endpoind somehow and fails to deploy with exception:
> 14:03:37,974 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestWSJMS-1.0-SNAPSHOT.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "TestWSJMS-1.0-SNAPSHOT.jar"
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_72]
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_72]
> 	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_72]
> Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
> 	at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:371)
> 	at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66)
> 	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251)
> 	at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539)
> 	at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:117)
> 	at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:129)
> 	at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:67)
> 	at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:75)
> 	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.1.0.Final.jar:8.1.0.Final]
> 	... 5 more
> Caused by: org.apache.cxf.configuration.ConfigurationException: Insufficient configuration for Destination. Did you configure a <jms:destination name="{http://test.ctdp.pl/}NewSessionBeanPort.jms-destination"> and set the jndiConnectionFactoryName ?
> 	at org.apache.cxf.transport.jms.JMSConfiguration.ensureProperlyConfigured(JMSConfiguration.java:115)
> 	at org.apache.cxf.transport.jms.JMSDestination.activate(JMSDestination.java:119)
> 	at org.apache.cxf.transport.AbstractObservable.setMessageObserver(AbstractObservable.java:49)
> 	at org.apache.cxf.binding.AbstractBaseBindingFactory.addListener(AbstractBaseBindingFactory.java:95)
> 	at org.apache.cxf.binding.soap.SoapBindingFactory.addListener(SoapBindingFactory.java:895)
> 	at org.apache.cxf.endpoint.ServerImpl.start(ServerImpl.java:131)
> 	at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:362)
> 	... 13 more



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

More information about the jboss-jira mailing list