Gotta love those IBM JDK stack traces . . .
Interesting comment: "We have deployed the same application successfully on
Solaris 6 and Winnt without any problems. which leads me to believe that it is
not my application code."
Of course the same facts would lead _me_ to believe it's not JRun either, since
the same byte codes are running on all three platforms. <grin/>
So, looks like we're in luck: based on the stack trace, I'd say JRun and your
code (well, your code may have a problem, but we'll see) are in the clear.
Either the JVM or something on your HP box's network is the culprit. I can
point in the direction of the problem, but your knowledge of the environment
will have to fill in the final pieces.
Am I correct in thinking that you have the free version of JRun running here?
If you have a license, check your event log to see if it's being accepted,
because it sure looks like you're limited to 5 concurrent requests. Which
raises a flag -- if you are load testing an app with only 5 concurrent requests,
the performance is going to stink.
So what are the 5 request handler threads that are actually doing anything
(other than sitting in a conditional wait because the 5 concurrent requests
limitation is in effect)?? Let's see --- jcp-0, jcp-5, jcp-9, jcp-10, and
jcp-15 are all reading input from an HttpURLConnection that was opened by your
com.i2.scm.reqBean:
"jcp-0" (TID:0x80033448, sys_thread_t:0x3076b260, state:R, native ID:0x90a)
prio=3D5
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java(Compiled Code))
at java.io.BufferedInputStream.fill(BufferedInputStream.java(Compiled Code))
at java.io.BufferedInputStream.read1(BufferedInputStream.java:231)
at java.io.BufferedInputStream.read(BufferedInputStream.java:287)
at java.io.FilterInputStream.read(FilterInputStream.java:120)
at java.io.PushbackInputStream.read(PushbackInputStream.java:170)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java(Compiled Code))
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.jav
a:466)
at com.i2.scm.reqBean.copyURLToString(reqBean.java:72)
at com.i2.scm.reqBean.getPage(reqBean.java:25)
at jsp.i2.scp_problems._jspService(scp_problems.java:234)
at com.livesoftware.jsp.HttpJSPServlet.service(HttpJSPServlet.java:31)
at com.livesoftware.jsp.JSPServlet.service(JSPServlet.java:129)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:840)
at com.livesoftware.jrun.JRun.runServlet(JRun.java:321)
at com.livesoftware.jrun.JRunGeneric.handleConnection(JRunGeneric.java:116)
at
com.livesoftware.jrun.service.proxy.JRunProxyServiceHandler.handleRequest(JRunPr
oxyServiceHandler.java(Compiled Code))
at
com.livesoftware.jrun.service.ThreadConfigHandler.run(ThreadConfigHandler.java:9
6)
You can further check out these threads and the objects they're waiting on
(using the Thread Identifiers table at the bottom to correlate):
jcp-0 . . .
> ident b "jcp-0" (0x3076b260) ee 0x3076b198
. . . is reading a BufferedInputStream through an HttpURLConnection
> sun.net.www.protocol.http.HttpURLConnection@809F00D8/809F00E0
> locknflags 000b0000 Flat locked by threadIdent b. Entrycount 1
> java.io.BufferedInputStream@809F17A8/809F17B0
> locknflags 000b0000 Flat locked by threadIdent b. Entrycount 1
Ditto for his pals, 5, 9, 10, 15.
So you've got a potential licensing problem, a slow network and/or hung JVM, and
a situation where you might want to reconsider how often you use that bean to
make an HTTP request.
Scott Stirling
> -----Original Message-----
> From: Naveen Shankar [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 22, 2000 8:45 PM
>
>
> ----- Original Message -----
> From: "Naveen Shankar" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, September 22, 2000 5:35 PM
> Subject: Jrun Lockup on AIX 4.3
>
>
> > Configuration:
> > AIX 4.3
> > Jrun2.3.3 build 157
> > Apache 1.3.9
> > jdk1.2.2
> >
> > Our Jar files have been compiled with jdk1.2.1 on solaris.
> >
> > Problem: If I execute a certain number of requests to my application, I
> see
> > the following
> >
> > 1. The responses stop after sometime. But I still see the requests going
> in
> > to my servlet .
> >
> > 2. If I continue pounding on this servlet, the requests stop going in.
> Jrun
> > locks up and I cannot even execute the SimpleServlet after that.
> >
> > We have deployed the same application successfully on Solaris 6 and Winnt
> > without any problems. which leads me to believe that it is not my
> > application code.
> >
> > Has anyone ever seen thsi kind of problem before?? Any suggestions would
> be
> > appreciated.
> >
> > Thanks
> > Naveen
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
