Send a request to a conversation that has already been finished

Question

This error continually occurs. Any idea why?
          An attempt was made to send a request to conversation id []:169.254.17.244-b61346.100533c48f4.-7fea-gend.
          This is not a valid conversation id. The most common cause of this exception is an attempt to send a request to a conversation that has already been finished.
          Work around is to restart WLS and maybe this time it will not happen. WLS 8.1SP3.
          From: [email protected] ([email protected])
          Subject: Weblogic Tutorial Question - Need help
          This is the only article in this thread
          View: Original Format
          Newsgroups: weblogic.developer.interest.jms
          Date: 2004-09-17 09:12:33 PST
          Hi guys,
          I'm a Weblogic newbie. I have started working with Weblogic Workshop's
          Tutorial. I find them interesting and easy to follow. All was going
          well until I reached the Step 4 (Add a JMS Control). The url to this
          page is:
          http://edocs.bea.com/workshop/docs81/doc/en/workshop/reference/navResources.html
          After completing this tutorial to the end I get all the results
          mentioned, but I get additional error messages like these in my
          InvestigateTest.jws Web Service client:
          1095373714829
          investigate:creditScoreJMS:listener.onMessage
          External Service Callback investigate:creditScoreJMS:listener.onMessage
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          Executable Request:Callback.onMessage
          ConversationNotFound Exception
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          An attempt was made to send a request to conversation id 1095373714829.
          This is not a valid conversation id. The most common cause of this
          exception is an attempt to send a request to a conversation that has
          already been finished.
          Request Cancelled
          Submitted at Friday, September 17, 2004 10:25:52 AM EDT
          Processing Request
          Submitted at Friday, September 17, 2004 10:25:53 AM EDT
          Request Complete
          Submitted at Friday, September 17, 2004 10:25:53 AM EDT
          I cannot figure out why I'm getting these. I'm doing everything as
          described in the Tutorial. Can somebody tell me what I'm doing wrong.
          I would greatly appreciate.
          Thanks.
          Adnan

Answer 1

hi
          We just encountered this problem while load testing using JMeter. While it may not be the same scenario, we have found that we can consistently trigger this error if:
          a) multiple threads from the same client are invoking the service (i.e. a JMeter using JavaSamplerClient can do this)
          b) the web service is conversational according to the polling design pattern recommended in the WLW doco: i.e.
          startQuery()(one-way) conversation phase = start
          checkQueryStatus() conversation phase = continue
          fetchQueryResponse()conversation phase = finish
          c) buffering is enabled for the startQuery() operation.
          d) the number of threads > 3 (might occur very infrequently <= 3 - cant remember)
          This is reproducable in our WLS/WLW 8.1 SP2/SP3 environment.
          With buffering enabled - errors occur
          With buffering not enabled - no errors
          On reflection, buffering isn't really needed for our usage so we removed it, however the errors might indicate a bug or unsupported use case
          Regards
          Jim Nicolson