You should find the solution here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/apache_setup
On Thu, May 30, 2013 at 5:48 AM, Antti Vanne <[email protected]> wrote: > 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() > > WebSocket connection to 'ws://localhost:8080/ws' failed: Unexpected > response code: 400 > > even though everything runs fine on the proxy server. Seems similar to > this stackoverflow question > http://stackoverflow.com/questions/16503349/node-http-proxy-with-proxytable-and-websockets > > > 2013/5/21 Sebastien Jourdain <[email protected]> > >> 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. >> 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. >> >> 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. >> 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. >> >> If you want to give a try, you can read >> https://blog.nodejitsu.com/http-proxy-intro, and if you have something >> that you are willing to share we can extend our "SessionManager" code base. >> >> Thanks, >> >> Seb >> >> >> >> >> On Tue, May 21, 2013 at 6:14 AM, Antti Vanne <[email protected]>wrote: >> >>> Thanks Sebastien, >>> >>> 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. >>> >>> WARN:oejw.WebSocketConnectionRFC6455:Text message too large > 2097152 >>> chars for SCEP@4a48edb5 >>> >>> >>> >>> >>> 2013/5/10 Sebastien Jourdain <[email protected]> >>> >>>> Hi Antti, >>>> >>>> if you have built ParaViewWeb from ParaView/master from git, you >>>> already have the newest version of ParaViewWeb available to you inside >>>> ParaView proper. >>>> >>>> That new version of ParaViewWeb does not require any thirdparty >>>> component such as activemq. >>>> In fact, if you install https://github.com/senchalabs/jsduck 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. >>>> >>>> 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. >>>> >>>> A real announcement for that new version with documentation update and >>>> so on will happen at the release of ParaVIew 4.0. >>>> >>>> Seb >>>> >>>> >>>> On Fri, May 10, 2013 at 8:41 AM, Antti Vanne <[email protected]>wrote: >>>> >>>>> Hi there, >>>>> >>>>> I've succesfully compiled and deployed ParaViewWeb upto the point that >>>>> I can login as admin on localhost:8080/PWService >>>>> >>>>> 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? >>>>> >>>>> The error message I get in the logs or on the command line is as >>>>> follows: >>>>> >>>>> ./PWServer.sh >>>>> Error message: This producer can only send messages to: >>>>> kitware.paraweb.viewupdates >>>>> This producer can only send messages to: kitware.paraweb.viewupdates >>>>> FILE: activemq/core/kernels/ActiveMQProducerKernel.cpp, LINE: >>>>> 271 >>>>> FILE: activemq/core/kernels/ActiveMQProducerKernel.cpp, LINE: >>>>> 181 >>>>> FILE: activemq/core/ActiveMQProducer.cpp, LINE: 100 >>>>> >>>>> ERROR: In >>>>> /home/vanne/src/SuperBuild/src/ParaViewAdapter/vtkPWJMSMessagingService.cxx, >>>>> line 158 >>>>> vtkPWJMSMessagingService (0x8856c58): CMS Exception >>>>> >>>>> >>>>> Any ideas how to proceed from here? Thanks. >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>>> >>>>> >>>> >>> >>> >>> -- >>> Antti Vanne >>> Kuava Oy >>> Microkatu 1 >>> PL 1188 >>> 70211 Kuopio Finland >>> tel. +358 50 356 6744 >>> >> >> > > > -- > Antti Vanne > Kuava Oy > Microkatu 1 > PL 1188 > 70211 Kuopio Finland > tel. +358 50 356 6744 >
_______________________________________________ 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
