[MyServiceCategory:MyWSProducerService].org.jboss.soa.esb.co

[asachde]

I have a simple webservice (modification of webservice_producer from MR3 samples. When I sent a test message I get the following exception. Am I missing something in the config?

2007-08-30 17:10:43,153 DEBUG [org.jboss.soa.esb.listeners.ServiceInvoker] Courier lookup failed for EPR [EPR: PortRefer
ence < <wsa:Address http://localhost:8765/> >] for Service [MyServiceCategory:MyWSProducerService].
org.jboss.soa.esb.couriers.CourierException: Courier for EPR not supported yet
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.courierFromGenericEPR(TwoWayCourierImpl.java:155)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.courierFromEpr(TwoWayCourierImpl.java:137)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.getDeliverCourier(TwoWayCourierImpl.java:111)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.setToEpr(TwoWayCourierImpl.java:82)
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.<init>(TwoWayCourierImpl.java:69)
at org.jboss.soa.esb.couriers.CourierFactory.getCourier(CourierFactory.java:129)
at org.jboss.soa.esb.couriers.CourierFactory.getMessageCourier(CourierFactory.java:92)
at org.jboss.soa.esb.listeners.ServiceInvoker.getCourier(ServiceInvoker.java:285)
at org.jboss.soa.esb.listeners.ServiceInvoker.attemptDelivery(ServiceInvoker.java:210)
at org.jboss.soa.esb.listeners.ServiceInvoker.deliver(ServiceInvoker.java:163)
at org.jboss.soa.esb.listeners.ServiceInvoker.deliverSync(ServiceInvoker.java:129)
at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(Uncomposed
MessageDeliveryAdapter.java:107)
at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAda
pter.java:86)
at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:303
)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828)
at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:290)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java
:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
2007-08-30 17:10:43,153 INFO [org.jboss.soa.esb.listeners.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:A
ddress http://localhost:8765/> >

Following is my jboss-esb.xml config snippet

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

 </providers>
<services>
 <service category="MyServiceCategory" name="MyWSProducerService"
 description="WS Frontend speaks natively to the ESB">
 <listeners>
 <jbr-listener name="Http-Gateway" busidref="Http-1"
 is-gateway="true" maxThreads="1" />
 <jms-listener name="semsInitListener"
 busidref="semsInitChannel" maxThreads="5" is-gateway="false" />
 </listeners>
 <actions>
 <action name="print-before"
 class="org.jboss.soa.esb.actions.SystemPrintln">
 <property name="message"
 value="[Quickstart_webservice_producer] Message before invoking jbossws endpoint" />
 </action>
 <!-- action name="JBossWSAdapter"
 class="org.jboss.soa.esb.actions.soap.SOAPProcessor">
 <property name="jbossws-endpoint"
 value="SEMSWebService" />
 </action-->
 <action name="print-after"
 class="org.jboss.soa.esb.actions.SystemPrintln">
 <property name="message"
 value="[Quickstart_webservice_producer] Message after invoking jbossws endpoint" />
 </action>
 </actions>
 </service>

[asachde]

Okay... so found what this error was (the WS targeNamespace was incorrect). Once I corrected it the Courier Not supported went away and now I have a new exception.

2007-08-30 19:12:39,123 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught
while processing the action pipeline
java.lang.NullPointerException
at org.jboss.wsf.spi.management.EndpointRegistryFactory.getEndpointRegistry(EndpointRegistryFactory.java:46)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.getServiceEndpoint(SOAPProcessor.java:193)
at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:118)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:262)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297)
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)

[tfennelly]

I assume you're using JBossESB 4.2MR3 deployed on JBossAS 4.2.0GA patched with JBossWS2.0.0GA.

After that, can you please verify that the webservice_producer quickstart works, *unmodified*. If that's a success, can you then detail the exact set of change you made to the quickstart, up to the point that it no longer works.

Thanks.

[asachde]

I am using ESB ver 4.2 MR3 installed on ver 4.0.5 GA for app server but not sure if it's WS2.0.0GA. The manifest.mf in the jbossws.sar states the following

Implementation-Version: jbossws-1.0.3.SP1 (date=200609291417)

I am guessing I need to update the sar (any recommended way of upgrading?). BTW The quickstart webservice_producer gives the same error message. I had to modify it to use jboss MQ but no other changes.

[tfennelly]

OK.

Please read the README in these quickstarts. In the case of webservice_producer, it clearly states that this quickstart requires version 4.2.0GA of the App Server. It also directs you to read "install/readme.txt", which gives you directions re installing JBossWS2.0.0GA + the patch for the ESB.

[asachde]

Oops... will follow.