There are 97 Online Users
(97 Guests,
0 Member
,
0 Invisible member
)
Who's Online:
What they are doing
|
Total Categories: 3
Total Forums: 9
Total Topics: 265
Total Posts: 1158
Total Members: 273
Latest Member: varmadvs
|
|
|
|
Forum: Glassbox 2.0 Developers »
Thread: Java is always Out of Memmory when we open new Thread
|
|
Posted by rbodkin
at Apr 24, 2008 10:44:42 PM
|
Re: Java is always Out of Memmory when we open new Thread
Glassbox uses AspectJ load-time weaving, which does increase the memory requirements of an application. It also keeps statistics about operations and calls in memory, which is normally constrained in size but in certain cases where an application dynamically generates queries or other items that produce many calls, it can use a lot of memory. If you can use a profiler (even Java's built in JVMPI, JVMTI, or java 6's jmap) to get a memory dump of the objects in use when you are out of memory, I'd be happy to give some input on what might be going wrong. Does it work if you increase the memory available to Java?
Sometimes Java just runs out of permanent memory for code, so you might try increasing that allocation too, e.g., with
-XX:MaxPermSize=256m
If that works you could also try a smaller setting like 128m or 64m.
Thanks,
Ron
|
|
Replies: 1 ::
Reply to this Post
|
|
Forum: HOW TO: Log or track Glassbox Issues »
Thread: JDK 1.5 and tomcat 5.5 giving a strange error for after upgrade
|
|
Posted by rbodkin
at Sep 5, 2007 12:23:29 AM
|
Re: JDK 1.5 and tomcat 5.5 giving a strange error for after upgrade
So if you enable Tomcat security, you are finding there are problems running Glassbox? You probably need to edit the security configuration to allow Glassbox to run under your more restrictive security settings. To help you configure this, can you give the startup options and security configuration file you're using, and the log error messages for the security errors you get when start Glassbox with Tomcat security please?
Thanks,
Ron
|
|
Replies: 1 ::
Reply to this Post
|
|
Forum: Glassbox 2.0 Technical Questions »
Thread: log4j:WARN No appenders could be found for logger (glassbox.bootstrap)
|
|
Posted by varmadvs
at May 15, 2008 5:27:48 AM
|
log4j:WARN No appenders could be found for logger (glassbox.bootstrap)
Hi,
We are encountering the below error while starting the application on websphere. Because of this the entire looging in the application is not working.
log4j:WARN No appenders could be found for logger (glassbox.bootstrap)
log4j:WARN Please initialize the log4j system properly.
And also the below error is showing in log
[5/14/08 23:32:08:648 CDT] 474779a8 ApplicationMg A WSVR0200I: Starting application: glassbox_war
[5/14/08 23:32:08:757 CDT] 474779a8 WebContainer A SRVE0169I: Loading Web Module: Glassbox Web Client.
[5/14/08 23:32:08:879 CDT] 474779a8 WebGroup I SRVE0180I: [Glassbox Web Client] [/glassbox] [Servlet.LOG]: JSP 1.2 Processor: init
[5/14/08 23:32:09:146 CDT] 474779a8 WebGroup I SRVE0180I: [Glassbox Web Client] [/glassbox] [Servlet.LOG]: SimpleFileServlet: init
[5/14/08 23:32:09:178 CDT] 474779a8 WebGroup I SRVE0180I: [Glassbox Web Client] [/glassbox] [Servlet.LOG]: initializer: init
[5/14/08 23:32:09:426 CDT] 474779a8 ServletInstan E ...
|
|
Replies: 0 ::
Reply to this Post
|
|
Forum: Glassbox Inspector Technical Support »
Thread: Enable logging of Glassbox1.0 inspector using with tomcat.
|
|
Posted by rbodkin
at Apr 21, 2008 7:19:52 PM
|
Re: Enable logging of Glassbox1.0 inspector using with tomcat.
Hi Narendra,
I'd highly encourage you to upgrade to Glassbox 2.0 which has a superset of Glassbox 1.0 inspector functionality, including better logging support.
That being said, if you are using log4j globally in Tomcat, you should edit your Tomcat log4j.properties file (typically found in conf or in common/classes), rather than just for your specific application.
You can also use -Dlog4j.debug=true to see how log4j is finding the relevant log files in your system.
Regards,
Ron
|
|
Replies: 1 ::
Reply to this Post
|
|
