[esb-issues] [JBoss JIRA] Commented: (JBESB-2258) Badly formed EPR. JBossRemotingGatewayListener registers esb-unaware endpoints into the registry.

[Tom Fennelly (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12447371#action_12447371 ] 

Tom Fennelly commented on JBESB-2258:
-------------------------------------

Sorry, typo there.  I meant to say "...these endpoints are registered in order that..."

> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira