I see null topics too. You can enter that area but the titles of the posts are null too. There is a box in the bottom right full of java errors.

It would be easier if you could provide link reference for quicker verification. When clicking on your profile it give following as last two of your posts:
- 2007.01.23 13:07 (this one)
- 2007.01.16 09:56 (first one before)

I'm not sure when you noticed that, but this morning I was unable to login to forums and there was some issue with database which got resolved later. Later that was confirmed by some other people too. It could be related (unless your issue has beeb around for few days now).

Here is some of the messages that show up ....


An error in the system has occurred. Please contact the system administrator if the problem persists.

type: java.lang.NullPointerException


java.lang.NullPointerException
at jsp_servlet.__category._jspService(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V(Optimized Method)
at weblogic.servlet.jsp.JspBase.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(Optimized Method)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava/lang/Object;(Optimized Method)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl;)V(Optimized Method)
at weblogic.servlet.internal.TailFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(Optimized Method)
at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(Optimized Method)
at com.jivesoftware.util.SetResponseCharacterEncodingFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(Optimized Method)
at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(Optimized Method)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(Optimized Method)
at weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(Optimized Method)
at com.jivesoftware.util.SetRequestCharacterEncodingFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V(Optimized Method)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V(Optimized Method)
at com.opensymphony.webwork.dispatcher.ServletDispatcherResult.doExecute(Ljava/lang/String;Lcom/opensymphony/xwork/ActionInvocation;)V(Optimized Method)
at com.opensymphony.webwork.dispatcher.WebWorkResultSupport.execute(Lcom/opensymphony/xwork/ActionInvocation;)V(Optimized Method)

etc etc etc ....

This looks like a permanent enhancement. I even completely left and came back and it's still there. Refreshed the screens, still there. There are only two areas affected, ironically they are the Control Center and Solutions Enabler forums.

sysmgr,

Is this something you see fixed to certain thread or is one of those things which disappears after reload of page?

If you actually go into the posts, the errors show up too.

Now I see what you mean. "Other Resource Management Software", "Other Host Software", "Mainframe" and "EMC Smarts" forums are affected too.

Please add the Smarts forum to the list of enhanced java functionality now. IE It is really broke at this time. Please notify the developers that a production system is not where they do their work....

Bob Teeter

Thanks for the notices. We are aware and working on this issue.

I'll update you when we have resolved it.

Thanks,
Erich

Hi all,

after an emergency bounce of the application, things appear to have returned to normal.

Please let us know if you see anything else odd, and thanks for your patience today.

Erich

Thanks Erich,
It seems to be operating correctly now.

The problem was resolved with an application bounce. Our team is looking into the root cause to mitigate further occurrences.