Discussion:
[omniORB] omniORB 4.1.0 on Altix/SLES 10 "Cannot create worker for endpoint" error
Nelson, Howard C
2007-07-19 04:05:45 UTC
Permalink
Hi,



Warning - newbie question!



I am porting a CORBA application from MIPS/Irix 6.5 (using omniORB
4.0.4) to SGI Altix/SuSE Linux 10 (using omniORB 4.1.0). I have
successively built omniORB 4.1.0 on the Altix/SLES 10 machine and
re-compiled/re-linked the application. omniNames comes up and runs
fine. When I run the application as the root user, the application
connects with the name service successively and the application runs
properly. However, when I start the application as a non-root user, I
get the following error:



omniORB: Cannot create a worker for this endpoint:
giop:tcp:[::ffff:127.0.0.1]:2809 from giop:tcp:[::ffff:127.0.0.1]:36433



After reading the FAQ, I removed the 127.0.0.1 entry in the /etc/hosts
file, but get the same error even when the IP address is used.



Here is a trace with ORBtraceLevel set to 25:



omniNames -start 2809 -logdir
/usr/people/nelsohc/css_3_7_0_0_pre/css/scripts/../logs &

omniORB: Distribution date: Tue Nov 28 13:27:23 GMT 2006 dgrisby

omniORB: My addresses are:

omniORB: 127.0.0.1

omniORB: 134.189.150.219

omniORB: 7.0.1.1

omniORB: ::1

omniORB: Maximum supported GIOP version is 1.2

omniORB: Native char code sets: ISO-8859-1 UTF-8.

omniORB: Transmission char code sets: ISO-8859-1(1.2) ISO-8859-1(1.1)
ISO-8859-1(1.0) UTF-8(1.2) UTF-8(1.1).

omniORB: Native wide char code sets: UTF-16.

omniORB: Transmission wide char code sets: UTF-16(1.2).

omniORB: Information: the omniDynamic library is not linked.

omniORB: Current configuration is as follows:

omniORB: DefaultInitRef (file) =

omniORB: DefaultInitRef (args) =

omniORB: abortOnInternalError = 0

omniORB: abortOnNativeException = 0

omniORB: acceptBiDirectionalGIOP = 0

omniORB: acceptMisalignedTcIndirections = 0

omniORB: bootstrapAgentHostname =

omniORB: bootstrapAgentPort = 900

omniORB: clientCallTimeOutPeriod = 0

omniORB: clientConnectTimeOutPeriod = 0

omniORB: clientTransportRule = * unix,ssl,tcp

omniORB: configFile = /etc/omniORB.cfg

omniORB: connectionWatchImmediate = 0

omniORB: connectionWatchPeriod = 50000

omniORB: copyValuesInLocalCalls = 1

omniORB: diiThrowsSysExceptions = 0

omniORB: dumpConfiguration = 0

omniORB: endPoint = giop:tcp::2809

omniORB: endPointPublish = addr

omniORB: giopMaxMsgSize = 2097152

omniORB: giopTargetAddressMode = KeyAddr

omniORB: id = omniORB4

omniORB: idleThreadTimeout = 10

omniORB: inConScanPeriod = 180

omniORB: lcdMode = 0

omniORB: maxGIOPConnectionPerServer = 5

omniORB: maxGIOPVersion = 1.2

omniORB: maxInterleavedCallsPerConnection = 5

omniORB: maxServerThreadPerConnection = 100

omniORB: maxServerThreadPoolSize = 100

omniORB: maxSocketRecv = 2147483647

omniORB: maxSocketSend = 2147483647

omniORB: nativeCharCodeSet = ISO-8859-1

omniORB: nativeWCharCodeSet = UTF-16

omniORB: objectTableSize = 0

omniORB: offerBiDirectionalGIOP = 0

omniORB: oneCallPerConnection = 1

omniORB: outConScanPeriod = 120

omniORB: poaHoldRequestTimeout = 0

omniORB: poaUniquePersistentSystemIds = 1

omniORB: principal = [Null]

omniORB: scanGranularity = 5

omniORB: serverCallTimeOutPeriod = 0

omniORB: serverTransportRule = * unix,ssl,tcp

omniORB: strictIIOP = 1

omniORB: supportBootstrapAgent = 0

omniORB: supportCurrent = 1

omniORB: supportPerThreadTimeOut = 0

omniORB: tcAliasExpand = 0

omniORB: threadPerConnectionLowerLimit = 9000

omniORB: threadPerConnectionPolicy = 1

omniORB: threadPerConnectionUpperLimit = 10000

omniORB: threadPoolWatchConnection = 1

omniORB: traceExceptions = 1

omniORB: traceFile = [stderr]

omniORB: traceInvocationReturns = 0

omniORB: traceInvocations = 0

omniORB: traceLevel = 25

omniORB: traceThreadId = 0

omniORB: traceTime = 0

omniORB: unixTransportDirectory = /tmp/omni-%u

omniORB: unixTransportPermission = 777

omniORB: useTypeCodeIndirections = 1

omniORB: verifyObjectExistsAndType = 1

omniORB: Initialising incoming endpoints.

omniORB: Instantiate endpoint 'giop:tcp::2809'

omniORB: Bind to address ::

omniORB: Publish specification: 'addr'

omniORB: Try to publish 'addr' for endpoint
giop:tcp:134.189.150.219:2809

omniORB: Publish endpoint 'giop:tcp:134.189.150.219:2809'

omniORB: Starting serving incoming endpoints.



Wed Jul 18 16:20:43 2007:



Starting omniNames for the first time.

Wrote initial log file.

omniORB: Adding key<NameService> (activating) to object table.

omniORB: State key<NameService> (activating) -> active

Read log file successfully.

omniORB: Creating ref to local: key<NameService>

target id : IDL:omg.org/CosNaming/NamingContextExt:1.0

most derived id: IDL:omg.org/CosNaming/NamingContextExt:1.0

Root context is
IOR:010000002b00000049444c3a6f6d672e6f72672f436f734e616d696e672f4e616d69
6e67436f6e746578744578743a312e300000010000000000000064000000010102001000
00003133342e3138392e3135302e32313900f90a00000b0000004e616d65536572766963
65000200000000000000080000000100000000545441010000001c000000010000000100
01000100000001000105090101000100000009010100

Checkpointing Phase 1: Prepare.

Checkpointing Phase 2: Commit.

Checkpointing completed.

omniORB: AsyncInvoker: thread id = 1 has started. Total threads = 1

omniORB: giopRendezvouser task execute for giop:tcp:134.189.150.219:2809

omniORB: SocketCollection idle. Sleeping.

Jul 18 16:20:45.154 - (INFO) - [AppServer] Starting AppServerManager...

Jul 18 16:20:45.154 - (INFO) - [AppServer]
NameService=corbaname::localhost:2809

omniORB: Exception trying to start new thread.

omniORB: Server accepted connection from
giop:tcp:[::ffff:127.0.0.1]:36433

omniORB: Exception trying to start new thread.

omniORB: Cannot create a worker for this endpoint:
giop:tcp:[::ffff:127.0.0.1]:2809 from giop:tcp:[::ffff:127.0.0.1]:36433

omniORB: Server connection refcount = 1

omniORB: Server connection refcount = 0

omniORB: Server close connection from giop:tcp:[::ffff:127.0.0.1]:36433

omniORB: Error in network receive (start of message):
giop:tcp:127.0.0.1:2809

omniORB: throw giopStream::CommFailure from
giopStream.cc:874(0,MAYBE,COMM_FAILURE_WaitingForReply)

omniORB: throw COMM_FAILURE from omniObjRef.cc:777
(MAYBE,COMM_FAILURE_WaitingForReply)

Nameservice not found

Jul 18 16:20:45.160 - (EXCEP)- [AppServer] CORBA::Exception

./startAppServer.sh: line 103: 4396 Aborted
${APPSERVER_BIN}/appservermanager -csshome ${SW_HOME} -port $NS_PORT
-mcip $MCIP -mcttl $MCTTL -minport $MINPORT -maxport $MAXPORT -minkey
$MINKEY -maxkey $MAXKEY -threadStart true

./startAppServer.sh: line 105: 4391 Terminated
${CORBA_BIN}/omniNames -start $NS_PORT -logdir $LOG_DIR





All help is greatly appreciated!!!



Howard Nelson

Software Engineer

Lockheed Martin Aerospace





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20070718/66abb255/attachment-0001.htm
Duncan Grisby
2007-07-20 19:04:46 UTC
Permalink
On Wednesday 18 July, "Nelson, Howard C" wrote:

[...]
Post by Nelson, Howard C
I am porting a CORBA application from MIPS/Irix 6.5 (using omniORB
4.0.4) to SGI Altix/SuSE Linux 10 (using omniORB 4.1.0). I have
successively built omniORB 4.1.0 on the Altix/SLES 10 machine and
re-compiled/re-linked the application. omniNames comes up and runs
fine. When I run the application as the root user, the application
connects with the name service successively and the application runs
properly. However, when I start the application as a non-root user, I
giop:tcp:[::ffff:127.0.0.1]:2809 from giop:tcp:[::ffff:127.0.0.1]:36433
omniORB: Exception trying to start new thread.
For some reason, as a non-root user you can't start a thread to service
the incoming connection. Perhaps you have a very small limited number of
threads a normal user can create?

Try making a simple program that uses omni_thread to create some threads
and see if it works. You could try the diner example in
src/examples/thread to see if that works.
Post by Nelson, Howard C
After reading the FAQ, I removed the 127.0.0.1 entry in the /etc/hosts
file, but get the same error even when the IP address is used.
That's ancient history. There's no longer any need to do that.

Cheers,

Duncan.
--
-- Duncan Grisby --
-- ***@grisby.org --
-- http://www.grisby.org --
Loading...