[esb-issues] [JBoss JIRA] Commented: (JBESB-1191) Unclear warning for unresponsive EPR

Martin Vecera (JIRA) jira-events at lists.jboss.org
Fri Oct 19 04:46:03 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBESB-1191?page=comments#action_12383390 ] 
            
Martin Vecera commented on JBESB-1191:
--------------------------------------

It is a performance test that sends messages to one of the EPR at the same time under really heavy load. So sometimes it happens that the EPR is not available for a moment and the message have to be send again. But this INFO should appear only for the particular EPR being involved. Not for all of the currently configured EPRs. For instance the EPR <wsa:Address http://0.0.0.0:18888/> is not used at all and thus it should be responsive. 


> 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
>
> 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

        



More information about the esb-issues mailing list