I noticed what could be an interesting point.
In the /Library/Tomcat/bin/catalina.sh file is setted the following line as
but when I type ps -e | grep Tomcat, it gives the following:
14952 ttys000 5:31.03 /Library/Java/Home/bin/java
16845 ttys000 0:00.00 grep Tomcat
Thus the -Djava.awt.headless=true setting does not appear here.
Would it mean that the setting comes from somewhere else then the
/Library/Tomcat/bin/catalina.sh file ?
If I do a modification on the /Library/Tomcat/bin/catalina.sh file, at what
stage should I rester the installation procedure ?
Just restart Tomcat (/Library/Tomcat/bin/shutdown.sh and then
The other thing I noticed, confirming that the Djava.awt.headless option is not
taken in account is that I get a windowed application named
org.apache.catalina.startup.Bootstrap that remains as mentioned by Jari.
What surprises me is that when I type the command :
/Library/Tomcat/bin/shutdown.sh I get the following output:
Using CATALINA_BASE: /Library/Tomcat
Using CATALINA_HOME: /Library/Tomcat
Using CATALINA_TMPDIR: /Library/Tomcat/temp
Using JRE_HOME: /Library/Java/Home
Using CLASSPATH: /Library/Tomcat/bin/bootstrap.jar
Using CATALINA_PID: /Library/Tomcat/catalina_pid.txt
PID file found but no matching process was found. Stop aborted.
And the Java process is still running…
Both /Library/Tomcat/work/Catalina/localhost/base2 and
/Library/Tomcat/work/Catalina/localhost/_/ directories are empty
I have set the owner of /Library/Tomcat/work directory and inner files to
_appserver user and _appserveradm group as defined for the tomcat process.
The other odd thing I am just discovering is that when typing the command line
'ps auxw | grep tomcat'
I only get one time out of three the shell process
And each time it has an other pid. Is it supposed to be so ?
That would explain why when I want to shutdown the Tomcat process it is aborted.
Thanks again for taking of your time.
Le 12 sept. 2013 à 20:48, Nicklas Nordborg <nicklas.nordb...@med.lu.se> a écrit
> On 2013-09-12 16:22, Jari Häkkinen wrote:
>> On 2013-09-11 10:57, Laurent Troxler wrote:
>>> going through the log files here is what I can get:
>>> system.log: repeating those two lines
>>> Sep 11 10:32:00 seridi java: kCGErrorFailure: Set a breakpoint @
>>> CGErrorBreakpoint() to catch errors as they are logged.
>>> Sep 11 10:32:02 seridi com.apple.launchd (org.apache.tomcat):
>>> Throttling respawn: Will start in 8 seconds
>>> /Library/Tomcat/logs/catalina.2013-09-11.log :
>>> Sep 11, 2013 10:52:05 AM org.apache.catalina.startup.Bootstrap
>>> SEVERE: Class loader creation threw exception
>>> java.lang.InternalError: Can't connect to window server - not enough
> I think this could be that the Java runtime engine is starting up
> various threads for handling GUI interactions. I have not seen this
> preventing startup of Tomcat or BASE but it can lead to issues with
> generating plots and other image handling (much) later.
> The installation instructions mention that "headless mode" should be
> enabled to prevent this. See 4:th bullet in the Tomcat section
> In any case, I don't think this is related to BASE not working, but it
> needs to be fixed sooner or later and better to rule it out as soon as
> How ServiceNow helps IT people transform IT departments:
> 1. Consolidate legacy IT systems to a single system of record for IT
> 2. Standardize and globalize service processes across IT
> 3. Implement zero-touch automation to replace manual, redundant tasks
> The BASE general discussion mailing list
> unsubscribe: send a mail with subject "unsubscribe" to
How ServiceNow helps IT people transform IT departments:
1. Consolidate legacy IT systems to a single system of record for IT
2. Standardize and globalize service processes across IT
3. Implement zero-touch automation to replace manual, redundant tasks
The BASE general discussion mailing list
unsubscribe: send a mail with subject "unsubscribe" to