With ODM 8.6 zRES with file system persistence get below error message when deploying with Ant:
[res-deploy] [ERROR] com.ibm.rules.res.tools.ant.xom.DeployManagedXOMException: The XOM repository service could not retrieve information about file: JAVA_XOM_NAME.jar
Or this exception when deploying from the management console:
ilog.rules.res.model.IlrRepositoryException: Could not get information from the XOM DAO.
at ilog.rules.res.console.util.IlrManagementActions.isXOMResourceAvailable(IlrManagementActions.java:1019)
at ilog.rules.res.console.service.IlrRepositoryServiceImpl.isXOMResourceAvailable(IlrRepositoryServiceImpl.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at ilog.rules.res.console.servlet.IlrRepositoryServiceServlet.doPost(IlrRepositoryServiceServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:440)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:943)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:756)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.NullPointerException
at com.ibm.rules.res.persistence.internal.file.FileXOMRepositoryDAO.getResourcesWithName(FileXOMRepositoryDAO.java:407)
at com.ibm.rules.res.persistence.internal.file.FileXOMRepositoryDAO.isAvailable(FileXOMRepositoryDAO.java:264)
at ilog.rules.res.console.util.IlrManagementActions.isXOMResourceAvailable(IlrManagementActions.java:1017)
... 23 more
The ++HBRWORKPATH++/res_xom directory contains empty jar file, JAVA_XOM_NAME.jar with size 0, without corresponding sha1 file (JAVA_XOM_NAME.jar.sha1)
Answer by odmgd (10516) | Dec 09, 2015 at 09:40 AM
The short term solution to solve the problem is to delete the empty jar files and restart the server.
The long term solution, because such problem is likely to be the consequence of space availability issue of the ++HBRWORKPATH++ file system, is to create a dedicated file system for ++HBRWORKPATH++/res_xom and ++HBRWORKPATH++/res_data.
Rule execution server vs. RES database availability 1 Answer
Installing WebSphere Operational Decision Management V7.5 using DVDs 1 Answer
How to rename a package name without loosing all references in that package? 1 Answer
Collection of complex types in DVS output 1 Answer
RES console on z/OS: No execution unit (XU) connected to this server through TCP/IP 1 Answer