Service Virtualization

 View Only

  • 1.  CICS Virtualization - Error with the protocol handler. The JMS Infrastructure cannot be accessed. 

    Posted Jun 11, 2018 11:04 AM

    Hi All, 

     

    When we trying to setup the recorder and RR pair configuration to do the CICS virtualization we are getting below mentioned protocol handler error message with "CICS LINK (DPL)" transport protocol. Requesting you to advise about this error. 

     

    INFO  - QuickSearch$QuickSearchPainter.hideSearch

    ERROR - [DevTest AGENT:][ERROR][22964][36][AWT-EventQueue-0][Jun 8, 2018 10:12:52 AM] JMS producer for the mainframe endpoint is null.

    ERROR - [DevTest AGENT:][ERROR][22964][36][AWT-EventQueue-0][Jun 8, 2018 10:12:52 AM] JMS session for the mainframe endpoint is null.

    ERROR - [DevTest AGENT:][ERROR][22964][36][AWT-EventQueue-0][Jun 8, 2018 10:12:52 AM] The Mainframe Client Message Handler can't connect to the LISA Broker.

    ERROR - The Mainframe Client Message Handler can't connect to the LISA Broker.

    WARN  - LisaException detail Null Mainframe Bridge Endpoints exception is n/a

    ERROR - The protocol handler encountered an error creating the message handler.

    WARN  - LisaException detail The protocol handler encountered an error creating the message handler. exception is

     

    ============================================================================

    | Exception:

    ============================================================================

    | Message:     Null Mainframe Bridge Endpoints

    ----------------------------------------------------------------------------

    ============================================================================

     CICS Transport Layer Error

     

    Recently, we are experiencing this error and we didn't made any changes around with DevTest property file and lib directory. 



  • 2.  Re: CICS Virtualization - Error with the protocol handler. The JMS Infrastructure cannot be accessed. 
    Best Answer

    Posted Jun 11, 2018 03:24 PM

    Can you confirm for us that the Broker service, LPAR agent and CICS Agents are running? If you have privileges, log onto the Portal application and navigate to the Agents and ensure you can see the CICS agents. Let's make sure everything is running as a first step. If the DevTest, LPAR and CICS agents are running, can you provide any screenshots that might help us further isolate where the exception is thrown? 

     

    For example, when you run the RR Pair Recorder Wizard and select CICS LINK as the protocol, does the wizard fail immediately or do you see the screen allowing you to select an LPAR, Region, and Program?

    If you see this screen, do you see any available programs or does the exception occur here?

    My general feeling is that you will need to open a ticket with CA Support so they can walk through the various configurations and ensure that nothing is misaligned.



  • 3.  Re: CICS Virtualization - Error with the protocol handler. The JMS Infrastructure cannot be accessed. 

    Posted Jun 12, 2018 01:58 PM

    Hi Joel,

     

    Thanks for your response.

     

    As we could see Broker service, LPAR and CICS Agents are running. Portal also we could see CICS agents configuration in Agents tab.

     

    We are getting error when we run the RR Pair or Recorder Wizard and select CICS LINK as the protocol and click next. Once we pressed next button we are getting this below error message as pop up window.

     

     Error message

     

    After Press Ok button, Recorder window navigated to next window with same error message like below

     

    error

    Workstation.log  --> We could see below error message. 

    2018-06-12 17:39:48,982Z (13:39) [AWT-EventQueue-0] ERROR System.err - [DevTest AGENT:C][ERROR][10276][26][AWT-EventQueue-0][12-Jun-2018 1:39:48 PM] JMS producer for the mainframe endpoint is null.
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] ERROR System.err - [DevTest AGENT:C][ERROR][10276][26][AWT-EventQueue-0][12-Jun-2018 1:39:48 PM] JMS session for the mainframe endpoint is null.
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] ERROR System.err - [DevTest AGENT:C][ERROR][10276][26][AWT-EventQueue-0][12-Jun-2018 1:39:48 PM] The Mainframe Client Message Handler can't connect to the LISA Broker.
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] ERROR com.itko.lisa.vse.stateful.protocol.cics.CICSMessageHandler - The Mainframe Client Message Handler can't connect to the LISA Broker.
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] WARN com.itko.lisa.test.LisaException - LisaException detail Null Mainframe Bridge Endpoints exception is n/a
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] ERROR com.itko.lisa.vse.stateful.protocol.cics.CICSProtocolHandler - The protocol handler encountered an error creating the message handler.
    2018-06-12 17:39:48,997Z (13:39) [AWT-EventQueue-0] WARN com.itko.lisa.test.LisaException - LisaException detail The protocol handler encountered an error creating the message handler. exception is

    ============================================================================
    | Exception:
    ============================================================================
    | Message: Null Mainframe Bridge Endpoints
    ----------------------------------------------------------------------------
    ============================================================================



  • 4.  Re: CICS Virtualization - Error with the protocol handler. The JMS Infrastructure cannot be accessed. 

    Posted Jun 12, 2018 02:55 PM

    Thanks for inputs. It was brought to my attention that a ticket was opened to look at the issue.