Product

Platform

Operating system

Windows 2000

Error

E 07Oct02 06:12:37.218-PDT [000.000] ycs669-61 prinergyoperator workshop com.creo.araxi.USVW.USVW_eFatalIDL: Unrecoverable Corba error occurred.

at com.creo.araxi.UORB.UORB_ExceptionHandler.HandleSystemException(UORB_ExceptionHandler.java:175)

at com.creo.araxi.UORB.UORB_ExceptionHandler.HandleCORBAException(UORB_ExceptionHandler.java:100)

at com.creo.araxi.UORB.UORB_ExceptionHandler.HandleCORBAException(UORB_ExceptionHandler.java:90)

at com.creo.araxi.USVW.USVW_JobLauncherServer.GetObjReferenceForJob(USVW_JobLauncherServer.java:103)

at com.creo.araxi.USVW.USVW_JobServer.DoResolve(USVW_JobServer.java:174)

at com.creo.araxi.USVW.USVW_aVersionedWrapper$ResolveThread.ThreadMain(USVW_aVersionedWrapper.java:191)

at com.creo.araxi.UCMN.UCMN_AraxiThread.run(UCMN_AraxiThread.java:86)

Caused by:

org.omg.CORBA.IMP_LIMIT: can't create new thread minor code: 1330577410 completed: No

at com.ooc.OB.Util.unmarshalSystemException(Util.java:127)

at com.ooc.OB.GIOPClientWorker.execute(GIOPClientWorker.java:544)

at com.ooc.OB.GIOPClientWorkerThreaded.receiverRun(GIOPClientWorkerThreaded.java:498)

at com.ooc.OB.GIOPClientWorkerThreaded$ReceiverThread.run(GIOPClientWorkerThreaded.java:67)

Build : 1, Fri Aug 23 13:39:54 2002

Symptoms

The system was just upgraded to Prinergy 2.1. When attempting to open a job which was created in Prinergy 2.0.x, the workshop appears to hang for several minutes. Eventually, workshop will crash with the Corba error shown above.

Cause

If the registry key HKLM\Software\Creo\Araxi\Settings\System\JobDaemonNodeList contains the primary server name in lowercase letters, Prinergy 2.0.x will store the primary server name in theJckdDaemonHostName column in lowercase letters.

NOTE: Jobs created in Prinergy 2.1 do not exhibit this problem because Prinergy substitutes the value %PRIMARY% in place of the primary server name in the JckdDaemonHostName column.

Solution

The problem is fixed in Minor Update 2.1.0.6. Install 2.1.0.6 when it becomes available.

For systems affected by this problem before 2.1.0.6 is released, change the computer name in the database:

1) Start SQLPLUS:

- D:\> SQLPLUS prinergy/araxi@araxidbserver

2) Query the database for the computer names stored in the JckdDaemonHostName column:

- SQL> SELECT distinct JckdDaemonHostName FROM DBCS_Jacket;

3) Find out how many jobs are affected:

- SQL> SELECT count(*) from DBCS_Jacket where JckdDaemonHostName='lowercase_primary_server_name';

- replace lowercase_primary_server_name with the actual computer name using lowercase letters.

- record the count of the number of rows affected.

4) Update the database:

- SQL> UPDATE DBCS_Jacket SET JckdDaemonHostName='UPPERCASE_PRIMARY_SERVER_NAME' where JckdDaemonHostName='lowercase_primary_server_name';

- replace UPPERCASE_PRIMARY_SERVER_NAME with the actual computer name using uppercase letters.

- replace lowercase_primary_server_name with the actual computer name using lowercase letters.

5) Ensure the count of the number of rows affected by the update is the same as the number of rows found in step 3.

6) If the number of rows is the same, commit the transaction:

- SQL> commit;

Permanent fix:

See also

Keywords

oracle, registry, workshop

Technical contact(s)

Stan Yoshida

Submitted by

Stan Yoshida

Date submitted

08 Oct 2002