search cancel

Problem with long time-outs on freshly installed servers on RHEL 8 (obsolete hibernate namespace?)

book

Article ID: 253768

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

I'm doing some test installations of 10.8 on RHEL 8 in preparation for migration from 10.7 SP3 to 10.8.

I have installed a MOM and two collectors in a test-environment. There are no metrics or agents involved at this time. The systems are completely empty.

The issue is that it takes a very long time for the collectors to connect to the MOM when I start them. 
It also takes a long time for MOM to allow for connecting via workstation-gui.

There are no Errors in the log files but there are warnings related to hibernate. I have the same warn-message in the logs on the MOM-server.

[WARN] [main] [org.hibernate.orm.deprecation] HHH90000012: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/hibernate-configuration. Use names
pace http://www.hibernate.org/dtd/hibernate-configuration instead.  Support for obsolete DTD/XSD namespaces may be removed at any time.

It looks like it hangs for 10+ minutes and then proceeds.

I'm supplying em.log from one collector and mom. Don't mind the "Connection refused" at the end of the mom-logs. I shut the collectors down. 

The issue is the gap in time that occurs in the following place in the mom-logs:
[INFO] [main] [org.hibernate.annotations.common.Version] HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
[INFO] [main] [org.hibernate.dialect.Dialect] HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL95Dialect

And here in the collector-log:
[INFO] [main] [org.hibernate.annotations.common.Version] HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
[INFO] [main] [org.hibernate.dialect.Dialect] HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL95Dialect

What is this hibernate-function? Can I supply some parameter to get around this time-out behavior? 



Environment

Release : 10.8

Resolution

Applied new jar fix.  This fixed the issue.

The release is tentatively planned for December/January time frame.  Please note that this is not firm and that the time frame is subject to change.