How can I integrate PCRE versions based on CORBA GIOP 1.2 with SilverStream 3.5 and 3.7?

Download PDF version of this faq: SilverStream_Patch.pdf
FAQ# 26-12190102

Issue:

We have indeed experienced some limited incompatibilities with SilverStream 3.5 and 3.7, primarily due to bugs in the jBroker ORB that SilverStream embeds in its application server. Some customers upgrading from PCRE 2.4 to PCRE 2.6/3.6 have encountered these compatibility problems, especially if they were simultaneously upgrading to SilverStream 3.5 or 3.7.

SilverStream and Dynalivery together found a bug in jBroker concerning support of CORBA GIOP 1.2. As a courtesy to Dynalivery customers, SilverStream provided us with patch that fixed this bug for SilverStream 3.7.0, 3.7.1, and 3.7.2. To the extent that you may be using SilverStream v3.7.0, 3.7.1, or 3.7.2 we strongly recommend that you upgrade to SilverStream 3.7.3 or later.

If upgrading is not possible immediately, then please apply the patch provided by SilverStream as a temporary solution.

SilverStream’s tech support can provide users with a similar patch for SilverStream 3.5 and jBroker 2.1.

Possible CORBA errors that have been associated with this bug are:

class com.mobileapps.pcre.PCREServerError CORBA error: org.omg.CORBA.COMM_FAILURE:
unable to connect to xxx.xxx.xxx.xxx:2254 minor code: 0 completed: No

ServerError: 'CORBA error: org.omg.CORBA.UNKNOWN: minor code: 1330446336 completed: No'

PCREError: com.mobileapps.pcre.PCREGatewayError: CORBA error: org.omg.CORBA.OBJECT_NOT_EXIST:
minor code: 0 completed: No

Connect : error com.mobileapps.pcre.PCREGatewayError: CORBA error: org.omg.CORBA.COMM_FAILURE:
unable to locate object at XXXXXXXX:1716 minor code: 0 completed: No

Solution:

Our friends at SilverStream have acknowledged this bug after some dialogue between Borland (publisher of Visibroker), Dynalivery, and SilverStream in June 2001 and have provided us with a jBroker 3 patch for Dynalivery customers. (The patch would also apply to anyone using Borland Visibroker 4.1 or higher with jBroker 3 alone – independent of either Parallel Crystal or SilverStream.)

The patch can be downloaded from the “Patches and Updates” section of our website.
http://www.dynalivery.com/customersupport/customersupport.html#patches

To apply the patch, follow these precise step-by-step instructions:

1. Download the patch from the link above.
2. Shut down the SilverStream server and Designer
3. Copy the provided jbroker-rt.jar file to <path_to_SilverStream37>\jre\lib\ext directory.
    Allow this file to overwrite the one that is there. (see diagram below)
4. After the new file has been copied and the old file has been overwritten, reboot.
5. Restart the SilverStream server and Designer
6. Execute your application again.

Important Notes:

1. When upgrading Parallel Crystal versions you must load the new Dynalivery Java client (middle-tier) library .jar files and recompile your SilverStream/Java application and then restart the SilverStream Application Server and Designer.
   
   
2. Again, it is preferrable to upgrade to SilverStream Application Server 3.7.3 or later rather than to apply the patch to which we refer to in this FAQ.
   
   
3. Some customers have not been successful in their first attempts to apply the patch due to skipping one of the above steps, labeled #1-6, or by renaming rather than overwriting (copying over) jbroker-rt.jar. PLEASE DO NOT RENAME THE ORIGINAL jbroker-rt.jar AS SOME OF THE JAVA CLASSES MAY STILL BE USED AND THEREFORE CAUSE THIS PATCH TO FAIL.