Re: [Resin-interest] Resin clustered session store
We're using Xfire 1.2.6. I don't have a simple app you can deploy to test. I'll try and put one together tomorrow if I have a chance. This is unlikely as I'm pretty swamped right now :-) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emil Ong Sent: 16 January 2008 18:38 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin clustered session store Hi Richard, Which version of XFire are you using? Also, is there any chance you have a sample service that exhibits this behavior? I'll see if I can find the message you referenced on the XFire list... Thanks, Emil On Mon, Jan 14, 2008 at 05:56:57PM -, Richard Grantham wrote: > We would send valid SOAP requests but XFire was not interpretting > parameters correctly. > > Eg. This SOAP request: > > http://www.w3.org/2001/XMLSchema"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > false > > > > > would give this response: > > 2007-08-08 09:59:03,894 ERROR [resin-tcp-connection-*:80-14] > (DefaultFaultHandler.java:35) - Fault occurred! > org.codehaus.xfire.XFireRuntimeException: Invalid boolean value: > at > org.codehaus.xfire.aegis.AbstractMessageReader.getValueAsBoolean(Abstr > ac > tMessageReader.java:115) > at > org.codehaus.xfire.aegis.type.basic.BooleanType.readObject(BooleanType > .j > ava:16) > at > org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBindi > ng > Provider.java:169) > at > org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding. > java:206) > at > org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedB > in > ding.java:51) > at > org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler > .j > ava:42) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java > :1 > 31) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint > .j > ava:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.j > av > a:38) > at > org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireS > er > vletController.java:304) > at > org.codehaus.xfire.transport.http.XFireServletController.doService(XFi > re > ServletController.java:129) > at > org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java: > 116) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:153) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:91) > at > com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterCh > ai > n.java:103) > > The only difference would be the version of Resin used. I think > someone else posted a question about it to the XFire mailing list and > didn't receive a response. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Emil Ong > Sent: 14 January 2008 17:38 > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] Resin clustered session store > > On Mon, Jan 14, 2008 at 04:54:19PM -, Richard Grantham wrote: > > Thanks for the response Scott. We did some firewall reconfiguration > > with regards to connections and sessions and the issue appears to > > have > > > gone away. > > > > I've not tried the 3.1 branch in a while as we found it didn't play > > well with XFire, but I will upgrade to 3.0.25 ASAP. > > Hi Richard, > > What problems did you run into with XFire and 3.1? We want to make > sure they work well together. > > Thanks, > Emil > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Scott > > Ferguson > > Sent: 14 January 2008 16:45 > > To: General Discussion for the Resin application server > > Subject: Re: [Resin-interest] Resin clustered session store > > > > > > On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > > > > > Hi list, > > > > > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > > > sessions) and I've seen this error a few times in the log file: > > > > We've made a few fixes to the synchronization/timing of the > > clustered session. Some in 3.0
Re: [Resin-interest] Resin clustered session store
Hi Richard, Which version of XFire are you using? Also, is there any chance you have a sample service that exhibits this behavior? I'll see if I can find the message you referenced on the XFire list... Thanks, Emil On Mon, Jan 14, 2008 at 05:56:57PM -, Richard Grantham wrote: > We would send valid SOAP requests but XFire was not interpretting > parameters correctly. > > Eg. This SOAP request: > > http://www.w3.org/2001/XMLSchema"; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; >xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > false > > > > > would give this response: > > 2007-08-08 09:59:03,894 ERROR [resin-tcp-connection-*:80-14] > (DefaultFaultHandler.java:35) - Fault occurred! > org.codehaus.xfire.XFireRuntimeException: Invalid boolean value: > at > org.codehaus.xfire.aegis.AbstractMessageReader.getValueAsBoolean(Abstrac > tMessageReader.java:115) > at > org.codehaus.xfire.aegis.type.basic.BooleanType.readObject(BooleanType.j > ava:16) > at > org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBinding > Provider.java:169) > at > org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding. > java:206) > at > org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBin > ding.java:51) > at > org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.j > ava:42) > at > org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:1 > 31) > at > org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.j > ava:64) > at > org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.jav > a:38) > at > org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireSer > vletController.java:304) > at > org.codehaus.xfire.transport.http.XFireServletController.doService(XFire > ServletController.java:129) > at > org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java: > 116) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:153) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:91) > at > com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChai > n.java:103) > > The only difference would be the version of Resin used. I think someone > else posted a question about it to the XFire mailing list and didn't > receive a response. > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Emil Ong > Sent: 14 January 2008 17:38 > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] Resin clustered session store > > On Mon, Jan 14, 2008 at 04:54:19PM -, Richard Grantham wrote: > > Thanks for the response Scott. We did some firewall reconfiguration > > with regards to connections and sessions and the issue appears to have > > > gone away. > > > > I've not tried the 3.1 branch in a while as we found it didn't play > > well with XFire, but I will upgrade to 3.0.25 ASAP. > > Hi Richard, > > What problems did you run into with XFire and 3.1? We want to make sure > they work well together. > > Thanks, > Emil > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson > > Sent: 14 January 2008 16:45 > > To: General Discussion for the Resin application server > > Subject: Re: [Resin-interest] Resin clustered session store > > > > > > On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > > > > > Hi list, > > > > > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > > > sessions) and I've seen this error a few times in the log file: > > > > We've made a few fixes to the synchronization/timing of the clustered > > session. Some in 3.0.25, but many more in 3.1. > > > > However, I was never able to reproduce that exact error here, so if > > anyone runs into this on 3.1.4 or later, it would be very helpful to > > send a bug report on the issue with as much detail as possible. > > > > -- Scott > > > > > > > > [2008-01-10 11:31:01.379] java.io.EOFException > > > [2008-01-10 11:31:01.379] at > > > java.io.ObjectInputStream$PeekInputStream.readFully > > > (ObjectInputStream.ja >
Re: [Resin-interest] Resin clustered session store
I've upgraded to 3.0.25 but I'm still seeing lots of session issues. One little bit or weirdness that I hope someone can answer is how the session database managed to shrink from around the 500MB mark to the 20MB mark. This seems to be a major drop in the space used. Also, I got an error whereby it tried to write an object of over 64mb to the file store, which gave an error. Now, I've checked through my application and I'm pretty sure that nothing is storing an object of that size in the session. I saw this bug: http://bugs.caucho.com/view.php?id=848 Could they be related? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Richard Grantham Sent: 14 January 2008 16:54 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin clustered session store Thanks for the response Scott. We did some firewall reconfiguration with regards to connections and sessions and the issue appears to have gone away. I've not tried the 3.1 branch in a while as we found it didn't play well with XFire, but I will upgrade to 3.0.25 ASAP. rgds, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 14 January 2008 16:45 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin clustered session store On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > Hi list, > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > sessions) and I've seen this error a few times in the log file: We've made a few fixes to the synchronization/timing of the clustered session. Some in 3.0.25, but many more in 3.1. However, I was never able to reproduce that exact error here, so if anyone runs into this on 3.1.4 or later, it would be very helpful to send a bug report on the issue with as much detail as possible. -- Scott > > [2008-01-10 11:31:01.379] java.io.EOFException > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$PeekInputStream.readFully > (ObjectInputStream.ja > va:2279) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$BlockDataInputStream.readShort > (ObjectInputStre > am.java:2748) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.(ObjectInputStream.java:280) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject > $DistributedObjectInputStream. it>(ClusterObject.java:474) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:286) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.FileBacking.loadSelf(FileBacking.java:318) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterStore.load(ClusterStore.java:423) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:259) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionImpl.load(SessionImpl.java:702) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionManager.getSession > (SessionManager.java: > 1278) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.createSession > (AbstractH > ttpRequest.java:1444) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.getSession > (AbstractHttp > Request.java:1256) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.writeHeaders > (AbstractH > ttpResponse.java:1556) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeHeaders > (ResponseStream. > java:216) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeNext > (ResponseStream.jav > a:401) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushByteBuffer > (ToByte > ResponseStream.java:518) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushBuffer > (ToByteResp > onseStream.java:424) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.finish > (ResponseStream.java:6 > 64) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.close > (ResponseStream.java:79 > 6) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.finish > (AbstractHttpRes > ponse.java:1956) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.close > (AbstractHttpResp > onse.java:260) &g
Re: [Resin-interest] Resin clustered session store
We would send valid SOAP requests but XFire was not interpretting parameters correctly. Eg. This SOAP request: http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> false would give this response: 2007-08-08 09:59:03,894 ERROR [resin-tcp-connection-*:80-14] (DefaultFaultHandler.java:35) - Fault occurred! org.codehaus.xfire.XFireRuntimeException: Invalid boolean value: at org.codehaus.xfire.aegis.AbstractMessageReader.getValueAsBoolean(Abstrac tMessageReader.java:115) at org.codehaus.xfire.aegis.type.basic.BooleanType.readObject(BooleanType.j ava:16) at org.codehaus.xfire.aegis.AegisBindingProvider.readParameter(AegisBinding Provider.java:169) at org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding. java:206) at org.codehaus.xfire.service.binding.WrappedBinding.readMessage(WrappedBin ding.java:51) at org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.j ava:42) at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:1 31) at org.codehaus.xfire.transport.DefaultEndpoint.onReceive(DefaultEndpoint.j ava:64) at org.codehaus.xfire.transport.AbstractChannel.receive(AbstractChannel.jav a:38) at org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireSer vletController.java:304) at org.codehaus.xfire.transport.http.XFireServletController.doService(XFire ServletController.java:129) at org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java: 116) at javax.servlet.http.HttpServlet.service(HttpServlet.java:153) at javax.servlet.http.HttpServlet.service(HttpServlet.java:91) at com.caucho.server.dispatch.ServletFilterChain.doFilter(ServletFilterChai n.java:103) The only difference would be the version of Resin used. I think someone else posted a question about it to the XFire mailing list and didn't receive a response. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emil Ong Sent: 14 January 2008 17:38 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin clustered session store On Mon, Jan 14, 2008 at 04:54:19PM -, Richard Grantham wrote: > Thanks for the response Scott. We did some firewall reconfiguration > with regards to connections and sessions and the issue appears to have > gone away. > > I've not tried the 3.1 branch in a while as we found it didn't play > well with XFire, but I will upgrade to 3.0.25 ASAP. Hi Richard, What problems did you run into with XFire and 3.1? We want to make sure they work well together. Thanks, Emil > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson > Sent: 14 January 2008 16:45 > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] Resin clustered session store > > > On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > > > Hi list, > > > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > > sessions) and I've seen this error a few times in the log file: > > We've made a few fixes to the synchronization/timing of the clustered > session. Some in 3.0.25, but many more in 3.1. > > However, I was never able to reproduce that exact error here, so if > anyone runs into this on 3.1.4 or later, it would be very helpful to > send a bug report on the issue with as much detail as possible. > > -- Scott > > > > > [2008-01-10 11:31:01.379] java.io.EOFException > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream$PeekInputStream.readFully > > (ObjectInputStream.ja > > va:2279) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream$BlockDataInputStream.readShort > > (ObjectInputStre > > am.java:2748) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream.(ObjectInputStream.java:280) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterObject > > $DistributedObjectInputStream. > it>(ClusterObject.java:474) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:286) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.FileBacking.loadSelf(FileBacking.java:318) > > [2008-01-10 11:31:01.379] at > > c
Re: [Resin-interest] Resin clustered session store
On Mon, Jan 14, 2008 at 04:54:19PM -, Richard Grantham wrote: > Thanks for the response Scott. We did some firewall reconfiguration with > regards to connections and sessions and the issue appears to have gone > away. > > I've not tried the 3.1 branch in a while as we found it didn't play well > with XFire, but I will upgrade to 3.0.25 ASAP. Hi Richard, What problems did you run into with XFire and 3.1? We want to make sure they work well together. Thanks, Emil > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson > Sent: 14 January 2008 16:45 > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] Resin clustered session store > > > On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > > > Hi list, > > > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > > sessions) and I've seen this error a few times in the log file: > > We've made a few fixes to the synchronization/timing of the clustered > session. Some in 3.0.25, but many more in 3.1. > > However, I was never able to reproduce that exact error here, so if > anyone runs into this on 3.1.4 or later, it would be very helpful to > send a bug report on the issue with as much detail as possible. > > -- Scott > > > > > [2008-01-10 11:31:01.379] java.io.EOFException > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream$PeekInputStream.readFully > > (ObjectInputStream.ja > > va:2279) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream$BlockDataInputStream.readShort > > (ObjectInputStre > > am.java:2748) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) > > [2008-01-10 11:31:01.379] at > > java.io.ObjectInputStream.(ObjectInputStream.java:280) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterObject > > $DistributedObjectInputStream. > it>(ClusterObject.java:474) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:286) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.FileBacking.loadSelf(FileBacking.java:318) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterStore.load(ClusterStore.java:423) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:259) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.session.SessionImpl.load(SessionImpl.java:702) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.session.SessionManager.getSession > > (SessionManager.java: > > 1278) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.AbstractHttpRequest.createSession > > (AbstractH > > ttpRequest.java:1444) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.AbstractHttpRequest.getSession > > (AbstractHttp > > Request.java:1256) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.AbstractHttpResponse.writeHeaders > > (AbstractH > > ttpResponse.java:1556) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ResponseStream.writeHeaders > > (ResponseStream. > > java:216) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ResponseStream.writeNext > > (ResponseStream.jav > > a:401) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ToByteResponseStream.flushByteBuffer > > (ToByte > > ResponseStream.java:518) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ToByteResponseStream.flushBuffer > > (ToByteResp > > onseStream.java:424) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ResponseStream.finish > > (ResponseStream.java:6 > > 64) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.ResponseStream.close > > (ResponseStream.java:79 > > 6) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.AbstractHttpResponse.finish > > (AbstractHttpRes > > ponse.java:1956) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.connection.AbstractHttpResponse.close > > (AbstractHttpResp > > onse.java:260) > > [2008-01-10 11:31:01.379] at > > com.caucho.server.webapp.WebAppFilterChain.doFilter > > (WebAppFilterChain.ja > > va:190) > > [2008-01-10 11:
Re: [Resin-interest] Resin clustered session store
Thanks for the response Scott. We did some firewall reconfiguration with regards to connections and sessions and the issue appears to have gone away. I've not tried the 3.1 branch in a while as we found it didn't play well with XFire, but I will upgrade to 3.0.25 ASAP. rgds, Richard -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ferguson Sent: 14 January 2008 16:45 To: General Discussion for the Resin application server Subject: Re: [Resin-interest] Resin clustered session store On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > Hi list, > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > sessions) and I've seen this error a few times in the log file: We've made a few fixes to the synchronization/timing of the clustered session. Some in 3.0.25, but many more in 3.1. However, I was never able to reproduce that exact error here, so if anyone runs into this on 3.1.4 or later, it would be very helpful to send a bug report on the issue with as much detail as possible. -- Scott > > [2008-01-10 11:31:01.379] java.io.EOFException > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$PeekInputStream.readFully > (ObjectInputStream.ja > va:2279) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$BlockDataInputStream.readShort > (ObjectInputStre > am.java:2748) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.(ObjectInputStream.java:280) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject > $DistributedObjectInputStream. it>(ClusterObject.java:474) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:286) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.FileBacking.loadSelf(FileBacking.java:318) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterStore.load(ClusterStore.java:423) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:259) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionImpl.load(SessionImpl.java:702) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionManager.getSession > (SessionManager.java: > 1278) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.createSession > (AbstractH > ttpRequest.java:1444) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.getSession > (AbstractHttp > Request.java:1256) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.writeHeaders > (AbstractH > ttpResponse.java:1556) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeHeaders > (ResponseStream. > java:216) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeNext > (ResponseStream.jav > a:401) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushByteBuffer > (ToByte > ResponseStream.java:518) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushBuffer > (ToByteResp > onseStream.java:424) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.finish > (ResponseStream.java:6 > 64) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.close > (ResponseStream.java:79 > 6) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.finish > (AbstractHttpRes > ponse.java:1956) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.close > (AbstractHttpResp > onse.java:260) > [2008-01-10 11:31:01.379] at > com.caucho.server.webapp.WebAppFilterChain.doFilter > (WebAppFilterChain.ja > va:190) > [2008-01-10 11:31:01.379] at > com.caucho.server.dispatch.ServletInvocation.service > (ServletInvocation.j > ava:229) > [2008-01-10 11:31:01.379] at > com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:274) > [2008-01-10 11:31:01.379] at > com.caucho.server.port.TcpConnection.run(TcpConnection.java:511) > [2008-01-10 11:31:01.379] at > com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520) > [2008-01-10 11:31:01.379] at > com.caucho.util.ThreadPool.run(ThreadPool.java:442) > [2008-01-10 11:31:01.379] at java.lang.Thread.run(Thread.java: > 619) > > The servers are configured to persist sessions across the cluster. On > both servers the siz
Re: [Resin-interest] Resin clustered session store
On Jan 10, 2008, at 4:19 AM, Richard Grantham wrote: > Hi list, > > I'm using Resin Pro 3.0.23 (2 servers, load balanced/distributed > sessions) and I've seen this error a few times in the log file: We've made a few fixes to the synchronization/timing of the clustered session. Some in 3.0.25, but many more in 3.1. However, I was never able to reproduce that exact error here, so if anyone runs into this on 3.1.4 or later, it would be very helpful to send a bug report on the issue with as much detail as possible. -- Scott > > [2008-01-10 11:31:01.379] java.io.EOFException > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$PeekInputStream.readFully > (ObjectInputStream.ja > va:2279) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream$BlockDataInputStream.readShort > (ObjectInputStre > am.java:2748) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) > [2008-01-10 11:31:01.379] at > java.io.ObjectInputStream.(ObjectInputStream.java:280) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject > $DistributedObjectInputStream. it>(ClusterObject.java:474) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:286) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.FileBacking.loadSelf(FileBacking.java:318) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterStore.load(ClusterStore.java:423) > [2008-01-10 11:31:01.379] at > com.caucho.server.cluster.ClusterObject.load(ClusterObject.java:259) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionImpl.load(SessionImpl.java:702) > [2008-01-10 11:31:01.379] at > com.caucho.server.session.SessionManager.getSession > (SessionManager.java: > 1278) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.createSession > (AbstractH > ttpRequest.java:1444) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpRequest.getSession > (AbstractHttp > Request.java:1256) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.writeHeaders > (AbstractH > ttpResponse.java:1556) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeHeaders > (ResponseStream. > java:216) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.writeNext > (ResponseStream.jav > a:401) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushByteBuffer > (ToByte > ResponseStream.java:518) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ToByteResponseStream.flushBuffer > (ToByteResp > onseStream.java:424) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.finish > (ResponseStream.java:6 > 64) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.ResponseStream.close > (ResponseStream.java:79 > 6) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.finish > (AbstractHttpRes > ponse.java:1956) > [2008-01-10 11:31:01.379] at > com.caucho.server.connection.AbstractHttpResponse.close > (AbstractHttpResp > onse.java:260) > [2008-01-10 11:31:01.379] at > com.caucho.server.webapp.WebAppFilterChain.doFilter > (WebAppFilterChain.ja > va:190) > [2008-01-10 11:31:01.379] at > com.caucho.server.dispatch.ServletInvocation.service > (ServletInvocation.j > ava:229) > [2008-01-10 11:31:01.379] at > com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java:274) > [2008-01-10 11:31:01.379] at > com.caucho.server.port.TcpConnection.run(TcpConnection.java:511) > [2008-01-10 11:31:01.379] at > com.caucho.util.ThreadPool.runTasks(ThreadPool.java:520) > [2008-01-10 11:31:01.379] at > com.caucho.util.ThreadPool.run(ThreadPool.java:442) > [2008-01-10 11:31:01.379] at java.lang.Thread.run(Thread.java: > 619) > > The servers are configured to persist sessions across the cluster. On > both servers the size of the DB file is 500M. It doesn't grow or > shrink. > Is this normal? I'm concerned as to what's causing the above error. > The > (hardware) load balancer has been reporting that it has reached it's > maximum number of sessions. Could this be playing a part? > > Any assistance would be appreciated. > > rgds, > > Richard > > > > Richard Grantham > Development > > --- > [EMAIL PROTECTED] > Limehouse Software Ltd > DDI: (020) 7566 3336 > Main: (020) 7566 3320 > Fax: (020) 7566 3321 > Limehouse Software Ltd > 4th Floor > 1 London Bridge > London > SE1 9BG > Manchester Office: > 3rd Floor, The Triangle, Exchange Square, Manchester M4 3TR > Tel: (0161) 240 2440, Fax: (0161) 240 2441, ISDN: 08700 119 400 > Check out Limehouse Software's innovative solutions > www.limehousesoftware.co.uk - Transforming the way you p
