Wednesday, December 2, 2009

The infamous BEA-000627

http://download.oracle.com/docs/cd/E13222_01/wls/docs100/messages/Common.html


Info: Reached maximum capacity of pool "pool", making "newVal" new resource instances instead of "oldVal".

Description
Hit configured maximum capacity of pool while making additional resources for the pool. Therefore, the number of resources being made has been increased.

Cause
Informational message.

Action
No action required.



I would expect to get a

####2 déc. 2009 04 h 10 CET Error WLI-Worklist peppe.acme.dns atlasappli2 [ACTIVE] ExecuteThread: '247' for queue: 'weblogic.kernel.Default
(self-tuning)' X5229701 1259723458590 BEA-493028 Internal error: unexpected ejb exception: java.sql.SQLException: Internal error: Cannot obtain
XAConnection weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool cgDataSource to allocate to applications, please in
crease the size of the pool and retry..
java.sql.SQLException: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool cgDataSource to allocate to applications, please increase the size of the pool and retry..
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1325)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:441)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:397)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.bea.wli.util.JDBCHelper.getConnection(JDBCHelper.java:77)



Still investigating on this weird message

2 comments:

Murali Sripadam said...

Any luck on this error message. Much awaiting for the fix.

Pierluigi Vernetto said...

no my friend I am sorry... I haven't had this error again, so I never bothered to investigate...

The KB says:
Cause
This normally happens when the connection pool runs out of connections.

Solution
In case of suspicious of connection leaking, set "Inactive Connection Timeout". Set the number of seconds of inactivity after which reserved connections will forcibly be released back into the pool.

If all connections are used up by high load, increase the value of the "Maximum Capacity" of the connection pool.