MxLoader 7.1

Forums MxLoader MxLoader 7.1

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #20135
    ManuSwe
    Participant

    Hi,

    Anyone have such error?

    #20137
    kfrohne
    Participant

    The image of the error isn’t visible. Would you please paste the text of the error message?

    #20138
    ManuSwe
    Participant

    Sorry, when I posted I saw the picture so I didn’t realised it didn’t followed…

    Here is the text I got when I press the Button Test Connection:

    Error Code: 500

    Source: DoHttpCall

    Description: Internal Server Error

    Error 500: nested exception is: java.lang.StringIndexOutOfBoundsException

    Cause: Check that Configuration Object Structure is defined

    Thanks.

    #20141
    kfrohne
    Participant

    Yes, I received the same error when testing the new release on on our systems. We use a custom context root for our Maximo instances, so the URL that MxLoader is generating doesn’t match. If you set the Logging level to Info and check the log you should see that the URL on the GET request doesn’t match what your system is expecting. I requested an additional Configuration parameter to override the default context root, and Bruno is planning to add the feature to the next release of MxLoader.

    #20142
    ManuSwe
    Participant

    Hi,

    Thanks, I see what you mean, on the HTTP POST request 2 times /meaweb/os, I wrote as I did in the old MxLoader but the /meaweb/os/ is not needed in the new MxLoader…

     

    Thanks for your help!

    #20145
    user
    Keymaster

    Version 7.1.1 has new parameters for custom context root address.

    The tool also checks now if Server Address parameter is including /meaweb/os/ and displays a nice message to avoid such error.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.
You must be logged in to reply to this topic.
Scroll to top