[Installation, Configuration & DEPLOYMENT] - jboss 5.0 migration classloader woes
by mlybarger
So, we're looking to migrate to JBoss AS 5.0. Recently, I ran into a problem where our applications do a lot of:
| URL m_url = this.getClass().getClassLoader().getResource( "WEB-INF" );
| File webinf = new File( m_url.getPath() );
| File newfolder = new File( webinf.getParent(), "newfolder" );
| if ( !newfolder.exists() )
| {
| newfolder.mkdir();
| }
|
In this particular case, the application runs this code on deployment so as to write a bunch of xml files into the newfolder that it creates. The application pulls the data for the xml files from a 3rd entity application (a global caching application, but one that doesn't deal with the xml files needed by this application).
Anyway, the getResource from above was throwing an NPE on jboss 5.0. Looking at the forums and bug list, it seems that the web application at one point had the root folder of the deployed web application in the class path of the class loader that loaded the classes deployed in the web application.
With JBoss AS 5.0, the root folder is no longer on the classpath of the deployed application. Whether or not the J2EE specification explicitly required this feature/behavior, jboss provided it.
We have > 20 hits for code usage like the above. Some of the code is never used in production, but all has to be analyzed to see if it's used, changed and then tested. The change is small, but finding what caused the problem, making the change, then testing the change is where all the time is spent.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199588#4199588
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199588
17 years, 3 months
[JBoss jBPM] - Cancelling action execution
by jjrs
Hi,
We have a JobExecutor running actions in parallel using async='true'. In this scenario, we need to be able to stop the execution of actions (from the command line or the console, it doesn't matter at this stage). If possible I would like to avoid killing the associated java process for being able to report to the database that the action has been stopped by user interaction.
I have been trying to accomplish this requirement using the jBPM console, although all I have been able to achieve is stop the node (so I get a SOE once the action is finished and the and the node information is modified in the database). I have been looking for a way to be able to stop the actions, but I don't see how to do this in an easy way, after having a look to the CancelXXXCommand classes.
Could anyone provide any idea or suggestion?
Thanks a lot in advance.
Jose.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199584#4199584
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199584
17 years, 3 months