On 8/25/11 12:46 AM, william.co...@gmail.com wrote:
Hi,
I am doing some experiments with UIMA AS. I create two deployment
descriptors that work fine alone, but if I try to launch both with the
command
deployAsyncService.sh Deploy01.xml Deploy02.xml
it fails. I get the following exception: Caus
On 8/24/11 8:38 PM, Richard Eckart de Castilho wrote:
I recently had trouble connecting to a JMX server running on Linux (not EC2 though). It
worked after I specified a "java.rmi.server.hostname"
The parameters I used on the server side in the end were:
-Djava.rmi.server.hostname=192.168.0.25
Hi,
I am doing some experiments with UIMA AS. I create two deployment
descriptors that work fine alone, but if I try to launch both with the
command
deployAsyncService.sh Deploy01.xml Deploy02.xml
it fails. I get the following exception: Caused by:
javax.management.MalformedObjectNameException:
I recently had trouble connecting to a JMX server running on Linux (not EC2
though). It worked after I specified a "java.rmi.server.hostname"
The parameters I used on the server side in the end were:
-Djava.rmi.server.hostname=192.168.0.25 -Dcom.sun.management.jmxremote=true
-Dcom.sun.managemen
On 8/23/11 10:48 PM, william.co...@gmail.com wrote:
Yes, I followed that instructions, but it didn't work. I tried searching
about this issue and looks like it is related to the second port you
mentioned and firewall. ActiveMQ has a configuration where one can set this
second port, but couldn't f
Meghana, make sure the ActiveMQ broker is running before starting your UIMA
AS service.
I use the following vm args to enable service jmx monitor:
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Duima.jmx.monitor.interval=1000 -Dcom.sun.management.jmxremo
As always, seconds after sending the email I finally found my Type inside the
CAS object:
myJCas.getRequiredType("de.fhg.scai.bio.uima.types.ImageArea");
(I was only looking up "ImageArea", that didn't work, but printing the
TypeSystem finally revealed what I needed )
Now it does work, with yo
Hi Richard,
I found something similar in one of your posts in the mailing list archive
before:
[...]Digging into the API again, I believe the fix should be this:
MetaData metaData = (MetaData)
jcas.getIndexRepository().getAllIndexedFS(MetaData.type).next()
[...]
If I get this
