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

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Fri Jan 16 03:56:04 EST 2009


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

Galder Zamarreno commented on JBIDE-3475:
-----------------------------------------

Rob:

Re: 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.

There's no such folder as node1 in your installation. That's me sorting the different server's log files into separate 
directories to upload them to the support case. These logs are located in server/<config>/log/server.log.

How do I deploy the datasource that you're refering to? When I click "Add/Remove Projects", I can only see the project 
archives I've created. I dunno how to deploy a datasource that way.

In the mean time, I'd suggest that you try deploying the provided jar via "Add/Remote Projects" and see if still works fine 
for you.

Having looked at my .metadata/.plugins/org.jboss.ide.eclipse.as.core/ , I can see two different folders for each server with 
each containing the deployed jar in the deploy/ directory

.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-jbide3475_1/deploy/acme-haejb2.jar
.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-jbide3475_2/deploy/acme-haejb2.jar

On top of that, I'also found log files under .metadata/.plugins/org.jboss.ide.eclipse.as.core/<server>/log. I'm attaching them 
for you to inspect.

I'm reattaching the server.log files for you to inspect server.<config-name>.server.log. It's clear from them that jbide3475_1 is 
deploying the same jar twice.

server.jbide3475_1.server.log:13275:2009-01-15 16:46:29,424 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-jbide3475_1/deploy/acme-haejb2.jar
server.jbide3475_1.server.log:13778:2009-01-15 16:46:40,733 DEBUG [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/home/galder/jboss/sandbox/git/.metadata/.plugins/org.jboss.ide.eclipse.as.core/4.3.0.ga.cp03-jbide3475_2/deploy/acme-haejb2.jar

If there's any other extra information or logging you'd want me to enable, please let me know.

> 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

        



More information about the jbosstools-issues mailing list