Either when using WebSphere Service Registry and Repository (WSRR) Studio or creating classification systems by hand it is possible to create a circular hierarchy, For example: Class A is a sub-class of Class B and Class B is a sub-class of Class A. This is not a valid classification system. However this classification system will load into WSRR without complaint. This then causes the symptoms below. Moreover it is then impossible to activate another WSRR profile.
The following is seen in the SystemOut.log when attempting to view the offending classification system in the Configuration perspective of the WebUI:
Loop of: com.ibm.sr.ui.util.TreeViewBuilder.createTreeNode(TreeViewBuilder.java:809)
and when attempting to delete this classification system or activate another WSRR profile:
com.ibm.ejs.container.UnknownLocalException: nested exception is: com.ibm.ws.exception.WsEJBException: nested exception is: java.lang.StackOverflowErrorcom.ibm.ws.exception.WsEJBException: nested exception is: java.lang.StackOverflowError
Loop of: com.ibm.athene.owl.impl.ReadWriteSession.retractClassesFromCache(ReadWriteSession.java:379)
Resolving the problem
If you cannot activate a WSRR profile due to a circular classification system, contact WSRR Support for further help.