November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8671) ClassNotFoundException when a EJB Timer with custom info is deserialized

by Sipatha Shoko (JIRA)

ClassNotFoundException when a EJB Timer with custom info is deserialized ------------------------------------------------------------------------ Key: JBAS-8671 URL: https://jira.jboss.org/browse/JBAS-8671 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: WinXP 32 bit, Ubuntu 10.04 32 bit, SunOS 5.10 sparc Reporter: Sipatha Shoko Assignee: Carlo de Wolf When an EJB3 Timer is created, you can optionally specify information pertaining to the timer. The information object must be serializable. A TimerVo (packaged in the same jar as the EJB) object thats serializable is used as the information. The EJB is first deployed, the timer is correctly created. However if the server is restarted, a ClassNotFoundException for TimerVo is thrown when the previously saved timer is deserialised. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-8551) tests.classpath length impacts running tests on Windows

by Shelly McGowan (JIRA)

tests.classpath length impacts running tests on Windows ------------------------------------------------------- Key: JBAS-8551 URL: https://jira.jboss.org/browse/JBAS-8551 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.CR1 http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.0.x-Wind... -- 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

13 years, 5 months

4
16
0 / 0

[JBoss JIRA] Created: (JBAS-8627) Fix testsuite failures affecting 6.0.0.Final release

by Shelly McGowan (JIRA)

Fix testsuite failures affecting 6.0.0.Final release ---------------------------------------------------- Key: JBAS-8627 URL: https://jira.jboss.org/browse/JBAS-8627 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.Final -- 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

13 years, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (JBCOMMON-102) Release jboss-common-core 2.2.18

by Dimitris Andreadis (JIRA)

Release jboss-common-core 2.2.18 -------------------------------- Key: JBCOMMON-102 URL: https://jira.jboss.org/jira/browse/JBCOMMON-102 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.18.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAOP-794) JBoss AOP deadlocks on JBoss AS with pluggable instrumentor

by Flavia Rainone (JIRA)

JBoss AOP deadlocks on JBoss AS with pluggable instrumentor ----------------------------------------------------------- Key: JBAOP-794 URL: https://jira.jboss.org/browse/JBAOP-794 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.1.Alpha2, 1.5.6.GA, 1.5.5 CP04 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 1.5.7.GA, 2.1.6 CP01 JBoss AOP deadlocks in loadtime weaving mode on JBoss AS. This is the scenario: -one thread loading a class starts loadtime weaving. In the process, the classloader performing the loading is locked. The thread ends up needing a concurrency lock held by the other thread. - another thread loading a class also starts loadtime weaving. In the process, this threads locks one of the concurrency locks and ends up needing to load a class (JBoss AOP or Javassist class). For loading this class, however, this thread needs the class loader lock held by the first thread. -- 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

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-793) Enable AspectManager's write lock during aspect loading

by Flavia Rainone (JIRA)

Enable AspectManager's write lock during aspect loading ------------------------------------------------------- Key: JBAOP-793 URL: https://jira.jboss.org/browse/JBAOP-793 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.1.Alpha2, 1.5.6.GA, 1.5.5 CP04 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: 1.5.7.GA, 2.1.6 CP01 Both AspectXMLLoader and AspectAnnotationLoader eventually trigger several operations at AspectManager that require write lock. Between two operations, on a multi-threaded loadtime-weaving scenario, a class loading in the Aspect***Loader thread may result in a dead lock. To avoid this scenario, we can enable the write during the entire aspect loading operation. -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4514) CLONE -Deadlock when logging trace

by chris effenberger (JIRA)

CLONE -Deadlock when logging trace ---------------------------------- Key: JBAS-4514 URL: http://jira.jboss.com/jira/browse/JBAS-4514 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: chris effenberger Assigned To: Scott M Stark SourceForge Submitter: genman . This was caused when trace was enabled. I imagine it was caused by the classloader trying to load a class while it was being rendered (?) to disk. Probably not a big issue, unless trace-logging is enabled. Java stack information for the threads listed above: =================================================== "SMPP-TIMER-0": at com.logica.smpp.util.ByteBuffer.getHexDump(ByteBuffer.java:379) at com.logica.smpp.util.ByteBuffer.toString(ByteBuffer.java:387) at org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:26) at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:70) at org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:288) at org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:395) at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:56) at org.apache.log4j.PatternLayout.format(PatternLayout.java:495) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292) at org.apache.log4j.WriterAppender.append(WriterAppender.java:150) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221) - locked <0x473874c8> (a org.apache.log4j.ConsoleAppender) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57) at org.apache.log4j.Category.callAppenders(Category.java:187) - locked <0x46829180> (a org.apache.log4j.spi.RootCategory) at org.apache.log4j.Category.forcedLog(Category.java:372) at org.apache.log4j.Category.debug(Category.java:241) at com.logica.smpp.debug.Log4JDebug.write(Log4JDebug.java:79) at com.logica.smpp.TCPIPConnection.send(TCPIPConnection.java:301) at com.logica.smpp.Transmitter.send(Transmitter.java:81) at com.logica.smpp.Session.send(Session.java:983) at com.logica.smpp.Session.bind(Session.java:452) at ... "SMSC-Accept-16910": at org.apache.log4j.Category.callAppenders(Category.java:185) - waiting to lock <0x46829180> (a org.apache.log4j.spi.RootCategory) at org.apache.log4j.Category.forcedLog(Category.java:372) at org.apache.log4j.Category.log(Category.java:864) at org.jboss.logging.Log4jLoggerPlugin.trace(Log4jLoggerPlugin.java:96) at org.jboss.logging.Logger.trace(Logger.java:113) at org.jboss.mx.loading.UnifiedClassLoader3.attempt(UnifiedClassLoader3.java:242) at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:126) - locked <0x472e2f38> (a org.jboss.mx.loading.UnifiedClassLoader3) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315) - locked <0x472e2f38> (a org.jboss.mx.loading.UnifiedClassLoader3) at com.proteusmobile.smsgw.server.ServerService.listen(ServerService.java:187) at com.proteusmobile.smsgw.server.ServerService.access$3(ServerService.java:46) at com.proteusmobile.smsgw.server.ServerService$Listener.run0(ServerService.java:163) at com.proteusmobile.smsgw.server.ServerService$Listener.run(ServerService.java:154) at java.lang.Thread.run(Thread.java:536) Found 1 deadlock. -- 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

13 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1037) JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint)

by Mariusz Olejnik (JIRA)

JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint) ---------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1037 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1037 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.4.0.CR1 Environment: Windows XP / Oracle 10g Reporter: Mariusz Olejnik Assigned To: Tim Fox Priority: Critical Fix For: 1.4.0.CR1 Reference should be inserted after message because: oracle-persistence-service.xml CREATE TABLE JBM_MSG_REF ( CHANNEL_ID INTEGER, MESSAGE_ID INTEGER REFERENCES JBM_MSG(MESSAGE_ID) [...] -- 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

13 years, 5 months

5
5
0 / 0

[JBoss JIRA] Created: (JBAS-8563) Implement persistence-context-ref resource provider

by Shelly McGowan (JIRA)

Implement persistence-context-ref resource provider --------------------------------------------------- Key: JBAS-8563 URL: https://jira.jboss.org/browse/JBAS-8563 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assignee: Scott Marlow Fix For: 6.0.0.CR1 -- 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

13 years, 5 months

2
19
0 / 0

[JBoss JIRA] Created: (JBRULES-2784) Use java-style annotations for metadata

by Davide Sottara (JIRA)

Use java-style annotations for metadata ---------------------------------------- Key: JBRULES-2784 URL: https://jira.jboss.org/browse/JBRULES-2784 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M1 Reporter: Davide Sottara Assignee: Mark Proctor Priority: Trivial Fix For: 5.2.0.M1 Drools Metadata, allowed in rules and bean declarations, are conceptually similar to java annotations, but the actual structure is different: Drools is free-form, while Java uses (optional) key - element pairs: Drools : @attr( <free text here> ) Java : @attr( key1 = value1, key2 ... ) I suggest the use of Java-like annotations in place of free-form meta-attributes. Compatibility with official metadata (e.g. event definition) will be guaranteed. Could break compatibility if a user defined and used their own metadata in the code, as some constructs like @author(john doe) will no longer be accepted, even if @author("john doe"), @author(john, doe) or @author(name="john doe") will. -- 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

13 years, 5 months

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010