P03B102 Commit Failed Errors

Hey everyone.

Got an iSeries running V5R3 with JDE Xe 7334, SP23_M1.

On Sunday, we applied changes to our JDE.ini to turn on XML:

[Previous DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=JDEKRNL
dispatchDLLFunction=JDEK_DispatchCallObjectMessage
maxNumberOfProcesses=75
numberOfAutoStartProcesses=0

[NEW DEF6]
[JDENET_KERNEL_DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=XMLCALLOBJ
dispatchDLLFunction=XMLCallObjectDispatch
maxNumberOfProcesses=1
numberOfAutoStartProcesses=1

Now, we are getting strange timeout and commit errors when using the P03B102... Here's a small sample of the errors from the CALL OBJECT KERNEL log:

----
26423 Thu Sep 21 16:45:26 2006 jdb_utl1.c9377
JDB3900000 - Elasped time on a manual commit transaction for <USER> exceeded 10 seconds, freeing that transaction.

26423 Thu Sep 21 16:45:26 2006 jdb_exet.c6097
JDB9900849 - Failed to commit user

26423 Thu Sep 21 16:45:26 2006 jdeknobj.c147
KNT0000191 - CommitUser failed, userh=SPP:0000 :1aefJDENET_K ONEWORLD 449263 :89550:2:11, client=10.x.x.x, pid=5476, mId=47753
----

And from the JDE.log:

7352/8896 Thu Sep 21 11:47:56 2006 jdb_exet.c5759
KNT0500010 - CommitRemoteUser <EnterpriseServer> Failed.

7352/8896 Thu Sep 21 11:47:56 2006 jdb_exet.c6130
JDB9900390 - Failed to commit remote user on server <EnterpriseServer>, rollback all users on remaining remote servers.

7352/8896 Thu Sep 21 11:47:56 2006 jdb_exet.c6146
JDB9900391 - Failed to commit user

7352/8896 Thu Sep 21 11:47:56 2006 DLG_MSGB.CPP190
Commit Failed or was Canceled. Transaction not committed.
----
Note: The time signatures don't match, but that's not important - we had the problem at multiple times.

So, what I'm trying to figure out is if the change to the JDE.ini caused this problem or if there is something else going on.

HELP!?!

In your original INI, you have this line:

maxNumberOfProcesses=75

In your updated version you have this?

maxNumberOfProcesses=1

Make sure you change that to = 75. When I changed to an XML call object kernel, i forgot to change that setting back and our server ground to a halt because there were a hundred users trying to use one Kernel.

As far as the actual error, changing to an XML kernel should not effect JDE transactions so hopefully changing the maxNumberProcesses will solve your problem.

DEA - thanks for your suggestion...while neither Oracle or any other document seemed to support this--we did it anyway...

And guess what? It worked.

We put the XML stuff back in, and ONLY changed the maxNumberOfProcesses to a higher number (75); and our problems/errors went away.

Thanks for the help.