WLS 5.1 hangs
Environment: WLS 5.1 SP6 on AIX 4.3.3, IBM JVM 1.2.2WLS becomes unresponsive and produces the following error (usually in the middle of the night when there is no activity on the system):Mon Jun 25 01:11:01 CDT 2001:<I> <TX> Transaction (TxC (-1667769276, xid = 993380456684_72, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.Are there any thoughts as to what to look for? There is no apparent pattern to the occurrences.
It sounds like you have an application deadlock resulting in a timeout and rollback of one of the competing transactions. Obviously, there is some activity on the server (perhaps batch scheduled). You could try taking thread dumps every 20 seconds during the period when you see this error. This should catch the offending code as it waits for the timeout.
-Charlie
Larry wrote:
Environment: WLS 5.1 SP6 on AIX 4.3.3, IBM JVM 1.2.2WLS becomes unresponsive and produces the following error (usually in the middle of the night when there is no activity on the system):Mon Jun 25 01:11:01 CDT 2001:<I> <TX> Transaction (TxC (-1667769276, xid = 993380456684_72, timeout = 300, txState = Marked Rollback, root = null) rolled back after 300 sec.Are there any thoughts as to what to look for? There is no apparent pattern to the occurrences.
Similar Messages
-
WLS 5.1 hangs due to many sockets in CLOSE_WAIT state
Hi,
we are having some serious problems with Weblogic Server 5.1 (SP 6) with
several of our customer installations (Solaris 5.8 and HP UX). The problem
relates to the WLS http server not dealing with socket connections in
CLOSE_WAIT state correctly. We have observered that these can be caused by
Netscape browsers when the end user clicks on the reload button. This causes
the socket connection to be placed in CLOSE_WAIT state, it stays like this
for ever and eventually when there are many sockets in this state WLS runs
out of file descriptors and hangs. We have tried using WLS Apache plugin but
Apache merely passes the CLOSE_WAIT's onto WLS web server. Any help
appreciated on this one,.....
regards Donal.The problem is that your file descriptor table is filling up with sockets in the
CLOSE_WAIT state so there is no more room to put new file descriptors. Any
machine that speaks HTTP is subject to this so you need to apply these changes
both to the web server machine(s) and the application server machine(s).
The way to handle this on Solaris is to decrease the close wait interval:
ndd -set /dev/tcp tcp_close_wait_interval 60000 (Solaris 2.6 and below)
ndd -set /dev/tcp tcp_time_wait_interval 60000 (Solaris 2.7 and above)
(NOTE: It is recommended that you not go below 60 seconds for this, as per
Adrian Cockroft of SUN).
and increase the size of the file descriptor table by adding the following in
/etc/system:
rlim_fd_cur 8192
rlim_fd_max 8192
(NOTE: The close wait interval can also be set in /etc/system, though I don't
remember the name of the parameter off the top of my head.)
Also, make sure that you change the startWebLogic.sh script to grab more file
descriptors with ulimit (or simply remove the ulimit section of the script)...
Hope this helps,
Robert
Donal Mc Ateer wrote:
We have done this. We have made the following 'tweaks' to the Solaris
installation
ndd -set /dev/tcp tcp_keepalive_interval 300000
ndd -set /dev/tcp tcp_ip_abort_interval 2000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_fin_wait_2_flush_interval 67500
ndd -set /dev/tcp tcp_time_wait_interval 30000
is there anything else we can do? Is there any way of influencing the WLS
http server handling of these CLOSE_WAIT sockets? Is this being addressed in
WLS 6.0?
-Donal.
"shivu" <[email protected]> wrote in message
news:[email protected]...
try tuning the tcp parameters at solaris level.
(i think tcp_conn_wait)
"Donal Mc Ateer" <[email protected]> wrote:
Hi,
we are having some serious problems with Weblogic Server 5.1 (SP 6) with
several of our customer installations (Solaris 5.8 and HP UX). The
problem
relates to the WLS http server not dealing with socket connections in
CLOSE_WAIT state correctly. We have observered that these can be causedby
Netscape browsers when the end user clicks on the reload button. Thiscauses
the socket connection to be placed in CLOSE_WAIT state, it stays likethis
for ever and eventually when there are many sockets in this state WLSruns
out of file descriptors and hangs. We have tried using WLS Apache pluginbut
Apache merely passes the CLOSE_WAIT's onto WLS web server. Any help
appreciated on this one,.....
regards Donal. -
I am having an issue with BEA 8.1 hanging when using XA. I have configured it
on several other Windows 2000 machines and not seen an issue. This particular
machine seems to hang and then give a time out error. ANy suggestions would
be appreciated. Below is the error that I am getting back and a thread dump.
java.lang.Exception: Exception while commiting Tx : Name=[EJB com.level3.ds9.business.ejb.SearchEJB.getLocations(java.lang.String,com.level3.ds9.common.L3Environment)],Xid=BEA1-001E3F8C31D9BB58DEB7(18601996),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=122,seconds left=2878,XAServerResourceInfo[lidPool]=(ServerResourceInfo[lidPool]=(state=new,assigned=none),xar=null),SCInfo[mydomain+brettjason]=(state=active),SCInfo[ds9FT+ds9server3]=(state=active),properties=({weblogic.transaction.name=[EJB
com.level3.ds9.business.ejb.SearchEJB.getLocations(java.lang.String,com.level3.ds9.common.L3Environment)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=brettjason+10.1.44.74:7001+mydomain+t3+,
XAResources={},NonXAResources={})],CoordinatorURL=ds9server3+10.1.19.141:7001+ds9FT+t3+);
nested exception is: javax.transaction.SystemException: Timeout during commit
processing
Exception while commiting Tx : Name=[EJB com.level3.ds9.business.ejb.SearchEJB.getLocations(java.lang.String,com.level3.ds9.common.L3Environment)],Xid=BEA1-001E3F8C31D9BB58DEB7(18601996),Status=Unknown,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=122,seconds left=2878,XAServerResourceInfo[lidPool]=(ServerResourceInfo[lidPool]=(state=new,assigned=none),xar=null),SCInfo[mydomain+brettjason]=(state=active),SCInfo[ds9FT+ds9server3]=(state=active),properties=({weblogic.transaction.name=[EJB
com.level3.ds9.business.ejb.SearchEJB.getLocations(java.lang.String,com.level3.ds9.common.L3Environment)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=brettjason+10.1.44.74:7001+mydomain+t3+,
XAResources={},NonXAResources={})],CoordinatorURL=ds9server3+10.1.19.141:7001+ds9FT+t3+);
nested exception is: javax.transaction.SystemException: Timeout during commit
processing
"ExecuteThread: '12' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x2
770EB70 nid=0xa34 in Object.wait() [2868f000..2868fd88]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <054801B8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x2
76E6858 nid=0x5f8 in Object.wait() [2864f000..2864fd88]
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480230> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x2
76E5C70 nid=0x670 in Object.wait() [2860f000..2860fd88]
at java.lang.Object.wait(Native Method)
- waiting on <054802A8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <054802A8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
6E50B0 nid=0x9c8 in Object.wait() [285cf000..285cfd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480320> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480320> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '8' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
71B350 nid=0x9bc in Object.wait() [2858f000..2858fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480398> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480398> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '7' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
71BC10 nid=0x7b8 in Object.wait() [2854f000..2854fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480410> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480410> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
71D7D8 nid=0x848 in Object.wait() [2850f000..2850fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480488> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480488> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '5' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
71C8F0 nid=0x9dc in Object.wait() [284cf000..284cfd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480500> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480500> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '4' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
71C798 nid=0x824 in Object.wait() [2848f000..2848fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480578> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480578> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
60B420 nid=0x770 in Object.wait() [2844f000..2844fd88]
at java.lang.Object.wait(Native Method)
- waiting on <054805F0> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <054805F0> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '2' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x26
F9FA10 nid=0xa64 in Object.wait() [2840f000..2840fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480668> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480668> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x27
580CC0 nid=0x8d8 in Object.wait() [283cf000..283cfd88]
at java.lang.Object.wait(Native Method)
- waiting on <054806E0> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <054806E0> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x26
F8F6B0 nid=0x7a0 in Object.wait() [2838f000..2838fd88]
at java.lang.Object.wait(Native Method)
- waiting on <05480758> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:426)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:145)
- locked <05480758> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:164)
"Signal Dispatcher" daemon prio=10 tid=0x008B4850 nid=0x978 waiting on condition
[0..0]
"Finalizer" daemon prio=9 tid=0x008FF7F8 nid=0x73c in Object.wait() [26cff000..2
6cffd88]
at java.lang.Object.wait(Native Method)
- waiting on <052A72C8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
- locked <052A72C8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=10 tid=0x008FE370 nid=0xa08 in Object.wait() [26
cbf000..26cbfd88]
at java.lang.Object.wait(Native Method)
- waiting on <052A7330> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:426)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:113)
- locked <052A7330> (a java.lang.ref.Reference$Lock)
"main" prio=5 tid=0x002358F8 nid=0x8a8 in Object.wait() [6f000..6fc40]
at java.lang.Object.wait(Native Method)
- waiting on <052A7508> (a weblogic.t3.srvr.T3Srvr)
at java.lang.Object.wait(Object.java:426)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:1170)
- locked <052A7508> (a weblogic.t3.srvr.T3Srvr)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:384)
at weblogic.Server.main(Server.java:32)
"VM Thread" prio=5 tid=0x008FD138 nid=0x88c runnable
"VM Periodic Task Thread" prio=10 tid=0x008B3390 nid=0x8bc waiting on condition
"Suspend Checker Thread" prio=10 tid=0x008B3E68 nid=0x524 runnableRunning Windows XP (even fully patched up with SP3 and latest fixes), you probably will have an increasing risk of Windows and IE being attacked. Windows XP has been getting security patches every month for over a decade. So it seems likely that people will continue to discover vulnerabilities in Windows XP that, over time, will be exploited (i.e., used in attacks).
Windows 8.1? For a good experience, you probably would be better off getting a new computer than installing 8.1 on a system that is several years old. I realize not everyone's budget permits.
What else can you do? It remains useful and important to keep your third party applications, such as Firefox, and your browser add-ons, such as Flash, up-to-date. It's also a good idea to run quality security software. And practice safe browsing habits like avoiding questionable websites and peer-to-peer networking, and being suspicious of email attachments. -
Hi,
I´ve got a problem when calling from a Tuxedo service to WLS within a transaction,
when the WSL-service makes a call to another Tuxedo service in the same domain
as the initiating service.
The call from WLS to Tuxedo hangs until timeout.
Eventually the following message extract occurs in the WLS log.
<2003-nov-03 kl 11:20 CET> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
weblogic.transaction.XAException: XAER_NOTA : The XID is not valid. ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+192.168.3.87:7001+examples+t3+,
XAResources={},NonXAResources={})].XAResource.end() fails. Foreign transaction
not recognized, foreignXid=BEA2-000000003FA61EE7000000BD000000010000002800000000000000000000001E-646F6D31..
Any ideas?
Or is it so that a transaction started in a Tuxedo domain cannot propagate all
the way around to WLS and back to the same Tuxedo domain again?
- BeritBerit,
The sequence that you described has worked in the past for us but it
is possible that something has changed between WTC and JTA. It is
also possible to get into confusion as to "initiator", "coordinator",
"delegated transactions", and "global transaction ids". I would suggest
that you open up a case with support and supply them with the Tuxedo
logs, the WLS logs and descriptions of the EJB and the two Tuxedo services.
Bob Finan
"Berit" <[email protected]> wrote in message
news:3fa64b3b$[email protected]..
>
Hi,
I´ve got a problem when calling from a Tuxedo service to WLS within atransaction,
when the WSL-service makes a call to another Tuxedo service in the samedomain
as the initiating service.
The call from WLS to Tuxedo hangs until timeout.
Eventually the following message extract occurs in the WLS log.
<2003-nov-03 kl 11:20 CET> <Error> <Kernel> <BEA-000802> <ExecuteRequestfailed
weblogic.transaction.XAException: XAER_NOTA : The XID is not valid.ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=examplesServer+192.168.
3.87:7001+examples+t3+,
XAResources={},NonXAResources={})].XAResource.end() fails. Foreigntransaction
not recognized,foreignXid=BEA2-000000003FA61EE7000000BD000000010000002800000000000000000000
001E-646F6D31..
>
Any ideas?
Or is it so that a transaction started in a Tuxedo domain cannot propagateall
the way around to WLS and back to the same Tuxedo domain again?
- Berit -
Getconnection hangs ( WLS 6.1 SP4, UDB 7.2 Fixpak7, Type 2 Driver)
Hello,
We sometimes experience application hang when a user logon due to all threads waiting to get connection from UDB server. Any help is appreciated.
Environment
App Server: WLS 6.1 SP4
Database: DB2 UDB 7.1
JDBC Adapter: Type 2 IBM Driver (COM.ibm.db2.jdbc.app.DB2Driver)
We have setup connection pool and a TX data source.
Connection pool related config.xml
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.ibm.db2.jdbc.app.DB2Driver" InitialCapacity="40"
LoginDelaySeconds="1" MaxCapacity="50" Name="LPDSS_DB2_POOL1"
PreparedStatementCacheSize="100"
Properties="user=xxx;password=xxx;language=C"
RefreshMinutes="999999" ShrinkingEnabled="false"
Targets="ms1" TestConnectionsOnRelease="false"
TestConnectionsOnReserve="true" TestTableName="SYSIBM.SYSDUMMY1" URL="jdbc:db2:xxxx"/>
The thread dump analysis shows that getconnection() call waiting for a lock (waiting for monitor entry) and java.weblogic.Admin RESET_POOL doesn't work either. The call never returns.
"ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x494e78 nid=0x1b waiting for monitor entry [0xaf580000..0xaf5819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x495970 nid=0x1c waiting for monitor entry [0xaf481000..0xaf4819d8]
at weblogic.common.internal.ResourceAllocator.reset(ResourceAllocator.java:848)
at weblogic.common.internal.ResourceAllocator_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x496468 nid=0x1d waiting for monitor entry [0xaf37f000..0xaf3819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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.jts.Connection.getOrCreateConnection(Connection.java:569)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:117)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78)
"ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x497568 nid=0x1e waiting for monitor entry [0xaf280000..0xaf2819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x494380 nid=0x1a waiting for monitor entry [0xaf680000..0xaf6819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x493888 nid=0x19 waiting for monitor entry [0xaf780000..0xaf7819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
Exception in JDBC log shows there is a communication problem.
SQLException: SQLState(40003) vendor code(-30081)
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL30081N A communication error has been detected. Communication protocol being
used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xx.xx.xx.xx". Communication function dete
cting the error: "recv". Protocol specific error code(s): "145", "*", "*". SQLSTATE=08001
---------------------------------------------------ganesh narayanan wrote:
Hello,
We sometimes experience application hang when a user logon due to all threads waiting to get connection from UDB server. Any help is appreciated.
Environment
App Server: WLS 6.1 SP4
Database: DB2 UDB 7.1
JDBC Adapter: Type 2 IBM Driver (COM.ibm.db2.jdbc.app.DB2Driver)
We have setup connection pool and a TX data source.
Connection pool related config.xml
<JDBCConnectionPool CapacityIncrement="1"
DriverName="COM.ibm.db2.jdbc.app.DB2Driver" InitialCapacity="40"
LoginDelaySeconds="1" MaxCapacity="50" Name="LPDSS_DB2_POOL1"
PreparedStatementCacheSize="100"
Properties="user=xxx;password=xxx;language=C"
RefreshMinutes="999999" ShrinkingEnabled="false"
Targets="ms1" TestConnectionsOnRelease="false"
TestConnectionsOnReserve="true" TestTableName="SYSIBM.SYSDUMMY1" URL="jdbc:db2:xxxx"/>
The thread dump analysis shows that getconnection() call waiting for a lock (waiting for monitor entry) and java.weblogic.Admin RESET_POOL doesn't work either.
The call never returns.
>
We'd need to see all the threads, preferably before you try (repeatedly it seems) to
reset the pool. There may well be problems with the IBM driver and DBMS...
Joe
"ExecuteThread: '14' for queue: 'default'" daemon prio=5 tid=0x494e78 nid=0x1b waiting for monitor entry [0xaf580000..0xaf5819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '15' for queue: 'default'" daemon prio=5 tid=0x495970 nid=0x1c waiting for monitor entry [0xaf481000..0xaf4819d8]
at weblogic.common.internal.ResourceAllocator.reset(ResourceAllocator.java:848)
at weblogic.common.internal.ResourceAllocator_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
"ExecuteThread: '16' for queue: 'default'" daemon prio=5 tid=0x496468 nid=0x1d waiting for monitor entry [0xaf37f000..0xaf3819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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.jts.Connection.getOrCreateConnection(Connection.java:569)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:117)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:78)
"ExecuteThread: '17' for queue: 'default'" daemon prio=5 tid=0x497568 nid=0x1e waiting for monitor entry [0xaf280000..0xaf2819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '13' for queue: 'default'" daemon prio=5 tid=0x494380 nid=0x1a waiting for monitor entry [0xaf680000..0xaf6819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
"ExecuteThread: '12' for queue: 'default'" daemon prio=5 tid=0x493888 nid=0x19 waiting for monitor entry [0xaf780000..0xaf7819d8]
at weblogic.common.internal.ResourceAllocator.resetThisOne(ResourceAllocator.java:877)
at weblogic.common.internal.ResourceAllocator.reserve(ResourceAllocator.java:486)
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 weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:319)
at weblogic.jdbc.jts.Driver.connect(Driver.java:120)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:214)
Exception in JDBC log shows there is a communication problem.
SQLException: SQLState(40003) vendor code(-30081)
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL30081N A communication error has been detected. Communication protocol being
used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "xx.xx.xx.xx". Communication function dete
cting the error: "recv". Protocol specific error code(s): "145", "*", "*". SQLSTATE=08001 -
Stateless Session EJB hangs using URLConnection but WLS doesn't clean up
Hi
We have a stateless session EJB running under WLS 5.1 with service
pack 10 on Solaris.
The bean calls a remote HTTP server using the java.net.URLConnection
class and forwards the response to the EJB client. The bean is largely
working fine but some threads hang waiting on the HTTP response. Debug
statements, which are written immediately after the response has been
read and the connection has been closed, do not appear in our log for
the hung threads. The WebLogic Console displays these threads as "in
use" and a "netstat -an" displays the tcp connections as ESTABLISHED.
However, the access logs of the remote Apache server show the HTTP
connections of the threads in question completed successfully with
HTTP code 200. The Apache server is using keep-alive connections.
Some EJB threads are still waiting for something it seems.
Has anyody else experienced this when using URLConnection from
stateless session EJBs under WLS?
The second problem is why doesn't WLS time these threads out after
trans-timeout-seconds (we're using the default of 300 seconds)? The
WLS log shows no error messages relating to this problem.
I'm grateful for any info offered.
Thanks in advance
SteveIf you suspect that WLS protocol handler is at fault (and quite often it is),
one thing to try is (if you use Sun's JVM) to use Sun's HTTP protocol handler
instead of WLS (the most common symptom is when code which makes HTTP requests
works fine outside of WebLogic and you have problems getting it to work inside
WebLogic) :
replace
URL url = new URL("http://...");
HttpURLConnection conn = (HttpURLConnection)url.openConnection();
with
URL url = new URL(null, "http://...", new sun.net.www.protocol.http.Handler());
HttpURLConnection conn = (HttpURLConnection)url.openConnection();
You will have to edit weblogic.policy to allow your code to specify protocol
handler.
Also note that transaction timeout is only checked on method boundaries, or
when your code attempts to do something with the database - it is not going to
interrupt thread which is waiting for HTTP response.
Steve Lock <[email protected]> wrote:
Hi
Thanks for the info. The remote HTTP server's access log shows that
the requests were successfully processed. Doesn't this mean that the
connection is then closed? I know the web server is using keep-alive
connections but I thought this was transparent to the client...?
Also why doesn't WLS remove the hung threads?
Steve
"Ignacio G. Dupont" <[email protected]> wrote in message news:<[email protected]>...
We have had a problem like yours with Weblogic 6.1 SP2 on Linux
The problem is sun's implementation of the HTTP connections doesn't have a
timeout, so if the other peer doesn't close the connection your threads will
be "locked" on the connection.
We have found searching the web that the Jakarta project has a package
called Jakarta commons that implements HTTP connections with an
setSoTimeout(int timeout) method so you can open the connections with your
desired timeout. You have to download the code from the CVS as the released
version doesn't support the timedout sockets yet.
When support for the JDK 1.4 version will be announced by Bea you could use
one of its new features that will allow you to pass arguments to the JVM to
specify the maximum socket connection stablising timeout and the max
inactivity on the socket too.
Hope it helps you.
Dimitri -
WLS hanger when calling EJB in second WLS
Hello,
I have a very strange problem I need to track down. The scenario is as follows:
WLS6.1 SP3/Solaris 2.8
One WLS containing an EJB A (stateless session) that has Trx=Required on method_A,
the second WLS that has an EJB B deployed (stateless session) that has Trx=NotSupported
on method_B. Now I call in a client method_A of EJB A, which calls method_B of
EJB B. This works fine.
Now I install the second WLS on an different machine (same OS=solaris), and repeat
above scenario. The result is that I am able to call method_A of EJB A, which
calls method_B of EJB B. But after I return from method_B/EJB in EJB A, I hang
in EJB A/postInvoke.
From the thread dump I see the following:
"ExecuteThread: '46' for queue: 'default'" daemon prio=5 tid=0x7c20c0 nid=0x35d
waiting on monitor [0xdb0f000..0xdb0fdc0]
at java.lang.Object.wait(Native Method)
at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:1970)
at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:1899)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:220)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:189)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:272)
at com.csg.pb.tit.tdc.cptypay.ejb.CounterpartyPayPathBean_43jp4t_EOImpl.routeCif(CounterpartyPayPathBean_43jp4t_EOImpl.java
at com.csg.pb.tit.tdc.cptypay.ejb.CounterpartyPayPathBean_43jp4t_EOImpl_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:305)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:274)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
How canI find out what is going on?
Thanks
JuergI am getting the same exception about an assertion failed at weblogic.t3.srvr.T3Srvr.checkServerLock. Any ideas?
-
Hello,
Not sure if this is the right newsgroup-I am trying to
diagnose a problem where the weblogic server(5.1, SP9) hangs. I have run
it through JProbe's Threadalyzer and I checked for deadlocks and no
deadlocks were reported. What was reported were three thread stalls (one
block stall and two wait stalls) . All the three thread stalls were
holding JMSServerSession(different instances of it).
Here is the architecture -
A third party application makes a HTTP request to a servlet running on
WLS and that servlet posts a message to JMS and returns. We are using
ServerSessionPool. The client class implementing the MessageListener
then calls other RMI objects within the same JVM(its non-clustered
weblogic).
Here is the question-under heavy load this seems to hang the system
eventually. I am unable to determine why at this point. The thread dump
is different each time.
The onMessage() method calls one RMI object which delegates to a
detailed object tree several layers deep(other RMI objects). In one of
those RMI objects there is a synchronized block.
Currently there is no notifyAll() being issued when this synchronized
block exits.
Is it necessary then to issue a notifyAll() within any synchronized code
that is within the 'scope' of the onMessage()
I would like the JMS thread to return immediately. So that the rest of
the RMI code is handled in other threads.
Thanks in advance,
Aswin.Here is the thread dump-JProbe did not report any deadlock again( I did not profile the
weblogic.* classes). However the CPU usage was 100% and the server just hung-
"Thread-5" daemon prio=5 tid=0x3e1e7470 nid=0xd9 runnable [0x3e2af000..0x3e2afdc
0]
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:225)
at java.io.BufferedInputStream.read(BufferedInputStream.java:280)
- locked <619fd20> (a java.io.BufferedInputStream)
at COM.activesw.api.client.BrokerConnection.readData(BrokerConnection.ja
va:1584)
at COM.activesw.api.client.BrokerConnection.run(BrokerConnection.java:15
06)
"SocketListener" daemon prio=5 tid=0x3cef3c30 nid=0xd4 runnable [0x3cf6f000..0x3
cf6fdc0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
- locked <4fb6d10> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at com.inprise.vbroker.IIOP.Listener.accept(Listener.java:102)
at com.inprise.vbroker.orb.SocketSCM$ListenerThread.run(SocketSCM.java:3
2)
at java.lang.Thread.run(Thread.java:484)
"AreYouAlive" daemon prio=5 tid=0x3cd1e520 nid=0x17a waiting on monitor [0x3ce2f
000..0x3ce2fdc0]
at java.lang.Object.wait(Native Method)
- waiting on <4da7f58> (a com.inprise.vbroker.ds.DSUser$AreYouAlive)
at com.inprise.vbroker.ds.DSUser$AreYouAlive.run(DSUser.java:115)
- locked <4da7f58> (a com.inprise.vbroker.ds.DSUser$AreYouAlive)
"DatagramThread" daemon prio=5 tid=0x3cd19af0 nid=0x138 runnable [0x3cdef000..0x
3cdefdc0]
at java.net.PlainDatagramSocketImpl.peek(Native Method)
- locked <4da1a10> (a java.net.PlainDatagramSocketImpl)
at java.net.DatagramSocket.receive(DatagramSocket.java:354)
- locked <140c7130> (a java.net.DatagramPacket)
- locked <4da19f8> (a java.net.DatagramSocket)
at com.inprise.vbroker.ds.DSUser$DatagramThread.run(DSUser.java:157)
"GarbageCollector" daemon prio=5 tid=0x3cb80100 nid=0x1a5 waiting on monitor [0x
3ccaf000..0x3ccafdc0]
at java.lang.Object.wait(Native Method)
- waiting on <4bca9c0> (a com.inprise.vbroker.orb.GarbageCollector)
at com.inprise.vbroker.orb.GarbageCollector.run(GarbageCollector.java:62
- locked <4bca9c0> (a com.inprise.vbroker.orb.GarbageCollector)
"ListenThread" prio=5 tid=0x3c57c310 nid=0x145 runnable [0x3c5df000..0x3c5dfdc0]
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:421)
- locked <3533380> (a java.net.PlainSocketImpl)
at java.net.ServerSocket.implAccept(ServerSocket.java:243)
at java.net.ServerSocket.accept(ServerSocket.java:222)
at weblogic.t3.srvr.ListenThread.run(ListenThread.java:286)
"LDAPConnThread majestix.xyz.com:389" daemon prio=5 tid=0x3a20bc40 nid=0
x110 runnable [0x3a29f000..0x3a29fdc0]
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:186)
at java.io.BufferedInputStream.read(BufferedInputStream.java:204)
- locked <3022d48> (a java.io.BufferedInputStream)
at netscape.ldap.ber.stream.BERElement.getElement(BERElement.java:101)
at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:420)
"NBExecuteThread-1" daemon prio=5 tid=0x38283ed0 nid=0x1e0 waiting on monitor [0
x388df000..0x388dfdc0]
at java.lang.Object.wait(Native Method)
- waiting on <2f0a498> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
- locked <2f0a498> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"NBExecuteThread-0" daemon prio=5 tid=0x38281180 nid=0x1ca waiting on monitor [0
x3889f000..0x3889fdc0]
at java.lang.Object.wait(Native Method)
- waiting on <2f09ea8> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
- locked <2f09ea8> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-19" daemon prio=5 tid=0x3827f660 nid=0x1b1 runnable [0x3885f000..
0x3885fdc0]
at java.lang.StringBuffer.toString(StringBuffer.java:1068)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:78)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <72e2d18> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-18" daemon prio=5 tid=0x3827e850 nid=0x170 waiting on monitor [0x
3881f000..0x3881fdc0]
at java.lang.Object.wait(Native Method)
- waiting on <2f08db0> (a weblogic.kernel.ExecuteThread)
at java.lang.Object.wait(Object.java:420)
at weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:99)
- locked <2f08db0> (a weblogic.kernel.ExecuteThread)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:126)
"ExecuteThread-17" daemon prio=5 tid=0x3827da10 nid=0x1e9 runnable [0x387df000..
0x387dfdc0]
at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
at java.lang.StringBuffer.append(StringBuffer.java:401)
- locked <140f83b0> (a java.lang.StringBuffer)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:78)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <6e04bf0> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-16" daemon prio=5 tid=0x3827cc20 nid=0x1c8 runnable [0x3879f000..
0x3879fdc0]
at org.apache.regexp.RECompiler.closure(RECompiler.java:939)
at org.apache.regexp.RECompiler.branch(RECompiler.java:1151)
at org.apache.regexp.RECompiler.expr(RECompiler.java:1203)
at org.apache.regexp.RECompiler.compile(RECompiler.java:1281)
at org.apache.regexp.RE.<init>(RE.java:495)
at com.xyz.king.common.Entities.decodeString(Entities.java:128)
at com.xyz.king.common.XmlEntities.decodeStringBasic(XmlEntities
.java:130)
at com.xyz.king.go.Tuvking$ExacgoatchFormatHandler.handleText(Tu
vking.java:264)
at com.xyz.king.common.DiplomatBasicParser.processText(DiplomatB
asicParser.java:196)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:85)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <6805850> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-15" daemon prio=5 tid=0x3827be10 nid=0x1a0 runnable [0x3875f000..
0x3875fdc0]
at java.lang.StringBuffer.<init>(StringBuffer.java:116)
at java.lang.StringBuffer.<init>(StringBuffer.java:104)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:91)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <7e02b88> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-14" daemon prio=5 tid=0x38279020 nid=0x139 runnable [0x3871f000..
0x3871fdc0]
at oracle.net.ns.NetInputStream.read(Unknown Source)
at oracle.jdbc.ttc7.MAREngine.unmarshalUB1(MAREngine.java:718)
at oracle.jdbc.ttc7.TTIoer.unmarshal(TTIoer.java:129)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:533)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822
- locked <2f22908> (a oracle.jdbc.ttc7.TTC7Protocol)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.ja
va:1446)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.jav
a:1371)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme
nt.java:1900)
at oracle.jdbc.driver.OracleStatement.executeUpdate(OracleStatement.java
:693)
- locked <140d4428> (a oracle.jdbc.driver.OracleStatement)
at weblogic.jdbc.pool.Statement.executeUpdate(Statement.java:59)
at weblogic.jms.server.JDBCStore.purgeMessages(JDBCStore.java:1147)
at weblogic.jms.server.JDBCStore.trigger(JDBCStore.java:880)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
edTrigger.java:205)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
er.java:199)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
0)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-13" daemon prio=5 tid=0x38278190 nid=0x1d1 runnable [0x386df000..
0x386dfdc0]
at java.lang.StringBuffer.toString(StringBuffer.java:1068)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:91)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <64dbad0> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-12" daemon prio=5 tid=0x38277660 nid=0x1d9 runnable [0x3869f000..
0x3869fdc0]
at weblogic.socket.NTSockegouxer.getNextSocket(Native Method)
at weblogic.socket.NTSockegouxer.processSockets(NTSockegouxer.java:331)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-11" daemon prio=5 tid=0x38276850 nid=0x12e runnable [0x3865f000..
0x3865fdc0]
at weblogic.socket.NTSockegouxer.getNextSocket(Native Method)
at weblogic.socket.NTSockegouxer.processSockets(NTSockegouxer.java:331)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
23)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-10" daemon prio=5 tid=0x38275a10 nid=0xce runnable [0x3861f000..0
x3861fdc0]
at org.apache.regexp.RECompiler$RERange.<init>(RECompiler.java:1305)
at org.apache.regexp.RECompiler.characterClass(RECompiler.java:572)
at org.apache.regexp.RECompiler.terminal(RECompiler.java:863)
at org.apache.regexp.RECompiler.closure(RECompiler.java:942)
at org.apache.regexp.RECompiler.branch(RECompiler.java:1151)
at org.apache.regexp.RECompiler.expr(RECompiler.java:1203)
at org.apache.regexp.RECompiler.compile(RECompiler.java:1281)
at org.apache.regexp.RE.<init>(RE.java:495)
at com.xyz.king.common.Entities.decodeString(Entities.java:128)
at com.xyz.king.common.XmlEntities.decodeStringBasic(XmlEntities
.java:130)
at com.xyz.king.go.Tuvking$ExacgoatchFormatHandler.handleText(Tu
vking.java:264)
at com.xyz.king.common.DiplomatBasicParser.processText(DiplomatB
asicParser.java:196)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:85)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <7828f40> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-9" daemon prio=5 tid=0x38274c20 nid=0x15c runnable [0x385df000..0
x385dfdc0]
at java.lang.Object.clone(Native Method)
at weblogic.utils.collections.NumericHashtable.clone(NumericHashtable.ja
va:267)
- locked <353a790> (a weblogic.utils.collections.NumericHashtable)
at weblogic.socket.NTSockegouxer.trigger(NTSockegouxer.java:107)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
edTrigger.java:205)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
er.java:199)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
0)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-8" daemon prio=5 tid=0x38273e10 nid=0x14b runnable [0x3859f000..0
x3859fdc0]
at oracle.jdbc.ttc7.MAREngine.unmarshalUB4(MAREngine.java:845)
at oracle.jdbc.ttc7.MAREngine.unmarshalSWORD(MAREngine.java:946)
at oracle.jdbc.ttc7.TTIoer.unmarshal(TTIoer.java:128)
at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:533)
at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:
643)
- locked <13bd83a8> (a oracle.jdbc.ttc7.TTC7Protocol)
at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.jav
a:1674)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStateme
nt.java:1870)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:737)
- locked <140e56f8> (a oracle.jdbc.driver.OracleStatement)
at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:6
88)
- locked <13bcc130> (a weblogic.jdbc.common.internal.ConnectionEnv)
at weblogic.common.internal.ResourceAllocator.trigger(ResourceAllocator.
java:1484)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(Schedul
edTrigger.java:205)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigg
er.java:199)
at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:6
0)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-7" daemon prio=5 tid=0x38271020 nid=0x164 runnable [0x3855f000..0
x3855fdc0]
at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
at java.lang.StringBuffer.append(StringBuffer.java:401)
- locked <140f8450> (a java.lang.StringBuffer)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:78)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <8ebc3e8> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-6" daemon prio=5 tid=0x38270190 nid=0x142 runnable [0x3851f000..0
x3851fdc0]
at java.lang.StringBuffer.<init>(StringBuffer.java:116)
at java.lang.StringBuffer.<init>(StringBuffer.java:104)
at com.xyz.king.common.DiplomatBasicParser.processTag(DiplomatBa
sicParser.java:154)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:72)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <9dab220> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-5" daemon prio=5 tid=0x3826f610 nid=0x14a runnable [0x384df000..0
x384dfdc0]
at java.lang.StringBuffer.expandCapacity(StringBuffer.java:202)
at java.lang.StringBuffer.append(StringBuffer.java:401)
- locked <140f84f8> (a java.lang.StringBuffer)
at com.xyz.king.common.DiplomatBasicParser.parse(DiplomatBasicPa
rser.java:91)
at com.xyz.king.go.Tuvking.getExacgoatchFormat(Tuvking.java:56)
at com.xyz.king.go.IndexerLocal.setExacgoatchKeys(IndexerLocal.j
ava:72)
at com.xyz.everest.integration.king.go.IndexerWLRMIImpl.setExact
MatchKeys(IndexerWLRMIImpl.java:68)
at com.xyz.everest.page.pageimport.PageImporter.createPageFromGx
ml(PageImporter.java:464)
at com.xyz.everest.page.pageimport.PageImporter.importSourcePage
(PageImporter.java:231)
at com.xyz.everest.page.pageimport.PageImporter.importPage(PageI
mporter.java:152)
at com.xyz.everest.page.PageManagerLocal.importPage(PageManagerL
ocal.java:340)
at com.xyz.everest.page.PageManagerWLRMIImpl.importPage(PageMana
gerWLRMIImpl.java:254)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssLocalizationRequest(RequestProcessor.java:168)
at com.xyz.everest.jobhandler.jobcreation.RequestProcessor.proce
ssRequest(RequestProcessor.java:65)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorLocal.addReq
uestToJob(JobCreatorLocal.java:89)
at com.xyz.everest.jobhandler.jobcreation.JobCreatorWLRMIImpl.ad
dRequestToJob(JobCreatorWLRMIImpl.java:41)
at com.xyz.everest.request.RequestHandlerLocal.submitRequest(Req
uestHandlerLocal.java:423)
at com.xyz.everest.request.RequestHandlerLocal.onMessage(Request
HandlerLocal.java:192)
at weblogic.jms.client.JMSMessageConsumer.run(JMSMessageConsumer.java:27
6)
at weblogic.jms.client.JMSSession.run(JMSSession.java:342)
at weblogic.jms.server.JMSServerSession.execute(JMSServerSession.java:44
- locked <84612a8> (a weblogic.jms.server.JMSServerSession)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
"ExecuteThread-4" daemon prio=5 tid=0x3826e820 nid=0x1fb waiting on monitor [0x3
849f000..0x3849fdc0]
at java.lang.Object.wait(Native Method)
- waiting on <2f03bc0> (a weblo -
I'm trying to troubleshoot a situation in which an WLS based application is
hanging on an HP system running UX 11.0. When the problem happens, the CPU
utilization on the box goes to 100% and the instance of WLS stops
responding. We had started the process and left running in the foreground
and tried generating a thread dump at the point of the hang with a kill -3
on the pid, but no data is produced. Anyone have any suggestions?
Thanks,
JHi.
What is the full version of your JDK?
If you haven't already done so you might want to look into tuning your HPUX
kernel as described in
http://edocs.bea.com/wls/platforms/hpux/index.html#hpux11
Does this occur randomly or regularly? Does this happen under high load? low
load? Is there any other way to characterize the circumstances for this hang?
Regards,
Michael
John Doe wrote:
I'm trying to troubleshoot a situation in which an WLS based application is
hanging on an HP system running UX 11.0. When the problem happens, the CPU
utilization on the box goes to 100% and the instance of WLS stops
responding. We had started the process and left running in the foreground
and tried generating a thread dump at the point of the hang with a kill -3
on the pid, but no data is produced. Anyone have any suggestions?
Thanks,
J--
Michael Young
Developer Relations Engineer
BEA Support -
Re: WLS 6.0 SP2 hangs due to many sockets in CLOSE_WAIT state
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000 platform.
Currently we are using running some stablity tests and noticing that there are
lot of sockets in close_wait state and handle count keeps going up and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay as suggested
in this newsgroup, and we are still noticing this problem. Does any body have
the same issue?. is this a know problem with weblogic http server?. and finally
any fixes or workarounds to this issue.
Thanks
Sogal.NBEA acknowledges this problem in 6.0 SP2 with iPlanet plug-in.
Solution that they recommend is to use 6.1 SP2 plug-in (they claim
full compatibility). Also, you may have to set KeepAliveEnabled to
false in obj.conf (the problem is in wrong pooling).
Hope it helps,
Bala
Robert Patrick <[email protected]> wrote in message news:<[email protected]>...
There are a couple of issues.
1.) You need to tune the machine running the web server and the machine
running WebLogic to make sure that it is configured appropriately for a
high-volume HTTP server. See
http://e-docs.bea.com/wls/platforms/sun/index.html for details on tuning
Solaris.
2.) I believe that there is a bug in the plugins in 6.0 where it is not
properly closing sockets. Try using the plugin from WLS 6.1 SP2...
Hope this helps,
Robert
Kevin Phillips wrote:
Tim Funk <[email protected]> wrote:
I am experiencing similar problems with WL 6.0 SP2 on Solaris 2.6.
We are already proxying all HTTP traffic through a
cluster of apache servers. Unfortuantely, the apache-WL
bridge seems to work so efficiently that our servers are
still flooded with open sockets in the TCP_CLOSE_WAIT state.
It seems to be bound by WebLogic's capacity to respond to
the requests in a speedy enough fashion.
Anybody have any suggestions?
Kevin
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because
it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000
platform.
Currently we are using running some stablity tests and noticing that
there are
lot of sockets in close_wait state and handle count keeps going up
and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay
as suggested
in this newsgroup, and we are still noticing this problem. Does any
body have
the same issue?. is this a know problem with weblogic http server?.
and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N -
WLS hang after java.lang.IllegalStateException: HttpSession is invalid occured
Hi, all:
I often got messages like below and server going to hang after got these message.
####<2004/6/15 PM time > <Error> <Kernel> <xxx.xxx.com.tw> <myserver> <ExecuteThread:
'18' for queue: 'default'> <> <> <000000> <ExecuteRequest failed>
java.lang.IllegalStateException: HttpSession is invalid
at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:162)
at weblogic.servlet.internal.session.SessionData.getValue(SessionData.java:134)
at weblogic.servlet.internal.ServletRequestImpl.getRemoteUser(ServletRequestImpl.java:814)
at weblogic.servlet.logging.CLFLogger.log(CLFLogger.java:60)
at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:293)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:670)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:851)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1636)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
I know 6.0 SP2 is stop-continued, but it's still production server before we upgrade
it.
did any one can told me what should I modify or set ?
Thanks for any response.Hi Eddy,
"Eddy Vina" <[email protected]> wrote in message news:3fbc46c2$[email protected]..
I get randomly in my application "java.lang.IllegalStateException: HttpSession
is invalid" exception thrown when I call getAttribute() method on a HttpSession
instance.
weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:410)
Any feedback to avoid this problem is greately appreciatedThis happens because getAttribute(...) is called on an invalidated
session. The session could have timed out or been invalidated
explicitly by the moment the call was made.
That may happen if you "cache" session objects.
Hope this helps.
Regards,
Slava Imeshev -
Console output not getting flushed - Causing server to hang - WLS 6.1 sp1
I am running WLServer 6.1 sp1 on Win 2000.
I start up the server from a Windows command prompt.
A web-app is deployed and some output is written to the console
The application functions correctly for a while and then stops
functioning. The browser keeps waiting for output. When I go to the console window
and hit the ENTER key a bunch of log statements that the app logged appear and
then the page on the browser also gets displayed. Seems like a problem with flushing
the output. Any help is appreciated.
Thanks
AnandYes. This is a Windows2000 problem. It doesn't happen on NT or Solaris. It
will often happen if you scroll the DOS window up to look at something in
the DOS window buffer and it gets cleared by pressing the enter key as you
point out.
Tom
"Anand Narayan" <[email protected]> wrote in message
news:[email protected]..
>
I am running WLServer 6.1 sp1 on Win 2000.
I start up the server from a Windows command prompt.
A web-app is deployed and some output is written to the console
The application functions correctly for a while and then stops
functioning. The browser keeps waiting for output. When I go to theconsole window
and hit the ENTER key a bunch of log statements that the app logged appearand
then the page on the browser also gets displayed. Seems like a problemwith flushing
the output. Any help is appreciated.
Thanks
Anand -
WebLogic 10.3.2.0 hanging at startup after "The server log file is opened."
Hi,
A WebLogic 10.3.2.0 server is hanging at startup. There are no error messages. The last command in the startup window is:
"The server log file <log file dest> is opened. All server side log events will be written to this file."
I think the next line should be:
"Security initializing using security realm realm."
Any ideas on what could be the issue? For instance what resources should be accessed at that point of time? There is sufficient space left on the (virtual machine) disk. The VM configured with 8GB memory. Could it be performance related still?
Following is written to the log file:
####<12.aug.2010 kl 09.47 CEST> <Info> <WebLogicServer> <oim> <> <Main Thread> <> <> <> <1281599254656> <BEA-000214> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.> ####<12.aug.2010 kl 09.47 CEST> <Notice> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255312> <BEA-170019> <The server log file ....logs\AdminServer.log is opened. All server side log events will be written to this file.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Log Management> <oim> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1281599255390> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Diagnostics> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599255671> <BEA-320001> <The ServerDebug service initialized successfully.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Store> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599256515> <BEA-280050> <Persistent store "WLS_DIAGNOSTICS" opened: directory="....s\domains\oim\servers\AdminServer\data\store\diagnostics" writePolicy="Disabled" blockSize=512 directIO=false driver="wlfileio2"> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "t3s" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "http" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "https" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257140> <BEA-002622> <The protocol "iiop" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "iiops" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldap" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257156> <BEA-002622> <The protocol "ldaps" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "cluster" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257187> <BEA-002622> <The protocol "clusters" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "snmp" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002622> <The protocol "admin" is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257218> <BEA-002624> <The administration protocol is "t3s" and is now configured.> ####<12.aug.2010 kl 09.47 CEST> <Info> <RJVM> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257468> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<12.aug.2010 kl 09.47 CEST> <Info> <Server> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599257687> <BEA-002609> <Channel Service initialized.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258000> <BEA-000406> <NTSocketMuxer was built on Jan 13 2005 17:47:03
####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000436> <Allocating 3 reader threads.> ####<12.aug.2010 kl 09.47 CEST> <Info> <Socket> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599258078> <BEA-000446> <Native IO Enabled.> ####<12.aug.2010 kl 09.47 CEST> <Info> <IIOP> <oim> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1281599259500> <BEA-002014> <IIOP subsystem enabled.>
Thanks!!tried both of these, still having same error as below:
<Sep 8, 2010 1:32:37 PM IST> <Critical> <Security> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.>
<Sep 8, 2010 1:32:37 PM IST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:959)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User weblogic2 javax.security.auth.login.FailedLoginException: [Security:090302]Authentication Failed: User weblogic2 denied
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:250)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Sep 8, 2010 1:32:37 PM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Sep 8, 2010 1:32:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Pls help me out ASAP... -
Connections not being released from jdbc pool on WLS 5.1 sp8
I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as shown in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.comHi Caren,
Weblogic doesn't close connections on "time-out". There are some reasons
for this. The most important one is that even if you have such a
functionality,
in case of a connection leak all the available connections can be trashed in
a matter of milliseconds, so it wouldn't help at all. Though, weblogic does
close leaked connection when they are garbage collected, but it's easy to
see
that it doesn't help a lot, too.
So you need to make sure that all the JDBC objects are closed properly,
for example like in this code:
try {
} finally {
try {resultSet.close();} catch (SQLException se) {}
try {preparedStatement.close();} catch (SQLException se) {}
try {connection.close();} catch (SQLException se) {}
Also it's possible that you simply don't have enough connection.
You could try to increase size of the pool.
Regards,
Slava Imeshev
"Karen Law" <[email protected]> wrote in message
news:[email protected]...
Closing the DB connections is important. But is there any parameters to be
set in the WebLogic configuration in order to release the connection whenit
hasn't been closed for a long time? Say, setting the connection timeout?
Many thx!
Karen
"Deyan D. Bektchiev" <[email protected]> wrote in message
news:[email protected]...
Do you close the DB connections in a finally block after you've finished
using them?
If not your application is leaking the connections and sometimes GC is
not able or does not free those in a timely manner.
--dejan
Anish Srivastava wrote:
I am using WLS 5.1 on RedHat Linux kernel 2.4
The database is oracle 8.1.6 and I am using the thin jdbc driver as
shown
in the config below.
weblogic.jdbc.connectionPool.bobePool=\
url=jdbc:oracle:thin:@localhost:1521:<sid>,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=10,\
maxCapacity=22,\
capacityIncrement=5,\
allowShrinking=true,\
shrinkPeriodMins=3,\
testConnsOnReserve=true,\
testTable=dual,\
refreshTestMinutes=5,\
props=user=<username>;password=<password>
The problem I am facing is that some connections remain active
after the SQL query has finished. The no. of open connections
keep on piling up till the limit of 18 connections is reached and
ultimately at that point weblogic hangs.
Has someone else faced this problem...and found a solution??
Regards,
Anish Srivastava
System Analyst
Baazee.com -
Start BI Services getting hang in obiee 11g
Hi Experts,
when I start the BI Service in obiee 11g in getting Hang, how could I resolve this.
SVR_GRP =
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=512m -XX:-UseSSE42Intr
insics
WLS Start Mode=Production
CLASSPATH=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\ext\jdbc\oracle\11g\ojdbc6dms.jar
;D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sys_manifest_classpath\weblog
ic_patch.jar;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sys_manifest_class
path\weblogic_patch.jar;C:\PROGRA~1\Java\JDK16~1.0_2\lib\tools.jar;D:\Oracle\MID
DLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server
\lib\weblogic.jar;D:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10
.3.3.0.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\Oracle\MI
DDLE~1\modules\ORGAPA~1.1/lib/ant-all.jar;D:\Oracle\MIDDLE~1\modules\NETSFA~1.0_
1/lib/ant-contrib.jar;D:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar
;D:\Oracle\Middleware\oracle_common\modules\oracle.dms_11.1.1\dms.jar;D:\Oracle\
Middleware\oracle_common\modules\oracle.jmx_11.1.1\jmxframework.jar;D:\Oracle\Mi
ddleware\oracle_common\modules\oracle.jmx_11.1.1\jmxspi.jar;D:\Oracle\Middleware
\oracle_common\modules\oracle.odl_11.1.1\ojdl.jar;D:\Oracle\MIDDLE~1\ORACLE~1\so
a\modules\commons-cli-1.1.jar;D:\Oracle\MIDDLE~1\ORACLE~1\soa\modules\oracle.soa
.mgmt_11.1.1\soa-infra-mgmt.jar;D:\Oracle\Middleware\Oracle_BI1\common\jlib\11.1
.2.0\ctg.jar;D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrf.jar;D:\Or
acle\MIDDLE~1\WLSERV~1.3\common\derby\lib\derbyclient.jar;D:\Oracle\MIDDLE~1\WLS
ERV~1.3\server\lib\xqrl.jar
PATH=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\native;D:\Oracle\MIDDLE~1
\patch_ocp353\profiles\default\native;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\nativ
e\win\x64;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;D:\Oracle\MIDDLE~1\modules\OR
GAPA~1.1\bin;C:\PROGRA~1\Java\JDK16~1.0_2\jre\bin;C:\PROGRA~1\Java\JDK16~1.0_2\b
in;D:\app\product\11.2.0\dbhome_1\bin;C:\Program Files (x86)\Dell\SysMgt\RAC5;C:
\Program Files (x86)\Dell\SysMgt\oma\bin;C:\Program Files (x86)\Dell\SysMgt\idra
c;C:\Program Files\Intel\DMIX;D:\Oracle\Middleware\Oracle_BI1\bin;D:\Oracle\Midd
leware\Oracle_BI1\opmn\bin;D:\Oracle\Middleware\Oracle_BI1\opmn\lib;D:\Oracle\Mi
ddleware\Oracle_BI1\perl\bin;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\x64
\oci920_8
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b17, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK16~1.0_2\bin\java -server -Xms256m -Xmx512m -XX:MaxPermSi
ze=512m -XX:-UseSSE42Intrinsics -Dweblogic.Name=AdminServer -Djava.security.poli
cy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.Producti
onModeEnabled=true -Doracle.home=D:\Oracle\Middleware\Oracle_BI1 -da -Dplatform
.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\ser
ver -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracl
e\MIDDLE~1\USER_P~1\domains\BIFOUN~1 -Dcommon.components.home=D:\Oracle\MIDDLE~1
\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commo
ns.logging.impl.Jdk14Logger -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\module
s\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\Oracle\MID
DLE~1\USER_P~1\domains\BIFOUN~1\config\FMWCON~1 -Doracle.server.config.dir=D:\Or
acle\MIDDLE~1\USER_P~1\domains\BIFOUN~1\config\FMWCON~1\servers\AdminServer -Dor
acle.security.jps.config=D:\Oracle\MIDDLE~1\USER_P~1\domains\BIFOUN~1\config\fmw
config\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dig
f.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\USER_P~1\domains\BIFOUN~1\config\FMWCO
N~1\carml -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\BIFOUN~1\c
onfig\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDL
E~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\o
racle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.biee.sear
ch.bisearchproperties=D:\Oracle\Middleware\Oracle_BI1\bifoundation\jee\BISearchC
onfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=true -Do
racle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHost
nameVerification=true -DEPM_ORACLE_HOME=D:\Oracle\Middleware\Oracle_BI1 -Doracle
.ecsf.crawl.mode.debug=true -Doracle.ecsf.security.service=oracle.biee.search.se
curity.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.sea
rch.services.BISearchServiceConfiguration -Dxdo.server.config.dir=D:\Oracle\Midd
leware\user_projects\domains\bifoundation_domain\config\bipublisher -DXDO_FONT_D
IR=D:\Oracle\Middleware\Oracle_BI1\common\fonts -Dorg.eclipse.emf.ecore.EPackag
e.Registry.INSTANCE=com.sigmadynamics.emf.util.SDEMFRegistry -Dweblogic.wsee.ski
p.async.response=true -Drtd.instanceName=RTD_AdminServer -Dem.oracle.home=D:\Ora
cle\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.disc
over=true -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToCon
sole=false -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default
\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\syse
xt_manifest_classpath -Dweblogic.management.username=Administrator -Dweblogic.ma
nagement.password=System12 weblogic.Server
<Mar 28, 2011 2:26:26 AM PDT> <Info> <WebLogicServer> <BEA-000377> <Starting Web
Logic Server with Java HotSpot(TM) 64-Bit Server VM Version 17.0-b17 from Sun Mi
crosystems Inc.>
<Mar 28, 2011 2:26:26 AM PDT> <Info> <Management> <BEA-141107> <Version: WebLogi
c Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 >
<Mar 28, 2011 2:26:29 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server sta
te changed to STARTING>
<Mar 28, 2011 2:26:29 AM PDT> <Info> <WorkManager> <BEA-002900> <Initializing se
lf-tuning thread pool>
<Mar 28, 2011 2:26:29 AM PDT> <Notice> <Log Management> <BEA-170019> <The server
log file D:\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers
\AdminServer\logs\AdminServer.log is opened. All server side log events will be
written to this file.>
Log file shows
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <WebLogicServer> <XTDBS1> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301304389287> <BEA-000000> <WebLogic Server "AdminServer" version:
WebLogic Server 10.3.3.0 Fri Apr 9 00:05:28 PDT 2010 1321401 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<Mar 28, 2011 2:26:29 AM PDT> <Notice> <Log Management> <XTDBS1> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301304389412> <BEA-170019> <The server log file D:\Oracle\Middleware\user_projects\domains\bifoundation_domain\servers\AdminServer\logs\AdminServer.log is opened. All server side log events will be written to this file.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Log Management> <XTDBS1> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1301304389427> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Diagnostics> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389521> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "t3" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "t3s" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "http" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "https" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "iiop" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "iiops" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "ldap" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "cluster" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389630> <BEA-002622> <The protocol "clusters" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389646> <BEA-002622> <The protocol "snmp" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389646> <BEA-002622> <The protocol "admin" is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389646> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <RJVM> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389677> <BEA-000570> <Network Configuration for Channel "AdminServer"
Listen Address :7001
Public Address N/A
Http Enabled true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Server> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389724> <BEA-002609> <Channel Service initialized.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Socket> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389739> <BEA-000406> <NTSocketMuxer was built on Jan 24 2006 20:40:35
>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Socket> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389762> <BEA-000436> <Allocating 3 reader threads.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <Socket> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389778> <BEA-000446> <Native IO Enabled.>
####<Mar 28, 2011 2:26:29 AM PDT> <Info> <IIOP> <XTDBS1> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1301304389918> <BEA-002014> <IIOP subsystem enabled.>
Thanks,
Balaa...balaa,
can you help in starting the bi services?
Thanks
Maybe you are looking for
-
Can someone help me with a problem of parsing an XML file?
Hello, I'm having some problems parsing an xml file. I get a SAXNotSupportedException when setting a property value. Here is the piece of code where I have the problem: SAXParserFactory spf = SAXParserFactory.newInstance(); spf.setNamespaceAware(true
-
Hi, I have the ORDERS05 extended . I have extended the segment E1EDKT2 with the custom segment. I will be having the multiple lines to be appeded into the custom segment How can i do that ? READ TABLE dint_edidd WITH KEY segnam = 'E1EDKT2'. lv_tabix
-
Hi wanna display as 3 in table row
Hi, Still in categories and subcategories: my below component is displaying the code as tree menu: <cfcomponent name="Categories"> <cffunction name="getCats"> <!--- Parent ID ---> <cfargument name="parent" type="numeric"> <!--- Query for Children of
-
Making a GUI take precedence over other threads.
Hi, Basically what I'm trying to do is display a message on screen after a user has clicked a button that starts a thread which conducts a Bluetooth device search. This message needs to say "please wait" or "discovery in progress" or something and wi
-
How is your cube set up to be maintained?
Hi, I, have a cube that grows with aproximately 50,000 rows per week, with the total of around 5 million for the entire cube. I created a script from AWM to maintain it where it was set to aggregate only for incoming values. From the xml_load_log tab