You can enter Chainsaw bugs by entering the bug against log4j and choosing the Chainsaw subcategory on the issue creation page.
Chainsaw supports per-tab settings, which are stored in $userhome/.chainsaw (/documents and settings/username/.chainsaw on Windows) - and I think you've got a problem with one of those files. Try exiting Chainsaw & deleting all files out of that directory except for chainsaw.settings.properties and chainsaw.settings.xml. Scott Deboy -----Original Message----- From: Owe Andresen [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 9:10 AM To: Log4J Users List Subject: Re: Question: Chainsaw usage Hello, thanks alot, Paul, this was very helpful! Where can i enter Bugs about Chainsaw? I see, there is no Chainsaw in http://issues.apache.org/bugzilla/enter_bug.cgi :( This userlist is maybe the wrong place to paste problems with Chainsaw. Anyway, in about 33% of the cases when i start Chainsaw (in Debug-mode from Eclipse), i get this error (first come come log entry, then an exception): Using font=Arial LOG4J-INTERNAL: 2007-10-24 18:04:03,289 DEBUG [main] org.apache.log4j.joran.action.ConfigurationAction#begin:42)- Starting internal logs on console. LOG4J-INTERNAL: 2007-10-24 18:04:03,305 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:45)- About to instantiate plugin of type [mymain.UDPReceiver] LOG4J-INTERNAL: 2007-10-24 18:04:03,399 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:59)- plugin named as [MyUDPReceiver] LOG4J-INTERNAL: 2007-10-24 18:04:03,399 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:70)- Pushing plugin on to the object stack. LOG4J-INTERNAL: 2007-10-24 18:04:03,399 DEBUG [main] org.apache.log4j.joran.action.ParamAction#begin:61)- In ParamAction setting parameter [Port] to value [514]. LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.PluginAction#end:102)- Popping plugin named [MyUDPReceiver] from the object stack LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:45)- About to instantiate plugin of type [mymain.LogFilePatternReceiver] LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:59)- plugin named as [MyLogFilePatternReceiver] LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.PluginAction#begin:70)- Pushing plugin on to the object stack. LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.PluginAction#end:102)- Popping plugin named [MyLogFilePatternReceiver] from the object stack LOG4J-INTERNAL: 2007-10-24 18:04:03,430 DEBUG [main] org.apache.log4j.joran.action.RootLoggerAction#begin:43)- Pushing root logger on stack LOG4J-INTERNAL: 2007-10-24 18:04:03,446 DEBUG [main] org.apache.log4j.joran.action.LevelAction#begin:45)- Encapsulating logger name is [root], levelvalue is [trace]. LOG4J-INTERNAL: 2007-10-24 18:04:03,446 DEBUG [main] org.apache.log4j.joran.action.LevelAction#begin:76)- root level set to TRACE LOG4J-INTERNAL: 2007-10-24 18:04:03,446 DEBUG [main] org.apache.log4j.joran.action.RootLoggerAction#end:61)- Removing root logger from top of stack. LOG4J-INTERNAL: 2007-10-24 18:04:03,446 DEBUG [main] org.apache.log4j.joran.action.ConfigurationAction#end:49)- Will stop writing internal logs on console. Wanting to add a row, but GUI not initialized, waiting... Exception in thread "AWT-EventQueue-0" java.lang.ArrayIndexOutOfBoundsException: 3 at javax.swing.plaf.basic.BasicTabbedPaneUI.tabForCoordinate(BasicTabbedPan eUI.java:1286) at javax.swing.plaf.basic.BasicTabbedPaneUI.setRolloverTab(BasicTabbedPaneU I.java:499) at javax.swing.plaf.basic.BasicTabbedPaneUI.access$1200(BasicTabbedPaneUI.j ava:37) at javax.swing.plaf.basic.BasicTabbedPaneUI$Handler.mouseMoved(BasicTabbedP aneUI.java:3254) at java.awt.AWTEventMulticaster.mouseMoved(AWTEventMulticaster.java:271) at java.awt.Component.processMouseMotionEvent(Component.java:5546) at javax.swing.JComponent.processMouseMotionEvent(JComponent.java:3153) at java.awt.Component.processEvent(Component.java:5270) at java.awt.Container.processEvent(Container.java:1966) at java.awt.Component.dispatchEventImpl(Component.java:3968) at java.awt.Container.dispatchEventImpl(Container.java:2024) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3905) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822) at java.awt.Container.dispatchEventImpl(Container.java:2010) at java.awt.Window.dispatchEventImpl(Window.java:1778) at java.awt.Component.dispatchEvent(Component.java:3803) at java.awt.EventQueue.dispatchEvent(EventQueue.java:463) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThrea d.java:242) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread. java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) ----- Original Message ----- From: "Paul Smith" <[EMAIL PROTECTED]> To: "Log4J Users List" <[email protected]> Sent: Tuesday, October 23, 2007 2:20 AM Subject: Re: Question: Chainsaw usage > > On 20/10/2007, at 7:51 PM, Owe Andresen wrote: > >> Hello, >> (@first, im new to this list). >> >> 1. I write a sutom receiver for our log-message formats. What bothers me >> is that i have to open the recevers configuration file each time when i >> start Chainsaw. >> > > Why don't you configure the URL of the config file in the preferences? > Then it will be loaded each time automatically? > >> 2. I restart Chainsaw alot, becase i cannot remove the visible receivers >> once they are in the treeview of the chainsaw lgomessage panel. >> > I don't understand what you mean here. > >> 3. I got concurrent modification exception, when having alot of messages >> (150000).. Also i got "IllegalArgumentException" when filtering by date >> (with only 7000 logmessages also). known? >> > A stacktrace to this mailing list would be useful here, otherwise we > don't know what problem you are encountering. > >> 4. I am missing that jump-to-logmessage by number, i heard it was >> announced somewhere. When will this feature come in a new Chainsaw >> release? > > This is in the trunk version of Chainsaw, not yet released (waiting on > some downstream log4j modules to be released first). > > cheers, > > Paul > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
