Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
yep, i've had several conversations with the cto of terracotta and they are very on the ball about their products. jon On Thu, Dec 17, 2009 at 11:42 PM, Wesley Wu wumen...@gmail.com wrote: Thanks Jon, I'll definitely give terracotta a try. As far as I know, EHCache was a opensymphony project one or two years ago. I noticed that ehcache was acquired by terracotta and became a key component of terracotta. That's great! -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
[Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0}
com.caucho.hemp.broker.HempMemoryQueue consumeQueue
java.lang.IllegalStateException: WebSocket binary must begin with a
0x80 packet at 0x51 (Q)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.readChunkLength(Hessian2StreamingInput.java:216)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.startPacket(Hessian2StreamingInput.java:142)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hessian.io.Hessian2StreamingInput.startPacket(Hessian2StreamingInput.java:82)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hmtp.HmtpReader.readPacket(HmtpReader.java:86)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.server.cluster.HmuxQueue.authenticate(HmuxQueue.java:258)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.server.cluster.HmuxQueue.openStream(HmuxQueue.java:190)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.server.cluster.HmuxQueue.dispatch(HmuxQueue.java:110)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hemp.broker.HempMemoryQueue.consumeQueue(HempMemoryQueue.java:330)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.hemp.broker.HempMemoryQueue.run(HempMemoryQueue.java:388)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0} at
com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-0}
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1}
com.caucho.hemp.broker.HempMemoryQueue consumeQueue
java.lang.IllegalStateException: WebSocket binary must begin with a
0x80 packet at 0x51 (Q)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.readChunkLength(Hessian2StreamingInput.java:216)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.startPacket(Hessian2StreamingInput.java:142)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hessian.io.Hessian2StreamingInput.startPacket(Hessian2StreamingInput.java:82)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hmtp.HmtpReader.readPacket(HmtpReader.java:86)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.server.cluster.HmuxQueue.authenticate(HmuxQueue.java:258)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.server.cluster.HmuxQueue.openStream(HmuxQueue.java:190)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.server.cluster.HmuxQueue.dispatch(HmuxQueue.java:110)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hemp.broker.HempMemoryQueue.consumeQueue(HempMemoryQueue.java:330)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.hemp.broker.HempMemoryQueue.run(HempMemoryQueue.java:388)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1} at
com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866)
[09-12-18 01:43:05.221] {hmtp-baa-to-aaa-1}
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4}
com.caucho.hemp.broker.HempMemoryQueue consumeQueue
java.lang.IllegalStateException: WebSocket binary must begin with a
0x80 packet at 0x51 (Q)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.readChunkLength(Hessian2StreamingInput.java:216)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hessian.io.Hessian2StreamingInput$StreamingInputStream.startPacket(Hessian2StreamingInput.java:142)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hessian.io.Hessian2StreamingInput.startPacket(Hessian2StreamingInput.java:82)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hmtp.HmtpReader.readPacket(HmtpReader.java:86)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.server.cluster.HmuxQueue.authenticate(HmuxQueue.java:258)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.server.cluster.HmuxQueue.openStream(HmuxQueue.java:190)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.server.cluster.HmuxQueue.dispatch(HmuxQueue.java:110)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hemp.broker.HempMemoryQueue.consumeQueue(HempMemoryQueue.java:330)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.hemp.broker.HempMemoryQueue.run(HempMemoryQueue.java:388)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.util.ThreadPool$PoolThread.runTasks(ThreadPool.java:901)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4} at
com.caucho.util.ThreadPool$PoolThread.run(ThreadPool.java:866)
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-4}
[09-12-18 01:43:35.171] {hmtp-baa-to-aaa-3}
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
this node is using Resin-4.0.s091216 the other is using Resin-4.0.s091202 -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
Wesley Wu wrote: this node is using Resin-4.0.s091216 the other is using Resin-4.0.s091202 The exception itself is a known issue that's blocking 4.0.3, but you also can't mix those two versions. We needed to change the cluster protocol to handle our upcoming EC2 support, and those two snapshots are basically a before-and-after of the change. -- Scott -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
Thanks. I switched back to 091202 snapshot and this issue was resolved. Would u take some time to look at my other mail about @ApplicationScoped bean distribution? -Wesley 2009/12/18 Scott Ferguson f...@caucho.com: Wesley Wu wrote: this node is using Resin-4.0.s091216 the other is using Resin-4.0.s091202 The exception itself is a known issue that's blocking 4.0.3, but you also can't mix those two versions. We needed to change the cluster protocol to handle our upcoming EC2 support, and those two snapshots are basically a before-and-after of the change. -- Scott -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
Wesley Wu wrote: Thanks. I switched back to 091202 snapshot and this issue was resolved. Would u take some time to look at my other mail about @ApplicationScoped bean distribution? I'm pretty sure the distributed events got dropped from the spec. It really was a capability that just didn't belong. In any case, there's never been a distributed bean concept in the spec, just distributed events. -- Scott -Wesley 2009/12/18 Scott Ferguson f...@caucho.com: Wesley Wu wrote: this node is using Resin-4.0.s091216 the other is using Resin-4.0.s091202 The exception itself is a known issue that's blocking 4.0.3, but you also can't mix those two versions. We needed to change the cluster protocol to handle our upcoming EC2 support, and those two snapshots are basically a before-and-after of the change. -- Scott -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
DO NOT USE JBOSS CACHE. Pile of shit. ehcache + terracotta (yes, there is an oss free version) = love. I'm not super clear on what you want, but it sounds like you want the TIM-MasterWorker (ExecutorService): http://forge.terracotta.org/releases/projects/tim-messaging/docs/about.html jon On Thu, Dec 17, 2009 at 11:51 AM, Wesley Wu wumen...@gmail.com wrote: So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
I know that Jon has spent many, many days debugging and tuning JBoss Cache on a production cluster, so I'd endorse his review, despite the brashness. Jeff On Thu, Dec 17, 2009 at 3:37 PM, Jon Stevens latch...@gmail.com wrote: DO NOT USE JBOSS CACHE. Pile of shit. ehcache + terracotta (yes, there is an oss free version) = love. I'm not super clear on what you want, but it sounds like you want the TIM-MasterWorker (ExecutorService): http://forge.terracotta.org/releases/projects/tim-messaging/docs/about.html jon On Thu, Dec 17, 2009 at 11:51 AM, Wesley Wu wumen...@gmail.com wrote: So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
thanks Jon Jeff, lol, I'll take a serious look at ehcache + terracotta. I've used JBossCache for more than 2 years, but only on single JVM (not clustered). I might think the clustered cache should be working as they advertised. -Wesley 2009/12/18 Jeff Schnitzer j...@infohazard.org: I know that Jon has spent many, many days debugging and tuning JBoss Cache on a production cluster, so I'd endorse his review, despite the brashness. Jeff On Thu, Dec 17, 2009 at 3:37 PM, Jon Stevens latch...@gmail.com wrote: DO NOT USE JBOSS CACHE. Pile of shit. ehcache + terracotta (yes, there is an oss free version) = love. I'm not super clear on what you want, but it sounds like you want the TIM-MasterWorker (ExecutorService): http://forge.terracotta.org/releases/projects/tim-messaging/docs/about.html jon On Thu, Dec 17, 2009 at 11:51 AM, Wesley Wu wumen...@gmail.com wrote: So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
Yea, I've been using it for 3 years, clustered. I recently moved to ehcache and all my problems magically went away, I got way better JMX stats and performance increased. That and I configured ehcache in invalidation mode. WAAAY better than replication. jon On Thu, Dec 17, 2009 at 7:05 PM, Wesley Wu wumen...@gmail.com wrote: thanks Jon Jeff, lol, I'll take a serious look at ehcache + terracotta. I've used JBossCache for more than 2 years, but only on single JVM (not clustered). I might think the clustered cache should be working as they advertised. -Wesley 2009/12/18 Jeff Schnitzer j...@infohazard.org: I know that Jon has spent many, many days debugging and tuning JBoss Cache on a production cluster, so I'd endorse his review, despite the brashness. Jeff On Thu, Dec 17, 2009 at 3:37 PM, Jon Stevens latch...@gmail.com wrote: DO NOT USE JBOSS CACHE. Pile of shit. ehcache + terracotta (yes, there is an oss free version) = love. I'm not super clear on what you want, but it sounds like you want the TIM-MasterWorker (ExecutorService): http://forge.terracotta.org/releases/projects/tim-messaging/docs/about.html jon On Thu, Dec 17, 2009 at 11:51 AM, Wesley Wu wumen...@gmail.com wrote: So if I want my beans synchronized across the cluster, I have to use either JMS or some thirdparty cluster middleware like JBossCache? -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
Re: [Resin-interest] HempMemoryQueue Exception when synchronizing sessions between two nodes in a cluster
Thanks Jon, I'll definitely give terracotta a try. As far as I know, EHCache was a opensymphony project one or two years ago. I noticed that ehcache was acquired by terracotta and became a key component of terracotta. That's great! -Wesley ___ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
