Troubleshoot upgrades

This topic describes known problems that may occur during upgrades, and provides solutions to those problems.

Problem: The installation of B2Bi takes a very long time (more than a hour).

Cause: Long install time can be due to various issues. See the following solution section.

Solution:  

Compare logs

If you have access to an earlier "normal" installation installer.log file, compare the installer.log files of the normal and long installation.

Investigate specific tasks

If the installer takes a abnormal time on a specific task, investigate the possible root cause (database access, particular command hanging ...)

Investigate file copy speed

If B2Bi 2.3.1 installation tasks are completed in a linear manner compared to the normal installation (but more slowly), the issue is likely a disk issue. A B2Bi installation is primarily a matter of copying files to the installation machine, so check the copy speed..

Run the following command to estimate the copy speed.

Note: This procedure requires disk space of a 1.7 Go file.

dd if=/dev/zero of=foobar count=4096 bs=409600

This command returns a summary similar to the following:

4096+0 records in

4096+0 records out

1677721600 bytes (1.7 GB) copied, 2.81981 s, 595 MB/s

If the copy takes more than 30 seconds, the disk is too slow and the installation will be abnormally long. Check with your IT administrator on how the disk speed can be increased.

 

Problem: When exporting the entire system configuration, the export file is empty. No error is displayed in the UI, but an NPE error is written to the cn.log:

2014-06-24 14:49:26,540 - ERROR [qtp2607345-640] (ExportSystem.exportSystem:243) - Failure exporting system java.lang.NullPointerException at com.cyclonecommerce.collaboration.profile.ExportSecurity.addPartnerException(ExportSecurity.java:309) at com.cyclonecommerce.collaboration.profile.ExportSecurity.addPartnerExceptionElements(ExportSecurity.java:282) at com.cyclonecommerce.collaboration.profile.ExportSecurity.exportMessageValidation(ExportSecurity.java:114) at com.cyclonecommerce.collaboration.profile.ExportInterchangeCommunityProfile.buildMessageValidationElement(ExportInterchangeCommunityProfile.java:349) at com.cyclonecommerce.collaboration.profile.ExportInterchangeCommunityProfile.getCommunityProfile(ExportInterchangeCommunityProfile.java:322) at com.cyclonecommerce.collaboration.profile.ExportInterchangeCommunityProfile.exportCommunity(ExportInterchangeCommunityProfile.java:227) at com.axway.exportimport.ExportSystem.getCommunitiesAndTheirPartners(ExportSystem.java:380) at com.axway.exportimport.ExportSystem.exportSystem(ExportSystem.java:137)

Cause:  

The cause of this problem may be:

  • An error in the configuration of the UI - for example no value set in a mandatory field or drop-down list.
  • Data incorrectly migrated from a previous version of B2Bi or Interchange.

Solution:  

Check the Java exception in the cn.log for clues about which UI object is incorrectly configured.

Example:

A corrupted Message Validation error is thrown.

Investigation of related objects reveals that a Validation Rule is configured in the UI, however the mandatory "Partner name" field is empty. After the invalid Message Validation Rule is deleted, the system export works normally.

 

Problem: CN (control node) fails to start after upgrade. Unsupported major .minor version appears in cn.log.

Example <hostname>_cn_console.log display:

<date/time> ERROR An unexpected error occurred while trying to start.

<date/time> ERROR Please check your configuration

<date/time> ERROR java.lang.reflect.InvocationTargetException

<date/time> ERROR at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

<date/time> ERROR at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

<date/time> ERROR at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

<date/time> ERROR at java.lang.reflect.Method.invoke(Unknown Source)

<date/time> ERROR at com.axway.clusterold.startup.Boot$MainRunnable.run(Boot.java:106)

<date/time> ERROR at java.lang.Thread.run(Unknown Source)

<date/time> ERROR at com.axway.cluster.extensions.thread.EventedThread.primRun(EventedThread.java:102)

<date/time> ERROR at com.axway.cluster.extensions.thread.EventedThread.run(EventedThread.java:80)

<date/time> ERROR Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/jetty/util/ssl/SslContextFactory : Unsupported major.minor version 51.0

<date/time> ERROR at java.lang.ClassLoader.defineClass1(Native Method)

<date/time> ERROR at java.lang.ClassLoader.defineClassCond(Unknown Source)

Cause:  

Incorrect Java version. Java 7 is required.

Solution:  

  1. Stop B2Bi.
  2. Create a backup of the file: <B2Bi_install_directory>/Interchange/bin/environment.
  3. Make sure the B2Bi installation has the correct java version (Java7) under <B2Bi_install_directory>/b2bi/Java/...
  4. Open : <B2Bi_install_directory>/Interchange/bin/environment and check the "set JAVA_HOME" value.
  5. This reference must point exactly to the Java directory in <B2Bi_installdirectory>\Java\
  6. For example (Windows): C:\My_B2Bi\Java\win-x86\jre7_u51_64\
  7. Note: Axway products should use the Java version provided by the Axway product installation.
  8. Save the changes.
  9. Start B2Bi.

 

Problem: When upgrading from 1.5 to 2.3.1, pickups are not created on the integration engine.

Cause: After the upgrade from B2Bi 1.5 to B2Bi 2.3.1, in cases where the character set data conversion option on the IBM MQ Series application pickup is set to "Custom", the MQ pickups in the configuration are missing values for the "Coded character set ID" which are needed in B2Bi 2.3.1. B2Bi cannot create the MQ pickups without this data. This defect blocks all pickups from being broadcast to the B2Bi integration engine.

Solution:  

  1. Upgrade to B2Bi 2.3.1 .
  2. Start the Interchange and Integrator servers but do not start the trading engine node.
  3. In B2Bi 2.3.1 you can use the manageTrading utility to start and stop the trading engine node from the command line.
  4. Go to <B2Bi_install_directory\Interchange\tools\
  5. Launch manageTrading with one of the options:
    • manageTrading help
    • manageTrading processing start – Starts all trading engines on the local server.
    • manageTrading processing stop – Stops all trading engines on the local server.
    • manageTrading consumption pause – Engages the Pause Consumption system throttler across all trading engines in the cluster.
    • manageTrading consumption resume – Stops the Pause Consumption system throttler across all trading engines in the cluster.
  6. Delete the MQ pickups and re-add the MQ pickups.
  7. You can either add pickups through the B2Bi UI wizards, or import them from a backup. When they are added or imported, the pickups are automatically broadcast to the integration engine , along with all other missing pickups.

Related Links