[
https://issues.apache.org/jira/browse/ODE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606007#action_12606007
]
Rafal Rusin commented on ODE-305:
---------------------------------
ode-axis2.properties:
ode-axis2.db.mode=EXTERNAL
ode-axis2.db.ext.dataSource=java:OdeDS
ode-ds.xml:
<datasources>
<local-tx-datasource>
<jndi-name>OdeDS</jndi-name>
<connection-url>jdbc:oracle:thin:@localhost:1521:xe</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>ode</user-name>
<password>ode</password>
<min-pool-size>5</min-pool-size>
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
<check-valid-connection-sql>select sysdate from
dual</check-valid-connection-sql>
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
</local-tx-datasource>
</datasources>
The Transaction Manager is standard from JBoss (4.2.1GA), so I think it's it:
jboss-service.xml:
<!-- JBoss Transactions JTA -->
<mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService"
name="jboss:service=TransactionManager">
<attribute name="TransactionTimeout">300</attribute>
<attribute
name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute>
</mbean>
Regards
> No luck running ODE with Oracle (EXTERNAL connection)
> -----------------------------------------------------
>
> Key: ODE-305
> URL: https://issues.apache.org/jira/browse/ODE-305
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Environment: All versions (1.1.1 & 1.2RC1 JBI & JBoss), EXTERNAL
> connection using dbcp connection pool
> Reporter: Rafal Rusin
>
> I tried to run ODE with Oracle, but I experienced problems as below. Those
> problems don't happen on Derby EMBEDDED and MySQL INTERNAL connections.
> My preocess is following:
> <receive listeningService cresteInstance="true"/>
> <invoke service1 with correlation c1 initiate="yes"/>
> <receive on service2 correlation c1 initiate="no"/>
> I run a test in a loop, which runs those processes in parallel.
> Do you have any ideas about it?
> 2008-06-18 10:00:31,974 FATAL
> [org.apache.ode.bpel.engine.OutstandingRequestManager] INTERNAL ERROR: No
> ENTRY for RESPONSE CHANNEL 123
> 2008-06-18 10:00:31,974 ERROR [org.apache.ode.bpel.engine.BpelEngineImpl]
> Scheduled job failed; jobDetail={type=INVOKE_INTERNAL,
> mexid=hqejbhcnphr3d43350qaw8, pid={http://test.pl/test-1}
> java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for RESPONSE
> CHANNEL 123
> at
> org.apache.ode.bpel.engine.OutstandingRequestManager.associate(OutstandingRequestManager.java:145)
> at
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.inputMsgMatch(BpelRuntimeContextImpl.java:872)
> at
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:211)
> at
> org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:198)
> at
> org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:362)
> at
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:328)
> at
> org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:341)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:340)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:179)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:339)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:336)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 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)
> 2008-06-18 10:00:31,992 ERROR
> [org.apache.ode.scheduler.simple.SimpleScheduler] Error while executing
> transaction
> org.apache.ode.bpel.iapi.Scheduler$JobProcessorException:
> java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for RESPONSE
> CHANNEL 123
> at
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:338)
> at
> org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:373)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:341)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(SimpleScheduler.java:340)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:179)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:339)
> at
> org.apache.ode.scheduler.simple.SimpleScheduler$4.call(SimpleScheduler.java:336)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
> at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> 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: java.lang.IllegalArgumentException: INTERNAL ERROR: No ENTRY for
> RESPONSE CHANNEL 123
> at
> org.apache.ode.bpel.engine.OutstandingRequestManager.associate(OutstandingRequestManager.java:145)
> at
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.inputMsgMatch(BpelRuntimeContextImpl.java:872)
> at
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:211)
> at
> org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:198)
> at
> org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(BpelProcess.java:362)
> at
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:328)
> ... 11 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
