Executing a jBPM process results in a DocumentException on SOA-P 4.3.0 CP02 with Sybase

Solution Verified - Updated -

Issue

We are using jBPM inside SOA-P 4.3.0 CP02 to orchestrate services. After a jBPM process instance is created and signalled to the first node with an EsbActionHandler, process execution fails with the following exception:

ERROR [org.jbpm.instantiation.FieldInstantiator] couldn't parse bean configuration : 
            <esbCategoryName xmlns="urn:jbpm.org:jpdl-3.2">BPM_Orchestration_Service1</esbCategoryName>
            <esbServiceName xmlns="urn:jbpm.org:jpdl-3.2">Service1</esbServiceName>
            <bpmToEsbVars xmlns="urn:jbpm.org:jpdl-3.2"><mapping bpm="theBo

org.dom4j.DocumentException: Error on line 4 of document  : The value of attribute "bpm" associated 
with an element type "mapping" must not contain the '<' character. 
Nested exception: The value of attribute "bpm" associated with an element type "mapping" 
must not contain the '<' character.
    at org.dom4j.io.SAXReader.read(SAXReader.java:482)
    at org.dom4j.DocumentHelper.parseText(DocumentHelper.java:278)
    at org.jbpm.instantiation.FieldInstantiator.parseConfiguration(FieldInstantiator.java:106)
    at org.jbpm.instantiation.FieldInstantiator.instantiate(FieldInstantiator.java:57)
    at org.jbpm.instantiation.Delegation.instantiate(Delegation.java:164)
    at org.jbpm.instantiation.Delegation.getInstance(Delegation.java:126) 

Environment

  • JBoss Enterprise SOA Platform (SOA-P) 4.3.0 CP02
  • Sybase ASE 12.5
  • jConnect 5.5 driver

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.