Any Suggestion for exception 3048

[ConvertFromOldNGs]

by Didier >> Tue, 23 Jan 2007 2:28:04 GMT

hi
I encounter an issue:
jade.exe, jadapp.exe application automatically termate in Linux RHES3 Server.
Terminated 3 times in 4 hours

Check in the jommsg.log, found that it caused by exception 3048.

Reboot Linux Server, and run jade.exe, jadapp.exe ,it will be OK for a long time.

Anybody has any suggestion for exception 3048.

Appricated for any help.

Didier
2007.1.23

/////////////////////////////////////////////////////////////////////////////////////// // partial content of jommsg.log /////////////////////////////////////////////////////////////////////////////////////// 2007/01/22 11:16:03 01d39-41246bb0 PDB: Journal /home/jade/system/journals/current/db0000007739.log deleted
2007/01/22 11:16:34 01d39-42977bb0 Jom: Remote process delete 0x90ff878: no=0, id=0, type=2, scm=BizAcct, app=FirstJump
2007/01/22 11:16:34 01d4b-41279bb0 Jom: Local process delete 0x9197e30: no=6, id=1105480624, type=2, scm=BizAcct, app=FirstJump
2007/01/22 11:16:34 01d4b-41e44bb0 JadApp: Thin Client disconnected and signed off: DAVID (10.65.1.137) schema=BizAcct app=FirstJump Compression ratio=46.1%.
2007/01/22 11:16:51 01d39-41246bb0 PDB: [size] switched to journal: /home/jade/system/journals/current/db0000007741.log
2007/01/22 11:17:01 01d39-41246bb0 PDB: Journal /home/jade/system/journals/current/db0000007740.log deleted
2007/01/22 11:17:40 01d39-41246bb0 PDB: [size] switched to journal: /home/jade/system/journals/current/db0000007742.log
2007/01/22 11:17:44 01d39-42876bb0 PDB: Client Node edition invalid for oid=[2244.8143:1543], database edition=1543, client edition=1544, state=committed(prior edition)
2007/01/22 11:17:44 01d39-42876bb0 PDB: <user8> encountered database error (3048)
2007/01/22 11:17:44 01d4b-4236ebb0 Jom: DB_EDITION_INVALID from db, oid=[2244.8143:1544], flag=1
2007/01/22 11:17:45 01d4b-4236ebb0 Jom: get object DB_EDITION_INVALID, process agent=0x83c5b78, pBuffer=0x43206e98, getLock=0, previousEdition=1544 2007/01/22 11:17:45 01d4b-4236ebb0 Jom: node: [186.2] name: E8-BRM2 2007/01/22 11:17:45 01d4b-4236ebb0 Jom: Persistent Cache Buffers 2007/01/22 11:17:45 01d4b-4236ebb0 Jom: cache type= Persistent, maxBuffersSize=5000000, maxOverdraftBuffersSize=2500000, readStartCount=751584, readStopCount=751583, writeStartCount=4528, writeStopCount=4528
2007/01/22 11:17:45 01d4b-4236ebb0 Jom: Buffer=0x9927fa0, status=0, nailCount=1, ioCount=1, pOwner=0x0, lastReadStop=0, flags=0, birth=8659696, ops=0
2007/01/22 11:17:45 01d4b-4236ebb0 Jom: oid=[0.1194.3912.2.1:1], fileNo=64, fAddr=542459966, flag=1, repInfo=0
2007/01/22 11:17:45 01d4b-4236ebb0 Jom: receiver class name= GLBatchCtrl 2007/01/22 11:17:45 01d4b-4236ebb0 Jom: Buffer=0x9430eb8, status=0, nailCount=1, ioCount=0, pOwner=0x0, lastReadStop=750583, flags=0, birth=8578918, ops=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: oid=[3912.1194:2], fileNo=64, fAddr=145024319, flag=1, repInfo=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: receiver class name= GLBatchCtrl 2007/01/22 11:17:46 01d4b-4236ebb0 Jom: Buffer=0x8726988, status=0, nailCount=0, ioCount=0, pOwner=0x0, lastReadStop=747391, flags=0, birth=8351275, ops=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: oid=[2114.500:26], fileNo=64, fAddr=26817, flag=1, repInfo=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: receiver class name= AcctPeriod 2007/01/22 11:17:46 01d4b-4236ebb0 Jom: Buffer=0x8bf4e88, status=0, nailCount=0, ioCount=0, pOwner=0x0, lastReadStop=751289, flags=0, birth=8590867, ops=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: oid=[3939.2414:323], fileNo=64, fAddr=153118186, flag=1, repInfo=0
2007/01/22 11:17:46 01d4b-4236ebb0 Jom: receiver class name= DocType 2007/01/22 11:17:46 01d4b-4236ebb0 Jom: Buffer=0x9430fd0, status=0, nailCount=0, ioCount=0, pOwner=0x0, lastReadStop=750582, flags=0, birth=8578909, ops=0
2007/01/22 11:17:47 01d4b-4236ebb0 Jom: oid=[3912.1193:2], fileNo=64, fAddr=145024121, flag=1, repInfo=0
2007/01/22 11:17:47 01d4b-4236ebb0 Jom: receiver class name= GLBatchCtrl

[ConvertFromOldNGs]

by Brendan >> Tue, 23 Jan 2007 8:22:16 GMT

Hi Didier,
It would be useful to know the version of JADE and any hotfixes you're running. Also which OS? Is it bona fide RHEL or one of the free lookalikes like CentOS? I suspect the issue would be with Jade since CentOS, for example, is binary compatible with RHEL.

The problem line from the jommsg log is
2007/01/22 11:17:44 01d39-42876bb0 PDB: Client Node edition invalid for oid=[2244.8143:1543], database edition=1543, client edition=1544, state=committed(prior edition)
2007/01/22 11:17:44 01d39-42876bb0 PDB: <user8> encountered database error (3048)

The *committed* client edition of oid 2244.8143 is 1 ahead of the server edition which should "never happen".

It's shortly after a journal switch but this is probably irrelevant.

There have been timing holes in 6.0 (JADE problem - fixed) when updating slobs and blobs which produced this exception and subsequent crash. Can you track down the JADE code causing the problem? Is it possible to produce a CardSchema exception dump when a fatal exception occurs?

I would suggest the following in turn:

1. Check that the ini options for cache coherency are enabled and consistent on the dbserver, each appserver and any fat clients. See if any messages re cache coherency are written to the jommsg log on startup.

2. If all OK and the problem persists, upgrade to the latest consolidated release.

3. If it still persists, you'll have to report the issue to the plant. However, if you're not running bona fide RHEL they reserve the right not to look too deeply into it which could be a problem for you getting a fix. However, my guess would be that it's a JADE not an OS issue.

One other thought. What is the usage pattern of your users? Would the app run just as well in singleuser appserver? I run on CentOS this way so would never see this problem.

Cheers, Brendan

[ConvertFromOldNGs]

by Didier >> Wed, 24 Jan 2007 7:01:35 GMT

Hi
The following is jverinfo.
for your reference.
Didier
2007.1.24
============================================================================ * System Information * ============================================================================ Host Name: E8-BRM
O/S Version: Linux 2.4.21 #1 Thu Feb 2 22:20:41 EST 2006
Red Hat Enterprise Linux ES release 3 (Taroon Update 7)
============================================================================ * File Version Information * ============================================================================

Executables: (path = /home/jade/bin/)
============
jadappb 6.0.21.002 Thu Jan 20 23:33:14 2005
jadclient 6.0.21.002 Thu Jan 20 23:49:07 2005
jaded 6.0.21.002 Thu Jan 20 23:33:49 2005
jadloadb 6.0.21.002 Thu Jan 20 23:34:53 2005
jadregb 6.0.21.002 Thu Jan 20 23:35:07 2005
jdbutilb 6.0.21.002 Thu Jan 20 23:35:37 2005
jddlutlb 6.0.21.002 Thu Jan 20 23:36:11 2005
jverinfo 6.0.21.002 Thu Jan 20 23:36:20 2005
jaded.sh -.-.--.--- Sat Jun 10 21:09:52 2006
jadappb.sh -.-.--.--- Sat Jun 10 21:09:52 2006 jadclient.sh -.-.--.--- Sat Jun 10 21:09:52 2006
jadloadb.sh -.-.--.--- Sat Jun 10 21:09:52 2006
jdbutilb.sh -.-.--.--- Sat Jun 10 21:09:52 2006
jadregb.sh -.-.--.--- Sat Jun 10 21:09:52 2006 FreeImage.dll -.-.--.--- Thu Aug 19 06:25:14 2004 jaddinst.exe 6.0.21.002 Thu Jan 20 08:30:09 2005 jadeactivexthin.dll 6.0.21.002 Thu Jan 20 08:30:13 2005
jadedit.dll 6.0.21.002 Thu Jan 20 08:30:13 2005
jade.exe 6.0.21.002 Thu Jan 20 08:30:10 2005
jadmsgs.eng -.-.--.--- Tue Dec 21 06:33:52 2004
jadprnt.dll 6.0.21.002 Thu Jan 20 08:30:14 2005
jomjdi.dll 6.0.21.002 Thu Jan 20 08:30:14 2005
jomos.dll 6.0.21.002 Thu Jan 20 08:30:14 2005
jomsec.dll 6.0.21.002 Thu Jan 20 08:30:15 2005
jomutil.dll 6.0.21.002 Thu Jan 20 08:30:16 2005 Jade60181.jpf -.-.--.--- Thu Sep 21 19:44:25 2006
jaded.sh~ -.-.--.--- Tue Nov 22 18:19:27 2005 jaded.sh.orig -.-.--.--- Fri Dec 23 01:32:48 2005
jade.ini -.-.--.--- Thu Sep 21 19:52:47 2006 jaded.sh.hendra -.-.--.--- Sat Dec 24 03:25:54 2005 Jade60180.jpf -.-.--.--- Wed Jan 11 18:52:24 2006 versioninfo.txt -.-.--.--- Thu Sep 21 19:55:00 2006 Jade60182.jpf -.-.--.--- Sat Jun 10 15:19:46 2006

Libraries: (path= /home/jade/lib/)
==============
libfilesmpl.so 6.0.21.002 Thu Jan 20 22:44:29 2005 libjadcnet.so 6.0.21.002 Thu Jan 20 23:49:02 2005 libjadeactivex.so 6.0.21.002 Thu Jan 20 22:46:22 2005 libjadeaqe.so 6.0.21.002 Thu Jan 20 22:55:08 2005 libjadedit.so 6.0.21.002 Thu Jan 20 22:55:14 2005 libjadesql.so 6.0.21.002 Thu Jan 20 22:58:57 2005 libjadexpat.so 6.0.21.002 Thu Jan 20 22:59:23 2005 libjadinet.so 6.0.21.002 Thu Jan 20 22:59:52 2005 libjadnet.so 6.0.21.002 Thu Jan 20 23:01:41 2005 libjadodbc.so 6.0.21.002 Thu Jan 20 23:09:20 2005 libjadpmap.so 6.0.21.002 Thu Jan 20 23:16:29 2005 libjadprnt.so 6.0.21.002 Thu Jan 20 22:55:24 2005 libjddmpld.so 6.0.21.002 Thu Jan 20 23:16:39 2005 libjetsupp.so 6.0.21.002 Thu Jan 20 23:16:47 2005 libjlncact.so 6.0.21.002 Thu Jan 20 23:50:32 2005 libjlncomp.so 6.0.21.002 Thu Jan 20 23:49:59 2005 libjlnctab.so 6.0.21.002 Thu Jan 20 23:16:53 2005 libjlngram.so 6.0.21.002 Thu Jan 20 23:49:20 2005 libjlnintp.so 6.0.21.002 Thu Jan 20 23:49:55 2005
libjomdb.so 6.0.21.002 Thu Jan 20 23:48:45 2005 libjominc.so 6.0.21.002 Thu Jan 20 23:17:25 2005 libjomjdi.so 6.0.21.002 Thu Jan 20 22:08:14 2005 libjommdb.so 6.0.21.002 Thu Jan 20 23:48:48 2005 libjomnadm.so 6.0.21.002 Thu Jan 20 23:48:48 2005 libjomnfyq.so 6.0.21.002 Thu Jan 20 23:49:00 2005
libjomos.so 6.0.21.002 Thu Jan 20 22:07:46 2005 libjomproxy.so 6.0.21.002 Thu Jan 20 23:49:00 2005 libjomreog.so 6.0.21.002 Thu Jan 20 23:19:04 2005 libjomrpc.so 6.0.21.002 Thu Jan 20 23:49:01 2005 libjomscm.so 6.0.21.002 Thu Jan 20 23:36:21 2005 libjomsec.so 6.0.21.002 Thu Jan 20 23:19:58 2005
libjom.so 6.0.21.002 Thu Jan 20 23:50:58 2005 libjomsrvr.so 6.0.21.002 Thu Jan 20 23:49:05 2005 libjomsupp.so 6.0.21.002 Thu Jan 20 23:30:55 2005 libjomsys.so 6.0.21.002 Thu Jan 20 23:32:11 2005 libjomutil.so 6.0.21.002 Thu Jan 20 23:02:44 2005 libjrnlreader.so 6.0.21.002 Thu Jan 20 23:23:32 2005 libtcpsmpl.so 6.0.21.002 Thu Jan 20 23:32:31 2005 mod_jadehttp.so -.-.--.--- Thu Jan 20 22:00:29 2005
libmodule.a 6.0.21.002 Thu Jan 20 22:05:01 2005

[ConvertFromOldNGs]

by Brendan >> Wed, 24 Jan 2007 8:09:26 GMT

Hi,
The only thing I can suggest is to upgrade to the latest 6.0 or 6.1 release. See schedule here http://www.jadeworld.com/jade/updates.htm

Support for 6.0 is due to end in Q3 this year.

It looks like a bona fide RHEL so reporting the problem to the plant if this doesn't fix the problem is worth a shot.

Cheers, Brendan