'Content IO Channel was opened but not closed'prevents start

curious_george — Fri, 04 Apr 2008 03:11:16 GMT

Hello,I just upgraded one of our environments from Alfresco 1.4 to Alfresco 2.1, running on Oracle 10G, Linux, and JBoss 4.2.2. I cannot start Alfresco now due to a "Content IO Channel was opened but not closed" error.On the initial upgrade, I received an error about requiring an X11 session. I had

Re: 'Content IO Channel was opened but not closed'prevents start

curious_george — Mon, 07 Apr 2008 17:43:00 GMT

I've fortunately solved the issue. I'm still getting the "Content IO Channel was opened but not closed" error in my JBoss server.log file, but it is no longer showing up in the web application.

There were two issues:
1) I was in the middle of an upgrade. This test environment took 5+ hours to completely upgrade (moving from 1.4 to 2.1). I mistakenly thought it was stuck in an infinite loop or frozen (especially because I couldn't access the JBoss jmx-console at the time). I let it run for several hours, the patching completed, and all was mostly well. Surprisingly, a copy of our production data (which is just as big as our test data) did not take anywhere near as long to upgrade.

2) I set my broadcast mask and domain correctly in the file-servers.xml file. In my opinion, this did not have anything directly to do with the resolution of the problem - but it sure didn't hurt to fix it.

Hope this helps others.

topic 'Content IO Channel was opened but not closed'prevents start in Alfresco Archive

'Content IO Channel was opened but not closed'prevents start

Re: 'Content IO Channel was opened but not closed'prevents start