Hi Steve,
I can confirm that we experienced same behavior with Argus 1.4 SL5 sun
JAVA 6
The order of starting/stopping the services actually matters.
starting:
1.argus-pap
2.argus-pdp
3.argus-pepd
stopping:
1.argus-pepd
2.argus-pdp
3.argus-pap
Cheers,
Orlin
On 09/07/12 15:19, Stephen Jones wrote:
> I'll take that as a no, then!
>
> BTW: we think it might be the that the services are started. The must
> be stopped
> 3) PEPD
> 2) PDP
> 1) PAP
>
> and started
> 1) PAP
> 2) PDP
> 3) PEPD
>
> whether that fixes it, I don't know. We'll see.
>
> Steve
>
>
> On 07/09/2012 11:19 AM, Stephen Jones wrote:
>> Hi all,
>>
>> We run emi-argus-1.4.0-1.sl5.
>>
>> When we try to stop the services, after they have been up for only a
>> short while, they stop properly.
>>
>> But if we leave the services running for a while then try to stop
>> them, some of them (pepd, pdp) stay running. I have to kill -9 the
>> javas.
>>
>> They silently "fail to stop"; bash -x say " Unable to connect to
>> localhost:8155, perhaps the service is not running".
>>
>> This doesn't interfere with the functionlity of ARGUS; it's just a
>> nuisance. Anybody else a bit suspicious of these javas?
>>
>> Steve
>>
>>
>
>
--
Scanned by iCritical.
|