[esb-issues] [JBoss JIRA] Commented: (JBESB-1954) QS https_2way_ssl does not work

Jiri Pechanec (JIRA) jira-events at lists.jboss.org
Mon Aug 25 06:28:38 EDT 2008


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

Jiri Pechanec commented on JBESB-1954:
--------------------------------------

The problem is caused by JBR listener not supporting non-XML messages anymore. It should be either fixed by fixing JBR or changed to use XML payload.

> QS https_2way_ssl does not work
> -------------------------------
>
>                 Key: JBESB-1954
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1954
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Examples, Rosetta
>    Affects Versions: 4.4
>         Environment: 4.3 IR2
>            Reporter: Jiri Pechanec
>             Fix For: 4.4 CP1
>
>
> The excpetion is thrown when the QS is executed
> 2008-08-25 11:52:55,686 ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog.
> 2008-08-25 11:52:55,686 ERROR [org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener] JBoss Remoting Gateway failed to synchronously deliver message to target service [Https QS Category:MyHTTPSService].
> org.milyn.SmooksException: Unable to filter InputStream for target profile [org.milyn.profile.Profile#default_profile].
>         at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:287)
>         at org.milyn.delivery.dom.SmooksDOMFilter.doFilter(SmooksDOMFilter.java:235)
>         at org.milyn.Smooks.filter(Smooks.java:288)
>         at org.milyn.Smooks.filter(Smooks.java:253)
>         at org.jboss.soa.esb.services.security.auth.ws.WSSecurityInfoExtractor.extractSecurityInfo(WSSecurityInfoExtractor.java:92)
>         at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:512)
>         at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener$JBossRemotingMessageComposer.populateMessage(JBossRemotingGatewayListener.java:479)
>         at org.jboss.soa.esb.listeners.message.AbstractMessageComposer.compose(AbstractMessageComposer.java:76)
>         at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSyncWithoutDecomposing(UncomposedMessageDeliveryAdapter.java:104)
>         at org.jboss.soa.esb.listeners.message.UncomposedMessageDeliveryAdapter.deliverSync(UncomposedMessageDeliveryAdapter.java:86)
>         at org.jboss.soa.esb.listeners.gateway.JBossRemotingGatewayListener.invoke(JBossRemotingGatewayListener.java:337)
>         at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)
>         at org.jboss.remoting.transport.coyote.CoyoteInvoker.service(CoyoteInvoker.java:310)
>         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
>         at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>         at java.lang.Thread.run(Thread.java:595)
> Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
>         at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>         at org.milyn.delivery.dom.DOMParser.parse(DOMParser.java:120)
>         at org.milyn.delivery.dom.DOMParser.parse(DOMParser.java:87)
>         at org.milyn.delivery.dom.SmooksDOMFilter.filter(SmooksDOMFilter.java:283)
>         ... 16 more
> 2008-08-25 11:52:55,690 WARN  [org.jboss.soa.esb.actions.routing.http.HttpRouter] Received status code '500' on HTTP org.apache.commons.httpclient.methods.PostMethod at 153b61e request to 'https://localhost:9433/x/y'.
> This can be cuase by either bug in QS or JMS Router does not pass the message as valid XML

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

        



More information about the esb-issues mailing list