5 Replies Latest reply on Aug 31, 2008 11:32 PM by some one

    Conversation id is already in use

    some one Newbie

      I'm getting a 'Conversation id is already in use' error which I'm not sure why it's happening. I am using natural conversations and am generating my own simple incrementor value for the conversations:


      <conversation name="regmem"
        parameter-name="memberID"
        parameter-value="#{memberreg.tempKey}"/>



      private static long tempKey = 0;
      ...
      // started at:
      // <page view-id="/register.xhtml">
      //   <begin-conversation join="true" conversation="regmem"/>
      // ..</page>
      public void start()
      {
          newMember = new Member();
          if(tempKey > Long.MAX_VALUE)
          {
              tempKey = 0;
          }
          tempKey++;
          started = true;
      }
      
      


      I have a conversation that runs for 5 pages (register, register1, register2, register3, and register4). When the jump from register3 goes to register4 I get the exception.


      The register3.xhtml and register4.xhtml page elements in my pages.xml file:


      <page view-id="/register3.xhtml"
        conversation-required="true"
        conversation="regmem">
        <restrict>#{memberreg.readyToConfirm}</restrict>
        <navigation from-action="#{memberreg.acceptInformation}">
          <redirect view-id="/register4.xhtml"/>
        </navigation>
        <navigation>
          <rule if="#{identity.loggedIn}">
            <redirect view-id="/memberadmin.xhtml"/>
          </rule>
       </navigation>
       </page>
       <page view-id="/register4.xhtml"
        conversation-required="true"
        conversation="regmem">
        <restrict>#{memberreg.acceptedInformation}</restrict>
        <end-conversation/>
      </page>



      memberreg.acceptInformation does not have any annotations although I tried the End annotation with beforeRedirect set to true and false, neither had any affect.


      The exception trace (part of it) is:


      WARNING: Conversation id is already in use: regmem:1
      java.lang.IllegalStateException: Conversation id is
      already in use: regmem:1
       at org.jboss.seam.core.Manager.updateCurrentConversationId
      (Manager.java:100)
       at org.jboss.seam.faces.FacesManager.beforeRedirect
      (FacesManager.java:76)
       at org.jboss.seam.faces.FacesManager.redirect
      (FacesManager.java:179)
       at org.jboss.seam.faces.Navigator.redirect
      (Navigator.java:50)



      I am using Tomcat 6, Seam 2.0.2. Any help appreciated.

        • 1. Re: Conversation id is already in use
          some one Newbie

          bump


          Anyone? I've seen one such issue at JIRA labeled as Natural conversation id already in use in seam-bay example but I am suspicious that this is actually fixed.


          Any developers have any ideas as to why this might be happening? By the way, the end-conversation element in the pages.xml file simply does nothing. In order to end a conversation one has to use the annotations approach but that only seems to work if you are not using the entity manager or a org.jboss.seam.faces.Renderer.


          • 2. Re: Conversation id is already in use
            Pete Muir Master

            Arron Ferguson wrote on Aug 28, 2008 05:02:


            bump



            Don't bump.



            Anyone? I've seen one such issue at JIRA labeled as Natural conversation id already in use in seam-bay example but I am suspicious that this is actually fixed.



            Yes, that issue is fixed. However you are seeing another problem I think. Please report in JIRA.

            • 3. Re: Conversation id is already in use
              some one Newbie

              Pete Muir wrote on Aug 31, 2008 12:25:


              Don't bump.


              Fair enough ... a four day turnaround is reasonable ... I didn't know if you guys were still checking the forum.



              Pete Muir wrote on Aug 31, 2008 12:25:


              Yes, that issue is fixed. However you are seeing another problem I think. Please report in JIRA.


              I'm actually seeing a few problems with natural conversations. However, it makes more sense if I wait for beta 2 to come out first (not sure when that is). I'll move up to beta 2 and run the same tests and see if I can produce the same problems. If I can (produce the same errors), I'll submit any problems to JIRA.

              • 4. Re: Conversation id is already in use
                Pete Muir Master

                Arron Ferguson wrote on Aug 31, 2008 21:40:


                Fair enough ... a four day turnaround is reasonable ... I didn't know if you guys were still checking the forum.



                I check the whole forum. But to be fair I'm catching up on about 3 weeks of posts ;-)




                Pete Muir wrote on Aug 31, 2008 12:25:


                Yes, that issue is fixed. However you are seeing another problem I think. Please report in JIRA.


                I'm actually seeing a few problems with natural conversations. However, it makes more sense if I wait for beta 2 to come out first (not sure when that is). I'll move up to beta 2 and run the same tests and see if I can produce the same problems. If I can (produce the same errors), I'll submit any problems to JIRA.


                BETA2 is no more, we are going straight to CR1. But there are no natural conversation issues I know of in JIRA, so get them in sooner rather than later so we can fix them for the GA :-)


                If you find something that is obviously a bug, don't be afraid to report it in JIRA (I check that every day) - the worst that can happen is that we reject it...

                • 5. Re: Conversation id is already in use
                  some one Newbie

                  Okay, I'm using 2.0.3 CR1 ... I'll set up a couple of examples and go onto JIRA for those. I'll do that in a couple of days. We have the August long weekend here (Canada) so I'm trying to do a little bit of unplugging. ;)


                  Thanks for the reply. :)