Breaking News
Home / ServerSide / Weblogic / Weblogic Server – Issue – Exceeded maximum allowed transactions on server

Weblogic Server – Issue – Exceeded maximum allowed transactions on server

Weblogic 11 Too many files open

Trouble time, sometimes when you start the weblogic server it fails to start up and throws an “Exceeded maximum allowed transactions on server”. Even restarting does not help.

Issue

The following issue can be seen in the weblogic log files.

May 2, 2011 9:47:27 AM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application
portalApp.
weblogic.management.ApplicationException: activate failed for portal_ejb
{
Module Name: eai_ejb, Error: Exception activating module: EJBModule(eai_ejb,status=PREPARED)

Unable to deploy EJB: Catalog from eai_ejb.jar:

[EJB:011007]Unable to create EJB Persistence Manager.
javax.transaction.SystemException: Exceeded maximum allowed transactions on server ‘mainServer’
at weblogic.transaction.internal.ServerTransactionManagerImpl.createTransaction

(ServerTransactionManagerImpl.java:14 34)
at weblogic.transaction.internal.TransactionManagerImpl.internalBegin

(TransactionManagerImpl.java:248) at weblogic.transaction.internal.ServerTransactionManagerImpl.internalBegin

(ServerTransactionManagerImpl.java:303)
at weblogic.transaction.internal.ServerTransactionManagerImpl.begin

(ServerTransactionManagerImpl.java:259)
at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:249)
at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:211)
at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate

(ClientDrivenBeanInfoImpl.java:1082)
at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1385)
at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:631)
at weblogic.j2ee.J2EEApplicationContainer.activateModule

(J2EEApplicationContainer.java:3315)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.j

Resolution

This normally happens if there are lot of pending transactions when the sever was stopped. It could be  pending XA transaction that did not commit.

Delete or Backup all transactions logs (server/*.tlog). Restart the server and it should come up fine.

Review the tlog to find out what kind of transactions where there.
Also you can increase the max transaction using the weblogic admin console.

[pb_builder]

Check Also

Error – Remote side declared peer gone on this JVM

Issue When trying to sent a JMS message to a remote Weblogic Application Server the …

Leave a Reply