tag:blogger.com,1999:blog-1375633167426904536.post3734669107196019629..comments2023-12-21T10:45:27.103+00:00Comments on The Impala Blog: The granularity of change in dynamic Java web applicationsPhil Zoiohttp://www.blogger.com/profile/06867992322338887577noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-1375633167426904536.post-59396785969720492772009-12-23T16:08:22.349+00:002009-12-23T16:08:22.349+00:00Petr,
Have you tried using the staging directory ...Petr,<br /><br />Have you tried using the staging directory approach.<br /><br />Into impala.properties, add <br />auto.reload.monitoring.type=stagingDirectory<br /><br />and <br /><br />use.touch.file=true<br /><br />You can then place the replacement jar in /WEB-INF/staging<br /><br />When you want to trigger reloading. then save touch.txt in /WEB-INF/modules<br /><br />The change in the touch file will trigger reloading of the jar from the staging directory.<br /><br />Hopefully you won't get any locking issue as the IO ops will take place within the Tomcat process.<br /><br />Let me know if this works (preferably on the user mailing list if possible).Phil Zoiohttps://www.blogger.com/profile/06867992322338887577noreply@blogger.comtag:blogger.com,1999:blog-1375633167426904536.post-72765562258849246842009-12-23T15:39:36.906+00:002009-12-23T15:39:36.906+00:00Phil, thanks for aswer. My problem is that when I&...Phil, thanks for aswer. My problem is that when I'm runnig the modules on Tomcat, I can't replace the module jar (WEB-INF/modules/.jar), because it is locked (opened) by the tomcat process. How can I solve this?Petr Nevarilnoreply@blogger.comtag:blogger.com,1999:blog-1375633167426904536.post-71624594095735985362009-12-23T10:18:31.852+00:002009-12-23T10:18:31.852+00:00Petr,
Yes, you can replace the module jar at runt...Petr,<br /><br />Yes, you can replace the module jar at runtime. You will need to property 'auto.reload.modules=true' set in impala.properties. There are a few other options you can set: whether to use a staging directory, whether to use a 'touch.file' to trigger reloads, etc.<br /><br />See again the 'auto.reload' properties in <a href="http://code.google.com/p/impala/wiki/PropertyConfiguration" rel="nofollow">http://code.google.com/p/impala/wiki/PropertyConfiguration</a><br /><br />You can also use JMX to trigger a reload of a modified jar.<br /><br />Cheers,<br />PhilPhil Zoiohttps://www.blogger.com/profile/06867992322338887577noreply@blogger.comtag:blogger.com,1999:blog-1375633167426904536.post-82648203997801571132009-12-23T09:21:19.181+00:002009-12-23T09:21:19.181+00:00How is it with modification of module in productio...How is it with modification of module in production environment (when module is deployed as jar on Tomcat in its WEB-INF/modules directory)? Is it possible to somehow replace the module jar at runtime?Petr Nevarilnoreply@blogger.comtag:blogger.com,1999:blog-1375633167426904536.post-21017872508018833212009-11-14T11:13:21.383+00:002009-11-14T11:13:21.383+00:00Mohamed
You can have it either way. If you set a ...Mohamed<br /><br />You can have it either way. If you set a property called 'auto.reload.modules', which if true will reload modules automatically. <br /><br />See <a href="http://code.google.com/p/impala/wiki/PropertyConfiguration" rel="nofollow">http://code.google.com/p/impala/wiki/PropertyConfiguration</a> for more details.<br /><br />Alternatively, you can trigger module reloading manually through a JMX interface. An admin console is planned, but does not exist yet.<br /><br />PhilPhil Zoiohttps://www.blogger.com/profile/06867992322338887577noreply@blogger.comtag:blogger.com,1999:blog-1375633167426904536.post-2848376170765245002009-11-13T22:40:38.195+00:002009-11-13T22:40:38.195+00:00so how is the developer experience like, does impa...so how is the developer experience like, does impala automatically reload the modifications or does the developer need to trigger a reload, manually specifing what is it exactly to be reloaded?Anonymoushttps://www.blogger.com/profile/07665782947470972925noreply@blogger.com