This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


May 7, 2015, 2:48 PM
4 Posts

Domino 9.0.1 FP3 IF2 on W64 crashing - NSD stack included

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags: crash,nsd,nHTTP,server,w64
  • Replies: 9

Just upgraded from 8.5.3 FP6. Never had a problem with 8.5.3 but 9.0.1 FP3 IF2 crashes about 6 times every day. Appears to be caused by the nHTTP task.

Any ideas? Thanks.

UPDATE: The crash is being caused by an application which tries to read data from a DB2 database via ODBC. Is this no longer supported in Domino 9? Why would it cause a horrible crash like this every time? This worked fine in 8.5.3...  

IBM ODBC Driver 10.01.00.872
Connectivity verified OK with ndctest.exe

query:="SELECT MIN(DATE) from ADMIN.ABSTRACTS";
dte:=@DbCommand("ODBC":"NoCache"; "MyDB"; "admin"; "*******"; query);
@If(@IsError(dte); "N/A"; dte)

---END OF UPDATE

 

Date            : Thu May 07 04:40:11 2015
Windows Dir     : C:\Windows
Arguments       : "E:\lotus\domino\nsd.exe" -dumpandkill -termstatus 5 -crashpid 3420 -crashtid 3932 -runtime 300 -ini "e:\lotus\domino\notes.ini" -svcreq 128
NSD Version     : 9.0.13.5078 (Release 9.0.1FP3)
OS Version      : Windows/2008 R2 6.1 [64-bit] (Build 7601), PlatID=2, Service Pack 1 (4 Processors)
CC Fix          : 297307
Build time      : Fri Mar 20 20:36:16 2015
Latest file mod : Fri Mar 20 19:58:40 2015
Domino Version   : Release 9.0.1FP3 HF241 (64-bit server)
Keyview Version : 10.16.0.0 
Java Path       : e:\lotus\domino\jvm\bin\java.exe 
Java Version    :     java version "1.6.0" 

############################################################
### thread 24/173: [   nHTTP:  0d5c:  0f5c] FATAL THREAD
### FP=0x15c90c68, PC=0x7710dc1a, SP=0x15c90c68

### stkbase=0x15ca0000, total stksize=1048576, used stksize=62360
### EAX=0x15c90c98, EBX=0x00000000, ECX=0x15c90b20, EDX=0x15c91230
### ESI=0x000493e0, EDI=0x00001764, CS=0x00000033, SS=0x0000002b
### DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0x00000000 Flags=0x00000287
############################################################
 [ 1] 0x7710dc1a ntdll.ZwWaitForSingleObject+10 (0,15c91688,7FEF57ACCA8,ffffffff)
 [ 2] 0x7FEFCF610DC KERNELBASE.WaitForSingleObjectEx+156 (0,15c90e10,0,1764)
@[ 3] 0x7FEF431930A nnotes.FRSendCommandToService+1450 (15c91688,15c91688,12c,7FEF4317CE0)
@[ 4] 0x7FEF431AE96 nnotes.OSRunExternalScript+1334 (d5c,0,0,5)
@[ 5] 0x7FEF431B82A nnotes.FRTerminateWindowsResources+1738 (0,5,1,428190)
@[ 6] 0x7FEF431BFB9 nnotes.OSFaultCleanupExt+1177 (1,0,15c9fb20,FFFFFFFFFFFFFFF)
@[ 7] 0x7FEF431C5B7 nnotes.OSFaultCleanup+23 (0,1,15c928a8,0)
@[ 8] 0x7FEF437F217 nnotes.OSNTUnhandledExceptionFilter+423 (15c92e60,0,1,341534E41525420)
 [ 9] 0x76f3b9c0 kernel32.UnhandledExceptionFilter+352 (15c92e60,6,0,1)
 [10] 0x771498b0 ntdll.MD5Final+7760 (15c93aa0,7FEEAE8E303,15c935b0,73cbf66b)
 [11] 0x770d7fa8 ntdll.__C_specific_handler+156 (15ca0000,15c9fb20,15c9fb20,771fdadc)
 [12] 0x770e908d ntdll.RtlDecodePointer+173 (15ca0000,76fadd94,12a5c,0)
 [13] 0x770d8baf ntdll.RtlUnwindEx+3007 (15c93aa0,15c935b0,7FE00000000,7FE00000000)
 [14] 0x7710db38 ntdll.KiUserExceptionDispatcher+46 (7FEFA018232,32889350,1ec10208,35c3c8)
@[15] 0x7FEFA021207 nlsxodbc.QTLibRefInitialize+7 (32889350,1ec10208,35c3c8,35c4b8)
@[16] 0x7FEFA018232 nlsxodbc.LsxMsgProcOdbc+578 (0,35c3c8,35c3c8,350009)
@[17] 0x7FEDA5A1CAD nDBODBC.DALInit+141 (35c4b8,15c90010,35c430,9)
@[18] 0x7FEF4D31581 nnotes.DBDFunction+2849 (fdc4160,15c93ea8,10002,15c90005)
@[19] 0x7FEF48B0431 nnotes.FallbackComputeExtension+625 (545,b9,15c93eb8,15c93f50)
@[20] 0x7FEF48B91A3 nnotes.CompGeneralContext::ExtensionProc+611 (2b,5,6800000501,7FEF434BE6C)
@[21] 0x7FEF48ED35F nnotes.ExtensionProc::Execute+319 (fdc4dc0,0,fdc4dc0,fdc4980)
@[22] 0x7FEF48BF7B5 nnotes.AtFunctionNode::ComputeVariants+69 (fdc4980,fdc4558,1f650c60,2)
@[23] 0x7FEF48BFA05 nnotes.AssignmentExpressionNode::ComputeVariants+69 (fdc4558,fdc4558,0,7FEF50CD41E)
@[24] 0x7FEF48C0543 nnotes.RootNode::ComputeVariants+131 (fdc4dc0,fdc4558,fdc49e8,15c98ee4)
@[25] 0x7FEF48B5AB1 nnotes.Compute::Eval+145 (fdc4160,7FE0000017D,fdc4160,15c98ee4)
@[26] 0x7FEF48B1DFE nnotes.NSFComputeEvaluateExt+222 (fdc4160,15c94a70,15c98ee4,15c96970)
@[27] 0x7FEEA93D345 ninotes.NFormula::Evaluate+165 (15c96ac0,7FEEABC0A3C,fdc1d60,12f04e28)
@[28] 0x7FEEA94564E ninotes.NItem::GetDefaultValue+446 (fdc1d60,15c996c0,0,fdc1960)
@[29] 0x7FEEA94AA2D ninotes.NItem::SetDefaultValue+45 (15c9a3c0,0,15c995d8,81)
@[30] 0x7FEEA93406D ninotes.NForm::AddField+253 (0,fdc1760,fdc0164,fdc1950)
@[31] 0x7FEEA934838 ninotes.NForm::ProcessFieldRecords+1784 (20,fdc1960,0,ff8a)
@[32] 0x7FEEA9370EC ninotes.NForm::PrivLoadFields+1356 (15c9a3c0,12f25160,fffe,54)
@[33] 0x7FEEA9373B5 ninotes.NForm::LoadFields+37 (15c9a3c0,7FEEA890A26,3,7FEEA9816E7)
@[34] 0x7FEEA92512E ninotes.NDocNote::CreateUsing+398 (12f24028,b13b828,b13b828,12f24028)
@[35] 0x7FEEA9824DF ninotes.CmdHandlerBase::HandleOpenFormCmd+559 (15c9b4e0,b13b828,0,7FEEAD5FDB0)
@[36] 0x7FEEA88FFC3 ninotes.CmdHandlerBase::PrivHandle+355 (12f24028,b13b828,0,7FEEA8D772E)
@[37] 0x7FEEA88E22F ninotes.CmdHandler::PrivHandle+207 (12f24028,12f34028,1,43247533D4E4626)
@[38] 0x7FEEA88F067 ninotes.CmdHandler::Handler+231 (12f24028,b13b828,12f34028,12f34028)
@[39] 0x7FEEA8E0918 ninotes.InotesHTTPProcessRequestImpl+2808 (1e762178,7FE00000000,0,1)
@[40] 0x7FEEA8E2FE2 ninotes.InotesHTTPProcessRequest+18 (1e762160,3,4f6,0)
@[41] 0x7FEEAE6DBE7 nhttpstack.HTInotesRequest::ProcessRequest+39 (1e761cf8,7FFFF68F2A0,1e761a68,1e762720)
@[42] 0x7FEEAE67346 nhttpstack.HTRequestExtContainer::ProcessRequest+1286 (fd63860,4f6,0,1d8ff788)
@[43] 0x7FEEAE7D1CC nhttpstack.HTRequest::ProcessRequest+2092 (1e761a68,0,0,1d8ff788)
@[44] 0x7FEEAE84283 nhttpstack.HTSession::StartRequest+1491 (1d8ff788,257E3E002FA0AD,d623920,838)
@[45] 0x7FEEAE8E303 nhttpstack.HTWorkerThread::CheckForWork+611 (d623920,0,fb0,4f6)
@[46] 0x7FEEAE8E4CF nhttpstack.HTWorkerThread::ThreadMain+127 (d623920,0,0,1)
@[47] 0x7FEEAE89A14 nhttpstack.HTThreadBeginProc+52 (0,0,0,0)
@[48] 0x7FEF432D0E2 nnotes.ThreadWrapper+258 (0,0,0,0)
 [49] 0x76eb59cd kernel32.BaseThreadInitThunk+13 (0,0,0,0)
 [50] 0x770eb891 ntdll.RtlUserThreadStart+33 (0,0,0,0)

 

 

 

May 7, 2015, 7:32 PM
74 Posts
Known issue, no solution yet - lsxodbc on w64 bit crashes
 There is a SPR tracking this issue:  JCHS9DDUDK:  Server Crash On Amgr When The Lsxodbc Is Initializing - Qtlibrefinitialize

There is not yet a solution, but it is actively being worked.  (lsxodbc running on w64 server)

Only workaround for now is to disable the agent (or code) that is trying to use lsxodbc.
May 7, 2015, 7:48 PM
145 Posts
Open a PMR with Lotus Support and reference SPR JCHS9DDUDK
Looks to be the same problem as   JCHS9DDUDK:  Server Crash On Amgr When The Lsxodbc Is Initializing - Qtlibrefinitialize

and they appear to be working on a fix.

Regards,
John Pag

jpaganet@us.ibm.com
May 7, 2015, 9:48 PM
4 Posts
Domino 9 unusable without ODBC support

Thanks for the replies. This is shocking. None of the ODBC features work anymore in Domino 9 and the server crashes every time. "Removing" this code is out of the question, interacting with DB2 data via ODBC is an integral part of many applications we run. Did this break in a later fixpack or are all 9.x versions affected? Wondering if I can just downgrade to an earlier 9.x release or if i have to drop back to 8.5.3

In my case it is not technically lsxodbc, not Lotus Script but a simple formula @DbCommand("ODBC":"NoCache"; "MyDB"; "admin"; "*******"; query)  .. but I see that perhaps it's the same lsxodbc module failing.

May 7, 2015, 10:59 PM
4 Posts
Where to open PMR?

Where are you looking up the SPR #s? Is there way to open a PMR/SPR internally in IBM? I see that the Lotus End User SPR DB has been sunset.

Thanks.

EDIT: found this SPR, wonder if that's the ODBC fix:
http://www-10.lotus.com/ldd/fixlist.nsf/8ed1b46cfdba8957852570c90054623b/46788f1aaebc106185257d8d005d6d22?OpenDocument&Highlight=0,odbc

SPR # SSHE9FDJW5 fixed in 9.0.2
9.0.1 FP3
 release

Product AreaServer  Technical Area: @Db Functions  PlatformCross Platform
SPR# SSHE9FDJW5 - Fixed an issue with ODBC causing a crash on 64-bit environments.

May 8, 2015, 9:35 PM
4 Posts
ODBC still crashing 9.0.1. FP3 IF3 (HF515)

Just installed 9.0.1. FP3 IF3 (HF515). Domino still crashes every time an application attempts to use ODBC.

Jun 24, 2015, 9:08 AM
1 Posts
ODBC crash in 9.0.1

Hi

Had the same problem with ODBC and opened a PMR.

Just got a fix to install and test. It works for me now !!
A solution is coming, probably included in 9.0.2 

Mar 12, 2016, 6:54 PM
1 Posts
ODBC still crashing 9.0.1. FP5

Dear All, We have migrated today one server from 8.5.3 to 9.01 FX5 and obtaining the same error, @dbcommand crashes server, there is any solution? 

Help Please

Apr 6, 2016, 2:28 PM
4 Posts
Odbc connectivity issues

 We have migrated from 6.5 to 9.01. Domino crashes every time an application attempts to use ODBC. We use lsxodbc and also @dbcommands to connect odbc.

Kindly help me if there is any fixes available. i even installed ODBC driver 9. Server is windows 2008 R2 64 bit

any help will be highly appreciated

thanks

Balaji

balaji.dhananjayan@hpe.com

 

Mar 1, 2017, 7:31 AM
1 Posts
odbc @dbcommand server crash

We have migrated from 8.5.3 to 9.0.1 FP7 HF409 . Every attempt for odbc dbcommand causes server crash. How can we solve this issue?


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal