David, I've deployed uima-as 2.9.0-SNAPSHOT here:
https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.0-SNAPSHOT/
there is a binary tarball (tar.gz) in there.
This is a trunk level uima-as code for the upcoming 2.9.0 uima-as release.
It has not been thoroughl
Another possibility is to deploy a snapshot in a public maven repo.
Hopefully you can get the binary tarball
onto your machines somehow. I will to do that know and let you know where
to get this.
-jerry
On Thu, Sep 22, 2016 at 3:01 PM, David Fox wrote:
> Building from svn on our linux machines
Building from svn on our linux machines is a bit tricky, because they are
cut off from the internet by a firewall, and maven install wants internet
access to download dependencies. It looks like there are workarounds for
that
(http://stackoverflow.com/questions/7233328/how-do-i-configure-maven-fo
I think I see the bug. Do you know how to build uima-as from svn?
https://uima.apache.org/building-uima.html
I will fix this shortly in the svn trunk. The next release of uima-as
(2.9.0) is in the
works. I will get a release candidate out hopefully next week.
-jerry
On Thu, Sep 22, 2016 at 12:0
Can you install AMQ broker 5.14.0 to see if this is related to broker
issues.
-jerry
On Thu, Sep 22, 2016 at 11:29 AM, nelson rivera
wrote:
> just like that, the parent CAS comes back but the child CAS doesnt.
>
> And the child CAS if processed, because the uima-as log shows the
> lines of th
Thanks for the quick response
Yes, it occurs every time, at the same line in RunRemoteAsyncAE and
org.apache.uima.adapter.jms.client.BaseUIMAAsynchronousEngine_
impl.undeploy(BaseUIMAAsynchronousEngine_impl.java:964)
On 9/22/16, 11:15 AM, "Jaroslaw Cwiklik" wrote:
>This warning
>
>WARN Tra
just like that, the parent CAS comes back but the child CAS doesnt.
And the child CAS if processed, because the uima-as log shows the
lines of the other annotators primitive of the flow processing the
child CAS, but not comes back to UIMA-AS client.
uima-as log only shows
"Jms Listener Failed.
This warning
WARN Transport - Transport Connection to: tcp://
127.0.0.1:56261 failed: java.io.EOFException
is from brokers log or console I suspect. It just means that the broker
lost a connection to a client. Looks like the client
went away without closing a connection. Thi
I’m using the UIMA C++ framework 2.4.0 (32-bit) on linux (CentOS 6.5), and
following the instructions
https://uima.apache.org/d/uimacpp-2.4.0/docs/overview_and_setup.html. I’ve
successfully built DaveDetector and run it with the standalone C++ pipeline
(runAECpp) and within a Java pipeline vi
When a parent CAS comes back (after broker is restored), can the client
send more CASes to the service and receive responses? I am trying to
determine what the real problem is here.
1) JMS Listener not recovering connection
2) UIMA-AS is not handling CAS reply failures when broker connection is
st
Strange. You say that the parent CAS comes back but the child CAS doesnt.
Are there any exceptions in the service log? Perhaps the service is unable
to send the child CAS due to missing broker. There should be something in
the uima-as log about this.
-jerry
On Thu, Sep 22, 2016 at 10:19 AM, nelso
Yes, it is supposed to do the service, given a
CAS it produces a child CAS and and this CAS continue in the flow,
that are other primitive annotators. And I expected that the child CAS
will sent to UIMA-AS client, but not do.
the scenario:
1- Start Broker and UIMA-AS aggregate service
2- Client s
Can you clarify if the UIMA-AS service is a Cas Multiplier. Meaning given a
CAS it produces child CASes
which are then sent to UIMA-AS client. Is this what this service is
supposed to do if the broker is running?
Can you confirm the scenario:
1) Client sends a CAS to UIMA-AS aggregate service
2) S
I will try the variants that you say. I was deepening the problem:
I have a Aggregate AE that contains CasMultiplier, the original CAS
is finish when it arrives to this CasMultiplier, this generates new
CAS and is this CAS that continue in the flow of Aggregate.
After restart broker (without res
14 matches
Mail list logo
