Runs fine on Win95 PII 200 at 64MB RAM. I used it for development up till 6
months ago. (not my choice!)
From: Stephen Davidson [EMAIL PROTECTED]@orionserver.com on
12/04/2001 12:46 PM
Please respond to Orion-Interest [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To:
Loadbalancer.jar will fail a session over to a second Orion, if it can't open a
successful session within several seconds to the first (sticky) Orion. Works
great, but you have that single point of failure.
I'm experimenting with the MS Network Load Balancer (it comes in Win2K AS) and
the main
I recently went through the Orion on NT ordeal (I usually work on Unix/Linux)
and found some new info, so I thought I would pass it along.
To masquerade Orion as a service, I'm using SRVSTART.EXE from Nick Rozanski (
http://www.nick.rozanski.com/software.htm
I run pretty much the same setup as you. What I've found, is that it is easier
to compile the JSP under NetBeans and let it gripe about errors. Servlets and
other classes are easy to debug remotely, but JSP's get compiled to servlets
and then run. I have had a much tougher time debugging them
This is generally an OS/Shell tunable.
On Unix, take a look at the ulimit command. You may also have to reconfigure
the kernel (OS) for more file handles.
Good luck,
Bob
From: Eddie [EMAIL PROTECTED]@orionserver.com on 07/20/2001 02:47 PM
ZE2
Please respond to Orion-Interest [EMAIL
I just finished doing some load testing with Orion, WebLogic, and WebSphere
(via IBM Apache).
All the servers but WebSphere/Apache eventually had connection failures. I
chalk it up to all the object creation/destruction going on for a connection.
Apache, having it's C heritage does not have as
