OS: AIX 5.1
Aix ML: All filesets for 5100-03_AIX_ML were found.
Not all filesets for 5100-04_AIX_ML were found.
APAR: All filesets for IY19177 were found.
LB ver: 5.0.2.9
Java ver: 1.3.1.0

This command is near the end of my default.cfg file:
dscontrol manager start manager.log 10004

If I take the "dscontrol manager start manager.log 10004" command out of my
default.cfg file and start LB, everything works fine. And once LB is
started, I
can run the "dscontrol manager start manager.log 10004" command from the cmd
line and things still work fine.

But if I put the "dscontrol manager start manager.log 10004" command in the
default.cfg file and try to start LB, it does not work. At that point if I
try
a "dscontrol status" it never returns. The only way to stop LB is to kill
it.

Here are the last lines in the manager.log and server.log files when LB does
not start OK:
manager.log
Nov03 14:15:12.915 EST MGR: Running in mode: KNDServer
server.log:
Nov03 14:15:08.923 EST SRV: AppendLoad command:  dscontrol manager start
manager.log 10004


Here are the last lines in the manager.log and server.log files when LB does
start OK:
manager.log:
Nov03 14:15:12.915 EST MGR: Running in mode: KNDServer
Nov03 13:39:44.085 EST MGR: bKeepServerHistory==true
server.log
Nov03 14:15:08.923 EST SRV: AppendLoad command:  dscontrol manager start
manager.log 10004
Nov03 13:52:19.839 EST SRV: The manager has been started.


It seems like some sort of timing issue with the manager starting too early.
I
tried putting a sleep in the default.cfg file but I don't think the sleep
gets
executed, so it does not help.

Any ideas?

Thanks......Paul

[ Post a follow-up to this message ]

Problem fixed.

When I ugraded to Java 1.3.1.11 the problem went away.

......Paul

"Paul Sala" <psala@btv.ibm.com> wrote in message
news:bo6g6k$5jqe$1@news.boulder.ibm.com...
quote:

> OS: AIX 5.1
> Aix ML: All filesets for 5100-03_AIX_ML were found.
>               Not all filesets for 5100-04_AIX_ML were found.
> APAR: All filesets for IY19177 were found.
> LB ver: 5.0.2.9
> Java ver: 1.3.1.0
>
> This command is near the end of my default.cfg file:
>  dscontrol manager start manager.log 10004
>
> If I take the "dscontrol manager start manager.log 10004" command out of

my
quote:

> default.cfg file and start LB, everything works fine. And once LB is
> started, I
> can run the "dscontrol manager start manager.log 10004" command from the

cmd
quote:

> line and things still work fine.
>
> But if I put the "dscontrol manager start manager.log 10004" command in

the
quote:

> default.cfg file and try to start LB, it does not work. At that point if I
> try
> a "dscontrol status" it never returns. The only way to stop LB is to kill
> it.
>
> Here are the last lines in the manager.log and server.log files when LB

does
quote:

> not start OK:
> manager.log
>  Nov03 14:15:12.915 EST MGR: Running in mode: KNDServer
> server.log:
>  Nov03 14:15:08.923 EST SRV: AppendLoad command:  dscontrol manager start
> manager.log 10004
>
>
> Here are the last lines in the manager.log and server.log files when LB

does
quote:

> start OK:
> manager.log:
>  Nov03 14:15:12.915 EST MGR: Running in mode: KNDServer
>  Nov03 13:39:44.085 EST MGR: bKeepServerHistory==true
> server.log
>  Nov03 14:15:08.923 EST SRV: AppendLoad command:  dscontrol manager start
> manager.log 10004
>  Nov03 13:52:19.839 EST SRV: The manager has been started.
>
>
> It seems like some sort of timing issue with the manager starting too

early.
quote:

> I
> tried putting a sleep in the default.cfg file but I don't think the sleep
> gets
> executed, so it does not help.
>
> Any ideas?
>
> Thanks......Paul
>
>

[ Post a follow-up to this message ]