[
http://jira.jboss.com/jira/browse/JBESB-1191?page=comments#action_12385095 ]
Mark Little commented on JBESB-1191:
------------------------------------
The ServiceInvoker is working correctly in this regard: those EPRs really are
unresponsive. The problem is earlier in your stack trace where you get:
2007-10-23 15:18:17,837 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Courier lookup
failed for EPR [EPR: PortReference < <wsa:Address
http://0.0.0.0:8765/> >] for
Service [MyServiceCategory:MyWSProducerService] and Message [header: [ To: null, From:
null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]].
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)
The ServiceInvoker seems to pull the following EPRs from the registry:
<From
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>http://0.0.0.0:18888</wsa:Address>
</From>
2007-10-23 15:18:17,819 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] EPR=EPR:
PortReference < <wsa:Address socket://0.0.0.0:8888/> > XML=<?xml
version="1.0" encoding="UTF-8"?>
<From
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>socket://0.0.0.0:8888</wsa:Address>
</From>
2007-10-23 15:18:17,820 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] EPR=EPR:
PortReference < <wsa:Address
http://0.0.0.0:8765/> > XML=<?xml
version="1.0" encoding="UTF-8"?>
<From
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>http://0.0.0.0:8765</wsa:Address>
</From>
2007-10-23 15:18:17,821 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] EPR=EPR:
PortReference < <wsa:Address jms://localhost/queue/quickstart_performance6_esb/>,
<wsa:ReferenceProperties jbossesb:java.naming.factory.initial :
org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties
jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties
jbossesb:destination-type : queue/>, <wsa:ReferenceProperties
jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties
jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties
jbossesb:type : urn:jboss/esb/epr/type/jms/> > XML=<?xml version="1.0"
encoding="UTF-8"?>
<From
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing">
<wsa:Address>jms://localhost/queue/quickstart_performance6_esb</wsa:Address>
<wsa:ReferenceProperties>
<jbossesb:java.naming.factory.initial
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
<jbossesb:java.naming.provider.url
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
<jbossesb:destination-type
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
<jbossesb:specification-version
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
<jbossesb:connection-factory
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
<jbossesb:type
xmlns:jbossesb="http://schemas.jboss.com/ws/2007/01/jbossesb"&g...
</wsa:ReferenceProperties>
</From>
All of them are associated with the same service name. The fact the SI doesn't flag
this as a different error is wrong.
Unclear warning for unresponsive EPR
------------------------------------
Key: JBESB-1191
URL:
http://jira.jboss.com/jira/browse/JBESB-1191
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 IR2
Environment: Xen guest, Sun JVM
Reporter: Martin Vecera
Assigned To: Mark Little
Attachments: server.my.log
While running webservice producer performance test (see
https://svn.corp.jboss.com/repos/soa/trunk/qa/tests/quickstarts/performance6) I made one
of my EPR to become unresponsive for a while. This test is working with only one EPR at
the same time so I would expect that ESB shows me this EPR. Instead of this it showed me
incorrectly all the EPRs currently configured:
15:07:54,183 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference <
<wsa:Address
http://0.0.0.0:8765/> > for message: header: [ To: null, From: null,
ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]
15:07:54,336 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference <
<wsa:Address socket://0.0.0.0:8888/> > for message: header: [ To: null, From:
null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]
I tried to add one more completely unused EPR to see if ESB shows really everything.
Guess what - it shows:
15:23:29,141 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference <
<wsa:Address
http://0.0.0.0:8765/> > for message: header: [ To: null, From: null,
ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]
15:23:29,141 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference <
<wsa:Address
http://0.0.0.0:18888/> > for message: header: [ To: null, From:
null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]
15:23:29,142 INFO [ServiceInvoker] Unresponsive EPR: EPR: PortReference <
<wsa:Address socket://0.0.0.0:8888/> > for message: header: [ To: null, From:
null, ReplyTo: null, FaultTo: null, Action: null, MessageID: null, RelatesTo: null ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira