Bug 67

Summary:	MT_Cubit server won't start on VxWorks
Product:	TAO	Reporter:	levine
Component:	Performance Test	Assignee:	DOC Center Support List (internal) <tao-support>
Status:	RESOLVED ---
Severity:	blocker
Priority:	P2
Version:	0.4.1
Hardware:	All
OS:	All

Description levine 1999-07-13 08:49:48 CDT

The MT_Cubit server appears to lock up on VxWorks at startup:

spa server, "-f", "ior", "-t", "4", "-ORBobjrefstyle", "url"
value = 0 = 0x0
-> Creating servant 0 with high priority 101
(0|263012016) Beginning Cubit task with args = 'ace_main -f ior -t 4
-ORBobjrefstyle url -ORBEndpoint iiop://  -ORBSndSock 32768  -ORBRcvSock 32768
' and priority 101

Is the svc.conf OK for VxWorks?

Comment 1 Carlos O'Ryan 1999-07-21 11:52:59 CDT

Updated to "blocker", we shouldn't make the final release (and maybe not even
the beta) until this is fixed.

Comment 2 levine 1999-07-23 13:18:59 CDT

It works now, all of the sudden.  Maybe it
correlates with the RootPOA resolution problem,
Bug 68.  MT_Cubit runs just fine on VxWorks
(and LynxOS/PPC) now.