I've been running Joget for over a month and it's been working fine. Today when I tried uploading my latest Workflow version I got an error.... i tried restarting Joget a couple times, and I'm always getting this error msg --> Problem while initializing caches. Suggestions?
...
2011-08-30 21:50:14,125: Problem while initializing caches !!!
java.lang.NullPointerException
at org.enhydra.shark.repositorypersistence.DODSRepositoryPersistenceManager.getXPDL(DODSRepositoryPersistenceManager.java:296)
at org.enhydra.shark.SharkUtilities.restorePackage(SharkUtilities.java:1468)
at org.enhydra.shark.SharkUtilities.synchronizeXPDLCache(SharkUtilities.java:1418)
at org.enhydra.shark.SharkUtilities.restorePackages(SharkUtilities.java:1450)
at org.enhydra.shark.SharkEngineManager.initCaches(SharkEngineManager.java:978)
at org.enhydra.shark.SharkEngineManager.init(SharkEngineManager.java:874)
at org.enhydra.shark.SharkEngineManager.configure(SharkEngineManager.java:535)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
...
5 Comments
Paul
I also can't see the workflow anymore in the Joget Console. If I try to upload the XPDL I get this error 'java.lang.Exception: The package with id **************_pkg is already open'.
When I try to update the package with the workflow designer I get this error:
org.enhydra.shark.api.internal.repositorypersistence.RepositoryException No xpdl ??(***************_pkg, 103) in repository
Anyone have a suggestion? It seems like my workflow is corrupted somehow............
Paul
Below is the line that's failing when I start the Joget server.... looks like an issue with my XPDL... this error started when I was uploading a new version of my XPDL. Could something be corrupted in the database or with my XPDL? How can I clear this?
2011-08-30 22:45:08,718: SharkUtilities -> synchronizing XPDL cache
2011-08-30 22:45:10,625: Problem while initializing caches !!!
java.lang.NullPointerException
at org.enhydra.shark.repositorypersistence.DODSRepositoryPersistenceManager.getXPDL(DODSRepositoryPersistenceManager.java:296)
2011-08-30 22:45:08,718: SharkUtilities -> synchronizing XPDL cache
Paul
Nvm. Figured it out. Somehow when I deployed the last workflow the database got out of sync. The table 'shkxpdls' had a record for the latest workflow version, but it was missing from 'shkxpdldata'. So I deleted the record from table 'shkxpdls' and everything now works fine. Seems like when I updated the last workflow the changes were committed to the 'shkxpdls' table but not the 'shkxpdldata' table. Is this a small bug? Perhaps both inserts should be committed at the same time.
Paul
Root cause turned out to be the MySql option 'max_packet_size' needed to be increased. I set it to 32M and that seemed to fix the update issue.
Aristo
I also have the same problem. But I'm using Oracle for the database.