Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Saurabh Kumar (SaurabhK6899) Capgemini
Capgemini
IN
SaurabhK6899 Member since 2016 3 posts
Capgemini
Posted: Dec 14, 2016
Last activity: Jan 20, 2017
Posted: 14 Dec 2016 9:18 EST
Last activity: 20 Jan 2017 3:26 EST
Closed
Solved

Error on running a Report Definition "Failed to create Java VM | SQL Code:0 | SQL State XX000"

Hi,

I am getting an error whem I am running the Report Definition. The data is fetched sometime while most of the time it shows the following Error. 

** An error occured on executing the query for the report definition - There was a problem getting a list: code:0 SQLState: XX000 Message: ERROR: Failed to create Java VM DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR:  Failed to create Java VM | SQL Code:0 | SQL State XX000"

Reporting
Posted: 6 years ago
Posted: 14 Dec 2016 12:57 EST
John Pritchard-Williams (JOHNPW_GCS) Client Support Team Lead
Pegasystems Inc.
GB

My guess here:

1. You haven't configured Postgresql to run Java Programs

and/or

2. You haven't imported the 'User Defined Functions' (AKA 'UDFs') into your PRPC system.

The UDFs are used to retrieve PRPC Properties directly from BLOB columns in the database - and they are implemented in Java (or .NET for SQLServer) - the database itself has to be configured to run Java: the installation guide for Postgresql-based PRPC has a section for doing this.

So for example:for PRPC721: see  - https://docs-previous.pega.com/pega-721-platform-installation-guide-apache-tomcat-and-postgresql - and see the section entitled "Creating secondary schema for Java user-defined functions" (Page 20/53 or Page 20 - depending on which page numbering schema you look at)

A confession: I haven't done this installation (PRPC against Postgresql) yet - but I have seen similar issues with other DBs (Oracle and SQLServer).

If you can get up a SQL command prompt ('pgAdmin' / 'psql') you can try running the UDFs directly from there to see if they are available or not.

The names of the UDFs are listed on Page 53/53 (the last page) as:

pr_read_from_stream
pr_read_decimal_from_stream
pr_read_int_from_stream

 

Hope this gets you started on this; if not or you have questions please ping back here !

 

 

Accepted Solution

Posted: 6 years ago
Posted: 5 Jan 2017 3:49 EST
Alex Pandourangam (apandour) Capgemini Application Officer
Capgemini
FR

Hi,

I had the same issue but it works most of the times and it appears during a period (5 times from 7:26am to 7:30am today). Here is the error message:

2017-01-05 07:26:45,067 [          httpexec-8] [OpenPortal] [                    ] [   DenguePH:01.01.01] ( rd.queryexec.SqlQueryExecutor) ERROR - An error occured on executing the query for the report definition - There was a problem getting a list: code: 0 SQLState: XX000 Message: ERROR: Failed to create Java VM
DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: Failed to create Java VM | SQL Code: 0 | SQL State: XX000

com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 0 SQLState: XX000 Message: ERROR: Failed to create Java VM

DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: Failed to create Java VM | SQL Code: 0 | SQL State: XX000

I don't think it's an error on postgresql configuration because it works most of the time.

When I tried java -version during this issue on the database server, I've got an error:

java -version

Error occurred during initialization of VM

Could not reserve enough space for object heap

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

Or, only 16% of VM memory is used on the server (we've got 8GB).

Show More

Hi,

I had the same issue but it works most of the times and it appears during a period (5 times from 7:26am to 7:30am today). Here is the error message:

2017-01-05 07:26:45,067 [          httpexec-8] [OpenPortal] [                    ] [   DenguePH:01.01.01] ( rd.queryexec.SqlQueryExecutor) ERROR - An error occured on executing the query for the report definition - There was a problem getting a list: code: 0 SQLState: XX000 Message: ERROR: Failed to create Java VM
DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: Failed to create Java VM | SQL Code: 0 | SQL State: XX000

com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 0 SQLState: XX000 Message: ERROR: Failed to create Java VM

DatabaseException caused by prior exception: org.postgresql.util.PSQLException: ERROR: Failed to create Java VM | SQL Code: 0 | SQL State: XX000

I don't think it's an error on postgresql configuration because it works most of the time.

When I tried java -version during this issue on the database server, I've got an error:

java -version

Error occurred during initialization of VM

Could not reserve enough space for object heap

Error: Could not create the Java Virtual Machine.

Error: A fatal exception has occurred. Program will exit.

Or, only 16% of VM memory is used on the server (we've got 8GB).

When I stopped Pega instance, I can execute java -version on the database server and I can also allocate 3 GB:

java -Xms3G -Xmx3G -version

java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)

After restart, java -Xms3G -Xmx3G -version will still work until we're trying to generate reports.

Does anybody had this issue? Thanks

 

 


Show Less
Posted: 6 years ago
Posted: 5 Jan 2017 5:22 EST
John Pritchard-Williams (JOHNPW_GCS) Client Support Team Lead
Pegasystems Inc.
GB

When you say:

I don't think it's an error on postgresql configuration because it works most of the time.

Do you mean that reports work most of the time ? If so: please double check that the same report works sometimes and not others ; if you find instead that some reports work and some others don't - then check the reports that do not run - do they contain any properties which are not exposed (do not have corresponding DB columns in the underlying table).

The reason for the test above: if properties are all exposed - the in-database JVM calls will not be used (they don't need to be) - but if you have a non-exposed property (that is: the property-value exists only in the BLOB) - the system will automatically select a 'pr_read*' function to parse the BLOB; and these 'pr_read*' are the only time (that I'm aware of) that make us of the in-database JVM.

Disclaimer: I haven't much experience of postgresql, so I'm not quite sure how it calls Java (or other 'host' Languages) - for Oracle ; there is a *separate* JVM that is used - different from the JVM that the App Server/PRPC uses.....

 
Posted: 6 years ago
Posted: 5 Jan 2017 15:04 EST
Alex Pandourangam (apandour) Capgemini Application Officer
Capgemini
FR

Hi PRITJ,

Thanks for your answer.

It's not always the same report that works. All are working but sometimes, they don't.

I've done some test (in attachment). It seems that postgres process used a lot of VIRT memory. Maybe it can explain our issue. Do we need to increase VM memory on database server from 8 GB to 16 GB or is it anormal behaviour ? Thanks

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice