New Application Wizard is throwing a errror
I am trying to create new application built on PegaRules, in Pega 7.1.8. Getting following error on the last screen after clicking "Create" button.
|
Error |
I am trying to create new application built on PegaRules, in Pega 7.1.8. Getting following error on the last screen after clicking "Create" button.
|
Error
|
Pegasystems Inc.
AU
Hello Sachin,
I believe there are unrequired prerequisite rulesets are present present in your ruleset stack. Could you please change the Application rulesets validaion mode to 'Ruleset Validation' and verify if there are unrequired prereuisite rulesets are present?
Also verify if you have missed any required hotfixes on any specific frameworks on PRPC instance
Pegasystems Inc.
US
I see this thread in your log - can you share your datasource configuration, normally under context.xml? Also attach your prconfig file if not using OOTB settings. I saw 100 batch threads in the thread dump.
"http-bio- Proprietary information hidden-9900-exec-195" Id=12184 in RUNNABLE (running in native)
BlockedCount : 23, BlockedTime : -1, WaitedCount : 815, WaitedTime : -1
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4838)
- locked com.microsoft.sqlserver.jdbc.TDSReader@50789766
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6154)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet$CursorFetchCommand.doExecute(SQLServerResultSet.java:4919)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1716)
- locked java.lang.Object@1d1bd2d0
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.doServerFetch(SQLServerResultSet.java:4956)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultSet.java:1058)
I see this thread in your log - can you share your datasource configuration, normally under context.xml? Also attach your prconfig file if not using OOTB settings. I saw 100 batch threads in the thread dump.
"http-bio- Proprietary information hidden-9900-exec-195" Id=12184 in RUNNABLE (running in native)
BlockedCount : 23, BlockedTime : -1, WaitedCount : 815, WaitedTime : -1
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(Unknown Source)
at java.net.SocketInputStream.read(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.read(IOBuffer.java:1782)
at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(IOBuffer.java:4838)
- locked com.microsoft.sqlserver.jdbc.TDSReader@50789766
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(IOBuffer.java:6154)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet$CursorFetchCommand.doExecute(SQLServerResultSet.java:4919)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1716)
- locked java.lang.Object@1d1bd2d0
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.doServerFetch(SQLServerResultSet.java:4956)
at com.microsoft.sqlserver.jdbc.SQLServerResultSet.next(SQLServerResultSet.java:1058)
at org.apache.tomcat.dbcp.dbcp.DelegatingResultSet.next(DelegatingResultSet.java:207)
at org.apache.tomcat.dbcp.dbcp.DelegatingResultSet.next(DelegatingResultSet.java:207)
at com.pega.pegarules.data.internal.access.DatabaseResultSet.next(DatabaseResultSet.java:452)
at com.pega.pegarules.data.internal.access.DBLockProviderImpl.expireRequestorLocks(DBLockProviderImpl.java:1332)
at com.pega.pegarules.data.internal.access.LockManagerImpl.expireRequestorLocks(LockManagerImpl.java:2106)
at com.pegarules.generated.activity.ra_action_pyonbeforewindowclose_f8ef50970fde8a8f067584fcd8ea788e.step1_circum0(ra_action_pyonbeforewindowclose_f8ef50970fde8a8f067584fcd8ea788e.java:165)
at com.pegarules.generated.activity.ra_action_pyonbeforewindowclose_f8ef50970fde8a8f067584fcd8ea788e.perform(ra_action_pyonbeforewindowclose_f8ef50970fde8a8f067584fcd8ea788e.java:69)
Cognizant
US
datasource configuration
<Resource maxWait="10000" maxIdle="30" maxActive="100" initialSize="20" password="" username="pegacrdevuser" url="jdbc:sqlserver://DBD_PEGA_CR\PEGA_CR1D; databaseName=PEGA_CR; SelectMethod=cursor;SendStringParametersAsUnicode=false" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" type="javax.sql.DataSource" auth="Container" factory="dbencryption.EncryptedDataSourceFactory" name="jdbc/PegaRULES"/><Environment type="java.lang.String" name="url/initialization/explicittempdir" value="D:/PEGA_TEMP/CLMWS1D"/>
<!-- END AMERIGROUP PEGA TEAM CONFIG SECTION -->
Pegasystems Inc.
IN
Hi Gaddamneeraj,
Thank you for posting your question in the Product Support Community.
Considering the age and current status of conversation in the original thread, it’s best advised that you create a new thread for your question. This is to gather more activity and visibility for the new question on the community.
You may include the original thread as a reference in the newly created thread to receive latest suggestions.
Further, refer the FAQ's for more information- Product Support Community Frequently Asked Questions
Thank you for your cooperation-
Regards,