March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSER-125) Tag JBoss Serialization 1.0.5

by Brad Maxwell (JIRA)

Tag JBoss Serialization 1.0.5 ----------------------------- Key: JBSER-125 URL: https://issues.jboss.org/browse/JBSER-125 Project: JBoss Serialization Issue Type: Task Reporter: Brad Maxwell Assignee: Clebert Suconic Fix For: 1.0.5.FINAL Need to tag JBoss Serialization 1.0.5 Final for release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (LOGMGR-28) PeriodicRotatingFileHandler does not roll the File on midnight when startet after 12PM

by Florian Lukschander (JIRA)

PeriodicRotatingFileHandler does not roll the File on midnight when startet after 12PM -------------------------------------------------------------------------------------- Key: LOGMGR-28 URL: https://issues.jboss.org/browse/LOGMGR-28 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: core Affects Versions: 1.2.0.CR9 Environment: Windows Server 2003, JDK 1.6.0_21-b07 64bit Server VM, Locale: de_AT Reporter: Florian Lukschander Assignee: David Lloyd If the Logging is initialized after 12 P.M. the PeriodicRotatingFileHandler does not roll the file on midnight if the suffix '.yyyy-MM-dd' or Period=DAY is being used. The culprit for this cause is in my unterstanding the usage of Calendar.clear(..) for the 'HOUR_OF_DAY' Field. As stated in http://download.oracle.com/javase/6/docs/api/java/util/Calendar.html#clea... the HOUR value will not be cleared in this case. Probably the HALF_DAY Period setting has the same problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-9085) Add URL and Driver class name to "javax.resource.ResourceException: Wrong driver class for this connection URL" message in LocalManagedConnectionFactory

by David Lloyd (JIRA)

Add URL and Driver class name to "javax.resource.ResourceException: Wrong driver class for this connection URL" message in LocalManagedConnectionFactory -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-9085 URL: https://issues.jboss.org/browse/JBAS-9085 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: John Bailey Fix For: 7.0.0.Beta2 As the summary says -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9067) Lifecycle methods on interceptor objects not functioning

by David Lloyd (JIRA)

Lifecycle methods on interceptor objects not functioning -------------------------------------------------------- Key: JBAS-9067 URL: https://issues.jboss.org/browse/JBAS-9067 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Critical Fix For: 7.0.0.Beta2 Need to revisit this piece of the component arch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-1276) SecondaryServerSocketThread should catch java.lang.Error

by Justin Bertram (JIRA)

SecondaryServerSocketThread should catch java.lang.Error -------------------------------------------------------- Key: JBREM-1276 URL: https://issues.jboss.org/browse/JBREM-1276 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Justin Bertram If org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread get's a java.lang.Error from processSocket (e.g. a java.lang.OutOfMemoryError) then the thread will die and no JMS clients will ever be able to connect to the server again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8771) Async log handler doesn't work

by David Lloyd (JIRA)

Async log handler doesn't work ------------------------------ Key: JBAS-8771 URL: https://issues.jboss.org/browse/JBAS-8771 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: 6.0.0.Final Async log handler doesn't work. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8389) Issue in using ThreadLocal

by Arunsakthi Kalyanasundharam (JIRA)

Issue in using ThreadLocal -------------------------- Key: JBAS-8389 URL: https://jira.jboss.org/browse/JBAS-8389 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Java EE APIs Affects Versions: JBossAS-4.2.2.GA Environment: Application Server - Garbage collection Reporter: Arunsakthi Kalyanasundharam Assignee: Shelly McGowan Fix For: JBossAS-4.2.3.GA I'm using Threadlocal in a web component. By definition, threadlocal variables should be cleared by end of execution of the thread. In case Application server, since its using a thread pool, the threadlocal variables are not cleared / garbage collected. This is leading to memory leakage (out of memory errors) and inconsistent behavior of the application since the variables are not getting cleared off. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-8927) jvisualvm on as7 with profile enabled results in ClassCircularityErrors - way to preconfigure AS7 allow it ?

by Max Rydahl Andersen (JIRA)

jvisualvm on as7 with profile enabled results in ClassCircularityErrors - way to preconfigure AS7 allow it ? ------------------------------------------------------------------------------------------------------------ Key: JBAS-8927 URL: https://issues.jboss.org/browse/JBAS-8927 Project: JBoss Application Server Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Max Rydahl Andersen 1) start as7 2) start jvisualvm and connect to the as 7 process. 3) go to Profiler tab 4) click CPU wait a few seconds and you as7 console output gets filled with ClassCircularityErrors: 02:35:22,145 ERROR [stderr] (RMI TCP Connection(idle)) Exception in thread "RMI TCP Connection(idle)" java.lang.ClassCircularityError: org/netbeans/lib/profiler/server/ProfilerRuntimeCPUFullInstr 02:35:22,145 ERROR [stderr] (RMI TCP Connection(idle)) at org.jboss.logmanager.Logger.isLoggable(Logger.java:153) 02:35:22,145 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.runtime.Log$LoggerLog.isLoggable(Log.java:206) 02:35:22,146 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:731) 02:35:22,146 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:652) 02:35:22,146 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 02:35:22,146 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:911) 02:35:22,147 ERROR [stderr] (RMI TCP Connection(idle)) at java.lang.Thread.run(Thread.java:680) 02:35:23,142 ERROR [stderr] (RMI TCP Connection(idle)) Exception in thread "RMI TCP Connection(idle)" java.lang.ClassCircularityError: org/netbeans/lib/profiler/server/ProfilerRuntimeCPUFullInstr 02:35:23,142 ERROR [stderr] (RMI TCP Connection(idle)) at org.jboss.logmanager.Logger.isLoggable(Logger.java:153) 02:35:23,142 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.runtime.Log$LoggerLog.isLoggable(Log.java:206) 02:35:23,142 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:731) 02:35:23,143 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:652) 02:35:23,143 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 02:35:23,143 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:911) 02:35:23,143 ERROR [stderr] (RMI TCP Connection(idle)) at java.lang.Thread.run(Thread.java:680) 02:35:23,159 ERROR [stderr] (RMI TCP Connection(idle)) Exception in thread "RMI TCP Connection(idle)" java.lang.ClassCircularityError: org/netbeans/lib/profiler/server/ProfilerRuntimeCPUFullInstr 02:35:23,159 ERROR [stderr] (RMI TCP Connection(idle)) at org.jboss.logmanager.Logger.isLoggable(Logger.java:153) 02:35:23,159 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.runtime.Log$LoggerLog.isLoggable(Log.java:206) 02:35:23,160 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:731) 02:35:23,160 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:652) 02:35:23,160 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 02:35:23,160 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:911) 02:35:23,160 ERROR [stderr] (RMI TCP Connection(idle)) at java.lang.Thread.run(Thread.java:680) 02:35:24,144 ERROR [stderr] (RMI TCP Connection(idle)) Exception in thread "RMI TCP Connection(idle)" java.lang.ClassCircularityError: org/netbeans/lib/profiler/server/ProfilerRuntimeCPUFullInstr 02:35:24,145 ERROR [stderr] (RMI TCP Connection(idle)) at org.jboss.logmanager.Logger.isLoggable(Logger.java:153) 02:35:24,145 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.runtime.Log$LoggerLog.isLoggable(Log.java:206) 02:35:24,146 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:731) 02:35:24,146 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:652) 02:35:24,146 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 02:35:24,146 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:911) 02:35:24,146 ERROR [stderr] (RMI TCP Connection(idle)) at java.lang.Thread.run(Thread.java:680) 02:35:24,151 ERROR [stderr] (RMI TCP Connection(idle)) Exception in thread "RMI TCP Connection(idle)" java.lang.ClassCircularityError: org/netbeans/lib/profiler/server/ProfilerRuntimeCPUFullInstr 02:35:24,157 ERROR [stderr] (RMI TCP Connection(idle)) at org.jboss.logmanager.Logger.isLoggable(Logger.java:153) 02:35:24,157 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.runtime.Log$LoggerLog.isLoggable(Log.java:206) 02:35:24,157 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:731) 02:35:24,157 ERROR [stderr] (RMI TCP Connection(idle)) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:652) 02:35:24,158 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 02:35:24,158 ERROR [stderr] (RMI TCP Connection(idle)) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:911) 02:35:24,158 ERROR [stderr] (RMI TCP Connection(idle)) at java.lang.Thread.run(Thread.java:680) Maybe add -Djboss.modules.system.pkgs=org.netbeans.lib.profiler.server as a default ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Deleted: (JBAS-4393) XAER_RMERR followed by Data Access Error

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/JBAS-4393?page=com.atlassian.jira.plugin.... ] Jason Greene deleted JBAS-4393: ------------------------------- > XAER_RMERR followed by Data Access Error > ---------------------------------------- > > Key: JBAS-4393 > URL: https://issues.jboss.org/browse/JBAS-4393 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Reporter: spectra28 > > Keep on receiving XAER_RMERR that makes our jboss crash. Please let us know how to solve this. what triggers this problem and how to prevent this. Is this issue related to JBAS 3336? > here's a part of our server.log file > 2007-05-03 16:19:03,826 WARN [org.jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl[FormatId=257, GlobalId=EMEAU1801/755, BranchQual=, localId=755] errorCode=XAER_RMERR > javax.transaction.xa.XAException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]xa_start (40000) returns -8 > Thanks -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-2266) Allow propagation of SecurityAssociation.Subject to child threads

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/JBAS-2266?page=com.atlassian.jira.plugin.... ] Jason Greene resolved JBAS-2266. -------------------------------- Assignee: Scott Stark Resolution: Out of Date > Allow propagation of SecurityAssociation.Subject to child threads > ----------------------------------------------------------------- > > Key: JBAS-2266 > URL: https://issues.jboss.org/browse/JBAS-2266 > Project: JBoss Application Server > Issue Type: Support Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.2 Final > Reporter: Scott Stark > Assignee: Scott Stark > > Need a patch for http://jira.jboss.com/jira/browse/JBAS-2175 for case4425 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
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 March 2011