January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBSER-92) Need to support Java 6.

by Nikita Ivanov (JIRA)

Need to support Java 6. ----------------------- Key: JBSER-92 URL: http://jira.jboss.com/jira/browse/JBSER-92 Project: JBoss Serialization Issue Type: Bug Affects Versions: 1.0.3 GA Reporter: Nikita Ivanov Assigned To: Clebert Suconic Doesn't work on Java 6. Run your own junits to see. It basically prevents anyone who's using JBoss Serialization to be Java 6 compatible. -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Closed: (JBREM-526) TimeUtil not using daemon thread

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-526?page=all ] Tom Elrod closed JBREM-526. ---------------------------- Resolution: Duplicate Issue Duplicate of JBREM-673 > TimeUtil not using daemon thread > -------------------------------- > > Key: JBREM-526 > URL: http://jira.jboss.com/jira/browse/JBREM-526 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Causing applications to remain running when should be shut down. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-526) TimeUtil not using daemon thread

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-526?page=all ] Tim Fox reopened JBREM-526: --------------------------- Doesn't seem to be fixed, or maybe it reverted due to having no test for it in the remoting test suite? > TimeUtil not using daemon thread > -------------------------------- > > Key: JBREM-526 > URL: http://jira.jboss.com/jira/browse/JBREM-526 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Causing applications to remain running when should be shut down. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBMESSAGING-417) JMS Client does not exit

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-417?page=all ] Ovidiu Feodorov reassigned JBMESSAGING-417: ------------------------------------------- Assignee: Ovidiu Feodorov (was: Tim Fox) > JMS Client does not exit > ------------------------ > > Key: JBMESSAGING-417 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-417 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.SP4 > > > After creating and cleanly closing connections to a remote JMS server, the JMS client process does not exit. > This is because JBossRemoting (TimerUtil class) contains a Timer which is not a daemon thus preventing the process from exiting. > Solution is simple: Make the timer a daemon. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-417) JMS Client does not exit

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-417?page=comments#action_12... ] Ovidiu Feodorov commented on JBMESSAGING-417: --------------------------------------------- Make sure this time we write a test for it. > JMS Client does not exit > ------------------------ > > Key: JBMESSAGING-417 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-417 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Fix For: 1.0.1.SP4 > > > After creating and cleanly closing connections to a remote JMS server, the JMS client process does not exit. > This is because JBossRemoting (TimerUtil class) contains a Timer which is not a daemon thus preventing the process from exiting. > Solution is simple: Make the timer a daemon. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-417) JMS Client does not exit

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-417?page=all ] Ovidiu Feodorov updated JBMESSAGING-417: ---------------------------------------- Fix Version/s: 1.0.1.SP4 (was: 1.0.1.CR3) > JMS Client does not exit > ------------------------ > > Key: JBMESSAGING-417 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-417 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.0.1.SP4 > > > After creating and cleanly closing connections to a remote JMS server, the JMS client process does not exit. > This is because JBossRemoting (TimerUtil class) contains a Timer which is not a daemon thus preventing the process from exiting. > Solution is simple: Make the timer a daemon. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-417) JMS Client does not exit

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-417?page=all ] Ovidiu Feodorov reopened JBMESSAGING-417: ----------------------------------------- Popped up again. > JMS Client does not exit > ------------------------ > > Key: JBMESSAGING-417 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-417 > Project: JBoss Messaging > Issue Type: Bug > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.0.1.CR3 > > > After creating and cleanly closing connections to a remote JMS server, the JMS client process does not exit. > This is because JBossRemoting (TimerUtil class) contains a Timer which is not a daemon thus preventing the process from exiting. > Solution is simple: Make the timer a daemon. -- 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

19 years, 3 months

1
0
0 / 0

Promoción Veraniega

by Hostex.cl

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2652) Need tests validating the expected JSR77 names of components

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2652?page=all ] Dimitris Andreadis updated JBAS-2652: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) Assignee: (was: Dimitris Andreadis) > Need tests validating the expected JSR77 names of components > ------------------------------------------------------------ > > Key: JBAS-2652 > URL: http://jira.jboss.com/jira/browse/JBAS-2652 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Management services > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Fix For: JBossAS-5.0.1.CR1, JBossAS-4.2.1.CR1 > > > We need to update the jsr77 tests to validate that the jsr77 names of the various component deployment types are as expected for the various project uses. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-339) Inteception on field inherited through generic superclass

by dunks80 (JIRA)

Inteception on field inherited through generic superclass --------------------------------------------------------- Key: JBAOP-339 URL: http://jira.jboss.com/jira/browse/JBAOP-339 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.0.5.GA JBoss AOP 1.5.2.GA load time weaving Java HotSpot(TM) 64-Bit Server VM (build 1.6.0-b105, mixed mode) Reporter: dunks80 I'm seeing the following unexpected behavior Code: public abstract class A { @MyFieldAnnotation protected Object myField; ... } public abstract class B<Z> extends A { ... } public class C extends B<Y> { ... } @InterceptorDef(scope = Scope.PER_VM) @Bind(pointcut = "get(* *->@MyFieldAnnotation)") public class MyFieldInterceptor implements Interceptor { ... } When i try to call myField on an instance of C from within a method in C my interceptor is not run. However if I duplicate the annotated field in class B like this... Code: public abstract class A { @MyFieldAnnotation protected Object myField; ... } public abstract class B<Z> extends A { @MyFieldAnnotation protected Object myField; ... } ...then the interceptor works when calling myField from an instance of C. I'm guess that since B is generic some sort of erasure of the annotation is happening. As a work around in the meantime I've just duplicated the annotated field. I just wanted to know whether this issue was known to the developers (if not I'll post it to jira) and whether or not there was some way to get this working without the need to duplicate that field. Thanks -- 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

19 years, 3 months

2
9
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 January 2007