log4j conflicts in Jboss

[Mike Ahlers]

Hi,

I am deploying an ear into Jboss, but at the moment that fails. Now, that is something that can be fixed, but having no logs available makes that really hard. The error I am getting is:

ERROR: invalid console appender config detected, console stream is looping

I was wondering if anyone has this problem before, and better, solved it! What I did so far is:

- wrapping the war (basically standard ops 3.6.0) into an ear, and deployed it in jboss (4.2.2 ga).
- configured the jboss-web.xml with the java2ClassLoadingCompliance='false', following the recommendation mentioned in the installation guide (plus the rest, matching the war name).
- removed the log4j and the commons-logging jars from the library as they are provided by jboss itself (to avoid class loading conflicts)
- Added the following option in the config script (jboss), as this is recommended as well:
    JAVA_OPTS="-Dorg.jboss.logging.Log4jService.catchSystemOut=false $JAVA_OPTS"

But, still, I am getting this error :/

Anyone who can help me with this? Thanks in advance,

Mike

[Mike Ahlers]

Update on this issue:

Jboss does NOT honor the settings as recommended:

2008-07-09 10:55:28,747 WARN  [org.jboss.deployment.DeploymentInfo] Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: cis-web-1.0.0.war:loader=cis-web-1.0.0.war, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)

Another observation, the application is running as expected so it is deployed correctly, and it seems the only problem is the logging itself. I made the assumption it wasn't because I saw nothing!

Regards,
Mike

[Mike Ahlers]

Hi,

Got it solved. All that is needed (none of the above is needed) is to have a file called jboss-app.xml at ear-level (META-INF), so it looks like:

<jboss-app>
  <loader-repository>cis-1.0.1.ear:loader=cis-1.0.1.ear</loader-repository>
</jboss-app>

Or, in my case, I let maven generate it (inside config of ear-plugin):

<jboss>
    <version>4</version>
    <loader-repository>${project.artifactId}-${project.version}.ear:loader=${project.artifactId}-${project.version}.ear</loader-repository>
</jboss>

So I don't need to worry about naming and versioning, since Maven will automatically pick it up.

Regards,
Mike Ahlers

[Alessandro Vernet]

Mike,

On Wed, Jul 9, 2008 at 7:20 AM, Mike Ahlers
<[hidden email]> wrote:
> Got it solved. All that is needed (none of the above is needed) is to have a
> file called jboss-app.xml at ear-level (META-INF), so it looks like:
> [...]

Good find! Thank you for sharing this back with us.

Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog: http://www.orbeon.com/blog/
Personal Blog: http://avernet.blogspot.com/
Twitter - http://twitter.com/avernet


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws