CODEWITHSUNDEEP
glassfishglassfish-3
lexicalscope
lexicalscope

Reputation: 7328

What might cause glassfish asadmin.bat start-domain 3.1.1 to exit with code 143?

I am running glassfish as a windows service created by the asadmin create-service command (where it starts with a command something like):

c:/xyz/glassfish/bin/asadmin.bat start-domain --verbose --domaindir C:\\xyz\\glassfish\\domains myDomain

I started the server then left it running with no further activities (no clients connecting to it, no scheduled task, etc).

After approximately 5hours 30mins it terminated with code 143.

Anyone know what might cause such behaviour?

Upvotes: 0

Views: 2895

Answers (2)

user3734115
user3734115

Reputation: 1

143 means the process was killed (SIGTERM).

You probably logged out.

Add this to the java line at the end of asadmin.bat

-Xrs

e.g.

%JAVA% -Xrs -jar "%~dp0..\modules\admin-cli.jar" %*

also add the following line in domain.xml

To set the -Xrs Java VM option, add the following line to the section of the as-install\domains\domain-name\config\domain.xmlfile that defines Java VM options:

-Xrs

If the Communications Server service is running, stop and restart the service for your changes to become effective.

Upvotes: 0

codeplumber
codeplumber

Reputation: 469

143 means the process was killed (SIGTERM).

You probably logged out.

Add this to the java line at the end of asadmin.bat

-Xrs

e.g.

%JAVA% -Xrs -jar "%~dp0..\modules\admin-cli.jar" %*

It's also a good idea to add "-Xrs" to the server. Go to the bin directory of your domain, edit the xml file (it's obvious what to do) and then

myDomainService stop 
myDomainService uninstall 
myDomainService install
myDomainService start

Upvotes: 2

Related Questions