David, here is the next snapshot:
https://repository.apache.org/content/repositories/snapshots/org/apache/uima/uima-as/2.9.0-SNAPSHOT/uima-as-2.9.0-20160923.195233-6.tar.gz
-jerry
On Fri, Sep 23, 2016 at 3:35 PM, Jaroslaw Cwiklik wrote:
> David, like I said not my code so
David, like I said not my code so not quite in-tune what this does.
I've added this to the snapshot you are using:
synchronized public String quiesceAndStop() throws IOException {
StringBuffer sb = new StringBuffer();
if (socket != null && !socket.isClosed() ) {
In the above I am checking
That’s odd… now I get
java.io.IOException: Error: no socket connection.
at
org.apache.uima.aae.controller.UimacppServiceManagement.quiesceAndStop(Uima
cppServiceManagement.java:109)
at
org.apache.uima.aae.controller.UimacppServiceManagement.quiesceAndShutdown(
UimacppServiceManagement.java:409)
David, so there is progress. :)
I am not familiar with UimacppServiceController code but a quick glance at
the source
suggests that this code communicates with a C++ process via a socket:
if (socket != null) {
// System.out.println("UimacppServiceManagement::quiesceAndStop()
// Sending
I was able to install that, and I’m not getting the NullPointerException.
The example annotator still runs successfully, but now I get
---
Attempting to deploy descriptors/Deploy_MeetingAnnotator.xml ...
Waiting for Uima C++
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
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
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.