search

hoangduit / openmeetings

Automatically exported from code.google.com/p/openmeetings
0 stars 0 forks source link

Stability problem after several hours the Hibernate-Session seems to be broken or throws Strange Errors Was: Not see initial screen on r2036 #744

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Which version of OpenMeetings are you running?

r2036

In case its an UI Bug => Images say more then words! Please attach a
Screen-Shot.

What's your operating system on client and server side?

Test in windows xp, Linux Ubuntu and Mac OS X 10.5.7

Is it a problem related to the client/usability or server-side?

Server Side

Did you have any trace/debug output?
To get the debug output of the client run the software in debug-modus
Debug modus of the client:
http://$RED5-HOME:$RED5-HTTPPORT/xmlcrm/maindebug.lzx.lzr=swf8.swf

for example for your local copy:
http://localhost:5080/xmlcrm/maindebug.lzx.lzr=swf8.swf

or see live example:
http://inno02.fh-pforzheim.de:8080/xmlcrm/maindebug.lzx.lzr=swf8.swf

Server side loging:
browser your Red5-Home directory. There's a log-file directory. On linux
boxes you can run red5 using:
nohup ./red5.sh &
and debug output will be written to nohup.out

please attach any debug output to get a patch on time

After some user the server refuse to open the main window and the message
apper in console.

DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - class
attrCount: 1
DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - attr len: 2
DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - class
attrCount incremented

The login window apper in blank.

Original issue reported on code.google.com by kleytonn@gmail.com on 26 May 2009 at 9:04

Attachments:

GoogleCodeExporter commented 9 years ago 
I think the Exception is:
ERROR 05-27 09:31:49.809 Sessionmanagement.java 74586119 145
org.openmeetings.app.data.basic.Sessionmanagement [http-8088-exec-4] - 
[checkSession]: 
java.lang.ClassCastException: java.lang.String cannot be cast to 
java.lang.Boolean
    at org.hibernate.type.BooleanType.set(BooleanType.java:59) [hibernate3.jar:na]
    at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:154)
[hibernate3.jar:na]
    at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:131)
[hibernate3.jar:na]
    at
org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityP
ersister.java:2025)
[hibernate3.jar:na]
    at
org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPers
ister.java:2271)
[hibernate3.jar:na]
    at
org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPers
ister.java:2688)
[hibernate3.jar:na]
    at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:79)
[hibernate3.jar:na]
    at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279) [hibernate3.jar:na]
    at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
[hibernate3.jar:na]
    at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:167)
[hibernate3.jar:na]
    at
org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(Abstract
FlushingEventListener.java:321)
[hibernate3.jar:na]
    at
org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListe
ner.java:50)
[hibernate3.jar:na]
    at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027) [hibernate3.jar:na]
    at
org.openmeetings.app.data.basic.Sessionmanagement.checkSession(Sessionmanagement
.java:119)
[openmeetings.jar:na]
    at org.openmeetings.app.remote.UserService.refreshSession(UserService.java:99)
[openmeetings.jar:na]
    at sun.reflect.GeneratedMethodAccessor490.invoke(Unknown Source) [na:na]
    at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
[na:1.6.0_13]
    at java.lang.reflect.Method.invoke(Method.java:597) [na:1.6.0_13]
    at org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:200) [red5.jar:na]
    at org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:118) [red5.jar:na]
    at org.red5.server.net.rtmp.RTMPHandler.invokeCall(RTMPHandler.java:152) [red5.jar:na]
    at org.red5.server.net.rtmp.RTMPHandler.onInvoke(RTMPHandler.java:392) [red5.jar:na]
    at
org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler.java:14
6)
[red5.jar:na]
    at org.red5.server.net.rtmpt.RTMPTHandler.messageReceived(RTMPTHandler.java:123)
[red5.jar:na]
    at org.red5.server.net.rtmpt.RTMPTServlet.handleSend(RTMPTServlet.java:385)
[red5.jar:na]
    at org.red5.server.net.rtmpt.RTMPTServlet.service(RTMPTServlet.java:471) [red5.jar:na]
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
[servlet-api-2.5.jar:6.1.7]
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
erChain.java:290)
[catalina-6.0.18.jar:na]
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
java:206)
[catalina-6.0.18.jar:na]
    at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:2
33)
[catalina-6.0.18.jar:na]
    at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:1
91)
[catalina-6.0.18.jar:na]
    at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.jav
a:433) [catalina-6.0.18.jar:na]
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
[catalina-6.0.18.jar:na]
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
[catalina-6.0.18.jar:na]
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
[catalina-6.0.18.jar:na]
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
[catalina-6.0.18.jar:na]
    at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:880)
[tomcat-coyote-6.0.18.jar:na]
    at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http1
1NioProtocol.java:719)
[tomcat-coyote-6.0.18.jar:na]
    at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2081)
[tomcat-coyote-6.0.18.jar:na]
    at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:8
86)
[na:1.6.0_13]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[na:1.6.0_13]
    at java.lang.Thread.run(Thread.java:619) [na:1.6.0_13]

can you verify that?

Original comment by seba.wag...@gmail.com on 27 May 2009 at 7:33

GoogleCodeExporter commented 9 years ago 
and the login window does not appear in blank, but with *error* instead of the 
labels

Original comment by seba.wag...@gmail.com on 27 May 2009 at 7:33

GoogleCodeExporter commented 9 years ago 
Since 2036 was mine I think I am to fix this issue, started working.... 8(

Original comment by volkov.r...@gmail.com on 27 May 2009 at 7:45

GoogleCodeExporter commented 9 years ago 
Cannot confirm seeing the bug - I've done a fresh install of the r2036 server 
and see 
no errors at all... 8( The only thing I've noticed is that main in latest 
client is 
named main.lzx.swf8.swf while in html code it is displayed as 
<script type="text/javascript"> 
        // <![CDATA[

        var so = new SWFObject("main.lzx.lzr=swf8.swf", "lzapp", "100%", 
"100%", "8", "#ffffff");

maybe, the reason of the bugs you see is that you use older client version with 
a new 
server?

Original comment by volkov.r...@gmail.com on 27 May 2009 at 8:42

GoogleCodeExporter commented 9 years ago

Original comment by volkov.r...@gmail.com on 27 May 2009 at 8:42

GoogleCodeExporter commented 9 years ago 
no I think this is more a *long-term* problem
we have it on the demo too. I restarted now but the effect is that after several
hours the server starts to do wrong things. Each HQL query does get confused by 
the
message on top. So nobody can use it anymore after several hours.

Original comment by seba.wag...@gmail.com on 27 May 2009 at 8:54

GoogleCodeExporter commented 9 years ago 
it would be very helpful if you could verify that on your test machine so that 
we can
make sure that its not a problem related to my environment and we see the same 
output
and work on it to resolve this Issue.

Original comment by seba.wag...@gmail.com on 27 May 2009 at 10:02

GoogleCodeExporter commented 9 years ago 
Sebastian, we're going to build the latest version today (or possibly tomorrow) 
and 
test it.
I'll report of anything concerning the problem to Issue 744.

Original comment by e.rovin...@gmail.com on 27 May 2009 at 10:31

GoogleCodeExporter commented 9 years ago 
I am sorry, but on fresh install I don't see anything wrong at all, but maybe I 
just 
miss the exact steps that are required to reproduce it, could you please 
describe the 
steps more thoroughly? I've recompiled main.lzx and ran everything again and 
it's 
still working

Original comment by volkov.r...@gmail.com on 27 May 2009 at 10:34

GoogleCodeExporter commented 9 years ago 
okay I renamed this Issue

Original comment by seba.wag...@gmail.com on 27 May 2009 at 10:36

GoogleCodeExporter commented 9 years ago 
Exactly how much time am I expected to wait until I see the exception?

Original comment by volkov.r...@gmail.com on 27 May 2009 at 11:35

GoogleCodeExporter commented 9 years ago 
The Demo run into it after around 12 hours, but I think it also depends on the 
usage.
So you might simply run the the test machine beside as some kind of stability 
test
and we will review the next days our systems.

Original comment by seba.wag...@gmail.com on 27 May 2009 at 11:49

GoogleCodeExporter commented 9 years ago 
Here in my enviroment the problem appers after some minutes, some like 20 
minutes.

After some minutes new users don't see de login window of openmeetings, no have 
http
errors. Users still loged work normaly but new connection have this problem.

On console show the message on port 5080 try connect.

DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - class
attrCount: 1
DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - attr len: 2
DEBUG 05-26 14:59:06.743 null 20481 -1
org.apache.jasper.compiler.SmapUtil$SDEInstaller [http-5080-1] - class
attrCount incremented

Debian Lenny 64bits
Red5 rc3
Jdk 1.6.14 64-bits 

Thank's

Original comment by kleytonn@gmail.com on 27 May 2009 at 1:13

GoogleCodeExporter commented 9 years ago 
I cannot reproduce the bahaviour that you report kleytonn. You are talking about
something different. Compare to http://openmeetings.de => you won't find that 
Issue
there. So what should we try to fix? 
Just to make clear: I don't think that we are talking about the same thing, I 
now did
rename this Issue to fit into my description. If you are sure that what you are
reporting is related to a problem inside openmeetings, please go ahead and open 
a new
Issue and include the hole server-log, a description of the problem and a 
screen from
the *empty* application by using the debug-version of openmeetings.

thanks,
sebastian

Original comment by seba.wag...@gmail.com on 27 May 2009 at 1:25

GoogleCodeExporter commented 9 years ago 
okay I might correct my statement ^^

it may look like in your case too like this Issue. I have seen something now 
that
looks similar to what you have reported here. But still not sure about it.

Original comment by seba.wag...@gmail.com on 27 May 2009 at 8:07

GoogleCodeExporter commented 9 years ago 
I think I found the root of the problem.
In the file Invitations there was a invalid mapping:
The attribute *String baseUrl* was mapped to a boolean in the database.
I think at this point the app did die silently and then tries to sync its cache 
with
the database crashes.

please test with 
r2041.

Original comment by seba.wag...@gmail.com on 28 May 2009 at 7:50

GoogleCodeExporter commented 9 years ago 
Thank's Sebastian... I will test now...

Original comment by kleytonn@gmail.com on 28 May 2009 at 1:27