[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- node1/server1.log: server.log:5763:2008-12-31 16:01:08,462 33229 INFO [org.jboss.ejb3.EJB3Deployer] (ScannerThread:) Deployed: file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-251304_1/deploy/acme-haejb3.jar ... server.log:5956:2008-12-31 16:01:08,586 33353 INFO [org.jboss.ejb3.EJB3Deployer] (ScannerThread:) Deployed: file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-251304_2/deploy/acme-haejb3.jar Second deployment should have gone to node2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- If 2nd server is started while 1st is starting up, it all works fine. If you wait for 1st server to finish startup before starting the 2nd, then the mentioned issue occurs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Snjezana Peco reassigned JBIDE-3475: ------------------------------------ Assignee: Snjezana Peco (was: Rob Stryker) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3475: ------------------------------------ judging by the deploy folders listed, it's DEPLOYING it to the right place... (_1 vs _2) but the first server is listening to the wrong folder... or to both?? That seems very weird. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- Rob, I've verified latest trunk and still does not work. Very easy to replicate: 1. Download eclipse-jee-ganymede-SR1-linux-gtk.tar.gz 2. Install latest from http://download.jboss.org/jbosstools/updates/nightly/trunk 3. Create two runtime+servers from EAP 4.3.0.GA_CP03, one called jbide3475_1 and the other jbide3475_2 based on 'all' configuration. 4. Double click on 4.3.0.ga.cp03-jbide3475_1 and change hostname to lo2 (see "Setting up a cluster with localhost addresses" section from http://www.jboss.org/community/docs/DOC-10211) 5. Double click on 4.3.0.ga.cp03-jbide3475_2 and change hostname to lo3 (see "Setting up a cluster with localhost addresses" section from http://www.jboss.org/community/docs/DOC-10211) 6. Click on "Open Launch configuration" for 4.3.0.ga.cp03-jbide3475_2 and add -Djboss.messaging.ServerPeerID=1 VM argument. 7. Take the attached .jar and deploy it in 4.3.0.ga.cp03-jbide3475_1 first and wait for the server to finish starting up. 8. Start 4.3.0.ga.cp03-jbide3475_2 and you'll see the phenomenon explained. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- By the way, wiped my .metadata/ folder as well and made no difference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Rob Stryker commented on JBIDE-3475: ------------------------------------ Also: [rob@localhost org.jboss.ide.eclipse.as.core]$ pwd /home/rob/apps/eclipse/workspaces/jbidetest/.metadata/.plugins/org.jboss.ide.eclipse.as.core [rob@localhost org.jboss.ide.eclipse.as.core]$ ls JBoss_4.2_Server/deploy/ Z_TEST-ds.xml [rob@localhost org.jboss.ide.eclipse.as.core]$ ls JBoss_4.2_Server_\(1\)/deploy/ Z_TEST-ds.xml [rob@localhost org.jboss.ide.eclipse.as.core]$ ls JBoss_4.2_Server/deploy/ Z_TEST-ds.xml [rob@localhost org.jboss.ide.eclipse.as.core]$ ls JBoss_4.2_Server_\(1\)/deploy/ Z_TEST-ds.xml Both folders have the output. And as shown above, each server only has 1 metadata location listed in its deployment urls -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno updated JBIDE-3475: ------------------------------------ Attachment: 20090116.zip -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-3475: ------------------------------- Attachment: mainOutput.txt The output of the above java file, once run. Note it fails because it cannot make a connection on lo3. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-3475: ------------------------------- Attachment: server.log The server log file, showing clearly at line 6755 that shutdown was called, somehow, magically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-3475: -------------------------------------- I can't reproduce this issue. Suppose that some additional settings needs to be done. When I try to deploy acme-haejb3.jar to workspace/.metadata or to the server's deploy folder, it is always deployed to only one node. If I deploy acme-haejb3.jar to the server/all/farm folder, it is depoyed/undeployed automatically to the both servers no matter when they were started. It is possible to deploy some Seam WAR project in the following way: - create two servers on two network nodes as described in https://jira.jboss.org/jira/browse/JBIDE-3475?focusedCommentId=12448062#a... - set deploy directory to server/all/farm - create a Seam WAR project - deploy *_ds.xml and do not deploy the project - open the Project Archives view - create a WAR archive - deploy the archive to any of these two servers The project will be deployed to the both nodes. I have used 4.3.0.GA_CP03 (build: SVNTag=JBPAPP_4_3_0_GA_CP03 date=200810241616). I couldn't create any EAR project archive due to an exception I got when I tried to create it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- By the way, deployment is done via "Add/Remove Project..." via the GUI, nothing to do with copying files around. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Galder Zamarreno commented on JBIDE-3475: ----------------------------------------- Rob, Re: 3) Use the attached JAVA file (modify it of course) to attempt to use JMX to SHUTDOWN a server on lo3. Remember, there is NO server running on lo3 currently. The only server running is on lo2. I believe what is happening is that when lo3 is not accessible, auto discovery kicks in: "If the property string java.naming.provider.url is empty or if all servers it mentions are not reachable, the JNP client will try to discover a bootstrap HA-JNDI server through a multicast call on the network (auto-discovery). " So, lo2 would reply to JNDI multicast discovery and hence that's how the shutdown call lands on lo2. http://docs.jboss.com/jbossas/guides/clusteringguide/r2/en/html_single/#c... Here's a more detailed client log for you to inspect: 2009-01-20 19:19:51,093 1 DEBUG [org.jnp.interfaces.NamingContext] (main:) Failed to connect to lo3:1099 javax.naming.CommunicationException: Failed to connect to server lo3:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server lo3:1099 [Root exception is java.net.ConnectException: Connection refused]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:274) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1533) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:634) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627) at javax.naming.InitialContext.lookup(InitialContext.java:351) at com.acme.jmx.ShutdownTest.test000(ShutdownTest.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server lo3:1099 [Root exception is java.net.ConnectException: Connection refused] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:248) ... 21 more Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:520) at java.net.Socket.connect(Socket.java:470) at java.net.Socket.<init>(Socket.java:367) at java.net.Socket.<init>(Socket.java:267) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84) at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77) at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:244) ... 21 more 2009-01-20 19:19:51,099 7 TRACE [org.jnp.interfaces.NamingContext] (main:) TTL on multicast discovery socket is 16 2009-01-20 19:19:51,099 7 TRACE [org.jnp.interfaces.NamingContext] (main:) MulticastSocket: java.net.MulticastSocket@f0c0d3 2009-01-20 19:19:51,099 7 TRACE [org.jnp.interfaces.NamingContext] (main:) Sending discovery packet(GET_ADDRESS) to: /230.0.0.4:1102 2009-01-20 19:19:51,102 10 TRACE [org.jnp.interfaces.NamingContext] (main:) Received answer packet: 127.0.0.2:1100 2009-01-20 19:19:51,219 127 TRACE [org.jboss.ha.framework.interfaces.HARMIClient] (main:) Init, clusterInfo: org.jboss.ha.framework.interfaces.FamilyClusterInfoImpl@2f549848{familyName=DefaultPartition/HAJNDI,targets=[HARMIServerImpl_Stub[UnicastRef2 [liveRef: [endpoint:[lo2:1101](remote),objID:[-606492d7:11ef5448e9a:-7fe8, 9137209410287297649]]]]],currentViewId=-7315973,isViewMembersInSyncWithViewId=false,cursor=999999999,arbitraryObject=null}, policy=org.jboss.ha.framework.interfaces.RoundRobin@e1899b 2009-01-20 19:19:51,222 130 TRACE [org.jboss.ha.framework.interfaces.HARMIClient] (main:) Invoking on target=HARMIServerImpl_Stub[UnicastRef2 [liveRef: [endpoint:[lo2:1101](remote),objID:[-606492d7:11ef5448e9a:-7fe8, 9137209410287297649]]]] 2009-01-20 19:19:51,303 211 DEBUG [org.jboss.security.SecurityAssociation] (main:) Using ThreadLocal: false 2009-01-20 19:19:51,305 213 TRACE [org.jboss.security.SecurityAssociation] (main:) getPrincipal, principal=null This needs to be taken into account when deploying something, you should be using the hostname of the server to hit that server and avoid your deploy call landing on a different node due to naming url host not being available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-3475: -------------------------------------------- never mind - google told Rob: .setProperty("jnp.disableDiscovery", "true"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-3475. -------------------------------- Resolution: Done I've tested again using the same setup Galder helped me set up where I previously reproduced his error exactly. I am not seeing the behavior I was before. I am strongly confident this issue is resolved. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira