SQL binding based timer in SwitchYard does not get updated with new deployment
Issue
- This scenario involves using
SwitchYard SQL bindingwith timer. Timer is triggering just fine. However, after making some changes in the timer configuration ofswitchyard.xmlfile and redploying the application, it is observed that the updated timer value is not reflected at runtime of theSwitchYardapplication. Scheduler service still refers the old application jar. -
The following steps were used in the redeployment process.
1) replace the old jar with new jar via web console
2) remove the old jar and deploy the new one jar via web console
3) placed directly the new jar underjboss-eap-6.1/standalone/deployments/directory
4) deploy and restart the FSW server
5) removed the/tmpfolder to clear the old jar file content from theFSW 6.0.0installation and restart the server -
How to fix this issue?
Environment
- Red Hat JBoss Fuse Service Works (FSW)
- 6.0.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
