When I looked at your client, I found that you have a loop that creates
100,000 instances of the EJB and have never free any. Thus, your client now
has 100,000 EJB's that will not be passivated until you leave the for loop.
This type of code will break most app servers.
SnowWolf Wagner
-Orig
the file is classes12.zip and should be in the orion/lib
SnowWolf
-Original Message-
From: Roland Dong [mailto:[EMAIL PROTECTED]]
Sent: Saturday, March 24, 2001 1:10 AM
To: Orion-Interest
Subject: problem running oracle with orion:
'oracle.jdbc.driver.OracleDriver' not found!
I tried
The Apache server on NT is considered beta by Apache. You should note that
it has be view as beta for years. They is almost no benfit to running Apache
in front of Orion. Why do oyu want to.
SnowWolf
-Original Message-
From: Harsh Vinod Mohta [mailto:[EMAIL PROTECTED]]
Sent: Friday, Marc
I think what you need here is to define the datasource.xml for each
application. This is then placed in the deployment folder for the
application just like the principles.xml. This bind a datasource or
multipule datasources to the app and not to the server.
SnowWolf Wagner, MAIP
-Original Me
I have used both PHP and JSP. If you understand PHP you can develop it
faster that JSP. The problem is that PHP is very Perl like which is a steep
learning curve and JSP will scale much better. The problem with this
comparison is you are leaving out Servlets. If you do JSP in the Model 2
style wit
