Skip to main content

Hi,

One of our customer using Scan It mobile app and once we provide the System URL to the app and enter user credentials we get following error,

{"error":{"code":"ODP_ILLEGAL_STATE","message":"Unable to fulfill the request due to unexpected server state."}}

We have granted WADACO_MOBILE_USER permission set to the user.

 


Appreciate if someone could help us on this.

Thank You,
Hashan

Hi @Technical Toby / @James Ashmore,

Do you have any sort of an idea with this issue?

I have done everything as mentioned in below community post,
How can I use IFS Scan it App in IFS Cloud?

Appreciate if you could help me on this.

Best Regards,
Hashan


Looks like a connectivity issue. Can you reach the Server URL from a browser?


Hi @James Ashmore,

Yes, Server URL accessible from browser. 

from scan it app also it redirects to login page once I enter the credentials I do get this error.


Okay. Any additional information in the client logs?


We have this java lookup error in odata pod, tried restarting the pod as well. but there are no any error records in the log file with the time we try to login.


{"type":"liberty_message","host":"ifsapp-odata-69c8d7cb86-bb7b7","ibm_userDir":"\/opt\/ifs\/wlp\/usr\/","ibm_serverName":"defaultServer","message":"2023-03-23 10:43:29.531 ERROR  500 f2cc9db3-1541-49da-9161-87ac33ab501d com.ifsworld.fnd.provider.processor.FndErrorProcessor.processError() : Error Stack : Error while Custom Java lookup.\ncom.ifsworld.fnd.common.exceptions.ODataProviderIllegalStateException: Error while Custom Java lookup.\n\tat com.ifsworld.fnd.storage.invoker.JavaOperationInvoker.invokeOperation(JavaOperationInvoker.java:130)\n\tat com.ifsworld.fnd.storage.invoker.JavaOperationInvoker.invoke(JavaOperationInvoker.java:84)\n\tat com.ifsworld.fnd.storage.invoker.JavaActionInvoker.invoke(JavaActionInvoker.java:30)\n\tat com.ifsworld.fnd.storage.invoker.BpaInvokerWrapper.invoke(BpaInvokerWrapper.java:166)\n\tat com.ifsworld.fnd.provider.processor.FndActionProcessor.processActionComplex(FndActionProcessor.java:681)\n\tat org.apache.olingo.server.core.ODataDispatcher.handleActionDispatching(ODataDispatcher.java:265)\n\tat org.apache.olingo.server.core.ODataDispatcher.handleResourceDispatching(ODataDispatcher.java:141)\n\tat org.apache.olingo.server.core.ODataDispatcher.dispatch(ODataDispatcher.java:117)\n\tat org.apache.olingo.server.core.ODataHandlerImpl.processInternal(ODataHandlerImpl.java:164)\n\tat org.apache.olingo.server.core.ODataHandlerImpl.process(ODataHandlerImpl.java:85)\n\tat com.ifsworld.fnd.provider.ODataHandlerWrapper.process(ODataHandlerWrapper.java:64)\n\tat com.ifsworld.fnd.provider.ODataHandlerWrapper.process(ODataHandlerWrapper.java:77)\n\tat com.ifsworld.fnd.web.api.FndODataServletBase.serviceODataRequest(FndODataServletBase.java:329)\n\tat com.ifsworld.fnd.web.api.FndODataServletBase.serviceProjectionRequest(FndODataServletBase.java:162)\n\tat com.ifsworld.fnd.web.api.FndODataServletBase.service(FndODataServletBase.java:112)\n\tat javax.servlet.http.HttpServlet.service(HttpServlet.java:791)\n\tat com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1258)\n\tat com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:746)\n\tat com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:443)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:193)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:98)\n\tat com.ifsworld.fnd.web.api.ResponseFilterBase.doFilter(ResponseFilterBase.java:60)\n\tat com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:201)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)\n\tat com.ifsworld.fnd.web.api.InitConfigurationFilterBase.doFilter(InitConfigurationFilterBase.java:201)\n\tat com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:201)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)\n\tat com.ibm.ws.security.jaspi.JaspiServletFilter.doFilter(JaspiServletFilter.java:56)\n\tat com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:201)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:1002)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1140)\n\tat com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1011)\n\tat com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:75)\n\tat com.ibm.ws.webcontainer40.servlet.CacheServletWrapper40.handleRequest(CacheServletWrapper40.java:85)\n\tat com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:938)\n\tat com.ibm.ws.webcontainer.osgi.DynamicVirtualHost$2.run(DynamicVirtualHost.java:281)\n\tat com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink$TaskWrapper.run(HttpDispatcherLink.java:1184)\n\tat com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.wrapHandlerAndExecute(HttpDispatcherLink.java:453)\n\tat com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.ready(HttpDispatcherLink.java:412)\n\tat com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:566)\n\tat com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleNewRequest(HttpInboundLink.java:500)\n\tat com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.processRequest(HttpInboundLink.java:360)\n\tat com.ibm.ws.http.channel.internal.inbound.HttpICLReadCallback.complete(HttpICLReadCallback.java:70)\n\tat com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:504)\n\tat com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:574)\n\tat com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:958)\n\tat com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1047)\n\tat com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:238)\n\tat java.base\/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)\n\tat java.base\/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)\n\tat java.base\/java.lang.Thread.run(Unknown Source)\nCaused by: java.lang.ClassNotFoundException: com.ifsworld.projection.MobileClientRuntimeActionsImpl\n\tat com.ibm.ws.classloading.internal.AppClassLoader.findClassCommonLibraryClassLoaders(AppClassLoader.java:733)\n\tat com.ibm.ws.classloading.internal.AppClassLoader.findClass(AppClassLoader.java:334)\n\tat java.base\/java.lang.ClassLoader.loadClass(Unknown Source)\n\tat com.ibm.ws.classloading.internal.AppClassLoader.findOrDelegateLoadClass(AppClassLoader.java:711)\n\tat com.ibm.ws.classloading.internal.AppClassLoader.loadClass(AppClassLoader.java:611)\n\tat java.base\/java.lang.ClassLoader.loadClass(Unknown Source)\n\tat java.base\/java.lang.Class.forName0(Native Method)\n\tat java.base\/java.lang.Class.forName(Unknown Source)\n\tat com.ifsworld.fnd.storage.invoker.JavaOperationInvoker.invokeOperation(JavaOperationInvoker.java:116)\n\t... 51 more","ibm_threadId":"000001f4","ibm_datetime":"2023-03-23T10:43:29.532+0000","module":"SystemErr","loglevel":"SystemErr","ibm_methodName":"","ibm_className":"","ibm_sequence":"1679568209532_00000000012CC","ext_requestID":"AAB4E4tD6Wk_AAAAAAAAImf","ext_thread":"Default Executor-thread-398"}

 


Odd. Suggest you raise a support case to get some additional support with this

Cheers

James


I was going to do the same, Thank you James 

Cheers,
Hashan


Hi

This is an environment issue. What’s the exact version and SU level? Has this environment upgraded recently? Looks to me as DB deployment has not performed correctly where Native side Java IMPL are missing or a issue in ODP. Also try to re start ODP and take full logs. 


Hi

This is an environment issue. What’s the exact version and SU level? Has this environment upgraded recently? Looks to me as DB deployment has not performed correctly where Native side Java IMPL are missing or a issue in ODP. Also try to re start ODP and take full logs. 

IFS Cloud 22R2 SU4
App version: 23.3.820.0
recently upgraded from APP9

we have restarted the Odata pod and as mentioned above java lookup error is there in Odata pod. But its not occured in a time we try to login.

Could you please let me know where exactly I could check  Native side java IMPL in DB?


Can you please send the Odata POD logs showing Java IMPL download history. We have native java libraries stored in the database. Could be they are missing? Did you see any warnings in the DB deployment side? 


Can you please send the Odata POD logs showing Java IMPL download history. We have native java libraries stored in the database. Could be they are missing? Did you see any warnings in the DB deployment side? 

Hi Kapila,

we couldnt see any warnings from DB deployment side.

Herewith I have attached connect, odata and native-server pods log files.

we could find some timeout errors in native-server log

Regards,
Hashan

 


If you run the below SQL, Do you see two records? 

SELECT * FROM fnd_java_implementations_tab WHERE MODULE = 'FNDMOB'


If you run the below SQL, Do you see two records? 

SELECT * FROM fnd_java_implementations_tab WHERE MODULE = 'FNDMOB'

No return values

this could be the issue then

 


Yes, you have got an issue in the environment / delivery or upgrade process. Do you know how the server upgrade went? did all other areas are working fine? With this all mobile apps should stop working as key API is missing.

Let’s try to analyse the environment and the process you followed. may be you will need a support ticket to het help from platforms team or delivery team 


Yes, you have got an issue in the environment / delivery or upgrade process. Do you know how the server upgrade went? did all other areas working fine? 

Hi Kapila,

As per your input we were able to narrow down the issue a bit.

We checked the build home and found out MobileAttachments.jar and MobileClientRuntime.jar are not available in following paths of the build home.


MobileAttachments.jar | path => buil_home/server/lob/fndmob/javaimpl/MobileAttachments
MobileClientRuntime.jar | path => buil_home/server/lob/fndmob/javaimpl/MobileClientRuntime

simply FNDMOB folder is not there under the following path,
buil_home/server/lob/

I downloaded the build_home again from build place and files are not available in newly downloaded build_home as well.

Customer recently upgraded to 22R2 from IFSAPP9

FNDMOB enabled in solution set.


Did you try to re build the environment/ may be clean build. if those files are not available means module has not been compiled. 


Did you try to re build the environment/ may be clean build. if those files are not available means module has not been compiled. 

Hi Kapila,

Yes, We have to try re-build and see. Will keep you update.

 


Reply