[jboss-dev-forums] [Design of JBoss Transaction Services] - Re: TransactionManager and AS' ServiceBindingManager

[wolfc]

All in all this thing should never communicate with SBM in the first place.
It's not some network service which AS provides. It's a hack around a JVM limitation. There are no real configuration options, because the option should actually be called: process id. So running two JBoss AS instances on one machine with the same 'process id' results in an error.

I think transaction-jboss-beans.xml should just be configured with a '0' setting => go figure out your own process id. The fact that this must happen via a localhost socket hack is an implementation detail. (Note that this not invalidate JBTM-406.) If anyone would configure one instance to use another interface it would screw things up badly. If anyone would preconfigure a port and do two micro startups, it would screw up as well. So no configuration is the best way out.

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

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