BPEL-BAM JMS Sensor

Hi,
I am using Oracle BPEL and BAM Versions 10.1.2.1.
I created sensors according to the below mentioned link
http://download-west.oracle.com/docs/cd/B14099_19/integrate.1012/b15813/phase11.htm
I am able to see the created sensors and its values in the BPEL Process Manager for Order Approval Process. I could not find any document explaining how these sensor values can be used in Oracle BAM to display reports. Could you please provide me the necessary documents for the same?
Thank you.
Regards,
Praveen. G
Software Engineer.
iSOFT R & D Pvt. Ltd.
[email protected]

Hi Praveen,
Any data including JMS Sensor data that is piped into the BAM Active Data Cache can be used in BAM reports.
See the following:
http://www.oracle.com/technology/products/integration/bam/10.1.3/TechNotes/TechNote_BAM_BPELJMSSensors.pdf
http://www.oracle.com/technology/products/integration/bam/10.1.3/Tutorials/Tutorial_10_BAM_ProcessMonitoringReport.pdf
Regards, Stephen

Similar Messages

  • How to see data in BAM from sensor on BPEL activity?

    Hello, I 'am working with BPEL on Jdeveloper (last version).
    I have putted sensors on some activity of my process. On an other machine I have putted the BAM server (last version) which is ON and I have the BAM connection on Jdevlepper. Now I try to see data on BAM from sensor but I can't.
    Can someone explain me how to do?
    (I just can build some data just like in a data base with BAM architect but I can't read and put to graphics the ones from the sensors)
    Thank's much
    JAck

    Hello,
    To answer your question, I have install BAM on the same machine where BPEL server is running.
    Now I steel can't get sensor's data from BPEL:
    With BAM architect I can build data, with BAM studio I can use that data to design graphics but when I try to feed data from BPEL it doesn't work because I just can't press the OK button!!
    In BPEL : When I try to Create BAM sensor action (from structure panel), I can't generate the xsl map file no action is done when pressing OK, create mapping or edit mapping button!

  • Unable to send BPEL data to BAM using Sensor

    Dear All,
    I did a simple Hello world process in Jdev and trying to send the same BAM using Sensor.
    I am following this link to do the integration http://technology.amis.nl/2008/05/05/integrating-bpel-and-bam-in-oracle-11g-soa-suite/
    But data is not going to BAM.
    Could you please suggest.
    Thanks,

    HI,
    Are you getting any Error.while testing the application.If you could tel errors.I will help you.
    I thought that you missed some configuration steps for BAM Adapter and BAM Connection factory properties.please check below link wherever you configured or not in your server.
    http://fmwarchitects.blogspot.in/2013/03/configuring-oracle-bam-adapter.html
    I hope this will be helpful.
    Regards
    Siva Sankar
    Edited by: Shankar on Mar 20, 2013 8:11 PM

  • Best approach to monitoring 'status' and Time in BPEL/BAM?

    Hi,
    I have a composite to handle 'Orders' which goes through various stages in the process. The process will change the status of the order as it goes through various activities, and the statuses include 'Submitted', 'Started Processing' and 'Processed'.
    My question is, how would I monitor the average time that orders spend before they begin being processed i.e. the time difference between 'Submitted' status and 'Started Processing' status? Would it be using sensors (variable or activity) or feeding data through BAM adapter?
    My Data Object in BAM is currently set to hold each different order and then I have columns to record the Time at which it reaches these statuses. Following these, I then have columns to hold the differences in Time between stages to see how long the order spends in these stages E.g difference between 'Submitted' and 'Started Processing' etc etc
    Order ID | Submit Time | Started Processing Time | Processed Time | Time between 'Submitted' & 'Started Processing'
    001 | 09:00 | 11:00 | 12:00 | 2 Hours
    002 | 09:45 | 11:15 | 12:00 | 1 Hour 30 mins
    I would appreciate it if someone could guide me on whether this design approach is correct and how I can build on this please. E.g, is the data object correct for this and will it be easy to work out average times across multiple orders (not sure how I can currently include this in the data object)
    Thanks in advance

    Hi
    Yes, your data approach is correct.
    You can use BAM adapter to feed information from the composite level e.g. mediator to BAM
    and either Monitor Express ( 1-click as one response below pointed out and our recommended approach) or Sensors depending on your preference.
    You can send timestamps for various status from composite to BAM.
    Let BAM do the calculations for you.
    The order booking sample on BAM OTN under samples and tutorials will be a good sample to refer to.
    Also there are samples on Monitor Express, BPEL-BAM ( highlights BAM adapter at composite level)
    http://www.oracle.com/technology/products/integration/bam/collateral/Samples11g.html
    Regards
    Payal

  • How  to Set JMS property and Read JMS property in BPEL using JMS adapter

    Does any one know how to set or read more than one JMS property in BPEL using JMS adapter. My queue server is Oracle JMS server.
    Any help and sample is well appreciated

    Hi Van
    I have noted that only the attribute "type" is missing. It seems that when you create a "string" property, the attribute "type" is droped from the XML. If you use another type (as "integer" or "double") it stays there.
    If you try to read your properties, except for the "type" attribute, you should be successful, as I am. If you need, please tell me your email, I can send you my code.
    Source Code:
    in ASSIGN activity (process which SENDS the JMS message):
    <assign name="TESTES">
    <copy>
         <from expression="'string'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@type"/>
    </copy>
    <copy>
         <from expression="'name'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@name"/>
    </copy>
    <copy>
         <from expression="'value1'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@value"/>
    </copy>
    <bpelx:append>
         <bpelx:from>
         <Property name="" type="" value=""
              xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/"/>
         </bpelx:from>
         <bpelx:to variable="HeaderJms" part="outboundHeader"
              query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties"/>
    </bpelx:append>
    <copy>
         <from expression="'string'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@type"/>
    </copy>
    <copy>
         <from expression="'name2'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@name"/>
    </copy>
    <copy>
         <from expression="'value2'"/>
         <to variable="HeaderJms" part="outboundHeader"
         query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@value"/>
    </copy>
    </assign>
    in ASSIGN activity (process which READS the JMS message)
    <assign name="Assign_1">
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@name"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@value"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@name"/>
    <to variable="temp"/>
    </copy>
    <copy>
    <from variable="Variable_1" part="inboundHeader"
    query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@value"/>
    <to variable="temp"/>
    </copy>
    </assign>
    Note that I do not try to read the "type" attribute, otherwise it will fail.
    Here is the JMS Header Message received:
    <inboundHeader>
    <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">
    <JMSInboundHeaders>
    <JMSCorrelationID>
    bpel://localhost/pi_lms-c001e/BpelPiAtualizacaoC001E~1.0/3200025-BpInv0-BpSeq1.6-2
    </JMSCorrelationID>
    <JMSDeliveryMode>2</JMSDeliveryMode>
    <JMSExpiration>0</JMSExpiration>
    <JMSMessageID>ID:467DFA1FA1ED459EBF37F51F596C3F12</JMSMessageID>
    <JMSPriority>4</JMSPriority>
    <JMSRedelivered>false</JMSRedelivered>
    <JMSType>com.mercurio.lms.integration.c001eip.c001EIntegrationPoint</JMSType>
    <JMSTimestamp>1201552046253</JMSTimestamp>
    </JMSInboundHeaders>
    - <JMSInboundProperties>
    <Property name="JMSXDeliveryCount" type="integer" value="1"/>
    <Property name="JMSXRecvTimestamp" type="long" value="1201552046698"/>
    <Property name="JMSXUserID" value="lms_dev_int_v1_user"/>
    <Property name="JMS_OracleDeliveryMode" value="2"/>
    <Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
    <Property name="JMS_OracleDelay" type="long" value="0"/>
    <Property name="JMSXState" type="integer" value="0"/>
    <Property name="IAS_VERSION" value="10.1.3"/>
    <Property name="JMS_OracleDeliveryMode" value="2"/>
    <Property name="name" value="value1"/> ("type" attribute was droped!!!)
    <Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
    <Property name="name2" value="value2"/> ("type" attribute was droped!!!)
    </JMSInboundProperties>
    </JMSInboundHeadersAndProperties>
    </inboundHeader>
    Regards
    Marcelo

  • Polling messages based on priority in BPEL using JMS adapter

    Hi All,
    Is it possible to poll the messages based on the priority in BPEL using JMS adapter?
    I could set the priority for the messages but while polling it is picking the messages in FIFO(First in First out) order. But I want the messages to be picked on priority.Any help is appreciated.

    Do you only want to pick up messeges with a certain priority? So anything larger than say priority 2?
    You can try this: Oracle JCA Adapter for JMS - 11g Release 1 (11.1.1.5.0)
    Message SelectorThis field is also optional. It filters messages based on header and property information. The message selector rule is a Boolean expression. If the expression is true, then the message is consumed. If the expression is false, then the message is rejected.For example, you can enter logic, such as:
    JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected.
    JMSType = 'car' AND color = 'blue' AND weight > 2500
    Country in ('UK', 'US', 'France')

  • BAM and Sensors 040306

    I have seen that in BPEL we have " Create Sensor action " and Create BAM Sensor action". I don't find any documentation about "Create BAM sensor action " in BPEL developer Guide. Where is it?
    What is the best solution to implement sensors to comunicate with BAM ? using " Create Sensor action " and publish to a jms Topic or use " Create BAM sensor action" ?
    thanks
    Gonçalo Ribeiro

    hello once again,
    I need to configure BAM JNDI service Provider URL. and Initial context factory to get the information from a topic which is being written by a BPEL process sensor.
    In my sensor I have:
    Name: BAMPublisher
    Publish type: jms Topic
    Connection factory: jms/TopicConnectionFactory
    Publish Target: jms/demoTopic
    I have to get the jndi Name URL from my app server?! Where is it? The initial context factory?
    Second as soon as I get the information from the topic how can We access to that information? Could you please point me to the right documentation?
    Thanks
    Gonçalo Ribeiro

  • BPEL BAM integration couldn't populate data in BAM repository.

    I have created one BPEL process which had BAM sensor at beginning and at end. I have created everything has mentioned as per tutorial of BAM and BPEL integration but I couldn't see any data in BAM Architect.
    In BPEL consoles the BPEL process run successfully but in Sensor value tab I don't see anything.
    What is wrong and How can I debug this problem?

    Usually errors relating to BAM will show up in the BPEL domain logs on the BPEL server.
    Check the deployment descriptor for your BPEL process and make sure that the BAM settings are correct: host name, port (should be 80), user name, password, and domain.

  • BPEL / BAM problem scope variable

    Hi,
    I try to notice BAM from a BPEL Process.
    Actually my DataObject in BAM make lookups on the another one. So i have to notice 2 times BAM :
    - 1 for the DataObject which is the target of the lookup of the 2nd DataObject (that i call genericDO)
    - 1 for the DataObject which make lookups (specificDO)
    The reason for these 2 notifications is that lookup fields are readonly. I can't set values using my specificDO. So i have to insert 1 genericDO and then a sspecificDO.
    So to have to do 2 notifications.
    Now the real problem :
    On the activity, i place 1 Sensor which use 2 BAMSensorAction.
    Sensor (use 1 simple variable which contains 3 strings) :
    *<sensor sensorName="BAM_KO_Sensor" classname="oracle.tip.pc.services.reports.dca.agents.BpelActivitySensorAgent" kind="activity" target="Invoke_signalerErreur">*
    *<activityConfig evalTime="all">*
    *<variable outputDataType="notification" outputNamespace="http://xmlns.oracle.com/NotificationBAM" target="$notification"/>*
    *</activityConfig>*
    *</sensor>*
    My 2 BAMSensorAction :
    *<action name="BAM_KO_SensorAction" publishName="OracleBam" publishType="BAM" enabled="true">*
    *<property name="bamDataObjectKey"></property>*
    *<property name="batchStatus">false</property>*
    *<property name="batchLowerLimit">100</property>*
    *<property name="batchTimeout">500</property>*
    *<property name="bamTransform">bam/BAM_SensorAction.xsl</property>*
    *<property name="bamServer">http://s-bam-dev:80/OracleBAM/DataObject/DataObjectOperations.asmx</property>*
    *<property name="batchDefault">true</property>*
    *<property name="bamOperation">Insert</property>*
    *<property name="bamDataObject">/DE/Activation/IntegrationProcess</property>*
    *<property name="batchUpperLimit">500</property>*
    *<sensorName>BAM_KO_Sensor</sensorName>*
    *</action>*
    *<action name="BAM_KO_Process_SensorAction" publishName="OracleBam" publishType="BAM" enabled="true">*
    *<property name="bamDataObjectKey"></property>*
    *<property name="batchStatus">false</property>*
    *<property name="batchLowerLimit">100</property>*
    *<property name="batchTimeout">500</property>*
    *<property name="bamTransform">bam/BAM_Process_SensorAction.xsl</property>*
    *<property name="bamServer">http://s-bam-dev:80/OracleBAM/DataObject/DataObjectOperations.asmx</property>*
    *<property name="batchDefault">true</property>*
    *<property name="bamOperation">Insert</property>*
    *<property name="bamDataObject">/DE/ProcessTransverse/Process</property>*
    *<property name="batchUpperLimit">500</property>*
    *<sensorName>BAM_KO_Sensor</sensorName>*
    *</action>*
    I deploy the process without compilation problem.
    And at runtime, the instance works well, i can see the 1st Insert in BAM, but the 2nd one is never done. In the log i can see that the 1st one is flushed, but i have this error for the 2nd one :
    *<2009-05-12 14:17:20,775> <ERROR> <default.collaxa.cube.sensor> <DataRouter::send> error*
    ORABPEL-20301
    Echec du Data Publisher.
    Echec du Reporting Data Publisher BAM_KO_Process_SensorAction.
    Pour plus dinformations, consultez le fichier journal.
    at com.collaxa.cube.engine.sensor.sa.DataRouter.send(DataRouter.java:101)
    at com.collaxa.cube.engine.sensor.sa.DataRouter.send(DataRouter.java:133)
    at com.collaxa.cube.engine.sensor.dca.DataCaptureAgency.send(DataCaptureAgency.java:181)
    at com.collaxa.cube.engine.sensor.dca.DataCaptureAgency.sendActivityData(DataCaptureAgency.java:153)
    at com.collaxa.cube.engine.sensor.dca.DataCaptureAgency.onActivityComplete(DataCaptureAgency.java:227)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:205)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3698)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1655)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:217)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:314)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5765)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1722)
    at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem(CubeEngineBean.java:307)
    at sun.reflect.GeneratedMethodAccessor209.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
    at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
    at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
    at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
    at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
    at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
    at CubeEngineBean_LocalProxy_4bin6i8.handleWorkItem(Unknown Source)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
    at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: ORABPEL-20301
    Echec du Data Publisher.
    Echec du Reporting Data Publisher BAM_KO_Process_SensorAction.
    Pour plus dinformations, consultez le fichier journal.
    at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:137)
    at com.collaxa.cube.engine.sensor.registry.BpelSensorActionInfo.publish(BpelSensorActionInfo.java:178)
    at com.collaxa.cube.engine.sensor.sa.DataRouter.send(DataRouter.java:93)
    *... 37 more*
    Caused by: ORABPEL-02117
    Variable déjà déclarée.
    Une variable portant la clé "bamserver.hostname" a déjà été déclarée dans le scope en cours.
    Enlevez du code linstruction de déclaration de variable.
    at com.collaxa.cube.engine.core.Scope.__checkVariantDecl(Scope.java:1411)
    at com.collaxa.cube.engine.core.Scope.declareAndSet(Scope.java:800)
    at com.collaxa.cube.engine.sensor.dca.data.BpelCapturedData.getHeaderProperties(BpelCapturedData.java:199)
    at com.collaxa.cube.engine.sensor.sa.FilteredDataPublisher.publish(FilteredDataPublisher.java:105)
    at com.collaxa.cube.engine.sensor.sa.BpelPublisher.publish(BpelPublisher.java:129)
    *... 39 more*
    All what i can say is that i never declare any variable with bamserver.hostname key. The only spot in all my process where this value can be seen is the bpel.xml :
    *<preferences>*
    *<property name="bamserver.hostname" encryption="plaintext">s-bam-dev</property>*
    *<property name="bamserver.protocol" encryption="plaintext">http</property>*
    *</preferences>*
    Seems like a variable is declared by the 1st SensorAction, and the 2nd one try to declare it again...
    Any ideas on the problem ?

    Hi,
    Thx for the response.
    Actually there's no variable declaration visible in the bpel.xml. It was the first thing that i have look for, regarding to the exeption.
    That's why i suppose that there's some sort of runtime variable declaration by the BAM sensor. No certitude on this...
    And yes, when you place the two BAMSensorAction on two Sensors which are on activities in separate scopes... it works.
    Finally i avoid the problem doing something like that :
    <ScopeForBAMNotification>
    <ScopeForNotification1>Empty activity 1 with 1 sensor activity which use 1 sensorBAMAction</ScopeForNotification1>
    <ScopeForNotification2>Empty activity 1 with 1 sensor activity which use 1 sensorBAMAction</ScopeForNotification2>
    </ScopeForBAMNotification>
    Not pretty, but works...

  • How to configure the integration BPEL x JMS on oracle aplication server

    follwing the error
    <remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
    </part><part name="summary"><summary>file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
    file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor JMSConnectionTest neither through JNDI nor instantiate it as a Java class [Caused by: weblogic.jndi.WLInitialContextFactory]
    Please examine the log file to determine the problem.
    [Caused by: weblogic.jndi.WLInitialContextFactory]
    ; nested exception is:
         ORABPEL-12511
    Adapter Framework unable to create outbound JCA connection.
    file:/u05/bpel/bpel/domains/default/tmp/.bpel_BPELxxBEA_1.0_fce047d117b03b6f174defa6316f81cd.tmp/jms.wsdl [ Produce_Message_ptt::Produce_Message(item) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor JMSConnectionTest neither through JNDI nor instantiate it as a Java class [Caused by: weblogic.jndi.WLInitialContextFactory]
    Please examine the log file to determine the problem.
    [Caused by: weblogic.jndi.WLInitialContextFactory]
    Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
    </summary>
    </part><part name="detail"><detail>null</detail>
    </part></remoteFault>
    bpel cook book says on pag 143 for put this on my oc4j-ra.xml
    <connector-factory location="eis/wljms/Queue" connector-name="Jms Adapter">
         <config-property name="connectionFactoryLocation"
                             value="com.seebeyond.jms.client.STCTopicConnectionFactory"/>
         <config-property name="factoryProperties"
                             value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://acom06:8888;java.naming.security.principal=oc4jadmin;java.naming.security.credentials=welcome123"/>
         <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
         <config-property name="isTopic" value="false"/>
         <config-property name="isTransacted" value="true"/>
         <config-property name="username" value=""/>
         <config-property name="password" value=""/>
         <connection-pooling use="none">
         </connection-pooling>
         <security-config use="none">
         </security-config>
    </connector-factory>
    <connector-factory location="eis/wljms/Topic" connector-name="Jms Adapter">
         <config-property name="connectionFactoryLocation"
                             value="com.seebeyond.jms.client.STCTopicConnectionFactory"/>
         <config-property name="factoryProperties"
                             value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://acom06:8888;java.naming.security.principal=oc4jadmin;java.naming.security.credentials=welcome123"/>
         <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
         <config-property name="isTopic" value="true"/>
         <config-property name="isTransacted" value="true"/>
         <config-property name="username" value=""/>
         <config-property name="password" value=""/>
         <connection-pooling use="none">
         </connection-pooling>
         <security-config use="none">
         </security-config>
    </connector-factory>
    where..
    acom06 = my server
    8888 = my port
    oc4jadmin = root user
    welcome123 = pass
    and put a weblogic.jar on
    /j2ee/acom06/connectors/JmsAdapter/JmsAdapter
    what else I have to do ???
    God bless all

    Hi, Swarup:
    Thanks for your reply.
    The reality here is that we could not get solid support from BSAIS team, we came to many situations that we have to search around and tell them how to do the job like this (They are all afraid of Java Stack
    I will keep search, if you have detailed information how to and where to configure those parameters, please let me know.
    Regards!
    Liang

  • BPEL and JMS/AQ Request

    Hello everybody,
    It would be great if I could get some information on the following from BPEL Developers/ Experts.
    In our Project we are planning to have
    1. BPEL Server in Server 1
    2. JMS/ AQ in Server 2
    I want the BPEL Process to interact with the JMS/AQ component to send or receive XML messages.By writing a webservice I can accomplish this. But I would like to know how can I make BPEL Process in Server1 to interact with the JMS Queue in Server 2 "directly".
    Also please send me any links which are related to this , if any.
    Thanks in advance
    Susilkumar.V

    You can use JMS Adapter for this.

  • 11g TP4 BAM JMS example

    Hi,
    Just wanted to check if there are any example java applications for pushing data objects through JMS for TP4 ?
    I've tried the examples located in [JMS-EL-BAM.zip|http://www.oracle.com/technology/products/integration/bam/10.1.3/samplefiles/Samples/Zip_Files/JMS-EL-BAM.zip], but I haven't been able to get these to work.
    There seem to be issues here for the ICommand syntax, as well for the syntax of ReadJMSMessage_Car.ems, which I presume needs
    to be provisioned before running the example.
    Thanks,
    Niklas

    To be more specific, when running +"icommand -cmd import -file ReadJMSMessage_Car.ems"+
    I get this error:
    +"Importing of EMS from previous version is not supported."+
    I also get the same basic error when trying to import the ReadCarJMSData.plan:
    +"Importing of Plan from previous version is not supported."+

  • BPEL logging using sensors

    Hi,
    I need to use sensors for achieving logging in our BPEL process.
    I have gone through the documentation and found out that by default BPEL using sensors will log to database (when sensor action is database)
    The tables are:
    VARIABLE_SENSOR_VALUES
    ACTIVITY_SENSOR_VALUES
    and so on...
    residing in the SOAINFRA schema.
    However i am not able to find any documentation related to these. Can any one help me in this regard?
    Thanks,
    Rosh

    If you will start doing the simple example
    Then the table (i) VARIABLE_SENSOR_VALUES will store the data if any sensor is made on the variable(local or Global)
    (ii) ACTIVITY_SENSOR_VALUES will store the data if sensor is established on any Activity (ex invoke, reply)
    (iii)FAULT_SENSOR_VALUES will store the data in it if sensor is established on fault ( SelectionFailure , RemoteFault)
    Hope this would help.
    Regards,
    Pushp

  • BPEL & BAM installation

    1) I am getting problem while running the IRCA.bat for loading schema.
    Please give solution.
    2) I have Microsoft windows server 2003 R2 Standard Edition service pack 1. This version does not support Enterprise link installation. Please give solution

    From the Eclipse developer notes, it appears that the org.eclipse.ui.versioncheck plugin was removed at the last minute from the final release of Eclipse 3.0. The BPEL plugins for Eclipse attempt to make use of this plugin, which is why they don't work properly.
    As Edwin noted, the 0.8 version (which I managed to get from an Oracle rep at OpenWorld) does work properly with the right release of Eclipse. I was able to get from our Oracle reps a full install which includes a cut-down Eclipse with the plugins included (thanks to Juliana Button!) - not ideal but OK for evaluation purposes.
    Oracle needs to address this quickly if they expect a reasonable level of takeup - our dev team can't use the RC* versions of Eclipse 3 - too buggy!

  • BPEL Sensor for BAM report transaction rollback exception, ORABPEL-05002

    HI,
    I meet a question about BPEL sensor to BAM, it often report below error for Transaction rollback exception and timed out. After this error last half an hour, BPEL will thoughout connect database error and out of Memory.
    It is running on BPEL/BAM 10.1.3.5.
    <2010-01-19 17:33:42,595> <INFO> <default.collaxa.cube.sensor> Flushed 2 rows in BAM batch
    <2010-01-19 17:33:42,600> <INFO> <default.collaxa.cube.sensor> Flushed 6 rows in BAM batch
    <2010-01-19 17:33:42,600> <INFO> <default.collaxa.cube.sensor> Flushed 4 rows in BAM batch
    <2010-01-19 17:33:42,603> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
    javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
    javax.transaction.RollbackException: Timed out
         at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:633)
         at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:273)
         at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:162)
         at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:472)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
         at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
         at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
         at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
         at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:139)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
         at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
         at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
         at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.transaction.RollbackException: Timed out
         at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:633)
         at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:273)
         at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:162)
         at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:472)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
         ... 29 more
    <2010-01-19 17:33:42,604> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseScheduledWorker::process> Failed to handle dispatch message ... exception ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
    ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:171)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
         at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
         at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    <2010-01-19 17:33:42,605> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
    javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
    javax.transaction.RollbackException: Timed out
         at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:633)
         at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:273)
         at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:162)
         at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:472)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
         at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
         at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
         at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    javax.ejb.EJBException: An exception occurred during transaction completion: ; nested exception is: javax.transaction.RollbackException: Timed out
         at com.evermind.server.ejb.EJBUtils.createEJBException(EJBUtils.java:365)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:139)
         at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
         at CubeDeliveryBean_LocalProxy_4bin6i8.handleInvoke(Unknown Source)
         at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
         at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
         at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
         at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
         at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
         at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
         at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
         at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
         at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
         at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
         at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
         at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
         at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
         at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: javax.transaction.RollbackException: Timed out
         at com.evermind.server.ApplicationServerTransaction.checkForRollbackOnlyWhileInCommit(ApplicationServerTransaction.java:633)
         at com.evermind.server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:273)
         at com.evermind.server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:162)
         at com.evermind.server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:472)
         at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:132)
         ... 29 more
    After half an hour, BPEL will report below error log:
    ORABPEL-04067
    Cannot update invoke message.
    The process domain was unable to update the state of the invocation message "99e5b70b31758b56:3c0225db:126439fa400:48c0". The exception reported is: Io exception: Connection reset
    Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: UPDATE invoke_message SET state = ? WHERE message_guid = ?
    I am not sure these two error has any relationship.
    But it is an issue that BAM sensor ofter report transaction time out.

    sorry, I forgot the below things which I tried to tune the JMS.
    <property name="retryMaxCount">10</property>
    <property name="retryInterval">60</property>
    <property name="useJCAConnectionPool">true</property>
    <property name="maxSizeJCAConnectionPool">500</property>
    Thanks.

Maybe you are looking for