I addition I tested running 2 instances on 1 machine with binding manager.
The behaviour does not change. The deployment of clustered SLSBs takes very long time on the 2nd instance, while the logfiles (JGroups trace, jboss debug) show no errors or warnings. So network issues are not the reason.
The time is taken after the SecurityProxy initialization messages. What happens at that point?
When I stop the first instance in this phase, the startup of the second instance returns to "normal speed".
Please can someone give me a hint, what is happening at this point behind the scenes. Has someone seen similar effects?
I figured it out. The reason for that behaviour was a system property "java.naming.provider.url" (node1:100,node2:1100) set on the server.