[jira] Closed: (UIMA-1292) Uima AS Jms Listener Should Support Retry When Establishing Connection To a Broker
[ https://issues.apache.org/jira/browse/UIMA-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1292. --- Resolution: Fixed Removed testTerminateOnInitializationFailureWithAggregateForcedShutdown() as it was causing a hang. In this test, an aggregate tries to establish a connection to a non-existent broker. before recent changes, the listener was not trying to recover a connection a broker and simply terminated the service. Recent code changes force the listener to silently reconnect until a broker is ready but since the broker is never started the test hangs. This test is no longer valid. > Uima AS Jms Listener Should Support Retry When Establishing Connection To a > Broker > -- > > Key: UIMA-1292 > URL: https://issues.apache.org/jira/browse/UIMA-1292 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Jerry Cwiklik >Assignee: Jerry Cwiklik > Fix For: 2.3AS > > > UIMA AS service should support retry when a listener on the service input > queue fails due to a broker not being available. The listener should log a > message stating the fact that the broker is not available and it should enter > a loop attempting to reconnect. When a broker becomes available the listener > should reconnect, log a message that the connection was made, and proceed to > complete initialization. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1694) Error 'scm url cannot be null' on uimaj POM
[ https://issues.apache.org/jira/browse/UIMA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili closed UIMA-1694. - > Error 'scm url cannot be null' on uimaj POM > --- > > Key: UIMA-1694 > URL: https://issues.apache.org/jira/browse/UIMA-1694 > Project: UIMA > Issue Type: Bug > Components: Core Java Framework >Affects Versions: 2.3S >Reporter: Tommaso Teofili >Assignee: Tommaso Teofili > Fix For: 2.3 > > > When launching 'mvn -Dmaven.repo.local=/tmp/uimaj-rc5 clean install' for > testing the new 2.3.0-rc5, an error 'scm url cannot be null' on uimaj POM > comes out -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1699) UIMA-AS start broker appears to hang - but maybe a logging issue (RC6)
[ https://issues.apache.org/jira/browse/UIMA-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-1699. -- Resolution: Fixed Assignee: Jerry Cwiklik (was: Marshall Schor) Jerry - any issues with this change? > UIMA-AS start broker appears to hang - but maybe a logging issue (RC6) > -- > > Key: UIMA-1699 > URL: https://issues.apache.org/jira/browse/UIMA-1699 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Marshall Schor >Assignee: Jerry Cwiklik >Priority: Blocker > Fix For: 2.3AS > > > Running the bringup tests with RC6 - the logging appears to be not working > properly. > bin/startBroker.sh appears to hang. But it is actually running ( both on > Linux and Windows ) - as indicated by trying the sample in section 3.4 of the > README for UIMA-AS. > The "log" specified in the log4j configuration is created, but is empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1700) copy LIC/NOT files to top level for UIMA-AS
[ https://issues.apache.org/jira/browse/UIMA-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-1700. Resolution: Fixed Fix Version/s: 2.3AS > copy LIC/NOT files to top level for UIMA-AS > --- > > Key: UIMA-1700 > URL: https://issues.apache.org/jira/browse/UIMA-1700 > Project: UIMA > Issue Type: Improvement > Components: Async Scaleout, Build, Packaging and Test >Reporter: Marshall Schor >Assignee: Marshall Schor > Fix For: 2.3AS > > > The License and Notice files for uima-as are under some directories - need to > be easily findable at the top level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1700) copy LIC/NOT files to top level for UIMA-AS
copy LIC/NOT files to top level for UIMA-AS --- Key: UIMA-1700 URL: https://issues.apache.org/jira/browse/UIMA-1700 Project: UIMA Issue Type: Improvement Components: Async Scaleout, Build, Packaging and Test Reporter: Marshall Schor Assignee: Marshall Schor The License and Notice files for uima-as are under some directories - need to be easily findable at the top level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-1699) UIMA-AS start broker appears to hang - but maybe a logging issue (RC6)
[ https://issues.apache.org/jira/browse/UIMA-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reassigned UIMA-1699: Assignee: Marshall Schor > UIMA-AS start broker appears to hang - but maybe a logging issue (RC6) > -- > > Key: UIMA-1699 > URL: https://issues.apache.org/jira/browse/UIMA-1699 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Reporter: Marshall Schor >Assignee: Marshall Schor >Priority: Blocker > Fix For: 2.3AS > > > Running the bringup tests with RC6 - the logging appears to be not working > properly. > bin/startBroker.sh appears to hang. But it is actually running ( both on > Linux and Windows ) - as indicated by trying the sample in section 3.4 of the > README for UIMA-AS. > The "log" specified in the log4j configuration is created, but is empty. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
