ithin Configured Window Of:1,000 millis
> Jun 12, 2014 10:07:17 AM
> org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngineCommon_impl
> notifyOnTimout
> WARNING: Request To Process Cas Has Timed-out. Service
> Queue:SlowNoOpAnnotatorQueue1. Broker: tcp://localhost.localdomain:61617
> Cas Timed-out on host: 19
Hi Jerry,
Am 10.06.2014 21:27, schrieb Jaroslaw Cwiklik:
The 2.4.2 AS code also supports interrupts on a thread stuck in
sendAndReceive(). You can implement your own
timer if you like, and if it pops just interrupt the thread and try calling
sendAndReceive() again. The subsequent call
should blo
can attach jconsole to the service to see if it is hung somewhere.
Please check UIMA-AS README for instructions how to configure service to
enable
jmx.
Jerry
On Tue, Apr 22, 2014 at 4:38 AM, Frank Enders wrote:
Dear all,
we are using a synchronous sendAndReceiveCAS() call within a webservice
Dear all,
we are using a synchronous sendAndReceiveCAS() call within a webservice
endpoint (JAX WS RI).
Doing so, in some cases we find hanging requests, which are not getting
completed.
I am attaching a corresponding part of a thread dump.
We are using UIMA AS 2.4.0. Application environment
Dear Roberto,
since we had similar requirements and didn't find any existing solution
we started to develop one on our ones some years ago.
Currently, besides viewing XMIs, our app is capable of working with UIMA
AS endpoints. Privileged users can start such endpoints via this gui and
recreate
Jerry, after disassembling our client, pipeline and broker configuration
I finally found out what's causing troubles:
When working with old AS 2.3.0 (and AMQ 4.x) we were used to work with a
failover transport
(http://activemq.apache.org/failover-transport-reference.html) by adding
"failover:" as p
Jerry, thanks for your reply first of all.
Pending messages don't seem to play a role in our scenario. I am just
sending single messages synchronously using sendAndReceiveCAS().
So when I restart the broker no messages are pending.
I attached jconsole to the broker in order to observe its behaviour
Dear all,
I am having problems in a UIMA AS 2.3.1 setting when restarting the
broker while endpoints are currently running and deployed to it.
After restarting the broker, JMS states correct reconnection to the
queues. But when sending a request to the endpoint I get the following
error:
javax.jm
Dear Georg,
we are working on an web based annotation tool, which allows working
with CASes, for quite a long time now.
We started to develop it within the THESEUS research programm and
continually improving it.
It enables you to manually add/remove annotations (given a specific type
system) or us
Marshall, thanks for your quick response.
> Can you provide more details on how you are seeing that Annotation in
this case
> is being translated to uima.tcas.Annotation, in your setup?
org.apache.uima.jcas.tcas.Annotation gets imported within Sentence.java:
"import org.apache.uima.jcas.tcas.Ann
Hi together,
in a TypeSystem we have a type "org.company.types.Annotation".
Now we have another type "org.company.types.Sentence" which uses
"org.company.types.Annotation" as its supertypeName.
When we generate the corresponding Java classes using JCasGen the
fully-qualified name seems to be omitt
Am 09.02.2011 17:37, schrieb Marshall Schor:
> Do all of the annotator (aggregate and primitive) xml descriptors you are
> referring to in your deployment, include a ... part in their
> metaData section?
Thanks, Marshall! There was an empty tag in the AAE's
descriptor, which caused the error. T
Hello,
when trying to deploy an engine using UIMA AS 2.3.1 RC4 it fails because
of a missing display name:
org.apache.uima.adapter.jms.activemq.SpringContainerDeployer deploy
WARNING:
java.lang.IllegalArgumentException: Display name must not be empty
at org.springframework.util.Assert.has
13 matches
Mail list logo
