- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: System Event Analyzer Java Exception
Operating System - OpenVMS
1748156
Members
3745
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2009 08:03 AM
тАО07-08-2009 08:03 AM
System Event Analyzer Java Exception
Hello,
I am having trouble with System Event Analyzer when connected to the GUI of an Itanium running OpenVMS 8.3-1h1. (https://hostname:7906). See below:
Exception during processing
org.hibernate.exception.JDBCConnectionException: Cannot open connection org.hibernate.exception.JDBCConnectionException: Cannot open connection at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144) at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119) at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57) at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326) at com.hp.svctools.managedentities.ManagedEntityFactory.getEntityList(ManagedEntityFactory.java:1898) at com.hp.svctools.managedentities.ManagedEntityFactory.entities(ManagedEntityFactory.java:1878) at com.compaq.svctools.desta.services.managedentities.DestaManagedEntityFactory.entities(DestaManagedEntityFactory.java:1417) at com.compaq.svctools.desta.services.managedentities.DestaManagedEntityFactory.infoNeeded(DestaManagedEntityFactory.java:1442) at com.compaq.svctools.ca.services.web.providers.AboutProvider.processHttp(AboutProvider.java:42) at HttpServer.HttpProcessThread.handleGet(HttpProcessThread.java:504) at HttpServer.HttpProcessThread.handleRequestByMethod(HttpProcessThread.java:775) at HttpServer.HttpProcessThread.run(HttpProcessThread.java:226) Caused by: java.sql.SQLException: socket creation error at org.hsqldb.jdbc.Util.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.(Unknown Source) at org.hsqldb.jdbcDriver.getConnection(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) at java.sql.DriverManager.getConnection(DriverManager.java:140) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423) ... 12 more
After the message appears, it is only cleared by restarting the DESTA director on the Itanium.
thx,
phil
I am having trouble with System Event Analyzer when connected to the GUI of an Itanium running OpenVMS 8.3-1h1. (https://hostname:7906). See below:
Exception during processing
org.hibernate.exception.JDBCConnectionException: Cannot open connection org.hibernate.exception.JDBCConnectionException: Cannot open connection at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:74) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426) at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144) at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:119) at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:57) at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1326) at com.hp.svctools.managedentities.ManagedEntityFactory.getEntityList(ManagedEntityFactory.java:1898) at com.hp.svctools.managedentities.ManagedEntityFactory.entities(ManagedEntityFactory.java:1878) at com.compaq.svctools.desta.services.managedentities.DestaManagedEntityFactory.entities(DestaManagedEntityFactory.java:1417) at com.compaq.svctools.desta.services.managedentities.DestaManagedEntityFactory.infoNeeded(DestaManagedEntityFactory.java:1442) at com.compaq.svctools.ca.services.web.providers.AboutProvider.processHttp(AboutProvider.java:42) at HttpServer.HttpProcessThread.handleGet(HttpProcessThread.java:504) at HttpServer.HttpProcessThread.handleRequestByMethod(HttpProcessThread.java:775) at HttpServer.HttpProcessThread.run(HttpProcessThread.java:226) Caused by: java.sql.SQLException: socket creation error at org.hsqldb.jdbc.Util.sqlException(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.(Unknown Source) at org.hsqldb.jdbcDriver.getConnection(Unknown Source) at org.hsqldb.jdbcDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:525) at java.sql.DriverManager.getConnection(DriverManager.java:140) at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110) at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423) ... 12 more
After the message appears, it is only cleared by restarting the DESTA director on the Itanium.
thx,
phil
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2009 08:22 AM
тАО07-08-2009 08:22 AM
Re: System Event Analyzer Java Exception
Reposting this; ITRC glitched again.
Problems with the HP service tools (like problems with ITRC) are unfortunately somewhat more common than any of us might want or like, though I've not seen this particular footprint before.
If you've loaded the expected Java version with the current ECO kits (and various of the HP tools around do expect specific Java versions, and Java versions that are too old or too new can cause the tools to tip over), then contact HP support directly.
There are forums for HP SIM and for the service tools, as well.
Here's the top-level ITRC forum family for the services tools and related stuff:
http://forums11.itrc.hp.com/service/forums/familyhome.do?familyId=121
If (when?) you repost over there, please do indicate if you're running all the pieces on OpenVMS or if there's another host involved here for part of this. And the Java and patches installed, too.
Problems with the HP service tools (like problems with ITRC) are unfortunately somewhat more common than any of us might want or like, though I've not seen this particular footprint before.
If you've loaded the expected Java version with the current ECO kits (and various of the HP tools around do expect specific Java versions, and Java versions that are too old or too new can cause the tools to tip over), then contact HP support directly.
There are forums for HP SIM and for the service tools, as well.
Here's the top-level ITRC forum family for the services tools and related stuff:
http://forums11.itrc.hp.com/service/forums/familyhome.do?familyId=121
If (when?) you repost over there, please do indicate if you're running all the pieces on OpenVMS or if there's another host involved here for part of this. And the Java and patches installed, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2009 05:32 AM
тАО08-25-2009 05:32 AM
Re: System Event Analyzer Java Exception
Well after nearly two months, HP has come to conclusion that running SEA on an OpenVMS box is not supported. They suggest we dump SEA in favor of RSP. OBTW, they just found an error message in the DESTA_DIR.LOG file for the machine in question:
Ma> Exception java.lang.OutOfMemoryError: requested 655360 bytes for
Ma> PSYoungGen::resize_helper Possible causes:
Ma> - process Page File Quota (PGFLQUOTA) is too small,
Ma> - per-thread stack size (default = -Xss128k) is too large for the number of threads created,
Ma> - large Java heap size conflicts with other application memory requirements, or
Ma> - system page file is too small.
Does this error message look familiar to anyone?
Ma> Exception java.lang.OutOfMemoryError: requested 655360 bytes for
Ma> PSYoungGen::resize_helper Possible causes:
Ma> - process Page File Quota (PGFLQUOTA) is too small,
Ma> - per-thread stack size (default = -Xss128k) is too large for the number of threads created,
Ma> - large Java heap size conflicts with other application memory requirements, or
Ma> - system page file is too small.
Does this error message look familiar to anyone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2009 06:00 AM
тАО08-25-2009 06:00 AM
Re: System Event Analyzer Java Exception
The first ITRC posting failed; attempting a repost.
Based solely on what is posted here, it appears that this particular Java tool blew out the available P0 process address space. (HP SEA runs have been seen to consume a sizable chunk of an AlphaServer GS1280 box analyzing an error log file; it's not lightweight software.)
On recent boxes (and that haven't had VIRTUALPAGCNT adjusted downward from what AUTOGEN usually sets it to) the available process address space is determined by the PGFLQUOTA and the available pagefile. If your PGFLQUOTA and your available system pagefile storage have enough room for a gigantic Java application, then you're left to do what HP says.
HP has likely investigated this sequence and these system resources as part of deciding that HP SEA is now unsupported. (The next step of the retirement would change the posted product status over at the HP SEA web page; that would be the next step for HP here as part of this retirement.)
If HP SEA is now unsupported, you're going to be migrating your monitoring and error analysis over to a Microsoft Windows box and to the HP Remote Support Pack (RSP) pieces. Given the bug and the bug response and given the use of HP products here and given the support contract, consider asking the HP services folks to provide the migration over to HP RSP.
Based solely on what is posted here, it appears that this particular Java tool blew out the available P0 process address space. (HP SEA runs have been seen to consume a sizable chunk of an AlphaServer GS1280 box analyzing an error log file; it's not lightweight software.)
On recent boxes (and that haven't had VIRTUALPAGCNT adjusted downward from what AUTOGEN usually sets it to) the available process address space is determined by the PGFLQUOTA and the available pagefile. If your PGFLQUOTA and your available system pagefile storage have enough room for a gigantic Java application, then you're left to do what HP says.
HP has likely investigated this sequence and these system resources as part of deciding that HP SEA is now unsupported. (The next step of the retirement would change the posted product status over at the HP SEA web page; that would be the next step for HP here as part of this retirement.)
If HP SEA is now unsupported, you're going to be migrating your monitoring and error analysis over to a Microsoft Windows box and to the HP Remote Support Pack (RSP) pieces. Given the bug and the bug response and given the use of HP products here and given the support contract, consider asking the HP services folks to provide the migration over to HP RSP.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP