Here is an interesting one,
If I package my application up as a JAR and put it in WEB-INF/lib then I get
memory leaks in the perm gen space as none of the Class objects are garbage
collected. This is easily re-producable every time. If however I put the
application's .class files inside
On our production Resin 2.1.17 periodicaly we get the following error:
[2006-12-07 15:31:56.630] close-idle 153:jdbc/data [active:4, total:10]
[2006-12-07 15:31:56.659] close 153:jdbc/data
[2006-12-07 15:31:56.659] 153:close()
[2006-12-07 15:31:56.660] 153:exn-close(java.sql.SQLException:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
is it possible to create EJBs packaged in a JAR file and have them
available without creating a WAR file and a servlet to access them?
Are there any examples on this?
I see in the server logfile that my EJBs are compiled, but I get a
Environment: Windows 2003 Server, Resin Pro 3.0.21, OpenSSL 0.9.8b,
Java 1.4.2_12
Saw this SSL-related error in our logs this morning just after a
spontaneous restart of resing caused by the JVM (jvm.dll):
[06:35:48.766] Loaded Socket JNI library.
[06:35:48.781] http listening to *:80
On Dec 8, 2006, at 00:10 , sksamuel wrote:
Here is an interesting one,
If I package my application up as a JAR and put it in WEB-INF/lib
then I get
memory leaks in the perm gen space as none of the Class objects are
garbage
collected. This is easily re-producable every time. If however
Do you mean simply having a web application as a place where you deploy
your EJBs that are then accessed from other web applications? Or do you
mean simply not packaging your web application as an .ear/.war file and
still have your EJBs deployed?
For the latter case, I don't use .war/.ear files
Environment: Windows 2003 Server, Resin Pro 3.0.21, OpenSSL 0.9.8b,
Java 1.4.2_12
More information on what caused the JVM/Resin to spontaneously
reboot. I get these fairly often (multiple times per month). They're
not always the same exact thing. Often the stack trace references one
of
On Dec 8, 2006, at 8:37 AM, Rob Lockstone wrote:
On Dec 8, 2006, at 00:10 , sksamuel wrote:
Here is an interesting one,
If I package my application up as a JAR and put it in WEB-INF/lib
then I get
memory leaks in the perm gen space as none of the Class objects are
garbage
collected.
If what you describe is really happening, it's gotta be nominated for
the Bizzaro Bug of the Month or something. :-)
You're sure the perm space is being exhausted? Are you using -XX:
+PrintGCDetails or something similar to see the results of gc's on
the perm space?
Yes of course. and
On Dec 8, 2006, at 8:56 AM, Rob Lockstone wrote:
Environment: Windows 2003 Server, Resin Pro 3.0.21, OpenSSL 0.9.8b,
Java 1.4.2_12
More information on what caused the JVM/Resin to spontaneously
reboot. I get these fairly often (multiple times per month).
They're not always the same
On Dec 8, 2006, at 09:10 , Scott Ferguson wrote:
On Dec 8, 2006, at 8:56 AM, Rob Lockstone wrote:
Environment: Windows 2003 Server, Resin Pro 3.0.21, OpenSSL 0.9.8b,
Java 1.4.2_12
More information on what caused the JVM/Resin to spontaneously
reboot. I get these fairly often (multiple
On Dec 7, 2006, at 6:05 PM, jason rutherglen wrote:
Where org.apache.solr.cluster.ClusterLogFormatter extends
java.util.logging.Formatter. Get this error:
[17:49:24.453] com.caucho.config.LineConfigException: WEB-INF/
web.xml:16: java.l
ang.IllegalAccessException: Class
If you were using the snapshot version 3.1.s061203, you might ran into a Resin
bug.
I found my EJB3 stopped working on this version and noticed Resin sample
stateless EJB not working either.
By the way, Markus, you can find sample code under:
On Dec 8, 2006, at 10:34 AM, Rob Lockstone wrote:
Fwiw, I just restarted a server and got three of these SSL-related
crashes in a row. It's just really, really bad when you try to
restart a server and add it to a pool of active servers and it
starts taking requests. Just awful.
So it
On Dec 8, 2006, at 6:00 PM, Rob Lockstone wrote:
We can add the OpenSSL version we tested with. That's a good idea.
We can't distribute the dll itself.
Damn. :-( Well, can you distribute the source AND your particular
build flags, etc? That should allow us to build the dll with the same
On Dec 8, 2006, at 18:43 , Scott Ferguson wrote:
On Dec 8, 2006, at 6:00 PM, Rob Lockstone wrote:
We can add the OpenSSL version we tested with. That's a good idea.
We can't distribute the dll itself.
Damn. :-( Well, can you distribute the source AND your particular
build flags, etc?
16 matches
Mail list logo
