[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488568#comment-13488568
 ] 

SebastianWagner commented on OPENMEETINGS-456:
----------------------------------------------

I don't think you are using OpenMeetings 2.0, your are using OpenMeetings 
nightly build or from source, OpenMeetings 2.1.x right ?
                
> Invitation Request link causes getLanguageByIdAndMax Exception
> --------------------------------------------------------------
>
>                 Key: OPENMEETINGS-456
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-456
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 2.0 Apache Incubator Release
>         Environment: Debian Squeeze
>            Reporter: Marco Roello
>            Assignee: SebastianWagner
>
> I've installed om on debian squeeze succesfully.
> (I followed this guide 
> https://cwiki.apache.org/OPENMEETINGS/tutorials-related-to-openmeetings.data/Installing%20OM2.x%20On%20Debian64%20-%20Headless.pdf
>  )
> I can login with my lan ipaddress, can manage the backend with the admin 
> users, and I can create users.
> The Default TimeZone is set to Europe/Berlin. The Debian system is set to 
> GMT+1 too.
> I can enter a room with admin user (or another user). When I send an 
> invitation, the invited user receives the invite, with the correct address 
> link (no localhost).
> an example invite link generated is:
> http://192.168.100.67:5080/openmeetings/?invitationHash=1e7acd4dcd31b1afb4c3eec37428c233&language=5
> clicking the url receive a empty modal window
> Error Missing [556]
> in the log details I've found:
> [ERROR] [http-nio-0.0.0.0-8088-exec-5] org.red5.server.service.ServiceInvoker 
> - Error executing call: Service: languageservice Method: 
> getLanguageByIdAndMax Num Params: 3 0: NaN 1: 0 2: 100
> java.lang.IllegalArgumentException: argument type mismatch
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
> ~[na:1.6.0_18]
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
> ~[na:1.6.0_18]
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[na:1.6.0_18]
>         at java.lang.reflect.Method.invoke(Method.java:616) ~[na:1.6.0_18]
>         at 
> org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:196) 
> [red5.jar:na]
>         at 
> org.red5.server.service.ServiceInvoker.invoke(ServiceInvoker.java:115) 
> [red5.jar:na]
>         at 
> org.red5.server.net.rtmp.RTMPHandler.invokeCall(RTMPHandler.java:157) 
> [red5.jar:na]
>         at 
> org.red5.server.net.rtmp.RTMPHandler.onInvoke(RTMPHandler.java:399) 
> [red5.jar:na]
>         at 
> org.red5.server.net.rtmp.BaseRTMPHandler.messageReceived(BaseRTMPHandler.java:130)
>  [red5.jar:na]
>         at 
> org.red5.server.net.rtmpt.RTMPTHandler.messageReceived(RTMPTHandler.java:129) 
> [red5.jar:na]
>         at 
> org.red5.server.net.rtmpt.RTMPTServlet.handleSend(RTMPTServlet.java:410) 
> [red5.jar:na]
>         at 
> org.red5.server.net.rtmpt.RTMPTServlet.service(RTMPTServlet.java:488) 
> [red5.jar:na]
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) 
> [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168) 
> [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) 
> [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) 
> [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
>  [tomcat-embed-core-jar-7.0.32.jar:7.0.32]
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>  [na:1.6.0_18]
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>  [na:1.6.0_18]
>         at java.lang.Thread.run(Thread.java:636) [na:1.6.0_18]
> If I've understood, getLanguageByIdAndMax is receiving null instead of 
> language_id.
> I've tried changing invite language id in the url querystring, but nothing 
> changes.
> If I remove the language querystring part from the url, for example:
> http://192.168.100.67:5080/openmeetings/?invitationHash=1e7acd4dcd31b1afb4c3eec37428c233
> I receive the message: No invitation available for this invitation code dialog
> But I've tried to send the invitation with no expire date, with a very wide 
> range of dates (from 01-01-2011 to 31-12-2013), with once, but nothing 
> changes.
> It seems the are two bugs, one language related, the second timezone related 
> (not sure)
> Any suggestions? Thanks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to