[esb-issues] [JBoss JIRA] Closed: (JBESB-611) org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work

Mark Little (JIRA) jira-events at lists.jboss.org
Sat Jun 9 17:44:19 EDT 2007


     [ http://jira.jboss.com/jira/browse/JBESB-611?page=all ]

Mark Little closed JBESB-611.
-----------------------------

    Resolution: Done

> org.jboss.soa.esb.actions.StaticRouter reports a fatal error - but it seems to work
> -----------------------------------------------------------------------------------
>
>                 Key: JBESB-611
>                 URL: http://jira.jboss.com/jira/browse/JBESB-611
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Examples
>    Affects Versions: 4.2 Milestone Release 2
>         Environment: RHEL5
> Sun Java 1.5
> ESB built from svn on June 6
>            Reporter: Len DiMaggio
>         Assigned To: Mark Little
>            Priority: Minor
>             Fix For: 4.2
>
>
> Potential bug:
> In trying a simple static router - with org.jboss.soa.esb.actions.StaticRouter - and text messages going thru a gateway listener - I'm seeing this error in the server log:
> ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog.
> This is with code and a jboss-esb.xml that worked with MR2 - also - although the error says fatal, the router seems to be working fine. A known problem? Thanks!
> Note - commenting out all the:
> [code]
>       <target class="NotifyConsole" /> 
> [/code]	
> statements in the jboss-esb has no effect. 
> See also:
>     http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110548

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