Service seems to randomly fail to start

Question

I wonder if I am missing something obvious here. The service never fails to start when started manually. It only fails occasionally from a system startup.
The Java jar needs to run with a user's credentials and networking. Why would this fail randomly? What can I do to cause a restart? If the service did fail all I do is log in and run svcadm disable rrtserver then svcadm enable rrtserver it's like I am missing some dependency that causes failure but is up when I log in. Any ideas?
Here's the file /lib/svc/method/rrtserver
. /lib/svc/share/smf_include.sh
# Java config
JAVA_HOME=/usr/jdk/instances/jdk1.5.0
JAVA=${JAVA_HOME}/bin/java
JAVA_OPTS="-server -Xms64m -Xmx1g"
# RRT config
RRT_HOME=/disk80/RRT/Programs/network
RRT_CONSOLE=${RRT_HOME}/logs/svc.log #/dev/null
# Instance specific
RRT_SERVICE=`echo $SMF_FMRI | sed 's/.*:\(.*\)/\1/'`
PIDFILE=${RRT_HOME}/rrtserver_${RRT_SERVICE}.pid
# Environment
PATH=/disk80/RRT/utils:/bin:/usr/bin
LD_LIBRARY_PATH=/usr/sfw/lib:${JAVA_HOME}/jre/lib/i386/server:${JAVA_HOME}/jre/lib/i386
RRTPATH=/disk80/RRT
export PATH LD_LIBRARY_PATH RRTPATH
rrt_start() {
     echo "Starting RRT Server..."
     $JAVA $JAVA_OPTS -jar $RRT_HOME/network-server.jar $RRT_HOME/server.xml >$RRT_CONSOLE 2>&1 & echo $! >${PIDFILE}
rrt_stop() {
     echo "Stopping RRT Server..."
     PID=`cat ${PIDFILE}`
     kill -TERM $PID
     pwait $PID
     rm ${PIDFILE}
case "$1" in
'start')
        rrt_start
'restart')
     echo "Restarting RRT Server..."
        rrt_stop
     rrt_start
'stop')
        rrt_stop
        echo "Usage: $0 { start | restart | stop }"
        exit 1
esac
exit $SMF_EXIT_OKHere's the file /var/svc/manifest/application/rrtserver.xml
<?xml version="1.0"?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="manifest" name="rrtserver">
     <service name="application/rrtserver" type="service" version="1">
          <create_default_instance enabled="true" />
          <single_instance />
          <dependency name="loopback" grouping="require_any" restart_on="error" type="service">
               <service_fmri value="svc:/network/loopback" />
          </dependency>
          <dependency name="filesystem" grouping="require_all" restart_on="error" type="service">
               <service_fmri value="svc:/system/filesystem/local"/>
          </dependency>
          <dependency name="autofs" grouping="require_all" restart_on="error" type="service">
               <service_fmri value="svc:/system/filesystem/autofs"/>
          </dependency>
          <dependency name="network" grouping="optional_all" restart_on="error" type="service">
               <service_fmri value="svc:/milestone/network" />
          </dependency>
          <exec_method name="start" type="method" exec="/lib/svc/method/rrtserver start" timeout_seconds="180">
               <method_context>
                    <method_credential user="aces" group="rrt" />
               </method_context>
          </exec_method>
          <exec_method name="restart" type="method" exec="/lib/svc/method/rrtserver restart" timeout_seconds="60">
               <method_context>
                    <method_credential user="aces" group="rrt" />
               </method_context>
          </exec_method>
          <exec_method name="stop" type="method" exec="/lib/svc/method/rrtserver stop" timeout_seconds="60">
               <method_context>
                    <method_credential user="aces" group="rrt" />
               </method_context>
          </exec_method>
          <!-- sub-process core dumps shouldn't restart session -->
          <property_group name="startd" type="framework">
               <propval name="ignore_error" type="astring" value="core,signal" />
          </property_group>
          <template>
               <common_name>
                    <loctext xml:lang="C">RRT server</loctext>
               </common_name>
          </template>
     </service>
</service_bundle>

Answer 1

[root]# ps -e | grep httpd
1234 1234 httpd
1235 1234 httpd
1236 1234 httpd
1237 1234 httpd
1238 1234 httpd
1239 1234 httpd
1240 1234 httpd
1241 1234 httpd
Your ps headers aren't there, but it looks like the columns are 'pid' 'ppid' 'name'   If this is the case, then these are threads, created by the parent pid of 1234, though these numbers look modified. Getting a pid of 1234 is quite lucky.
If this is the case then it's not spawning procs, but threads and is normal. Why they don't appear when manually started may be a configuration thing, as in it loads a different config file. What command do you use to start it manually?