[jira] Created: (UIMA-1710) All projects should fail if not compiled with at least maven 2.2.0
All projects should fail if not compiled with at least maven 2.2.0 -- Key: UIMA-1710 URL: https://issues.apache.org/jira/browse/UIMA-1710 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Affects Versions: 2.3S, 2.3, 2.3AS Reporter: Jörn Kottmann Priority: Trivial Right now the build fails if uimaj is build with a maven version prior 2.2.0, but it does not fail in other projects. If a maven version prior 2.2.0 is used the build should fail with the invalid version error message in all projects, instead of: [INFO] Error configuring: org.apache.maven.plugins:maven-antrun-plugin. Reason: java.lang.NoSuchMethodError: org.apache.tools.ant.util.FileUtils.close(Ljava/io/InputStream;)V -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1711) All eclipse tooling projects should compile against the same eclipse version
All eclipse tooling projects should compile against the same eclipse version Key: UIMA-1711 URL: https://issues.apache.org/jira/browse/UIMA-1711 Project: UIMA Issue Type: Improvement Components: Build, Packaging and Test Reporter: Jörn Kottmann Priority: Trivial Right now the eclipse tooling projects are compiled against eclipse 3.2 and the cas editor is compiled against 3.3.0. To build uima both version of eclipse must be downloaded. The initial build will be faster if everything is compiled against 3.3.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: UIMA AS client connection to broker lost issue
Jaroslaw Cwiklik wrote: That is right. jerry On Mon, Dec 14, 2009 at 9:53 AM, Jörn Kottmann kottm...@gmail.com wrote: Jaroslaw Cwiklik wrote: Yes, this exception comes from UIMA AS client and it is thrown if the connection to the broker is lost. If the connection to a broker is lost the current code doesnt use onBeforeMessageSend() callback. This method is only called if the connection is ok, right before the send(). The code that detects connection failure is before this. When you get BrokerConnectionException you know that what you've sent previously will not come back. The reply queue has already been deleted. You may assume this and awake all waiting threads and invalidate their states and retry if that is what you want to do. If the broker finally comes online, eventually UIMA AS client will call onBeforeMessageSend() and that will be a clue that things are back to normal. Sorry, have been through a few very busy weeks, since the release is now delayed I would like to fix this problem. To make sure I understand you correctly, a CAS is send via sendCas(...), but it cannot be send because of a broker connection exception, the error is then reported to the status call back listeners entityProcessComplete method. When the status call back listener receives the BrokerConnectionException it should consider all outstanding CASes as failed and retry them. Is that correct ? Must the same action be taken if a timed out CAS comes back ? Jörn
Re: UIMA AS client connection to broker lost issue
No. With timeouts the client API will notify the application for each request that eventually fails. Eddie On Thu, Dec 17, 2009 at 9:32 AM, Jörn Kottmann kottm...@gmail.com wrote: When the status call back listener receives the BrokerConnectionException it should consider all outstanding CASes as failed and retry them. Is that correct ? Must the same action be taken if a timed out CAS comes back ? Jörn
