Bugs item #824105, was opened at 2003-10-15 15:21
Message generated for change (Comment added) made by koecke
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=824105&group_id=22866
Category: JBoss-IDE
Group: v3.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Bernd Köcke (koecke)
Assigned to: Laurent Etiemble (letiemble)
Summary: JBoss-IDE shuts down foreign server on the same net
Initial Comment:
I'm using Eclipse 2.1.1 with Sun-JDK 1.4.2 JBoss-IDE
1.2.1 on Linux with JBoss 3.2.2RC4
When I use "-s localhost:1199 -S" as program arguments
for shutdown in eclipse, JBoss on another machine in
the same subnet is shutting down. JBoss on my machine
listens on port 1099. And JBoss on the other machine
too. I recognized this while I was playing around with
the binding manager.
It seems that if nobody answers on localhost, JBoss-IDE
tries to connect on the network on the default port. I
checked it with jnp://localhost:1199, my own machine
name instead of localhost and I checked port numbers
1199, 1299, 9090 and 1099 when my machine listens on
port 1199, nothing changes. It happens only, when I use
a URL on which nobody listens on my server.
There are no error messages or exceptions.
----------------------------------------------------------------------
>Comment By: Bernd Köcke (koecke)
Date: 2003-10-17 16:11
Message:
Logged In: YES
user_id=803141
Ok, nowt it works. Thanks a lot! No JBoss is shutting down
in the same net when my machine is not running.
But, where is this documented? I never heared from such a
feature and I think it is really strange. What is it good
for, when I say "shutdown server on localhost" and the
software does "Oh, I doesn't find a local server, try to
shutdown any other server on the net"? :) In my opinion this
feature should be switched off by default.
But with this property all works as expected.
Thanks again and sorry for calling it an IDE-Bug.
----------------------------------------------------------------------
Comment By: Laurent Etiemble (letiemble)
Date: 2003-10-17 10:00
Message:
Logged In: YES
user_id=437455
I think this is not a bug but a feature (in the spirit of
the clustering creators). I agree that it is not obvious.
Explanation :
When no jndi server is found on the target machine, a
multicast signal is sent to find another one on the same
subnet. If another JBoss server is running with clustering
enabled, it answers the request.
To disable this behaviour, you have to add an entry in your
jndi.properties file :
jnp.disableDiscovery=true
It will prevent your client to send a multicast signal.
Tell me if it works and I will close this bug.
----------------------------------------------------------------------
Comment By: Bernd Köcke (koecke)
Date: 2003-10-16 12:28
Message:
Logged In: YES
user_id=803141
Hi all,
A small update:
I could only shutdown JBoss-Server on other machines, if
they have clustering enabled. I can do this from JBoss-IDE
and commandline and I can do it with the smallest command
(bin/shutdown.sh -S) too, when no JBoss is running on my
machine or is not listening on port 1099. My local
JBoss-config has no clustering enabled.
Even it is not a JBoss-IDE bug, I think it is still a bug.
When I call -s localhost:9090, no other host than localhost
should be asked. Or can I configure this behaviour and it is
a bug in my config?
Thanks,
Bernd
----------------------------------------------------------------------
Comment By: Bernd Köcke (koecke)
Date: 2003-10-15 17:07
Message:
Logged In: YES
user_id=803141
Yes, it happens on command line, too.
Sorry should have checked that prior to call it an IDE bug :(.
But now I get the following stack trace:
bin/shutdown.sh -s localhost:9090 -S
17:03:42,571 WARN [NamingContext] Failed to connect to
localhost:9090
javax.naming.CommunicationException: Failed to connect to
server localhost:9090 [Root exception is
javax.naming.ServiceUnavailableException: Failed to connect
to server localhost:9090 [Root exception is
java.net.ConnectException: Connection refused]]
at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:215)
at
org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1181)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:514)
at
org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at
javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:180)
Caused by: javax.naming.ServiceUnavailableException: Failed
to connect to server localhost:9090 [Root exception is
java.net.ConnectException: Connection refused]
at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:190)
... 5 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at
java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:211)
at
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
at
org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
at
org.jnp.interfaces.NamingContext.getServer(NamingContext.java:186)
... 5 more
Shutdown complete
----------------------------------------------------------------------
Comment By: Laurent Etiemble (letiemble)
Date: 2003-10-15 16:48
Message:
Logged In: YES
user_id=437455
Do you have the same behaviour when using the shutdown
script with the same arguments from a command line ?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=824105&group_id=22866
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
