FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.



Dec 2, 2015, 5:11 AM
6 Posts

HTTP500 error on 9.0 server not 8.5

  • Category: Debugging
  • Platform: All
  • Release: 9.0.1
  • Role: Developer
  • Tags: http500 error
  • Replies: 2

This has been (de)bugging me for quite a while now, have anyone else experienced and solved a similar issue:

We run the same xpage application on two different servers. One is the good old development server stil running on 8.5.1 and the other the production server running on 9.0.1

Everything works beautifully on the 8.5.1 server but when we test it on the 9.0.1 server we find some random xpages throw a http500 error

What makes it unusual to me is that a page working perfectly on the 8.5.1 server throws an error on the 9.0.1 server.

The build is in a 9.0.1 designer client so that should not be an issue, but apparently some other compatibility problem is.

Any input welcome!

 

Regards,

 

Vidar Solevag

Dec 2, 2015, 4:05 PM
589 Posts
ok

My input is this...

You're crazy to run 8.5.1 for your dev server.  Upgrade that immediately and make it work there and then move it to production.  Problem solved.

8.5.1 was the initial release of XPages.  Back in 2009.  A lot has happened since then.  Things have changes which is probably breaking something.  Do NOT NOT NOT think that the almighty "Notes Backward Compatibility" is in effect for XPages, or any other web app dev system.

If your production server, and clients are on 9.01 - and that's awesome by the way, there's no reason in the world to have your dev server be 8.5.1.

Feb 2, 2016, 9:37 AM
14 Posts
outside of the craziness of developing in a different version than you deploy to ...

... often a production environment has more data in it. You may be searching for something that's not found in the production environment, or the code's not configured properly. That's what I got out of 500-errors.

Is the crash dump turned on to see, does the HTTP server have something more to say?


FORUM PLAN UPDATE
Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.