IPlanet- WebLogic Proxy Connection Pools

In the NSAPI weblogic plugin doco it says that the wlproxy plugin pools connections. How do you control the size of the connection pool. I don't see a min/max paramater. All I see is KeepAlive, ConnectTimeoutSecs and a few other related but nothing related to connection pool size. Any help would be appreciated.
Jack

Hi.
You might try posting this in the plug-in newsgroup.
Regards,
Michael
Jack wrote:
In the NSAPI weblogic plugin doco it says that the wlproxy plugin pools connections. How do you control the size of the connection pool. I don't see a min/max paramater. All I see is KeepAlive, ConnectTimeoutSecs and a few other related but nothing related to connection pool size. Any help would be appreciated.
Jack--
Michael Young
Developer Relations Engineer
BEA Support

Similar Messages

  • Weblogic DB connection pool load balancing problem

    hi all,
    here is a strange issue. We have a clustered weblogic environment with2 servers. And the application is deployed to cluster. But strangely when we check the active connections for the connection pool that is being used by the application, we see that 2nd server has more connections when compared to 1st server, lets say 1st server has 4 active connections, 2nd server has 50 connections, What might be the problem.
    <?xml version='1.0' encoding='UTF-8'?>
    <jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/jdbc-data-source" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/jdbc-data-source http://www.bea.com/ns/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
    <name>##########</name>
    <jdbc-driver-params>
    <url>jdbc:oracle:thin:@hostname:portnumber:Schema</url>
    <driver-name>oracle.jdbc.OracleDriver</driver-name>
    <properties>
    <property>
    <name>user</name>
    <value>#####</value>
    </property>
    <property>
    <name>portNumber</name>
    <value>#####</value>
    </property>
    <property>
    <name>SID</name>
    <value>######</value>
    </property>
    <property>
    <name>serverName</name>
    <value>hostname</value>
    </property>
    </properties>
    <password-encrypted>##########</password-encrypted>
    <use-xa-data-source-interface>false</use-xa-data-source-interface>
    </jdbc-driver-params>
    <jdbc-connection-pool-params>
    <initial-capacity>0</initial-capacity>
    <max-capacity>75</max-capacity>
    <capacity-increment>5</capacity-increment>
    <shrink-frequency-seconds>900</shrink-frequency-seconds>
    <highest-num-waiters>2147483647</highest-num-waiters>
    <connection-creation-retry-frequency-seconds>0</connection-creation-retry-frequency-seconds>
    <connection-reserve-timeout-seconds>10</connection-reserve-timeout-seconds>
    <test-frequency-seconds>60</test-frequency-seconds>
    <test-connections-on-reserve>true</test-connections-on-reserve>
    <profile-harvest-frequency-seconds>300</profile-harvest-frequency-seconds>
    <ignore-in-use-connections-enabled>true</ignore-in-use-connections-enabled>
    <inactive-connection-timeout-seconds>0</inactive-connection-timeout-seconds>
    <test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
    <login-delay-seconds>0</login-delay-seconds>
    <statement-cache-size>10</statement-cache-size>
    <statement-cache-type>LRU</statement-cache-type>
    <remove-infected-connections>true</remove-infected-connections>
    <seconds-to-trust-an-idle-pool-connection>10</seconds-to-trust-an-idle-pool-connection>
    <statement-timeout>-1</statement-timeout>
    <profile-type>0</profile-type>
    <pinned-to-thread>false</pinned-to-thread>
    </jdbc-connection-pool-params>
    <jdbc-data-source-params>
    <jndi-name>##########</jndi-name>
    </jdbc-data-source-params>
    </jdbc-data-source>

    are you using any front end web server or hardware load balancer ? verify your load balancing if it's happening or not properly between your clustered managed servers.
    Regards
    Mukesh Negi
    http://weblogicserveradministration.blogspot.com/

  • Weblogic Server 9.2 Crashes when using the JMS Wrapped Connection Pooling.

    ===== BEGIN DUMP =============================================================
    JRockit dump produced after 0 days, 01:05:05 on Thu Sep 16 18:27:36 2010
    Additional information is available in:
    E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.dump
    E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.mdmp
    If you see this dump, please open a support case with BEA and
    supply as much information as you can on your system setup and
    the program you were running. You can also search for solutions
    to your problem at http://forums.bea.com in
    the forum jrockit.developer.interest.general.
    Error Message: Illegal memory access. [54]
    Exception Rec: EXCEPTION_ACCESS_VIOLATION (c0000005) at 0x0095065F - memory at 0x00740060 could not be read.
    Minidump : Wrote mdmp. Size is 567MB
    SafeDllMode : -1
    Version : BEA JRockit(R) R27.2.0-131-78843-1.5.0_10-20070320-1457-windows-ia32
    GC Mode : Garbage collection optimized for throughput
    GC Strategy : Generational Parallel Mark & Sweep
    : Current OC phase is: not running. YC is not running.
    : GC strategy for GC 36 was genparpar
    : GC strategy for GC 37 was genparpar
    : GC strategy for GC 38 was genparpar
    : GC strategy for GC 39 was genparpar
    : GC strategy for GC 40 was genparpar
    : mmHeap->data = 0x00C00000, mmHeap->top = 0x10C00000
    : The nurserylist starts at 0x01BE75E8 and ends at 0x0CB52440
    : mmStartCompaction = 0x00C00000, mmEndCompaction = 0x01C00000
    : References are 32-bit.
    CPU : Intel Pentium III/Pentium III Xeon SSE SSE2 SSE3 SSSE3 EM64T
    Number CPUs : 2
    Tot Phys Mem : 3451408384 (3291 MB)
    OS version : Microsoft Windows XP version 5.1 Service Pack 3 (Build 2600) (32-bit)
    Thread System: Windows Threads
    State : JVM is running
    Command Line : -Djava.library.path=E:\bea\jrockit90_150_10\bin;E:\bea\jrockit90_150_10\jre\bin;E:\bea\weblogic92\server\native\win\32;E:\bea\weblogic92\server\bin;E:\bea\weblogic92\server\native\win\32\oci920_8 -Dweblogic.management.discover=false -Dplatform.home=E:\bea\weblogic92 -Dwls.home=E:\bea\weblogic92\server -Dwli.home=E:\bea\weblogic92\integration -Dweblogic.Name=myserver -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic -Dweblogic.ext.dirs=E:\bea\patch_weblogic901\profiles\default\sys_manifest_classpath\weblogic_patch.jar Djava.security.auth.login.config=E://workspace/Bhopal/LoginModulesConfig/ewp_loginmodules.config -Djava.naming.factory.initial.ewp.remote=weblogic.jndi.WLInitialContextFactory -Dcom.ewp.proxy.is_remote=false -Djava.naming.provider.url.ewp.remote=t3://localhost:7001 -Dweblogic.webservice.verbose=true -Dweblogic.log.Log4jLoggingEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true Xdebug -Xnoagent -Dcom.sun.management.jmxremote -Xms256m -Xmx1024m -Dsun.java.launcher=SUN_STANDARD weblogic.Server
    java.home : E:\bea\jrockit90_150_10\jre
    JAVA_HOME : <not set>
    JAVAOPTIONS: <not set>
    PATH : E:\bea\jrockit90_150_10\jre\bin;E:\oracle\product\10.2.0\client_1\bin;C:\Program Files\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\TortoiseSVN\bin
    C Heap : Good; no memory allocations have failed
    StackOverFlow: 0 StackOverFlowErrors have occured
    OutOfMemory : 0 OutOfMemoryErrors have occured
    Registers (from ThreadContext: 0x4B29E378 / OS context: 0x4B29E764):
    eax = 00740060 ecx = 00740060 edx = 45a45ba0 ebx = 08c953b8
    esp = 4b29ea30 ebp = 00000000 esi = 4b29ea60 edi = 4b29efb4
    es = 00000023 cs = 0000001b ss = 00000023 ds = 00000023
    fs = 0000003b gs = 00000000
    eip = 0095065f eflags = 00010206
    Stack:
    (* marks the word pointed to by the stack pointer)
    4b29ea30: 00981099* 08c953b8 008ab310 4b29eb34 09e5c308 009810ea
    4b29ea48: 4b29ead8 0098ecd2 4b29ea60 4b29ea90 48bd8960 48bd8960
    4b29ea60: 00000001 45aa0278 45a45ba0 00000007 00000000 08c953b8
    4b29ea78: 08512180 4b29ef60 00000000 09d56368 09d563b0 4b29efb4
    Code:
    (* marks the word pointed to by the instruction pointer)
    0095062c: 5e5f0cc4 c35bc033 01b85e5f 5b000000 ccccccc3 0424448b
    00950644: a5f06ca3 ccccc300 cccccccc 04244c8b 01a8018b e0830774
    0095065c: 8bc88bfe* 40788301 44408b03 af0f0a75 c0830841 f8e08317
    00950674: ccccccc3 cccccccc cccccccc 0424448b 00f4888b 158b0000
    Loaded modules:
    (* denotes the module causing the exception)
    00400000-0040ffff E:\bea\jrockit90_150_10\bin\javaw.exe
    7c900000-7c9b1fff C:\WINDOWS\system32\ntdll.dll
    7c800000-7c8f5fff C:\WINDOWS\system32\kernel32.dll
    7e410000-7e4a0fff C:\WINDOWS\system32\USER32.dll
    77f10000-77f58fff C:\WINDOWS\system32\GDI32.dll
    77dd0000-77e6afff C:\WINDOWS\system32\ADVAPI32.dll
    77e70000-77f02fff C:\WINDOWS\system32\RPCRT4.dll
    77fe0000-77ff0fff C:\WINDOWS\system32\Secur32.dll
    77c10000-77c67fff C:\WINDOWS\system32\MSVCRT.dll
    76390000-763acfff C:\WINDOWS\system32\IMM32.DLL
    00820000-00a9cfff *E:\bea\jrockit90_150_10\jre\bin\jrockit\jvm.dll
    76b40000-76b6cfff C:\WINDOWS\system32\WINMM.dll
    71ab0000-71ac6fff C:\WINDOWS\system32\WS2_32.dll
    71aa0000-71aa7fff C:\WINDOWS\system32\WS2HELP.dll
    7c340000-7c395fff E:\bea\jrockit90_150_10\bin\MSVCR71.dll
    5dac0000-5dac7fff C:\WINDOWS\system32\rdpsnd.dll
    76360000-7636ffff C:\WINDOWS\system32\WINSTA.dll
    5b860000-5b8b4fff C:\WINDOWS\system32\NETAPI32.dll
    76bf0000-76bfafff C:\WINDOWS\system32\PSAPI.DLL
    6d700000-6d70bfff E:\bea\jrockit90_150_10\jre\bin\verify.dll
    6d370000-6d38cfff E:\bea\jrockit90_150_10\jre\bin\java.dll
    6d2f0000-6d2f7fff E:\bea\jrockit90_150_10\jre\bin\hpi.dll
    6d720000-6d72efff E:\bea\jrockit90_150_10\jre\bin\zip.dll
    6d520000-6d527fff E:\bea\jrockit90_150_10\jre\bin\management.dll
    6d530000-6d542fff E:\bea\jrockit90_150_10\jre\bin\net.dll
    71a50000-71a8efff C:\WINDOWS\system32\mswsock.dll
    662b0000-66307fff C:\WINDOWS\system32\hnetcfg.dll
    71a90000-71a97fff C:\WINDOWS\System32\wshtcpip.dll
    41c00000-41c26fff C:\WINDOWS\system32\DNSAPI.dll
    41c30000-41c37fff C:\WINDOWS\System32\winrnr.dll
    41c40000-41c6bfff C:\WINDOWS\system32\WLDAP32.dll
    41c80000-41c85fff C:\WINDOWS\system32\rasadhlp.dll
    68000000-68035fff C:\WINDOWS\system32\rsaenh.dll
    769c0000-76a73fff C:\WINDOWS\system32\USERENV.dll
    438b0000-438b8fff E:\bea\jrockit90_150_10\jre\bin\nio.dll
    41ba0000-41ba9fff E:\bea\jrockit90_150_10\jre\bin\jmapi.dll
    41bb0000-41bbdfff E:\bea\weblogic92\server\native\win\32\wlfileio2.dll
    43ce0000-43cf8fff C:\WINDOWS\system32\iphlpapi.dll
    43d10000-43d27fff C:\WINDOWS\system32\MPRAPI.dll
    77cc0000-77cf1fff C:\WINDOWS\system32\ACTIVEDS.dll
    43d30000-43d54fff C:\WINDOWS\system32\adsldpc.dll
    43d60000-43d70fff C:\WINDOWS\system32\ATL.DLL
    43d80000-43ebcfff C:\WINDOWS\system32\ole32.dll
    43ec0000-43f4afff C:\WINDOWS\system32\OLEAUT32.dll
    43f50000-43f5dfff C:\WINDOWS\system32\rtutils.dll
    71bf0000-71c02fff C:\WINDOWS\system32\SAMLIB.dll
    43f60000-44052fff C:\WINDOWS\system32\SETUPAPI.dll
    44060000-44064fff E:\bea\weblogic92\server\native\win\32\wlntio.dll
    44540000-44545fff E:\bea\jrockit90_150_10\jre\bin\rmi.dll
    4d010000-4d122fff E:\bea\jrockit90_150_10\jre\bin\dbghelp.dll
    "[STANDBY] ExecuteThread: '21' f" id=87 idx=0xf0 tid=4208 lastJavaFrame=0x4B29EB4C
    Stack 0: start=0x4B260000, end=0x4B2A0000, guards=0x4B263000 (ok), forbidden=0x4B261000
    Thread Stack Trace:
    at _mmGetPossibleMovedObjectSize+15()@0x0095065F
    at _refIterInit+393()@0x00981099
    at _refIterInit+474()@0x009810EA
    at _trProcessLocksForThread+66()@0x0098ECD2
    at _javalockCouldBeLock+1047()@0x008AB417
    at _javalockConvertThinToFat+42()@0x008AC13A
    at RJNIjrockit_vm_Locks_convertThinLockedToFatLocked@8+15()@0x00986B1F
    -- Java stack --
    at jrockit/vm/Locks.convertThinLockedToFatLocked(Ljava/lang/Object;)V(Native Method)
    at jrockit/vm/Locks.createMonitorAndConvert(Ljava/lang/Object;Z)Ljrockit/vm/ObjectMonitor;(Unknown Source)
    at java/lang/Object.wait(J)V(Native Method)
    at java/lang/Object.wait(Object.java:474)
    at weblogic/common/CompletionRequest.getResult(CompletionRequest.java:109)
    ^-- Holding lock: weblogic/common/CompletionRequest@0x09E5C2A8[thin lock]
    at weblogic/store/gxa/internal/GXATransactionImpl.commitStoreIO(GXATransactionImpl.java:99)
    at weblogic/store/gxa/internal/GXATransactionImpl.doOperationCallbacks(GXATransactionImpl.java:215)
    at weblogic/store/gxa/internal/GXAResourceImpl.commit(GXAResourceImpl.java:1448)
    at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:1333)
    at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:577)
    at weblogic/transaction/internal/ServerSCInfo.startCommit(ServerSCInfo.java:514)
    at weblogic/transaction/internal/ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1993)
    at weblogic/transaction/internal/ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2658)
    at weblogic/transaction/internal/ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2580)
    at weblogic/transaction/internal/ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:278)
    at weblogic/transaction/internal/ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
    at weblogic/deployment/jms/WrappedTransactionalSession.delistFromTransaction(WrappedTransactionalSession.java:258)
    ^-- Holding lock: weblogic/deployment/jms/PooledSession_weblogic_jms_client_JMSXASession@0x09D56368[thin lock]
    at weblogic/deployment/jms/WrappedMessageProducer.send(WrappedMessageProducer.java:149)
    at com/obopay/jms/helper/BaseQueueHelper.sendMessage(BaseQueueHelper.java:107)
    The above is the jrockit crash dump file..
    I am using the JMS Wrapper Connection Poooling provided by Weblogic. When i use Jmeter and do the load testing for around 10 users, the server gets crashed.
    I doubt something is going wrong with the Weblogic JMS Connection Pooling, please help me..

    The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
    Regards,
    tom
    Edited by: TomB on Sep 17, 2010 2:33 PM

  • Database connection pooling with weblogic 8.1.

    Hai All,
    I am new to weblogic database connection pooling.
    I am using Weblogic8.1 and want to use connection pooling to get a jdbc connection. my database server is Oracle 8.1.7.
    Things which i have done using the weblogic admin console.
    I have created a Jdbc connection pool named myconnectionpool.
    I have created a datasource named mydatasource.
    and named the JNDI as myjndi.
    Is the above process correct to create the connection pool in the weblogic8.1.
    I am not aware of the java code to get the database connection object from the connection pool which i have created.
    can any one please let me know the java code to get the connection from the pool.
    Any help is appreciated
    Thanks in advance
    pooja.

    Hai
    I have tried using the code u have mentioned but it returned me
    an error which is below.
    C:\javaexamples\Javaprograms\JDBC>java jdbcexampleconnectionpool
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    I have added the following lines code, which i read in some weblogic documentation. The code i added is below and it worked fine.
    ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
    ht.put(Context.PROVIDER_URL,"t3://localhost:7001");
    Context ctx = new InitialContext(ht);I am not sure what the above code does.
    Can anyone let me know what does the above code do.
    Thanks a lot and i appreciate ur help,
    Pooja.

  • Error While reading CLOB from Oracle using WebLogic Connection Pool, Works fine with out using pool

    PROBLEM DESCRIPTION :
         When I try to read a clob from Oracle, I receive "ORA-03120: two-task
    conversion routine: integer overflow" Error.
         This error occurs only for CLOB Type and only if I try to connect to
    Oracle using WebLogic JDriver/Oracle POOL.
         IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
    connection to ORacle with out any problem.
         Below Please find the JAVA CODE for Both Working and NON Working .
    Created a Connection Pool as:
    Name: MyJDBCConnectionPool
    URL : jdbc:weblogic:oracle
    DIRVER:weblogic.jdbc.oci.Driver
    NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
    Driver myDriver =
    (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection mconn =
    myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
    mconn.setAutoCommit (false);
    CallableStatement cs = mconn.prepareCall("{call
    P_XMLTEST2(?)}"); //This returns a CLOB
    cs.registerOutParameter(1,java.sql.Types.CLOB);
    cs.execute();
    Clob clob = null;
    clob = cs.getClob(1);
    String data =new String();
    data = clob.getSubString(1, (int)clob.length());
    System.out.println(data); //print the data
    data = null;
    clob=null;
    cs.close();
    WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
    Driver myDriver =
    (Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
    Connection mconn =
    myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
    mconn.setAutoCommit (false);
    CallableStatement cs = mconn.prepareCall("{call
    P_XMLTEST2(?)}"); //This returns a CLOB
    cs.registerOutParameter(1,java.sql.Types.CLOB);
    cs.execute();
    Clob clob = null;
    clob = cs.getClob(1);
    String data =new String();
    data = clob.getSubString(1, (int)clob.length());
    System.out.println(data); //print the data
    data = null;
    clob=null;
    cs.close();
    ERROR MESSAGE:
         ORA-03120: two-task conversion routine: integer overflow
    I appreciate your help on this problem.

    PROBLEM DESCRIPTION :
         When I try to read a clob from Oracle, I receive "ORA-03120: two-task
    conversion routine: integer overflow" Error.
         This error occurs only for CLOB Type and only if I try to connect to
    Oracle using WebLogic JDriver/Oracle POOL.
         IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
    connection to ORacle with out any problem.
         Below Please find the JAVA CODE for Both Working and NON Working .
    Created a Connection Pool as:
    Name: MyJDBCConnectionPool
    URL : jdbc:weblogic:oracle
    DIRVER:weblogic.jdbc.oci.Driver
    NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
    Driver myDriver =
    (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection mconn =
    myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
    mconn.setAutoCommit (false);
    CallableStatement cs = mconn.prepareCall("{call
    P_XMLTEST2(?)}"); //This returns a CLOB
    cs.registerOutParameter(1,java.sql.Types.CLOB);
    cs.execute();
    Clob clob = null;
    clob = cs.getClob(1);
    String data =new String();
    data = clob.getSubString(1, (int)clob.length());
    System.out.println(data); //print the data
    data = null;
    clob=null;
    cs.close();
    WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
    Driver myDriver =
    (Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
    Connection mconn =
    myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
    mconn.setAutoCommit (false);
    CallableStatement cs = mconn.prepareCall("{call
    P_XMLTEST2(?)}"); //This returns a CLOB
    cs.registerOutParameter(1,java.sql.Types.CLOB);
    cs.execute();
    Clob clob = null;
    clob = cs.getClob(1);
    String data =new String();
    data = clob.getSubString(1, (int)clob.length());
    System.out.println(data); //print the data
    data = null;
    clob=null;
    cs.close();
    ERROR MESSAGE:
         ORA-03120: two-task conversion routine: integer overflow
    I appreciate your help on this problem.

  • VARRAY mapping issues using WLS spk2 connection pools

    We have an ongoing issue with VARRAY's and WLS Connection pools. The connection
    pool of WebLogic does not support certain data structures of Oracle such as VARRAY.
    To create array/struct object in java application, we have to register these
    objects through array/struct descriptor methods. These methods require Oracle.sql.Connection
    as a parameter. There is no way to get Oracle.sql.Connection from Weblogic Server
    Connection Pool because the Oracle.sql.Connection is not serializable.
    So, what is the recommended solution for a situation in which the application
    tends to need to use VARRAYs and can we instead pass tables?
    Any recommendations?

    More information on this issue.
    I'm using the method DriverManager.getConnection(URL) to get a connection to
    the database, passing in the name of the connection pool. This method is
    throwing the following SecurityException:
    java.lang.SecurityException: User "john" does not have Permission
    "reserve"
    based on ACL "weblogic.jdbc.connectionPool.ICOM_DEV2_A".
    When running under the LDAP realm:
    -calls to getConnection() from within a jsp fail
    -calls to getConnection() from within a Session Bean or Entity Bean work
    -calls to getConnection() from a non-EJB class fail if it is called directly
    from the jsp
    -calls to getConnection() from a non-EJB class work if it is called from a
    Session Bean
    When running under the RDBMS realm, all calls to getConnection() work,
    whether they are a jsp, non-EJB class or a Session Bean.
    Is there some security context that is only present inside the EJB
    container?

  • XA connection pools on MSSQL 6.5

    Hi,
    is it possible to use Weblogic XA connection pools on MSSQL 6.5 database? If not, what could be alternative solution?

    lol predicted that answer ^^ LOL @ MTU (BTW DOsent WORK)
    listen bro i have the exact same problem , execept with 1 v8
    i run a counter-strike server and i got 10mbps down and 1mbps up and the game lags about every 3-4 min on the dot...not hardware neither tis tha router cuz we got exact same problem .. "Little Hiccups" Any other suggestions?
    Message Edited by KnewbZ on 11-06-2007 06:37 AM
    (Edited post for guideline compliance. Thanks!)
    Message Edited by JOHNDOE_06 on 11-06-2007 06:42 AM

  • Creating Connection Pools/ Connection Pool does not exist error

    Hi everyone -
    I have a question about when/how weblogic creates connections pools.
    Here is the scenario. Sometimes when our weblogic server starts, our
    oracle database is not available. Therefor, weblogic can't create the
    connection pool. However, after oracle comes weblogic up, weblogic
    could create the connection pool, but it doesn't appear to be smart
    enough to do this. Is there a way to ask weblogic to attempt to
    recreate a connection pool?
    We've noticed this behavior on weblogic 6.0 sp2.
    Thanks,
    Scott

    If you define the pool with an initial size of zero, you should be OK. The
    server is currently a little severe with a pool when the server cannot
    create the pool with it's initial capacity, the pool isn't created. The server
    could create it later, if told to via the console or via the admin command line,
    or via the dynamic pool API, but init=0 is easiest.
    Joe
    Scott Gilpin wrote:
    Hi everyone -
    I have a question about when/how weblogic creates connections pools.
    Here is the scenario. Sometimes when our weblogic server starts, our
    oracle database is not available. Therefor, weblogic can't create the
    connection pool. However, after oracle comes weblogic up, weblogic
    could create the connection pool, but it doesn't appear to be smart
    enough to do this. Is there a way to ask weblogic to attempt to
    recreate a connection pool?
    We've noticed this behavior on weblogic 6.0 sp2.
    Thanks,
    Scott

  • JBO Parameters + Connection Pooling Question

    I know that it is possible to pass in BC4J configuration parameters (such as jbo.dofailover) to the JVM via the -D parameter. It is unclear to me, though, how those parameters are actually used because I can also configure each application module in my app differently. If parameters are passed using the -D parameter, does that override any individual application module configuration settings at run-time?
    It looks like every application module instance, at runtime, creates a JDBC connection into the database. How can I put a cap on that or limit the entire application to X number of connections? Currently, I'm using a JDBC URL and I'm seeing the following behavior:
    * 10 users all using 12 application modules = 120 JDBC connections into Oracle. Ouch.
    If I were to switch over to a JDBC DataSource using the WebLogic JDBC Connection Pool driver, will this effectively take over JDBC connection pooling for my application? In other words, if I set that datasource to a maximum of 50 simultaneous connections, will this truly limit the app to 50 connections or will the maximum possible be 50 connections * 12 application modules = 600?!?
    Thanks!

    I know that it is possible to pass in BC4J configuration parameters (such as jbo.dofailover) to the JVM via the -D
    parameter. It is unclear to me, though, how those parameters are actually used because I can also configure each
    application module in my app differently. If parameters are passed using the -D parameter, does that override any
    individual application module configuration settings at run-time? .
    The configuration settings take precedence over VM parameters. Tthe following thread also
    contains some discussion regarding BC4J parameter precedence:
    Re: using OLB, PLL etc., on 10gAS on AIX and 10G AS on windows =>Very Urgen
    It looks like every application module instance, at runtime, creates a JDBC connection into the database. How can
    I put a cap on that or limit the entire application to X number of connections? Currently, I'm using a JDBC URL and
    I'm seeing the following behavior:.
    * 10 users all using 12 application modules = 120 JDBC connections into Oracle. Ouch..
    If connecting with a JDBC URL then BC4J's connection pool will be used to acquire application modules. The max size
    of a connection pool may be defined with the parameter jbo.maxpoolsize. However, if the application has been
    architected to simultaneously use 12 root application modules per application request/session then BC4J will require
    12 JDBC connections per user. Specifying a maximum pool size will simply cause the other users to wait for
    connections resulting in high latency and/or wait timeouts. So, you should probably plan on configuring the connection
    pool size to meet your average application demands or consider using fewer AMs.
    Please also note that the BC4J connection pool parameters apply to a single pool instance. So, if each application
    user is connecting as a different DB user then the jbo.maxpoolsize will apply to each DB user's connection pool only.
    If I were to switch over to a JDBC DataSource using the WebLogic JDBC Connection Pool driver, will this effectively
    take over JDBC connection pooling for my application?.
    Yes.
    In other words, if I set that datasource to a maximum of 50 simultaneous connections, will this truly limit the app to
    50 connections or will the maximum possible be 50 connections * 12 application modules = 600?!?.
    Depends upon WebLogic's implementation. However, if you have 50 simultaneous application requests and if each
    request requires 12 simultaneous ApplicationModule(s) then you will require 600 ApplicationModule(s) and these 600
    ApplicationModule(s) will require 600 JDBC connections.
    Hope this helps.
    JR

  • WebLogic proxy plugin: getPooledConn: No more connections in the pool

    Hi,
    We have weblogic proxy plugin installed in Sun One web server. but frequently we are getting following errors in proxy log:
    <1670612410085901> attempt #0 out of a max of 5
    <1670612410085901> Trying a pooled connection for '<IP>/<port>/<port>'
    <1670612410085901> getPooledConn: No more connections in the pool for Host [<IP>] Port[<port>] SecurePort[<port>]
    Can anybody please tell how this proxy plugin manages connection pools? I don't find any minimum / maximum number of conection to mention anywhere or how exactly it works?

    Try increasing the "AcceptBackLog" settings on the weblogic server and then verify for any changed behavior.
    Raise the Accept Backlog value from the default by 25 percent. Continue increasing the value by 25 percent until the messages cease to appear.
    Link :[http://e-docs.bea.com/wls/docs81/perform/WLSTuning.html#1136287]

  • Weblogic proxy plugin closes keep-alive connections to clients randomly

    In short we have following arhitecture:
    clients ---> wl proxy plugin 1 ----> weblogic 1
    clients ---> wl proxy plugin 2 ----> weblogic 2
    Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
    Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
    Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
    As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
    We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
    Trace (replaced sensitive information):
    Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
    Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
    Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
    Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
    Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
    Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
    Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
    !!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
    WL proxy plugin conf params are:
    WebLogicCluster $IP$:$PORT$
    DynamicServerList OFF
    KeepAliveTimeout 90
    MaxKeepAliveRequests 0
    KeepAliveSecs 55
    Apache worker configuration is:
    <IfModule mpm_worker_module>
    PidFile var/run/httpd-worker.pid
    LockFile var/run/accept-worker.lock
    StartServers 2
    MinSpareThreads 25
    MaxSpareThreads 75
    ThreadLimit 200
    ThreadsPerChild 200
    MaxClients 2000
    MaxRequestsPerChild 0
    AcceptMutex pthread
    </IfModule>
    Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
    Any help?

    If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
    MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
    Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
    See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
    You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
    On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

  • Issues with Weblogic connection pool creation

    Hi,
    I need to create a Connection pool in weblogic to access a mdb file(MS Access) .
    Iam not able to see any precoded drivers in weblogic for accessing MS Access.
    Let me know if anyone has details on this.
    Thanks.

    I tried this one and this seems to be a trial version.
    Are there any free apis available? In case there are any other way do let me know.
    Thanks.

  • Proxy functionality in the database connection pool

    Hi,
    I am scouring the internet and forums looking for a way to connect to my database from the .rpd connection pool using proxy authetication. NOT Act-As proxy that is a BIEE feature, but RDBMS proxy authentication with BIEE acting as the middle-tier connecting on behalf of many users and authenticating to the RDBMS AS THE INDIVIDUAL USER. I haven't had any luck, and am hoping someone here has set up this same kind of access.
    We have a requirement to use SSO with BIEE to integrate with our portal and discoverer apps. We also have a requirement to use EUS (Enterprise User Security). EUS allows you to login to the database using the userids/password from OID. Note that the database doesn't support the SSO token, but it uses the same userid/password stored in OID for authenticating to the database. You still must initiate a connection to the database, but the authentication goes to LDAP. Every connection to BIEE may be using a different userid - we will not have a shared login.
    So the issue I see is:
    - We configure SSO
    - In the BI Server the :USER session variable is set (but NOT :PASSWORD, since BI Server didn't authenticate you it doesn't have the password)
    - We create a connection pool - This is where we hit the issue - we need each connection to BI Server to connect down to the database as the SSO user. Since we aren't using a shared account we can't enter a userid/password in this connection. We also can't user :USER and :PASSWORD since SSO doesn't set the :PASSWORD session variable. What I would hope to find is a checkbox "Proxy Authentication" (around where "Shared Logon" checkbox is located) that would connect to the database as the proxy user and then switch to the SSO user.
    This is what happens with BI Publisher. On the JDBC connection screen there is a "Proxy Authentication" checkbox.
    So, has anyone already solved this problem? Thanks!

    Hello, is there anyone knows what this program does
    and how this program is executed? There is nodatabase
    mentioned.That's because it's expecting the URL (which contains
    the database type, hostname, and so on) to be passed
    in on the command line (argv[0]), as well as the
    username and password (argv[1] and argv[2]).
    Thank you very much for your help.
    Regards,
    Lucas

  • Connection Pooling problem in Weblogic Server 6.1

    Hi
    We are using weblogic server 6.1 sp3. The server creates three database connection
    pools (details available in the attached config.xml).
    The database has a regular downtime every day for a few hours. We are running
    the server as a windows service. As per the "RefreshMinutes" property, the server
    should be able to get new fresh connections once the database comes up. But in
    our case it is not doing so. Once the database comes up after its regular downtime:
    -- Sometimes the server does not respond as in we are not able to open the console
    page.
    -- Any client that tries connecting to the database thru the server gets blocked
    and does not respond.
    -- The log file(weblogic.log) does not get updated after some time.
    Can someone suggest why the server is showing such a behaviour??
    Could it be anything related to the DBMS setting or to the local machine's settings
    ? Following is the thread dump after the server stops responding:
    Full thread dump:
    "ListenThread" prio=5 tid=0x14ffb570 nid=0x148c runnable [0x1685f000..0x1685fdbc]
         at java.net.PlainSocketImpl.socketAccept(Native Method)
         at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)
         at java.net.ServerSocket.implAccept(ServerSocket.java:243)
         at java.net.ServerSocket.accept(ServerSocket.java:222)
         at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:260)
    "Thread-3" daemon prio=5 tid=0x14fb18b8 nid=0x12d4 waiting on monitor [0x167df000..0x167dfdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-2" daemon prio=5 tid=0x14f21c68 nid=0xf08 waiting on monitor [0x1679f000..0x1679fdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-1" daemon prio=5 tid=0x14fb97d8 nid=0xcac waiting on monitor [0x1675f000..0x1675fdbc]
         at java.lang.Thread.sleep(Native Method)
         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e75a10
    nid=0x13ec waiting on monitor [0x1671f000..0x1671fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e74e58
    nid=0x1434 waiting on monitor [0x166df000..0x166dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e742a0
    nid=0x1154 waiting on monitor [0x1669f000..0x1669fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72ed0
    nid=0xfe4 waiting on monitor [0x1665f000..0x1665fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72318
    nid=0x9a4 waiting on monitor [0x1661f000..0x1661fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e717d8 nid=0xf38
    waiting on monitor [0x165df000..0x165dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70c98 nid=0xf68
    waiting on monitor [0x1659f000..0x1659fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70158 nid=0x1008
    waiting on monitor [0x1655f000..0x1655fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6f610 nid=0x1204
    waiting on monitor [0x1651f000..0x1651fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ead0 nid=0xef4
    waiting on monitor [0x164df000..0x164dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6dfa8 nid=0x12bc
    waiting on monitor [0x1649f000..0x1649fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6d5e8 nid=0xf70
    waiting on monitor [0x1645f000..0x1645fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ccb0 nid=0xf84
    waiting on monitor [0x1641f000..0x1641fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e67510 nid=0x1418
    waiting on monitor [0x163df000..0x163dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e64f60 nid=0x1228
    waiting on monitor [0x1639f000..0x1639fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e5c3f0 nid=0xf60 waiting on monitor [0x1635f000..0x1635fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e5b908 nid=0xf78 waiting on monitor [0x1631f000..0x1631fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemon prio=5
    tid=0x14e3ebe0 nid=0xfb4 waiting on monitor [0x162df000..0x162dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e35958
    nid=0x9e8 waiting on monitor [0x1629f000..0x1629fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3ba30
    nid=0x5ac waiting on monitor [0x1625f000..0x1625fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3af20
    nid=0xdc4 waiting on monitor [0x1621f000..0x1621fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e3a410
    nid=0x11ec waiting on monitor [0x161df000..0x161dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14bfdff0
    nid=0x1078 waiting on monitor [0x1619f000..0x1619fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14bfd4e0
    nid=0x43c waiting on monitor [0x1615f000..0x1615fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e32410
    nid=0xb64 waiting on monitor [0x1611f000..0x1611fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14c4ee68
    nid=0xe30 waiting on monitor [0x160df000..0x160dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14c4ec10
    nid=0x1140 waiting on monitor [0x1609f000..0x1609fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemon prio=5 tid=0x14e33b18
    nid=0xfc0 waiting on monitor [0x1605f000..0x1605fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x14e33968
    nid=0x718 waiting on monitor [0x1601f000..0x1601fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemon prio=5 tid=0x14e3c0a0
    nid=0x119c waiting on monitor [0x15fdf000..0x15fdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfbce0 nid=0xb90 waiting on monitor
    [0x15f9f000..0x15f9fdbc]
         at java.lang.Object.wait(Native Method)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x14e39758
    nid=0x11ac waiting on monitor [0x15f5f000..0x15f5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5 tid=0x14e38898
    nid=0x1194 waiting on monitor [0x15f1f000..0x15f1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfc040 nid=0x10a8 waiting on monitor
    [0x15edf000..0x15edfdbc]
         at java.lang.Object.wait(Native Method)
         at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
         at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
         at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x14e30c40 nid=0x794 waiting on monitor
    [0x15e9f000..0x15e9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
         at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x14e2fe20 nid=0xee8
    runnable [0x15e5f000..0x15e5fdbc]
         at java.net.SocketInputStream.socketRead(Native Method)
         at java.net.SocketInputStream.read(SocketInputStream.java:90)
         at oracle.net.ns.Packet.receive(Unknown Source)
         at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.net.ns.NetInputStream.read(Unknown Source)
         at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
         at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
         at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
         at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
         at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
         at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
         at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
         at weblogic.jdbc.pool.Statement.executeQuery(Statement.java:850)
         at tavant.platform.jdbc.JDBCTransaction.executeReadQuery(Unknown Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x14e2f268 nid=0x12f0
    runnable [0x15e1f000..0x15e1fdbc]
         at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x14be7af0 nid=0x11c4
    runnable [0x15ddf000..0x15ddfdbc]
         at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
         at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
         at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x14be7748 nid=0x6dc
    waiting for monitor entry [0x15d9f000..0x15d9fdbc]
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:681)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:520)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
         at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
         at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
         at java.sql.DriverManager.getConnection(DriverManager.java:517)
         at java.sql.DriverManager.getConnection(DriverManager.java:199)
         at tavant.platform.jdbc.JDBCTransaction.getConnection(Unknown Source)
         at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
         at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
         at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '25' for queue: 'default'" daemon prio=5 tid=0x14be6b90 nid=0x10f4
    waiting for monitor entry [0x15d5f000..0x15d5fdbc]
         at java.sql.DriverManager.println(DriverManager.java:424)
         at java.sql.SQLException.<init>(SQLException.java:44)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
         at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
         at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:197)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:270)
         at weblogic.jdbc.common.internal.ConnectionEnv.refresh(ConnectionEnv.java:919)
         at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:885)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
         at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
         at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
         at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
         at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '24' for queue: 'default'" daemon prio=5 tid=0x14be5fd8 nid=0x10a4
    waiting on monitor [0x15d1f000..0x15d1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '23' for queue: 'default'" daemon prio=5 tid=0x14be5420 nid=0x11b0
    waiting on monitor [0x15cdf000..0x15cdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '22' for queue: 'default'" daemon prio=5 tid=0x14be4868 nid=0x11bc
    waiting for monitor entry [0x15c9f000..0x15c9fdbc]
         at java.sql.DriverManager.println(DriverManager.java:424)
         at java.sql.SQLException.<init>(SQLException.java:44)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
         at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
         at oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnection.java:758)
         at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:712)
         at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:977)
         at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:470)
         at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
         at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
         at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
         at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
         at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '21' for queue: 'default'" daemon prio=5 tid=0x14be3cb0 nid=0x10e0
    waiting on monitor [0x15c5f000..0x15c5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '20' for queue: 'default'" daemon prio=5 tid=0x14be30f8 nid=0x620
    waiting on monitor [0x15c1f000..0x15c1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '19' for queue: 'default'" daemon prio=5 tid=0x14be2540 nid=0x350
    waiting on monitor [0x15bdf000..0x15bdfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '18' for queue: 'default'" daemon prio=5 tid=0x14be1988 nid=0x104c
    waiting on monitor [0x15b9f000..0x15b9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x14c4db30 nid=0xff0
    waiting on monitor [0x15b5f000..0x15b5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x14c4cf78 nid=0x1148
    waiting on monitor [0x15b1f000..0x15b1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x14c4c3c0 nid=0x1118
    waiting on monitor [0x15adf000..0x15adfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x14c4b808 nid=0x684
    waiting on monitor [0x15a9f000..0x15a9fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x14c4ac50 nid=0xd7c
    waiting on monitor [0x15a5f000..0x15a5fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x14c4a098 nid=0xdb4
    waiting on monitor [0x15a1f000..0x15a1fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'default'" daemon prio=5 tid=0x14c49588 nid=0x114c
    waiting on monitor [0x159df000..0x159dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'default'" daemon prio=5 tid=0x14bdf540 nid=0x90c
    waiting on monitor [0x1599f000..0x1599fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'default'" daemon prio=5 tid=0x14bdea00 nid=0x11cc
    waiting on monitor [0x1595f000..0x1595fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'default'" daemon prio=5 tid=0x14bdded8 nid=0x12f8
    waiting on monitor [0x1591f000..0x1591fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'default'" daemon prio=5 tid=0x14ba0420 nid=0x1350
    waiting on monitor [0x158df000..0x158dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'default'" daemon prio=5 tid=0x14bfae20 nid=0x11d8
    waiting on monitor [0x1589f000..0x1589fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'default'" daemon prio=5 tid=0x14b9e6a8 nid=0x134c
    waiting on monitor [0x1585f000..0x1585fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'default'" daemon prio=5 tid=0x14b9e430 nid=0x10bc
    waiting on monitor [0x1581f000..0x1581fdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420)
         at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'default'" daemon prio=5 tid=0x14bdbc00 nid=0x1090
    waiting on monitor [0x157df000..0x157dfdbc]
         at java.lang.Object.wait(Native Method)
         at java.lang.Object.wait(Object.java:420

    Hi Joseph,
    Thanks for your useful suggestion.
    BTW, I am attaching the config.xml for your
    convenience.
    Please go through and let us know if anything
    to be tuned.
    Regards.
    Kunal
    Joseph Weinstein <[email protected]> wrote:
    >
    >
    Kunal Jain wrote:
    Hi
    We are using weblogic server 6.1 sp3. The server creates three databaseconnection
    pools (details available in the attached config.xml).
    The database has a regular downtime every day for a few hours. We arerunning
    the server as a windows service. As per the "RefreshMinutes" property,the server
    should be able to get new fresh connections once the database comesup. But in
    our case it is not doing so. Once the database comes up after its regulardowntime:
    -- Sometimes the server does not respond as in we are not able toopen the console
    page.
    -- Any client that tries connecting to the database thru the servergets blocked
    and does not respond.
    -- The log file(weblogic.log) does not get updated after some time.
    Can someone suggest why the server is showing such a behaviour??
    Could it be anything related to the DBMS setting or to the local machine'ssettings
    ? Following is the thread dump after the server stops responding:Hi. I do see a problem in the thread dump. The application code is calling
    java.sql.DriverManager
    calls, which are a serious problem in multithreaded applications like
    weblogic, because
    DriverManager calls are all class-synchronized! All JDBC drivers and
    the SQLException constructor
    call DriverManager calls all the time, so a single long-running call
    to DriverManager.getConnection()
    can stop all other JDBC in the whole JVM. One problem you can fix is
    at:
    at tavant.platform.jdbc.JDBCTransaction.getConnection(Unknown Source)
    at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
    The getConnection() method should be altered to instantiate a Driver
    object and
    call Driver.connect() directly to make a pool connection, avoiding the
    DriverManager
    call:
    Driver d = (Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
    Connection c = d.connect("jdbc:weblogic:pool:" + myPoolName, null );
    Let me know if you can make this application change and whether it fixes
    the
    problem or not.
    I could also help if I could see the config.xml, but you seem to have
    attached the
    startup script.
    Joe Weinstein
    Full thread dump:
    "ListenThread" prio=5 tid=0x14ffb570 nid=0x148c runnable [0x1685f000..0x1685fdbc]
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:468)
    at java.net.ServerSocket.implAccept(ServerSocket.java:243)
    at java.net.ServerSocket.accept(ServerSocket.java:222)
    at weblogic.socket.WeblogicServerSocket.accept(WeblogicServerSocket.java:26)
    at weblogic.t3.srvr.ListenThread.run(ListenThread.java:260)
    "Thread-3" daemon prio=5 tid=0x14fb18b8 nid=0x12d4 waiting on monitor[0x167df000..0x167dfdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-2" daemon prio=5 tid=0x14f21c68 nid=0xf08 waiting on monitor[0x1679f000..0x1679fdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "Thread-1" daemon prio=5 tid=0x14fb97d8 nid=0xcac waiting on monitor[0x1675f000..0x1675fdbc]
    at java.lang.Thread.sleep(Native Method)
    at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
    "ExecuteThread: '14' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e75a10
    nid=0x13ec waiting on monitor [0x1671f000..0x1671fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '13' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e74e58
    nid=0x1434 waiting on monitor [0x166df000..0x166dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '12' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e742a0
    nid=0x1154 waiting on monitor [0x1669f000..0x1669fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '11' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72ed0
    nid=0xfe4 waiting on monitor [0x1665f000..0x1665fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '10' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e72318
    nid=0x9a4 waiting on monitor [0x1661f000..0x1661fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e717d8nid=0xf38
    waiting on monitor [0x165df000..0x165dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70c98nid=0xf68
    waiting on monitor [0x1659f000..0x1659fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e70158nid=0x1008
    waiting on monitor [0x1655f000..0x1655fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6f610nid=0x1204
    waiting on monitor [0x1651f000..0x1651fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ead0nid=0xef4
    waiting on monitor [0x164df000..0x164dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6dfa8nid=0x12bc
    waiting on monitor [0x1649f000..0x1649fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6d5e8nid=0xf70
    waiting on monitor [0x1645f000..0x1645fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e6ccb0nid=0xf84
    waiting on monitor [0x1641f000..0x1641fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e67510nid=0x1418
    waiting on monitor [0x163df000..0x163dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'JmsDispatcher'" daemon prio=5 tid=0x14e64f60nid=0x1228
    waiting on monitor [0x1639f000..0x1639fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e5c3f0 nid=0xf60 waiting on monitor [0x1635f000..0x1635fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e5b908 nid=0xf78 waiting on monitor [0x1631f000..0x1631fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: 'weblogic.transaction.AsyncQueue'" daemonprio=5
    tid=0x14e3ebe0 nid=0xfb4 waiting on monitor [0x162df000..0x162dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e35958
    nid=0x9e8 waiting on monitor [0x1629f000..0x1629fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '8' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3ba30
    nid=0x5ac waiting on monitor [0x1625f000..0x1625fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '7' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3af20
    nid=0xdc4 waiting on monitor [0x1621f000..0x1621fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '6' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e3a410
    nid=0x11ec waiting on monitor [0x161df000..0x161dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '5' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14bfdff0
    nid=0x1078 waiting on monitor [0x1619f000..0x1619fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '4' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14bfd4e0
    nid=0x43c waiting on monitor [0x1615f000..0x1615fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '3' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e32410
    nid=0xb64 waiting on monitor [0x1611f000..0x1611fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '2' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14c4ee68
    nid=0xe30 waiting on monitor [0x160df000..0x160dfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14c4ec10
    nid=0x1140 waiting on monitor [0x1609f000..0x1609fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_rmi_queue'" daemonprio=5 tid=0x14e33b18
    nid=0xfc0 waiting on monitor [0x1605f000..0x1605fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x14e33968
    nid=0x718 waiting on monitor [0x1601f000..0x1601fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'" daemonprio=5 tid=0x14e3c0a0
    nid=0x119c waiting on monitor [0x15fdf000..0x15fdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfbce0 nid=0xb90 waitingon monitor
    [0x15f9f000..0x15f9fdbc]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '1' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x14e39758
    nid=0x11ac waiting on monitor [0x15f5f000..0x15f5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '0' for queue: '_weblogic_dgc_queue'" daemon prio=5tid=0x14e38898
    nid=0x1194 waiting on monitor [0x15f1f000..0x15f1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "TimeEventGenerator" daemon prio=5 tid=0x14bfc040 nid=0x10a8 waitingon monitor
    [0x15edf000..0x15edfdbc]
    at java.lang.Object.wait(Native Method)
    at weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:279)
    at weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:138)
    at java.lang.Thread.run(Thread.java:484)
    "SpinnerRandomSource" daemon prio=5 tid=0x14e30c40 nid=0x794 waitingon monitor
    [0x15e9f000..0x15e9fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.security.SpinnerRandomBitsSource.run(SpinnerRandomBitsSource.java:57)
    at java.lang.Thread.run(Thread.java:484)
    "ExecuteThread: '29' for queue: 'default'" daemon prio=5 tid=0x14e2fe20nid=0xee8
    runnable [0x15e5f000..0x15e5fdbc]
    at java.net.SocketInputStream.socketRead(Native Method)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at oracle.net.ns.Packet.receive(Unknown Source)
    at oracle.net.ns.NetInputStream.getNextPacket(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.net.ns.NetInputStream.read(Unknown Source)
    at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:931)
    at oracle.jdbc.ttc7.MAREngine.unmarshalSB1(MAREngine.java:893)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:369)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1891)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:830)
    at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2391)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2672)
    at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:572)
    at weblogic.jdbc.pool.Statement.executeQuery(Statement.java:850)
    at tavant.platform.jdbc.JDBCTransaction.executeReadQuery(UnknownSource)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '28' for queue: 'default'" daemon prio=5 tid=0x14e2f268nid=0x12f0
    runnable [0x15e1f000..0x15e1fdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '27' for queue: 'default'" daemon prio=5 tid=0x14be7af0nid=0x11c4
    runnable [0x15ddf000..0x15ddfdbc]
    at weblogic.socket.NTSocketMuxer.getNextSocket(Native Method)
    at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:589)
    at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '26' for queue: 'default'" daemon prio=5 tid=0x14be7748nid=0x6dc
    waiting for monitor entry [0x15d9f000..0x15d9fdbc]
    at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:681)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:520)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:405)
    at weblogic.common.internal.ResourceAllocator.reserveWaitSecs(ResourceAllocator.java:395)
    at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:163)
    at weblogic.jdbc.common.internal.ConnectionPool.reserveWaitSecs(ConnectionPool.java:117)
    at weblogic.jdbc.pool.Driver.connect(Driver.java:152)
    at java.sql.DriverManager.getConnection(DriverManager.java:517)
    at java.sql.DriverManager.getConnection(DriverManager.java:199)
    at tavant.platform.jdbc.JDBCTransaction.getConnection(UnknownSource)
    at tavant.platform.jdbc.JDBCTransaction.start(Unknown Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean.invokeSQL(Unknown
    Source)
    at tavant.custom.iri.erpconnector.b2bi.communication.receiver.webservice.WebServiceBean_t63yf9_EOImpl.invokeSQL(WebServiceBean_t63yf9_EOImpl.java:456)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.invokeMethod(StatelessBeanAdapter.java:184)
    at weblogic.soap.server.servlet.StatelessBeanAdapter.doPost(StatelessBeanAdapter.java:115)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:262)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:198)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2637)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2359)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '25' for queue: 'default'" daemon prio=5 tid=0x14be6b90nid=0x10f4
    waiting for monitor entry [0x15d5f000..0x15d5fdbc]
    at java.sql.DriverManager.println(DriverManager.java:424)
    at java.sql.SQLException.<init>(SQLException.java:44)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)
    at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:404)
    at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
    at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:197)
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:270)
    at weblogic.jdbc.common.internal.ConnectionEnv.refresh(ConnectionEnv.java:919)
    at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:885)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '24' for queue: 'default'" daemon prio=5 tid=0x14be5fd8nid=0x10a4
    waiting on monitor [0x15d1f000..0x15d1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '23' for queue: 'default'" daemon prio=5 tid=0x14be5420nid=0x11b0
    waiting on monitor [0x15cdf000..0x15cdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '22' for queue: 'default'" daemon prio=5 tid=0x14be4868nid=0x11bc
    waiting for monitor entry [0x15c9f000..0x15c9fdbc]
    at java.sql.DriverManager.println(DriverManager.java:424)
    at java.sql.SQLException.<init>(SQLException.java:44)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at oracle.jdbc.driver.OracleConnection.privateCreateStatement(OracleConnection.java:758)
    at oracle.jdbc.driver.OracleConnection.createStatement(OracleConnection.java:712)
    at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:977)
    at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:470)
    at weblogic.common.internal.ResourceAllocator.reserveUnused(ResourceAllocator.java:381)
    at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.java:1125)
    at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:238)
    at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:229)
    at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:69)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    "ExecuteThread: '21' for queue: 'default'" daemon prio=5 tid=0x14be3cb0nid=0x10e0
    waiting on monitor [0x15c5f000..0x15c5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '20' for queue: 'default'" daemon prio=5 tid=0x14be30f8nid=0x620
    waiting on monitor [0x15c1f000..0x15c1fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '19' for queue: 'default'" daemon prio=5 tid=0x14be2540nid=0x350
    waiting on monitor [0x15bdf000..0x15bdfdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '18' for queue: 'default'" daemon prio=5 tid=0x14be1988nid=0x104c
    waiting on monitor [0x15b9f000..0x15b9fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:118)
    "ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x14c4db30nid=0xff0
    waiting on monitor [0x15b5f000..0x15b5fdbc]
    at java.lang.Object.wait(Native Method)
    at java.lang.Object.wait(Object.java:420)
    at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:94)
    at webl

  • [原创] 有关Weblogic Connection Pool 连接恢复的问题

    这是一个古老的问题，一直困扰我，这里既然碰到了，就看看能不能解决。
    环境描述：
    WEBLOGIC版本是8.1 SP2，数据库是SQL SERVER 2000，分别部署在两个服务器上。
    第一步：
    问题描述：
    数据库服务器重新启动，导致WEBLOGIC 的CONNECTION POOL中的连接中断，EJB无法获得连接，导致应用出错。
    解决方法：
    进入WEBLOGIC ADMIN CONSOLE,
    Services->JDBC->Connection Pools->Config->Connections， 点开Advanced Options.
    打开 Test Reserved Connections ，Test Created Connections，Test Released Connections这三个选项。
    将Test Table Name属性设置为:sysproperties(SQL Server系统表，即使自己的应用不存在，这个表也存在，而且默认的内部没有数据)
    根据如下解释：
    Connections that fail the test are closed and reopened to re-establish a valid physical database connection.
    (You must specify a Test Table Name below.)
    每次调用首先进行测试连接，如果测试失败连接将重新建立。
    测试结果：
    WEBLOGIC启动后，关闭数据库SQL SERVER，应用服务器前端调用此时失败。
    重新启动SQL SERVER后，WEBLOGIC端略做等待，前端应用恢复正常。
    第二步：
    问题描述：
    进一步测试，如果WEBLOGIC先启动，启动完成后再启动数据库。
    在WEBLOGIC CONSOLE得到如下输出：
    <2006-3-22 上午11时50分08秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
    ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
    <2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001150> <Connection Pool "MyJDBC Connection Pool" deployment
    failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [Microsoft][SQLServe
    r 2000 Driver for JDBC]Error establishing socket..>
    <2006-3-22 上午11时50分10秒 GMT+08:00> <Error> <JDBC> <BEA-001151> <Data Source "MyJDBC Data Source" deployment failed w
    ith the following error: DataSource(jdbc/OMSEIITxDS) can't be created with non-existent Pool (connection or multi) (MyJD
    BC Connection Pool).>
    Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
    [EJB:011028]The DataSource with the JNDI name: jdbc/XXXXXX could not be located. Please ensure that the DataSource h
    as been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
    1、在默认初始化打开的连接一一失败以后，连接池发现可用的连接为0，郁闷的宣布自己部署失败。
    2、接着数据源发现没有可用的连接池，自己也宣布部署失败。
    3、下面所有的EJB发现不了数据源的JNDI名，部署也全部失败。
    应用启动完成后，大部分EJB的状态为INACTIVE。前端应用无法使用，此时启动数据库，前端应用无法使用。
    手动重新部署 EJB失败,错误还是找不到JNDI，前端应用无法使用。
    手动重新部署 连接池，数据源后，部署EJB 依然失败。前端应用无法使用。
    解决方法：
    进入WEBLOGIC ADMIN CONSOLE,
    Services->JDBC->Connection Pools->Config->Connections， 点开Advanced Options.
    将
    Connection Creation Retry Frequency 参数设置为 60。
    ConnectionCreationRetryFrequencySeconds含义：
    当创建数据库连接时,如果数据库不可用(如数据库没启动),隔多长时间试着重新创建该连接,
    WLS8.1会每隔ConnectionCreationRetryFrequencySeconds秒重试一次.直到JDBC POOL创建成功
    参考：http://dev2dev.bea.com.cn/techdoc/20030469.html，‘JDBC Connect Pool’部分。
    英文解释可以直接控制台上看到，或者edocs查。
    测试结果：
    将数据库关闭，WEBLOGIC重新启动。
    在WEBLOGIC CONSOLE得到如下输出：
    打开Connection Creation Retry Frequency 参数后，连接池在第一轮尝试失败以后，就成功部署了，数据源也成功部署。
    EJB部署会失败，但是提示也与先前的不同：
    Unable to deploy EJB: XXXXXXX from XXXXXXX.jar:
    weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool MyJDBC Connection Pool to
    allocate to applications, please increase the size of the pool and retry..
    每隔一段时间会看到，CONNECTION POOL不断的重新进行连接：
    <2006-3-22 下午12时17分56秒 GMT+08:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for p
    ool "MyJDBC Connection Pool": [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.>
    在WEBLOGIC启动完成后，所有EJB为INACTIVE状态。
    启动数据库服务器，稍后，手动重新部署所有的EJB，EJB可以部署成功，前端应用可以正常使用。
    此时，此问题已经基本解决，仍需要手动部署EJB。
    第三步：
    问题描述：
    解决方法：
    有关部署次序的问题，首先查阅WEBLOGIC文档，http://edocs.bea.com/wls/docs81/faq/deploy.html#744900，得到
    WebLogic Server deploys server-level resources (first JDBC and then JMS) before deploying applications.
    Applications are deployed in this order: connectors, then EJBs, then Web Applications.
    If the application is an EAR, the individual components are loaded in the order in which they are declared
    in the application.xml deployment descriptor.
    WEBLOGIC先部署服务器端资源，JDBC -> JMS....，然后部署我们的应用，EJB->WEB APPLICATION。
    实际从WEBLOGIC启动日志来看，即使打开了Connection Creation Retry Frequency，如果当时数据库不是可用的，CONNECTION POOL
    会不断的调度CONNECTION进行重新连接。但是此时，EJB的部署也同时在进行。个人猜测这应该是两个不同的线程（组）分别调度的任务。
    现在考虑的是能不能用StartupClass截住EJB的部署过程，粗略的说是如果DATASOURCE没有连接好，或者没有可用的连接池，
    就不往下进行EJB部署的过程。
    参考：http://edocs.bea.com/wls/docs81/config_xml/EJBComponent.html#DeploymentOrder
    DeploymentOrder：
    A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable
    items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and
    deploys startup classes.Items with the lowest Deployment Order value are deployed first.
    There is no guarantee on the order of deployments with equal Deployment Order values.
    There is no guarantee of ordering across clusters. Default: 1000 Minimum: 0 Maximum: 2N31-1
    在部署同一类应用时，按照 DEPLOYMENT LOADER的数值决定，数值越小越先。（EJB的参数在ADMIN CONSOLE界面上叫做LOAD ORDER)
    而且上面看来服务器是先部署EJB，再部署STARTUP CLASS，遗憾了。
    好在STARTUP CLASS上有两个选项，
    Run Before Application Deployments
    Run Before Application Activations
    这两个选项分别可以设置StartupClass分别在系统资源部署之前，以及在系统资源部署和用户应用部署之间启动。
    选上Run Before Application Activations。
    现在可以了，我写了一个STARTUP CLASS，思路见下：
    主代码：
    private void testConnection(){
    while (!isTimeout() && !getConnection()){
    try{
    Thread.sleep(testInterval*1000);
    }catch(Exception ignor){}
    log("DBConnectHolder job finished with following status:");
    log("Timeout:"+isTimeout +",Connection OK:"+isConnected);
    测试结果：
    只要配置的等待时间足够长，应用服务器先行启动的情况下，等待数据库启动后才进行EJB等等的部署。
    （主要考虑如果数据库连接不OK，EJB启动了也没有太大用，还得手工重新部署。）算是比较完满的解决了问题。
    另外一个思路是是否可行？ 通过MBean, 在CONNECTION 建立起来以后通知一把，进行EJB的重新部署。
    没来得及研究，请有经验的同学帮我补充完善。
    结论：
    其实也没什么结论，只是把自己遇到问题，解决问题的思路写了一下。短时间内阅读的文献有限，可能采用了一些苯方法
    ，或者走了弯路，也请大家拍砖。
    在WL8版本上，数据库连接进行恢复和重新连接的时候，上面提出的几个参数应该是比较重要的，我再次强调一下。
    Services->JDBC->Connection Pools->Config->Connections， 点开Advanced Options.
    Test Reserved Connections
    Test Created Connections
    Test Released Connections
    Test Table Name
    Connection Creation Retry Frequency

    在第一个情景中应该只需要打开Test Reserved Connections 就可以了。
    Test Created Connections表示创建连接后放到pool之前进行测试看连接是否可用
    Test Released Connections表示释放连接回到pool之前进行测试看连接是否可用
    I think so！

Maybe you are looking for

  • Partners in partners tab in CHARM

    Hi Everybody , I copied standard partner function procedure SDCR0001 to ZDCR0001 and added few new partners. It is working fine . But my issue is in partners tab in CRMD_ORDER i am getting all partner functions in system . I need to have only partner

  • Embedding form code into a lightbox

    Hello, I am working on a simple test page trying to figure out lightboxes. I have it almost functional based on examples I found online, however, I am stuck. I can't seem to figure out how to embed my form code into the lightbox successfully. Basical

  • Stealth mode and firewall logging problems to be resolved please.

    I am running OS X v10.6.8 and am having difficulty setting stealth mode. System Preferences shows stealth mode to be switched on, but System Profiler shows it to be off, no matter how many times I set it and shut down/restart. System profiler also sh

  • How do I canel my anual iCloud payment. I no longer have an iPhone

    I no longer have an Iphone but I paid to increase my iCloud storage to 15GB. How do I cancel my account to stop further payments?

  • Restrictions for children

    Hi, I have just invested in iPod Touch for both my children. We have already fallen in love with them and have had lots of fun already. I have set up restrictions on both and installed a safe browser app. This I thought would mean that anything of an