Amos Fong:
I think something is slipping through the friendly url normalizer and it's producing duplicate friendly URLs.
What are you naming your organizations?
I think I see what happened. The names are fine. But it looks like the record is partially there from an earlier failed attempt to create the organization when Liferay experienced a lost DB connection error. (Haven't completely solved that problem yet, but that's a different story).
Anyway, I perused the source code and the DB and found the issue. The friendly URL is already in the lportal. Group_ table, but apparently needs a corresponding Organization_ entry (which is what failed to insert previously). Since the Org entry is not there it does not show up in the Control Panel or generated a duplicate error. But then it checks to see if the Group_ is there and fails. The error message is somewhat inaccurate since the URL isn't really failing a validation - we never get that far.
Of course, now the problem is how to fix this. I tried removing the Group_ and corresponding LayoutSet table rows, but that doesn't seem to be enough as I now get this exception when trying to access the Organizations control panel:
[#|2009-04-22T20:16:17.304+0000|INFO|glassfish|null|_ThreadID=17;_ThreadName=Thread-3;|2009-04-22 20:16:17,291 [httpWorkerThread-8080-1] ERROR com.liferay.portal.model.Organization -
com.liferay.portal.NoSuchGroupException: No Group exists with the key {companyId=10108, classNameId=10017, classPK=10206}
at com.liferay.portal.service.persistence.GroupPersistenceImpl.findByC_C_C(GroupPersistenceImpl.java:656)
at sun.reflect.GeneratedMethodAccessor341.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
Any new thoughts?
