How can the orbdebug log help me?

Body

When trying to connect Corba probes for the first time you see errors that are not helpful, like this one from the probe log file

2017-01-26T15:24:51:  Error: E-JPR-000-000: Exception when subscribing to notification : org.omg.CORBA.UNKNOWN:   vmcid: 0x0  minor code: 0 completed: Maybe

Support ask for orb debug to be enabled and to send the file in, you want to understand what this message is and read the orb debug file for yourself.

From the orb debug

OUT GOING:   --- Probe request
Request Message
Date:          January 26, 2017 3:24:51 PM CEST

Operation:         obtain_notification_push_supplier

IN COMING:  ---- EMS response
Reply Message
Date:          January 26, 2017 3:24:51 PM CEST

Reply Status:      SYSTEM_EXCEPTION

From the IDL definition, obtain_notification_push_supplier() is a standard API call which is defined in CosNotifyChannelAdmin.idl. In this case. both Generic probe and end users IDL files have a common API declaration as follows:

       * Obtain a pull supplier proxy for this administration object.
       * @parm <code>ctype</code> - The client type.
       * @parm <code>proxy_id</code> - The ID of the newly created proxy,
       * i.e. the return value.
       * @returns A ProxySupplier object reference.
       * @raises AdminLimitExceeded If the number of proxies associated
       * with this administration object exceeds the MaxConsumers property.
       */ProxySupplier obtain_notification_push_supplier ( in ClientType ctype, out ProxyID proxy_id) raises ( AdminLimitExceeded );

In this case the IDL the probe was built on, is not the same version as the end user has.  Its most important to ensure the IDL on the EMS is not at a version the probe does not support.

Subscribe and follow us for all the latest information directly on your social feeds: