Exceptionally Slow Response for End Users! 1

[scanjam]

Hello Ladies, Gentlemen!

Currently we are experiencing issues with our JDE Systems as a whole.

To try and explain the situation the entire JDE Setup is actually coping (after a few internal resourcing and server issues) we believe its finally setup ok (this is ONLY from a technical MCSE background not a JDE perspective)

Alas however as JDE (from the client side) is experiencing exceptionally slow response times when running reports etc.

We have been clever and run network monitoring and the SQL profiler to basically ascertain that there is a HUGE timeout / wait time between the JDE client and the enterprise server.... (anywhere from 17 seconds until about 5 minutes)

From SQL all the reports etc are processed in milliseconds, it just seems that the transfer of the information (within the application not from a network side of things) from Client --> through JDE --> to SQL and back again is somewhere lagging or timing out.

Is there somewhere in JDE that a specific timout value or something similar is specified (ie JDE.ini) or has ANYONE at all experienced any problems of this nature before? In all our experience we believe all the servers to be setup perfectly (SQL, Operating System and Network) but yet there is still this significant lag / wait time between client/server requests, keep alives or whatever.

We are running OneWorld Xe B7333, Service Pack 19 - Update 5. Enterprise is running on a dual HP xeon 700 with 4 gig of ram. The JDE database is running on a dual HP 1.4 xeon, 2gig ram.

Hope someone can help...
Kind Regards

James

 

[ChelseaGirl]

Check the jde.ini on the Enterprise server and check the debug section - if you've got it switched on it will slow things down.

For UBE's make sure that you'r not running UBE's that should be single threaded, in more than one queue.

How many jdenet and jdequeue processes are you running, if there arn't egough jdenet processes it will slow users logging on, and jdequeue will be used to run the UBE's.

 

[scanjam]

ChelseaGirl..
Thanks for the quick reply!

Here is the jde.ini attached. you will have to excuse me, im only Server "Technical" not JDE technical, so i may be a little slow.

Im positive debugging is turned off, however upgrading our server has been on the list of things to do for ages so we can get "more queues" etc etc.. however as to how many we are running... i couldnt be sure.. I have attached the JDE.ini from the enterprise server as below.

Our issues is we need to justify the server upgrade and from all the "Server Technical" people it looks like The enterprise server is doing NOTHING.. (can this be because we are running fat client?.... im assuming if we ran a citrix environment eventuially that the ability to "locally" run logic on the users session would be disabled? essentially pushing all that processing BACK to the enterprise server??

Thanks again for your help!
Hope this isnt too big.....







JDE.ini
; OneWorld initialization file INI(JDE)
; NT Intel specific version - B73.3.3

[JDE_CG]
;TARGET=DEBUG
TARGET=RELEASE
INCLUDES=D:\Program Files\Microsoft Visual Studio\Vc98\atl\include;D:\Program Files\Microsoft Visual Studio\Vc98\mfc\include;D:\Program Files\Microsoft Visual Studio\Vc98\include;$(SYSTEM)\INCLUDE;$(SYSTEM)\INCLUDEV;$(SYSTEM)\CG;$(APP)\INCLUDE;
LIBS=d:\Program Files\Microsoft Visual Studio\Vc98\mfc\lib;D:\Program Files\Microsoft Visual Studio\Vc98\lib;$(SYSTEM)\LIB32;$(SYSTEM)\LIBV32;$(APP)\LIB32;
MAKEDIR=d:\Program Files\Microsoft Visual Studio\Common\Tools\WinNT;d:\Program Files\Microsoft Visual Studio\Common\MSDev98\Bin;d:\Program Files\Microsoft Visual Studio\Common\Tools;d:\Program Files\Microsoft Visual Studio\VC98\bin
STDLIBDIR=d:\Program Files\Microsoft Visual Studio\Vc98\lib;d:\Program Files\Microsoft Visual Studio\Vc98\mfc\lib

[TCEngine]
TraceLevel=1
; (Where n is a number from 0 through 10.)

[DEBUG]
LogErrors=TRUE
Output=NONE
;Output=FILE
Trace=FALSE
DebugFile=d:\jdedwardsoneworld\ddp\b7333\log\jdedebug.log
JobFile=d:\jdedwardsoneworld\ddp\b7333\log\jde.log
ClientLog=1
JDETSFile=d:\jdedwardsoneworld\ddp\b7333\log\JDETS.log
KeepLogs=1
RepTrace=0
TamTraceLevel=0

[SVR]
SpecPath=spec
SourcePath=source
ObjectPath=obj
HeaderPath=include
HeaderVPath=includev
BinPath=bin32
LibPath=lib32
LibVPath=libv32
MakePath=make
WorkPath=work
EnvironmentName=PD7333
LibraryListName=PD7333

[INSTALL]
B733=d:\jdedwardsoneworld\ddp\b7333
Double_Byte=0
LocalCodeSet=WE_ISO88591
StartServicePrefix=JDE Update 3

[JDENET]
serviceNameListen=6009
serviceNameConnect=6009
maxNetProcesses=5
maxNetConnections=400
maxKernelProcesses=50
maxKernelRanges=13
netTrace=0
ServiceControlRefresh=5

[JDENET_KERNEL_DEF1]
krnlName=JDENET RESERVED KERNEL
dispatchDLLName=jdenet.dll
dispatchDLLFunction=_JDENET_DispatchMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF2]
krnlName=UBE KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchUBEMessage@28
maxNumberOfProcesses=3
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF3]
krnlName=REPLICATION KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_DispatchRepMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF4]
krnlName=SECURITY KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchSecurity@28
maxNumberOfProcesses=2
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF5]
krnlName=LOCK MANAGER KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_TM_DispatchTransactionManager@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF6]
krnlName=CALL OBJECT KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchCallObjectMessage@28
maxNumberOfProcesses=10
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF7]
krnlName=JDBNET KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchJDBNETMessage@28
maxNumberOfProcesses=2
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF8]
krnlName=PACKAGE INSTALL KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchPkgInstallMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF9]
krnlName=SAW KERNEL
dispatchDLLName=jdesaw.dll
dispatchDLLFunction=_JDEK_DispatchSAWMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF10]
krnlName=SCHEDULER KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchScheduler@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=1

[JDENET_KERNEL_DEF11]
krnlName=PACKAGE BUILD KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchPkgBuildMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF12]
krnlName=UBE SUBSYSTEM KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchUBESBSMessage@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0

[JDENET_KERNEL_DEF13]
krnlName=WORK FLOW KERNEL
dispatchDLLName=jdekrnl.dll
dispatchDLLFunction=_JDEK_DispatchWFServerProcess@28
maxNumberOfProcesses=5
numberOfAutoStartProcesses=0

[NETWORK QUEUE SETTINGS]
QEnv=PD7333
QUser=JDE

QueueDelay=5
JDENETTimeout=60
KillImmediate=1
UBEQueues=3
UBEQueue1=QB7333
UBEQueue2=NIGHTQ
UBEQueue3=POSTQ
UBEPriority=5
PackageQueues=1
PKGQueue1=QB7333
SpecInstallQueues=1
SpcQueue1=QB7333
; Add more queues here ... UBEQueues=n, UBEQueuen
;UBEQueues=6
;UBEQueue1=QB7333
;UBEQueue2=QB7333
;UBEQueue3=QB7333
;UBEQueue4=QB7333
;UBEQueue5=NIGHTQ
;UBEQueue6=POSTQ

[BSFN BUILD]
BuildArea=d:\jdedwardsoneworld\ddp\b7333\packages
OptimizationFlags=/Gz /O2 /MD /W4 /GX /Gy
DebugFlags=/Gz /Od /Zi /MDd /Yd /W4 /GX /Gy /D "_DEBUG"
InliningFlags=
DefineFlags=/D "WIN32" /D "_WINDOWS" /D "IAMASERVER" /D "KERNEL"
CompilerFlags=/nologo /c
OSReleaseLevel=5.0
LinkFlags=/DLL /DEBUG /SUBSYSTEM:windows /FORCE:MULTIPLE /FORCE:UNRESOLVED /INCREMENTAL:YES /VERBOSE /MAP
LinkLibraries=jdekrnl.lib jdel.lib jdenet.lib jdeipc.lib owver.lib
;SimultaneousBuilds=0
SimultaneousBuilds=5

[JDEIPC]
ipcTrace=0
;CLSID=
startIPCKeyValue=6000

[JDEMAIL]


[DB SYSTEM SETTINGS]
Version=43
ODBCCursors=1
CursorType=3
Default User=JDE

Default Env=PD7333
Default PathCode=PD7333
Base Datasource=CHJDE - B7333 Server Map
Object Owner=SVM7333
Server=CHSQL01
Database=CHJDE - B7333 Server Map
Load Library=JDBODBC.DLL
Decimal Shift=Y
Julian Dates=Y
Use Owner=Y
Secured=Y
Type=S
Library List=
TDSError=1
ConnectionPooling=0

[UBE]
UBEDebugLevel=1

[LOCK MANAGER]
Server=CHJDE
AvailableService=TS
RequestedService=NONE

[SERVER ENVIRONMENT MAP]

[SECURITY]
SecurityServer=CHJDE
User=JDE

DefaultEnvironment=PD7333
DataSource=System - B7333
History=0

[Bsfn Builder]
BuildArea=d:\jdedwardsoneworld\ddp\b7333
User=JDE

PathCode=pd7333

 

[ChelseaGirl]

Yep - If you ran Citrix the Logic would get "pushed" back to the Server - we got two Logic servers to get over this.
We've also got a Batch server as well to spread things out a bit.

Looking at your ini. You may want to change the following to
there are several different places Debuging gets turned on....

[DEBUG]
LogErrors=0

[UBE]
UBEDebugLevel=0

[TCEngine]
TraceLevel=0
; (Where n is a number from 0 through 10.)

You may have to stop and start the JDE Services for the change to take affect, not too sure what the TCEngine is....

[JDENET]
maxNetProcesses=5
maxNetConnections=400

This means that you have 400 connections per one jdenet_n.exe running - so that looks OK, unless you expect to have more than 2000 concurent users.

check
[JDENET]
maxKernalProcesses=5
you might be able to up the number, but it mustn't be less than the total "maxNumberOfProcess" in each JDE_KERNAL_DEF sections.

Don't worry about the BSFN section - that's to do with package builds.

I see you have JDE_KERNAL_DEF for workflow. If your running workflow the SQL tables might need checking out, they get very messy very quickly.....

Hope this helps, do double check out the above in the manual

 

[Housemartins]

Hi there,
One think you should also be aware of, is NOT to use mixed operating systems (NT, 2000, 98 or XP), all together on your fat client installations, under the same domain.
This is something JDE does not really like to work with and usually slows down the end user. Hope this also helps.

 

[4rayman]

Hi Scanjam,
I have a Client experiencing exactly the same symtoms as you have described, were you able to resolve your issues and if so how ?

 

[richardsdd]

Seeing as though performance issues vary from client to client, could you post a bit of their configuration?

 

[monkeylizard]

I have no doubt that ChelseaGirl must've fixed ScanJam's problem.

Debugging was deff. ON. this WILL ALWAYS slow down JDE in a very noticable way.

Always check JDE.INI debug settings if you experience slow performance.

Monkeylizard
-Isaiah 35-

 

[4rayman]

All,
the answer to our problems turned out to be MS SQL using a clustered rather than non-clustered index when interpreting the following statement:
"Select * from xxxx where a=1 b=2 c=3"
table xxxx had 2 indexes as follows
index 1 : clustered keys : d f a e c b
index 2 : non-clustered keys : a b c

Sql used the first index to service the select due to the Select *. We replaced the * with item "a" which allowed sql to use the 2nd index.

The results were dramtic. An 8 hour + UBE now runs in 30 minutes.

Thank goodness for SQLprofiler.