Chat not available

[15年前 に paul a adams によって更新されました。]

I logged into our SO and there were 2 updates that it asked to install. I did them and now the chat has not been available. How can i check to see what updates were done and how to repair the chat feature.

[15年前 に Jon Goldberg によって更新されました。]

I am having the same problem. I have installed the older version via the plugin under my profile (as admin user) and I get the same error. In the catalina.out file I am getting a large dump whenever any page is hit with chat on it. Here is the log. I tried to google this but I don't think many people have seen this yet. Thanks in advance for any help.

18:07:50,816 ERROR [[jsp]:711] Servlet.service() for servlet jsp threw exception
org.apache.jasper.JasperException: /view.jsp(33,1) No tag "html-top" defined in tag library imported with prefix "liferay-util"
at org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
at org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
at org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:198)
at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1329)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1589)
at org.apache.jasper.compiler.Parser.parseBody(Parser.java:1818)
at org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1081)
at org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1389)
at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1589)
at org.apache.jasper.compiler.Parser.parse(Parser.java:132)
at org.apache.jasper.compiler.ParserController.doParse(ParserController.java:212)
at org.apache.jasper.compiler.ParserController.parse(ParserController.java:101)
at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:156)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:296)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:277)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:265)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:302)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:329)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:679)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:584)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:497)
at com.liferay.portlet.PortletRequestDispatcherImpl.dispatch(PortletRequestDispatcherImpl.java:302)
at com.liferay.portlet.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:107)
at com.liferay.util.bridges.jsp.JSPPortlet.include(JSPPortlet.java:194)
at com.liferay.util.bridges.jsp.JSPPortlet.include(JSPPortlet.java:178)
at com.liferay.util.bridges.jsp.JSPPortlet.doView(JSPPortlet.java:140)
at com.liferay.portal.kernel.portlet.LiferayPortlet.doDispatch(LiferayPortlet.java:119)
...

I am running on Fedora Core 10, using JRE 1.6.0. The jre's I have used are:

export JAVA_HOME=/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/
AND
export JAVA_HOME=/usr/lib/jvm/jre-1.6.0/

The is the log on startup if that helps.

Mar 2, 2009 6:06:58 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
Mar 2, 2009 6:06:58 PM org.apache.coyote.http11.Http11BaseProtocol init
Mar 2, 2009 6:06:58 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1076 ms
Mar 2, 2009 6:06:58 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Mar 2, 2009 6:06:58 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.27
Mar 2, 2009 6:06:58 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Mar 2, 2009 6:06:59 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:06:59 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:00 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:01 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:01 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:02 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:03 PM org.apache.catalina.core.StandardWrapper unload
INFO: Waiting for 6 instance(s) to be deallocated
Mar 2, 2009 6:07:04 PM org.apache.coyote.http11.Http11BaseProtocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Mar 2, 2009 6:07:04 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: Failed shutdown of Apache Portable Runtime
Mar 2, 2009 6:07:47 PM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Mar 2, 2009 6:07:47 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Mar 2, 2009 6:07:47 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/53 config=null
Mar 2, 2009 6:07:47 PM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Mar 2, 2009 6:07:47 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 49223 ms

[15年前 に Channing K Jackson によって更新されました。]

It looks like the update that was downloaded was the 5.2.X version of the chat-portlet. The liferay-util taglib for 5.2.X does indeed have a "html-top" tag defined in the TLD file, but it does not exist in the 5.1.X tag library definition.

I *think* you can probably just replace the view.jsp with the version that originally came with the SO distribution and it should resolve the issue. However, if there is other chat-portlet code that is dependent on 5.2.X code base, the dependencies could go deeper.

My opinion is that this identifies an issue with the automatic update capabilities. The update manager is not distinguishing that you are running a version of SO and chat-portlet that is not compatible with 5.2.X code base.

[15年前 に Channing K Jackson によって更新されました。]

After more research...

It looks like all the JSPs were updated in the update download, so you'll probably need to replace *.jsp with the original distribution.

• buddies.jsp
• css.jsp
• css_init.jsp
• init.jsp
• json_init.jsp
• lateset.jsp
• send.jsp
• view.jsp

The ~/liferay/temp/5-chat-portlet directory will be holding "cached" versions of the JSP files for that portlet. Copy all the original JSPs into this directory as well, so Liferay will not keep dumping tons of stack traces to the log.

[15年前 に Jon Goldberg によって更新されました。]

Channing,

Thanks you had the part I need to get it out of the tomcat cache. The other way to fix this is to go to the control panel, then to the plugins and search for the chat portlet. Once you do that install the older version. Once you do that then delete the cache in the VM in that directory chat starts to work. Not sure why the upgraded version doesn't work in social office. But the old version works once you clear the cache.

Thanks,

Jon

[15年前 に Bryan Cheung によって更新されました。]

Thanks all, filed as a bug on JIRA:

http://issues.liferay.com/browse/SOS-70

[15年前 に Josh Asbury によって更新されました。]

I ran into this today. It is a result of LPS-2277's change in javascript.js. Simply revert back to revision 26453. I assume that if the rest of the code base has been updated to the latest branch revision that this wouldn't occur.

[15年前 に paul a adams によって更新されました。]

Thanks to all I just copied the files in and then told SO to ignore the update.