You are on page 1of 2

ID : SEVERE-2050132

Time : 2019-12-17 06:59:12.930 GMT-0500


i3 Time : 2019-12-17 11:59:12.930 GMT
Thread : Thread-16 (ID: 1852509142)
Class : com.precise.shared.connectionpool.ConnectionManager
Method : initPool
Logger : com.precise.shared.connectionpool.rhel7-ora12
Msg : Unable to get registry information. Returned code: Error unable to read
pool information from registry. URL=registry/connection-pools/jdbc/pools/pw.
This message has appeared for the second time in 2 hours. Further occurrences will
be ignored.
Frame : caused by: Error unable to read pool information from registry.
URL=registry/connection-pools/jdbc/pools/pw
caused by: failed getting data from path registry/connection-pools/jdbc/pools/pw
caused by: error returned from registry
root cause: com.precise.shared.util.xml.XMLAnswerException: No data exists in
registry file registry/connection-pools/jdbc/pools/pw.
at com.precise.shared.util.xml.XmlAnswer.checkNoError(XmlAnswer.java:158)
at
com.precise.shared.util.xml.XmlAnswer.checkNoErrorAllLevels(XmlAnswer.java:92)
at
com.precise.shared.util.xml.XmlAnswer.checkNoErrorAllLevels(XmlAnswer.java:98)
at
com.precise.shared.util.xml.XmlAnswer.checkNoErrorAllLevels(XmlAnswer.java:87)
at
com.precise.shared.util.registry.QuickRegistry.checkError(QuickRegistry.java:627)
at
com.precise.shared.util.registry.QuickRegistry.getData(QuickRegistry.java:412)
at
com.precise.shared.util.registry.QuickRegistry.getData(QuickRegistry.java:388)
at
com.precise.shared.util.registry.QuickRegistry.getTree(QuickRegistry.java:131)
at
com.precise.shared.connectionpool.ConnectionManager.initPool(ConnectionManager.java
:699)
at
com.precise.shared.connectionpool.ConnectionManager.createAliasPool(ConnectionManag
er.java:1022)
at
com.precise.shared.connectionpool.ConnectionManager.createPool(ConnectionManager.ja
va:744)
at
com.precise.shared.connectionpool.ConnectionManager.initPool(ConnectionManager.java
:701)
at
com.precise.shared.connectionpool.ConnectionManager.isPoolDefined(ConnectionManager
.java:1037)
at
com.precise.shared.util.sync.DataProvider.JDBCDbAccess.isValid(JDBCDbAccess.java:51
)
at
com.precise.shared.util.sync.DataProvider.DbAccessMgr.isValid(DbAccessMgr.java:27)
at com.precise.shared.util.sync.core.TableSync.runWorker(TableSync.java:83)
at com.precise.shared.util.sync.core.TableSync.run(TableSync.java:66)
at
com.precise.shared.util.sync.core.SyncFileWorker.performTables(SyncFileWorker.java:
88)
at
com.precise.shared.util.sync.core.SyncFileWorker.run(SyncFileWorker.java:49)
at
com.precise.shared.util.taskpools.TaskPoolWorker.performTask(TaskPoolWorker.java:75
)
at
com.precise.shared.util.taskpools.TaskPoolWorker.run(TaskPoolWorker.java:45)
at java.lang.Thread.run(Thread.java:748)

========================================

ID : WARNING-1000014
Time : 2019-12-17 07:00:00.383 GMT-0500
i3 Time : 2019-12-17 12:00:00.383 GMT
Thread : Thread-14 (ID: 1674705143)
Class : com.precise.infra.communication.core.server.MessageHandler
Method : cryptIdCheck
Logger : com.precise.shared.util.communication.rhel7-ora12
Msg : A Communication Server error has occurred from client address:
ideracloud1.siteox.com, client product: unknown, client process:
./infra/bin/psin_infra -ba-status. For more details, see the trace file.
Frame : root cause:
com.precise.shared.util.communication.CommunicationException: Unable to process the
communication message. The communication encryption settings on the 12.202.69.219
server (945331989017) are different than the settings on the rhel7-ora12 server
(945867374757).
To overcome this situation, refer to the security documentation.
at
com.precise.infra.communication.core.server.MessageHandler.cryptIdCheck(MessageHand
ler.java:121)
at
com.precise.infra.communication.core.server.MessageHandler.handle(MessageHandler.ja
va:96)
at
com.precise.infra.communication.core.server.RequestHandler.run(RequestHandler.java:
56)
at
com.precise.shared.util.taskpools.TaskPoolWorker.performTask(TaskPoolWorker.java:75
)
at
com.precise.shared.util.taskpools.TaskPoolWorker.run(TaskPoolWorker.java:45)
at java.lang.Thread.run(Thread.java:748)

========================================

You might also like