Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Error while publishing a mobile app

    Posted Fri February 24, 2023 04:32 PM
    Edited by System Test Wed March 22, 2023 11:51 AM

    Hi,
    in a Mobile v8.9 dev environment, the publish of a cloned app goes to error.
    The log in the ConfigApp is:

    2023-02-24 22:12:52 Work Center Upload with apikey provided: url = http://maxdev1:80/maximo/api/os/OSLCMAFAPPDATA?appid=Z0TECHMOBILE&action=wsmethod:uploadFile&version=8.9.0.0
    2023-02-24 22:12:52   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
    2023-02-24 22:12:52                                  Dload  Upload   Total   Spent    Left  Speed
    100 5189k    0   347  100 5189k    265  3964k  0:00:01  0:00:01 --:--:-- 3961k
    2023-02-24 22:12:53 {"oslc:Error":{"oslc:statusCode":"400","spi:reasonCode":"BMXAA9238E","oslc:message":"BMXAA9238E - An error occurred when the Application Service WebMethod was started. The nested stack trace gives details of the error.\n\tnull","oslc:extendedError":{"oslc:moreInfo":{"rdf:resource":"http:\/\/maxdev1\/maximo\/api\/error\/messages\/BMXAA9238E"}}}}executing command:
    2023-02-24 22:12:53 curl --insecure -T "./build/app/build/Z0TECHMOBILE__ver-8.9.0.0.zip" "http://maxdev1:80/maximo/api/os/OSLCMAFAPPDATA?appid=Z0TECHMOBILE&action=wsmethod:uploadFile&version=8.9.0.0&apikey=2v5me7ikj6636nc9cu73k78rriokp4cmqcdf6m2j"

     

    On Maximo side, it is GraphiteAppService.getAppInfo() that throws the exception (I suspect it is related to the "content-length" of the request):

    [2/24/23 22:12:53:657 CET] 000001e5 SystemOut     O 24 Feb 2023 22:12:53:657 [ERROR] [MAXIMO] [CID-MXOSLC-11206] BMXAA9238E - An error occurred when the Application Service WebMethod was started. The nested stack trace gives details of the error.
        null
    psdi.util.MXApplicationException: BMXAA9238E - An error occurred when the Application Service WebMethod was started. The nested stack trace gives details of the error.
        null
        at com.ibm.tivoli.maximo.oslc.provider.action.WebMethodActionHandler.invokeMethod(WebMethodActionHandler.java:621) ~[businessobjects.jar/:?]
        at com.ibm.tivoli.maximo.oslc.provider.action.WebMethodActionHandler.action(WebMethodActionHandler.java:128) ~[businessobjects.jar/:?]
        at com.ibm.tivoli.maximo.oslc.provider.OslcActionProcessor.invoke(OslcActionProcessor.java:357) ~[businessobjects.jar/:?]
        at com.ibm.tivoli.maximo.oslc.provider.OSPOSTRouteHandler.handleRequest(OSPOSTRouteHandler.java:788) ~[businessobjects.jar/:?]
        at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.handleRoute(MaximoOslcProviderServlet.java:1300) ~[commonweb.jar:?]
        at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.processPostPut(MaximoOslcProviderServlet.java:1412) [commonweb.jar:?]
        at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.doPost(MaximoOslcProviderServlet.java:266) [commonweb.jar:?]
        at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.doPut(MaximoOslcProviderServlet.java:274) [commonweb.jar:?]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) [javax.j2ee.servlet.jar:?]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [javax.j2ee.servlet.jar:?]
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1235) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:779) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:179) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:143) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:96) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.tivoli.maximo.filter.UnSupportedMethodBlockFilter.doFilter(UnSupportedMethodBlockFilter.java:60) [commonweb.jar:?]
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90) [com.ibm.ws.webcontainer.jar:?]
        at psdi.webclient.system.filter.HttpXFrameOptionsFilter.doFilter(HttpXFrameOptionsFilter.java:38) [classes/:?]
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90) [com.ibm.ws.webcontainer.jar:?]
        at psdi.webclient.system.filter.MTContextFilter.doFilter(MTContextFilter.java:53) [classes/:?]
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90) [com.ibm.ws.webcontainer.jar:?]
        at org.apache.logging.log4j.web.Log4jServletFilter.doFilter(Log4jServletFilter.java:71) [log4j-web-2.17.1.jar:2.17.1]
        at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:197) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:90) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:979) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1119) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:4238) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.webapp.WebAppImpl.handleRequest(WebAppImpl.java:2210) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1033) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:382) [com.ibm.ws.webcontainer.jar:?]
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) [com.ibm.ws.runtime.jar:?]
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:532) [com.ibm.ws.runtime.jar:?]
        at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:318) [com.ibm.ws.runtime.jar:?]
        at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) [com.ibm.ws.runtime.jar:?]
        at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) [com.ibm.ws.runtime.jar:?]
        at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) [com.ibm.ws.runtime.jar:?]
        at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909) [com.ibm.ws.runtime.jar:?]
    Caused by: java.lang.NumberFormatException: null
        at java.lang.Integer.parseInt(Integer.java:554) ~[?:2.9 (09-29-2022)]
        at java.lang.Integer.parseInt(Integer.java:627) ~[?:2.9 (09-29-2022)]
        at com.ibm.iot.maximo.GraphiteAppService.getAppInfo(GraphiteAppService.java:149) ~[businessobjects.jar/:?]
        at com.ibm.iot.maximo.GraphiteAppService.uploadFile(GraphiteAppService.java:105) ~[businessobjects.jar/:?]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) ~[?:1.8.0]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0]
        at java.lang.reflect.Method.invoke(Method.java:508) ~[?:1.8.0]
        at com.ibm.tivoli.maximo.oslc.provider.action.WebMethodActionHandler.invokeMethod(WebMethodActionHandler.java:538) ~[businessobjects.jar/:?]
        ... 47 more

    Do you have any suggestions on how to fix the problem?

    Thanks , Diego


    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Error while publishing a mobile app

    Posted Mon February 27, 2023 06:45 AM

    Hi Diego,

    I have seen this issue while trying to upload TECHMOBILE after making some customer changes. My issue was resolved by giving object structure access to the user ( I think i ended up using MAXADMIN user). My issue was in V8.8.

    If you have built a custom app then I believe it could also be a case of app not being available in Maximo to map you custom app. I will start with enabling 3 loggers in debug mode - Graphite, OSLC and sql ( info mode). Sometimes the errors from Maximo mobile is misleading.



    ------------------------------
    Biplab Choudhury
    IBM Champion 2022
    Senior Consultant
    BPD Zenith
    Melbourne
    ------------------------------

    Original Message


  • 3.  RE: Error while publishing a mobile app

    Posted Mon February 27, 2023 08:50 AM

    That error as you mentioned looks to be trying to parse the content-length header. I've never seen this before but if you could monitor the request to make sure that the content-length header is being provided and looks correct on the request to the server. I'm not sure if you're using EAM or MAS but it'd be good to log the header on the server side as well to see if something (a firewall for example) is stripping or modifying the header in some way. 



    ------------------------------
    Steven Shull
    ------------------------------

    Original Message


  • 4.  RE: Error while publishing a mobile app

    Posted Thu March 02, 2023 09:32 AM

    It looks like there was an error when trying to publish a cloned app on a Mobile v8.9 dev environment. The error message suggests that the error occurred when the application service web method was started.

    The nested stack trace provides more information and suggests that the issue may be related to the "content-length" of the request. It's possible that the request is too large, causing the web method to fail.

    To troubleshoot this issue further, you could try reducing the size of the request by removing any unnecessary files or data. You could also check the server logs for any additional error messages that may provide more context on the issue.

    It's also possible that there may be a configuration issue on the server side that is causing the problem. In that case, you may need to consult with a server administrator to determine if any changes need to be made to the server configuration.



    ------------------------------
    Aiden Markram
    ------------------------------

    Original Message


  • 5.  RE: Error while publishing a mobile app

    Posted Mon March 13, 2023 02:09 PM

    Thanks to all the replies.
    Below the debug traces of the http-plugin log of my EAM environment.
    Ad you can see, the content-length is zero so I suppose it's the mobile dev env. sending it blank

    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    PUT /maximo/api/os/OSLCMAFAPPDATA?appid=X3ASSETMOBILE&action=wsmethod:uploadFile&version=8.9.0.0&apikey=<removed> HTTP/1.1
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Host: max7613demo
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    User-Agent: curl/7.61.1
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Transfer-Encoding: chunked
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Accept: */*
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Expect: 100-continue
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSXCTCONTEXTID: <removed>
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSIS: false
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSSC: http
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSPR: HTTP/1.1
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSRA: 192.168.1.217
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSRH: 192.168.1.217
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSSN: max7613demo
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    $WSSP: 80
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    _WS_HAPRT_WLMVERSION: -1
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DEBUG: lib_htrequest: htrequestWrite: Waiting for the continue response
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    HTTP/1.1 100 Continue
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Content-Length: 0
    [Fri Mar 10 21:08:47 2023] 00004d94 00002b98 - DETAIL:    Date: Fri, 10 Mar 2023 20:08:46 GMT


    ------------------------------
    Diego Visentin
    EAM BU Director
    Tempestive S.p.A.
    ------------------------------

    Original Message


  • 6.  RE: Error while publishing a mobile app

    Posted Sun January 19, 2025 05:33 AM

    Hello @Diego Visentin

    I hope you are doing well,

    I'm currently facing the same issue right now after duplicating SRMOBILE and adding some customization, i successfuly was able to duplicate it but i can't publish any of my changes giving the same above error.

    Did you manage to bypass this error. If so, can you tell me what is causing this to happen.

    App Version : 8.11.0.0 

    Framework Version: 8.11.20_3855

    Manage Version: 8.7.13

    Best Regards.



    ------------------------------
    Mostafa Mosaad
    Software Engineer
    Megasoft
    Cairo
    01117275779
    ------------------------------

    Original Message


  • 7.  RE: Error while publishing a mobile app

    Posted Thu January 30, 2025 09:36 AM

    Hi @Mostafa Mosaad,
    I'm sorry, but I don't have a solution to share for v8.11.
    We have migrated to MAS v9 and are trying the v9.1 preview.
    If this problem recurs I will try to investigate it better and possibly fix it.

    PS: no publish problem if your backend is EAM v7.6.1.3 with last fixes



    ------------------------------
    Diego Visentin
    ------------------------------

    Original Message


  • 8.  RE: Error while publishing a mobile app

    Posted Fri March 07, 2025 12:43 AM
    Edited by Dhiraj Panjwani Fri March 07, 2025 12:43 AM

    Hi Mostafa,

    Were you able to find solution for your issue with respect to publishing the duplicate application? We are getting error with permissions when the app is getting published.

    Thanks,

    Dhiraj Panjwani



    Original Message


  • 9.  RE: Error while publishing a mobile app

    Posted Sun March 09, 2025 05:24 AM

    Hi Dhiraj,

    Our issue was related to the network, but if you're encountering a permission issue, I recommend ensuring that the necessary object structures are granted. Specifically, you should grant access to the MAFAPPDATA object structure for the user you're working with.

    Let me know if you need further assistance.

    Best regards,
    Mostafa



    ------------------------------
    Mostafa Mosaad
    Software Engineer
    Megasoft
    Cairo
    01117275779
    ------------------------------

    Original Message