Maximo

Maximo

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

 View Only

  • 1.  BMXAA8744E - The OSLC query was not parsed

    Posted Thu August 20, 2020 05:07 AM
    I've got a customer who's gone live with Anywhere 7.6.4 but getting issues of timer messages to stop it on previously workorders then just completed. When they go back to search for that workorder and stop the timer it complains that there is an active timer on the previous when that they tried to start.

    Only thing in the logs that i can see is this. Are there any tools whereby I can view the OSLC query that its trying to run or maybe just increase the logging on OSLC?


    BMXAA8744E - The OSLC query was not parsed. Ensure that the query in the HTTP request follows the correct syntax of the OSLC query specification.
    Encountered " "," ", "" at line 1, column 51.
    Was expecting one of:
    " " ...
    <BOOLEAN_OP> ...
    <LITERAL_SUFFIX> ...
    "}" ...
    <LITERAL_SUFFIX> ...

    psdi.util.MXApplicationException: BMXAA8744E - The OSLC query was not parsed. Ensure that the query in the HTTP request follows the correct syntax of the OSLC query specification.
    Encountered " "," ", "" at line 1, column 51.
    Was expecting one of:
    " " ...
    <BOOLEAN_OP> ...
    <LITERAL_SUFFIX> ...
    "}" ...
    <LITERAL_SUFFIX> ...

    at com.ibm.tivoli.maximo.oslc.provider.OslcRequest.setupOslcQuery(OslcRequest.java:567)
    at com.ibm.tivoli.maximo.oslc.provider.OslcRequest.<init>(OslcRequest.java:404)
    at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.initHttpSession(MaximoOslcProviderServlet.java:1102)
    at com.ibm.tivoli.maximo.oslc.provider.MaximoOslcProviderServlet.doGet(MaximoOslcProviderServlet.java:602)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1233)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:782)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:481)
    at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97)
    at psdi.webclient.system.filter.HttpXFrameOptionsFilter.doFilter(HttpXFrameOptionsFilter.java:38)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
    at psdi.webclient.system.filter.MTContextFilter.doFilter(MTContextFilter.java:53)
    at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195)
    at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967)
    at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:87)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:949)
    at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:213)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316)
    at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88)
    at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1833)
    at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175)
    at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
    at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
    at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
    at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
    Caused by: com.ibm.oslc.query.parser.where.ParseException: Encountered " "," ", "" at line 1, column 51.
    Was expecting one of:
    " " ...
    <BOOLEAN_OP> ...
    <LITERAL_SUFFIX> ...
    "}" ...
    <LITERAL_SUFFIX> ...

    at com.ibm.oslc.query.parser.where.OslcWhereParser.generateParseException(OslcWhereParser.java:583)
    at com.ibm.oslc.query.parser.where.OslcWhereParser.jj_consume_token(OslcWhereParser.java:468)
    at com.ibm.oslc.query.parser.where.OslcWhereParser.scoped_term(OslcWhereParser.java:174)
    at com.ibm.oslc.query.parser.where.OslcWhereParser.simple_term(OslcWhereParser.java:89)
    at com.ibm.oslc.query.parser.where.OslcWhereParser.compound_term(OslcWhereParser.java:49)
    at com.ibm.oslc.query.parser.where.OslcWhereParser.where(OslcWhereParser.java:45)
    at com.ibm.tivoli.oslc.OslcQuery.parseOslcWhere(OslcQuery.java:273)
    at com.ibm.tivoli.oslc.OslcQuery.init(OslcQuery.java:175)
    at com.ibm.tivoli.oslc.OslcQuery.<init>(OslcQuery.java:132)
    at com.ibm.tivoli.maximo.oslc.provider.OslcRequest.setupOslcQuery(OslcRequest.java:543)
    ... 36 more

    ------------------------------
    Christopher Kung
    ------------------------------



    #MaximoAnywhere
    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: BMXAA8744E - The OSLC query was not parsed

    Posted Thu August 20, 2020 10:24 AM
    Update

    We think its related to either of these two system properties

    mxe.oslc.restwebappurl
    mxe.oslc.webappurl

    To which we recently switched it to HTTPS instead of HTTP. Seems to have been resolved when we changed it back and got users to reinstall the app

    I can sort of recreate in a TEST environment by providing incorrect URLs in those two system properties, install the app, complete a workorder then start the timer on a new workorder then refresh the Query list again. The Timer icon doesn't show green against the workorder but when I try to stop it, it complains to stop the active timer on the same workorder that I'm clicking on.

    ------------------------------
    Christopher Kung
    ------------------------------

    Original Message


  • 3.  RE: BMXAA8744E - The OSLC query was not parsed

    Posted Mon August 24, 2020 05:39 AM
    still seeing these messages in the logs so not sure what the root cause is yet

    ------------------------------
    Christopher Kung
    ------------------------------

    Original Message


Related Content