ERROR: Failed to refresh lock for store '$sys.nonfailsafe', [ERRSTR = org.hibernate.exception.GenericJDBCException: Cannot open connection.
book
Article ID: KB0085464
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Message Service
-
Not Applicable
-
Description
Resolution: The errors may be due to an intermittent network problem between the EMS server machine and the database server machine or resource utilization on one of the host is high.
-- Database server being temporarily unavailable. -- Network issue. -- Database max user limit is reached. -- EMS server file descriptor limit is reached.
Check with your network/database administrator and see if there was any network/database problem. If the problem is due to the database max user limit is reached, ask your DBA to find out which application is using too many connections. The EMS server itself set the c3p0 connection pool size, hence it won’t use many connections. If Tibco BW is using a lot of connectones, you can specify the maximum connections for a JDBC Connection resource activity. The number of physical connections made from that activity won't go beyond the threshold. If you still have the problem, collect the following information which covers the problem period:
- Ems server log file: Run tibemsadmin command “set server log_trace=+JVM,+JVMERR,+DBSTORE”, additional database trace information will be put into the EMS log file. - strace/truss output: strace -fvall -ttT -p <ems_pid> -o strace.log/ truss -aefDl -v all -r ALL -w ALL -o <Output-File> -p <PID>
- tcpdump: tcpdump –s 0 –i <NIC> -w <output file> - database logs - ask your Database Administrator to check this and advise of any problems noted around this time.
Issue/Introduction
ERROR: Failed to refresh lock for store '$sys.nonfailsafe', [ERRSTR = org.hibernate.exception.GenericJDBCException: Cannot open connection.