Back to bug 1033008
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ondrej Chaloupka | 2013-11-21 12:07:34 UTC | CC | mnovak, msimka, ochaloup | |
| Ondrej Chaloupka | 2013-11-29 14:11:17 UTC | Doc Text | Cause: Generic resource adapter handles incorrectly settings of the timeout. Consequence: User can use only default timeout specified in standalone.xml under transaction subsystem. Usage of timeout definition by user in application (e.g. with org.jboss.ejb3.annotation.TransactionTimeout annotation) causes the NullPointer exception is thrown and transaction is rollbacked. Fix: Result: User has to use default transction timeout. |
|
| Jeff Mesnil | 2013-11-29 14:46:48 UTC | Assignee | jmesnil | ochaloup |
| Ondrej Chaloupka | 2013-11-29 15:29:37 UTC | Assignee | ochaloup | jmesnil |
| Summary | NullPointer exception when setting transaction timeout with generic jms ra | Generic JMS RA is not consistent with the EE spec - it does *not* ignore the parameters when session is created in the transaction context | ||
| Ondrej Chaloupka | 2013-11-29 16:06:13 UTC | Doc Text | Cause: Generic resource adapter handles incorrectly settings of the timeout. Consequence: User can use only default timeout specified in standalone.xml under transaction subsystem. Usage of timeout definition by user in application (e.g. with org.jboss.ejb3.annotation.TransactionTimeout annotation) causes the NullPointer exception is thrown and transaction is rollbacked. Fix: Result: User has to use default transction timeout. | Cause: Generic JMS resource adapter does *not* ignore the parameters when session is created in the transaction context which is a Java EE spec violation. Consequence: For the session works correctly the session has to be set as transacted either in EE environment when session context is active. The correct way is like: connection.createSession(true, Session.SESSION_TRANSACTED); Fix: Result: User has to create the session as transacted either when the session context exists. |
| Russell Dickenson | 2013-12-02 00:04:43 UTC | Doc Text | Cause: Generic JMS resource adapter does *not* ignore the parameters when session is created in the transaction context which is a Java EE spec violation. Consequence: For the session works correctly the session has to be set as transacted either in EE environment when session context is active. The correct way is like: connection.createSession(true, Session.SESSION_TRANSACTED); Fix: Result: User has to create the session as transacted either when the session context exists. | When a session is created in a transaction's context and parameters are passed to the generic JMS resource adapter, a Null Pointer Exception (NPE) occurs. The issue occurs because the processing of parameters is atempted, when the Java EE specification states that they are *not* to be processed. The root cause of the issue is under investigation, but until then a workaround is to set the session to be transacted, as per the following example. With this workaround, the NPE will not occur. ---- connection.createSession(true, Session.SESSION_TRANSACTED); ---- |
| Doc Type | Bug Fix | Known Issue | ||
| Ondrej Chaloupka | 2014-03-18 14:49:27 UTC | CC | jmesnil | |
| Flags | needinfo?(jmesnil) | |||
| Ondrej Chaloupka | 2014-03-18 14:49:48 UTC | CC | hhovsepy | |
| Jeff Mesnil | 2014-03-18 17:39:57 UTC | Flags | needinfo?(jmesnil) | |
| Jeff Mesnil | 2014-03-25 10:31:16 UTC | Link ID | JBoss Issue Tracker WFLY-3159 | |
| Kabir Khan | 2014-03-26 09:17:05 UTC | Status | NEW | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | ER1 | ||
| Jeff Mesnil | 2014-03-31 13:39:16 UTC | Depends On | 1082617 | |
| Paul Gier | 2014-04-03 22:12:14 UTC | Status | MODIFIED | ON_QA |
| Kabir Khan | 2014-04-04 15:53:38 UTC | Depends On | 1080668 | |
| Ondrej Chaloupka | 2014-04-17 11:07:11 UTC | Target Milestone | ER1 | ER2 |
| Miroslav Novak | 2014-04-28 08:08:55 UTC | Depends On | 1090769 | |
| Martin Simka | 2014-05-05 08:34:27 UTC | Target Milestone | ER2 | ER3 |
| Ondrej Chaloupka | 2014-05-06 11:28:34 UTC | Status | ON_QA | ASSIGNED |
| Jeff Mesnil | 2014-10-27 08:28:04 UTC | CC | wfink | |
| Component | JCA | JMS | ||
| Ondrej Chaloupka | 2014-10-29 13:48:38 UTC | Status | ASSIGNED | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2014-10-29 09:48:38 UTC | |||
| Ondrej Chaloupka | 2014-10-29 13:53:47 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1158496 | |
| Jitka Kozana | 2015-01-29 09:57:49 UTC | CC | jkudrnac | |
| Lucas Costi | 2015-02-04 00:14:01 UTC | Target Release | EAP 6.4.0 | |
| CC | lcosti | |||
| Scott Mumford | 2015-02-05 00:34:16 UTC | Target Release | EAP 6.3.0 | EAP 6.4.1 |
| CC | smumford | |||
| Scott Mumford | 2015-03-09 03:42:22 UTC | Doc Text | When a session is created in a transaction's context and parameters are passed to the generic JMS resource adapter, a Null Pointer Exception (NPE) occurs. The issue occurs because the processing of parameters is atempted, when the Java EE specification states that they are *not* to be processed. The root cause of the issue is under investigation, but until then a workaround is to set the session to be transacted, as per the following example. With this workaround, the NPE will not occur. ---- connection.createSession(true, Session.SESSION_TRANSACTED); ---- | This release of JBoss EAP 6 carries the following issue in the JMS component. When a session is created in a transaction's context and parameters are passed to the generic JMS resource adapter, a `NullPointerException` (NPE) occurs. The issue occurs because the processing of parameters is attempted, when the Java EE specification states that they are *not* to be processed. The root cause of the issue is under investigation, but until then a workaround is to set the session to be transacted, as per the following example. With this workaround, the NPE will not occur. ---- connection.createSession(true, Session.SESSION_TRANSACTED); ---- |
| Lucas Costi | 2015-03-09 04:57:37 UTC | CC | lcosti | |
| Carlo de Wolf | 2015-03-31 12:54:03 UTC | Target Release | EAP 6.4.1 | |
| CC | cdewolf | |||
| Target Milestone | ER3 | GA |
Back to bug 1033008