On 5 Feb, 20:34, Yakov Gerlovin <yakov.gerlo...@[EMAIL PROTECTED]
> wrote:
> Hi,
>
> First of all, I hope your solved the CORBA.INV_OBJREF exception
> problem.
First of all, many thanks for trying to help :-)
> Now, concerning your question, if you're on Solaris, may be using
> 'truss' can help your to find the problem.
Unfortunately not. I already have the stack trace. Besides, when using
truss on event driven programs it will typically just show the
routines that drive it round the event loop. For CORBA programs that
will be the socket read and select calls.
> BTW, it is usually a good
> idea to specify the platform you're working on (even if you're writing
> in Java).
Solaris 8.
> When you say 'When we start the 3 servers', do you mean you start them
> after the reboot or you're starting them after those servers were
> shuted down (restarted)?
There is no reboot. The machine stays up the whle time. I should have
been more specific. When I said "restart tings" that was a bit vague.
What I meant was running a script that finds the server pids (using
ps) then issues a kill -9. Then I run the script that starts the
servers again.
> Are your servers configured to run always on
> the same ****t?
There is no ****t configuration as such. This is CORBA, where ****ts are
an implementation detail buried in the IOR. I have made no changes in
this area so OW will choose whatever ****ts it sees fit. There is a
particular ****t number used to communicate with the orbix daemon, it
is ****t 1570, er, I think. Anyhow this also is the default and if
there was a problem with that then the Orbix daemon would not start.
> Is it possible other processes are using those ****ts?
No.
>
> Regards,
> Yakov
|
