Automic Workload Automation

  • Private Community
 View Only
Back to discussions
Expand all | Collapse all

JWP and JCP fail to start due to mismatch of own version and entry in UC_ZDU

  • 1.  JWP and JCP fail to start due to mismatch of own version and entry in UC_ZDU

    Posted Oct 06, 2022 03:03 PM
    After upgrading a database clone of a production V12.2.2 system to V21.0.4 for testing purposes the JWP and JCP fail to start due to a mismatch of their own version and an entry in UC_ZDU. All traditional WP and CP started normally. The server has been set up especially for this test case and there are no remainings of installations of other Automic versions.

    20221006/205108.291 - 1 U00045062 Error: The version of the initial data or the stored JWP component (change list) in UC_ZDU does not match the version of this JWP.
    20221006/205108.291 - 1 U00045063 Upgrade mode: 'N' - Number of entries in UC_ZDU: '1'
    20221006/205108.291 - 1 U00045064 The entry for message queue set '1' and version '12.2.2+hf.4.build.1555333595857' and change list '1555053522' cannot be used for this JWP.
    20221006/205108.510 - 35 U00045025 OSGI ['com.automic.indexsearch']: 'FrameworkEvent ERROR'
    20221006/205108.510 - 35 Unhandled Exception in thread Framework Event Dispatcher: Equinox Container: 8912706e-b217-4b3c-95d4-47aa9a79e2f7
    20221006/205108.510 - 35 U00045014 Exception 'java.lang.IllegalStateException: "The service has been unregistered"' at 'org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getReferenceImpl():285'.
    20221006/205108.510 - 35 U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.
    20221006/205108.510 - 35 U00003450 The TRACE file was opened with the switches '0000000000000000'.
    20221006/205108.979 - 35 U00003449 Output to the TRACE file is finished.
    20221006/205108.979 - 34 U00003432 Termination of Server 'AWA12#WP' initiated.

    This error reminds me of https://community.broadcom.com/enterprisesoftware/communities/community-home/digestviewer/viewthread?MessageKey=ae9bcf11-0188-482c-9f02-154e594c3990&CommunityKey=2e1b01c9-f310-4635-829f-aead2f6587c4&tab=digestviewer#bmae9bcf11-0188-482c-9f02-154e594c3990

    Any ideas or similar experience in the community?

    ------------------------------
    [JobTitle] -- [CompanyName]
    ------------------------------


  • 2.  RE: JWP and JCP fail to start due to mismatch of own version and entry in UC_ZDU

    Posted Oct 07, 2022 06:51 AM
    Even a gradual approach (V12.2.2 --> V12.2.11 --> V12.3.9 --> V12.0.4) results in the same problem. Now I tend to update the UC_ZDU with the proper values.

    ------------------------------
    [JobTitle] -- [CompanyName]
    ------------------------------

    Original Message


  • 3.  RE: JWP and JCP fail to start due to mismatch of own version and entry in UC_ZDU

    Posted Oct 07, 2022 10:30 AM
    Updating the column ZDU_JwpChngeList which was Null with the proper value doesn't fix the issue. JWP still complains about a version mismatch and indeed the changelist numbers of the JWP and the initial data differ! This applies to both builds of 21.0.4 of 2022-10-05 and 2022-10-06. 

    All MQ1 and MQ2 tables are empty. I have no idea where in the database this old version number 12.2.2 is stored and how to get rid of it.

    In a local test installation of V21.0.2 the changelist numbers of the JWP and the initial data match exactly.

    ------------------------------
    Managing Consultant -- setis GmbH (Germany)
    ------------------------------

    Original Message