[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6161) ESB Projects stall on start

Brian Fitzpatrick (JIRA) jira-events at lists.jboss.org
Mon Apr 12 19:04:06 EDT 2010


     [ https://jira.jboss.org/jira/browse/JBIDE-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fitzpatrick updated JBIDE-6161:
-------------------------------------

    Attachment: JbrEsb.esb


Comments from Aaron Pestel:

"Very sorry, I didn't read my own support case well enough.  This was on
SOA-P 4.3 CP02.  I would have to create a different .esb to get the
problem on SOA-P 5 since I think they removed the dependence of the JBR gateway on Smooks in SOA-P 5.

I just tested this to make sure it still happens:

1.)  Start SOA-P 4.3 CP02 "default" server and wait for it to come up
2.)  Drop the JbrEsb.esb in the default/deploy directory
3.)  Verify that it starts deploys successfully
4.)  Stop the SOA-P server (leaving the .esb file in the deploy directory)
5.)  Start the SOA-P server again
6.)  Note that it gets an exception when trying to deploy the
JbrEesb.esb that we just saw deploy successfully

The problem is that the JbrEsb.esb is getting deployed (or maybe
started) before jbossesb.esb, smooks.esb, etc.

Now support said that's because the JbrEsb.esb doesn't declare
dependencies on smooks.esb, etc.  The problem is that if you look in
the JbrEsb.esb file, you'll find there is nothing there about Smooks -
so how would the JBDS user know to do that?  The user won't know that
the JBR Gateway implicitly depends on smooks (in SOA-P 4.3 CP02).  My
point is that since this ESB project (that created the .esb) was created
in JBDS, probably JBDS should (could) have automatically added
dependencies on the core .esb deployments since the user is not going to know that JBR (for example) implicitly depends on Smooks.  This assumes that the support folks are right that this will fix the problem.

Again, this is just one concrete manifestation.  I didn't even follow
through with the support case to see if adding a dependency.xml file to
the project (ultimately .esb file) or not."

> ESB Projects stall on start
> ---------------------------
>
>                 Key: JBIDE-6161
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-6161
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.GA
>            Reporter: Gary Lamperillo
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.1.1
>
>         Attachments: hang_myESBXML.png, JbrEsb.esb, myESB.esb, myJSR181.war
>
>
> When developing an Application ESB, the ESB archive works fine when it is deployed last, but on server restarts the archive hangs.  It appears there are dependencies not being met for Application ESB.  When a ESB Project is created a deployment.xml should be added to the META-INF which adds all the dependencies.

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