4 Replies Latest reply on Aug 14, 2009 2:46 AM by kconner

Problem JBR-PROVIDER HTTP

konstt2000 Aug 12, 2009 6:43 AM

Hi,

I've two webservice with his methods.
I've configured a jbr-provider for every webservice in different ports.

When I realize a call to the webservice every time it is listening in one of two ports alternative, ignoring the jbr-provider that has assigned.

Why??

Thaks.

My jboss-esb.xml is:

 <providers>
 <jms-provider name="JBossMQ" connection-factory="ConnectionFactory"
 jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
 jndi-URL="localhost">
 <jms-bus busid="EsbChannel">
 <jms-message-filter dest-name="queue/queueGde_esb" dest-type="QUEUE"/>
 </jms-bus>
 </jms-provider>

 <jms-provider name="JBossMQ2" connection-factory="ConnectionFactory"
 jndi-context-factory="org.jnp.interfaces.NamingContextFactory"
 jndi-URL="localhost">
 <jms-bus busid="EsbChannel2">
 <jms-message-filter dest-name="queue/queueGde_esb" dest-type="QUEUE"/>
 </jms-bus>
 </jms-provider>

 <jbr-provider name="JBR-Http" protocol="http" host="localhost">
 <jbr-bus busid="Http-1" port="8889" />
 </jbr-provider>

 <jbr-provider name="JBR-Http2" protocol="http" host="localhost">
 <jbr-bus busid="Http-2" port="8888" />
 </jbr-provider>

 </providers>

 <services>
 <service category="servicioConsultasGde" name="servicioConsultasGde" description="Servicio para realizar consultas de datos en GDE">
 <listeners>
 <jbr-listener name="Http-Gateway" busidref="Http-1" is-gateway="true" maxThreads="1"/>
 <jms-listener name="JMS-ESBListener" busidref="EsbChannel" maxThreads="1"/>
 </listeners>
 <actions>
 <action name="WebServiceGde" class="org.jboss.soa.esb.actions.soap.SOAPProcessor">
 <property name="jbossws-endpoint" value="WebServiceGde"/>
 </action>
 </actions>
 </service>

 <service category="AccesoGde" name="AccesoGde" description="Servicio para crear y modificar nuevas solicitudes en GDE">
 <listeners>
 <jbr-listener name="Http-Gateway2" busidref="Http-2" is-gateway="true" maxThreads="1"/>
 <jms-listener name="JMS-ESBListener2" busidref="EsbChannel2" maxThreads="1"/>
 </listeners>
 <actions>
 <action name="WebServiceConsultas" class="org.jboss.soa.esb.actions.soap.SOAPProcessor">
 <property name="jbossws-endpoint" value="WebServiceConsultas"/>
 </action>
 </actions>
 </service>
 </services>

</jbossesb>

1. Re: Problem JBR-PROVIDER HTTP

konstt2000 Aug 13, 2009 3:31 AM (in response to konstt2000)

Hello,

I've been trying...
Really the 1 Ã‚Âº called it correctly and the second one gives me a error in the port that should be listening.

If realized two calls to
http: // 127.0.0.1:8889/WebServiceGde/WebServiceGde with SOAPUI the first one works and the second not.

The error is:

09:31:03,225 INFO [ClassUtil] Loaded 4 classes from 2 URLs through class list file META-INF/content-handlers.inf. Process took 16ms. Turn on debug logging for more info.
09:31:03,678 INFO [ContentDeliveryConfigBuilder] All configured XML Element Content Handler resource configurations can be applied using the SAX or DOM Stream Filter. Defaulting to DOM Filter. Set 'global-parameters:stream.filter.type'. Turn on debug logging for more info.
09:31:03,693 INFO [ServiceInvoker] Badly formed EPR [EPR: PortReference < <wsa:Address http://localhost:8889/> >] for Service [servicioConsultasGde2:servicioConsultasGde] and Message [header: [ ]].Courier for EPR not supported: ESB-unaware EPR used!
09:31:03,693 INFO [ServiceInvoker] Invalid EPR for service (probably ESB-unaware): ignoring for message: header: [ ]
09:31:03,834 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://logica.webservice.gde.ree.es/}WebServiceConsultasPort does not contain operation meta data for: {http://logica.webservice.gde.ree.es/}crearSolicitud
 at org.jboss.ws.core.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:457)
 at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
 at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:185)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:520)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:392)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)
09:31:03,834 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://logica.webservice.gde.ree.es/}WebServiceConsultasPort does not contain operation meta data for: {http://logica.webservice.gde.ree.es/}crearSolicitud
 at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
 at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:157)
 at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
 at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645)
 at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
 at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:185)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:520)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:392)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)
09:31:03,850 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://logica.webservice.gde.ree.es/}WebServiceConsultasPort does not contain operation meta data for: {http://logica.webservice.gde.ree.es/}crearSolicitud
 at org.jboss.ws.core.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:457)
 at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:410)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
 at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:185)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:520)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:392)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)
09:31:03,850 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://logica.webservice.gde.ree.es/}WebServiceConsultasPort does not contain operation meta data for: {http://logica.webservice.gde.ree.es/}crearSolicitud
 at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
 at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:157)
 at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
 at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:645)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:432)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:273)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:190)
 at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:123)
 at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:185)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:520)
 at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:392)
 at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:538)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
 at java.lang.Thread.run(Thread.java:595)

2. Re: Problem JBR-PROVIDER HTTP

kconner Aug 13, 2009 9:45 AM (in response to konstt2000)

The error message is coming from JBossWS and it is stating that the deployed webservice does not contain the operation being invoked.

Can you create a simple, standalone example of this problem so that we can investigate?

Kev
Actions
3. Re: Problem JBR-PROVIDER HTTP

konstt2000 Aug 13, 2009 2:08 PM (in response to konstt2000)

Hi,

It works fine.
I've create two different "queue/queueGde_esb" (deployment.xml) one for every webservice and it works correctly.

Why???
Actions
4. Re: Problem JBR-PROVIDER HTTP

kconner Aug 14, 2009 2:46 AM (in response to konstt2000)

Not sure but I would be interested in an example so we can chase it down.

Kev
Actions

Go to original post