Hi. We have a large app with several modules. On ocassion our app presents an error stating "The system is experiencing technical difficulties". On VP this shows as a PAVB_00213. These are consistent with something stuck on the WAS.

We would expect this to be the case when the system is running some of our code, however it seems that the server is stuck in FormatLocal.MASSpeakNumber, which we don't change. Note that this only happens in some cases. That is, something on the data seems to trigger this behavior, but we have not been able to pinpoint what.

####<Nov 19, 2012 5:59:31 AM COT> <Error> <WebLogicServer> <server.example.net> <voiceportal> <[ACTIVE] ExecuteThread: '110' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1353322771931> <BEA-000337> <[STUCK] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "659" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@137adc61[
GET /PagoServicios/IVCPProcess-PaymentValue?___DDSESSIONID=v2vMQqTByNYB1hS264W2BQGw1hq7PRvfy7jvCnvJrwh2SvTJP2dr%21706077840%211353321985808%3A%2FServilinea HTTP/1.1
Accept: */*
User-Agent: AvayaVXI/2.0
AVB-Version: 2.1.4
Referer: https://10.84.254.17:7002/PagoServicios/IVCPProcess-SetVar
Cache-Control: max-age=3600
Cache-Control: max-stale=0
Cookie: $Version=1; JSESSIONID=v2vMQqTByNYB1hS264W2BQGw1hq7PRvfy7jvCnvJrwh2SvTJP2dr!706077840; $Path=/; $Domain=10.84.254.17
Cookie: $Version=1; ___DDSESSIONID=v2vMQqTByNYB1hS264W2BQGw1hq7PRvfy7jvCnvJrwh2SvTJP2dr!706077840!1353321985808:/Servilinea; $Path=/; $Domain=10.84.254.17

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-36 "[STUCK] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, suspended, priority=1, DAEMON> {
locale.es_la.FormatLocale.MasSpeakNumber(FormatLocale.java:1302)
locale.es_la.FormatLocale.MasSpeakNumber(FormatLocale.java:1302)
locale.es_la.FormatLocale.currencyFormat1(FormatLocale.java:1603)
locale.es_la.FormatLocale.getCurrencyFormat(FormatLocale.java:1436)
locale.es_la.FormatLocale.toCurrency(FormatLocale.java:780)
locale.es_la.FormatLocale.formatTextToAudio(FormatLocale.java:426)
com.avaya.sce.runtime.PromptElement.getFormattedVariableAudio(PromptElement.java:354)
com.avaya.sce.runtime.vxml.OutputGenerator.promptMiddle(OutputGenerator.java:819)
com.avaya.sce.runtime.Prompt.generate(Prompt.java:222)
com.avaya.sce.runtime.Form.handleRequest(Form.java:158)
com.avaya.sce.runtime.AppDocument.processRequest(AppDocument.java:158)
com.avaya.sce.runtime.SCEServlet.requestHandler(SCEServlet.java:191)
com.avaya.sce.runtime.SCEServlet.doGet(SCEServlet.java:176)
javax.servlet.http.HttpServlet.service(HttpServlet.java:700)

]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:

This sounds like you running out of thread. There is no reason the thread gets stuck at this particular spot otherwise. You may need to contact Weblogic support to get some explanation of the problem.

We have checked and the system is outputing this upon receiving "000000070460.00 ". The system is not running out of threads, but will eventually do so (each call makes one thread unusable). WebLogic tells us to go to Avaya. Is it possible to at least know what is being done on FormatLocale.java:1302? We have looked for this file, but we cannot find the source.

This is the line, and it doesn't make sense it is stuck:

if (number < 0){

You do have the code. Open the es-la<version>.jar in winzip and you will find the es-la.jar file inside. Open it in winzip also. The FormatLocale.java file is in inside.

Weblogic support needs to tell you why the thread is stuck there.

After a lot of pain we finally discovered that this was due to a problem when the WAS resolved a name. That is, the WAS had a misconfigured /etc/hosts file and when it looked up the name it got stuck. We fixed the /etc/hosts and the problem went away.