IBM Support

Importing and the dreaded Internal Server Error

Technical Blog Post


Importing and the dreaded Internal Server Error


Your in the midst of importing a ton of records into Maximo via the new Application Import feature or simply previewing them via the Import Preview feature in the External Systems application when the browser gui throws up an 'Internal Server Error'.
The generic explanation for this error:

The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser) for access to the requested URL.

This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyze these logs.

In this case, the WebSphere Application Server ships with a default IO timeout of 60 seconds. Depending on the the number of records being imported (5000, 10000, etc.) and their complexity the timeout value should be increased to indicate to WAS more time is needed for the transaction. Note that regardless of the displayed 'Internal server Error', the import transaction is successfully processed by Maximo.

Details on modifying the WAS plugin-config.xml file to increase the default ServerIOTimeout value are here.

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]