[Paraview] ParaViewWeb build - PWServer
Sebastien Jourdain
sebastien.jourdain at kitware.com
Sun Aug 21 20:38:33 EDT 2011
Hi Max,
I never get that error. It seems that the tomcat application (Java) is
sending an incomplete stream to the server PWServer (c++).
What is the content of the tomcat log ? (catalina.out)
What did you try to load with PWApp ? Did you check the PWService and
were you able to see the running process or the history of them ?
Thanks,
Seb
On Sun, Aug 21, 2011 at 11:33 AM, WILKINSON M.
<maxwell.wilkinson at durham.ac.uk> wrote:
> Hi
>
> I think I have solved the 8080 already in use issue. I did have tomcat
> running on startup, so I was running two instances, both trying to use port
> 8080. I did check this a number of times, but I've only just realized
> exactly what the problem was.
>
> When running PWApp I now receive the following logged error messages from
> the ParaViewWeb working directory:
>
> ERROR: In
> /home/max/Downloads/ParaViewWeb/ParaViewAdapter/vtkPWJMSMessagingService.cxx,
> line 154
> vtkPWJMSMessagingService (0x14870f0): CMS Exception
>
> ----
>
> Also from pw-out-1.log: (I'm not sure if this is in fact an error)
>
> JMS Initialized in 0.115973 seconds
>
> sessionID : org.paraview.paraweb
> logLevel : ERROR
> Processing Engine Initialized in 2.20879 seconds
>
> Processing engine is started !
> Error message: DataInputStream::readLong - Reached EOF
> DataInputStream::readLong - Reached EOF
> FILE: decaf/io/DataInputStream.cpp, LINE: 495
> FILE: decaf/io/DataInputStream.cpp, LINE: 501
> FILE: decaf/io/DataInputStream.cpp, LINE: 129
> FILE: activemq/wireformat/openwire/OpenWireFormat.cpp, LINE: 265
> FILE: activemq/transport/IOTransport.cpp, LINE: 243
>
> ----
>
> I've searched for the above errors, but I couldn't find a solution.
>
> Could someone suggest what the problem may be?
>
> Thanks
> Max
>
>
>
> -----Original Message-----
> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
> Sent: Fri 19/08/11 23:09
> To: WILKINSON M.
> Cc: paraview at paraview.org
> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>
> Hi Max,
>
> thanks for sharing that with others.
>
> Based on the latest informations that you are providing, it seems that
> you use the tomcat from the system.
> In order to ease the testing/deployment process of ParaViewWeb, you
> should first try to run your own tomcat as your own user that should
> not be root.
> But as tomcat seems to work as a daemon (root/tomcat6), you have to
> make sure you did stop it before starting your own tomcat.
> Moreover, if you don't want to fall on previous error, just remove all
> log files, so when you start tomcat, you are sure that the new log
> files contains only the information of the current session. (You can
> do the same with the database directory of ParaViewWeb)
>
> Moreover, don't try to hot deploy ParaViewWeb while tomcat is running.
>
> Seb
>
> On Fri, Aug 19, 2011 at 3:51 PM, WILKINSON M.
> <maxwell.wilkinson at durham.ac.uk> wrote:
>> Hi all
>>
>> I'm having a problem with runtime configuration of ParaViewWeb.
>>
>> When I go to http://localhost:8080/PWApp and try to start a visualization,
>> the loading screen hangs without error.
>>
>> In the log file for tomcat I'm given:
>>
>> SEVERE: Error initializing endpoint
>>
>> java.net.BindException: Address already in use <null>:8080
>>
>> This tells me that port 8080 is already in use.
>>
>> In the terminal if I do:
>>
>> $ netstat -lnp | grep 8080
>> tcp6 0 0 :::8080 :::*
>> LISTEN 2449/java
>>
>> $ ps -lf 2449
>> F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME
>> CMD
>> 0 S root 2449 1 2 80 0 - 199655 futex_ 20:38 pts/0 0:04
>> /usr/bin/java
>> -Djava.util.logging.config.file=/usr/local/tomcat/conf/logging.properti
>>
>> This tells me that tomcat is running on port 8080. Isn't this the port it
>> should be running on? So what's the problem?
>>
>> If I shutdown tomcat
>> $./shutdown.sh
>>
>> Then check port 8080 again, the process has been stopped:
>> $ netstat -lnp | grep 8080
>> $
>>
>> What exactly is wrong here? I've set up tomcat to use port 8080, but when
>> I
>> try to run ParaViewWeb through tomcat it complains that port 8080 is
>> already
>> in use?
>>
>> Thanks
>>
>> Also, for the archive, please find attached to the remainder of this post
>> some answers to previous problems I've had while setting up ParaViewWeb.
>> Hopefully these will be of use to other users. A big thank you to
>> Sebastian
>> for his help.
>>
>> Max
>>
>> -----Original Message-----
>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>> Sent: Mon 15/08/11 21:31
>> To: WILKINSON M.
>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>
>> are you sure you don't have any system tomcat already running...
>> Otherwise, when you stop tomcat and restart it, you did not fully stop
>> tomcat.
>>
>> To make sure that tomcat is not running anymore after you requested it
>> to stop type the following command line.
>>
>>> ps aux | grep java | grep tomcat
>>
>> If you still have a process just kill it before trying to starting it
>> again.
>>
>> Seb
>>
>> On Mon, Aug 15, 2011 at 3:52 PM, WILKINSON M.
>> <maxwell.wilkinson at durham.ac.uk> wrote:
>>> Hi Seb
>>>
>>> I have LD_LIBRARY_PATH set correctly using PWServer.sh
>>>
>>> When I start a session in PWApp the pw-out log file is as follows:
>>>
>>> -----
>>>
>>> JMS Initialized in 0.118797 seconds
>>> sessionID : org.paraview.paraweb
>>> logLevel : ERROR
>>> Processing Engine Initialized in 2.14165 seconds
>>>
>>> Processing engine is started !
>>> -----
>>>
>>> However the session hangs while it is still loading without any onscreen
>>> error.
>>>
>>> The log file for tomcat details the following:
>>>
>>> SEVERE: Error starting endpoint
>>> java.net.BindException: Address already in use <null>:8080
>>>
>>> SEVERE: Failed to start connector [Connector[HTTP/1.1-8080]]
>>> LifecycleException: service.getName(): "Catalina"; Protocol handler
>>> start
>>> failed: java.net.BindException: Address already in use <null>:8080
>>>
>>> -----
>>>
>>> I have checked to see if I have other processes using port 8080:
>>>
>>> None are listed before running tomcat:
>>> $ sudo netstat -anp | grep 8080
>>>
>>> Once I start tomcat:
>>> $ sudo netstat -anp | grep 8080
>>> tcp6 0 0 :::8080 :::*
>>> LISTEN 2318/java
>>>
>>> Once I start firefox with /localhost:8080/PWApp/
>>> $ sudo netstat -anp | grep 8080
>>> tcp 0 0 127.0.0.1:38587 127.0.0.1:8080
>>> ESTABLISHED 1732/firefox-bin
>>> tcp6 0 0 :::8080 :::*
>>> LISTEN 2318/java
>>> tcp6 0 0 127.0.0.1:8080 127.0.0.1:38587
>>> ESTABLISHED
>>>
>>> Are these processes correct for port 8080 and are you able to suggest
>>> what
>>> the problem may be?
>>>
>>> Thanks for your patience!
>>>
>>> Max
>>>
>>> -----Original Message-----
>>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>>> Sent: Sun 14/08/11 16:17
>>> To: WILKINSON M.
>>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>>
>>> Hi Max,
>>>
>>> I think you successfully build everything. Now it is just a matter of
>>> runtime setting. Basically your LD_LIBRARY_PATH is not properly set so
>>> the ParaView shared library are not found.
>>>
>>> One way to solve that is to create an executable script PWServer.sh in
>>> the same location of the PWServer executable.
>>> In that script, you just set the LD_LIBRARY_PATH as it is supposed to
>>> be. In order to quickly test if you solved all your runtime library
>>> dependency, you can run the executable/script manually in order to get
>>> directly the name of the missing library.
>>>
>>> Here is an example of what a PWSever.sh file could look like.
>>>
>>> export LD_LIBRARY_PATH=....set of directory that contains the so files
>>> that the application is using....
>>> .../PWServer $1 $2 $3 $4 $5 $6 $7 $8
>>>
>>> But if you take the route of the script don't forget to update the
>>> executable path/name in the pw-config.properties file inside your
>>> tomcat lib directory.
>>>
>>> Seb
>>>
>>> On Sun, Aug 14, 2011 at 10:58 AM, WILKINSON M.
>>> <maxwell.wilkinson at durham.ac.uk> wrote:
>>>> Hi Seb
>>>>
>>>> Deleting the PW database fixed the problem, thanks for your help with
>>>> this.
>>>>
>>>> I now have the following error given in the log error file:
>>>>
>>>> /opt/install-pw/bin/PWServer: error while loading shared libraries:
>>>> libvtkPVServerManager.so: cannot open shared object file: No such file
>>>> or
>>>> directory
>>>>
>>>> I have this file installed under
>>>> /opt/install-ParaView/lib/paraview-3.10/
>>>>
>>>> Should I have specified this location in the ccmake for ParaViewWeb?
>>>>
>>>> ----------
>>>>
>>>> My ccmake for ParaView looks like this:
>>>>
>>>> BUILD_SHARED_LIBS
>>>> ON
>>>> CMAKE_BUILD_TYPE
>>>> Debug
>>>> CMAKE_INSTALL_PREFIX
>>>> /opt/install-ParaView
>>>> PARAVIEW_BUILD_QT_GUI
>>>> OFF
>>>> PARAVIEW_DATA_ROOT
>>>> PARAVIEW_DATA_ROOT-NOTFOUND
>>>> PARAVIEW_ENABLE_PYTHON
>>>> ON
>>>> PARAVIEW_ENABLE_PYTHON_FILTERS
>>>> ON
>>>> PARAVIEW_USE_MPI
>>>> OFF
>>>> PARAVIEW_USE_VISITBRIDGE
>>>> OFF
>>>> PYVERSIONS_EXE
>>>> /usr/bin/pyversions
>>>> QT_QMAKE_EXECUTABLE
>>>> QT_QMAKE_EXECUTABLE-NOTFOUND-NOTFOUND
>>>> VTK_EXTRA_COMPILER_WARNINGS
>>>> OFF
>>>> VTK_WRAP_PYTHON_SIP OFF
>>>>
>>>> ----------
>>>> My ccmake for ParaViewWeb looks like this:
>>>>
>>>> ACTIVEMQ_CPP
>>>> /usr/local/lib/libactivemq-cpp.so
>>>> ACTIVEMQ_INCLUDE_DIR
>>>> /usr/local/include/activemq-cpp-3.4.0
>>>> ANT_EXECUTABLE
>>>> /usr/share/ant/bin/ant
>>>> BUILD_CONSOLE_SAMPLE
>>>> ON
>>>> BUILD_FLEX_RENDERER
>>>> ON
>>>> BUILD_MANTA_SAMPLE
>>>> OFF
>>>> BUILD_PW_SERVER
>>>> ON
>>>> BUILD_SANDBOX_SAMPLE
>>>> ON
>>>> BUILD_SHUTTLE
>>>> ON
>>>> BUILD_SIMPLE_JS
>>>> ON
>>>> BUILD_STATE_APP_BUILDER
>>>> ON
>>>> BUILD_TESTING
>>>> ON
>>>> BUILD_WEB_APPLICATION
>>>> ON
>>>> BUILD_WEB_SAMPLES
>>>> ON
>>>> BUILD_WEB_SERVICE
>>>> ON
>>>> CMAKE_BUILD_TYPE
>>>> Debug
>>>> CMAKE_INSTALL_PREFIX /opt/install-pw
>>>> CORE_CTX_ROOT
>>>> PWService
>>>> DART_TESTING_TIMEOUT
>>>> 1500
>>>> FLEX_HOME
>>>> /opt/flex
>>>> GWT_SDK_HOME
>>>> /opt/gwt-2.0.3
>>>> LOGGING_LEVEL
>>>> ERROR
>>>> LOG_PARAVIEW
>>>> OFF
>>>> LOG_PARAWEB
>>>> ON
>>>> PV_ADAPTER_EXEC
>>>> /opt/install-pw/bin/PWServer
>>>> ParaView_DIR
>>>> /opt/build-paraview
>>>> QOOXDOO_SDK_PATH
>>>> /opt/qooxdoo-1.5-sdk
>>>> VTK_DIR
>>>> /opt/build-paraview/VTK
>>>> WEB_DEPLOY
>>>> OFF
>>>> WORKING_DIR /opt/PW-work
>>>>
>>>> ----------
>>>>
>>>> Thanks for all your help with this.
>>>>
>>>> Max
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>>>> Sent: Thu 11/08/11 22:50
>>>> To: WILKINSON M.
>>>> Cc: paraview at paraview.org
>>>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>>>
>>>> Did you properly set the working directory in the CMake configuration.
>>>> If so, just try to delete the database by removing the database
>>>> directory in the working directory that you set in CMake.
>>>>
>>>> Seb
>>>>
>>>> On Thu, Aug 11, 2011 at 5:35 PM, WILKINSON M.
>>>> <maxwell.wilkinson at durham.ac.uk> wrote:
>>>>> Hi Seb
>>>>>
>>>>> To answer my previous email, I've managed to build all the components.
>>>>> I'm
>>>>> able to load each of the .war components in my browser from
>>>>> http://localhost:8080/PW/PWApp.html
>>>>>
>>>>> However when I try to load a visualization using PWApp, for example the
>>>>> wavelet dataset, I'm given the error:
>>>>>
>>>>> 'An error occured during the loading.
>>>>> org.hibernate.exception.GenericJDBCException: Cannot open connection'
>>>>>
>>>>> Are you able to suggest a solution?
>>>>>
>>>>> I have checked activemq is running using ./activemq status
>>>>>
>>>>> I'm nearly there!
>>>>>
>>>>> Thanks
>>>>> Max
>>>>>
>>>>> -----Original Message-----
>>>>> From: WILKINSON M.
>>>>> Sent: Thu 11/08/11 21:19
>>>>> To: Sebastien Jourdain
>>>>> Subject: RE: [Paraview] ParaViewWeb build - PWServer
>>>>>
>>>>> Hi Seb
>>>>>
>>>>> Thanks for your reply, I understand the ccmake process now. I've
>>>>> managed
>>>>> to
>>>>> build PWServer and PWService.
>>>>>
>>>>> I've added:
>>>>> PWService.war to ../tomcat/webapps/
>>>>> pw-config.properties to ../tomcat/lib/
>>>>>
>>>>> However, the host cannot find http://localhost:8080/PWService
>>>>>
>>>>> If I go to http://localhost:8080/ I get the tomcat default home page,
>>>>> so
>>>>> I
>>>>> think tomcat is working okay.
>>>>>
>>>>> From within ccmake, there was no entry for CORE_SERVICE_URL available,
>>>>> so
>>>>> I
>>>>> could not specify http://localhost:8080/PWService
>>>>>
>>>>> The ccmake parameters available are as follows:
>>>>>
>>>>> ../build-pw$ ccmake ../ParaViewWeb/
>>>>>
>>>>> ACTIVEMQ_CPP
>>>>> /usr/local/lib/libactivemq-cpp.so
>>>>> ACTIVEMQ_INCLUDE_DIR
>>>>> /usr/local/include/activemq-cpp-3.4.0
>>>>> ANT_EXECUTABLE
>>>>> /usr/share/ant/bin/ant
>>>>> BUILD_CONSOLE_SAMPLE
>>>>> ON
>>>>> BUILD_FLEX_RENDERER
>>>>> OFF
>>>>> BUILD_MANTA_SAMPLE
>>>>> OFF
>>>>> BUILD_PW_SERVER
>>>>> ON
>>>>> BUILD_REMOTE_LAUNCHER
>>>>> OFF
>>>>> BUILD_SANDBOX_SAMPLE
>>>>> OFF
>>>>> BUILD_SHUTTLE
>>>>> ON
>>>>> BUILD_SIMPLE_JS
>>>>> ON
>>>>> BUILD_STATE_APP_BUILDER
>>>>> ON
>>>>> BUILD_TESTING
>>>>> ON
>>>>> BUILD_WEB_APPLICATION
>>>>> OFF
>>>>> BUILD_WEB_SAMPLES
>>>>> OFF
>>>>> BUILD_WEB_SERVICE
>>>>> ON
>>>>> BZRCOMMAND
>>>>> BZRCOMMAND-NOTFOUND
>>>>> CMAKE_AR
>>>>> /usr/bin/ar
>>>>> CMAKE_BUILD_TYPE
>>>>> Debug
>>>>> CMAKE_COLOR_MAKEFILE
>>>>> ON
>>>>> CMAKE_CXX_COMPILER
>>>>> /usr/bin/c++
>>>>> CMAKE_CXX_FLAGS
>>>>> CMAKE_CXX_FLAGS_DEBUG
>>>>> -g
>>>>> CMAKE_CXX_FLAGS_MINSIZEREL -Os
>>>>> -DNDEBUG
>>>>> CMAKE_CXX_FLAGS_RELEASE -O3
>>>>> -DNDEBUG
>>>>> CMAKE_CXX_FLAGS_RELWITHDEBINFO -O2
>>>>> -g
>>>>> CMAKE_C_COMPILER
>>>>> /usr/bin/gcc
>>>>> CMAKE_C_FLAGS
>>>>> CMAKE_C_FLAGS_DEBUG
>>>>> -g
>>>>> CMAKE_C_FLAGS_MINSIZEREL -Os
>>>>> -DNDEBUG
>>>>> CMAKE_C_FLAGS_RELEASE -O3
>>>>> -DNDEBUG
>>>>> CMAKE_C_FLAGS_RELWITHDEBINFO -O2
>>>>> -g
>>>>> CMAKE_EXE_LINKER_FLAGS
>>>>> CMAKE_EXE_LINKER_FLAGS_DEBUG
>>>>> CMAKE_EXE_LINKER_FLAGS_MINSIZE
>>>>> CMAKE_EXE_LINKER_FLAGS_RELEASE
>>>>> CMAKE_EXE_LINKER_FLAGS_RELWITH
>>>>> CMAKE_INSTALL_PREFIX
>>>>> /home/max/Downloads/install-pw
>>>>> CMAKE_LINKER
>>>>> /usr/bin/ld
>>>>> CMAKE_MAKE_PROGRAM
>>>>> /usr/bin/make
>>>>> CMAKE_MODULE_LINKER_FLAGS
>>>>> CMAKE_MODULE_LINKER_FLAGS_DEBU
>>>>> CMAKE_MODULE_LINKER_FLAGS_MINS
>>>>> CMAKE_MODULE_LINKER_FLAGS_RELE
>>>>> CMAKE_MODULE_LINKER_FLAGS_RELW
>>>>> CMAKE_NM
>>>>> /usr/bin/nm
>>>>> CMAKE_OBJCOPY
>>>>> /usr/bin/objcopy
>>>>> CMAKE_OBJDUMP
>>>>> /usr/bin/objdump
>>>>> CMAKE_RANLIB /usr/bin/ranlib
>>>>> CMAKE_SHARED_LINKER_FLAGS
>>>>> CMAKE_SHARED_LINKER_FLAGS_DEBU
>>>>> CMAKE_SHARED_LINKER_FLAGS_MINS
>>>>> CMAKE_SHARED_LINKER_FLAGS_RELE
>>>>> CMAKE_SHARED_LINKER_FLAGS_RELW
>>>>> CMAKE_SKIP_RPATH
>>>>> OFF
>>>>> CMAKE_STRIP
>>>>> /usr/bin/strip
>>>>> CMAKE_USE_RELATIVE_PATHS
>>>>> OFF
>>>>> CMAKE_VERBOSE_MAKEFILE
>>>>> OFF
>>>>> CORE_CTX_ROOT
>>>>> PWService
>>>>> COVERAGE_COMMAND
>>>>> /usr/bin/gcov
>>>>> CTEST_SUBMIT_RETRY_COUNT
>>>>> 3
>>>>> CTEST_SUBMIT_RETRY_DELAY
>>>>> 5
>>>>> CVSCOMMAND
>>>>> CVSCOMMAND-NOTFOUND
>>>>> CVS_UPDATE_OPTIONS -d -A
>>>>> -P
>>>>> DART_TESTING_TIMEOUT
>>>>> 1500
>>>>> GITCOMMAND
>>>>> /usr/bin/git
>>>>> GWT_SDK_HOME
>>>>> HGCOMMAND
>>>>> HGCOMMAND-NOTFOUND
>>>>> Java_JAR_EXECUTABLE
>>>>> /usr/bin/jar
>>>>> Java_JAVAC_EXECUTABLE
>>>>> /usr/bin/javac
>>>>> Java_JAVA_EXECUTABLE
>>>>> /usr/lib/jvm/java-6-sun-1.6.0.26/jre/bin/java
>>>>> LOGGING_LEVEL
>>>>> ERROR
>>>>> LOG_PARAVIEW
>>>>> OFF
>>>>> LOG_PARAWEB
>>>>> ON
>>>>> MAKECOMMAND /usr/bin/make
>>>>> -i
>>>>> MEMORYCHECK_COMMAND
>>>>> MEMORYCHECK_COMMAND-NOTFOUND
>>>>> MEMORYCHECK_SUPPRESSIONS_FILE
>>>>> PV_ADAPTER_EXEC
>>>>> /home/max/Downloads/install-pw/bin/PWServer
>>>>> ParaView_DIR
>>>>> /home/max/Downloads/build-paraview
>>>>> SCPCOMMAND
>>>>> /usr/bin/scp
>>>>> SITE
>>>>> Vostro
>>>>> SLURM_SBATCH_COMMAND
>>>>> SLURM_SBATCH_COMMAND-NOTFOUND
>>>>> SLURM_SRUN_COMMAND
>>>>> SLURM_SRUN_COMMAND-NOTFOUND
>>>>> SVNCOMMAND
>>>>> SVNCOMMAND-NOTFOUND
>>>>> TCL_LIBRARY
>>>>> TK_LIBRARY
>>>>> WEB_DEPLOY
>>>>> OFF
>>>>> WORKING_DIR
>>>>> /home/max/Downloads/PW-work
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------------------
>>>>>
>>>>> Could you suggest how to display CORE_SERVICE_URL and FLEX_HOME within
>>>>> ccmake?
>>>>>
>>>>> I think then the deployment should be successful.
>>>>>
>>>>> Thanks for your help.
>>>>>
>>>>> Max
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>>>>> Sent: Thu 11/08/11 01:05
>>>>> To: WILKINSON M.
>>>>> Cc: paraview at paraview.org
>>>>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>>>>
>>>>> Hi Max,
>>>>>
>>>>> the wiki might be confusing, but each time the CMake step are similar
>>>>> in the sense that the wiki highlight each property setting needed for
>>>>> each individual component of ParaViewWeb, but as you might want to
>>>>> build the "full" ParaViewWeb, you should setup everything at once. No
>>>>> need to stop/start CMake as many time as ParaViewWeb has components.
>>>>>
>>>>> Seb
>>>>>
>>>>> On Wed, Aug 10, 2011 at 5:13 PM, WILKINSON M.
>>>>> <maxwell.wilkinson at durham.ac.uk> wrote:
>>>>>> Hi Seb,
>>>>>>
>>>>>> I haven't got to deployment just yet, I'm trying to build PWService at
>>>>>> the
>>>>>> moment.
>>>>>>
>>>>>> For PWServer, I downloaded activemq-cpp 3.4.0 as source and compiled
>>>>>> using
>>>>>> the instructions in the wiki:
>>>>>>
>>>>>> ----------
>>>>>> ActiveMQ-CPP
>>>>>>
>>>>>> ActiveMQ-CPP is needed for the compilation and the execution of the
>>>>>> application. Therefore, you will need to download the source files at
>>>>>> the
>>>>>> following url http://activemq.apache.org/cms/download.html. As of
>>>>>> (06/28/2010) activemq-cpp 3.2 appears to have a bug in it. Please use
>>>>>> activemq-cpp 3.1.x. Then you will need to build that library. The
>>>>>> command
>>>>>> line given below are for Unix systems.
>>>>>>
>>>>>> > ./configure
>>>>>> > make
>>>>>> > sudo make install
>>>>>>
>>>>>> Make sure that you have all the dependency needed to build this
>>>>>> library.
>>>>>> Here are the required package for Debian/Ubuntu:
>>>>>>
>>>>>> apt-get install build-essential libaprutil1-dev libapreq2-dev
>>>>>> apache2-utils
>>>>>> python-dev cmake-curses-gui uuid-dev libapr1 libapreq2-dev
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> In order to build PWService, should I continue to use the ./build-pw
>>>>>> and
>>>>>> ./install-pw directories carried over from the build of PWServer?
>>>>>>
>>>>>> I'm following the instructions from the wiki, given below:
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> Configuration and building
>>>>>>
>>>>>> The PWService do not require any sample to work, therefore we will
>>>>>> focusing
>>>>>> on building only the core service with all the settings that are
>>>>>> mandatory.
>>>>>> The command line given below are for Unix systems and paths are given
>>>>>> as
>>>>>> example.
>>>>>>
>>>>>> > mkdir build-pw install-pw <---- Optional if you've done
>>>>>> > cd build-pw <---- it for ParaviewAdapter
>>>>>> > ccmake ../SOURCE_DIR
>>>>>>
>>>>>> ----------
>>>>>>
>>>>>> Should the ccmake source directory be set to ../ParaViewWeb or should
>>>>>> I
>>>>>> use
>>>>>> one of the sub-directories?
>>>>>>
>>>>>> I'm hoping to have the sample applications running soon!
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Max
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>>>>>> Sent: Wed 10/08/11 19:51
>>>>>> To: WILKINSON M.
>>>>>> Cc: paraview at paraview.org
>>>>>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>>>>>
>>>>>> Hi Max,
>>>>>>
>>>>>> Great ! Did you managed to deploy and test the sample applications
>>>>>> yourself
>>>>>> ?
>>>>>> Just to my knowledge how did you install activemq-cpp ? Did you used
>>>>>> your system package system or you build it from the source ?
>>>>>>
>>>>>> Thanks for your feedback,
>>>>>>
>>>>>> Seb
>>>>>>
>>>>>> On Wed, Aug 10, 2011 at 12:40 PM, WILKINSON M.
>>>>>> <maxwell.wilkinson at durham.ac.uk> wrote:
>>>>>>> Hi Seb
>>>>>>>
>>>>>>> Thanks for the swift reply. I now have PWServer compiled using
>>>>>>> activemq-cpp
>>>>>>> 3.4.0, all tests were passed and it is now installed :)
>>>>>>>
>>>>>>> Max
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Sebastien Jourdain [mailto:sebastien.jourdain at kitware.com]
>>>>>>> Sent: Wed 10/08/11 16:56
>>>>>>> To: WILKINSON M.
>>>>>>> Cc: paraview at paraview.org
>>>>>>> Subject: Re: [Paraview] ParaViewWeb build - PWServer
>>>>>>>
>>>>>>> Moreover, all the version of activemq-cpp can be found here:
>>>>>>> http://activemq.apache.org/cms/download.html
>>>>>>>
>>>>>>> On Wed, Aug 10, 2011 at 11:54 AM, Sebastien Jourdain
>>>>>>> <sebastien.jourdain at kitware.com> wrote:
>>>>>>>> Hi Max,
>>>>>>>>
>>>>>>>> there is two things happening here.
>>>>>>>>
>>>>>>>> The first one is related to an API change in ActiveMQ-cpp which
>>>>>>>> induce
>>>>>>>> this compilation issue. Although it happen that I was working on
>>>>>>>> that
>>>>>>>> part lately and managed to use activemq-cpp 3.4 on a linux machine.
>>>>>>>> To
>>>>>>>> do so, you will need to edit the ParaViewWeb source code. I've paste
>>>>>>>> the small diff at the end of that mail.
>>>>>>>>
>>>>>>>> The second issue is related to the ParaView version that you are
>>>>>>>> using. Before getting further, you should either use 3.10.1 or
>>>>>>>> git/master. But depending on the version, you have to checkout a
>>>>>>>> given
>>>>>>>> tag on the ParaViewWeb git repository.
>>>>>>>>
>>>>>>>> Hope this help,
>>>>>>>>
>>>>>>>> Seb
>>>>>>>>
>>>>>>>> ====================================
>>>>>>>> In file : /ParaViewAdapter/vtkPWJMSMessagingService.cxx
>>>>>>>>
>>>>>>>> -vtkPWJMSMessagingService::~vtkPWJMSMessagingService()
>>>>>>>> +vtkPWJMSMessagingService::~vtkPWJMSMessagingService() throw()
>>>>>>>>
>>>>>>>> [...]
>>>>>>>>
>>>>>>>> -void vtkPWJMSMessagingService::onMessage(const cms::Message
>>>>>>>> *message)
>>>>>>>> +void vtkPWJMSMessagingService::onMessage(const cms::Message
>>>>>>>> *message)
>>>>>>>> throw()
>>>>>>>>
>>>>>>>> In file: /ParaViewAdapter/vtkPWJMSMessagingService.h
>>>>>>>>
>>>>>>>> - void onMessage(const cms::Message *message);
>>>>>>>> + void onMessage(const cms::Message *message) throw();
>>>>>>>>
>>>>>>>> [...]
>>>>>>>>
>>>>>>>> - ~vtkPWJMSMessagingService();
>>>>>>>> + ~vtkPWJMSMessagingService() throw();
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>
>
More information about the ParaView
mailing list