[jira] Closed: (UIMA-927) Provide a way to drain Dead Letter Queue
[ https://issues.apache.org/jira/browse/UIMA-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-927. -- Resolution: Won't Fix Draining queues should be responsibility of the broker and based on policy configured in brokers config file. > Provide a way to drain Dead Letter Queue > - > > Key: UIMA-927 > URL: https://issues.apache.org/jira/browse/UIMA-927 > Project: UIMA > Issue Type: Improvement > Components: Async Scaleout >Affects Versions: 2.3AS >Reporter: Jerry Cwiklik >Priority: Minor > > ActiveMQ currently doesnt evict expried messages from the Dead Letter Queue. > This can potentially lead to Out Of Memory situation as by default the broker > keeps all messages in memory. One possible strategy is to modify ActiveMQ > broker configuration to spool messages from the DLQ to disk when memory is > tight. Other strategy may involve creating a custom DLQ Consumer to drain > messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1680) Async Scaleout Monitor has many issues
[ https://issues.apache.org/jira/browse/UIMA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1680. --- Resolution: Fixed Fixed the source of NPE in the JmxMonitor class. Updated documentation to remove a comment that says that the -Duima.jmx.monitor.interval=xx is optional. Tested on Linux platform and see no problems. > Async Scaleout Monitor has many issues > -- > > Key: UIMA-1680 > URL: https://issues.apache.org/jira/browse/UIMA-1680 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Affects Versions: 2.3AS >Reporter: Burn Lewis >Assignee: Jerry Cwiklik >Priority: Minor > > uima.jmx.monitor.interval is required (not optional) to activate the internal > JMX logging. > During testing by Burn and Eddie: Output is not appearing; null pointer > exception is thrown: > Exception in thread "Thread-25" java.lang.NullPointerException > at > org.apache.uima.aae.jmx.monitor.SingleLineUimaJmxMonitorListener.onNewMetrics(SingleLineUimaJmxMonitorListener.java:75) > at > org.apache.uima.aae.jmx.monitor.JmxMonitor.notifyListeners(JmxMonitor.java:132) > at org.apache.uima.aae.jmx.monitor.JmxMonitor.run(JmxMonitor.java:539) > at java.lang.Thread.run(Thread.java:735) > Getting message: 19: org.apache.uima.aae.jmx.monitor.JmxMonitor.collectStats: > WARNING: Thread: Thread-25 > Exception:java.lang.reflect.UndeclaredThrowableException (May be OK?) > On Linux: got an InstantiationException loading the basic formatter class -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1680) Async Scaleout Monitor has many issues
[ https://issues.apache.org/jira/browse/UIMA-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik updated UIMA-1680: Assignee: Jerry Cwiklik > Async Scaleout Monitor has many issues > -- > > Key: UIMA-1680 > URL: https://issues.apache.org/jira/browse/UIMA-1680 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout >Affects Versions: 2.3AS >Reporter: Burn Lewis >Assignee: Jerry Cwiklik >Priority: Minor > > uima.jmx.monitor.interval is required (not optional) to activate the internal > JMX logging. > During testing by Burn and Eddie: Output is not appearing; null pointer > exception is thrown: > Exception in thread "Thread-25" java.lang.NullPointerException > at > org.apache.uima.aae.jmx.monitor.SingleLineUimaJmxMonitorListener.onNewMetrics(SingleLineUimaJmxMonitorListener.java:75) > at > org.apache.uima.aae.jmx.monitor.JmxMonitor.notifyListeners(JmxMonitor.java:132) > at org.apache.uima.aae.jmx.monitor.JmxMonitor.run(JmxMonitor.java:539) > at java.lang.Thread.run(Thread.java:735) > Getting message: 19: org.apache.uima.aae.jmx.monitor.JmxMonitor.collectStats: > WARNING: Thread: Thread-25 > Exception:java.lang.reflect.UndeclaredThrowableException (May be OK?) > On Linux: got an InstantiationException loading the basic formatter class -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [Informal Vote] please express your opinion on using Nexus and Hudson: see https://issues.apache.org/jira/browse/UIMA-1717
Yes, it really sounds nice to me too (so +1 again). Tommaso 2010/4/6 Jörn Kottmann > Marshall Schor wrote: > >> Here's my vision of automation (achieved over time :-) ), and why CI >> could be important - it is building the potential releases from source >> checkout. >> >> We have CI going on Hudson; we decide at some point that things merit a >> release; so we push some button on the CI or Nexus interface and get a >> particular snapshot release tagged, checked out and built as a candidate. >> >> We do some additional integration testing, and then vote on the thing in >> the nexus repo, where it look like a release but is in some "held" >> state. After the vote succeeds, we log onto the Nexus web interface and >> push another button, and the release happens. >> >> > > +1 sounds nice > > Jörn >
