We have been noticing lately that opening content types in Workbench have become a big big torture.
We can do the work normally in content explorer but cannot open the content types in workbench.
Has anyone experienced similar kind of problem?
thanks
Manvinder
What does “big torture” mean specifically?
Do you have any errors in the server.log when you log into the WB?
Do you have any errors in the server.log when you attempt to open a CT?
Have you tried opening up the WB using the console?
If not, create a shortcut of the RhythmyxWorkbench.exe, right click properties, add " -is:javaconsole" to the end of the target field, open the WB with the new shortcut.
When you open the WB with the console, do you notice any errors in the console? What about when you attempt to open a CT?
On the server side, I see the following exception being thrown up:
java.io.IOException: javax.xml.transform.TransformerException: ClientAbortException: java.net.SocketException: Connection timed out
at com.percussion.xml.PSXmlTreeWalker.write(Unknown Source)
at com.percussion.xml.PSXmlDocumentBuilder.write(Unknown Source)
at com.percussion.server.PSResponse.send(Unknown Source)
at com.percussion.servlets.PSAppServlet.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.percussion.webdav.PSWebDavRequestFilter.doFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.percussion.servlets.PSSecurityFilter.doFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at com.percussion.servlets.PSCharacterSetFilter.doFilter(Unknown Source)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Unknown Source)
I dont see any error logs on the client side Java console for the work bench. The only log that I see on the Java console is:
Reading certificates from 435412 http://xxxxxx Rhythmyx/sys_resources/AppletJars/rxcx.jar | C:\Documents and Settings\msingh\Application Data\Sun\Java\Deployment\cache\6.0\31\3026c59f-23d80645.idx
Reading certificates from 435412 http://xxxxx Rhythmyx/sys_resources/AppletJars/rxcx.jar | C:\Documents and Settings\msingh\Application Data\Sun\Java\Deployment\cache\6.0\31\3026c59f-23d80645.idx
Also the problem does not happens in connection of the workbench to Rhythmyx server. The problem starts happening on attempting to open a content type.
thanks
Manvinder
Also another kind of error that I frequently see on the server side log is:
2010-03-25 13:00:28,260 ERROR [com.percussion.AgentMgr] An unexpected exception occurred. The reason was: An exception occurred while processing the internal request handler call: java.lang.RuntimeException: No rows returned in result set for fieldset ‘CT_gsaLink’… Please consult the log for further information.
Can these kind of errors contribute to the problem that we are having?
thanks
Manvinder
Errors with custom code, plugins, exits or queries can definitely negatively impact WB performance. I recommend finding the query that’s failing and fix it.
Also, did you try running the WB with the console window? Did you see anything new in there?
What do you mean by finding the query that is failing? Also how do we find the query that is failing and remove it?
manvinder
The error you posted, “No rows returned in result set for fieldset ‘CT_gsaLink’…” clearly states that you have a query somewhere that is returning no results where results are expected. There is no out of the box content type named gsaLink…, so that must be something you have created on your own. Since this is something specific to your implementation, it’s not going to be possible for me to tell you exactly where to look.
I recommend that you check further up in the log to what occurred before this error. If you’re attempting to publish something, start by checking out the content lists in the Edition that was started. Once you’ve identified the edition, try to narrow the scope by removing content lists and attempting to reproduce the behavior. Once you’ve identified the offending content list, simplifying your query to figure out what content type is generating the error and so on until you find the specific cause.