December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-642) incorrect log level in PersistenceFactory.getInstance()

by Chris Ekberg (JIRA)

incorrect log level in PersistenceFactory.getInstance() ------------------------------------------------------- Key: JGRP-642 URL: http://jira.jboss.com/jira/browse/JGRP-642 Project: JGroups Issue Type: Bug Affects Versions: 2.5.1 Reporter: Chris Ekberg Assigned To: Bela Ban Priority: Trivial in PersistenceFactory.java: public static PersistenceFactory getInstance() { log.error(" getting factory instance "); ... I think that should be log.debug, not log.error. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4389) nestedjarXXXX.temp files remain in the User's Temp directory on Windows after AS shutdown.

by Mark Spritzler (JIRA)

nestedjarXXXX.temp files remain in the User's Temp directory on Windows after AS shutdown. ------------------------------------------------------------------------------------------ Key: JBAS-4389 URL: http://jira.jboss.com/jira/browse/JBAS-4389 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Mark Spritzler When you startup the App Server some temp jar files are created in "C:\Documents and Settings\Username\Local Settings\Temp" directory. After you shutdown the App Server, a lot of them are deleted, but not all of them. After restarting the server many times those files that remain are all still there, causing your hard drive to run out of space. I had had 15 gigs used up by these remaining files. Here are the statistics of restarting the server about 4 times after cleaning everything out of the Temp folder before the first startup. Start 386 Files 73.5 MB Shutdown 224 Files 33.7 Megabytes Second start 546 Files 97.6 MB Second Shutdown 576 Files 86.9 MB Third start // This tells me I didn't refresh(F5) Windows Explorer to get all the new files. 576 Files 86.9 MB Third Shutdown 1024 Files 154 MB Fourth start 1410 Files 228 MB Fourth Shutdown 1280 Files 193 MB Format of files remaining in temp nestedjarNNNN.temp -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-5030) Upgrade jboss-ha-client.jar to 1.0.0.GA

by Brian Stansberry (JIRA)

Upgrade jboss-ha-client.jar to 1.0.0.GA --------------------------------------- Key: JBAS-5030 URL: http://jira.jboss.com/jira/browse/JBAS-5030 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need a GA release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1762) Myfaces Example

by Wesley Hales (JIRA)

Myfaces Example --------------- Key: JBPORTAL-1762 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1762 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1760) JSR-301 JSF Portlet Bridge Integration

by Wesley Hales (JIRA)

JSR-301 JSF Portlet Bridge Integration -------------------------------------- Key: JBPORTAL-1760 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1760 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales Integrate Implementation of 301 spec into JBP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3996) Web Console AppletBrowser hangs browser because of missing Logger

by teej TJ (JIRA)

Web Console AppletBrowser hangs browser because of missing Logger ----------------------------------------------------------------- Key: JBAS-3996 URL: http://jira.jboss.com/jira/browse/JBAS-3996 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-5.0.0.Beta1 Environment: Ubuntu Edgy Eft 6.10 Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux Firefox 2.0.0.1 Sun Java 1.5.0_08 Reporter: teej TJ Assigned To: Darran Lofthouse Firefox hangs and has to be killed when the JBoss Web Console link is followed on the JBoss Management service (http://localhost:8080/). The hang is caused by a NoClassDefFoundError exception whilst attempting to load AppletBrowser in applet.jar. This appears to be another instance of the use of Logger where it has been removed (as in the shutdown.sh script bugs JBAS-3560). org.jboss.console.remote.Util: private static org.jboss.logging.Logger log = org.jboss.logging.Logger.getLogger(Util.class); --- Java Console Report --- basic: Loading applet ... basic: Initializing applet ... basic: Starting applet ... network: Connecting http://10.254.251.2:8080/web-console/applet.jar with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/applet.jar with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" basic: Loading http://10.254.251.2:8080/web-console/applet.jar from cache basic: No certificate info, this is unsigned JAR file. http://10.254.251.2:8080/web-console/Invoker network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) basic: Exception: java.lang.NoClassDefFoundError: org/jboss/logging/Logger java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

6
5
0 / 0

[JBoss JIRA] Created: (JBAS-3857) shutdown.sh does not work

by Ovidiu Feodorov (JIRA)

shutdown.sh does not work ------------------------- Key: JBAS-3857 URL: http://jira.jboss.com/jira/browse/JBAS-3857 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Ovidiu Feodorov $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/system/server/ServerImplMBean at org.jboss.Shutdown.main(Shutdown.java:116) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-854) Mechanism for interceptor-level communications

by David Lloyd (JIRA)

Mechanism for interceptor-level communications ---------------------------------------------- Key: JBREM-854 URL: http://jira.jboss.com/jira/browse/JBREM-854 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 Need a way for interceptors to "talk" across the wire, to implement interceptor operations and share state. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-643) ClassConfigurator.getInstance() not thread safe

by Michael Newcomb (JIRA)

ClassConfigurator.getInstance() not thread safe ----------------------------------------------- Key: JGRP-643 URL: http://jira.jboss.com/jira/browse/JGRP-643 Project: JGroups Issue Type: Bug Reporter: Michael Newcomb Assigned To: Bela Ban Creating 2 or more JChannels simultaneously could result in multiple ClassConfigurators being created and inited at once or a ClassConfigurator being used before it has been inited. Recommend synchronizing the getInstance() method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JGRP-297) Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation

by Bela Ban (JIRA)

Use deadlock detection (JDK 5) to find deadlocks in stress tests or during regular operation -------------------------------------------------------------------------------------------- Key: JGRP-297 URL: http://jira.jboss.com/jira/browse/JGRP-297 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 The java.lang.management.ThreadMXBean has a method to check for and (if found) enumerate deadlocked threads (only with simply synchronized locks, jav.util.concurrent locks currently not supported afaik). This can be run every N seconds, and is useful in both stress testing and possibly also during operation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007