Hi,
I have done some tests like the exemples distribueted. In my fail over test I
have make 2 clustered istances of Jboss 4.2.2 + JBM 1.4.0 SP1 and I have sended
100 messages in to node 1. In my condition test the balancer have put all (!?)
messages in node 2 and afther few second I have manualy
Node 2 works in a PC with XP Windows. For simulate crash, I have killed Jboss
by task manager. Node 1 works in a PC with Linux. If necessary, I can repeat
the test with stop Node 1.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109169#4109169
Reply to the p
At moment I work to porting in prodution the clustering configuration. Monday,
I hope, I will rerun the test. Bye
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109186#4109186
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
Hi,
in my production enviroment ( jboss 4.2.2 GA, jboss messaging 1.4.0.SP3, JBoss
Remoting 2.2.2.SP3 on Red Hat 2.6.9 ) I have a lot of errors equals this:
2007-12-19 09:49:32,829 ERROR
[org.jboss.remoting.transport.socket.ServerThread] Worker thread initialization
failure
| java.io.EOFExcep
Done. This is the result:
2007-12-21 11:29:42,956 DEBUG [org.jboss.remoting.ServerInvoker]
SocketServerInvoker[UNINITIALIZED] stopped
...
2007-12-21 11:29:42,956 DEBUG [org.jboss.remoting.Client] starting callback
Connector: InvokerLocator
[bisocket://10.0.1.21:1035918315/callback?guid=a01l-yo1
