| |
From chipa@s... Fri Jul 07 14:25:26 2000
Received: (qmail 25190 invoked from network); 7 Jul 2000 21:25:26 -0000
Received: from unknown (10.1.10.26) by m2.onelist.org with QMQP; 7 Jul 2000 21:25:26 -0000
Received: from unknown (HELO WWW.houseoffusion.com) (207.31.122.140) by mta1 with SMTP; 7 Jul 2000 21:25:26 -0000
Received: from StockCharts.com ([209.20.177.62]) by WWW.houseoffusion.com (Post.Office MTA v3.5.3 release 223 ID# 0-54969U100L100S0V35) with ESMTP id com for <jrun-talk@h...>; Fri, 7 Jul 2000 13:50:52 -0400
Received: from megadell [10.1.1.122] by StockCharts.com [209.20.177.62] with SMTP (MDaemon.v2.8.5.0.R) for <jrun-talk@h...>; Fri, 07 Jul 2000 10:41:52 -0700
From: "Chip Anderson" <chipa@s...>
To: <jrun-talk@h...>
Subject: RE: ISAPI connector talking to Multiple JVMs?
Date: Fri, 7 Jul 2000 10:41:48 -0700
Message-ID: <NDBBIHMEGMPBABKNLABOIEPLFFAA.chipa@s...>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
In-Reply-To: <NDBBIHMEGMPBABKNLABOKEIFFFAA.chipa@s...>
Importance: Normal
Reply-To: jrun-talk@h...
Return-Path: owner-jrun-Talk@h...
Scott and others: Thanks for your help so far on the multiple JVM problem I am having. Here's where I am at today:
- I added the name of other JVM to jrun.ini's "jvmlist" entry.
- I restarted the server just to be sure
- The "listening port" setting for the two JVM's that are connected to IIS are different (7001, 7002)
- I commented out the JSP mappings in the "global.properties" file.
- I commented out the JSP mapping in the "local.properties" file for the servlet-only JVM ("Default").
- I changed the JSP mapping in the "local.properties" file for the JSP-only JVM ("JSP") to be:
webapp.servlet-mapping.*.jsp=jsp
- I restarted both JVMs.
At this point, the servlet works fine inside the "Default" JVM but the JSP's in the other JVM aren't getting compiled when accessed
from the ISAPI connector. For example, if I create a new file, test.jsp, and place it on the server,
http://mydomain.com/jsp/test.jsp yields:
404 Not Found
/jsp/test.jsp:
allaire.jrun.JRunServletException: The page /test.jsp could not be found.
at allaire.jrun.jsp.JSPParser.generateXML(JSPParser.java:57)
at allaire.jrun.jsp.JSPServlet.parsePage(JSPServlet.java:403)
...
However, if I first refer to the JSP using the built-in web server (i.e., port 8101) - things work fine AND THEY WORK FINE ON THE
ISAPI VERSION (i.e., port 80). However if I then change test.jsp, the changes don't show up on port 80 until I first view the JSP
on port 8101. (FWIW: I've switched browsers and client machines just to make sure this wasn't a caching problem.) So, it seems the
JSP compiler isn't being invoked when I access things via the ISAPI connector. Any ideas why that would be?
=============================================
I don't know if this is related or not, but we are also now getting the following exception in the _Default_ JVM's error log:
07/04 17:31:35 error (jcp) Connection reset by peer: JVM_recv in socket input stream read [java.net.SocketException: Connection
reset by peer: JVM_recv in socket input stream read]
java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:86)
...
These messages appear sporadically about once every 20 minutes and appear to have started right after I added the second JVM to the
jvmlist property (although I'm not positive about that). They appear to correspond to another message we are seeing in the ISAPI
log files:
17:31:33 jrISAPI[4608] writeClient failed: 10053
There are other worrisome messages in the ISAPI log file also. They look like:
17:10:43 jrISAPI[1952] JRun unable to fetch servlet-mappings <- [524]
17:10:43 jrISAPI[1952] PROXY_BUSY <- [1580]
17:24:19 jrISAPI[4608] PROXY_BUSY <- [2672]
17:31:33 jrISAPI[4608] writeClient failed: 10053
17:31:33 jrISAPI[4608] writeClient failed: 10053
17:36:51 jrISAPI[filter] JRun unable to fetch servlet-mappings <- [2980]
17:50:56 jrISAPI[5936] PROXY_BUSY <- [2376]
17:50:57 jrISAPI[624] PROXY_BUSY <- [2732]
17:51:45 jrISAPI[624] writeClient failed: 10054
17:51:45 jrISAPI[624] writeClient failed: 10054
There are _lots_ of these. Should we be worried about these?
============================================
Thanks in advance!
Chip
-----Original Message-----
From: Scott Stirling [mailto:sstirling@m...]
Sent: Tuesday, July 04, 2000 4:43 PM
To: jrun-talk@h...
Subject: RE: ISAPI connector talking to Multiple JVMs?
The jrun.ini file has a jvmlist property. Manually add a comma-separated list
of JRun JVMs there. Don't worry about the proxyports in the jrun.ini, but do
have jcps listening on three different proxyports on the JRun side. The
connector should use the jrun.rootdir property to find the local.properties and
other info it needs for each server.
An obvious problem you are likely to encounter here is that /servlet/ is an
implicit mapping for every server, as is *.jsp. So you've got to disable it in
global.properties if you aren't going to override it in local.properties.
Scott Stirling
-----Original Message-----
From: Chip Anderson [mailto:chipa@s...]
Sent: Tuesday, July 04, 2000 7:14 PM
To: jrun-talk@h...
Subject: ISAPI connector talking to Multiple JVMs?
Is it possible to have the ISAPI connector pass requests to different JVMs
depending on the URL of the request.
I've spent most of this holiday trying to accomplish this without much luck.
Any help would be greatly appreciated.
i.e. I've got JRun 3.0 on Win2K with IIS 5.0.
I've got three JVMs installed - the Admin one, the Default one, and a new one
called "JSP"
Each one works great if I include the port specification in the URL (:8100,
:8101, etc.).
I want http://foo.com/servlet/myServletClass?param=Fred to run inside of the
"Default" JVM.
I want http://foo.com/jsp/HelloWorld.jsp to run inside of the "JSP" JVM.
I've set the Default application in "Default" to look for "/servlet".
I've set the Default application in "JSP" to look for "/jsp".
Again, everything works fine if I actually specify the port number in the URL,
but there are
compatibility reasons why I can't do that in the production environment.
Best I can tell, the "JRun.ini" file in my /scripts directory only allows one
"ProxyPort". If
I set it to the Default JVM's port, the servlets work, but the JSPs don't and
vice versa.
There must be a solution to this. What am I missing?
Thanks in advance,
Chip
----------------------------------------------------------------------
--------
Archives:
target=_blank>http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_t
alk
or send a message to jrun-talk-request@h... with 'unsubscribe' in the body.
---- 관리자님이 쓰신 글 ----
class 파일 위치; /usr/local/JRun/servers/default/default-app/WEB-INF
[Wed Oct 22 18:12:41 2003] [notice] jrApache[1680] JRun unable to fetch servlet-
mappings <- [5]
[Wed Oct 22 18:12:41 2003] [notice] jrApache[1681] JRun unable to fetch servlet-
mappings <- [5]
[Wed Oct 22 18:12:41 2003] [notice] jrApache[1680] JRun unable to fetch servlet-
mappings <- [6]
[Wed Oct 22 18:12:41 2003] [notice] jrApache[1681] JRun unable to fetch servlet-
mappings <- [6]
[Wed Oct 22 18:13:20 2003] [notice] jrApache[3873] JRun unable to fetch servlet-
mappings <- [6]
[Wed Oct 22 18:13:20 2003] [notice] jrApache[3873] PROXY_BUSY <- [7]
[Wed Oct 22 18:13:21 2003] [notice] jrApache[3882] JRun unable to fetch servlet-
mappings <- [5]
[Wed Oct 22 18:13:21 2003] [notice] jrApache[3882] PROXY_BUSY <- [7]
[Wed Oct 22 18:14:23 2003] [notice] jrApache[33896] JRun unable to fetch servlet
-mappings <- [5]
[Wed Oct 22 18:14:23 2003] [notice] jrApache[33896] PROXY_BUSY <- [7]
[Wed Oct 22 18:14:58 2003] [notice] jrApache[10986] JRun unable to fetch servlet
-mappings <- [5]
|