[10/6/20 12:03:10:188 CDT] 0000015c WPSWCMService E Failed to initalise Repository
javax.jcr.RepositoryException: RT7508E: Unable to initialize RepositoryFactory due to exception of type: java.lang.NullPointerException with message: null.
at com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:302)
at com.ibm.icm.jcr.RepositoryFactory.getRepository(RepositoryFactory.java:528)
[snip]
Caused by: java.lang.NullPointerException
at java.io.File.<init>(File.java:288)
at com.ibm.icm.ci.data.impl.binary.cache.BinaryCacheConfig.<init>(BinaryCacheConfig.java:86)
at com.ibm.icm.jcr.RepositoryImpl.getRepository(RepositoryImpl.java:293)
at com.ibm.icm.jcr.RepositoryImpl.getRepository(RepositoryImpl.java:234)
Running OSGIInit and Clearing /opt/IBM/WebSphere/AppServer/profiles/wp_profile/PortalServer/jcr/binaryValues Doesn't resolve the issue.
Any help is appreciated
Are there ay other exceptions prior to this in the log during startup? Can you verify your JCR database connection? Unfortunately that RT5708E is very generic and I've seen it related to wimconfig issues, datasource issues as well as the database not being reachable.
test Connections was the first thing tried. All Good.
Sister Portal server is using the same connections and DB's. No problem.
Hi Richard,
Check your jcr config for the parameter jcr.binaryValueFileDir.
From your WAS console, click Resources > Resource Environment > Resource Environment Providers > JCR ConfigService PortalContent > Custom properties.
Make sure the location that is specified under jcr.binaryValueFileDir has sufficient disk space.
Also if you have a cluster, verify that the jcr.binaryValueFileDir value is unique within the HCL Portal node where the server is located.
Refer step 9. d. in the following for this:
https://help.hcltechsw.com/digital-experience/8.5/install/add_vert_clus.html
A case was opened with support, and we used this suggestion to resolve the issue.
Agree with Billy and Anushree. RT7508E is a very generic error message, you can also try deleting the jcr binary cache directory, restart the server. This may help resolve the issue if the cache is corrupt.