MBConnectorException

I setup a Messaging Bridge with Source Destination as the queue(JNDI Name:SourceJMSQueue)
defined in WebLogic JMS Server and Target Destination uses MQ Queue. When I put
a message in the SourceJMSQueue, I am getting the following error:
<Error> <WLI-Core> <BEA-530003> <Caught Exception:
com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create process
variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't read
XML (no root element) com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
Can't create process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
Can't read XML (no root element) at com.bea.wli.mbconnector.MBConnMDBBase.parseXmlMsg(MBConnMDBBase.java:
458) at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.ja
va:269)
at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:433)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
java:316)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Any thoughts ???
-Prasad

Never mind, I figured out. Trying ot post a text message where it's expecting a
XML message
"Prasad" <[email protected]> wrote:
>
I setup a Messaging Bridge with Source Destination as the queue(JNDI
Name:SourceJMSQueue)
defined in WebLogic JMS Server and Target Destination uses MQ Queue.
When I put
a message in the SourceJMSQueue, I am getting the following error:
<Error> <WLI-Core> <BEA-530003> <Caught Exception:
com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create
process
variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
Can't read
XML (no root element) com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
Can't create process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
Can't read XML (no root element) at com.bea.wli.mbconnector.MBConnMDBBase.parseXmlMsg(MBConnMDBBase.java:
458) at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.ja
va:269)
at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:433)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.
java:316)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
Any thoughts ???
-Prasad

Similar Messages

  • Timer Event Generator.

    Hi there
    I'm running WL Platform 8.1 SP4. I am using the timer event generator to fire requests to a channel/process. The timer is simply used to start a given process, there is no notion of message sent to it.
    Issues
    1) When defining a channel,
    e.g
    <channel name ="XToY" messageType="xml"
    qualifiedMetadataType="eg:TimerEventGenerator" />
    It seems I must define messageType="xml", if i define it as 'none' then it does not appear in the channel list when defining the timer event generator, therefore i cannot bind to it. So if I leave the messageType as xml, it appears. For the configuration of the timer, the message element is optional. Problem is when the timer now fires it throws the following error:
    <08-May-2006 10:25:25 o'clock BST> <Error> <WLI-Core> <BEA-489030> <Error publishing Timer Event message for XToYTimerEG : com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create proc
    ess variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't read XML (no root element)>
    Any ideas?
    2) Can someone direct me to any wlst scripts that allow the creation of a timer event generator in a cluster? ?I cannot find anything on dev2dev ?
    TIA
    Arvinder

    Ok, you can basically leave the messageType as XML
    and for the Timer EG configuration, for the optional message you can add <dummy/> this will fire the request and start a workflow or whatever is bound to the channel.

  • Problems with body email using Email Event Generator

    Hi I need to start a workflow when an email is received by a email account. In
    order to do that, I built a Email Event Generator that uses the next channel:
    <?xml version="1.0"?>
    <channels xmlns="http://www.bea.com/wli/broker/channelfile"
              channelPrefix="/cgr"
              xmlns:eg="http://www.bea.com/wli/eventGenerator"
              xmlns:dp="http://www.bea.com/wli/control/dynamicProperties"
              xmlns:oagpo="http://www.openapplications.org/003_process_po_007">
         <channel name ="Rendicion" messageType="none">
              <channel name ="RendicionEmail" messageType="xml"
              qualifiedMessageType="oagpo:PROCESS_PO_007"
              qualifiedMetadataType="eg:EmailEventGenerator"/>
         </channel>
    </channels>
    I'm using "Suscribe to a Message Broker" oprtion to start my work flow. That option
    uses two input variables: com.bea.xml.XmlObject and com.bea.wli.eventGenerator.EmailEventGeneratorDocument.
    * @jpd:mb-static-subscription message-metadata="{x1}" message-body="{x0}"
    channel-name="/cgr/Rendicion/RendicionEmail"
    public void subscription(com.bea.xml.XmlObject x0, com.bea.wli.eventGenerator.EmailEventGeneratorDocument
    x1)
    //#START: CODE GENERATED - PROTECTED SECTION - you can safely add code
    above this comment in this method. #//
    // input transform
    // parameter assignment
    this.body = x0;
    this.emailXML = x1;
    //#END : CODE GENERATED - PROTECTED SECTION - you can safely add code
    below this comment in this method. #//
    That configuration only functions when the email has plain text body containing
    a xml structure. Other waise that error is showed by the server:
    <Oct 24, 2003 4:16:26 PM GMT-05:00> <Error> <WLI-Core> <BEA-530203> <Error while
    publishing message: com.bea.wli.mbconnector.
    MBConnMDBBase$MBConnectorException: Can't create process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException
    : Can't read XML (no root element)>
    <Oct 24, 2003 4:17:26 PM GMT-05:00> <Error> <WLW> <000000> <Error publishing email:
    com.bea.wli.mbconnector.MBConnMDBBase$MBC
    onnectorException: Can't create process variable: com.bea.xml.XmlException: error:
    Unexpected element: TAG_END>
    <Oct 24, 2003 4:17:26 PM GMT-05:00> <Error> <WLI-Core> <BEA-530203> <Error while
    publishing message: com.bea.wli.mbconnector.
    MBConnMDBBase$MBConnectorException: Can't create process variable: com.bea.xml.XmlException:
    error: Unexpected element: TAG_E
    ND>
    Is it a Bug?, or Is the configuration wrong?
    Thank you very much
    David

    I've got the same issue going on here... I also posted the problem to this newsgroup
    earlier today.... please check your log files or server output window to see if
    you're also getting the encoding error...
    "David Uribe" <[email protected]> wrote:
    >
    Hi I need to start a workflow when an email is received by a email account.
    In
    order to do that, I built a Email Event Generator that uses the next
    channel:
    <?xml version="1.0"?>
    <channels xmlns="http://www.bea.com/wli/broker/channelfile"
              channelPrefix="/cgr"
              xmlns:eg="http://www.bea.com/wli/eventGenerator"
              xmlns:dp="http://www.bea.com/wli/control/dynamicProperties"
              xmlns:oagpo="http://www.openapplications.org/003_process_po_007">
         <channel name ="Rendicion" messageType="none">
              <channel name ="RendicionEmail" messageType="xml"
              qualifiedMessageType="oagpo:PROCESS_PO_007"
              qualifiedMetadataType="eg:EmailEventGenerator"/>
         </channel>
    </channels>
    I'm using "Suscribe to a Message Broker" oprtion to start my work flow.
    That option
    uses two input variables: com.bea.xml.XmlObject and com.bea.wli.eventGenerator.EmailEventGeneratorDocument.
    * @jpd:mb-static-subscription message-metadata="{x1}" message-body="{x0}"
    channel-name="/cgr/Rendicion/RendicionEmail"
    public void subscription(com.bea.xml.XmlObject x0, com.bea.wli.eventGenerator.EmailEventGeneratorDocument
    x1)
    //#START: CODE GENERATED - PROTECTED SECTION - you can safely
    add code
    above this comment in this method. #//
    // input transform
    // parameter assignment
    this.body = x0;
    this.emailXML = x1;
    //#END : CODE GENERATED - PROTECTED SECTION - you can safely
    add code
    below this comment in this method. #//
    That configuration only functions when the email has plain text body
    containing
    a xml structure. Other waise that error is showed by the server:
    <Oct 24, 2003 4:16:26 PM GMT-05:00> <Error> <WLI-Core> <BEA-530203> <Error
    while
    publishing message: com.bea.wli.mbconnector.
    MBConnMDBBase$MBConnectorException: Can't create process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException
    : Can't read XML (no root element)>
    <Oct 24, 2003 4:17:26 PM GMT-05:00> <Error> <WLW> <000000> <Error publishing
    email:
    com.bea.wli.mbconnector.MBConnMDBBase$MBC
    onnectorException: Can't create process variable: com.bea.xml.XmlException:
    error:
    Unexpected element: TAG_END>
    <Oct 24, 2003 4:17:26 PM GMT-05:00> <Error> <WLI-Core> <BEA-530203> <Error
    while
    publishing message: com.bea.wli.mbconnector.
    MBConnMDBBase$MBConnectorException: Can't create process variable: com.bea.xml.XmlException:
    error: Unexpected element: TAG_E
    ND>
    Is it a Bug?, or Is the configuration wrong?
    Thank you very much
    David

  • E-mail event generator errors

    We've done many different channels and not had many problems however, we've been
    experiencing problems when creating Email event generators that publish on a message
    broker channel and there's not a decent example in the documentation.
    The errors are listed in the attached file along with the contents of our channel
    definition file. The encoding error happens no matter how the e-mail is encoded.
    Has anybody seen this error? How was it resolved? An example would be helpful
    too!
    [email_channel_errors.txt]

    Hi Sean,
    The channel definition specifies through the ' messageType="xml" ' attribute that
    the message body is well-formed xml. Based on this I created an Email Event Generator
    that publishes to that channel (I used your channel definition). I sent four types
    of messages. Type 1 was a message with no body at all. Type 2 was a message with
    a random text body. Type 3 was a message with a malformed xml body. Type 4 was
    a message with a proper xml body. The results indicate that the error message
    you are seeing is due to a message being published that has no body at all (Type
    1 in my test).
    Type 1 - message with no message body content: BINGO!
    <Mar 24, 2004 10:49:24 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publishing
    message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create
    process variable: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException:
    Can't read XML (no root element)>
    Type2: Random text body:
    "<Mar 24, 2004 10:50:54 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publishing
    message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can't create
    process variable: com.bea.xml.XmlException: error: Unexpected element: CDATA>
    Type 3: Malformed xml body:
    <Mar 24, 2004 10:58:26 PM PST> <Error> <WLI-Core> <BEA-489203> <Error while publ
    ishing message: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: Can'
    t create process variable: weblogic.xml.stream.XMLStreamException: '>' expected
    [?! -- [CDATA[ ] - with nested exception: [weblogic.xml.stream.XMLStreamException:
    '>' expected [?! -- [CDATA[ ] - with nested exception: [Error at line:1 col:10
    '>' expected [/?! -- [CDATA[ ]]]>
    Type 4: well-formed XML message body
    ...No error message!...
    If there actually was a message body please post it and I'll give it a go.
    Hope this helps!
    Steve Waterhouse
    BEA WorldWide Technical Training
    "Sean McGillen" <[email protected]> wrote:
    >
    >
    >
    We've done many different channels and not had many problems however,
    we've been
    experiencing problems when creating Email event generators that publish
    on a message
    broker channel and there's not a decent example in the documentation.
    The errors are listed in the attached file along with the contents of
    our channel
    definition file. The encoding error happens no matter how the e-mail
    is encoded.
    Has anybody seen this error? How was it resolved? An example would
    be helpful
    too!

  • What is the format for a Client Request JMS message.

    I am trying to send directly to the JMS queue to start a WLI process. From the Workshop browser, the message is received. However, when sending my own JMS message, WebLogic complains with an "Unexpected message format" onMessageException.
    What is the correct format for a WLI Client Request node? A text message? Please help. Thanks - Frank.

    Kai,
    Thanks for the info. I have created a MB channel and a JMS event generator. But now it seems that my problem has simply been moved further out. Case in point: If I send a simple XML text message to the JMS event queue, the WebLogic JPD throws a MBConnectorException ("Could not determine channel type").
    So I am wondering if this is still not the best practice to accomplish what I want. Should I be using a MDB which then simply calls a JCX control that knows how to talk to the WLI start node? The whole idea is that I want to start the workflow with a simple JMS message.
    Thanks in advance,
    Frank

  • MessagingBridge with mqseries

    Hello, All.
              Due to searching a solution to integrate mqseries and weblogic with XA transactions and without WebSphere MQ Extended Transactional Client i thinking about using MessagingBridge.
              Main goal to use XA in mqseries+weblogic is code like
              EJB.method() {
              //operate with MQSeries via MessagingBridge and JMS
              //operate with JDBC
              //JDBC operation failed - don't send really to MQSeries
              //JDBC operation succ, transaction commited - data transferred
              So, sending message to queue will put message to messagingbridge, but messagingbridge should forward message to mqseries only after commit transaction.
              It is possible? How it should be configured?
              I think it should be like that
              <BridgeDestination
              AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
              Name="mq_q_xa_bridgeQueue" Properties="DestinationJNDI=TEST2;DestinationType=Queue;ConnectionURL=file:/c:/jndidir;InitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory;ConnectionFactoryJNDI=QCF2"/>
              <JMSBridgeDestination
              ConnectionFactoryJNDIName="thqueueconnectionfactory"
              DestinationJNDIName="bridgequeue" Name="THbridgequeue"/>
              <MessagingBridge AsyncEnabled="false" Name="mq2wlsXA"
              QOSDegradationAllowed="false" QualityOfService="Duplicate-okay"
              SourceDestination="mq_q_xa_bridgeQueue" Started="true"
              TargetDestination="THbridgequeue" Targets="cgServer"/>
              <MessagingBridge AsyncEnabled="true" Name="wls2mqXA"
              QOSDegradationAllowed="false" QualityOfService="Duplicate-okay"
              SourceDestination="THbridgequeue" Started="true"
              TargetDestination="mq_q_xa_bridgeQueue" Targets="cgServer"/>
              But when i send message to bridgequeue or to TEST2 mqseries queue, i have problems in weblogic.log
              <31.10.2005 18:02:52 MSK> <Error> <WLI-Core> <BEA-489003> <Caught Exception: com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: [WLI-Core:489049]Could not determine channel type
              com.bea.wli.mbconnector.MBConnMDBBase$MBConnectorException: [WLI-Core:489049]Could not determine channel type
                   at com.bea.wli.mbconnector.jms.JmsConnMDB.publishMBMessage(JmsConnMDB.java:270)
                   at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:466)
                   at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
                   at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
                   at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2804)
                   at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
                   at java.lang.Thread.run(Thread.java:534)
              >
              <31.10.2005 18:02:52 MSK> <Warning> <EJB> <BEA-010065> <MessageDrivenBean threw an Exception in onMessage(). The exception was:
              java.lang.IllegalStateException: [EJB:010167]Message-driven beans are not allowed to call setRollbackOnly..
              java.lang.IllegalStateException: [EJB:010167]Message-driven beans are not allowed to call setRollbackOnly.
                   at weblogic.ejb20.internal.MessageDrivenEJBContextImpl.setRollbackOnly(MessageDrivenEJBContextImpl.java:53)
                   at com.bea.wli.mbconnector.jms.JmsConnMDB.onMessage(JmsConnMDB.java:487)
                   at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
                   at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
                   at com.ibm.mq.jms.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:2804)
                   at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java:406)
                   at java.lang.Thread.run(Thread.java:534)
              >
              Thanks.

    3 : dis chl(*);
              AMQ8414: Display Channel details.
              CHANNEL(CHANNEL11) CHLTYPE(SVRCONN)
              AMQ8414: Display Channel details.
              CHANNEL(CHANNEL12) CHLTYPE(SDR)
              set MQSERVER=CHANNEL11/TCP/test02(5414)
              and it works. Strange, before was
              set MQSERVER=CHANNEL21/TCP/test02(5414)

Maybe you are looking for

  • How to backup downloaded updates in windows 8 ?

    I have recently updated my system and also updated some other softwares . but by mistakely i forgot to create a restore point of my system. now, i have installed many other softwares on my system and as a result something went wrong and my system is

  • PO creation changes the price in PO

    Hi As i am creating PO manually in the system, the quantity changes automatically to a rounding value. I have checked the material master, the rounding profile and rounding values are not maintained. The lot size is FX (Fixed lot) with quantity as 25

  • Free alternative to adobe indesign for macbook air

    I have experience in using adobe indesign however I have just brought a MacBook air and my copy of indesign is on my windows machine! is there a free alternative to indesign that anyone can recommend or someway of me getting it from a windows to a ma

  • How do I start the Setup Assistant???

    Okay, so I upgraded to Leopard, but the Setup Assistant got stuck on the "connecting" page during registration and stayed like that for an hour. I had no choice but to cancel and disconnected -- and that froze for another 20 minutes. So, I closed the

  • Cannot create connection pool with weblogic jDriver XA for oracle

    Hi everybody, we have serious problems configuring the weblogic jDriver for Oracle with support for distributed transactions. Everything works fine with the non-XA driver. We tried the suggestions given here before like setting the environment variab