[Design of JBoss jBPM] - JTA integration
by tom.baeyens@jboss.com
There has been an email discussion about jBPM's JTA integration.
anonymous wrote : I am referring to the fact that Hibernate needs to be flushed in beforeCompletion(), and closed in afterCompletion(), which is currently impossible because everything happens in the close() method.
| ________________________________
|
| From: Tom Baeyens
| Sent: Thursday, December 14, 2006 5:05 AM
| To: Gavin King
| Cc: Dev - jBPM
| Subject: RE: jBPM *still* unusable in JTA environment
|
| we have fixed this in head, but it is not yet backported to 3.1 branch.
|
| at least, if you are referring to the capability of using the hibernate current session.
| ________________________________
|
| From: Gavin King
| Sent: Thu 12/14/2006 6:25 AM
| To: Dev - jBPM
| Subject: jBPM *still* unusable in JTA environment
|
| Guys, when are we going to get this fixed? It's been a long time since I raised this really major issue.
I now have added a configuration property to jBPM 3.1 to get this behaviour:
a) when a jbpm needs a hibernate session, it uses SessionFactory.getCurrentSession()
b) at jbpmContext.close(), jbpm does not do anything with the hibernate session. no flush and no close.
Do you need the flush method to be exposed too ? Eventually i want to add it, but doing that in 3.1.x might be tricky.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995305#3995305
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995305
19 years, 3 months
[Design of JBoss Internal Benchmarking] - Changes required for using the pooled invoker from the exist
by mahendra_kutare
anonymous wrote :
|
| I have made the changes to conf/jboss-service.xml and also to standardjboss.xml to use pooled invoker. What puzzles me is if i comment out UNIFIED INVOKER and the CONFIGURATION in jboss-service.xml all of the SPECJ ejb jars deployment fails.
|
| Can anyone explain this or experience this with SPECjAppServer2004 ?
|
| I am using FC5, SPECjAppServer2004 and MySQL 5.0.8 for my setup.
|
| Also my change for POOLED INVOKER to standardjboss.xml differs from entity-rmi-invoker using UNIFIED INVOKER only in the making the following line -
|
| <invoker-mbean>jboss:service=invoker,type=unified</invoker-mbean>
|
| to
|
| <invoker-mbean>jboss:service=invoker,type=pooled</invoker-mbean>
|
| I would like to know if all client and server interceptors from UNIFIED invoker be still valid for POOLED INVOKER -
|
| <invoker-proxy-binding>
| entity-rmi-invoker
| <invoker-mbean>jboss:service=invoker,type=POOLED</invoker-mbean>
| <proxy-factory>org.jboss.proxy.ejb.ProxyFactory</proxy-factory>
| <proxy-factory-config>
| <client-interceptors>
|
| org.jboss.proxy.ejb.HomeInterceptor
| org.jboss.proxy.SecurityInterceptor
| org.jboss.proxy.TransactionInterceptor
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor
|
|
| org.jboss.proxy.ejb.EntityInterceptor
| org.jboss.proxy.SecurityInterceptor
| org.jboss.proxy.TransactionInterceptor
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor
|
| <list-entity>
| org.jboss.proxy.ejb.ListEntityInterceptor
| org.jboss.proxy.SecurityInterceptor
| org.jboss.proxy.TransactionInterceptor
| <interceptor call-by-value="false">org.jboss.invocation.InvokerInterceptor
| <interceptor call-by-value="true">org.jboss.invocation.MarshallingInvokerInterceptor
| </list-entity>
| </client-interceptors>
| </proxy-factory-config>
| </invoker-proxy-binding>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995280#3995280
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995280
19 years, 3 months