| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error in console.txt. White space required between "SYS |
« View previous topic :: View next topic » |
| Author |
Message
|
| ruimadaleno |
 Posted: Tue Jan 20, 2015 3:22 am Post subject: Error in console.txt. White space required between "SYS |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
we are getting some errors in console.txt (full text bellow). This is hitting our production environment but, so far, we have no reports from users, but i cannot assume there is no impact in business, something is going wrong and we just don't know what 
so, i will open a PMR and report this issue to IBM, but this will get an low priority level and take too long to be solved  i'd like to investigate this issue further and i need your help 
There are several message flows deployed in this broker, how can i understand what is the message flow that is throwing this exception ?
| Code: |
Exception in thread "Thread-86" 2015-01-17 12:03:16.031 108 org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: White space is required between "SYSTEM" and the system identifier.
2015-01-17 12:03:16.031 108 at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:255)
2015-01-17 12:03:16.031 108 at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:157)
2015-01-17 12:03:16.031 108 at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:106)
2015-01-17 12:03:16.031 108 at com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:2220)
2015-01-17 12:03:16.031 108 at com.ibm.broker.axis2.SoapUtilities.createSOAPMessage(SoapUtilities.java:1920)
2015-01-17 12:03:16.031 108 at com.ibm.broker.axis2.Axis2Requester.processResponseMessageSync(Axis2Requester.java:2180)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)
2015-01-17 12:03:16.031 108 at com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:503)
2015-01-17 12:03:16.031 108 at com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:316)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)
2015-01-17 12:03:16.031 108 at com.ibm.broker.soap.SoapExtractNode.evaluate(SoapExtractNode.java:188)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal._propagate(Native Method)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:133)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbOutputTerminal.propagate(MbOutputTerminal.java:88)
2015-01-17 12:03:16.031 108 at com.ibm.broker.ct.mapping.MappingNode.buildAndPropagate(MappingNode.java:503)
2015-01-17 12:03:16.031 108 at com.ibm.broker.ct.mapping.MappingNode.evaluate(MappingNode.java:316)
2015-01-17 12:03:16.031 108 at com.ibm.broker.plugin.MbNode.evaluate(MbNode.java:1480)
2015-01-17 12:03:16.031 108 Caused by: javax.xml.stream.XMLStreamException: White space is required between "SYSTEM" and the system identifier.
2015-01-17 12:03:16.031 108 at com.ibm.xml.xlxp2.api.stax.msg.StAXMessageProvider.throwWrappedXMLStreamException(StAXMessageProvider.java:76)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.produceFatalErrorEvent(XMLStreamReaderImpl.java:2013)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.jaxb.JAXBXMLStreamReader.produceFatalErrorEvent(JAXBXMLStreamReader.java:316)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DocumentScanner.reportFatalError(DocumentScanner.java:4886)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DTDScanner.reportFatalError(DTDScanner.java:444)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DTDScanner.scanDoctypeDeclCommon(DTDScanner.java:534)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.stax.StAXDTDScanner.scanDoctypeDeclCommon(StAXDTDScanner.java:155)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DTDScanner.scanDoctypeDecl(DTDScanner.java:481)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl$DTDSupportProxy.scanDoctypeDecl(XMLStreamReaderImpl.java:227)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DocumentScanner.scanProlog(DocumentScanner.java:1757)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.scan.DocumentScanner.nextEvent(DocumentScanner.java:1324)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.stax.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:586)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.stax.XMLInputFactoryImpl$XMLStreamReaderProxyImpl.next(XMLInputFactoryImpl.java:183)
2015-01-17 12:03:16.047 108 at com.ibm.xml.xlxp2.api.wssec.WSSXMLInputFactory$WSSStreamReaderProxy.next(WSSXMLInputFactory.java:55)
2015-01-17 12:03:16.047 108 at org.apache.axiom.om.impl.builder.StAXBuilder.parserNext(StAXBuilder.java:567)
2015-01-17 12:03:16.047 108 at org.apache.axiom.om.impl.builder.StAXOMBuilder.nextToken(StAXOMBuilder.java:634)
2015-01-17 12:03:16.047 108 at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:175)
2015-01-17 12:03:16.047 108 ... 22 more
|
environment info:
WMB 8.0.0.4 running on windows 2008 server R2
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jan 20, 2015 5:38 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I suggest that you do some investigation before you open a PMR. You will only end up doing the work anyway because IBM L2 service will ask for all of the diagnostic data.
You should have found this already:
http://stackoverflow.com/questions/6514158/white-spaces-are-required-between-publicid-and-systemid
Read the accepted answer to find out what the error means.
| Quote: |
| how can i understand what is the message flow that is throwing this exception ? |
How do you normally diagnose errors in message flows? Usually, error handling logic is attached to every message flow that is deployed in production. Do your message flows have error handling?
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Tue Jan 20, 2015 6:47 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi Kimbert
Thank you for your reply, you gave me a excellent ideia to find the message flow throwing this exception. 
Every message flow in this environment stores info in record and replay (ok not every message flow, maybe 90% of the message flows , the ones designed with our policies), every xml input and every xml output is stored in record and replay datastore, so it should by easy to find a xml reply wich contains the string "White space is required between "SYSTEM" ".
I'll go for it and give some feedback.
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| Armageddon123 |
| Posted: Tue Jan 20, 2015 11:23 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2014
Posts: 61
|
We had a similar error recently, In case it helps you.
This kind of error was thrown after a HTTPrequest node.
The problem was, the response expected from the web service was XML, but what was being sent back was an HTML.
So the RCD node after HTTPrequest node was unable to process it throwing the error. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
