kodo.util.UnsupportedOptionException

kodo.jdbc.SQL language queries cannot be executed in-memory. Either set the javax.jdo.option.IgnoreCache property to true, set the kodo.FlushBeforeQueries property to true, or execute the query before modifying objects within the transaction.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Unknown by 3004,
  • via Unknown by 3004,
  • Stack trace

    • kodo.util.UnsupportedOptionException: kodo.jdbc.SQL language queries cannot be executed in-memory. Either set the javax.jdo.option.IgnoreCache property to true, set the kodo.FlushBeforeQueries property to true, or execute the query before modifying objects within the transaction. at kodo.jdbc.query.SQLQuery.newInMemoryQueryExecutor(SQLQuery.java:117) at kodo.query.AbstractQuery.internalCompile(AbstractQuery.java:545) at kodo.query.AbstractQuery.getAccessPathMetaDatas(AbstractQuery.java:938) at kodo.query.AbstractQuery.isAccessPathDirty(AbstractQuery.java:745) at kodo.query.AbstractQuery.executeWithMap(AbstractQuery.java:672) at kodo.query.AbstractQuery.executeWithArray(AbstractQuery.java:640) at kodo.query.AbstractQuery.execute(AbstractQuery.java:622) at com.metasolv.resources.queries.ChannelAvailabilityQueryBean.execute(ChannelAvailabilityQueryBean.java:84) at com.metasolv.oss.inventory.InventorySessionBean.queryInventory(InventorySessionBean.java:1504)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.