BEA-001129:Received exception while creating connection for pool - Weblogic

This is a discussion on BEA-001129:Received exception while creating connection for pool - Weblogic ; I am getting the below mentioned error from WLS. My configuration is : WLS - WLS 8.1 sp3 Informix Driver : 2.21 JC5 Informix DBMS Version: 9.30 The error is not coming always. It comes only under high load. I ...

+ Reply to Thread
Results 1 to 7 of 7

BEA-001129:Received exception while creating connection for pool

  1. Default BEA-001129:Received exception while creating connection for pool

    I am getting the below mentioned error from WLS. My configuration is :
    WLS - WLS 8.1 sp3
    Informix Driver : 2.21 JC5
    Informix DBMS Version: 9.30

    The error is not coming always. It comes only under high load. I could see =
    one more post on the same with the same behaviour. But there was no solutio=
    n for the same.

    Error:
    <Sep 9, 2005 3:33:42 PM GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received =
    exception while creating connection for pool "gcdbr_connpool": Message text=
    will be provided in later releases java.lang.NullPointerException>
    <Sep 9, 2005 3:33:45 PM GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received =
    exception while creating connection for pool "gcdbr_connpool": null>
    <Sep 9, 2005 3:33:47 PM GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received =
    exception while creating connection for pool "gcdbr_connpool": Message text=
    will be provided in later releases java.lang.NullPointerException>

  2. Default Re: BEA-001129:Received exception while creating connection for pool

    Some more details :-

    Also I read in some post that from JDBC logs, ConnectionEnv was made to nul=
    l(though that was for Oracle I think). Will get JDBC logs and post the same

    The stacktrace in WLS logs is as below:
    ####<Sep 9, 2005 3:33:45 PM GMT+08:00> <Info> <JDBC> <classic2.apis.dhl.com=
    > <Managed05Aug1> <ExecuteThread: '17' for queue: 'default'> <<anonymous>> =

    <> <BEA-001156> <Stack trace associated with message 001129 follows:

    java.lang.NullPointerException
    at com.informix.jdbc.IfxDriver.getPropertiesFromUrl(IfxDriver.java:866)
    at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:233)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Co=
    nnectionEnvFactory.java:189)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Co=
    nnectionEnvFactory.java:124)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(Resource=
    PoolImpl.java:1145)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(Resource=
    PoolImpl.java:1079)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resour=
    cePoolImpl.java:334)
    at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(Resour=
    cePoolImpl.java:266)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.=
    java:449)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.=
    java:359)
    at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(Connecti=
    onPoolManager.java:80)
    at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDat=
    aSource.java:288)
    at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSou=
    rce.java at com.dhl.gis.sds.loader.common.AppDAO.getConnection(AppDAO.java:=
    662)
    at com.dhl.gis.sds.loader.common.AppDAO.getCallableStatement(AppDAO.jav=
    a:1428)
    at com.dhl.gis.sds.statsldr.BlockStatsSDO.updateStatistics(BlockStatsSD=
    O.java:588)
    at com.dhl.gis.sds.statsldr.StatsLoaderMDB.onMessage(StatsLoaderMDB.jav=
    a:420)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.Kernel.execute(Kernel.java:343)
    at weblogic.kernel.Kernel.execute(Kernel.java:367)
    at weblogic.kernel.Kernel.execute(Kernel.java:355)
    at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:2474)
    at weblogic.jms.client.JMSSession.invoke(JMSSession.java:3006)
    at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.ja=
    va:643) =20
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(Dispatc=
    herImpl.java:132)
    at weblogic.jms.dispatcher.DispatcherImpl.dispatchOneWay(DispatcherImpl=
    ..java:341)
    at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticat=
    edSubjectat weblogic.security.service.SecurityManager.runAs(SecurityManager=
    ..java:147)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.ja=
    va:415) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteR=
    equest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

  3. Default Re: BEA-001129:Received exception while creating connection for pool

    Anirudh Chitnis wrote:


    > Some more details :-
    >
    > Also I read in some post that from JDBC logs, ConnectionEnv was made to null(though that was for Oracle I think). Will get JDBC logs and post the same
    >
    > The stacktrace in WLS logs is as below:
    > ####<Sep 9, 2005 3:33:45 PM GMT+08:00> <Info> <JDBC> <classic2.apis.dhl.com> <Managed05Aug1> <ExecuteThread: '17' for queue: 'default'> <<anonymous>> <> <BEA-001156> <Stack trace associated with message 001129 follows:
    >
    > java.lang.NullPointerException
    > at com.informix.jdbc.IfxDriver.getPropertiesFromUrl(IfxDriver.java:866)
    > at com.informix.jdbc.IfxDriver.connect(IfxDriver.java:233)



    Hi. This is a weak programming bug in the Informix driver to throw an NPE while
    processing a URL, but it is almost certain that you are giving the driver
    an incorrect URL, and if you fix that your problem will go away. If you canget
    a simple standalone 30-line java program to make a connection to Informix using
    that driver (usually the driver vendor provides examples), show it to us, and
    the pool definition.
    Joe


    > at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:189)
    > at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:124)
    > at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1145)
    > at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1079)
    > at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:334)
    > at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:266)
    > at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:449)
    > at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:359)
    > at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:80)
    > at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:288)
    > at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java at com.dhl.gis.sds.loader.common.AppDAO.getConnection(AppDAO.java:662)
    > at com.dhl.gis.sds.loader.common.AppDAO.getCallableStatement(AppDAO.java:1428)
    > at com.dhl.gis.sds.statsldr.BlockStatsSDO.updateStatistics(BlockStatsSDO.java:588)
    > at com.dhl.gis.sds.statsldr.StatsLoaderMDB.onMessage(StatsLoaderMDB.java:420)
    > at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    > at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    > at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    > at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    > at weblogic.kernel.Kernel.execute(Kernel.java:343)
    > at weblogic.kernel.Kernel.execute(Kernel.java:367)
    > at weblogic.kernel.Kernel.execute(Kernel.java:355)
    > at weblogic.jms.client.JMSSession.pushMessage(JMSSession.java:2474)
    > at weblogic.jms.client.JMSSession.invoke(JMSSession.java:3006)
    > at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:643)
    > at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncInternal(DispatcherImpl.java:132)
    > at weblogic.jms.dispatcher.DispatcherImpl.dispatchOneWay(DispatcherImpl.java:341)
    > at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
    > at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    > at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    > at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjectat weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    > at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415) at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


  4. Default Re: BEA-001129:Received exception while creating connection for pool

    Thanks for the reply Joe. But if its a buggy program or the URL in Connecti=
    on Pool is buggy, then the error should be thrown always ! The error is thr=
    own only when server is put under high load.

    As far as buggy URL is concerned, I have been using the same URL since last=
    4 years and no issues with that.

    The conn pool configuration is as below.=20

    <JDBCConnectionPool CapacityIncrement=3D"8"
    DriverName=3D"com.informix.jdbc.IfxDriver" InitialCapacity=3D"25"
    MaxCapacity=3D"25" Name=3D"gcdbr_connpool"
    PasswordEncrypted=3D"{3DES}JYd9mqIFqf8=3D"
    Properties=3D"user=3Dgcdbadm2" ShrinkingEnabled=3D"false"
    StatementCacheSize=3D"0" Targets=3D"Managed05Aug1" URL=3D"jdbc:informix-sql=
    i://myserver:7103/myDB:INFORMIXSERVER=3Dgcdb_server;DBDATE=3DY4MD-"/>

  5. Default Re: BEA-001129:Received exception while creating connection for pool

    Anirudh Chitnis wrote:


    > Thanks for the reply Joe. But if its a buggy program or the URL in Connection Pool is buggy, then the error should be thrown always ! The error is thrown only when server is put under high load.



    Nope, life isn't that simple. See below.


    > As far as buggy URL is concerned, I have been using the same URL since last 4 years and no issues with that.



    Ok, then the problem is maybe one of thread-safety in the driver in this area.
    What's odd is that the pool below is defined (well) to create all it's 25 connections
    at startup, yet the stacktrace you show is for a pool trying to make a DBMS
    connection at runtime. The only way that could happen is if the pool is
    defined to test a connection at reserve, and if the original connection had
    failed. The config you show below does not have test-on-reserve. Thus, I suspect
    that you are getting the exception with a different configuration. I suggest that
    you change that other configuration to be like this one (init=max), and if you
    have test-on-reserve in that other one, maybe we can do some other debug...
    Joe


    >
    > The conn pool configuration is as below.
    >
    > <JDBCConnectionPool CapacityIncrement="8"
    > DriverName="com.informix.jdbc.IfxDriver" InitialCapacity="25"
    > MaxCapacity="25" Name="gcdbr_connpool"
    > PasswordEncrypted="{3DES}JYd9mqIFqf8="
    > Properties="user=gcdbadm2" ShrinkingEnabled="false"
    > StatementCacheSize="0" Targets="Managed05Aug1" URL="jdbc:informix-sqli://myserver:7103/myDB:INFORMIXSERVER=gcdb_server;DBDATE=Y4MD-"/>


  6. Default Re: BEA-001129:Received exception while creating connection for pool

    Yeah I think I had changed the configuration to avoid the error as in the e=
    arlier configuration (init !=3D max). But I have not received the error sin=
    ce then. May be the error comes only when the server is trying to get a new=
    connection as u have mentiond.

    Thanks.

  7. Default Re: BEA-001129:Received exception while creating connection for pool

    Hi,

    please correct the database name

    regards,
    Prasanna Yalam

+ Reply to Thread