CA Service Management

 View Only
  • 1.  17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Posted Mar 23, 2020 12:37 PM
    Hi,
    after upgrade from 17.1 RU03 to 17.2 RU06 (GERMAN) submitting Cart does end in status 5001 and nothing else happens.
    What else I have to do to get catalog-requests from Cart running?

    Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------


  • 2.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior
    Best Answer

    Broadcom Employee
    Posted Mar 24, 2020 06:46 AM
    Hi,

    For anyone else that needs to check, 5001 is "Request Queued" - this usually means that your submitted cart has triggered a PAM request, but that has failed. If you check the view.log there should be more detail, but I suspect that the update has broken the integration in some way.

    Though I'll also mention that the new 17.2 RU07 has just been uploaded; you may wish to be using that if you're still in the testing period anyway.

    thanks
    Iain


  • 3.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Posted Mar 24, 2020 06:52 AM
    Hi Iain,
    great info (also for 17.2 RU07).
    I'll check it as soon as possible.

    Many thanks,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 4.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Posted Mar 27, 2020 04:28 AM
    Hi Iain,
    when checking integration from SLCM to Process Automation - Integration test is ok (PAM-Process run ok)

    When trying to submit my service from cart Request end in 'Request Queued' and view.log shows:
    2020/03/27 09.13.50.992 INFO [http-nio-8080-exec-15] [FormRendererServiceImpl] --------- Form is not found in cache
    2020/03/27 09.13.51.851 INFO [http-nio-8080-exec-15] [WPFServlet] END: Time taken for GET request, Node=icguinode.request_cart&NspPath=&ObjectID=&b2b=json&sh=paVAuEEiAIq3vxOIx7dxrWp%2FNa0%3D&portal=true&callback=jQuery16400908234352840378_1585296813761&_=1585296830180 is:1594
    2020/03/27 09.13.51.851 INFO [http-nio-8080-exec-15] [WPFServlet] NUmber of sqls=66
    2020/03/27 09.13.54.789 INFO [http-nio-8080-exec-16] [FormRendererServiceImpl] --------- Form is not found in cache
    2020/03/27 09.13.55.336 INFO [http-nio-8080-exec-16] [WPFServlet] END: Time taken for GET request, Node=icguinode.request_cart&NspPath=&ObjectID=&b2b=json-html&sh=paVAuEEiAIq3vxOIx7dxrWp%2FNa0%3D&portal=true&callback=jQuery16400908234352840378_1585296813762&_=1585296834311 is:953
    2020/03/27 09.13.55.336 INFO [http-nio-8080-exec-16] [WPFServlet] NUmber of sqls=63
    2020/03/27 09.13.59.133 ERROR [ActiveMQ Session Task-3] [RequestQueueListener] Unable to handle request failure due to JMS message exception: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.133 ERROR [ActiveMQ Session Task-3] [RequestQueueListener] Request Submission failed for request with exception:javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Unable to handle request failure due to JMS message exception: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Request Submission failed for request with exception:javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-3] [RequestQueueListener] Unable to handle request failure due to JMS message exception: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-3] [RequestQueueListener] Request Submission failed for request with exception:javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Unable to handle request failure due to JMS message exception: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.148 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Request Submission failed for request with exception:javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.211 ERROR [ActiveMQ Session Task-5] [DBJDBC] Could not set value in prepared statement of type:java.lang.Object at index:0
    2020/03/27 09.13.59.320 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Unable to handle request failure due to JMS message exception: javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.320 ERROR [ActiveMQ Session Task-2] [RequestQueueListener] Request Submission failed for request with exception:javax.jms.JMSException: Failed to build body from bytes. Reason: java.io.StreamCorruptedException: Inconsistent vector internals
    2020/03/27 09.13.59.508 INFO [http-nio-8080-exec-17] [WPFServlet] END: Time taken for POST request, icguinode.checkoutsubmit is:579
    2020/03/27 09.13.59.508 INFO [http-nio-8080-exec-17] [WPFServlet] NUmber of sqls=45
    2020/03/27 09.14.02.195 INFO [http-nio-8080-exec-18] [WPFServlet] END: Time taken for GET request, Node=icguinode.request_create&NspPath=&Args=10210&Args=true&ObjectID=10210&b2b=json-html&sh=paVAuEEiAIq3vxOIx7dxrWp%2FNa0%3D&portal=true&callback=jQuery16400908234352840378_1585296813763&_=1585296841446 is:672
    2020/03/27 09.14.02.211 INFO [http-nio-8080-exec-18] [WPFServlet] NUmber of sqls=63
    2020/03/27 09.14.02.601 INFO [http-nio-8080-exec-9] [WPFServlet] END: Time taken for GET request, Node=icguinode.request_cart&NspPath=&ObjectID=&b2b=json&sh=paVAuEEiAIq3vxOIx7dxrWp%2FNa0%3D&portal=true&callback=jQuery16400908234352840378_1585296813764&_=1585296842194 is:328
    2020/03/27 09.14.02.601 INFO [http-nio-8080-exec-9] [WPFServlet] NUmber of sqls=18

    Any idea for me?
    Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 5.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Broadcom Employee
    Posted Mar 27, 2020 04:32 AM
    Thanks for the "inconsistent vector internals" error - that allowed me to find the solution for you. There's a post-install step in the patch that doesn't appear to have been applied:

    https://knowledge.broadcom.com/external/article?articleId=141207

    If that doesn't solve it, let us know.

    regards
    Iain


  • 6.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Posted Mar 27, 2020 05:07 AM
    Hi Iain,
    your the greatest, many thanks.

    One thing left:
    While upgrading from 17.1.03 to 17.2 and 17.2.RU06 I think I answered Yes for autotmatically post-install-steps. But my protocol does not show it in Upgrading-process of catalog-server.

    What I  didn't see/recognize in documentation:
    Post-Install Tasks After Installing CA Service Catalog 17.2.0.6 on CA Service Catalog 17.2.0.2 or CA Service Catalog 17.2.0.1 or  CA Service Catalog 17.2.

    Many thanks again Iain.
    Have a nice weekend,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------



  • 7.  RE: 17.2 RU08 - Catalog after Upgrade from 17.1 RU03 - Request-Behavior

    Broadcom Employee
    Posted Mar 27, 2020 05:12 AM
    That's great to hear this is working for you now.

    Yes, there's something of an inconsistency between how SDM has the ability to apply these post-install steps automatically, but Catalog still has manual steps. The good news is that this should happen less frequently for 17.3.

    regards
    Iain