Getting Content is not allowed in prolog message in console window when running sample TxM client app (Legacy_Onyx KB Id: 196234)
search cancel

Getting Content is not allowed in prolog message in console window when running sample TxM client app (Legacy_Onyx KB Id: 196234)


Article ID: 54992


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On



Customer is running tutorial from TransactionMinder 6.0 on a Solaris machine. He is able to post to WebServiceA which is protected by DCC Auth scheme and get back SAML session ticket response, however he fails on the redirect to WebServiceB which is protected by the SAML session ticket auth scheme. He sees the following error printed out in the console window from which the sample client application runs:

[Fatal Error] :1:1: Content is not allowed in prolog.
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at b5.a(DashoA8550)
at b2.&ltinit>(DashoA8550)
at b2.a(DashoA8550)
at t.a(DashoA8550)
at al.actionPerformed(DashoA8550)
at javax.swing.AbstractButton.fireActionPerformed(
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(
at javax.swing.DefaultButtonModel.fireActionPerformed(
at javax.swing.DefaultButtonModel.setPressed(
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(
at java.awt.Component.processMouseEvent(
at java.awt.Component.processEvent(
at java.awt.Container.processEvent(
at java.awt.Component.dispatchEventImpl(
at java.awt.Container.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.LightweightDispatcher.retargetMouseEvent(
at java.awt.LightweightDispatcher.processMouseEvent(
at java.awt.LightweightDispatcher.dispatchEvent(
at java.awt.Container.dispatchEventImpl(
at java.awt.Window.dispatchEventImpl(
at java.awt.Component.dispatchEvent(
at java.awt.EventQueue.dispatchEvent(
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(
at java.awt.EventDispatchThread.pumpEventsForHierarchy(
at java.awt.EventDispatchThread.pumpEvents(
at java.awt.EventDispatchThread.pumpEvents(

The policy server trace log (smtracedefault.log) shows the following message indicating that the user is not being disambiguated on the login call to WebServiceB:

Evaluating OnAuthAttempt policy...|asgsm1-tm|/txmdemo/tmb/WebServiceB||Sm_Auth_Message.cpp:946|12/14/2004|CSm_Auth_Message::AuthenticateUser||||Shipping Realm|||Bod User Store


Component: TXMFNC