How is III.3.3?

How many people are using version 3.3.3, and have you had many problems with it so far? We are being advised to upgrade to it, and I want to see what land mines might be out there.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

It's not terrible. :)

But you may want to go straight to III.3.3p16 which was just announced. It fixes an annoying bug that altered the look of TargetedContent channels.

We have seen some issues with CPIP connectors timing out to SSB and INB, but we aren't certain if they are III.3.3 related or application server related.

One gotcha that we are experiencing that SCT is stumped over...

Our upgrade to III.3.3 went smoothly. I had altered nested-tables.xsl to hide a few of the icons based on roll. SCT provided a Java method for this. Since I implemented that method, I get the following error within the cp.log file. This has SCT stumped at the moment.
[2006-09-03 00:35:17,319] [ERROR] WebServlet [uportal]: **** CustomIconEvaluator : failed to evaluate cpicons
[2006-09-03 00:35:17,319] [ERROR] WebServlet [uportal]: failed to construct channel cache key
java.lang.IllegalStateException: cThreadedCpInfo.get() == null
at campuspipeline.uportal.dlm.provider.ExtensionClass.getCpInfo(ExtensionClass.java:44)
at campuspipeline.uportal.dlm.provider.ExtensionClass.getLDAPAttributes(ExtensionClass.java:79)
at com.sungardhe.cpicons.CustomIconEvaluator.evaluate(Unknown Source)
at org.jasig.portal.channels.cpicons.Channel.generateKey(Channel.java:98)
at campuspipeline.uportal.ScheduledChannelRenderer$ScheduledWorker.setCharacterCache(ScheduledChannelRenderer.java:1051)
at campuspipeline.uportal.ScheduledChannelRenderer$ScheduledWorker.access$6(ScheduledChannelRenderer.java:1039)
at campuspipeline.uportal.ScheduledChannelRenderer.setCharacterCache(ScheduledChannelRenderer.java:677)
at org.jasig.portal.ChannelManager.outputChannel(ChannelManager.java:507)
at org.jasig.portal.UserInstance.renderState(UserInstance.java:662)
at org.jasig.portal.UserInstance.writeContent(UserInstance.java:299)
at org.jasig.portal.PortalSessionManager.doGet(PortalSessionManager.java:282)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at com.pipeline.uportal.CpPortalSessionManager.service(CpPortalSessionManager.java:150)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.iplanet.server.http.servlet.NSServletRunner.invokeServletService(NSServletRunner.java:943)
at com.iplanet.server.http.servlet.WebApplication.service(WebApplication.java:1094)
at com.iplanet.server.http.servlet.NSServletRunner.ServiceWebApp(NSServletRunner.java:1005)

This is just about the only gotcha we've encountered.

Same error

We are getting the same error. It doesn't seem to effect the end-user but it does clutter up the log files. Are you on 3.3.3p16?

--
David McMillan

be prepared

If you are using "Automatic Enhanced Account Creation", 3.3.3 requres a new version of the AEAC jar file that is not automatically installed, even when SCT does the install! When we went to 3.3.3 in July, we lost LDI account creation/updates for the better part of two days until SCT figured out what the problem was.

I think we reported a lot of the known bugs. It's almost like we were a beta tester for the product.

We haven't yet applied the recently released patch, but plan to do so in the near future.

Eileen

Syndicate content