AdminServer start: Undefined server.start.retryInterval property - Forum - OpenEdge RDBMS - Progress Community

AdminServer start: Undefined server.start.retryInterval property

 Forum

AdminServer start: Undefined server.start.retryInterval property

This question is not answered

Hello,

The customer faced out with some strange message in admserv.log after restart AdminServer:

[2017/01/09@07:53:13.049+0300] [3] [OpenEdge] /usr/dlc/bin/jvmStart -d -w $WRKDIR -o stdout -e 1 /usr/dlc-11.5/jdk/jre/bin/java -classpath /usr/dlc-11.5/jdk/lib/tools.jar:/usr/dlc-11.5/java/progress.jar -DInstall.Dir=/usr/dlc -Djava.security.policy=/usr/dlc-11.5/java/java.policy -DCanonicalName=fathom1.bisfilial:ID=NameServer com.progress.nameserver.NameServer -i NS1 -r rmi://bisfilial:20931/NS1 -f /usr/dlc/properties/ubroker.properties
[2017/01/09@07:53:13.224+0300] [3] [OpenEdge] Failed to start Service
[2017/01/09@07:53:13.224+0300] [3] [OpenEdge] Undefined server.start.retryInterval property
[2017/01/09@07:53:13.224+0300] [3] [OpenEdge] Undefined server.start.retryCount property

I have not found anything like this in ProKB.

What is the meaning of these messages and what to do with this?

Regards,
Valeriy

All Replies
  • This might be helpful- knowledgebase.progress.com/.../000047299  

  • Thank you!

    But,

    >>Upgrade to OpenEdge version 11.5.1 or later.

    This customer alredy have OpenEdge 11.5.1 (SUSE Linux Enterprise Server 11 SP1)

    [2017/01/09@07:51:24.921+0300]=== Progress Version 11.5.01.025 1191 ===

    Also in  admserv.log is no any exception. There is also no ads0.exp file.

    We will try to add parameters "-Dserver.start.retryInterval = 30 -Dserver.start.retryCount = 3" and see what happens.

  • Adding these parameters resolve the problem.

    But I do not understand something:

    1. Why earlier AdminServer (11.5.1) worked without these parameters?

    2. -Dserver.start.retryInterval = 30,  this value it is minutes or seconds?

    3. I still do not understand for what these parameters?

  • These parameters are implemented as part of #PSC00288458
     
    Thanks,
    Satya