cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

Automatic shutdown of JVM and tomcat.

AP_9587236
17-Peridot

Automatic shutdown of JVM and tomcat.

While installing thingworx. Tomcat is not running and successful_license_capability_response.bin is not created in the ThingworxPlatform folder.

 the following errors where noticed in application log:

 

1. Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (3). Last acquisition attempt exception:
2. Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicResourcePool@71f704f6 is interrupting all Threads waiting on a resource to check out. Will try again in response to new client requests.
3. *** CRITICAL ERROR ON STARTUP: Connections could not be acquired from the underlying database!
4. *** Web Application STATE is being set to ERROR! ***
5. >>>>>>> PLATFORM SHUTDOWN START <<<<<<<<<

 

In tomcat logs:

1. Apache Commons Daemon procrun stdout initialized.

 

because of automatic shutdown of tomcat, not proceeded with db installation and configuration. Kindly guide me what is wrong with this installation.

3 REPLIES 3
abjain
13-Aquamarine
(To:AP_9587236)

@AP_9587236 Are you using manual installation of thingworx or through installer? Database installation and configuration should happen before installing thingworx. Are you following our help center document for thingworx installation?

 

There are many articles for this error:

https://www.ptc.com/en/support/article/CS235937

https://www.ptc.com/en/support/article/CS351187

https://www.ptc.com/en/support/article/CS321828

https://www.ptc.com/en/support/article/CS282332

 

AP_9587236
17-Peridot
(To:abjain)

We are not trying to do intallation or upgradation now. The server was running fine for an year. Suddenly now the tomcat is stopping automatically

slangley
23-Emerald II
(To:AP_9587236)

Hi @AP_9587236.

Your initial post indicated the problem was related to installation.  Based on the error you provided there, ThingWorx is unable to connect to the database.  If the database is on a different server than ThingWorx, you could have a firewall issue, etc.  You would need to begin your testing by verifying that you can connect to the database server from the ThingWorx server.  There could be any number of configuration issues, however, depending on the database you're running.

 

If the issue is unrelated to installation as you indicated in your last post, you need to start by reviewing the ThingWorx logs. But this issue could be caused by any number of things.  For example, if you're running multiple applications on the same server, you may be running out of resources.  Therefore, it may be necessary to check the o/s logs as well.   Have you made recent changes?  Have you checked the database logs?

 

Regards.

 

--Sharon

Top Tags