0 Replies Latest reply on Apr 6, 2009 6:22 AM by peter craddock

    seperate log4j config for my application

    peter craddock Novice

      I wish to deploy several apps into the container and have each one have there own log file.

      I have managed to do this with a spring application no problem and I have had limited success with a ejb2 application but I feel that this is a problem that should be covered in more detail in the docs (We are using 4.2.3AS).

      To get my ejb2 app to use its own log file I had to implement a RepositorySelector but this only seems to work on the calls to get logger in the web application the ejb tier is still logging to the main log file. The app is set up so the classpath is set in the ejb.jar and I have no jars in the war file except the ones that are available for download for the applet and jnlp parts of the app.

      I attempted to use the isolation and use my own classloader but this caused many more problems when the container was parsing the xml config files. From viewing the new loader in the JMX viewer you can see the container jar files are still loaded.

      I tried repackaging the apps to get round the loader problem but this did not seam to work.

      If anyone has any worked examples of how to achieve this that would be great.