[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
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
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
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
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
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
Thanks Jeff Scott
Of course Resin quality stability and performance are the priority also
for me. And for the moment I use simple sql queries instead of Amber.
Amber comes with Resin as many other features like hessian, comet etc. -
all in one. That also makes Resin very attractive and as
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
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,
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
Hi Scott,
sorry to have to let you know that the POST data problem still occurs
randomly
with our applications (http://bugs.caucho.com/view.php?id=3789).
It seems that there are (also) other issues compared to 0003790.
Thanks for the update. It'll be another couple of days before we can
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,
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
___
13 matches
Mail list logo
