Originally Posted by TB0ne
Short answer: something changed, so change it back to the working state. Otherwise, post details, and we can try to help you.
I haven't changed anything. But I am not sure if someone else changed something on the server machine or not.
I remember what I did yesterday is: I set the 'svcadm -t disable service-name' because I want to test if the service can be started by rebooting. But since I can't reboot the machine at this moment - the other colleague are working at the machine. I try to enable it again with 'svcadm enable service-name'. Since here the service can't be started.
What details do you want? I will attach the svcs -x and svcs -l here.
root@S001AP61-TEST (vws-tst1) # svcs -xv wsvws:default
svc:/application/jboss/wsvws:default (wsvws service)
State: maintenance since Fri Jul 12 07:33:01 2013
Reason: Restarting too quickly.
Impact: This service is not running.
root@S001AP61-TEST (vws-tst1) # svcs -l wsvws:default
name wsvws service
state_time Fri Jul 12 07:33:01 2013
root@S001AP61-TEST (vws-tst1) #
From the error id in svcs -x 'http://sun.com/msg/SMF-8000-L5', the description is: The service terminated and was restarted more frequently than normal. The Solaris Service Manager placed the service into maintaenance mode instead of restarting it again.
I don't understand what here "restarted more frequently than normal" means.