://activemq.apache.org/download.html
-Jerry
On Wed, Sep 21, 2016 at 4:52 PM, Jaroslaw Cwiklik wrote:
> Not sure what is causing this. I need to stage this with UIMA-AS 2.8.1. I
> am currently testing with trunk (latest) code. The most current code does
> have newer broker.
>
> I've started a
any idea that what happen?
>
> 2016-09-21 16:09 GMT-04:00, Jaroslaw Cwiklik :
> > Which version of UIMA-AS are you using?
> >
> > -Jerry
> >
> > On Wed, Sep 21, 2016 at 3:42 PM, nelson rivera >
> > wrote:
> >
> >> When start ActiveMQ a
Which version of UIMA-AS are you using?
-Jerry
On Wed, Sep 21, 2016 at 3:42 PM, nelson rivera
wrote:
> When start ActiveMQ and deploys an annotator as service, processing is
> executed correctly, but when the broker is stopped and subsequently
> restarted. UIMA-AS log show the lines below and
Can you just write out the component descriptor to a file and pass that to
the factory? I think you need a path since
the underlying code needs uima-style include which supports import by name
or location. Perhaps CPE can do this for you
with a new API you are suggesting but I the quickest path for
get more information with a increased
> log level, and get back to you.
>
> Thanks again!
>
> Regards,
>
> Egbert
>
>
> Op 25-8-2016 om 17:17 schreef Jaroslaw Cwiklik:
>
> Hi, I have a feeling that there might be a race condition here. In the
>> client, the
Hi, I have a feeling that there might be a race condition here. In the
client, the timer pops and at the same time a reply is received.
The timout logic is resetting the CAS while its being deserialized which
may lead to NPE. Not 100% certain but this might be the problem.
Any chance you can incre
The Apache UIMA team is pleased to announce the release of the UIMA DUCC,
version 2.1.0.
DUCC stands for Distributed UIMA Cluster Computing. DUCC is a cluster
management system providing tooling, management, and scheduling facilities
to automate the scale-out of applications written to the UIMA fr
Matthias, I will create a JIRA for this so that it can be addressed for the
next UIMA-AS release For some reason I have not seen this type of problem
when running regression tests. Thank you for discovering this and finding
the fix.
Jerry
On Fri, Aug 5, 2016 at 3:16 AM, Matthias Koch
wrote:
> H
Hello Yamen, you can deploy uima-as service on a node which does not have a
broker. One of the benefits of JMS is location transparency. The broker can
run on any node in a cluster and mediates messages between client(s) and
service(s). A service connects to a broker and registers its queue. Client
The Apache UIMA team is pleased to announce the release of the Apache
UIMA-AS version 2.8.1, which includes asynchronous scaleout capabilities
for the UIMA annotators.
UIMA-AS includes the base UIMA SDK and augments it with scaleout
capability; it is a next-generation replacement for the original
I think this is import by name so no need for .xml at the end.
Try: classpath*:Users/anni/ /typesystem
Jerry
On Thu, Apr 28, 2016 at 5:06 PM, Anni R Coden wrote:
> Hi -
>
> I am using UIMAfit
>
> I created a a file: META-INF/org.apache.uima.fit/types.txt
>
> in the file I put
>
> c
Forgot to add a link to documentation where import by location is described:
https://uima.apache.org/d/uimaj-current/references.html#ugr.ref.xml.component_descriptor.imports
Jerry
On Tue, Apr 26, 2016 at 9:03 AM, Jaroslaw Cwiklik wrote:
> Not familiar with this code but it appears that
Not familiar with this code but it appears that the CPE GUI only supports
import by location:
CpmPanel.java
private boolean addAE(CpeCasProcessor cpeCasProc) throws
CpeDescriptorException,
InvalidXMLException, IOException, ResourceConfigurationException {
URL aeSpecifierUrl =
cpeCa
ery
> interested.
> Sylvain
>
> 2015-12-21 19:55 GMT+01:00 Jaroslaw Cwiklik :
>
> > Hi, the UIMA-AS currently works with ActiveMQ only. Perhaps we should
> take
> > a look at refactoring UIMA-AS to make it possible to use a different JMS
> > provider. So far
Hi, the UIMA-AS currently works with ActiveMQ only. Perhaps we should take
a look at refactoring UIMA-AS to make it possible to use a different JMS
provider. So far there was no demand for this.
Jerry
On Mon, Dec 21, 2015 at 12:26 PM, Sylvain Surcin
wrote:
> Hi,
>
> Is it possible to configure
Yes, the new release will have the latest ActiveMQ v.5.12.1 which comes
with Spring Framwork v.3.2.11.
Jerry
On Tue, Dec 8, 2015 at 10:52 AM, Peter Klügl
wrote:
> Hi,
>
> are there plans concerning the spring versions?
>
> Best,
>
> Peter
>
> Am 08.12.2015 um 16:
Mihaela, I am working on the new UIMA-AS release right now. It will include
the UIMA SDK 2.8.1, ActiveMQ 5.12.1, and a few fixes and features like:
- Fixed Performance Metrics for Async Aggregates
- Prime AEs before processing
- Fixed Eclipse Runtime Configurations
The new release should be avail
If I understand your question correctly, you can use a Flow Controller to
determine which part of the pipeline should be called next. UIMA-AS uses a
static deployment descriptor where you declare your remote and collocated
parts of the pipeline. The Flow Controller is responsible for orchestrating
The Apache UIMA team is pleased to announce the release of the UIMA DUCC,
version 2.0.1.
DUCC stands for Distributed UIMA Cluster Computing. DUCC is a cluster
management system providing tooling, management, and scheduling facilities
to automate the scale-out of applications written to the UIMA fr
t;>> Is there any changes regarding job descriptor or service descriptor?
The
>>> both did not work in my case for DUCC 2.0.0 but for DUCC 1.0.0 and DUCC
>>> 1.1.0.
>>>
>>> In Service descriptor it shows some spring Framework's class not found
>>> exception. See below:
>
Hi, can you try Ducc 2.0.0? It was recently released into Apache. One of
the key changes was to remove queues as means of transport between JD (Job
Driver) and JP (Job Process). Instead, each JP uses HTTP to request a Work
Item (CAS) from a JD.
DUCC 1.1.0 has a concept of a WI timeout which I thin
The Apache Maven team is pleased to announce the release of the UIMA DUCC,
version 2.0.0.
DUCC stands for Distributed UIMA Cluster Computing. DUCC is a cluster
management system providing tooling, management, and scheduling facilities
to automate the scale-out of applications written to the UIMA f
The UIMA-AS *does* have an API to generate deployment descriptors although
its not documented. Its an internal API for now and most likely will be
documented in the next release of UIMA-AS. The API is implemented by
DeploymentDescriptorFactory.java. in the uimaj-as-core project.
Jerry
On Thu, Ju
In async aggregate you scale individual AEs not the aggregate as a whole.
The below configuration should do that. Are there any warnings from
dd2spring at startup with your configuration?
Not sure if this is the cause but check if your AE descriptor has this
true
Jerry
On Mon, Apr 13, 2015 at 12:07 PM, Eddie Epstein wrote:
> The CPE runs pipeline threads in parallel, not necessarily CAS processors.
> In a CPE descriptor, generally all non-CasConsumer components make up the
> pip
:Command=2000 OR
> Command=2002.
> Feb 19, 2015 5:39:56 PM org.apache.uima.adapter.jms.activemq.JmsInputChannel
> stopChannel
> INFO: Stopping Service JMS Transport. Service: ducc.jd.queue.13202
> ShutdownNow true
> Feb 19, 2015 5:39:56 PM org.apache.uima.adapter.jms.activemq.JmsInput
One possible explanation for destroy() not getting called is that a process
(JP) may be still working on a CAS when Ducc deallocates the process. Ducc
first asks the process to quiesce and stop and allows it 1 minute to
terminate on its own. If this does not happen, Ducc kills the process via
kill
1.What are Heartbeat Packets?
Ducc Agent publishes node metrics at regular intervals. The information
included is node identification, OS info, memory, etc. This is consumed by
the RM and WS. If the RM stops seeing publication from a node within a
configurable window, it will mark the node as d
contains fixes and improvements over
UIMA DUCC 1.0.0.
For a full list of changes, please refer to Jira:
http://uima.apache.org/d/uima-ducc-1.1.0/issuesFixed/jira-report.html
More information about UIMA DUCC can be found here:
http://uima.apache.org/doc-uimaducc-whatitam.html
- Jaroslaw Cwiklik
When you initialize uima-as client, how big is the CasPool? The default is
1 which might explain what you are seeing.
Try increasing a CasPool on the client side to improve the throughput.
Map appCtx = new HashMap();
appCtx.put(UimaAsynchronousEngine.ServerUri, brokerURL);
appCtx.put(UimaAsynchron
This error comes from UIMA-AS client not the pipeline code. From what I can
see
the UIMA-AS received getMeta reply from the service (your pipeline). This
means
that it connected to the service and it received a reply.
The only thing that comes to my mind is to check the Map that you pass in
to the
The Apache UIMA team is pleased to announce the release of version 2.6.0 of
the Apache
UIMA AS, which includes asynchronous scaleout capabilities for the UIMA
annotators.
The UIMA AS 2.6.0 binaries and source are available for download from:
http://uima.apache.org/downloads.cgi
UIMA AS includes t
Hi, the UIMA-AS 2.6.0 release is being voted right now. If no issues are
found it should release soon.
The UIMA-DUCC uses UIMA-AS. It just extends it with extra capabilities. You
can learn more
about it here: https://uima.apache.org/doc-uimaducc-whatitam.html
Jerry
On Mon, Jun 23, 2014 at 1:54
ound occurrences of
> System.exit(), which is quite fatefull when running within a shared JVM ;)
>
> Thanks and all the best
> Frank
>
> Am 12.06.2014 16:09, schrieb Jaroslaw Cwiklik:
> > All you need is a reference to a thread that called sendAndReceive().
> Once
> > you have
RNING: Request To Process Cas Has Timed-out. Service
Queue:SlowNoOpAnnotatorQueue1. Broker: tcp://localhost.localdomain:61617
Cas Timed-out on host: 192.168.6.65
Jerry
On Wed, Jun 11, 2014 at 6:30 PM, Frank Enders
wrote:
> Hi Jerry,
>
> Am 10.06.2014 21:27, schrieb Jaroslaw Cwiklik:
her recover after the broker gets restarted
> nor time out when UimaAsynchronousEngine.Timeout is reached.
>
> Is this the expected behaviour when a broker is getting terminated
> unexpectedly?
>
> Thanks and all the best
> Frank
>
> Am 22.04.2014 15:22, schrieb Jaroslaw
You can use UIMA-AS client API. All you need to know is the endpoint and
the broker url to communicate.
Jerry C
On Wed, May 28, 2014 at 8:53 AM, reshu.agarwal wrote:
>
> Hi,
>
> I am just curious about DUCC Service uses. Can we call Ducc Service using
> UIMA AS client API. Or there is any API i
Hi, do you see any evidence in the service log of any problems? The client
side will block in sendAndReceive() until a reply comes back from the
service.
You 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
Each UIMA-AS service should produce uima.log. Is there another exception
preceding
org.apache.uima.aae.error.AsynchAEException: javax.jms.JMSException: JMS
Send Failed. Check UIMA Log For Details.
Looks like the service was unable to deliver an ACK message to the client.
This ACK
message is a conf
til the reply
> and because that method is synchronized, it won't be able to send further
> CASes to the pipeline (from other threads) and have them processed in
> parallel. Please correct me if I'm wrong.
>
> Thanks,
> Mihaela
>
>
>
>
> On Wednesday, February
Mihaela, does your REST service provide threading to handle client
requests? If so, you can consider using a shared instance of
UimaAsynchronousEngine
client. Each thread would call sendAndReceive() and block until reply
comes. This would be the most efficient way of doing this I think.
Jerry C
, Jaroslaw Cwiklik wrote:
> Got it. Thanks for clarifying this.
>
> Jerry Cwiklik
>
>
> On Tue, Feb 18, 2014 at 12:24 PM, Bai Shen wrote:
>
>> I don't need a newer version of AMQ. I was attempting to fix the SLF4J
>> issue and had to change AMQ to 5.7 just to ge
d any problems with using 5.7 instead of 5.6.
>
> The problem with the test cases is from removing the SLF4J dependencies
> from the UIMA pom.
>
> Just wanted to clarify that they are two separate issues.
>
>
> On Tue, Feb 18, 2014 at 11:32 AM, Jaroslaw Cwiklik
> wrote:
>
gt;
> On Tue, Feb 18, 2014 at 12:52 PM, Jaroslaw Cwiklik
> wrote:
>
> > Got it. Thanks for clarifying this.
> >
> > Jerry Cwiklik
> >
> >
> > On Tue, Feb 18, 2014 at 12:24 PM, Bai Shen
> > wrote:
> >
> > > I don't need a newer
m referring to is explained here.
>
> https://stackoverflow.com/questions/12938083/what-where-is-net-sf-josql
>
>
>
>
> On Tue, Feb 18, 2014 at 10:20 AM, Jaroslaw Cwiklik
> wrote:
>
> > Hi, thanks for spotting references to 5.4.1. I will create JIRA and fix
> > these. Th
Hi, thanks for spotting references to 5.4.1. I will create JIRA and fix
these. The fixes will be in the next release.
I will take a look at SLF4J to see if this can be fixed. From what I
remember this is just a Warning not a Fatal
condition. Nevertheless, its worth looking into. Will create JIRA t
It seems like the ActimeMQ documentation (
http://activemq.apache.org/configuring-wire-formats.html)
is wrong with respect to the default maxFrameSize being MAX_LONG. I checked
ActiveMQ source code and the default is 100 MB:
public final class OpenWireFormat implements WireFormat {public
stati
:
http://uima.apache.org/
Jaroslaw Cwiklik, on behalf of the Apache UIMA Community
ill be out?
> Ryan
>
>
> On 1/23/14, 2:37 PM, "Jaroslaw Cwiklik" wrote:
>
> >The UIMA-AS client code calls onBeforeMessageSend() for both Process and
> >CPC requests. Its just a confirmation the request was delivered to a
> >queue.
> >From what I see
The UIMA-AS client code calls onBeforeMessageSend() for both Process and
CPC requests. Its just a confirmation the request was delivered to a queue.
>From what I see while trying to replicate the scenario is that on CPC the
status object (passed in to onBeforeMessageSend() )contains a reference to
The Apache UIMA team is pleased to announce the release of version 2.4.2 of
the Apache
UIMA AS, which includes asynchronous scaleout capabilities for the UIMA
annotators.
The UIMA AS 2.4.2 binaries and source are available for download from:
http://uima.apache.org/downloads.cgi
UIMA AS includes t
Not knowing your particular CPE deployment details here is one way to
programmatically configure the CR:
CollectionProcessingEngine cpe =
UIMAFramework.produceCollectionProcessingEngine(cpeDescriptor, params);
cpe.getCollectionReader().getProcessingResourceMetaData().getConfigurationParame
Is your application calling UIMA-AS client collectionProcessComplete()
method?
-
void collectionProcessingComplete(): Sends a Collection Processing
Complete request to the UIMA-AS Analysis Service. This call is cascaded
down to all delegates; however, if a particular delegate is scal
The problem is with the implementation.
I will be working on solving this shortly. Should be fixed in the upcoming
2.4.2 uima-as release.For now I created JIRA for this problem
https://issues.apache.org/jira/browse/UIMA-3160
JC
JC
On Wed, Aug 7, 2013 at 3:19 PM, Jaroslaw Cwiklik wrote:
> Inst
Instead of speculating, I decided to setup a test with similar
configuration ( casPool=6) and am noticing similar
problem. It appears that the input queue is drained one CAS at a time as if
there was only one thread processing
an input queue.
Investigating...
JC
On Wed, Aug 7, 2013 at 3:14 PM,
, 2013 at 2:43 PM, Marshall Schor wrote:
>
> On 8/7/2013 2:07 PM, Jaroslaw Cwiklik wrote:
> > When you launch your service, do you see a Warning similar to this:
> >
> > *** WARN: line-number: 30 Top Lovel Async Primitive specifies a scaleout
> of
> > numberOfIn
When you launch your service, do you see a Warning similar to this:
*** WARN: line-number: 30 Top Lovel Async Primitive specifies a scaleout of
numberOfInstances="1", but also specifies a Cas Pool size of
numberOfCASes="6". The Cas Pool size is being forced to be the same as the
scaleout.
If yes
UIMA-AS and Camel integration is described in Chapter 6 Uima Async Scaleut
document:
http://uima.apache.org/d/uima-as-2.4.0/uima_async_scaleout.html#ugr.async.camel.driver
Its essentially a thin camel wrapper around UIMA-AS client. Its quite dated
and may not
work with newer versions of Camel. Th
igure this scenario.
>
>
>
>
> On 07/26/2013 06:42 PM, Jaroslaw Cwiklik wrote:
>
>> Do you want to share your code across nodes? If so, use Network File
>> System
>> (NFS)
>>
>> JC
>>
>>
>> On Fri, Jul 26, 2013 at 12:02 AM, reshu.agarwal &
> --
> Reshu Agarwal
>
>
>
>
> On 07/25/2013 08:02 PM, Jaroslaw Cwiklik wrote:
>
>> If I understand your scenario, you only need one broker.Services can be
>> deployed an different machines and point to the same
>> queue (endpoint) and broker (brokerURL) defined
AM, reshu.agarwal wrote:
> On 07/24/2013 06:13 PM, Jaroslaw Cwiklik wrote:
>
>> The "...Cannot publish to a deleted Destination.." is caused by a broker
>> not being able to deliver a message to a
>> given queue. It looks like the client has terminated and the b
If I understand your scenario, you only need one broker.Services can be
deployed an different machines and point to the same
queue (endpoint) and broker (brokerURL) defined in the deployment
descriptor.
JC
On Thu, Jul 25, 2013 at 7:49 AM, reshu.agarwal wrote:
>
> Hi,
>
> I want to consume the m
The "...Cannot publish to a deleted Destination.." is caused by a broker
not being able to deliver a message to a
given queue. It looks like the client has terminated and the broker deleted
its temp reply queue while the service
was processing a CAS.
JC
On Wed, Jul 24, 2013 at 12:11 AM, reshu.a
Have you deployed RoomNumberAnnotator service first? Use
Deploy_RoomNumberAnnotator.xml to launch it.
JC
On Tue, Jul 16, 2013 at 1:32 AM, Reshu Agarwal wrote:
>
> Hii...
>
> If I try to run the Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml {example
> deployment xml} the following error is give
Hi, there were recent changes to the AnalysisEnginePerformanceMetrics
class. Specifically a name of one if its internal attributes changed from
uniqueName to uimaContextPath. Afterwords, I realized that such change
breaks compatibility with older installations and reverted the name back to
uniqueNa
Hi, is this problem reproducable? This error happens when the uima-as is
unable to deliver a reply to the client. Typically, this means that the
uima-as client
has gone away or there is a problem with the network. Are you running your
client and service and the same machine?
Not sure what else cou
As a followup, can you describe your uima-as deployment? Is it async
aggregate or primitive? If aggregate, what are the delegates and how each
is scaled?
Jerry C
On Thu, Jun 6, 2013 at 11:20 AM, Jaroslaw Cwiklik wrote:
> I frequently run UIMA-AS with scaled up AEs in the same jvm with
I frequently run UIMA-AS with scaled up AEs in the same jvm with no
problems. The UIMA-AS calls defineCasPool() once
when all AEs are instantiated.
The uima-core code that throws the exception is in
CasManager_impl.defineCasPool()
private synchronized void defineCasPool(UimaContext aRequestorCon
Florin, try the latest uima-as (2.4.0) and let me know if you can replicate
the problem.
There are many bug fixes in the latest code.
-jc
On Mon, Apr 15, 2013 at 5:58 AM, Spico Florin wrote:
> Hello!
>I'm using UIMA AS 2.3.1. My pipeline has this structure:
>
> 1. An entry AAE
> 2. One re
on, what is the mechanism behind the CAS pool used by
> the client BaseUIMAAsynchronousEngineCommon in the following terms:
>
> 1. what should be the pool size depending on the hw?
> 2. how CAS lifecycle is managed by the pool? Maning creting a new one,
> releasing, getting from the po
Hi, do you have a deeply nested CMs in your pipeline? Is the top level
UIMA-AS service (the one the client is sending CASes to) a CM?
What you can do to debug this is to use jConsole attached to the UIMA-AS
process once you observe a hang. Click on Threads tab
and check each thread to determine w
Spico, both of these:
stopProducingCases()
stopProducingCases(String casReferenceId);
were meant to stop remote UIMA-AS CM from producing child CASes.
So the first question is, is your remote service (UIMA-AS pipeline) a CM?
If it is, what is the behavior that you are seeing? A hang?
If the rem
Elmar, this seems to be a bug. Just to clarify, are you deploying the
aggregate in the same jvm as the
RunRemoteAsyncAE? The client's stop() method is not waiting for the AE
threads to finish. Its doing an immediate
stop. The 2.4.0 version of UIMA-AS does support Queisce mode where the
service wai
Florin, the newly released UIMA-AS 2.4.0 provides performance breakdown you
are looking for.
There is a new API on UIMA-AS client that facilitates this:
public String sendAndReceiveCAS(CAS aCAS,
List componentMetricsList) throws
ResourceProcessException;
For each CAS that you send you get a lis
Hi, JMS connection in UIMA-AS is created once, cached and reused.
- Jerry C
On Tue, Dec 11, 2012 at 8:51 AM, Spico Florin wrote:
> Hello!
> I would like to know what kind of JMS connection is used by UIMA AS:
> pooled connection or each time a message is sent to a new remote component,
> a ne
The Apache UIMA team is pleased to announce the release of version 2.4.0 of
the Apache UIMA AS, which includes
asynchronous scaleout capabilities for the UIMA annotators.
The UIMA AS 2.4.0 binaries and source are available for download from:
http://uima.apache.org/downloads.cgi
UIMA AS includes t
Not sure I fully understand your problem. In the CPE, the CR runs in its
own thread supplying CASes to processing pipelines.
Cas Consumer(s) run in a dedicated thread(s) as well.
The processingUnitThreadCount property determines scaleout for your AEs
if you set it to say 3, you get 3 processing thr
Florin, check the README that ships with the release. It says:
"...set the ACTIVEMQ_HOME environment variable to the location of
ActiveMQ you intend to use..."
Jerry
On Sat, Oct 6, 2012 at 2:46 PM, Spico Florin wrote:
> Hello!
> I have installed UIMA 2.3.1 AS that comes with ActiveMQ 5.4.1
ecial processing.
It seems to me that the StatusCallbackListener.batchProcessComplete()
should be deprecated since it is never called.
Jerry C
On Tue, Aug 7, 2012 at 11:32 AM, Jaroslaw Cwiklik wrote:
> Christine, I took another look at this and tested the code. You are right,
> the
Christine, I took another look at this and tested the code. You are right,
the listener's batchProcessComplete() is not called no matter what the
batchSize is set to.
I think the real intent for the element within
is to define a checkpoint file and frequency of checkpoints.
The CPE saves its
pro
If I recall, you need to modify element and set "batch"
attribute to enable this
function. I think, by default this method is not called since batch=0
(default).
JC
On Tue, Jul 31, 2012 at 3:22 PM, Christine Engelmann
wrote:
> Hi,
>
> I seem to have some issues with the batchProcessComplete()-m
It seems like a CPM hung of some sort while running a jUnit tests. Does
this happen every time you do mvn install?
I just fetched 2.3.1 source and built fine on Win XP with java 1.5 and
maven 3.0.2. I built multiple times each time with success. Not denying
there is a problem, just saying cant rep
Peter, I don't recall a specific reason why Exceptions caught in
ArtifactProducts.run()
method are only logged at Level.FINER. This seems wrong to me. I remember
putting
conditionals around all logging though. Perhaps this was a cut and paste
mistake. I'll
add JIRA to fix this.
If you want to hand
u
>
>
>
>
> On Jun 20, 2012, at 1:03 PM, Jaroslaw Cwiklik wrote:
>
> > I've checked the code and indeed this is a bug in uima-as client when
> > running with a CR. As soon as the CR
> > returns false from hasNext() the uima-as client process() method calls
&g
I've checked the code and indeed this is a bug in uima-as client when
running with a CR. As soon as the CR
returns false from hasNext() the uima-as client process() method calls
collectionProcessComplete().
The fix for this is to wait until all outstanding CASes are processed
before calling collect
Jorn, this problem has been fixed:
https://issues.apache.org/jira/browse/UIMA-2414
Jerry
On Wed, Jun 13, 2012 at 7:30 AM, Jörn Kottmann wrote:
> I am running the 2.3.1 release version on my cluster.
>
> Jörn
>
>
> On 06/13/2012 01:02 PM, Jörn Kottmann wrote:
>
>> The error was linked to my del
>From UIMA AS documentation:
"The continueOnRetryFailure attribute, if set to 'true' causes the
framework to ask the aggregate's flow controller if the processing for the
CAS can continue. If this attribute is 'false' or if the flow controller
indicates it cannot continue, further processing on th
Not sure if this the best way, but consider using different
Logger.properties (default one is in UIMA_HOME/as_config) for each
service. Change
java.util.logging.FileHandler.pattern = uima.log
to whatever you want and set
UIMA_JVM_OPTS=-Djava.util.logging.config.file=myfile
before you launch the
After you restart the broker, do you send another CAS to the remote and
does it fail for the same reason?
JC
On Fri, Mar 2, 2012 at 9:59 AM, Spico Florin wrote:
> Hello!
> I have a pipeline that is using the AdvancedFixedFlowController.xml.
> After shooting down the ActiveMQ Broker and restar
Arun, it looks like you are missing timeout setting in .
It looks like you are never timing out waiting for a reply from the remote.
JC
On Mon, Feb 27, 2012 at 1:35 AM, Arun Tewatia wrote:
> Dear all,
>
> I have been trying to configure node failure recovery for my uima-as
> cluster.
> Followi
>
> Thank you.
> Regards,
> Florin
>
> On Wed, Feb 22, 2012 at 8:24 PM, Jaroslaw Cwiklik
> wrote:
>
> > I am not certain, but perhaps you are running into a similar bug reported
> > and fixed recently under
> >
> > https://issues.apache.org/jira/browse/UI
Seems like a bug, as a workaround can you try the following:
mCPE = UIMAFramework.produceCollectionProcessingEngine();
ConfigurationParameterSettings settings =
mCPE.getCollectionReader().getProcessingResourceMetaData().getConfigurationParameterSettings();
You should be able to change
I am not certain, but perhaps you are running into a similar bug reported
and fixed recently under
https://issues.apache.org/jira/browse/UIMA-2354
Maybe the UIMA AS primitive service suffers from a similar problem than the
UIMA AS aggregate as described in the JIRA. I will verify this soon.
Anot
. None was logged.
In your test case, do you send just one CAS after bouncing the broker or
does your client send multiple CASes and each fails the same way
(InvalidDestination) in the service?
Jerry C
On Wed, Feb 8, 2012 at 2:38 PM, Jaroslaw Cwiklik wrote:
> Frank, I will try to recreate
Florin, your problem is that you are using one CAS instance with asynch
sendCAS(). Your main() is calling sendCAS(CAS) where the CAS is being
serialized. Serialization is an expensive operation and on a slow machine
may exceed your 100ms sleep. While the CAS is being serialized you calling
reset()
Frank, I will try to recreate the problem. Yesterday, I tried the scenario
with async sendCAS() and saw no problems after bouncing a broker. Will test
the scenario with sendAndReceive().
Jerry C
On Wed, Feb 8, 2012 at 9:32 AM, Frank Enders wrote:
> Jerry, thanks for your reply first of all.
>
Frank, is it possible that when you bounce a broker, the service queue
might still contain messages with a stale temp reply queue? If this is the
case, the service attempts to deliver them a temp queue which no longer
exists (broker was bounced). If your client keeps sending CASes, eventually
the o
inishes is added
> > back to the pool.
> > 4) Since you can generate CASes in the client faster than the pipeline
> can
> > process them, a Queue builds up to hold the CASes the client has
> submitted,
> > but are not yet being processed. The size of this qu
UIMA AS aggregate client waits for all replies to come back from Parallel
step before allowing a CAS to move on to the next step in the flow. From
the UIMA AS service point of view, services are independent and consume
messages(CASes) as soon there is capacity to do so. Faster service will
consume
Sorry didnt finish my thought on question #1. If you see sendCAS()
blocking, attach jConsole to the application (you may need to enable JMX),
view the threads and check where your application thread is blocking.
JC
On Wed, Feb 1, 2012 at 9:52 AM, Jaroslaw Cwiklik wrote:
> Florin from
101 - 200 of 266 matches
Mail list logo
