roq-messaging / RoQ

RoQ, Elastically scalable MOM
21 stars 4 forks source link

Bug in moving request #135

Closed sskhiri closed 11 years ago

sskhiri commented 11 years ago

In Test117b, the moving request failed during a local test: 20:44:53,217 DEBUG Thread-154 - Do we need to relocate ? 20:44:53,217 DEBUG Thread-154 - Is 265514032 > 82500000 20:44:53,218 INFO Thread-154 - Relocating for load optimization on 192.168.1.12:6004 20:44:53,218 DEBUG Thread-154 - relocating 66ecca0a-808e-44ce-a3b7-e9631d49c507 on 192.168.1.12:6004 20:44:53,218 INFO Timer-0 - CPU usage this last minute: 0.5 20:44:53,218 INFO Timer-0 - Current memory 23.6875 Mo on 118.8125 Mo 20:44:53,218 INFO Thread-167 - Sending a de-connect event to exchange 20:44:53,296 INFO Thread-1 - Successfully removed publisher 66ecca0a-808e-44ce-a3b7-e9631d49c507 remains 3 publishers. 20:44:53,297 INFO Thread-167 - 66ecca0a-808e-44ce-a3b7-e9631d49c507 Succesfully disconnected from exchange. 20:44:53,297 INFO Thread-167 - The Request exchange address is: tcp://192.168.1.12:6007 20:44:53,299 INFO Thread-167 - Re-allocation order - Moving to 192.168.1.12:6004 Exception in thread "Loader Publisher" org.zeromq.ZMQException: Socket operation on non-socket(0x58) at org.zeromq.ZMQ$Socket.send(Native Method) at org.zeromq.ZMQ$Socket.send(ZMQ.java:1222) at org.roqmessaging.core.PublisherClient.sendMessage(PublisherClient.java:57) at org.roqmessaging.loaders.SenderLoader.run(SenderLoader.java:99) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505)