Saturday, November 14, 2009

JBoss 5

I've recently migrated AtTask from JBoss 4 to JBoss 5. We've were running on JBoss 4 for the past 2 years and we want to take advantage of the new rewrite of JBoss Messaging, JBossMQ has problems and we are hoping JBoss Messaging solves these problems. What I can't figure out is why in JBoss 5 the server peer id must be set for every node. Why can't JBoss automatically generate a unique id. I know in JBoss 4 I didn't have the set the server peer id. The other thing that is frustrating is this unique server peer id has to been queue across the LAN. We have two clusters on the same LAN with different cluster partitions and they won't work unless every node has a unique server peer id.

No comments:

Post a Comment