XPages discussion database: "Command Not Handled Exception"

HCL Domino Domino Forum
1

I have run into a serious issue when using the new 8.5 discussion database based on XPages.

I am running 8.5 HF1 on Windows 2003 Server R2 Service Pack 1 (32-bit)

  1. Create a new discussion template

  2. Access it with a web browser

  3. Open new topic and attach a file (at this point the attachment is still accessible)

  4. Save the new topic

  5. Try to open the attachment (no matter the filetype) the following error occurs:

06.02.2009 00:47:48 HTTP JVM: SEVERE: CLFAD####E: Exception thrown

06.02.2009 00:47:48 HTTP JVM: SEVERE: CLFAD####E: Exception occurred servicing request for: /mediagor/forum.nsf/xsp/.ibmmodres/domino/OpenAttachment/forum.nsf/78E9EDD3481D80AFC1257554007FE1F9/Body/abc.txt - HTTP Code: 500

06.02.2009 00:47:49 HTTP Web Server: Command Not Handled Exception [/mediagor/forum.nsf/xsp/.ibmmodres/domino/OpenAttachment/forum.nsf/78E9EDD3481D80AFC1257554007FE1F9/Body/abc.txt]

Then I tried to access the file the old fashion way and this came up:

06.02.2009 00:56:38 HTTP Web Server: Corrupt Data Exception [/mediagor/forum.nsf/0/78E9EDD3481D80AFC1257554007FE1F9/Body/abc.txt]

I still wasn’t convinced because the attachment was opening just fine in the Lotus Notes client, so I tried:

/mediagor/forum.nsf/0/78e9edd3481d80afc1257554007fe1f9/Body/M2/abc.txt?OpenElement

and it worked just fine… I don’t know why?

This happens with every database and every file I try to attach.

I also tried a clean install of the server but it didn’t help much (I thought it was caused by upgrading from 8.0.1 to 8.5b2 and then 8.5 HF1)

And I checked and double checked the security settings.

Is there any way to get a better error message?

-J

2

Subject: XPages: Setting a detailed error page…

Hi Janko,

Open the Application Properties view for the application. Then select the “XPages” tab across the bottom of this view. Now “check” the “Display default error page” option, save, and reload the application in the browser. You will get a detailed stack trace in the browser - please forward this to me (tony.mcguckin@ie.ibm.com).

Thanks.

3

Subject: No detailed stack trace

I’ve already have this option set… but there is no stack trace on the error message in the browser:

Error 500

HTTP Web Server: Command Not Handled Exception

4

Subject: You have to change the setting as Tony suggested in order to get the stacktrace

5

Subject: It’s turned on, but nothing more shows up

I read this article on Domino Designer wiki:

http://www-10.lotus.com/ldd/ddwiki.nsf/dx/error-management-in-xpages.htm

and not only turned on the “Display the default error page” in the Application properties, but also set:

edit the xsp.properties file under \xsp\nsf. Uncomment the line “xsp.error.page.default” and set the value to true.

I’m all out of ideas…

Maybe it could be a character set problem…

6

Subject: Same here…

We are running into the same issue with some of our code on an 8.5 server. The JVM is throwing the same errors. Any update on this? We have reported this in the Design Partner Forum as well.

7

Subject: Is there a way to handle these errors?

For instance…I was just testing dynamically assigning data values to a column in a view and put in a non-existent data value on purpose to see what happens.

It errors which is fine but is there a way to code that script so that if it does error and cannot locate that data value that the page can still display?

8

Subject: Anything happening on this subject?

Because at the moment it’s useless for production use…

9

Subject: Agreed I am trying funnel traffic to your post

This is embarrassing to have a non functioning template which has been so core to Lotus Notes in the past.

Have you submitted a PMR? I will submit a support request.

Elijah

10

Subject: Opened a PMR #62376 L6Q 000

FYI

11

Subject: No, I haven’t… thank you

Thank you for submitting it. I hope it gets clarified in a reasonable time.

I am considering a clean server install (Windows and Domino) because it might be a compatibility issue from an upgrade from a prior version.

I’ll post my findings.

12

Subject: Update to the PMR

I was sent this info "… discussed this issue with my team and found that in one customer case, this problem was resolved by re-installing Domino 8.5 due to possible corruption in the JVM\Lib\Ext directory. Before reinstall, rename or move out the existing JVM directory to ensure the install will add new files.

Please run the install process for the Domino 8.5 code again on the same directories after removing JVM\Lib\Ext directory. "

We did do an upgrade as well. Not super happy about doing a reinstall on our production box but I guess I will give it a try.

Elijah

13

Subject: New/Reinstall not working for me either

Same error thrown when opening attachments.

14

Subject: New install didn’t work for me

Tried a complete reinstall (removed all of the Domino files from the server) but had no luck.

I’ll try a clean install on a brand new server in the next days, when the new machines are setup…

Frustrating…

15

Subject: Enable HTTP Logging

Hi Janko,

If you enable HTTP Logging (http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg21099151) and post the request that is part of the 500 error. It should start with “*** New Request” and end with “*** End Request Step”. That will give more information about the request and where is it failing in the http call stack.

16

Subject: Any update on this?

We are experiencing the same issue. Any resolution identified?

17

Subject: SPR #PHAN7QPARZ

This issue sounds like a match to SPR #PHAN7QPARZ (APAR #LO41243), which was fixed in Domino 8.5.1.

Has anyone on thread tested in 8.5.1 that could post their results?

18

Subject: 8.5.1

I’m on 8.5.1 and sent over all logs to IBM and spend months of time, and got no answers.

19

Subject: Work Around

I was able to get rid of the message as we don’t use XPages by turning it off by modifiing the NOTES INI with the following line:

INOTESDISABLEXPAGECMD=1

Then restarted HTTP.