[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3475) New deployment mechanism not working correclty on clustered or multi-server envs.

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12448213#action_12448213 ] 

Rob Stryker commented on JBIDE-3475:
------------------------------------

I've tested this with a simple -ds.xml file only so far, but in all attempts, it is DEPLOYING to the proper folder (_2, _3), and in addition to that, only the PROPER SERVER's console is showing any output.  Here's my attempt so far. I admit I've not gotten to using your exact setup, but the issues here are basically, 1) is the proper server reading the proper deploy folder or not, and 2) is the data being deployed to the proper deploy folder. 

Using two JBoss 4.2.2.GA server objects, set up exactly as you said with lo2 and lo3:

Step 1: start lo2_server
Step 2: deploy xml file to lo2_server
Step 3: Observe:

          19:22:10,774 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 23s:583ms
          19:27:17,827 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=Z_TESTDatasource' to JNDI name 'java:Z_TESTDatasource'

Step 4: Go to server1's JMX page and get a list of deploy folders, verify only ONE .metadata location is added  (jboss.deployment:type=DeploymentScanner,flavor=URL   operation name = listDeployedURLs):

         file:/home/rob/apps/eclipse/workspaces/jbidetest/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/Z_TEST-ds.xml

Step 5: Start lo3 server
Step 6: Deploy xml file to lo3 server
Step 7: Observe proper console shows output

         19:28:31,252 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 1m:3s:658ms
         19:28:51,522 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=Z_TESTDatasource' to JNDI name 'java:Z_TESTDatasource'



Step 8: Verify lo2 console did *NOT* show any additional output during the deployment to lo3

          19:22:10,774 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 23s:583ms
          19:27:17,827 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=Z_TESTDatasource' to JNDI name 'java:Z_TESTDatasource'


Step 9: Check via JMX on lo3 server that only one .metadata location is added, and that it is DIFFERENT than the one in step 4 (See step 4)

file:/home/rob/apps/eclipse/workspaces/jbidetest/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server_(1)/deploy/Z_TEST-ds.xml

Step 10: Verify via JMX on lo2 that only one metadata location is STILL there. 
         file:/home/rob/apps/eclipse/workspaces/jbidetest/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_4.2_Server/deploy/Z_TEST-ds.xml




It is quite clear to me that, at least for JBoss 4.2.2.GA, the server's are definitely distinct, and they are NOT overlapping at all. To be honest, your judgement is being made entirely on a log file "node1/server.log", a log file which I can't see ANYWHERE in my installation. Maybe I don't know how virtual host log files are kept separate. 

jboss-4.2.2.GA/server/default/log only has boot.log, server.log, and versions of server.log with dates. I do not see a folder "node1" anywhere, nor do I see a folder node2, lo2, lo3, or anything that might indicate separate server logs. 

Admittedly I am not testing this with a full ear project, but I think the evidence here is pretty conclusive that the servers are distinct, that each server has its own deployment location, that the consoles themselves are not overlapping or receiving deployments when they should be going to the other. The console output with its timestamps show that nothing unusual is going on. 

The only evidence you bring are some specific log files you mention but I cannot find anywhere on my computer. 



> New deployment mechanism not working correclty on clustered or multi-server envs.
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-3475
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3475
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.CR2
>            Reporter: Galder Zamarreno
>            Assignee: Snjezana Peco
>            Priority: Blocker
>             Fix For: 3.0.0.CR2
>
>         Attachments: acme-haejb2.jar, jbide3475.zip
>
>
> There's something not working correctly with the new deployment mechanism:
> I have a cluster of 2 nodes with an clustered EJB3 application deployed (SLSBs, SFSBs, Entities...etc). 
> When I start the 1st node, it works perfectly and after startup being completed, ear is deployed without
> any issues. 
> After deployment is complete, I start the 2nd node and the EJB3 application is deployed again in the 1st
> node and the 2nd node has no deployment whatsoever.
> See attached logs + ear app.

-- 
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