Re: [Resin-interest] Quercus Question

Hi, I take advantage of the situation about this email to ask Caucho's team if we are allowed to fork the project [Quercus] on GitHub to make our own changes/bug fixes. The project seems to run slowly (*as looked on the bug report*) and we are making some improvements for a production environment

Re: [Resin-interest] Resin 4.0.9 release

Hi Jan, Did your resin server have a busy traffic? Did u observed any memory leak or heap overflow? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest

Re: [Resin-interest] Resin 4.0.9 release

Hi Wesley, Did your resin server have a busy traffic? Did u observed any memory leak or heap overflow? neither nor. Best regards, --- Jan. ___ resin-interest mailing list resin-interest@caucho.com

Re: [Resin-interest] Resin 4.0.9 release

Out of curiosity do you have multiple instances of Resin (separate JVMs) running on that same virtual machine? If so do you use different ports for the watchdog on both instances? We had a similar situation and it was fixed by just running the watchdog on separate ports for each instance of

Re: [Resin-interest] Resin 4.0.9 release

Hi Aaron, Out of curiosity do you have multiple instances of Resin (separate JVMs) running on that same virtual machine? If so do you use different ports for the watchdog on both instances? We had a similar situation and it was fixed by just running the watchdog on separate ports for

Re: [Resin-interest] Resin 4.0.9 release

Jan Kriesten wrote: Hi Scott, I've put up a new snapshot. On a restart, you should see additional logging information in both the watchdog-manager.log and the jvm-default.log that should help narrow this down. the only new entry in the log on restart in the jvm-default.log is

[Resin-interest] Session object casting - resin 4.0.7

I am running resin 4.0.7 and I store a user object in the session using User_Bean as a key. Everything works fine most of the time but it seems when my session expires and I have not logged out, every subsequent call to get this object returns some HashMap instead of my object or null. Since I

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

Wesley Wu wrote: Hi Scott, I've applied the 4.0.10 snapshot and the Alarm issue went away. Thanks. But Resin consumed all memory after certain hours and resulted in a halt or restart. I did a jrockit flight recording and found there was a slow heap increase during various GCs. The

[Resin-interest] [ANN]VTD-XML 2.9

VTD-XML 2.9, the next generation XML Processing API for SOA and Cloud computing, has been released. Please visit https://sourceforge.net/projects/vtd-xml/files/ to download the latest version. a.. Strict Conformance a.. VTD-XML now fully conforms to XML namespace 1.0 spec b..

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

Hi Scott, The memory leak circumstance was not spotted in Resin 4.0.5 and early 4.0.x versions. One of the inject path is: * A filter CmsPageFilter dispatch a request to a Jsp page through javax.servlet.RequestDispatcher.forward(request, response) * Jsp page called a BeanMethod custom jsp tag *

Re: [Resin-interest] Possible memory leak in Resin 4.0.9

My BeanManager wrapper code @Singleton @Startup public class MDIObjectFactory { private static BeanManager beanManager; private static BeanManager getBeanManager() { if (beanManager == null) { try {

Re: [Resin-interest] Resin 4.0.9 release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Scott, As a workaround, you can disable the ping (or PingThread) until I figure out why that's happening. as an idea, I have the following in resin.xm from an old default: resin:if test=${resin.professional} ping !--