By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,496 Members | 1,517 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,496 IT Pros & Developers. It's quick & easy.

Client and Server process both seems to be sleeping forever

P: n/a
I joined a company recently and they have a java program which hangs
(does nothing) after a while. This is no way consistent. It could
succeed quite a few times and can fail a few other times. There is no
consistency when it fails.

Could anyone here shed some light on how to debug/resolve the issue. I
guess IBM looked at the issue and were not able to pinpoint where the
issue is.

When the program hangs and when force the DB2 application (Agentid),
the java program dies. This seems, the java program is waiting for
DB2. But I am not sure what DB2 is waiting on. The process trace
yields nothing. Accoriding to the java guys, they have instrumented
the code very weel and there is no way the problem is in the java
code.

The server is DB2 UDB 7.1.0.9 EEE (db is spread across 2 servers with
16 partitions per server) on AIX 5.2

On tracing (truss) both the client side process and server side
process seems to be sleeping.

% truss -ael -p 1871902
psargs: db2agent (FRAUD) 16
1994855: __semop(0, 0x00000000, 0) (sleeping...)

% truss -ael -p 7262272
psargs: db2agntp (FRAUD) 16
8110133: __semop(0, 0x00000000, 0) (sleeping...)
This is the snapshot for that agent at the pending and co-ordinating
node.

% db2 get snapshot for application agentid 1012555 global
--This shows the following
Subsection number = 1
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 31378

All other "Subsection status" were 'Completed'
ex,
Subsection number = 1
Subsection node number = 15
Subsection status = Completed
Execution elapsed time (seconds) = 0
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
% db2 get snapshot for application agentid 1012555 at node 16
Application Snapshot

Application handle = 1012555
Application status = Pending remote request
Status change time = Not Collected
Application code page = 819
Application country code = 1
DUOW correlation token = *N16.xxxx.xxxx
Application name = java
Application ID = *N16.xxxx.xxxxx
TP Monitor client user ID =
TP Monitor client workstation name =
TP Monitor client application name =
TP Monitor client accounting string =

Sequence number = 0001
Connection request start timestamp = 06-10-2004
07:33:53.313339
Connect request completion timestamp = 06-10-2004
07:33:53.355625
Application idle time =
Authorization ID = xxxxx
Client login ID = xxxxx
Configuration NNAME of client =
Client database manager product ID = SQL07029
Process ID of client application = 6864934
Platform of client application = AIX
Communication protocol of client = Local Client

Inbound communication address = *N16.xxxx

Database name = DEVP
Database path =
/db/xxxx/NODE0016/SQL00001/
Client database alias = DEVP
Input database alias =
Last reset timestamp =
Snapshot timestamp = 06-10-2004
17:16:31.231795
The highest authority level granted =
Direct CONNECT authority
Direct LOAD authority
Coordinating node number = 16
Current node number = 16
Coordinator agent process or thread ID = 1871902
Agents stolen = 1064
Agents waiting on locks = 0
Maximum associated agents = 6
Priority at which application agents work = 0
Priority type = Dynamic

Locks held by application = 2
Lock waits since connect = 0
Time application waited on locks (ms) = 0
Deadlocks detected = 0
Lock escalations = 0
Exclusive lock escalations = 0
Number of Lock Timeouts since connected = 0
Total time UOW waited on locks (ms) = Not Collected

Total sorts = 0
Total sort time (ms) = 0
Total sort overflows = 0

Data pages copied to extended storage = 0
Index pages copied to extended storage = 0
Data pages copied from extended storage = 0
Index pages copied from extended storage = 0
Buffer pool data logical reads = 48620
Buffer pool data physical reads = 12379
Buffer pool data writes = 2
Buffer pool index logical reads = 1040311
Buffer pool index physical reads = 1461
Buffer pool index writes = 0
Total buffer pool read time (ms) = 129148
Total buffer pool write time (ms) = 1
Time waited for prefetch (ms) = 0
Direct reads = 0
Direct writes = 0
Direct read requests = 0
Direct write requests = 0
Direct reads elapsed time (ms) = 0
Direct write elapsed time (ms) = 0
Number of SQL requests since last commit = 7
Commit statements = 6708
Rollback statements = 0
Dynamic SQL statements attempted = 338671
Static SQL statements attempted = 6708
Failed statement operations = 0
Select SQL statements executed = 2
Update/Insert/Delete statements executed = 338662
DDL statements executed = 0
Internal automatic rebinds = 0
Internal rows deleted = 0
Internal rows inserted = 0
Internal rows updated = 0
Internal commits = 1
Internal rollbacks = 0
Internal rollbacks due to deadlock = 0
Binds/precompiles attempted = 0
Rows deleted = 0
Rows inserted = 1
Rows updated = 24309
Rows selected = 1
Rows read = 48619
Rows written = 24310
UOW log space used (Bytes) = Not Collected
Previous UOW completion timestamp = Not Collected
Elapsed time of last completed uow (sec.ms)= Not Collected
UOW start timestamp = Not Collected
UOW stop timestamp = Not Collected
UOW completion status = Not Collected
Open remote cursors = 0
Open remote cursors with blocking = 0
Rejected Block Remote Cursor requests = 0
Accepted Block Remote Cursor requests = 2
Open local cursors = 0
Open local cursors with blocking = 0

Total User CPU Time used by agent (s) = 237.640000
Total System CPU Time used by agent (s) = 105.770000
Host execution elapsed time = 0.014564
Package cache lookups = 342034
Package cache inserts = 5
Application section lookups = 673978
Application section inserts = 6
Catalog cache lookups = 0
Catalog cache inserts = 0
Catalog cache overflows = 0
Catalog cache heap full = 0

Most recent operation = Execute
Most recent operation start timestamp = 06-10-2004
08:21:34.665360
Most recent operation stop timestamp =
Agents associated with the application = 2

Number of hash joins = 0
Number of hash loops = 0
Number of hash join overflows = 0
Number of small hash join overflows = 0

Statement type = Dynamic SQL Statement
Statement = Execute
Section number = 5
Application creator = NULLID
Package name = SQLLC200
Cursor name = SQLCUR5
Statement node number = 16
Statement start timestamp = 06-10-2004
08:21:34.665360
Statement stop timestamp =
Elapsed time of last completed stmt(sec.ms)= 0.000000
Total user CPU time = 0.000000
Total system CPU time = 0.000000
SQL compiler cost estimate in timerons = 52
SQL compiler cardinality estimate = 1
Degree of parallelism requested = 1
Number of agents working on statement = 1
Number of subagents created for statement = 1
Statement sorts = 0
Total sort time = 0
Sort overflows = 0
Rows read = 0
Rows written = 0
Rows deleted = 0
Rows updated = 0
Rows inserted = 0
Rows fetched = 0
Blocking cursor = NO
Dynamic SQL statement text:
update table24 set last_used_dt=? where loc=?
Subsection number = 0
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 32097
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
Current number of tablequeue buffers overflowed = 0
Total number of tablequeue buffers overflowed = 0
Maximum number of tablequeue buffers overflowed = 0
Rows received on tablequeues = 0
Rows sent on tablequeues = 0
Rows read = 0
Rows written = 0
Number of agents working on subsection = 1

Agent process/thread ID = 1871902

Node number = 16
Agent process/thread ID = 1871902
Agent process/thread ID = 7262272
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
From a general view of point, I never see any Java application can driver db
server crazy (I mean the CPU can't be used so well, compare with C/C++
applications or sql scripts). For your scenario, I don't think people here
can help you with this information.
"Prince Kumar" <gs**@yahoo.com> wrote in message
news:62*************************@posting.google.co m...
I joined a company recently and they have a java program which hangs
(does nothing) after a while. This is no way consistent. It could
succeed quite a few times and can fail a few other times. There is no
consistency when it fails.

Could anyone here shed some light on how to debug/resolve the issue. I
guess IBM looked at the issue and were not able to pinpoint where the
issue is.

When the program hangs and when force the DB2 application (Agentid),
the java program dies. This seems, the java program is waiting for
DB2. But I am not sure what DB2 is waiting on. The process trace
yields nothing. Accoriding to the java guys, they have instrumented
the code very weel and there is no way the problem is in the java
code.

The server is DB2 UDB 7.1.0.9 EEE (db is spread across 2 servers with
16 partitions per server) on AIX 5.2

On tracing (truss) both the client side process and server side
process seems to be sleeping.

% truss -ael -p 1871902
psargs: db2agent (FRAUD) 16
1994855: __semop(0, 0x00000000, 0) (sleeping...)

% truss -ael -p 7262272
psargs: db2agntp (FRAUD) 16
8110133: __semop(0, 0x00000000, 0) (sleeping...)
This is the snapshot for that agent at the pending and co-ordinating
node.

% db2 get snapshot for application agentid 1012555 global
--This shows the following
Subsection number = 1
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 31378

All other "Subsection status" were 'Completed'
ex,
Subsection number = 1
Subsection node number = 15
Subsection status = Completed
Execution elapsed time (seconds) = 0
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
% db2 get snapshot for application agentid 1012555 at node 16
Application Snapshot

Application handle = 1012555
Application status = Pending remote request
Status change time = Not Collected
Application code page = 819
Application country code = 1
DUOW correlation token = *N16.xxxx.xxxx
Application name = java
Application ID = *N16.xxxx.xxxxx
TP Monitor client user ID =
TP Monitor client workstation name =
TP Monitor client application name =
TP Monitor client accounting string =

Sequence number = 0001
Connection request start timestamp = 06-10-2004
07:33:53.313339
Connect request completion timestamp = 06-10-2004
07:33:53.355625
Application idle time =
Authorization ID = xxxxx
Client login ID = xxxxx
Configuration NNAME of client =
Client database manager product ID = SQL07029
Process ID of client application = 6864934
Platform of client application = AIX
Communication protocol of client = Local Client

Inbound communication address = *N16.xxxx

Database name = DEVP
Database path =
/db/xxxx/NODE0016/SQL00001/
Client database alias = DEVP
Input database alias =
Last reset timestamp =
Snapshot timestamp = 06-10-2004
17:16:31.231795
The highest authority level granted =
Direct CONNECT authority
Direct LOAD authority
Coordinating node number = 16
Current node number = 16
Coordinator agent process or thread ID = 1871902
Agents stolen = 1064
Agents waiting on locks = 0
Maximum associated agents = 6
Priority at which application agents work = 0
Priority type = Dynamic

Locks held by application = 2
Lock waits since connect = 0
Time application waited on locks (ms) = 0
Deadlocks detected = 0
Lock escalations = 0
Exclusive lock escalations = 0
Number of Lock Timeouts since connected = 0
Total time UOW waited on locks (ms) = Not Collected

Total sorts = 0
Total sort time (ms) = 0
Total sort overflows = 0

Data pages copied to extended storage = 0
Index pages copied to extended storage = 0
Data pages copied from extended storage = 0
Index pages copied from extended storage = 0
Buffer pool data logical reads = 48620
Buffer pool data physical reads = 12379
Buffer pool data writes = 2
Buffer pool index logical reads = 1040311
Buffer pool index physical reads = 1461
Buffer pool index writes = 0
Total buffer pool read time (ms) = 129148
Total buffer pool write time (ms) = 1
Time waited for prefetch (ms) = 0
Direct reads = 0
Direct writes = 0
Direct read requests = 0
Direct write requests = 0
Direct reads elapsed time (ms) = 0
Direct write elapsed time (ms) = 0
Number of SQL requests since last commit = 7
Commit statements = 6708
Rollback statements = 0
Dynamic SQL statements attempted = 338671
Static SQL statements attempted = 6708
Failed statement operations = 0
Select SQL statements executed = 2
Update/Insert/Delete statements executed = 338662
DDL statements executed = 0
Internal automatic rebinds = 0
Internal rows deleted = 0
Internal rows inserted = 0
Internal rows updated = 0
Internal commits = 1
Internal rollbacks = 0
Internal rollbacks due to deadlock = 0
Binds/precompiles attempted = 0
Rows deleted = 0
Rows inserted = 1
Rows updated = 24309
Rows selected = 1
Rows read = 48619
Rows written = 24310
UOW log space used (Bytes) = Not Collected
Previous UOW completion timestamp = Not Collected
Elapsed time of last completed uow (sec.ms)= Not Collected
UOW start timestamp = Not Collected
UOW stop timestamp = Not Collected
UOW completion status = Not Collected
Open remote cursors = 0
Open remote cursors with blocking = 0
Rejected Block Remote Cursor requests = 0
Accepted Block Remote Cursor requests = 2
Open local cursors = 0
Open local cursors with blocking = 0

Total User CPU Time used by agent (s) = 237.640000
Total System CPU Time used by agent (s) = 105.770000
Host execution elapsed time = 0.014564
Package cache lookups = 342034
Package cache inserts = 5
Application section lookups = 673978
Application section inserts = 6
Catalog cache lookups = 0
Catalog cache inserts = 0
Catalog cache overflows = 0
Catalog cache heap full = 0

Most recent operation = Execute
Most recent operation start timestamp = 06-10-2004
08:21:34.665360
Most recent operation stop timestamp =
Agents associated with the application = 2

Number of hash joins = 0
Number of hash loops = 0
Number of hash join overflows = 0
Number of small hash join overflows = 0

Statement type = Dynamic SQL Statement
Statement = Execute
Section number = 5
Application creator = NULLID
Package name = SQLLC200
Cursor name = SQLCUR5
Statement node number = 16
Statement start timestamp = 06-10-2004
08:21:34.665360
Statement stop timestamp =
Elapsed time of last completed stmt(sec.ms)= 0.000000
Total user CPU time = 0.000000
Total system CPU time = 0.000000
SQL compiler cost estimate in timerons = 52
SQL compiler cardinality estimate = 1
Degree of parallelism requested = 1
Number of agents working on statement = 1
Number of subagents created for statement = 1
Statement sorts = 0
Total sort time = 0
Sort overflows = 0
Rows read = 0
Rows written = 0
Rows deleted = 0
Rows updated = 0
Rows inserted = 0
Rows fetched = 0
Blocking cursor = NO
Dynamic SQL statement text:
update table24 set last_used_dt=? where loc=?
Subsection number = 0
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 32097
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
Current number of tablequeue buffers overflowed = 0
Total number of tablequeue buffers overflowed = 0
Maximum number of tablequeue buffers overflowed = 0
Rows received on tablequeues = 0
Rows sent on tablequeues = 0
Rows read = 0
Rows written = 0
Number of agents working on subsection = 1

Agent process/thread ID = 1871902

Node number = 16
Agent process/thread ID = 1871902
Agent process/thread ID = 7262272

Nov 12 '05 #2

P: n/a
What I am interested in is, whether anyone faced such an issue and how
they traced the root cause. As I mentioned the os leel trace did not
provide any information. I am trying to identify, what resource the
DB2 agent/process is waiting for?

Thanks,
Prince.

"Fan Ruo Xin" <fa*****@sbcglobal.net> wrote in message news:<QG**********************@newssvr28.news.prod igy.com>...
From a general view of point, I never see any Java application can driver db
server crazy (I mean the CPU can't be used so well, compare with C/C++
applications or sql scripts). For your scenario, I don't think people here
can help you with this information.
"Prince Kumar" <gs**@yahoo.com> wrote in message
news:62*************************@posting.google.co m...
I joined a company recently and they have a java program which hangs
(does nothing) after a while. This is no way consistent. It could
succeed quite a few times and can fail a few other times. There is no
consistency when it fails.

Could anyone here shed some light on how to debug/resolve the issue. I
guess IBM looked at the issue and were not able to pinpoint where the
issue is.

When the program hangs and when force the DB2 application (Agentid),
the java program dies. This seems, the java program is waiting for
DB2. But I am not sure what DB2 is waiting on. The process trace
yields nothing. Accoriding to the java guys, they have instrumented
the code very weel and there is no way the problem is in the java
code.

The server is DB2 UDB 7.1.0.9 EEE (db is spread across 2 servers with
16 partitions per server) on AIX 5.2

On tracing (truss) both the client side process and server side
process seems to be sleeping.

% truss -ael -p 1871902
psargs: db2agent (FRAUD) 16
1994855: __semop(0, 0x00000000, 0) (sleeping...)

% truss -ael -p 7262272
psargs: db2agntp (FRAUD) 16
8110133: __semop(0, 0x00000000, 0) (sleeping...)
This is the snapshot for that agent at the pending and co-ordinating
node.

% db2 get snapshot for application agentid 1012555 global
--This shows the following
Subsection number = 1
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 31378

All other "Subsection status" were 'Completed'
ex,
Subsection number = 1
Subsection node number = 15
Subsection status = Completed
Execution elapsed time (seconds) = 0
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
% db2 get snapshot for application agentid 1012555 at node 16
Application Snapshot

Application handle = 1012555
Application status = Pending remote request
Status change time = Not Collected
Application code page = 819
Application country code = 1
DUOW correlation token = *N16.xxxx.xxxx
Application name = java
Application ID = *N16.xxxx.xxxxx
TP Monitor client user ID =
TP Monitor client workstation name =
TP Monitor client application name =
TP Monitor client accounting string =

Sequence number = 0001
Connection request start timestamp = 06-10-2004
07:33:53.313339
Connect request completion timestamp = 06-10-2004
07:33:53.355625
Application idle time =
Authorization ID = xxxxx
Client login ID = xxxxx
Configuration NNAME of client =
Client database manager product ID = SQL07029
Process ID of client application = 6864934
Platform of client application = AIX
Communication protocol of client = Local Client

Inbound communication address = *N16.xxxx

Database name = DEVP
Database path =
/db/xxxx/NODE0016/SQL00001/
Client database alias = DEVP
Input database alias =
Last reset timestamp =
Snapshot timestamp = 06-10-2004
17:16:31.231795
The highest authority level granted =
Direct CONNECT authority
Direct LOAD authority
Coordinating node number = 16
Current node number = 16
Coordinator agent process or thread ID = 1871902
Agents stolen = 1064
Agents waiting on locks = 0
Maximum associated agents = 6
Priority at which application agents work = 0
Priority type = Dynamic

Locks held by application = 2
Lock waits since connect = 0
Time application waited on locks (ms) = 0
Deadlocks detected = 0
Lock escalations = 0
Exclusive lock escalations = 0
Number of Lock Timeouts since connected = 0
Total time UOW waited on locks (ms) = Not Collected

Total sorts = 0
Total sort time (ms) = 0
Total sort overflows = 0

Data pages copied to extended storage = 0
Index pages copied to extended storage = 0
Data pages copied from extended storage = 0
Index pages copied from extended storage = 0
Buffer pool data logical reads = 48620
Buffer pool data physical reads = 12379
Buffer pool data writes = 2
Buffer pool index logical reads = 1040311
Buffer pool index physical reads = 1461
Buffer pool index writes = 0
Total buffer pool read time (ms) = 129148
Total buffer pool write time (ms) = 1
Time waited for prefetch (ms) = 0
Direct reads = 0
Direct writes = 0
Direct read requests = 0
Direct write requests = 0
Direct reads elapsed time (ms) = 0
Direct write elapsed time (ms) = 0
Number of SQL requests since last commit = 7
Commit statements = 6708
Rollback statements = 0
Dynamic SQL statements attempted = 338671
Static SQL statements attempted = 6708
Failed statement operations = 0
Select SQL statements executed = 2
Update/Insert/Delete statements executed = 338662
DDL statements executed = 0
Internal automatic rebinds = 0
Internal rows deleted = 0
Internal rows inserted = 0
Internal rows updated = 0
Internal commits = 1
Internal rollbacks = 0
Internal rollbacks due to deadlock = 0
Binds/precompiles attempted = 0
Rows deleted = 0
Rows inserted = 1
Rows updated = 24309
Rows selected = 1
Rows read = 48619
Rows written = 24310
UOW log space used (Bytes) = Not Collected
Previous UOW completion timestamp = Not Collected
Elapsed time of last completed uow (sec.ms)= Not Collected
UOW start timestamp = Not Collected
UOW stop timestamp = Not Collected
UOW completion status = Not Collected
Open remote cursors = 0
Open remote cursors with blocking = 0
Rejected Block Remote Cursor requests = 0
Accepted Block Remote Cursor requests = 2
Open local cursors = 0
Open local cursors with blocking = 0

Total User CPU Time used by agent (s) = 237.640000
Total System CPU Time used by agent (s) = 105.770000
Host execution elapsed time = 0.014564
Package cache lookups = 342034
Package cache inserts = 5
Application section lookups = 673978
Application section inserts = 6
Catalog cache lookups = 0
Catalog cache inserts = 0
Catalog cache overflows = 0
Catalog cache heap full = 0

Most recent operation = Execute
Most recent operation start timestamp = 06-10-2004
08:21:34.665360
Most recent operation stop timestamp =
Agents associated with the application = 2

Number of hash joins = 0
Number of hash loops = 0
Number of hash join overflows = 0
Number of small hash join overflows = 0

Statement type = Dynamic SQL Statement
Statement = Execute
Section number = 5
Application creator = NULLID
Package name = SQLLC200
Cursor name = SQLCUR5
Statement node number = 16
Statement start timestamp = 06-10-2004
08:21:34.665360
Statement stop timestamp =
Elapsed time of last completed stmt(sec.ms)= 0.000000
Total user CPU time = 0.000000
Total system CPU time = 0.000000
SQL compiler cost estimate in timerons = 52
SQL compiler cardinality estimate = 1
Degree of parallelism requested = 1
Number of agents working on statement = 1
Number of subagents created for statement = 1
Statement sorts = 0
Total sort time = 0
Sort overflows = 0
Rows read = 0
Rows written = 0
Rows deleted = 0
Rows updated = 0
Rows inserted = 0
Rows fetched = 0
Blocking cursor = NO
Dynamic SQL statement text:
update table24 set last_used_dt=? where loc=?
Subsection number = 0
Subsection node number = 16
Subsection status = Executing
Execution elapsed time (seconds) = 32097
Total user CPU time (sec.ms) = 0.000000
Total system CPU time (sec.ms) = 0.000000
Current number of tablequeue buffers overflowed = 0
Total number of tablequeue buffers overflowed = 0
Maximum number of tablequeue buffers overflowed = 0
Rows received on tablequeues = 0
Rows sent on tablequeues = 0
Rows read = 0
Rows written = 0
Number of agents working on subsection = 1

Agent process/thread ID = 1871902

Node number = 16
Agent process/thread ID = 1871902
Agent process/thread ID = 7262272

Nov 12 '05 #3

P: n/a
gs**@yahoo.com (Prince Kumar) wrote in message news:<62*************************@posting.google.c om>...
What I am interested in is, whether anyone faced such an issue and how
they traced the root cause. As I mentioned the os leel trace did not
provide any information. I am trying to identify, what resource the
DB2 agent/process is waiting for?

Thanks,
Prince.


Are you by chance using an older version of Java? About a year ago we
faced some "hanging" problems that were completely intermittent. We
were also using version 7 (not EEE, however) on an AIX server. After
many long calls to support and tons of traces, IBM hypothesized that
our problem was due to the JVM's garbage collection. While we never
had definitive proof that it was garbage collection, upgrading to the
next level of Java solved our hang problem.

Evan
Nov 12 '05 #4

P: n/a
Evan,

Thanks for the info.

I had the impression that the program is using JRE 1.3.1. It may also
possibe that the program is using 1.1.8. I will confirm this with the
group.

Also, when I kill the session from DB2 side Java immediately gets
notified and dies. But, if I kill the client program (java program),
the db2 session still hangs there.

I have the client (java program) runs locally on the same machine as
the db server.

Thanks,

es********@hotmail.com (Evan Smith) wrote in message news:<23**************************@posting.google. com>...
gs**@yahoo.com (Prince Kumar) wrote in message news:<62*************************@posting.google.c om>...
What I am interested in is, whether anyone faced such an issue and how
they traced the root cause. As I mentioned the os leel trace did not
provide any information. I am trying to identify, what resource the
DB2 agent/process is waiting for?

Thanks,
Prince.


Are you by chance using an older version of Java? About a year ago we
faced some "hanging" problems that were completely intermittent. We
were also using version 7 (not EEE, however) on an AIX server. After
many long calls to support and tons of traces, IBM hypothesized that
our problem was due to the JVM's garbage collection. While we never
had definitive proof that it was garbage collection, upgrading to the
next level of Java solved our hang problem.

Evan

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.