03-11-2009 11:17 AM
LMS 3.0.1
LMS Portal 1.0.1
CiscoWorks Assistant
CiscoView 6.1.7
CiscoWorks Common Services 3.1.1
Integration Utility 1.7.1
Resource Manager Essentials 4.1.1
Campus Manager 5.0.2
from time to time I observe that LMS Portal > RME > Home does not open _OR_ take extremely long time to open. The same can be observed for the RME Job Management, LMS Portal > RME > Job Management > RME Jobs (http://LMS-server:1741/rme/JobMgmtAction.do)
I think it could be related as information from RME Jobs are used in the RME Homepage. I found the following errors in stdout.log from tomcat which is in the timeline related to a session which had this problem (LMSuser_1):
[...]
Exceuting Callable Statement
Mar 11, 2009 10:19:36 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:518)
at org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
at org.apache.coyote.Response.action(Response.java:182)
at org.apache.coyote.Response.finish(Response.java:304)
at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:754)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:684)
at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:876)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Mar 11, 2009 10:19:36 AM org.apache.jk.common.ChannelSocket processConnection
WARNING: processCallbacks status 2
[...]
[Wed Mar 11 10:29:39 MET 2009] The User LMSuser_1 is not allowed[Ljava.lang.String;@67a974
Time taken:503ms
Mar 11, 2009 10:29:40 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
[...]
Local User Setup is used.
LMSuser_1 has the user roles helpdesk, network operator, network administrator
LMSuser_2 has every user role except approver
both should be able to open the page; when LMSuser_1 did it for the first time he got the message he is not allowed to view the page (something in that sense); this message was only seen once;
then LMSuser_1 logged out and LMSuser_2 logged in from the same client. He neither could open the page.
In the log file I found that the JSESSIONID=EBA351021A6E52FB7F4E3C616E50F2A2 from LMSuser_1 was re-used but I do not know if that is correct.
Usually the dmgtd will be restarted but I want to know what the reason is for this behaviour. Does anybody have a clue?
03-11-2009 11:19 AM
03-12-2009 12:19 PM
has someone else seen this behaviour before?
03-14-2009 03:58 AM
at least anybody who finds the same java error in the tomcat stdout.log?
03-14-2009 11:39 PM
Sorry, I missed this. These Broken pipe errors are cosmetic, and a known bug in Tomcat 5. When LMS moves to Tomcat 6 (after LMS 3.2), these errors will go away. A Cisco bug was filed to track this (CSCsg63918), but it was closed pending the Tomcat upgrade.
I don't see anything in this log that would explain why you're getting an authorization error. My guess is that a session is expiring, or there is an external authorization issue. The log is incomplete, though, and does not start from Tomcat's initialization.
03-18-2009 12:55 PM
thanks! I will try and get the complete Tomcat log from a backup because meanwhile dmgtd was restarted ...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: