[Resin-interest] Shutdown Issues

2011-05-26 Thread Aaron Freeman
Starting with resin-4.0.16 and persisting with Resin-4.0.18 we can no longer shutdown the Resin process properly. When I attempt to do so I get this: - Resin/4.0.18 can't shutdown watchdog at 127.0.0.1:10080. com.caucho.bam.RemoteConnectionFailedException:

Re: [Resin-interest] Writer and OutputStream mixup in 4.0.10...?

2011-05-26 Thread Mattias Jiderhamn
We're still seeing this issue at random under 4.0.18 :-( http://bugs.caucho.com/view.php?id=4290 /Mattias Scott Ferguson wrote (2010-11-17 18:50): Mattias Jiderhamn wrote: Scott Ferguson wrote (2010-11-12 18:01): Mattias Jiderhamn wrote: Since upgrading to Resin 4.0.10 this error has turned

Re: [Resin-interest] Shutdown Issues

2011-05-26 Thread Aaron Freeman
I have tried each version, starting with 4.0.18 and going back, and the shutdown problem begins with resin-pro-4.0.14 and up. I noticed this on the change log for version 4.0.14: resin: CLI added deploy, undeploy, list, start-webapp, stop-webapp, restar-webapp commands (#4316, rep by Patrick

Re: [Resin-interest] Shutdown Issues

2011-05-26 Thread Chris Pratt
I definitely don't know for sure, but that strikes me as a duplicate jar problem. You might look at what new jars were introduced in 4.0.14 and see if you are duplicating any of them in your WEB-INF/lib directory. (*Chris*) On Thu, May 26, 2011 at 7:49 AM, Aaron Freeman

Re: [Resin-interest] Shutdown Issues

2011-05-26 Thread Scott Ferguson
On 05/26/2011 02:29 AM, Aaron Freeman wrote: Starting with resin-4.0.16 and persisting with Resin-4.0.18 we can no longer shutdown the Resin process properly. When I attempt to do so I get this: Do you have multiple resin:AdminAuthenticator or resin:XmlAuthenticator anywhere in the resin.xml

Re: [Resin-interest] MySQL issues with 4.0.18

2011-05-26 Thread Rachel McConnell
You probably have your mysql server configured to only accept socket connections, and not TCP/IP connections. As a rule, external client programs use TCP/IP by default, as sockets can only be used if the db server is on the same machine as the client program and this is often not the case for

Re: [Resin-interest] MySQL issues with 4.0.18

2011-05-26 Thread Rick Mann
Thank you, Rachel, that does indeed seem to be the case. Is it not possible to get Connector/J to use a socket underneath, if it's running on the same host? -- Rick On May 26, 2011, at 17:09 , Rachel McConnell wrote: You probably have your mysql server configured to only accept socket