[Paraview] WebSocket Connection lost in ParaviewWeb

Scott Wittenburg scott.wittenburg at kitware.com
Tue Jan 21 11:42:00 EST 2014


Just wanted to jump in here.  The patch instructions are, strangely,
missing from that Amazon EC2 setup documentation.  That's my fault, since I
wrote it.  I'll update the documenation with the steps below, which should
have been in there all along.  However, I just checked, and the version
you're using (2.4.7) already has the patch included, so these steps really
only apply to versions 2.4.6 and earlier.  Sorry for the oversight.

1)  Download the patch:

wget -O patch.txt
https://issues.apache.org/bugzilla/attachment.cgi?id=30886&action=diff&context=patch&collapsed=&headers=1&format=raw

2) Change to the root of the httpd source tree and patch the source:

patch -u -p1 < path-to-patch/patch.txt




On Tue, Jan 21, 2014 at 4:24 AM, Arya Mazaheri <aryanet at gmail.com> wrote:

> Thanks for your reply.
> Previously, I was following the old model approach using apache 2.2. Now,
> I upgraded to Apache 2.4.7. And followed the Amazon EC2 tutorial. However,
> now I get the following message in the firebug which the rickshaw.min.js
> file generated that:
> Firefox can't establish a connection to the server at
> ws://pvwserver/proxy?sessionId=9521c7c5-d2c6-4e9d-980e-5c7ea9f7dfd4.
>
> Is it related to the rewriting module? Maybe it's not working! Any idea?
>  I've attached my 'pw-config.properties' and 'httpd-vhosts.conf' files to
> this thread.
>
> Regards,
>
>
> On Mon, Jan 20, 2014 at 10:26 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> The web socket forwarding should be handle by Apache at that point and it
>> seems to be done by Jetty?
>> In your jetty configuration, the session URL might not be valid when
>> using Apache as a front-end.
>>
>> Moreover, which Apache setup did you used? 2.4+ like for the EC2 Amazon
>> documentation or the old one with the Python module?
>>
>> Seb
>>
>>
>>  On Mon, Jan 20, 2014 at 9:24 AM, Arya Mazaheri <aryanet at gmail.com>wrote:
>>
>>>  Hi there,
>>> I've installed ParaviewWeb from source and configured apache to work
>>> with jetty. I think I've done every configuration according to the
>>> tutorials. But everytime I try to open DataProber application I face with
>>> the following error in Jetty console output:
>>>
>>> Jan 20, 2014 7:50:18 PM
>>>> com.kitware.paraviewweb.websocket.WebSocketForwarder onOpen
>>>> INFO: null
>>>> java.util.concurrent.ExecutionException: java.net.ConnectException:
>>>> Connection refused
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketClient$WebSocketFuture.get(WebSocketClient.java:569)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketClient$WebSocketFuture.get(WebSocketClient.java:372)
>>>>     at
>>>> com.kitware.paraviewweb.websocket.WebSocketForwarder.onOpen(WebSocketForwarder.java:54)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketConnectionRFC6455.onWebSocketOpen(WebSocketConnectionRFC6455.java:425)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketServletConnectionRFC6455.handshake(WebSocketServletConnectionRFC6455.java:60)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketFactory.upgrade(WebSocketFactory.java:309)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketFactory.acceptWebSocket(WebSocketFactory.java:382)
>>>>     at
>>>> org.eclipse.jetty.websocket.WebSocketHandler.handle(WebSocketHandler.java:43)
>>>>     at
>>>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>>>>     at org.eclipse.jetty.server.Server.handle(Server.java:365)
>>>>     at
>>>> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
>>>>     at
>>>> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926)
>>>>     at
>>>> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988)
>>>>     at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
>>>>     at
>>>> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>>>>     at
>>>> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>>>>     at
>>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
>>>>     at
>>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
>>>>     at
>>>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>>>>     at
>>>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>>>>     at java.lang.Thread.run(Thread.java:701)
>>>> Caused by: java.net.ConnectException: Connection refused
>>>>     at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
>>>>     at
>>>> sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:597)
>>>>     at
>>>> org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:628)
>>>>     at
>>>> org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290)
>>>>     ... 3 more
>>>>
>>>
>>> In the firebug, I see the following error:
>>> Connection lost - retrying (1) ..
>>>
>>> Any ideas?
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>
>>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20140121/77befe41/attachment-0001.html>


More information about the ParaView mailing list