I haven't tried FF3.7. Try chrome. There's lots of logging, you'll have to look through it (in the client) to figure out why it's closing the channel.
On Wed, Jun 30, 2010 at 23:35, andreas <[email protected]> wrote: > Does exactly the same when I start the web client with hosted_gwt > target in FF3.7. > > On 30 Jun., 15:13, andreas <[email protected]> wrote: >> OK, it seems like I messed it up. I'm actually still new to hg and >> hence not familiar with it. I made some changes and sort of was no >> longer able to pull and update so I created a new clone with hopefully >> head revision. >> >> hg sum prints: >> 226:db8332248da5 tip >> branch merge >> >> Now I just setup everything to check the log again for above mentioned >> problem with connection state and I just run into a different one: >> >> Web client is not able to connect. It periodically tries to reconnect >> but fails. Server log for the reconnect attempts is: >> >> 2010-06-30 15:05:12.479:DBUG::REQUEST /socket on >> org.eclipse.jetty.server.nio.selectchannelconnecto...@4bb369 >> 2010-06-30 >> 15:05:12.479:DBUG::servlet=org.waveprotocol.wave.examples.fedone.rpc.Server >> RpcProvider >> $WaveWebSocketServlet-29469766 >> 2010-06-30 15:05:12.479:DBUG::servlet holder= >> org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider >> $WaveWebSocketServlet-29469766 >> 2010-06-30 15:05:12.479:DBUG::chain= null >> 30.06.2010 15:05:12 >> org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider >> $WebSocketConnection <init> >> INFO: New websocket connection set up. >> 2010-06-30 15:05:12.488:DBUG::RESPONSE /socket 101 >> 2010-06-30 15:05:17.481:DBUG::REQUEST /socket on >> org.eclipse.jetty.server.nio.selectchannelconnecto...@1c79dfc >> 2010-06-30 >> 15:05:17.481:DBUG::servlet=org.waveprotocol.wave.examples.fedone.rpc.Server >> RpcProvider >> $WaveWebSocketServlet-29469766 >> 2010-06-30 15:05:17.481:DBUG::servlet holder= >> org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider >> $WaveWebSocketServlet-29469766 >> 2010-06-30 15:05:17.481:DBUG::chain= null >> 30.06.2010 15:05:17 >> org.waveprotocol.wave.examples.fedone.rpc.ServerRpcProvider >> $WebSocketConnection <init> >> INFO: New websocket connection set up. >> 2010-06-30 15:05:17.491:DBUG::RESPONSE /socket 101 >> >> Before I try messing around with hg again and destroy my clone again, >> do I have to apply the websocket patch? >> >> On 30 Jun., 10:29, andreas <[email protected]> wrote: >> >> >> >> > Where exactly? In the web-client log or server? >> >> > I'll have a look... >> >> > On 30 Jun., 03:08, Anthony Baxter <[email protected]> wrote: >> >> > > There should have been an earlier log message showing why the channel >> > > was closed. >> >> > > On Tue, Jun 29, 2010 at 21:39, andreas <[email protected]> >> > > wrote: >> > > > Hey everyone, >> >> > > > I'm experiencing a problem running FedOne (io2010). >> >> > > > In simple web client when I open another Wave besides the first opened >> > > > one and edit the reopened first Wave I get the following error >> > > > message: >> >> > > > [SEVERE] LB: Cannot send to closed operation channel: Operation >> > > > Channel State = [state: CLOSED] >> >> > > > The server itself does not log any errors. Sometimes I can reopen the >> > > > first Wave and type one letter which is successfully transmitted but >> > > > all following edits generate the above error. >> >> > > > After restarting the web client (F5) it works again. At least until I >> > > > start switching between Waves again. Then the same behavior: switch >> > > > back to the first open Wave and only first operation successfully >> > > > transmitted... >> >> > > > Has anybody experienced a similar problem? >> >> > > > Running on: >> > > > Ubuntu 10.04 >> > > > Java(TM) SE Runtime Environment (build 1.6.0_20-b02) >> > > > Java HotSpot(TM) Server VM (build 16.3-b01, mixed mode) >> > > > Federation is not active >> >> > > > Thanks, >> > > > Andreas >> >> > > > -- >> > > > You received this message because you are subscribed to the Google >> > > > Groups "Wave Protocol" 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 >> > > > athttp://groups.google.com/group/wave-protocol?hl=en. >> >> > > -- >> > > Anthony Baxter, [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" 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/wave-protocol?hl=en. > > -- Anthony Baxter, [email protected] -- You received this message because you are subscribed to the Google Groups "Wave Protocol" 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/wave-protocol?hl=en.
