[
https://issues.apache.org/jira/browse/ODE-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730613#comment-13730613
]
Sathwik Bantwal Premakumar commented on ODE-997:
------------------------------------------------
This issue affects current deployments on Tomcat.
There are possibly 2 approaches.
1) Integrate an external TM managed by the Tomcat server (Ex: Bitronix,
Atokimos, etc).
I have evaluated this option with bitronix and can provide the steps to
integrate. This will involve few changes in the configuration file of ODE and
removal of some conflicting libraries with bitronix.
2) We use the same mechanism to create the managed connection factory as it is
done currently for the Internal/Embedded database configuration.
This would mean either we reuse the same set of config options as that of
internal/embedded or create a duplicate set for the external database
configuration. This option will need some refactoring of code.
if (TM available through JNDI) //configured in tomcat and registered in JNDI
then
use it
else
use the embedded TM and MCF
What do you think tammo/hadrain.
> External datasource pool is not transaction aware
> -------------------------------------------------
>
> Key: ODE-997
> URL: https://issues.apache.org/jira/browse/ODE-997
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.3.5
> Reporter: Sathwik Bantwal Premakumar
> Fix For: 1.3.6, 1.4
>
>
> Thanks to Nandika for reporting,
> http://markmail.org/message/lice5bxgfppheiqf?q=JobNoLongerInDbException+and+Incomplete+instances
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
