Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Application not responding after clicking on the "Accept" button

SA-8766

Summary



Application does not respond after clicking on the "Accept" button in NBAA.

Error Messages



fail Unable to synchronize on requestor H0AD087632E5974672EA8C61024C14DD9 within 120 seconds: (thisThread = http-bio-8443-exec-37) (originally locked by = http-bio-8443-exec-36) (finally locked by = http-bio-8443-exec-36) Unauthenticated or not available No ID available PegaRULES 7.10 ML7 (coreAssemblyCached_717_644)

Steps to Reproduce



1. Launch the NBAA Portal.
2.Start >Customer NBA Interaction.
3.Select a reason and the Customer Treatment link enabled.
4.From the Customer Treatment screen, click on Accept button.
Progress icon displays for more than 10 minutes and the next screen never gets displayed.

Root Cause



The hung threads indicates that HTTP request is failing while setting the response to Adaptive Decision Manager (ADM).

"http-bio-8443-exec-8" Id=304 in RUNNABLE (running in native)
BlockedCount : 2, BlockedTime : -1, WaitedCount : 2, WaitedTime : -1
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
- locked java.io.BufferedInputStream@12e50a1d

at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:698)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:641)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1218)
- locked sun.net.www.protocol.http.HttpURLConnection@74a35830

at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:379)
at org.springframework.remoting.httpinvoker.SimpleHttpInvokerRequestExecutor.validateResponse(SimpleHttpInvokerRequestExecutor.java:138)
at org.springframework.remoting.httpinvoker.SimpleHttpInvokerRequestExecutor.doExecuteRequest(SimpleHttpInvokerRequestExecutor.java:62)
at org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:134)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:191)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:173)
at org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:141)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy79.insertFactRecords(Unknown Source)
at com.pegarules.generated.pxInsertRecordsFromPages_071011_nNFU5kwAtj9QKN1Qvhl_Nw.pxInsertRecordsFromPages07_10_11(pxInsertRecordsFromPages_071011_nNFU5kwAtj9QKN1Qvhl_Nw.java:199)
at com.pegarules.generated.pxInsertRecordsFromPages_071011_nNFU5kwAtj9QKN1Qvhl_Nw.invoke(pxInsertRecordsFromPages_071011_nNFU5kwAtj9QKN1Qvhl_Nw.java:91)


To trace the actual error, modified the actions on the Accept button by removing the 'finishassignment' and running the Flow again. The setResponse call to ADM was failing due to missing Jar file (geronimo-jta_1.1_spec-1.1.1.jar) in the classpath.

Resolution



Issue is resolved by adding the missing jar file (geronimo-jta_1.1_spec-1.1.1.jar) to Tomcat lib directory as per the DSM installation document.

Published May 5, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us