cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
941
Views
0
Helpful
1
Replies
Highlighted
Beginner

JDEdwards Launch failure - JdeNetTimeoutException

Has anyone else running JDEdwards encountered the following error periodically and if so what was the cause?

Launch failure: JDE request failed: com.jdedwards.system.net.JdeNetTimeoutException

1 REPLY 1
Highlighted
Beginner

Hi John,

Can you check that the following parameters are updated in enterprise server jde.ini file

 

Review the following and make changes as appropriate:


LINUX/SOLARIS/AIX/HPUX


[JDENET_KERNEL_DEF16]
krnlName=XML LIST KERNEL
dispatchDLLName=libxmllist.so (.sl for HPUX)
dispatchDLLFunction=XMLListDispatch
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0


[JDENET_KERNEL_DEF22]
krnlName=XML DISPATCH KERNEL
dispatchDLLName=libxmldispatch.so (.sl for HPUX)
dispatchDLLFunction=JDEK_XMLDispatch
maxNumberOfProcesses=6
numberOfAutoStartProcesses=1


WINDOWS
[JDENET_KERNEL_DEF16]
krnlName=XML List Kernel
dispatchDLLName=xmllist.dll
dispatchDLLFunction=_XMLListDispatch@28
maxNumberOfProcesses=1
numberOfAutoStartProcesses=0


[JDENET_KERNEL_DEF22]


krnlName=XML DISPATCH KERNEL
dispatchDLLName=xmldispatch.dll
dispatchDLLFunction=_XMLDispatch@28
maxNumberOfProcesses=6
numberOfAutoStartProcesses=1

AS400
[JDENET_KERNEL_DEF16]
krnlName=XML LIST KERNEL
dispatchDLLName=XMLLIST
dispatchDLLFunction=XMLListDispatch
maxNumberOfProcesses=3
beginningMsgTypeRange=5257
endingMsgTypeRange=5512
newProcessThresholdRequest=0
numberOfAutoStartProcesses=1


[JDENET_KERNEL_DEF22]
krnlName=XML DISPATCH KERNEL
dispatchDLLName=XMLDSPATCH
dispatchDLLFunction=XMLDispatch
maxNumberOfProcesses=6
numberOfAutoStartProcesses=1


 [XMLLookupInfo]
XMLRequestType1=list
XMLKernelMessageRange1=5257
XMLKernelHostName1=local
XMLKernelPort1=0
XMLRequestType2=callmethod
XMLKernelMessageRange2=920
XMLKernelHostName2=local
XMLKernelPort2=0
XMLRequestType7=ube
XMLKernelMessageRange7=380
XMLKernelHostName7=local
XMLKernelPort7=0
XMLKernelReply7=1

 

Once you are done, restart the enterprise server and try scheduling jobs

 

Thanks,

Ashwin

Content for Community-Ad
This widget could not be displayed.