<div dir="ltr">Thanks for the tips. I started working on http-proxy, but there seems to be an issue with websocket proxying. On the Chrome javascript console we get error code 400 on paraview.start() <div><span style="color:rgb(255,0,0);font-family:'dejavu sans mono',monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div><span style="color:rgb(255,0,0);font-family:'dejavu sans mono',monospace;font-size:11px;white-space:pre-wrap">WebSocket connection to 'ws://localhost:8080/ws' failed: Unexpected response code: 400</span><span style="color:rgb(255,0,0);font-family:'dejavu sans mono',monospace;font-size:11px;white-space:pre-wrap"> </span><br>
</div><div><br></div><div style>even though everything runs fine on the proxy server. Seems similar to this stackoverflow question <a href="http://stackoverflow.com/questions/16503349/node-http-proxy-with-proxytable-and-websockets">http://stackoverflow.com/questions/16503349/node-http-proxy-with-proxytable-and-websockets</a></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/21 Sebastien Jourdain <span dir="ltr"><<a href="mailto:sebastien.jourdain@kitware.com" target="_blank">sebastien.jourdain@kitware.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The current version of the session manager based on Jetty is just a starting point and depending on the deployment that you expect, you may build your own.<div>
In fact, there is still some work to be done if we want to make it bullet proof. Although, using apache as a proxy and jetty as job launcher seems to be pretty reliable.</div>
<div><br></div><div>But if you like the light weight and ease of deployment of the current JettySessionManager, you may find a system based on Node.js as easy.</div><div>In fact, to provide a larger set of front-end technologies, we were thinking to use Node.js for that as it seems to have built-in websocket and http proxy/forwarding capabilities.</div>
<div><br></div><div>If you want to give a try, you can read <a href="https://blog.nodejitsu.com/http-proxy-intro" target="_blank">https://blog.nodejitsu.com/http-proxy-intro</a>, and if you have something that you are willing to share we can extend our "SessionManager" code base.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Seb</div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 21, 2013 at 6:14 AM, Antti Vanne <span dir="ltr"><<a href="mailto:antti.vanne@kuava.fi" target="_blank">antti.vanne@kuava.fi</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks Sebastien, <div><br></div><div>the nightly build works nicely. We're using Jetty as a frontend. Where would it be easiest to set Jetty's properties? When a larger model is transferred to client in geometry form, the default max message size is met pretty soon. </div>
<div><br></div><div>WARN:oejw.WebSocketConnectionRFC6455:Text message too large > 2097152 chars for SCEP@4a48edb5<br></div><div><br></div><div><br></div></div><div class="gmail_extra"><div><div><br><br><div class="gmail_quote">
2013/5/10 Sebastien Jourdain <span dir="ltr"><<a href="mailto:sebastien.jourdain@kitware.com" target="_blank">sebastien.jourdain@kitware.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi Antti,<div><br></div><div>if you have built ParaViewWeb from ParaView/master from git, you already have the newest version of ParaViewWeb available to you inside ParaView proper.</div><div><br>
</div><div>That new version of ParaViewWeb does not require any thirdparty component such as activemq.</div><div>In fact, if you install <a href="https://github.com/senchalabs/jsduck" target="_blank">https://github.com/senchalabs/jsduck</a> and turn ON the WEB_DOCUMENTATION inside CMake, ParaView will automatically generate a full web site with all the new documentation for ParaViewWeb. Just search for a 'www' directory inside your build or install tree. </div>
<div><br></div><div>In fact, if you download any nightly binary from our web site, they already come with ParaViewWeb available (No need to compile it anymore...). Only the windows binaries does not contains the Web documentation, but you can get the web pages from any other system, and those will work just fine.</div>
<div><br></div><div>A real announcement for that new version with documentation update and so on will happen at the release of ParaVIew 4.0.</div><div><br></div><div>Seb</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote"><div><div>On Fri, May 10, 2013 at 8:41 AM, Antti Vanne <span dir="ltr"><<a href="mailto:antti.vanne@kuava.fi" target="_blank">antti.vanne@kuava.fi</a>></span> wrote:<br></div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>
<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi there, </span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">I've succesfully compiled and deployed ParaViewWeb upto the point that I can login as admin on localhost:8080/PWService </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">However, all visualization fail and the root cause seems to be with the message broker. I've tried starting different versions of ActiveMQ (3.1, 4.1.2, 5.3.2, 5.5.1 and 5.7.0) but all fail. Should the broker be configured and not just started from the vanilla binary installation package? </div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">The error message I get in the logs or on the command line is as follows: <br clear="all"><div><br>
</div><div><div>./PWServer.sh</div><div>Error message: This producer can only send messages to: kitware.paraweb.viewupdates</div><div>This producer can only send messages to: kitware.paraweb.viewupdates</div><div> FILE: activemq/core/kernels/ActiveMQProducerKernel.cpp, LINE: 271</div>
<div> FILE: activemq/core/kernels/ActiveMQProducerKernel.cpp, LINE: 181</div><div> FILE: activemq/core/ActiveMQProducer.cpp, LINE: 100</div><div><br></div><div>ERROR: In /home/vanne/src/SuperBuild/src/ParaViewAdapter/vtkPWJMSMessagingService.cxx, line 158</div>
<div>vtkPWJMSMessagingService (0x8856c58): CMS Exception</div></div><div><br></div><div><br></div><div>Any ideas how to proceed from here? Thanks. </div></div><div><br></div></div>
<br></div></div>_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/mailman/listinfo/paraview</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br>Antti Vanne<br>Kuava Oy<br>Microkatu 1<br>PL 1188<br>70211 Kuopio Finland<br>tel. <a href="tel:%2B358%2050%20356%206744" value="+358503566744" target="_blank">+358 50 356 6744</a>
</font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Antti Vanne<br>Kuava Oy<br>Microkatu 1<br>PL 1188<br>70211 Kuopio Finland<br>tel. +358 50 356 6744
</div>