Urgent : !!!! AutoCommit in EJB Transaction
Hi,
We have problem in stateless Session Bean with Bean Managed Transaction. We are getting SQLException - Connection closed. Even though we have tx.rollback() in catch, the some of the data which are inserted before the exception is commited.
When I checked the Connection's AutoCommit property after starting UserTransaction, it is set to "true". I am wondering does the Transaction Manager should change this to "false" and then give the connection if it is in Transaction.
Is there is any problem if I set the connection's AutoCommit to "true" in CMT and BMT?
please can any one respond urgently.
Regards
arun
This is a user specific setting
Ask the user to go to FB00 transaction,
In that go to the line item tab and there you will find a setting "Item selection goes to", select the option you want there and the system will change the behaviour.
Thanks
Naveen
Similar Messages
-
Urgent: EJB Transaction mechanism and Database Transaction mechanism
Anybody please clarify me how EJB transaction mechanism use the underlying database transaction mechanism? Here my concern is that in the context EJB transaction, how much reponsibilities are performed by EJB container and how much responsibilities are performed by underlying database server. I will deem it a great favor if you kindly explain the whole story with example(s).
Actually the ejb container is managing the persistence.
It will be like this.
if u r using entity beans or statefull beans
while creating entity bean class you have to specify in the
deployment descriptor, which table in the database this bean is representing .
On the runtime , when you are creating an instance of a entity bean ,that instance will be corresponds to a row in the mapped table.
what all changes you have made to that instance's attributes ie;
columns in that row that all will be avilable in the session
When you commit this particular session .this changes will be written to disk.
that's how the change is managed ...
assume if one user is modifying the particular row and another user is deleting it ..which ever transaction commits first will be get effected.
if modification is committing first and then delete the row will be deleted last.but if first delete and then modify while commiting modifycation..
you should get an error saying that particular row is missing from storage
this how ejb container is manging the persistence
in all cases even in case of synchronus acess
i think u r cleard with this much -
JDBC, JMS and EJB transactions - possible problem?
Hello,
I am using Oracle 9, Weblogic 8.1 SP 4, MyEclipse and
XDoclet.
In my current project I have the following piece of code
in one of my message driven beans (code cited as pseudocode
without unnecessary details):
* @ejb.bean name="MyMessageProcessor"
* display-name="Display name for a MyMessageProcessor"
* jndi-name="ejb/MyMessageProcessor"
* description="Bean MyMessageProcessor"
* destination-type="javax.jms.Queue"
* transaction-type="Container"
* acknowledge-mode="Auto-acknowledge"
* subscription-durability="Durable"
* generate="false"
* @ejb.transaction type="Required"
public class MyMessageProcessor implements MessageDrivenBean, MessageListener {
public void onMessage(Message msg) {
try {
//obtaining connections to two different databases via JNDi
java.sql.Connection connOne =
((DataSource)ctx.lookup("DataSourceOne")).getConnection();
java.sql.Connection connTwo =
((DataSource)ctx.lookup("DataSourceTwo")).getConnection();
// performing some UPDATEs and INSERTs on connOne and connTwo
// calling some other methods of this bean
//creating the reply JMS message and sending it to another JMS queue
Message msgTwo = this.createReplyMessage(msg)
this.queueSender.send(msgTwo);
//commiting everything
this.queueSession.commit();
} catch (Exception ex) {
try {
if (this.queueSession!=null) this.queueSession.rollback();
} catch (JMSException JMSEx) {};
this.context.setRollbackOnly();
Some days ago (before the final remarks from my client) there used to be only one DataSource configurated on the basis of the
connection pool with non-XA jdbc driver. Everything worked fine
including the transactions (if anything wrong happend not only wasn't the replymessage sent, but also no changes were written
to database and the incomming message was thrown back to the my bean's
queue).
When I deployed the second DataSource I was informed by an error message, that only one non-transactional resource may
participate in a global transaction. When I changed both datasources
to depend on underlying datasources with transatcional (XA) jdbc drivers, everything stopped working. Even if
EJB transaction was theoretically successfully rolledbacked, the changed were written to the database
and the JMS message wasn't resent to the JMS queue.
So here are my questions:
1. How to configure connection pools to work in such situations? What JDBC drivers should I choose?
Are there any global server configurations, which may influence this situation?
2. Which jdbc drivers should I choose so that the container was able to rollback the database transactions
(of course, if necessary)?
3. Are there any JMS Queue settings, which would disable the container to send message back to the
queue in case of setRollbackOnly()? How should be the Queue configurated?
As I am new to the topic and the deadline for the project seems to be too close I would be grateful
for any help.
This message was sent to EJB list and JDBC list.
Sincerely yours,
Marcin ZakidalskiHi,
I found these information extremely useful and helpful.
The seperate transaction for sending messages was, of course, unintentional. Thanks a lot.
Anyway, I still have some problems. I have made some changes to the
code cited in my previous mail. These changes included changing QueueSessions
to non-transactional. I also set the "Honorate global transactions" to true.
I am using XA JDBC driver. After setting "Enable local transactions" to false
(I did it, because I assume that JDBC transactions should be part on the global
EJB transaction) I got the following error:
java.sql.SQLException: SQL operations are not allowed with no global transaction by default for XA drivers. If the XA
driver supports performing SQL operations with no global transaction, explicitly allow it by setting
"SupportsLocalTransaction" JDBC connection pool property to true. In this case, also remember to complete the local
transaction before using the connection again for global transaction, else a XAER_OUTSIDE XAException may result. To
complete a local transaction, you can either set auto commit to true or call Connection.commit() or Connection.rollback().
I have also inspected the calls of methods of bean inside of onMessage() method just to check, whether
the transactions are correctly initialized (using the weblogic.transaction.Transaction class).
My questions are as follows:
1. Any suggestions how to solve it? I have gone through the google answers on that problem and only
thing I managed to realize that JDBC must start its own transaction. Is there any way to prohibit it
from doing that? Can using setAutocommit(true/false) change the situation for better?
2. How to encourage the JDBC driver to be a part of EJB transaction?
3. As I have noticed each of ejb method has its own transactions (transactions have different
Xid). Each method of the bean has "required" transaction attribute. Shouldn't it work in such
way that if already started transaction exists it is used by the called method?
4. The DataSources are obtained in my application via JNDI and in the destination environment I will have slight
impact on the configuration of WebLogic. What is least problematic and most common WebLogic configuration which would
enable JDBC driver to participate in the EJB transaction? Is it the WebLogic configuration problem or can it be
solved programmically?
Currently my module works quite fine when "enable local transactions" for DataSources is set to true, but this way
I am loosing the ability to perform all actions in one transaction.
Any suggestions / hints are more than welcomed. This message was posted to jdbc list and ejb list.
Marcin -
ORABPEL-08033: EJB Transaction Error
Hi
I have a usecase in which procA(sync Service) calling procB (Async Service) and on completion of execution, ProcB gives a non blocking invoke back to procA. Condition: The either of one should be in running state always.
However there are fault situation in ProcB hence to not to break the sequence we have put a catchAll block which handles/logs and then gives the non blocking invoke back to procA.
But when ProcB fails somewhere because of some other partner links, it is safely going into catchAll and handling it well and when it tries to do a non blocking invoke it is resulting in following:
ORABPEL-08033
EJB Transaction Error.
EJB exception happened while invoking the partner. Please verify partner service.
Can somebody give me some leads in this?
TIA
regards
JoyI have setup catch statements, both an catch all in the outermost scope and a catch for remote fault at the scope surrounding the call to the AQ. But that's not the issue. The problem is that BPEL don't get the error. The error stay's at the adapter and the BPEL don't come to a failed state.
-
Non transactional data source and ejb transaction
Inside an ejb method with trans-attribute = Required,
Do a bunch of things using a transactional data source and a bunch of things using
a non trasnactional data source.
Looks like the time spent doing the non-transactional data source related work
does not count for the transaction timeout defined for the ejb.
So, what happens here, the ejb transaction is suspended ( when I start using the
non transactional ds ) ?Hi,
"siddiqut" <[email protected]> wrote in message news:3fa7c79d$[email protected]..
Inside an ejb method with trans-attribute = Required,
Do a bunch of things using a transactional data source and a bunch of things using
a non trasnactional data source.
Looks like the time spent doing the non-transactional data source related work
does not count for the transaction timeout defined for the ejb.
So, what happens here, the ejb transaction is suspended ( when I start using the
non transactional ds ) ?The transaction is not suspended when you call something
which is not non-transactional.
Regards,
Slava Imeshev -
"domain was null"; rmicontext=false; JTA UserTransaction;EJB Transaction
Hi folks!
I´m doing a test with EJB´s and JTA transactions.
The goal of the test is to verify if the OC4J will recognize a JTA User Transaction opened by a client just before an EJB method invocation and use it inside the EJB method, instead of opening a new transaction.
So, I have an EJB with conteiner managed transaction feature "Required".
And I have a client of this EJB, that opens a JTA UserTransaction and performs some updates and calls the EJB.
After the EJB call, I throwed a RuntimeException. The proposal of throwing this exception is to force the rollback of all the transaction ( the updates made by the client and the updates made by the ejb must not be commited ).
My method seems like this ( actually it´s a little bit more structured, but for understading purporses, i put it all in one method only here ):
<pre>
public void testTransaction () {
boolean commit = false;
javax.transaction.UserTransaction ut = null;
try {
// getting the JTA Transaction
javax.naming.Context initCtx = new javax.naming.InitialContext();
ut = (javax.transaction.UserTransaction) initCtx.lookup("java:comp/UserTransaction");
ut.begin();
try{
//issue the update
Connection conn = null;
try {
Context ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("jdbc/JTADS");
conn = ds.getConnection();
PreparedStatement stmt = conn.prepareStatement("UPDATE dont_drop_this_table set field2 =? where field1 = ?");
stmt.setString(1, "First Record");
stmt.setInt(2, 1);
stmt.executeUpdate();
} finally {
if (conn != null) conn.close();
//issue another update via EJB
Hashtable env = new Hashtable();
String initialContextFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String securityPrincipal = "jazn.com/admin";//admin
String securityCredentials = "welcome";//admin
String providerUrl = "ormi://localhost:23791/jta";
env.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
env.put(Context.SECURITY_PRINCIPAL, securityPrincipal);
env.put(Context.SECURITY_CREDENTIALS, securityCredentials);
env.put("dedicated.rmicontext", "false");
env.put("dedicated.connection", "false");
env.put(Context.PROVIDER_URL, providerUrl);
Context ctx = new InitialContext(env);
Object home = ctx.lookup(jndiName);
Object o = PortableRemoteObject.narrow(home, Class.forName("mytest.MyEJBHome"))
Class clazz = o.getClass();
Method method = clazz.getMethod("create", null);
MyEJBBean bean = (MyEJBBean) method.invoke(o, null);
//invoking ejb
bean.updateTable(2, "Second Record")
//force an ArrayOutOfBoundsException, in order to test
//if the EJB container will rollback or commit the ejb transaction.
int x[] = { 0 };
x[1] = 1;
x[2] = 1;
} catch (Exception e) {
throw new RuntimeException(e);
//if there was no exception thrown until here... then commit
commit = true;
catch ( Exception e ) {
throw new RuntimeException (e);
finally {
try {
if ( commit ) ut.commit();
else ut.rollback();
} catch ( Exception e ) {
throw new RuntimeException (e);
</pre>
Now my question:
When I use dedicated.rmicontext = true or dedicated.connection = true, the EJB container commits the transaction, even after the exception thrown. I understand that EJB container open a new transaction, instead of use the existing one ( jta UserTransaction.
When I use dedicated.rmicontext = false and dedicated.connection = false, the EJB container rollbacks the transaction, as I expected.
I´ve seen many posts about "domain was null" message after a NullPointerException.
I did many tests, but no NullPointerException was thrown, even when calling the EJB remotely nor issuing concurrent calls.
- I need the container rollback the transaction.
- I found that it only rollbacks when I put dedicated.rmicontext = false and dedicated.connection = false.
- I found that when dedicated.rmicontext = false and dedicated.connection = false, a NullPointerException may ocurr.
This "domain was null" problem seems to be an OC4J bug and the rmicontext=true an workaround for this bug, but I can´t use rmicontext=true because it will make the EJB transaction not to be the same JTA UserTransaction opened before the EJB call.
Is there any other way to make an EJB transaction be the same JTA UserTransaction openned before the EJB call?
PS: I´m using JDeveloper 10.1.2
Thanks for any help...Can anybody help me?
I need to know how can I set my EJB to use the same connection opened by a POJO class via JTA. ( Actually I need the EJB and POJO class be in same JTA transaction )
If I set the dedicated.rmicontext to false, it works but I run to risk of getting a NullPointerException "domain was null".
I realy need your help!
Thanks! -
What happens to EJB transaction when user stops/reloads JSP?
My JSP application uses container managed EJBs. Frequently, my stateless
session beans manipulate entity beans.
Does anyone have any documentation about whether or not a containter-managed
EJB transaction will roll-back in the event that a user clicks "Stop" or
"Reload" while the bean transaction is processing?
Thanks in advance,
DBine.
http://www.flutter.com
Clicking stop has no effect if the request has already left the browser. It
just prevents the display of the result. There is nothing you can do about
that.
A real problem is if they get impatient and click your link or button
repeatedly and the back end transaction is (for example) putting a charge
repeatedly on their credit card. Best way to solve that is to id the
transaction before it happens (build it in as part of the url or action) and
only process that id once.
Cameron Purdy
[email protected]
http://www.tangosol.com
Consulting Services Available
"dbine" <[email protected]> wrote in message
news:39b6e29b$[email protected]..
> My JSP application uses container managed EJBs. Frequently, my stateless
> session beans manipulate entity beans.
>
> Does anyone have any documentation about whether or not a
containter-managed
> EJB transaction will roll-back in the event that a user clicks "Stop" or
> "Reload" while the bean transaction is processing?
>
> Thanks in advance,
>
> DBine.
> http://www.flutter.com
>
>
>
-
EJB transaction hanging over VPN connection
EJB transaction hanging over VPN connection
I am trying to diagnose a problem that only occurs when I am doing testing from home and connected via VPN to work.
We are using WL 10.3. Our clusters are setup to communicate via multicast. We have a stateless session bean that uses many different resources (Sybase DB, other EJBs, Sonic JMS). I have a local EJB on my home network that I am testing and it connects with other EJBs and resources on my corporate network. While I don't think it is related to the problem, there is a cluster of the same EJB I am trying to test deployed to my corporate environment. i.e. I am testing ResetService EJB and there is a deployed domain cluster of several ResetService EJBs in the environment I am connecting to. My local server and admin domain are named differently than the one deployed and my local ejb shouldn't try to connect to the cluster in the environment.
When I make a call into my local ejb everything seems to work as expected until it gets to the commit part of the transaction (after my ejb returns). At this point the executing thread hangs at the following location
"[STUCK] ExecuteThread: '16' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=2 tid=0x2e8cb400 nid=0x22fc in Object.wait() [0x3031f000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x091a4b18> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrePrepare(ServerTransactionImpl.java:2130)
- locked <0x091a4b18> (a weblogic.transaction.internal.ServerTransactionImpl)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:266)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean_shnf9c_EOImpl.resetTradeByRate(ResetTradeServiceBean_shnf9c_EOImpl.java:1921)
at advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean_shnf9c_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)This thread is obviously waiting for a notification from some other thread but it is unclear what exactly it is waiting for. This only seems to happen when I am connected via VPN because when I try this same setup connected directly to my corporate network at work it works fine.
I connected w/ debugger and tried to dig. Some interesting observations I see are.
1) The ServerTransactionImpl object that is hanging has a 'preferredHost' of a different machine on my corporate network. It is an EJB that my service got some information from but it wasn't involved in any create, update, or delete aspects of the tran so in theory it shouldn't be part of it. Does anyone know what exactly this peferredHost attribute is signifying? I also see this same remote ejb server reference defined in a ServerCoordinatorDescriptor variable.
2) I also sometimes see other XA resources (JMS) with this ServerTransactionImpl that point to references of resources that live on other machines on my corporate network (not my local ejb). This doesn't always seem to be the case though.
VPN will definetly block multicast packets from the corporate env back to my machine. I don't think it works from my machine to the corporate env machines either.
I also have two IPs when connected over VPN. One for my local home network and one given to me by my VPN client. I have setup my local WL server to listen on the VPN client provided IP which the corporate machines should be able to resolve and send TCP message over.
This definetly seems to be transaction related because when I remove the tran support from my ejb things work as expected. The problem is I need to test within the transaction just like it runs in a deployed environment so this isn't really a fix.
My theory: My local test WL EJB is waiting for a communication from some other server before it can commit the tran. This communication is blocked due to my VPN connection. I just don't know what exactly it is trying to communicate and how to resolve if that is in fact the problem. I thought about looking into unicast rather than multicast for cluster communication but in my mind that doesn't come into play here because I am not deploying a local cluster for my EJB and I thought multicast was just used for inter-cluster communication.
I also saw some docs talking about resources need to be uniquely named when inter-domain communication is performed (http://docs.oracle.com/cd/E13222_01/wls/docs81/ConsoleHelp/jta.html#1120356).
Anyone have any thoughts on what might be going on?
Here is some log output from my local WL instance:
Servers in this output--
My test Server - AdminServer+10.125.105.14:7001+LJDomain+t3
Server in env I read data from during ejb method call - TradeAccessTS_lkcma00061-1+171.149.24.240:17501+TradeSupportApplication2+t3
Server in env I read data from during ejb method call - MesaService_lkcma00065-1+171.149.24.244:17501+MESAApplication1+t3
Server in env I read data from during ejb method call - DataAccess_lkcma00055-0+171.149.24.234:17500+AdvantageApplication1+t3
Server in env I read data from during ejb method call - DataAccess_lkcma00053-6+171.149.24.232:17506+AdvantageApplication1+t3
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606895> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: ServerTransactionImpl.commit()>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606895> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: TX[BEA1-0005C168CCCC337F43A8] active-->pre_preparing>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606896> <BEA-000000> <SC[LJDomain+AdminServer] active-->pre-preparing>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606896> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: before completion iteration #0>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606896> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: Synchronization[weblogic.ejb.container.internal.TxManager$TxListener@11b0cf9].beforeCompletion()>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606897> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: Synchronization[weblogic.ejb.container.internal.TxManager$TxListener@11b0cf9].beforeCompletion() END>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606898> <BEA-000000> <SC[LJDomain+AdminServer] pre-preparing-->pre-prepared>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606898> <BEA-000000> <SC[TradeSupportApplication2+TradeAccessTS_lkcma00061-1] active-->pre-preparing>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606898> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: delist weblogic.jdbc.wrapper.JTSXAResourceImpl, TMSUSPEND, beforeState=new, startThread=null>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606898> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: delist weblogic.jdbc.wrapper.JTSXAResourceImpl, afterStatenew>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606899> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: sc(TradeAccessTS_lkcma00061-1+171.149.24.240:17501+TradeSupportApplication2+t3+).startPrePrepareAndChain>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606900> <BEA-000000> <SC[TradeSupportApplication2+TradeAccessTS_lkcma00061-1] pre-preparing-->pre-preparing>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606902> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: delist weblogic.jdbc.wrapper.JTSXAResourceImpl, TMSUSPEND, beforeState=new, startThread=null>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606903> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: delist weblogic.jdbc.wrapper.JTSXAResourceImpl, afterStatenew>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTANaming> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606903> <BEA-000000> <SecureAction.runAction Use Subject= <anonymous>for action:sc.startPrePrepareAndChain to t3://171.149.24.240:17501>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606903> <BEA-000000> <PropagationContext: Peer=null, Version=4>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606904> <BEA-000000> < +++ otherPeerInfo.getMajor() :: 10>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606904> <BEA-000000> < +++ otherPeerInfo.getMinor() :: 3>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606904> <BEA-000000> < +++ otherPeerInfo.getServicePack() :: 1>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606905> <BEA-000000> < +++ otherPeerInfo.getRollingPatch() :: 0>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278606905> <BEA-000000> < +++ otherPeerInfo.hasTemporaryPatch() :: false>
####<Mar 20, 2012 4:23:26 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0005C168CCCC337F43A8> <> <1332278606905> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: waitForPrePrepareAcks AdminServer+10.125.105.14:7001+LJDomain+t3+=>pre-prepared TradeAccessTS_lkcma00061-1+171.149.24.240:17501+TradeSupportApplication2+t3+=>pre-preparing MesaService_lkcma00065-1+171.149.24.244:17501+MESAApplication1+t3+=>active DataAccess_lkcma00055-0+171.149.24.234:17500+AdvantageApplication1+t3+=>active DataAccess_lkcma00053-6+171.149.24.232:17506+AdvantageApplication1+t3+=>active>
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Then eventually I get timeout errors like below in log
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789379> <BEA-000000> < +++ otherPeerInfo.getMajor() :: 10>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789380> <BEA-000000> < +++ otherPeerInfo.getMinor() :: 3>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789380> <BEA-000000> < +++ otherPeerInfo.getServicePack() :: 1>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789381> <BEA-000000> < +++ otherPeerInfo.getRollingPatch() :: 0>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789382> <BEA-000000> < +++ otherPeerInfo.hasTemporaryPatch() :: false>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789382> <BEA-000000> < +++ Using new Method for reading rollback reason....>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTANaming> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789383> <BEA-000000> <RMI call coming from = TradeSupportApplication2>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTANaming> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789384> <BEA-000000> <SecureAction.stranger Subject used on received call: <anonymous> for action: startRollback AUTHENTICATION UNDETERMINABLE use SecurityInteropMode>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789385> <BEA-000000> <PropagationContext.getTransaction: tx=null>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789385> <BEA-000000> <PropagationContext.getTransaction: xid=BEA1-0005C168CCCC337F43A8, isCoordinator=true, infectCoordinatorFirstTime=false, txProps={weblogic.transaction.name=[EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)], weblogic.jdbc=t3://171.149.24.240:17501}>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789391> <BEA-000000> < +++ looking up class : weblogic.transaction.internal.TimedOutException :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789397> <BEA-000000> < +++ looking up class : weblogic.transaction.TimedOutException :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789398> <BEA-000000> < +++ looking up class : java.lang.Exception :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789398> <BEA-000000> < +++ looking up class : java.lang.Throwable :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789402> <BEA-000000> < +++ looking up class : [Ljava.lang.StackTraceElement; :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789403> <BEA-000000> < +++ looking up class : java.lang.StackTraceElement :: in classloader : java.net.URLClassLoader@15e92d7>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTAPropagate> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789404> <BEA-000000> < +++ converted bytes to rollback reason : weblogic.transaction.internal.TimedOutException: Timed out tx=BEA1-0005C168CCCC337F43A8 after 30000 seconds>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789404> <BEA-000000> <Name=[EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)],Xid=BEA1-0005C168CCCC337F43A8(21880283),Status=Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Timed out tx=BEA1-0005C168CCCC337F43A8 after 30000 seconds],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=502,seconds left=29497,activeThread=Thread[[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],XAServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(ServerResourceInfo[weblogic.jdbc.wrapper.JTSXAResourceImpl]=(state=new,assigned=none),xar=null,re-Registered = false),SCInfo[LJDomain+AdminServer]=(state=pre-prepared),SCInfo[TradeSupportApplication2+TradeAccessTS_lkcma00061-1]=(state=pre-preparing),SCInfo[MESAApplication1+MesaService_lkcma00065-1]=(state=active),SCInfo[AdvantageApplication1+DataAccess_lkcma00055-0]=(state=active),SCInfo[AdvantageApplication1+DataAccess_lkcma00053-6]=(state=active),properties=({weblogic.transaction.name=[EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)], weblogic.jdbc=t3://171.149.24.240:17501}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+10.125.105.14:7001+LJDomain+t3+, XAResources={LJDomain.AdminServer.JMSXASessionPool.advantage.jms.queue.sonicConnectionFactory, LJDomain.AdminServer.JMSXASessionPool.advantage.jms.topic.sonicConnectionFactory, WLStore_LJDomain__WLS_AdminServer, WSATGatewayRM_AdminServer_LJDomain},NonXAResources={})],CoordinatorURL=AdminServer+10.125.105.14:7001+LJDomain+t3+) wakeUpAfterSeconds(60)>
####<Mar 20, 2012 4:26:29 PM CDT> <Debug> <JTA2PC> <F68B599F56D71> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1332278789406> <BEA-000000> <BEA1-0005C168CCCC337F43A8: [EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]: setProperty: weblogic.transaction.name=[EJB advantage.tradesupport.rates.resets.ejb.ResetTradeServiceBean.resetTradeByRate(java.lang.Long,java.util.Set,java.lang.String,java.lang.String,boolean,advantage.common.service.context.ServiceContext)]>Hello asirigaya,
MSDTC configure does not belong to this forum, this forum topic is "Discuss client application development using Windows Forms controls and features."
I didn't see MSDN has this kind of forum so I will help you move this case to "Where is the forum for"
Regards,
Barry Wang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
EJB Transaction timeout and Statement Query Timeout
I am looking for some details on how statement query timeout is set when statement execution is part of the session bean transaction. I have done some test in webshere 6.1. and JBoss 5.0 and not getting the desired behavior. My understanding is following
- DB is Oracle 11g
- EJB transaction is set to 5 mins.
- Query time out setting is set to default vaule (not sure what is the default value)
- Session bean is updating say customer record using PreparedStatement
- Prior to calling session bean method I am locking the customer record using external/db tool and holding the lock.
- Call session bean method. Method waits endlessly for the lock to be acquired. No transaction rollback after 5 mins.
- After 10 minutes commit the transaction in the external db tool
- Session bean methods throws transaction rollback.
My understanding was that query timeout is set based on transaction "time to live". Please share out thoughts.
Edited by: hdjava on Jun 18, 2010 1:06 PM
Edited by: hdjava on Jun 18, 2010 1:07 PMThe following configuration seems working:
version: OC4J (9.0.3.0.0) (build 020927.1699)
AM deployment:
- bc4j.xcfg: <jbo.ejb.txntimeout>30000</jbo.ejb.txntimeout>
- orion-ejb-jar.xml: <session-deployment name="..." timeout="0"/>
OC4J config:
- data-source: inactivity-timeout="30000"
This keeps connection open for more than default 30 mins of inactivity (30000 secs configured).
Although, oc4j console prints multiple warnings:
DriverManagerConnectionPoolConnection not closed, check your code!
Looks like this is not an intended usage - but working.
Notice that it was a test, not a production environment.
Also pls see 9033: AM as EJB Session bean: pooled connection lost for new txn
I would be thankful for any experience in running AM Session EJB w/o timeout. -
Get and close connections many times in an EJB transaction drains pool
I have run into an odd bug in OC4J, and I'm hoping someone out there has the solution for it.
If I am inside an EJB transaction and call datasource.getConnection() and connection.close() more than (10 * max-connections) times, I can no longer get a connection from the datasource. Instead, I get this message:
java.sql.SQLException: Timed out waiting for an available connection after 60 seconds (connection pool reached max-connections which was set to 100)
at com.evermind[Oracle Application Server Containers for J2EE 10g (9.0.4.0.0)].sql.OrionPooledDataSource.waitForConnection(OrionPooledDataSource.java:1012)
Note the message says that max-connections is set to 100, when it is in fact set to 10. The figure is always 10 times the max-connections value.
These connections are not being held, each is released before the next is fetched.
The OC4J output looks like:
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@d042d7 to pool (Pool size: 1)
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@702936 to pool (Pool size: 2)
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@1c0db6a to pool (Pool size: 3)
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@616f6c to pool (Pool size: 98)
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@19d83c7 to pool (Pool size: 99)
[java] com.evermind.sql.DriverManagerConnectionPoolDataSource@1d4e49a: Releasing connection com.evermind.sql.DriverManagerPooledConnection@16ad2fd to pool (Pool size: 1)
[java] null: Releasing connection com.evermind.sql.DriverManagerXAConnection@c1ec95 to pool (Pool size: 100)
[java] com.evermind.sql.OrionPooledDataSource@46bb9f: Cache timeout, closing connection (Pool size: 0)
[java] com.evermind.sql.OrionCMTDataSource@1c80063: Cache timeout, closing connection (Pool size: 99)
[java] com.evermind.sql.OrionCMTDataSource@1c80063: Cache timeout, closing connection (Pool size: 98)
[java] com.evermind.sql.OrionCMTDataSource@1c80063: Cache timeout, closing connection (Pool size: 2)
[java] com.evermind.sql.OrionCMTDataSource@1c80063: Cache timeout, closing connection (Pool size: 1)
[java] com.evermind.sql.OrionCMTDataSource@1c80063: Cache timeout, closing connection (Pool size: 0)
Since often the number of times a connection is required in my application is data driven, I really need a general solution for this problem. Can anyone make a suggestion?We are facing the problem as given below.please advice.
We have developed an application wherein we are calling DB functions using Type-4 connections. We have deployed it on Oracle AS OC4J 10.1.2.0.2. When the function executes we get the below error in the log file.
When this error msg comes the application is unable to fetch the desired results.
How do we solve this issue?
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 13)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 12)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 11)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 10)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 9)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 8)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 7)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 6)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 5)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 4)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 3)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 2)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 1)
com.evermind.sql.OrionCMTDataSource@478e3074: Cache timeout, closing connection (Pool size: 0)
com.evermind.sql.OrionCMTDataSource@1326b07a: Cache timeout, closing connection (Pool size: 2)
com.evermind.sql.OrionCMTDataSource@1326b07a: Cache timeout, closing connection (Pool size: 1)
com.evermind.sql.OrionCMTDataSource@1326b07a: Cache timeout, closing connection (Pool size: 0)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 1)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 2)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 3)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 4)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 5)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 6)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 7)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 8)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 9)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 10)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 11)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 12)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 13)
null: Releasing connection oracle.jdbc.driver.T4CXAConnection@43bbf685 to pool (Pool size: 14) -
What driver and DataSource for EJB transactional semantics?
Hi people.
Joe Weinstein clarified a point that should be much clearer in the online docs:
"If you want EJB transactional semantics, you must use a TxDataSource."
I'm not clear about the relationship between TxDataSource and XA-drivers. I want
transactional EJB semantics.
So I must use TxDataSource.
Must I use XA-enabled drivers too?
What drivers can I use for Oracle?
Thanks, AlexHi Alexander,
You need to use XA driver in case you need truly distributed
transactions (spanning multiple databases instances).
Otherwise you could use non-XA driver with TxDataSource.
weblogic will simulate XA behavior. It will work for single
db instance.
Regards,
Slava Imeshev
"Alexander Bunkenburg" <[email protected]> wrote in
message news:3cd15be6$[email protected]..
>
Hi people.
Joe Weinstein clarified a point that should be much clearer in the onlinedocs:
>
"If you want EJB transactional semantics, you must use a TxDataSource."
I'm not clear about the relationship between TxDataSource and XA-drivers.I want
transactional EJB semantics.
So I must use TxDataSource.
Must I use XA-enabled drivers too?
What drivers can I use for Oracle?
Thanks, Alex -
Transaction support? Can i coordinate EJB transactions and COM+ transactions?
Can I call a transactional com object within an ejb transaction and have
success/rollback handled correctly? Or will I have to hand-code this? Are
any examples available?
Niels Harremoës
PricewaterhouseCoopersWebLogic jCOM does not support coordination of transactions over COM+. There
are no examples of manual transaction coordination in the WebLogic jCOM
examples, and at present BEA has no plans to create one.
Chris Hopper
BEA Systems, Inc.
"Niels Ull Harremoës" <[email protected]> wrote in news:3bcc91f4
@newsgroups.bea.com:
Can I call a transactional com object within an ejb transaction and have
success/rollback handled correctly? Or will I have to hand-code this? Are
any examples available?
Niels Harremoës
PricewaterhouseCoopers -
Excellent resources about EJB Transactions
Is there any good (better, excellent) web resource (or book) about EJB Transactions, covering topics like
- Flat Transactions vs. Nested Transaction
- Using EJB EntityBeans & Hibernate together: pay attention to Transaction Isolation
- Transaction Isolation examples, especially when having suspended transactions?
Thank you for any hint.
MichaelNothing's better than Google.
Rich -
What is the main advantage in EJB Transactions.
My question is i can have a stateless bean to accept the client requests and will set the Autocommit of database to false and which will invoke the java bean component based up on transaction code and passes the database connection object . the java bean component may perform its business logic and return a success or failure to the stateless bean. then the stateless bean can commit or rollback the transaction.
In the above case i am able to achieve atomicity . In that case what is the need for Transactions.
Thanks
Bala.Jyou're forgetting that EJBs are components.
I may decide that my component should call your component.
I may need to have all this work happen as a unit of work.
I may be on a different app-server (connections are not serializable)
Possibly your component is integrated into a larger work-flow process.
In these cases, a commit of rollback by your EJB would be incorrect. -
We are using Ejbs2.1
Our system uses Database but we are not writing IT System so we do not need To use trasactions at all.
We are using RequiresNew as the Transaction Attribute so every
ejb starts in a new transaction and each method only invoke one database access
We are now considering to change the Transaction Attribute to NotSupported So each database access will do a commit (the database connection is set to autoCommit)
We thought that this approach will be more efficient since no transaction will be created.
I will be happy to hear what you think about this approach, is our assumption is correct?it means that the method must operate outside of an active transaction - in other words there will be no active transaction during its runtime. If there is an active transaction when the method is called, that transaction is "put on hold" until the "notsupported" EJB call finishes.
Maybe you are looking for
-
Can we call two layouts for a single script?
Can we call two layouts for a single script? Where dow e assign print program to a script? in NACE transaction is it possible....... Thanks in advance. Regards. Abhilash.
-
We have various users reporting issues where they are missing records in Discoverer reports. After posting a journal in Oracle General Ledger the Discoverer report displays 1 or more related journal lines, while other lines from the same journal are
-
Lightroom 4 is the version
-
Problems with playback in Walkman
I had this issue with my Z, and am now having the same issue with my Z2. When I load music onto my handset (using a 32GB memory card for storage), it starts playing tracks but within 10 seconds or so it glitches and starts playing split-second bits o
-
Trouble signing into this forum
If I go to this page on this forum (http://community.vzw.com/t5/DROID-RAZR-by-Motorola/bd-p/RAZR) and click on the Sign In right above the list of messages, the sign in page it takes me to rejects my Username and password, saying the combination are