-
1. Re: more than one standalone running in the same machine problem
morphy Feb 13, 2012 4:44 PM (in response to morphy)-Djboss.socket.binding.port-offset=xxx works and both instances start
bye
-
2. Re: more than one standalone running in the same machine problem
jbertram Feb 13, 2012 4:46 PM (in response to morphy)Are both 192.168.1.99 and 192.168.1.98 real interfaces (e.g. they show up when you run
ifconfig
)? -
3. Re: more than one standalone running in the same machine problem
morphy Feb 13, 2012 4:59 PM (in response to jbertram)Mmmmm no, they are 2 ip on the same interface:
ifconfig
....
wlan0 Link encap:Ethernet HWaddr 00:08:54:AC:49:D5
inet addr:192.168.1.99 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
RX packets:321745 errors:0 dropped:0 overruns:0 frame:0
TX packets:508057 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:53407155 (50.9 Mb) TX bytes:279990492 (267.0 Mb)
wlan0:me2 Link encap:Ethernet HWaddr 00:08:54:AC:49:D5
inet addr:192.168.1.98 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING ALLMULTI MULTICAST MTU:1500 Metric:1
but... i was used to use this workaround, in the past...
-
4. Re: more than one standalone running in the same machine problem
jaikiran Feb 14, 2012 12:14 AM (in response to morphy)Riccardo Pasquini wrote:
-Djboss.socket.binding.port-offset=xxx works and both instances start
bye
That is the right solution. Starting multiple instance bound to the same IP means you have to take care of port conflicts by setting that offset.