vani.as@rsys.com (Vani) writes:

A. Because doing so makes the conversation harder to read.
Q. Why should I not top-post?

Please do not top post. Rest of the message re-ordered.

> Paul Pluzhnikov wrote:
> >
> > There could be any number of reasons (most likely to least likely):
> > - a bug in your Java code
> > - a bug in JVM
> > - a bug in libpthread
> > - a bug in the kernel

> I eliminated the first two possibility by checking my application
> through pure c/c++ program.

You can *never* prove absence of bugs by testing, only their presence.

> I removed the Java interface and called C++ part directly.

In so doing, you've constructed an entirely different program,
which may still be as buggy as the original, but the bug simply
does not show up.

> It works properly even for 100 threads on AIX 5.1

It is *very* often that application bugs are discovered when porting
(or even just moving) from one OS to the next. The application
should always be your first suspect.

> BUT on 5.2 OS even
> for 2 threads it just hangs with CPU utilization stuck at around 50 %.

Attach to it with 'dbx', find where all the threads are
('thread current 1; where; thread current 2; where; ...)

From that info you (or someone else here) could be able to tell you more.

> Is there any known thread contention problem on OS 5.2.Any patches
> available

Don't know.

Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.