]
Kevin Conner commented on JBESB-2258:
-------------------------------------
The JBoss Remoting gateway has always registered itself in the registry although I am not
sure why it ever did this.
The safest action would be to reduce the logging level to DEBUG for now, at least until we
can determine why this was done.
Badly formed EPR. JBossRemotingGatewayListener registers esb-unaware
endpoints into the registry.
-------------------------------------------------------------------------------------------------
Key: JBESB-2258
URL:
https://jira.jboss.org/jira/browse/JBESB-2258
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Registry and Repository, Rosetta
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Priority: Minor
Fix For: 4.5
This causes ServiceInvoker to log this following at info level:
D21:56:04,636 INFO [ServiceInvoker] Badly formed EPR [EPR: PortReference <
<wsa:Address socket://localhost:8888/> >] for Service
[MyServiceCategory:MyWSProducerService] and Message [header: [ ]].Courier for EPR not
supported: ESB-unaware EPR used!
21:56:04,636 INFO [ServiceInvoker] Invalid EPR for service (probably ESB-unaware):
ignoring for mes
sage: header: [ ]
21:56:04,636 INFO [ServiceInvoker] Badly formed EPR [EPR: PortReference <
<wsa:Address
http://localhost:8765/> >] for Service
[MyServiceCategory:MyWSProducerService] and Message [header: [ ]].Courier for EPR not
supported: ESB-unaware EPR used!
21:56:04,636 INFO [ServiceInvoker] Invalid EPR for service (probably ESB-unaware):
ignoring for mes
sage: header: [ ]
Investigate what the reason is for the registration of the esb-unaware endpoints and see
if they can be safely removed. Perhaps the logging level might need tuning as I think this
confuses users plus will make logs more difficult to read.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: