Portal + Hibernate + Oracle 9i, /nodetypes/custom_nodetypes.xml null pointer issue ---------------------------------------------------------------------------------- Key: JBPORTAL-883 URL: http://jira.jboss.com/jira/browse/JBPORTAL-883 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal CMS Affects Versions: 2.2.1 Final Environment: Portal 2.2.1 bundle, Oracle 9i (driver 9.2.0.4), Win2k server Reporter: David Nebinger Assigned To: Roy Russo This is related to the JBPORTAL-816 defect reported but erroneously closed because it could not be duplicated. The bug is still out there, and it is related to the columns generated in the jbp_cms_repositoryentry table. Basically when the portal is first set up, it creates the columns using the hibernate schema tools. The generated table has a blob in the FSENTRY_DATA column. As long as you do not cycle jboss, the portal/cms system works just fine. But after jboss restart, the null pointer exception related to the loading of the /nodetypes/custom_nodetypes.xml file (represented in a row from the table) fails, resulting in the CMS service not coming up and the portal is totally unusable. See 816 for the stack trace indicating the source of the cascading failures in the code. As oracle/hibernate have a history of not functioning well using blobs, this really came as no surprise once I figured out what was going on. And since hibernate does not treat this as a bug, it probably won't be considered a bug for the portal either. :-( However, should someone care to work with me on testing a resolution, feel free to contact me about it.