-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Manuel
Sent: Friday, August 31, 2001 6:55 AM
To: Orion-Interest
Subject: RE: Limiting no of Entity Instances in the containerTo run the two instances on the same machine is going to be a waiste - you are going be kicking up two JVM's etc or at least double amount of management overhead on the same machine for no reason. Your problem looks more like a software issue, either there is a bug in the orion software or chances are you are not synchronizing something properly, when you simulate the larger number of users the error becomes apparent. Rather try to solve the software problem than work around it ... kicking up two instance of the same application to get around a potential bug is only going to make your final system less predicable and unstable.-----Original Message-----ciao Biswajit
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Paolo Ramasso
Sent: Friday, August 31, 2001 8:13 AM
To: Orion-Interest
Subject: Re: Limiting no of Entity Instances in the container
i use more than one oc4j istance on the same box, did you update the http,jms,rmi listening ports?
files:
http:default-web-site.xml, jms:jms.xml, rmi:rmi.xml
ciao
PaoloBiswajit Nayak wrote:
Hi Gurus
I want to configure two OC4J instances in one node for load balancing . I have a 4CPU E420 solaris box . With one OC4J I can support only 50 users . When I am simulating 100 users I am getting the following error messages . So I think mulitple OC4J instances will help .
Thanks
Biswajit
Errors on OC4J Console
************************
java.lang.NullPointerException
at com.evermind.server.jms.JMSServer.removeClient(JMSServer.java:712)
at com.evermind.server.jms.JMSRequestHandler.run(Compiled Code)
at com.evermind.util.ThreadPoolThread.run(Compiled Code)
Failed to bind Launcher to port 9127Errors in global-application.log
*********************************
12:26 PM defaultWebApp: Servlet error
javax.servlet.ServletException: No HTTP headers received from runform
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at javax.servlet.ServletException.<init>(ServletException.java:16)
at
oracle.forms.servlet.ListenerServlet.forwardResponseFromRunform(Compi
led Code)
at oracle.forms.servlet.ListenerServlet.doPost(Compiled Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at javax.servlet.http.HttpServlet.service(Compiled Code)
at com.evermind[Oracle9iAS (1.0.2.2) Containers for
J2EE].server.http.Se
rvletRequestDispatcher.invoke(Compiled Code)
at com.evermind[Oracle9iAS (1.0.2.2) Containers for
J2EE].server.http.Se
rvletRequestDispatcher.forwardInternal(Compiled Code)
at com.evermind[Oracle9iAS (1.0.2.2) Containers for
J2EE].server.http.Ht
tpRequestHandler.processRequest(Compiled Code)
at com.evermind[Oracle9iAS (1.0.2.2) Containers for
J2EE].server.http.Ht
tpRequestHandler.run(Compiled Code)
at com.evermind[Oracle9iAS (1.0.2.2) Containers for
J2EE].util.ThreadPoo
lThread.run(Compiled Code)
***
Get your FREE download of MSN Explorer at http://explorer.msn.com
I
disagree with any assertion that running multiple VMs on a large SMP box is a
waste.
I've
corroborated advise given from many places (other J2EE vendors who support
multi-VM)
that
tuning a VM for less than 500 threads and 512Mb max memory is desirable.
Split into
many
VMs as these limits are approached. I.E. a 6 fast CPU box with 12GB RAM
should
run
around 6-12 VMs. Some sophisticated J2EE vendors support
auto-spinning up new
VMs as
needed. This list does not included WLS.
Why? The VM becomes inefficient at it's own
internal thread management as # of threads goes
up. Experimental determination has found that
>200 threads and the VM starts slowing. >512
and
it's really getting inefficient. Same goes for heap size management
>512Mb of RAM.
curt
- Limiting no of Entity Instances in the container Ivo Rakovac
- Re: Limiting no of Entity Instances in the container Biswajit Nayak
- Re: Limiting no of Entity Instances in the container Paolo Ramasso
- RE: Limiting no of Entity Instances in the container Manuel
- Curt Smith
