One of the reason for this could be the number of CP workers is not enough to satisfy
the number of requests comming in. Try increasing the CP workers gradually.
The number
of max CP workers will depend on the RAM on your machine and RAM used by each
CP
worker(default setting is 100 MB per CP worker on Solaris at least)
--Navjeet
Mika Saastamoinen <[EMAIL PROTECTED]> wrote:
>More interesting errors...
>
>Can anyone please explain what this log entry
>(CNdSecurityException/Client Ticket timed out) means and under what
>conditions it is triggered? This seems to occur every now and then and
>when this happens we get the dreaded "Could not connect to the
>NetDynamics Application Server..." -error message in the browser.
>
>I'm fairly sure that this has happened to you as well, I've seen
>mentions of similar problems on this list before.
>
>We're running ND4.02 on NT.
>
>Thanks for your input,
> -Mika
>
>--- log entries ---->
> Error 226 ndCGI CNdServiceProxy:1:getNewWorker
>exception:cosi::stubs::CNdSecurityException:9
>86"LogServiceWorker.INdLogWorker.log Client ticket
>CGI||901717942470|2010896275 timed out"
>:IDL:cosi/stubs/CNdSecurityException:1.0
>
>Error 226 ndCGI CNdServiceProxy:1:handleException
>exception:CORBA::UNKNOWN:0 2 :IDL:omg.org/CORBA/UNKNOWN:1.0
>
>ndCGI CNdWebHit:1:processRequest exception:CORBA::SystemException:0 2
>:IDL:omg.org/CORBA/SystemException:1.0
>
>
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
