No transaction manager found - software error

[pawel.masloch]

Hello,

I seem to be getting an error related to Transaction Manager: ‘No transaction manager found - software error’.

This is rather weird one as right after Apache TomCat restart the issue goes away immediately. However, it is a show stopper considering the use of forms at our end.

Has anyone come across and managed to solve this type of problem before?

Thx.

[Jon]

Do you know what circumstances lead to this error message?
Is it reproduceable?
Maybe cut and paste a section of the server log into this post.

[pawel.masloch]

Hi Jon,

Thx for getting back.

Unfortunately, I haven't figure it out how I can possibly reproduce it intentionally, however I can confirm it is intermittent and random yet persistent.

There isn't much in the log, but I am more than happy to share it:

Localhost_access_log:

00.123.45.678 - [17/Apr/2015:08:47:10 +0100] "GET /ufs/ufsmain?formid=GREEN_WASTE_FORM&ebd=0&ebz=1_1429256876814 HTTP/1.1" 200 1297
00.123.45.678 - [17/Apr/2015:08:47:10 +0100] "GET /ufs/BrowserCheck?ebz=1_1429256830674&formid=GREEN_WASTE_FORM&ebase_CSSOK=true&ebase_CKOK=true&ebase_JSOK=true HTTP/1.1" 302 -
00.123.45.678 - [17/Apr/2015:08:47:11 +0100] "GET /ufs/ufsmain?ebz=1_1429256830674&formid=GREEN_WASTE_FORM HTTP/1.1" 302 -
00.123.45.678 - [17/Apr/2015:08:47:11 +0100] "GET /ufs/errorPage?ebz=1_1429256830674 HTTP/1.1" 200 1064
00.123.45.678 - [17/Apr/2015:08:47:25 +0100] "GET /ufs/ufsmain?formid=BW_BOOKING_FORM&STAFF=1&TEST_FLAG=0&ebd=0&ebz=1_1429014501596 HTTP/1.1" 302 -
00.123.45.678 - [17/Apr/2015:08:47:25 +0100] "GET /ufs/errorPage?ebz=2_1429256844745 HTTP/1.1" 200 1064
00.123.45.678 - [17/Apr/2015:08:52:28 +0100] "GET /ufs/ufsmain?formid=BW_BOOKING_FORM&STAFF=1&TEST_FLAG=0&ebd=0&ebz=1_1429014501596 HTTP/1.1" 302 -
00.123.45.678 - [17/Apr/2015:08:52:28 +0100] "GET /ufs/errorPage?ebz=3_1429257148337 HTTP/1.1" 200 1064

Catalina log is almost empty and has got no relevant entries.

...then the restart took place and forms seems to be OK for the rest of the day.

Please drop me an email with your details should you wish to discuss this in details. Otherwise, I am a bit tide up with internal policies, sorry.

Please, ask Hovik should you struggle to unearth my email address.

Cheers.

[Jon]

It's probably easier to pursue this by raising a support call.

[Hovik]

These errors were caused by incorrect settings in ufs.xml (see below). Correcting these settings and restarting Tomcat has stopped all the errors.

Several comments about contents of ufs.xml:

1. maxWait and maxIdle are redundant. They were used by the earlier version of the connection pool package but they are now obsolete. The only relevant settings are min and max.

2. checkLevel="2" is our strong recommendation for ALL database connections except embedded Derby connections. It means that when Tomcat needs a new DB connection, it uses one from the connection pool first (these are created by the min setting at startup time), but it first issues the validationQuery using that connection and if the query fails, Tomcat discards that connection and grabs a new one. This one setting solves many DB connection issues.

3. validationQuery should NEVER include a ; (semi-colon) at the end. This will always give an error if checkLevel="2".

4. preparedStatementCache should ALWAYS be set to 0 (zero).

Some of the connections defined within the designer also have the above issues.


Remember that changing ufs.xml will cause Tomcat to restart.

I suggest:

Stop Tomcat
Clear the cache (delete contents of folder UfsServer\tomcat\work\Catalina\localhost\ufs)
Amend and save ufs.xml
Start Tomcat