Thingworx 7.4 Composer does not start the Tomcat service go down

[dbologna1]

Hi All,

I installed Thingworx 7.4 on VM Windows 7 64 bit using Postgres 9.4.

During the installation I did not receive warning or error (I used the Installing_ThingWorx_7.4_1.pdf downloaded from PTC).

When I use the url localhost:8080 (for access to apache-tomcat) or localhost:808/Thingworx/Composer/index.html  (for access to Composer) the

Apache-Tomcat service on machine go down.

Are there some suggestion?

Many Thank

Dimitri

[efernandez1]

I have the same problem, if I put the Thingworx.war file on my Tomcat folder, tomcat will not start and if I use the Tomcat manager app in localhost and try to upload the Thingworx.war, it will stop at 2% and then say there has been an error.

Any help would be appreciated thank you!

Eric

[ankigupta]

Hi Eric Fernandez​,

I would suggest you to open a Separate Thread as your case could be different.

If you are facing error in deploying the war file; you can place the war file directly in <Tomcat-Home>/webapps folder.

[efernandez1]

Hi Ankit Gupta​,

I understand there may be a difference as I am upgrading and he is installing it but the problem itself is the same, Tomcat server does not run when updating to 7.4. As I mentioned before, if I place the war file directly into the /webapps folder Tomcat will not start, and if I use the manager app to load the war file, Tomcat will stop and say connection lost.

I checked my Thingworx Applications log (this is the one inside Thingworx Composer right?) and there were no errors related to this upgrade.

Just went through all the updates steps again, put the license, added the djava, updated the database through the bat... Still same problem.

Thank you for your help.

Eric

[ankigupta]

Eric Fernandez​,

Please look for \ThingworxStorage\logs\ApplicationLog.log and tomcat logs.

Are new ThingWorx Application logs entries generated?

At what point in logs it stops working?

[efernandez1]

Ankit Gupta​, Sushant Pandey​

I have attached the logs and an image of what happens when I try to deploy the war. Thank you very much for your help.

Also I am using Windows 10, Tomcat 8.0, PostgressSQL 9.4.11.

Eric

[ankigupta]

Hi Eric Fernandez​,

As per Application logs; it seems that ThingWorx Application is already running.

At 2017-04-12 10:03:00.454+0100 systemRuntime= 41 hours

Was the old Exploded ThingWorx folder undeployed before deploying the new war file?

Or maybe some old folder of previous try of war file deployment exists in webapps folder.

[efernandez1]

Hi Ankit Gupta​,

I do not know what you mean by Exploded folder sorry, however I did stop tomcat, deleted the files (no remaining war files in the webapps folder) and dragged the new one.

[ankigupta]

Eric Fernandez I meant the unzipped folder i.e. the Thingworx folder. Thingworx.war file and Thingworx folder both needs to be deleted from the Tomcat/webapps folder.

[efernandez1]

Ankit Gupta Yes both have been deleted, currently I can't even go back to 7.3 by redeploying it, thankfully I have another laptop with Thingworx!

[ankigupta]

As the war file is not getting deployed; you probably would have an issue at Tomcat level. So, tomcat logs should show something around this.

[supandey]

Eric could you also please attach the Tomcat's catalina.out log from \\<tomcatInstallation>\logs. Which version of Tomcat are you using and which OS?

[AnnaAn]

Hi Dimitri Bologna,

Could you check if any error logs in your Tomcat?

1. I suppose this issue is caused by misconfiguration between ThingWorx and PostgreSQL connection.

2. Also to use the default ThingworxPlatform configuration directory, create a folder called ThingworxPlatform at the root of the drive where Tomcat was installed. Alternatively, if you want to specify the location where ThingWorx stores its settings, you can set the THINGWORX_PLATFORM_SETTINGS environment variable to the desired location.

Ensure that the folder referenced by THINGWORX_PLATFORM_SETTINGS exists and is writable by the Tomcat user. This environment variable should be configured as part of the system environment variables.

3. Place the platform-settings.json file into the ThingworxPlatform folder, and make sure you input a correct username and password you creatd in PostgreSQL.

Hope this helps,

Br,

Anna

[efernandez1]

Hi Anna,

Checked all you mentioned and everything was set alright. Still nothing, and there are no errors coming from Tomcat, it just does not start or while loading the war file it disconnects.

I can only think of doing a from scratch installation but that should not be needed. Thank you for your help.

Eric

[ankigupta]

Did you get a chance to check the ThingWorx Application logs too?

[dbologna1]

Hi Ann Many Thanks for your answer;

Could you check if any error logs in your Tomcat?

I'm not found error on Log files.

1. I suppose this issue is caused by misconfiguration between ThingWorx and PostgreSQL connection.

I do not Know but I used the PTC documentation during the installation.

2. Also to use the default ThingworxPlatform configuration directory, create a folder called ThingworxPlatform at the root of the drive where Tomcat was installed. Alternatively, if you want to specify the location where ThingWorx stores its settings, you can set the THINGWORX_PLATFORM_SETTINGS environment variable to the desired location.

Ensure that the folder referenced by THINGWORX_PLATFORM_SETTINGS exists and is writable by the Tomcat user. This environment variable should be configured as part of the system environment variables.

I configurated into Environmente variabile the item THINGWORX_PLATFORM_SETTINGS to link the C:\ThingworxPlatform

3. Place the platform-settings.json file into the ThingworxPlatform folder, and make sure you input a correct username and password you creatd in PostgreSQL.

I stored platform-settings.json into THINGWORX_PLATFORM_SETTINGS with correct username and password.

Which occurs can I do?

BR

Dimitri

[ankigupta]

Hi Dimitri Bologna​,

There are some changes in the ThingWorx 7.4 installation.

A new setting is required in 7.4: Djava.library.path=<path to Tomcat>\webapps\Thingworx\WEB-INF\extensions

And have you added the license file?

Other than this; did you add credentials for Database connection in platform-settings.json

If you still face the issue please check the Tomcat logs and ThingWorx Application logs and share the logs snippet to find the Root cause.

[dbologna1]

Hi Ankit,

I added all the setting for java

I added the licence file  and the platform-settings.json into THINGWORX_PLATFORM_SETTINGS .

BR

Dimitri

[supandey]

Dimitri, could you please attach/share you catalina.out from Tomcat. Which version of Tomcat are you using? Additionally, do note that Win7 is not an officially supported environment, even though it may work.

[dbologna1]

Hi Sushant,

in the following the last row of catalina.log

12:39:36.118 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina

12-Apr-2017 12:39:36.118 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.36

12-Apr-2017 12:39:36.274 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive C:\Tomcat 8.0.36\webapps\Thingworx.war

12-Apr-2017 12:39:54.977 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version:        Apache Tomcat/8.0.36

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          Jun 9 2016 13:55:50 UTC

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server number:         8.0.36.0

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Windows 7

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            6.1

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             C:\Java_1.8.0_101\jre

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version:           1.8.0_101-b13

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor:            Oracle Corporation

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE:         C:\Tomcat 8.0.36

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME:         C:\Tomcat 8.0.36

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=C:\Tomcat 8.0.36

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=C:\Tomcat 8.0.36

12-Apr-2017 12:40:24.155 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.endorsed.dirs=C:\Tomcat 8.0.36\endorsed

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=C:\Tomcat 8.0.36\temp

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=C:\Tomcat 8.0.36\conf\logging.properties

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dserver -Dd64

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:+UseG1GC

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dfile.encoding=UTF-8

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.library.path=C:\Tomcat 8.0.36\webapps\Thingworx\WEB-INF\extensions

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit

12-Apr-2017 12:40:24.171 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Tomcat 8.0.36\webapps\Thingworx\WEB-INF\extensions

12-Apr-2017 12:40:24.702 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-80"]

12-Apr-2017 12:40:24.874 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read

12-Apr-2017 12:40:24.889 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["ajp-nio-8009"]

12-Apr-2017 12:40:24.889 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read

12-Apr-2017 12:40:24.889 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 2034 ms

12-Apr-2017 12:40:24.936 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina

12-Apr-2017 12:40:24.936 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.36

12-Apr-2017 12:40:24.983 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive C:\Tomcat 8.0.36\webapps\Thingworx.war

12-Apr-2017 12:40:43.216 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.

BR

Dimitri

[ankigupta]

Hi Dimitri Bologna​,

Could you please share the ThingWorx application logs too?

[dupatel]

Dimitri Bologna​ Eric Fernandez​

Could you please try below steps and share feedback:

1.Stop tomcat

2.Delete Thingworx folder and Thingworx.war file present inside Tomcat webapps. ( Backup if you have something important)

3.Configure Java Options in Tomcat as below:

-Dserver -Dd64

-XX:+UseNUMA

-XX:+UseConcMarkSweepGC

-XX:PermSize=2048m

-XX:MaxPermSize=2048m

-Djava.library.path=C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\Thingworx\WEB-INF\extensions

Please refer KCS article for more details : https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS195506&lang=en_US

4. Copy the Thingworx.war file and place it in the following location of your Tomcat installation:

\Apache Software Foundation\Tomcat 8.0\webapps

5. Obtain the license.bin file from the download package and place the license.bin file in your ThingworxPlatform folder.

NOTE: The location of the ThingworxPlatform folder varies, as it is determined per your initial set up. Failure to place the license.bin in the ThingworxPlatform folder will result in ThingWorx not starting after deployment.

6. Launch Tomcat and verify Thingworx login.

If you still have issues please share your tomcat, java and OS versions along with Tomcat logs & ThingWorx Application logs.

-Durgesh

[efernandez1]

Hi Durgesh Patel​,

I have attached the logs in a previous message. Tomcat 8.0, Java JDK 1.8.0_121, Windows 10, PostgressSQL 9.4.11. Following your steps I was able to run Tomcat and it not shutting down, however it was like in a constant loading loop and nor the localhost nor Thingworx loaded.

Thank you very much,

Eric

[dbologna1]

Hi Durgest,

I configured yout setting into Java Configuration afther that the  service does not start.

In the file tomcat-stderr.log i found the following message

2017-04-12 12:54:20 Commons Daemon procrun stderr initialized

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=2048m; support was removed in 8.0

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=2048m; support was removed in 8.0

Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed

2017-04-12 12:54:27 Commons Daemon procrun stderr initialized

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=2048m; support was removed in 8.0

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=2048m; support was removed in 8.0

Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed

BR

Dimitri

[dbologna1]

Hi All,

I started the apache_tomcat service but during the deploy of Thingworx.war I received the following message

B.R.

Dimitri

[dbologna1]

Hi Ann,

I analyzed the log on Thingwork and I found the following message into ApplicationLog.log

2017-04-12 13:51:53.296+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Initializing Reference Caches...

2017-04-12 13:51:53.343+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Scheduler Engine...

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] ========================================

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Platform Subsystems

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] ========================================

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem ValueStreamProcessingSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [ValueStreamProcessingSubsystem]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem ValueStreamProcessingSubsystem is started

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem WSCommunicationsSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [WSCommunicationsSubsystem]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.c.p.m.DispatchingServerCommunicationModule] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Registering as EndpointBinding Registry Observer

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.c.c.m.CommunicationModuleBase] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Started DispatchingServerCommunicationModule [Running: true]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem WSCommunicationsSubsystem is started

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem UserManagementSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [UserManagementSubsystem]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem UserManagementSubsystem is started

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem TunnelSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [TunnelSubsystem]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem TunnelSubsystem is started

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem MessageStoreSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [MessageStoreSubsystem]

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem MessageStoreSubsystem is started

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Subsystem LicensingSubsystem is starting

2017-04-12 13:51:53.405+0200 [L: INFO] [O: c.t.s.s.Subsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Starting Subsystem [LicensingSubsystem]

2017-04-12 13:51:53.515+0200 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] ====================================================================

2017-04-12 13:51:53.515+0200 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Failed to load FlxCore library. Ensure it's in PATH (Windows) or LD_LIBRARY_PATH(other platforms) or set with the VM arg, -Djava.library.path. Error message : com.flexnet.licensing.DllEntryPoint.entry([B)I

2017-04-12 13:51:53.515+0200 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] ====================================================================

2017-04-12 13:51:53.515+0200 [L: WARN] [O: c.t.s.ThingWorxServer] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Shutting down the Platform.

BR

Dimitri

[dbologna1]

HI Ankit,

in attach the applicationlog.log

BR

Dimitri

[ankigupta]

Hi Dimitri Bologna​,

I found following error in ThingWorx Application logs:

2017-04-12 13:51:53.515+0200 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1] Failed to load FlxCore library. Ensure it's in PATH (Windows) or LD_LIBRARY_PATH(other platforms) or set with the VM arg, -Djava.library.path. Error message : com.flexnet.licensing.DllEntryPoint.entry([B)I

I can see that you have added -Djava.library.path=C:\Program Files\Apache Software Foundation\Tomcat 8.0\webapps\Thingworx\WEB-INF\extensions in Java but it seems that it was not added correctly. I would suggest you to re-check this and enter the ( - ) and ( \ ) manually. Usually Copy/Paste causes issue.

[dbologna1]

HI Ankit,

I take the path from Java Options and I run the command dir for that path.

I received the following list fo files

I'm using window 7 64 bit, can you see any problem ?

BR

Dimitri

[supandey]

Hi Dimitri, while checking for the logs you have shared above there is following error :

Failed to load FlxCore library. Ensure it's in PATH (Windows) or LD_LIBRARY_PATH(other platforms) or set with the VM arg, -Djava.library.path. Error message : com.flexnet.licensing.DllEntryPoint.entry([B)I

2017-04-12 13:51:53.515+0200 [L: ERROR] [O: c.t.s.s.l.LicensingSubsystem] [I: ] [U: SuperUser] [S: ] [T: localhost-startStop-1]

Can you please check if you have placed the license.bin file in correct location i.e. \\ThingworxPlatform\?

If this is missing it could explain the error since the license subsystem isn't starting up for you, as noted in the logs you have shared above.