Hi Paul and Scott,
Thanks - I tried the big log file again and the OutOfMemory exceptions have gone
away... But getting a different strange error now:
log4j:ERROR Parsing error on line 1 and column -1
log4j:ERROR Expected "</log4j:eventSet>" to terminate element starting on line 1.
org.xml.sax.SAXParseException: Expected "</log4j:eventSet>" to terminate element
starting on line 1.
But line 1 of the log is:
<log4j:event logger="org.apache.struts.util.PropertyMessageResources"
timestamp="1085138166014" level="DEBUG" thread="ExecuteThread: '2' for queue:
'weblogic.admin.RMI'">
And <log4j:eventSet> is nowhere to be found in the file!
Maybe this is fixed by your most recent change, Scott - I will try the grabcvs trick
later to get the latest build and try again.
Paul - I agree that the duplicate plugins seem to be a display issue. Probably related
to another strange behaviour that when you "shutdown" a receiver, it remains in the
list...?
As for automatically reconnecting, yes it would be great :) Is it as simple as
leaving the connector thread open all the time? Or maybe to save unnecessary network
trips, (after the initial connection has been made) the connector thread could check
to see if anything's been received within the last timeout interval and only attempt a
remote connection if there have been no new messages...?
Still loving Chainsaw & log4j :) I stumbled across the ConfigurationServlet yesterday
and five minutes later our project had taken another big step forward towards having
logs that (1) contain only relevant information and (2) are easily accessible by
anyone who needs them.
Cheers,
Stephen
Phone x59668
Paul Smith
<[EMAIL PROTECTED] To: Stephen Pain/DMGGM/DMG
UK/[EMAIL PROTECTED] UK, "'[EMAIL PROTECTED]
x.com.au> '" <[EMAIL PROTECTED]>
cc:
23/05/2004 08:26 Subject: RE: reconnecting to
SocketHubAppender
Please respond to
"Log4J Users
List"
Hi Stephen.
I have modified the jnlp file so that it specifies a max-heap-size of 256.
It's better than 64m now I guess. It would be nice to not have to specify
some arbitary value, but there you go. Let me know whether that small
change works better for you.
For the record, I also made 1 other small change. Previously it specified a
JDK verion of "1.3+". It appears that if you have 1.3 AND 1.4 installed, it
chooses 1.3. I changed it so that 1.4+ is the preferred, but can use 1.3 if
you have it installed.
As for the ReceiverPanel displaying multiple nodes, I think I have seen this
before, but have forgotten about it until now. I will try and take a look
at it. I am very confident that the original receiver has been stopped and
restarted, and it is just that it is a display related issue, although very
confusing I am sure.
Now it would be even better if the Receivers just automatically tried to
reconnect without manualy intervention eh?
cheers,
Paul Smith
-----Original Message-----
From: Stephen Pain
To: [EMAIL PROTECTED]
Sent: 5/23/04 10:28 AM
Subject: reconnecting to SocketHubAppender
Hi - me again :)
I just wrote an email about how I was having problems with a
SocketHubReceiver not reconnecting to a SocketHubAppender that got
restarted during a bounce of weblogic and asking how I might be able to
put a LogManager.shutdown() somewhere..... and just before sending it,
noticed the refresh button on the receivers panel of chainsaw, which was
exactly what I was about to request. Good work (again)!
BUT, when I clicked it, all the receivers I had set up got duplicated -
I now have twenty receivers in my list where before I had ten. The new
ones seem to be working ok, but it's a bit strange. Also, I've noticed
that when you "shutdown" a receiver, it doesn't actually disappear from
the list. Or at least, mine don't. Would it be too much to ask to get a
"refresh" option added to the right-click menu for an individual
receiver plugin to restart it if it's lost a connection and hasn't been
notified?
Btw, Scott/Paul - I'm still getting a java.lang.OutOfMemoryError if I
try to load a large (20MB) log file. I've got the latest release... not
sure what's going on there?
Cheers,
Stephen
--
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
This e-mail may contain confidential and/or privileged information. If you are not the
intended recipient (or have received this e-mail in error) please notify the sender
immediately and destroy this e-mail. Any unauthorized copying, disclosure or
distribution of the material in this e-mail is strictly forbidden.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
