Hi,
in the javaws.trace-log is no more message after that.
Here is the end of the jawaws.log:
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719406</millis>
<sequence>26</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[DEBUG] [AWT-EventQueue-0]
org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
swfUrl=null, videoCodecs=252} connectCallback
org.red5.screen.webstart.screensharert...@bf7916 conectCallArguments
null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>27</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>[ERROR] [Thread-12]
org.red5.screen.webstart.ScreenShareRTMPT - null
</message>
</record>
<record>
<date>2010-05-10T13:41:59</date>
<millis>1273491719500</millis>
<sequence>28</sequence>
<logger>com.sun.deploy</logger>
<level>FINE</level>
<class>com.sun.deploy.util.LoggerTraceListener</class>
<method>print</method>
<thread>10</thread>
<message>null
</message>
</record>
On port 80 with rtmpt it dosn't work.
Frank
On 10 Mai, 13:20, Sebastian Wagner <[email protected]> wrote:
> Hi Frank,
>
> I have tested with rtmpt running on port 8088 with two machines and it
> went well.
>
> [ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null null
> => is there any message after that?
>
> Sebastian
>
> 2010/5/10 frank <[email protected]>:
>
> > I test the screensharing with 2 computers as 2 different users in
> > differrent networks.
> > Now i see, there is an error-entry in the client-java-log:
>
> > [DEBUG] [AWT-EventQueue-0] org.red5.screen.webstart.ScreenShareRTMPT -
> > ScreenShare startStream
> > [DEBUG] [AWT-EventQueue-0]
> > org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
> > onlife3.brandenburg.de port 80 application openmeetings/4
> > connectCallback org.red5.screen.webstart.screensharert...@eb7331
> > [DEBUG] [AWT-EventQueue-0]
> > org.red5.server.net.rtmp.BaseRTMPClientHandler - connect server:
> > onlife3.brandenburg.de port 80 connectionParams {objectEncoding=0,
> > app=openmeetings/4, flashVer=WIN 9,0,115,0, fpad=false, tcUrl=rtmpt://
> > onlife3.brandenburg.de:80/openmeetings/4, audioCodecs=1639,
> > videoFunction=1, pageUrl=null, path=openmeetings/4, capabilities=15,
> > swfUrl=null, videoCodecs=252} connectCallback
> > org.red5.screen.webstart.screensharert...@eb7331 conectCallArguments
> > null
> > [ERROR] [Thread-14] org.red5.screen.webstart.ScreenShareRTMPT - null
> > null
>
> > Frank
>
> > On 10 Mai, 11:34, Sebastian Wagner <[email protected]> wrote:
> >> you do not test by sending the screensharing to yourself back again no?
> >> You have to login with two users, sharing back to yourself is disabled.
>
> >> Sebastian
>
> >> 2010/5/10 frank <[email protected]>:
>
> >> > Hi Sebastian,
>
> >> > thanks, for your work. The screensharing from outside the firewall to
> >> > the computers behind the firewall works fine.
> >> > Over the rtmpt-connection i can starting the screensharing and i can
> >> > download the application and now <thats new> starts the screensharing-
> >> > window.
> >> > But thats all. Nothing happens, when i klick the the start- or the
> >> > record-button. (no entry in the logs)
> >> > The last lines:
>
> >> > 2010-05-10 11:22:46,159 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
> >> > openmeetings] - Velocity [info] VelocityViewServlet: Default
> >> > content-type is: text/html; charset=UTF-8
> >> > 2010-05-10 11:22:46,234 [TP-Processor35] INFO o.a.c.c.C.[.[.0.0.0.[/
> >> > openmeetings] - Velocity [debug] ResourceManager : found
> >> > screenshare.vm with loader
> >> > org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
>
> >> > Frank
>
> >> > On 8 Mai, 15:06, Sebastian Wagner <[email protected]> wrote:
> >> >> Hi,
>
> >> >> check with this
> >> >> revision:http://code.google.com/p/openmeetings/source/detail?r=3242
>
> >> >> Sebastina
>
> >> >> On 27 Apr., 10:50, frank <[email protected]
>
> >> >> brandenburg.de> wrote:
> >> >> > Hi Sebastian,
>
> >> >> > after many test with different ports for rtmp,rtmptand http, i can
> >> >> > say it is not a port-problem.
> >> >> > If i use rtmp audio, video and screen-sharing are working.
> >> >> > But when i try it withrtmpt, only audio and video are working. I
> >> >> > think there is a failure in the screen-sharing application. The switch
> >> >> > tortmptis faulty.
>
> >> >> > Frank
>
> >> >> > On 22 Apr., 15:55, frank <[email protected]
>
> >> >> > brandenburg.de> wrote:
> >> >> > > I can start the screensharing by clicking the button. Then begins
> >> >> > > the
> >> >> > > download of the screensharing apllication.
> >> >> > > Thats all. There is an exeption in the java-log, but only, if port
> >> >> > > 1935 is closed.
>
> >> >> > > [ERROR] [javawsApplicationMain]
> >> >> > > org.red5.screen.webstart.ScreenShareRTMPT - createWindow Exception:
> >> >> > > java.lang.NullPointerException
> >> >> > > at
> >> >> > > org.red5.screen.webstart.gui.VirtualScreen.<init>(VirtualScreen.java:
> >> >> > > 34) [red5-screenshare.jar:na]
> >> >> > > at
> >> >> > > org.red5.screen.webstart.ScreenShareRTMPT.createWindow(ScreenShareRTMPT.jav
> >> >> > > a:
> >> >> > > 315) [red5-screenshare.jar:na]
> >> >> > > at
> >> >> > > org.red5.screen.webstart.ScreenShareRTMPT.main(ScreenShareRTMPT.java:
> >> >> > > 228) [red5-screenshare.jar:na]
> >> >> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >> > > Method) [na:
> >> >> > > 1.6.0_19]
> >> >> > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> >> >> > > Source) [na:
> >> >> > > 1.6.0_19]
> >> >> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> >> >> > > Source)
> >> >> > > [na:1.6.0_19]
> >> >> > > at java.lang.reflect.Method.invoke(Unknown Source)
> >> >> > > [na:1.6.0_19]
> >> >> > > at com.sun.javaws.Launcher.executeApplication(Unknown
> >> >> > > Source) [na:na]
> >> >> > > at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> >> >> > > [na:na]
> >> >> > > at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> >> >> > > [na:na]
> >> >> > > at com.sun.javaws.Launcher.run(Unknown Source) [na:na]
> >> >> > > at java.lang.Thread.run(Unknown Source) [na:1.6.0_19]
> >> >> > > java.lang.NullPointerException
> >> >> > > at
> >> >> > > org.red5.screen.webstart.gui.VirtualScreen.<init>(VirtualScreen.java:
> >> >> > > 34)
> >> >> > > at
> >> >> > > org.red5.screen.webstart.ScreenShareRTMPT.createWindow(ScreenShareRTMPT.jav
> >> >> > > a:
> >> >> > > 315)
> >> >> > > at
> >> >> > > org.red5.screen.webstart.ScreenShareRTMPT.main(ScreenShareRTMPT.java:
> >> >> > > 228)
> >> >> > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> >> >> > > Method)
> >> >> > > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
> >> >> > > Source)
> >> >> > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> >> >> > > Source)
> >> >> > > at java.lang.reflect.Method.invoke(Unknown Source)
> >> >> > > at com.sun.javaws.Launcher.executeApplication(Unknown
> >> >> > > Source)
> >> >> > > at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
> >> >> > > at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
> >> >> > > at com.sun.javaws.Launcher.run(Unknown Source)
> >> >> > > at java.lang.Thread.run(Unknown Source)
>
> >> >> > > On 22 Apr., 15:31, Sebastian Wagner <[email protected]> wrote:
>
> >> >> > > > What do you mean by does not work?
> >> >> > > > The Screen sharing should switch toRTMPT(so to port 80 in your
> >> >> > > > case) if
> >> >> > > > the user is connected to the application usingrtmpt. (In other
> >> >> > > > words
> >> >> > > > screensharing should always use the same as audio and video)
>
> >> >> > > > As you maybe have seen: Initially the application it will try
> >> >> > > > rtmp 3 times,
> >> >> > > > if that fails it switches tortmpt.
> >> >> > > > If you then later start the screen sharing it will use the same
> >> >> > > > settings as
> >> >> > > > the main-connection (that is also used to broadcast audio/video).
> >> >> > > > If it initially suceeds in connecting via rtmp of course screen
> >> >> > > > sharing will
> >> >> > > > also use rtmp.
>
> >> >> > > > Sebastian
>
> >> >> > > > 2010/4/22 frank <[email protected]>
>
> >> >> > > > > Hi Sebastian,
> >> >> > > > > we used these instruction
> >> >> > > > > (http://groups.google.com/group/openmeetings-
> >> >> > > > > user/msg/f73bd2ada345759d<http://groups.google.com/group/openmeetings-%0Auser/msg/f73bd2ada345759d>)
> >> >> > > > > and the follow ports:
>
> >> >> > > > > config.xml
> >> >> > > > > rtmpport 1935
> >> >> > > > > rtmpTunnelport 80
> >> >> > > > > httpport 80
>
> >> >> > > > > red5.properties
> >> >> > > > > rtmp.port=1935
> >> >> > > > >rtmpt.port 80
>
> >> >> > > > > How i say: audio and video are ok, but screensharing does'n
> >> >> > > > > work.
> >> >> > > > > Frank
>
> >> >> > > > > On 22 Apr., 14:56, Sebastian Wagner <[email protected]>
> >> >> > > > > wrote:
> >> >> > > > > > Hi Frank,
>
> >> >> > > > > > when you change in the red5.properties and config.xml
> >> >> > > > > > the ports of rtmp andrtmpt
> >> >> > > > > > audio + video and screensharing will use those.
>
> >> >> > > > > > Screensharing does automatically use the same ports as audio
> >> >> > > > > > and video.
>
> >> >> > > > > > Sebastian
>
> >> >> > > > > > 2010/4/22 frank <[email protected]>
>
> >> >> > > > > > > Hi,
> >> >> > > > > > > our openmeetings is running on port 80, so we can use it
> >> >> > > > > > > behind a
> >> >> > > > > > > firewall. Audio and video are ok.
> >> >> > > > > > > Only screensharing is not working (it works, when the
> >> >> > > > > > > firewallport
> >> >> > > > > > > 1935 is open). Would it be possible to run screensharing on
> >> >> > > > > > > port 80.
>
> >> >> > > > > > > --
> >> >> > > > > > > You received this message because you are subscribed to the
> >> >> > > > > > > Google
> >> >> > > > > Groups
> >> >> > > > > > > "OpenMeetings User" group.
> >> >> > > > > > > To post to this group, send email to
> >> >> > > > > [email protected].
> >> >> > > > > > > To unsubscribe from this group, send email to
> >> >> > > > > > > [email protected]<openmeetings-user%2Bunsubscr
> >> >> > > > > > > [email protected]>
> >> >> > > > > <openmeetings-user%[email protected]<openmeetings-user%252Buns
> >> >> > > > > [email protected]>
>
> >> >> > > > > > > .
> >> >> > > > > > > For more options, visit this group at
> >> >> > > > > > >http://groups.google.com/group/openmeetings-user?hl=en.
>
> >> >> > > > > > --
> >> >> > > > > > Sebastian
> >> >> > > > > Wagnerhttp://www.webbase-design.dehttp://openmeetings.googlecode.comhttp://
> >> >> > > > >www.laszlo-forum.de
> >> >> > > > > > [email protected]
>
> >> >> > > > > > --
> >> >> > > > > > You received this message because you are subscribed to the
> >> >> > > > > > Google Groups
> >> >> > > > > "OpenMeetings User" group.
> >> >> > > > > > To post to this group, send email to
> >> >> > > > > > [email protected].
> >> >> > > > > > To unsubscribe from this group, send email to
> >> >> > > > > [email protected]<openmeetings-user%2Bunsubscr
>
> ...
>
> Erfahren Sie mehr »
--
You received this message because you are subscribed to the Google Groups
"OpenMeetings User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/openmeetings-user?hl=en.
