5:57 a.m.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Reporter: Matt C
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service beans
are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services.
--
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
6:01 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Matt C updated EJBTHREE-1701:
-----------------------------
Environment: 5.0.0.GA
Description:
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service beans
are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
was:
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service beans
are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
2:46 a.m.
New subject: [JBoss JIRA] Assigned: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Andrew Lee Rubinger reassigned EJBTHREE-1701:
---------------------------------------------
Assignee: Andrew Lee Rubinger
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
2:48 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Andrew Lee Rubinger commented on EJBTHREE-1701:
-----------------------------------------------
Likely you'll need some help working with the @Service Container lifecycle to get
around this.
If you can make my job really easy (ie. attach an integration test and build-test.xml
changes in a patch to this issue) it'll really help me give it some more attention.
PS - After some more patches/tests we can get you a CLA and commit rights.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
10:46 a.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Matt C updated EJBTHREE-1701:
-----------------------------
Attachment: EJBTHREE-1701_testcase_v1.patch
Integration test.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
11 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Matt C commented on EJBTHREE-1701:
----------------------------------
I need guidance on the correct use of [Current]Invocation and AllowedOperationsAssociation
to write this patch. It looks like both these contexts need to be set up during service
lifecycle method invocation, currently neither context is set up. Aiming at
ServiceContainer lockedStart|Stop() or invokeOptionalMethod().
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
5:53 p.m.
New subject: [JBoss JIRA] Updated: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Matt C updated EJBTHREE-1701:
-----------------------------
Attachment: EJBTHREE-1701_testcase_v2.patch
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
6:35 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Ville Skyttä commented on EJBTHREE-1701:
----------------------------------------
Another forum reference:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=158378
Any progress on this?
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
10:10 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Christian Hehtke commented on EJBTHREE-1701:
--------------------------------------------
i would love to have a fix, workaround or unofficial patch for this, because it is relly
important for us to have application wide timers on app start.
anything one can do to put a higher priority on this?
thanks in advance
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
5:03 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/jira/browse/EJBTHREE-1701?page=com.atlassian.jira....
]
Chris Meadows commented on EJBTHREE-1701:
-----------------------------------------
I'm echoing Christian's comment. I can't migrate our codebase to JB5 without
this fix, or doing some kind of workaround.
As such, does anyone have any thoughts on a potential workaround?
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/jira/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Lee Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
7:36 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://jira.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plugi...
]
Erik Lupander commented on EJBTHREE-1701:
-----------------------------------------
A possible workaround:
We enountered this issue migrating from 4.2.3.GA to 5.1.0.GA. After patching JBoss
5.1.0.GA with the latest JBoss EJB3 plugin, the @TimerService stuff works again in our
@Service annotated POJO:s lifecycle methods. E.g. start(). Version of the JBoss EJB3
Plugin: 1.0.19
http://www.jboss.org/ejb3/ejb3plugin.html
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://jira.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
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
4:03 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://issues.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plu...
]
JimDwyer commented on EJBTHREE-1701:
------------------------------------
I followed these steps but didn't get the same results. My bean is still blowing up
with this exception. Any suggestions?
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://issues.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:05 p.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://issues.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plu...
]
JimDwyer commented on EJBTHREE-1701:
------------------------------------
I should add that I am running 5.1.0.GA and patched with ejb plugin 1.0.19.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://issues.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:07 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://issues.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plu...
]
JimDwyer edited comment on EJBTHREE-1701 at 4/6/11 4:06 PM:
------------------------------------------------------------
I followed these steps but didn't get the same results. My bean is still blowing up
with this exception. Any suggestions?
I should add that I am running 5.1.0.GA and patched with ejb plugin 1.0.19.
was (Author: JimDwyer):
I followed these steps but didn't get the same results. My bean is still blowing
up with this exception. Any suggestions?
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://issues.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:09 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://issues.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plu...
]
JimDwyer edited comment on EJBTHREE-1701 at 4/6/11 4:07 PM:
------------------------------------------------------------
Did this fix work for others or was there more to it?
was (Author: JimDwyer):
I should add that I am running 5.1.0.GA and patched with ejb plugin 1.0.19.
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://issues.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:05 a.m.
New subject: [JBoss JIRA] Commented: (EJBTHREE-1701) getTimerService() can no longer be called in @Service start()
[
https://issues.jboss.org/browse/EJBTHREE-1701?page=com.atlassian.jira.plu...
]
jaikiran pai commented on EJBTHREE-1701:
----------------------------------------
Jim, Please open a forum thread http://community.jboss.org/en/ejb3?view=discussions with
details of the issue you are running into
getTimerService() can no longer be called in @Service start()
-------------------------------------------------------------
Key: EJBTHREE-1701
URL: https://issues.jboss.org/browse/EJBTHREE-1701
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: trunk
Environment: 5.0.0.GA
Reporter: Matt C
Assignee: Andrew Rubinger
Attachments: EJBTHREE-1701_testcase_v1.patch, EJBTHREE-1701_testcase_v2.patch
Calling getTimerService() is no longer allowed from the lifecycle methods of @Service.
Exception java.lang.IllegalStateException: getTimerService() not allowed during injection
(EJB3 4.5.2).
This occurs in the start() method of a @Service bean. The effect is to disallow setup of
application-wide timers.
This action is erroneously disallowed based on Table 2 in the EJB3 specification, section
4.5.2 (IMHO).
Service lifecycle methods are not dependency injection methods, furthermore @Service
beans are outside of the EJB3 specification.
Lifecycle methods of a service should probably be considered business methods, not DI in
the context of Table 2. They are in the @Management business interface.
There is no workaround yet for this backwards incompatible change which breaks apps that
set up application-wide timers from Services when they are migrated to 5.0.0.GA. This used
to work in 4.2.x.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4763
days inactive
5566
days old
15 comments
8 participants
participants (8)
-
Andrew Lee Rubinger (JIRA) -
Chris Meadows (JIRA)
-
Christian Hehtke (JIRA)
-
Erik Lupander (JIRA)
-
jaikiran pai (JIRA)
-
JimDwyer (JIRA)
-
Matt C (JIRA)
-
Ville Skyttä (JIRA)