2 Replies Latest reply on Oct 3, 2011 10:11 PM by jboss_practioner

    Jboss esb needs to restart when properties in jbossesb-properties.xml file changed?

    jboss_practioner Newbie

      Hi all,

      I am studying about Jboss esb. I wonder whether the esb server needs to restart everytime the properties in the jbossesb-properties.xml file changed?

      And is there any way that I can configure the properties per application? For example if I want to enable message tracing for only one application, not as a esb-wide property.

        • 1. Re: Jboss esb needs to restart when properties in jbossesb-properties.xml file changed?
          Ryan Hochstetler Newbie

          The short and safe answer:  Yes, it must be restarted every time you wish to make config changes.

           

          The seems to be working for us answer:  You can get a reference to the MainDeployerMBean and call redeploy() on your .esb archive.

           

          The are you sure you want to do this? answer:  If your changes are structural in nature (adding, removing services, adding file gateways), perhaps you should consider whether JBESB is the solution for you.  If your changes are configuration-based (hostnames, timeout values, etc), perhaps you should consider removing these arguments from the jboss-esb.xml file, and providing them to your application through other means.

           

          The jbossesb-properties.xml is a deployer-level file, so I don't think so, but maybe a maintainer can step-in and correct me.  You could implement your own message interceptor, and add it to the chain.  You could then tag messages from one .esb archive with a property that would indicate to the custom interceptor that those messages should be trace-logged.  Of course, cross-deployment-unit message passing might create an over-logging problem.  Trace-logging sounds like it's really, really expensive, btw.  But we have millions of messages a day, so my perspective may be different.