Redployment with new paramater from SystemPropertiesService

[garuda]

Hello experts,

I defined the following test-properties-service.xml, injecting an mbean for "org.jboss.varia.property.SystemPropertiesService"

<?xml version="1.0" encoding="UTF-8"?>
<server>
 <mbean code="org.jboss.varia.property.SystemPropertiesService"
 name="ach.properties:type=Service,name=TestProperties">
 <attribute name="Properties">
 test_parameter=/incoming_test
 </attribute>
 <attribute name="Properties">

 </mbean>
</server>

I use "test_parameter" in a service located in test.esb as filesystem lister value. See jboss.esb:

<fs-message-filter
 directory="${test_parameter}/in"
 error-delete="false"
 error-directory="${test_parameter}/err"
 error-suffix=".err" input-suffix=".txt" post-delete="true"
 post-directory="${test_parameter}/archive"
 post-suffix=".done" work-suffix=".work"/>

My main service test.esb has a deployment dependency on "ach.properties:type=Service,name=TestProperties".
My deployment.xml:

<jbossesb-deployment>
...
 <depends>ach.properties:type=Service,name=TestProperties</depends>

...
</jbossesb-deployment>

When I now change the value of parameter "test_parameter" to "/incoming_live" e.g. in my test-properties-service.xml, I would expect that
1) Re - deployment of test-properties-service.xml
2) Re - deployment of test.esb with new parameter test_parameter = "incoming_live"

Re - deployment of test-properties-service.xml succeeds. I checked these properties in JMX. Test.esb re - deploys aswell, but not with the new parameter settings, but the old one. I checked the service in JMX MBEan View in JMX-Console I can only see the old configuration.

Can you please help ? Why doesn't test.esb redeploy with new parameters?



Best regards,

Dennis

[garuda]

Hello again,

no idea about that theme ?

Br,

Dennis

[beve]

Hi,

<?xml version="1.0" encoding="UTF-8"?>
<server>
 <mbean code="org.jboss.varia.property.SystemPropertiesService"
 name="ach.properties:type=Service,name=TestProperties">
 <attribute name="Properties">
 test_parameter=/incoming_test
 </attribute>
 <attribute name="Properties">

 </mbean>
</server>

That xml should not be valid as the second attribute element does not have a closing tag. Was that perhaps just an error when pasting the example in your post?

Regards,

/Daniel

[beve]

Hi Dennis,

I've tried this locally and this works for me. Let me know how you get along with this issue. I can send you the modified quickstart that I'm using in case that would help you.

I wonder if this is something that a lot of users need. Perhaps we should add this to one of the quickstarts. What do you think?

Regards,

/Daniel

[garuda]

Hi Daniel.

Sorry, it was just an error when pasting the example.

What do you mean by "I've tried this locally and this works for me" ?

If you only change parameter "test_parameter" in test-properties-service.xml, this will lead to redeployment of test.esb with new parameter settings ?

Br,

Dennis

[kconner]

This is a consequence of the way in which the deployer currently works and is arguably a bug. I'll create an issue to address this but it may take some time to fix.

Kev

[garuda]

Hello Kevin.

Thank you very much for your help.

Br,

Dennis

[kconner]

I have created https://jira.jboss.org/jira/browse/JBESB-2874 but there should be a simple workaround, touching the .esb (or jboss-esb.xml file) should force a redeploy with the new properties.

Kev