glassfish
  1. glassfish
  2. GLASSFISH-16513

Events and @Observes(during=TransactionPhase.AFTER_COMPLETION) not working in Glassfish 3.1

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 3.1
    • Fix Version/s: 3.1.2_b14
    • Component/s: cdi
    • Labels:
      None
    • Environment:

      Windows 7, 64bit, Windows XP, 32bit

      Description

      First of all let me state, that the following code example worked just fine in GF 3.0.1. The troubles started when we switched to GF 3.1.

      I'm using a method
      @Asynchronous
      public void executeFlowStep(@Observes(during=TransactionPhase.AFTER_COMPLETION) ExecuteFlowStepEvent executeFlowStepEvent)

      Since the switch, whenever this method should receive an ExecuteFlowStepEvent I get the following error message:

      WELD-000401 Failure while notifying an observer of event [package].ExecuteFlowStepEvent

      No further information or Stacktrace is given. It works if I remove the @Asynchronous annotation and the AFTER_COMPLETION attribute, of course this breaks the program as I depend on the AFTER_COMPLETION timing.

      Is this a bug, or is this intended behaviour?

      Does this imply that Weld does NOT work with Asynchronous methods/AFTER_COMPLETION attributes?

      Why did this work in GF 3.0.1?

        Activity

        Hide
        prasads added a comment -

        Increasing the priority

        Show
        prasads added a comment - Increasing the priority
        Hide
        Sivakumar Thyagarajan added a comment -

        Filed https://issues.jboss.org/browse/WELD-936 to track this issue

        Show
        Sivakumar Thyagarajan added a comment - Filed https://issues.jboss.org/browse/WELD-936 to track this issue
        Hide
        Sivakumar Thyagarajan added a comment -

        Marked issue as "Major"

        Show
        Sivakumar Thyagarajan added a comment - Marked issue as "Major"
        Hide
        stuartdouglas added a comment -

        This is fixed in weld upstream, and will be part of 1.1.2

        Show
        stuartdouglas added a comment - This is fixed in weld upstream, and will be part of 1.1.2
        Hide
        Sivakumar Thyagarajan added a comment -

        Marking this issue as resolved as with the integration of Weld 1.1.2 and beyond, this issue doesn't occur with latest builds of GlassFish 3.1.2 (b14+) and trunk:

        – server.log snippet showing successful invocation of app –
        [#|2011-12-11T21:44:50.691+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=25;_ThreadName=Thread-2;|IN BEAN|#]

        [#|2011-12-11T21:44:50.762+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=25;_ThreadName=Thread-2;|FINISH|#]
        – server.log snippet showing successful invocation of app –

        Show
        Sivakumar Thyagarajan added a comment - Marking this issue as resolved as with the integration of Weld 1.1.2 and beyond, this issue doesn't occur with latest builds of GlassFish 3.1.2 (b14+) and trunk: – server.log snippet showing successful invocation of app – [#|2011-12-11T21:44:50.691+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=25;_ThreadName=Thread-2;|IN BEAN|#] [#|2011-12-11T21:44:50.762+0530|INFO|glassfish3.1.2|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=25;_ThreadName=Thread-2;|FINISH|#] – server.log snippet showing successful invocation of app –

          People

          • Assignee:
            Sivakumar Thyagarajan
            Reporter:
            nagelfar
          • Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: