Re: [JPublish-developer] JBoss 3.0.0 console appender error

[Ben A. <ben...@ac...>]

In the end I edited the log.properties file in each .war and commented =
out every entry. This fixed the problem, with JBoss' log4j =
implementation now capturing all JPublish messages.

Thanks to everyone for their responses.

Ben

  ----- Original Message -----=20
  From: Dmitri Colebatch=20
  To: Anthony Eden ; jpu...@li...=20
  Sent: Thursday, June 20, 2002 10:01 AM
  Subject: Re: [JPublish-developer] JBoss 3.0.0 console appender error


  yep - the easiest thing is to just change the log4j config to not use =
the console.

  hth
  dim
    ----- Original Message -----=20
    From: Anthony Eden=20
    To: jpu...@li...=20
    Sent: Thursday, June 20, 2002 12:23 AM
    Subject: RE: [JPublish-developer] JBoss 3.0.0 console appender error


    I have heard others mention this problem before: it has to do with =
Log4J initializing twice.  Check the mailing list archives because I =
believe someone does have a patch although I do not recall if they =
actually posted the patch to the list.

    If someone comes up with a clean workaround for this I will make the =
necessary changes.  The best thing would be to determine from Log4J =
whether or not it is already initialized, right?  I will look into it =
personally as well.

    Sincerely,
    Anthony Eden
      -----Original Message-----
      From: jpu...@li... =
[mailto:jpu...@li...]On Behalf Of Ben =
Alex
      Sent: Wednesday, June 19, 2002 6:33 AM
      To: jpu...@li...
      Subject: [JPublish-developer] JBoss 3.0.0 console appender error


      Hi

      When I deploy the jpublish-docs.war shipped with JPublish 1.0b3 to =
JBoss 3.0.0 with integrated Jetty, I receive the following message on =
the JBoss console:

      17:07:26,786 INFO  [Jetty] jpublish: init
      ERROR: invalid console appender config detected, console stream is =
looping

      After this error, no further logging messages are displayed on the =
JBoss console or appended to the JBoss log file.

      I have tried adjusting the log4j properties for both JPublish and =
JBoss, but have not been able to correct this. Code is my next stop, but =
I thought I'd first ask if anyone else can reproduce this behaviour or =
offer some hints?

      Thanks in advance

      Ben