[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Changes on the JBM stack on JBoss5

[lovelyliatroim]

Hi Guys,
    Sorry to jump the thread ;) but also having getting the same issue. Tested it with 2.6.5 and the 2.6.6 version set up. I am able to reproduce it consistently. 

Dont know if you have resolved the issue or not but will post details of what i have and if you want more let me know.

What i have is just a 2 node cluster, inside each node i have 2 channels, im not using the multiplexer but setting the "singleton_name" attribute to be the same so both channels share jgroup resources. 

Basically whats happening is this, i have 



  | try{
  | ChannelManager.getChannel().getState(dest, Path1, timeout);
  | ChannelManager.getChannel().getState(dest, Path2, timeout);
  | ChannelManager.getChannel().getState(dest, Path3, timeout);
  | }catch(Exception e){
  | log.error("problem asking older node for its state",e);
  | }
  | 
  | .........
  | ChannelManager.broadcastMessage(msg);
  | 

Now whats happening is, the exception gets thrown and is caught and printed but as soon as i try to do the "broadcastMessage" it hangs and my whole thread goes into wait state.
Here is the thread dump.



  | "LiveFeed_ConnectionHandler 1" daemon prio=3 tid=0x0983cc00 nid=0x51 in Object.wait() [0x7817e000..0x7817eaf0]
  |    java.lang.Thread.State: WAITING (on object monitor)
  |         at java.lang.Object.wait(Native Method)
  |         - waiting on <0x7ed443e0> (a java.lang.Object)
  |         at java.lang.Object.wait(Object.java:485)
  |         at org.jgroups.protocols.pbcast.FLUSH.blockMessageDuringFlush(FLUSH.java:300)
  |         - locked <0x7ed443e0> (a java.lang.Object)
  |         at org.jgroups.protocols.pbcast.FLUSH.down(FLUSH.java:254)
  |         at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:475)
  |         at org.jgroups.JChannel.down(JChannel.java:1452)
  |         at org.jgroups.JChannel.send(JChannel.java:625)
  | 
  | 

What is getting transfered is this, i am using jboss cache, and ask another node to transfer a branch, this branch that i get this exception on has 260,000 records with each record containing about 10 fields. I havent seen the exception with smaller branches, just this one.


if you want anymore information let me know, if you think you have a fix let me know, i will check it out and see if it works for my scenario.

Cheers,
LL








View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188923#4188923

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4188923