Hey Sean, Are you using RMI also? Vaughn Bullard Hey Software/Javant Software Inc. -----Original Message----- From: madhu [mailto:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 1:55 PM To: [EMAIL PROTECTED] Subject: [JRun-Talk] RE: JRun 2.3.3 dies aperiodically once or twice a day Hi!! It may be that the customer starts the Jrun from a shell and when he closes the shell , JRUN goes down. Start the Jrun with nohup command, nohup ./jsmctl start That should solve.. Madhu -----Original Message----- From: Sean Lim [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 17, 2000 8:51 PM To: [EMAIL PROTECTED] Subject: JRun 2.3.3 dies aperiodically once or twice a day Hi, Our customer has a problem using JRun 2.3.3 on AIX . Details are below ; Machine: RS6000H70(4CPU) OS: AIX 4.3.3 JRun 2.3.3 build 157 Unlimited JDK: J2RE 1.2.2 IBM Build ca122-20000607b Web Server: Netscape Enterprise Server 3.6 DB Server: Infomix RDBMS The problem is that JRun is dying once or twice a day. At that time, java process shows alive but no requests are accepted, and only the message displayed on the browser are below ; JRUN Connector Proxy requests timed out Please contact the system administrator for this web site Next is web server's log ; [09/Aug/2000:17:16:57] warning (20070): for host 211.107.127.41 trying to POST /servlet/nacf_vcs, jrNSAPI[1124] reports: 127.0.0.1:8081 timed out after waiting 300 seconds for [1] In this case JRun will not restart ,so we have to kill the process and start. In addistion, We can see CPU idle is almost 100% and the JRun log has nothing particular. The value we use is default value in JRun, Max thread is 1000 , Min thread is 1 and active thread is 100. We also set the jcp logging option. There are nothing particular, too. The logs are below ; jcp [9/07:00:15:16] 97659kb, 5+1=8 threads, 1 peak, 0/1 rq delayed, 0 dropped. jcp [9/07:00:15:26] 97659kb, 5+3=9 threads, 3 peak, 0/5 rq delayed, 0 dropped. jcp [9/07:00:15:46] 97659kb, 5+2=9 threads, 2 peak, 0/3 rq delayed, 0 dropped. ==> dying... jcp [9/07:00:15:56] 97659kb, 5+3=8 threads, 3 peak, 0/5 rq delayed, 0 dropped. ==> kill and start jcp [9/07:00:16:06] 97659kb, 5+2=8 threads, 2 peak, 0/2 rq delayed, 0 dropped. jcp [9/07:00:16:16] 97659kb, 5+4=9 threads, 4 peak, 0/4 rq delayed, 0 dropped. jcp [9/07:00:16:26] 97659kb, 5+3=10 threads, 3 peak, 0/6 rq delayed, 0 dropped. jcp [9/07:00:16:36] 97659kb, 5+2=10 threads, 2 peak, 0/6 rq delayed, 0 dropped. ==> dying jcp [9/07:00:16:46] 97659kb, 5+1=11 threads, 1 peak, 0/5 rq delayed, 0 dropped. ==> kill and start jcp [9/07:00:16:56] 97659kb, 5+2=9 threads, 2 peak, 0/5 rq delayed, 0 dropped. jcp [9/07:00:17:06] 97659kb, 5+2=9 threads, 2 peak, 0/5 rq delayed, 0 dropped. At the busiest time, total thread number is not more than 60. One more thing, our customer has another problem with JVM. We might find out the solution in that, I think. They set the JIT compiler disabled. It is because the JRun dies more often than when it is set enabled. The Heap size is set Min. 100MB ~ Max. 500MB. So what do you think I should check out for this problem? Any suggestion and possibility will save us. Thanks in advance. Sean Lim ---------------------------------------------------------------------------- -- 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. ---------------------------------------------------------------------------- -- 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. ------------------------------------------------------------------------------ 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.
