Tools Release 8.98.4.2 HTML Logging Issues

Has anyone else noticed that there HTML instances produce a lot of logs since they have upgraded to 8.98.4.2?

I have two clients now that are on 8.98.4.2 and the HTML instances produce logs full of the same types of errors but the users are not reporting any issues. And they were not experiencing the html logging issues on 8.98.4.1.

The errors are always problems with the server while running a business function, for example:

28 Apr 2011 10:52:02,294 [SEVERE] USER1 - [RUNTIME] An exception has been caught by the Web client. Please contact your system administrator. See log for details. Exception id =Exception_2011-04-28 10:52:02.294_USER1 There was a problem with the sever while running the business function MemoryFreeFixedAssetRetrieval.\nPlease exit the application and restart it.\nEnd Dialog Line number 2\nP122101_W122101A com.jdedwards.runtime.base.SystemException: There was a problem with the sever while running the business function MemoryFreeFixedAssetRetrieval.\nPlease exit the application and restart it.\nEnd Dialog Line number 2\nP122101_W122101A

Jeremy, this is not a web problem, probably that's an enteprise problem (where bf are executed) or timeout comunication beetween web and enterprise server.
Did you analyze enterprise server logs?
Regards
gg

Jeremy,

I have two clients testing 898.4.2 and we are not experiencing this issue. What is your enterprise server type? (If its ISeries you may want to run the LINKBSFN on all your pathcodes) You may want to try building a full package to see if it corrects the issues with running BSFN's!

Regards
Bob

My Enterprise server type is Windows 2008 R2. I do have a couple of logs on the Enterprise server that have this error, but other than that they look clean. Also, I have built several clean full packages since the TR upgrade.

2288/1312 SYSispatch Mon May 02 12:54:06.551000 JDEKDISP.C2049
KNT0000099 - JDEK_DispatchCallObjectMessage: Pooled Connection: 01CEA010 timed out!

2248/3888 SYSispatch Mon May 02 13:19:16.496000 JDEKDISP.C2049
KNT0000099 - JDEK_DispatchCallObjectMessage: Pooled Connection: 01C4A008 timed out!

3536/3972 SYSispatch Mon May 02 13:26:19.524000 JDEKDISP.C2049
KNT0000099 - JDEK_DispatchCallObjectMessage: Pooled Connection: 01C4A008 timed out!

3296/3800 SYSispatch Mon May 02 13:39:10.043000 JDEKDISP.C2049
KNT0000099 - JDEK_DispatchCallObjectMessage: Pooled Connection: 01CB3518 timed out!

Hi,
I have 1 customer on TR8.98.4.1 and one on 8.98.4.2 and have exactly the same issue. Both customers are on Oracle Linux enterprise server. No users are reporting issues but the logs are filling up.
Mathieu M
FRANCE

Well, at least its not just me. I did do a lot of performance tuning last week for one of my clients with the issue. I'll find out this week if it made any difference.

I am getting the exact issiue with a client as well. JAS.log shows the business funtion error as well as:

10 May 2011 11:50:15,108 [SEVERE] - [JPD812_6014_90_M1][RUNTIME] RID not found in request

Although the logs have a lot of errors like the ones in the posts above, every once in a while a user does experince "processing" for about 3 - 4 minutes while the COK times out.

I also noticed that this error happens in almost all of the COK.

in the COK:
12709/29 SYSispatch Tue May 10 11:28:34.834528 jdekdisp.c2049
KNT0000099 - JDEK_DispatchCallObjectMessage: Pooled Connection: SPP:0000 :0000 :0:0:11 timed out!

JDENET kernels have this message written in it:

12696/1025MAIN_THREAD Tue May 10 11:22:44.213496netrcv.c407
3426-Error from Host=<10.48.2.4> in recv returned A connection with a remote socket was reset by that socket.



IBM AS400 V6R1
WAS 7.0.0.11 on Intel Win 2008
TR 8.98.4.2

The performance tuning that I did, did seem to resolve the issue. However I made a lot of changes to both the Enterprise server, Web server, and modified the inactive timeout settings on WLS, HTTP server, and E1.

Has anyone who has the issue found a way to reproduce it on will? I will make the performance tuning changes one at a time on my other client and see if I can track down the exact change that resolves the issue.

I do recall also some users experiencing the processing issue.

I having a very similar problem. We have Windows 2008 R2, running Websphere 7.0.0.11, with E1 on a AS400 V6R1, software 8.12. So very similar enviroment to the original post. I plan on sending this off to Oracle Technical support, but I thought I would ask if a solution was ever found here?

Did you ever fix this?

I seem to have a very similar environment and the same problem.

Thanks, Gerd