Hi:
I'm trying to kick off a BPEL process via an incoming JMS message. I managed to get past the issue of the BC not accepting a Topic name with a slash character ("jms/topicName"), even though I've been sending messages to, and consuming messages from, this topic on Glassfish for a long time (to get past this issue, I changed the topic name). Now, when the NMR begins the normalization of my JMS message, it chokes on some part of it, with the error message "Content is not allowed in prolog". The content of the JMS message is valid and I've been consuming these messages for 6 months on this project with non-JBI-based code. Is the JMS binding component not quite ready for prime time yet? I'm a little reluctant to tell my users what types of topic names they can have, and what types of TextMessage payloads they're allowed to create, in order to use this feature of Glassfish. Below is the log output (the bold font is the text payload of my JMS TextMessage). I appreciate any feedback.
Wayne
[#|2008-04-07T10:06:14.153-0600|INFO|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=166;_ThreadName=JMSJCA sync #0(LocalAppEvents);126968673197097-64558-134268771741530065;ID:192-10.1.2.52(d3:f5:93:6a:db:32)-3007-1207584374153;|Received a JMS TextMessage, created message exchange ID 126968673197097-64558-134268771741530065; JMS Message ID ID:192-10.1.2.52(d3:f5:93:6a:db:32)-3007-1207584374153|#]
[#|2008-04-07T10:06:14.153-0600|INFO|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=166;_ThreadName=JMSJCA sync #0(LocalAppEvents);Heap memory usage: init=0MB; used=19MB; committed=22MB; max=99MB; used/max=19%
Non-heap memory usage: init=8MB; used=36MB; committed=36MB; max=96MB; used/max=38%
Thread count: 15; peak count: 16; total started: 24
Process uptime: 0d 0h 15m 15s; started at 1207583458 sec (Mon Apr 07 09:50:58 MDT 2008);|Received JMS TextMessage, text content is [b][Heap memory usage: init=0MB; used=19MB; committed=22MB; max=99MB; used/max=19%
Non-heap memory usage: init=8MB; used=36MB; committed=36MB; max=96MB; used/max=38%
Thread count: 15; peak count: 16; total started: 24
Process uptime: 0d 0h 15m 15s; started at 1207583458 sec (Mon Apr 07 09:50:58 MDT 2008)][/b]|#]
[#|2008-04-07T10:06:14.153-0600|INFO|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=166;_ThreadName=JMSJCA sync #0(LocalAppEvents);|Start normalizing the JMS message to NMR message|#]
[#|2008-04-07T10:06:14.168-0600|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=166;_ThreadName=JMSJCA sync #0(LocalAppEvents);_RequestID=8b980cca-434e-4138-b01a-3000bced8091;|[Fatal Error] :1:1: Content is not allowed in prolog.
|#]
[#|2008-04-07T10:06:14.168-0600|SEVERE|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.InboundMessageProcessorListenerEndpoint|_ThreadID=166;_ThreadName=JMSJCA sync #0(LocalAppEvents);org.xml.sax.SAXParseException: Content is not allowed in prolog.
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:239)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:283)
at com.sun.jbi.jmsbc.XmlUtil.createDocumentFromInputSource(XmlUtil.java:74)
[/b]
[Message sent by forum member 'wmadams' (wmadams)]
http://forums.java.net/jive/thread.jspa?messageID=268029