Does the JCA connector have a timeout mechanism

Question

          Hi,
          does anybody know if JCA connectors has got a timeout mechanism in Weblogic 6.1?
          I don't support transactions in my JCA connector.
          My point of view is that there should be some one because
          if I do a call from the SessionBean and the connection of the
          EIS hangs, the ejb blocks.
          Thanks
          Andre
          

Answer 1

Hi Andre,
          in addition to add,
          Once you initiated the request/process, how much time to wait to get the
          result. If you are working with any EAI middleware vendors and developing
          adapters/connectors, then the timeout implementation and setting also be
          provided by them. so that you can directly use like below, the "execute"
          method in the implementation class of Interaction .
          This is a sample
          public boolean execute(InteractionSpec ispec, Record input, Record output)
          throws ResourceException
          //the below statement will do some process in the method "sendRequest",
          it may do some
          //repetitive process to get some values from your EIS and wait until
          the specified timeout
          //mentioned.
          m_connection.sendRequest(input, ispec.getExecutionTimeout());
          If you are not depends on any EAI vendor, Or if the API what you will use to
          connect EIS system and execute some thing and get result from EIS, if they
          are not providing a kind of waiting for some time to get result, then you
          may need to implement your own Timer Thread in the connector to wait for the
          specified timeout.
          Thanks
          Kumar
          "Björn Hamrin" <[email protected]> wrote in message
          news:[email protected]...
          > Andre Genser wrote:
          >
          > > Hi Björn,
          > >
          > > that means that I have to implement a Workerthread that is controlled
          > > by its father
          > > thread (SessionBean) context.
          > > Perhaps I should use the java.util.Timer but in my point of view there
          > > is a conflict
          > > because in ejb I may not start threads
          > > and I invoke the JCA connector inside an ejb.
          > >
          > > Andre
          >
          > You are of course right. A bean should not start a thread. This is
          > because resource management should be left to the EJB server. However
          > there might not be any other reasonable way to implement a timeout. As
          > long as you make sure that there is no more than one extra thread
          > started for the connector, not one per connection, you should be
          > alright. I have an extra background thread running in my connector with
          > no harmful effects.
          >
          > /Björn
          >