Spring Tool Suite 3.6.1 and Pivotal tc Server Developer Edition are ignored
I was trying to change the logging that takes place since Pivotal tc Server Developer version 3.0 and I found out that the java process that starts the server never reads the logging.properties file in the catalina database.
I created a new Pivotal tc Server 3.0 with a new instance named diff-instance and added a bio. When finished, a logging.properties file was created in the / diff -instannce / conf folder. I started the server and stopped it by looking at the settings (F3 or open in the server list). It says:
config path:
Option selected: use tc Server installation (takes control of tc Server installation) server path (catalina.base): / diff-instance
Then I stop the server and change the logging.properties file and notice that no changes I make to this logging.properties file are ever reflected on the tc server.
I brought the good old sysinternals (www.sysinternals.com) tools into my Swiss army knife and started to mount. Much to my surprise, the logging.properties file in the catalina.base directory folder is never read by the javaw.exe process (only the logging.properties file in / jre / lib is read). This explains what I saw.
I have 3 important questions related to this:
- Why is the logging.properties file never read?
- Where is the method of documenting developer version of Pivotal tc Server? I have looked at "Getting Started with Pivotal tc Server" at http://tcserver.docs.pivotal.io/index.html under "tc Runtime Instance Configuration Files" on page 29 and it says this file should be used. In addition, "Pivotal tc Server Administration" has an entire section "Configuring logging for tc Runtime" on page 50 that goes on to talk about this same file.
- I know there is a lot of glue between tc Server developer and STS. It's all about defining a new server and about server locations that can be defined as shown below,
everything is very cool, but where is the documentation for this?
everything is very cool, but where is the documentation for this?This page describes the old version of the tc server and how to change the log. It also links to the logging.properties file in catalina.base.
source to share
Actually, this was recorded by the STS group. See the comment from Alex Boyko about the tc Server night update site http://dist.springsource.com/snapshot/TOOLS/eclipse-integration-tcserver/nightly in JIRA STS-3998 . In STS 3.6.3, if you select "Help / Install New Software" and you insert this update site and select it, you should be able to install the tc server integration version in STS 3.6.3 which fixes this. This should be fixed in STS 3.6.4.
source to share
Have you tried to create a tc server instance from the command line and change the log for that instance?
Did you have logging capabilities working with previous versions of tc Server like 2.9.x?
If it worked, but the logging for the instance created with STS didn't work, then I think you found a bug in the Tc Server Eclipse integration code. I suspect that perhaps the option for the logging.properties file needs to be specified at the time the tc server is instantiated in the create command in some way. Please file a bug report for this issue here: https://issuetracker.springsource.com/browse (project: Spring Toolkit, component: SERVER)
source to share