[jira] Closed: (UIMA-1726) Long GC causes UIMA AS service to loose broker connection and marks the client as dead
[ https://issues.apache.org/jira/browse/UIMA-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1726. --- Resolution: Fixed Fix Version/s: 2.3AS Removed DoNotProcess list as means of tracking disconnected clients. To detect dead clients and to optimize processing, the code checks for existence of a temp reply queue in the broker's JMX MBeanServer registry. If the temp queue exists, the message is processed. If the queue lookup fails, the message is dropped. A temp reply queue exists in the same broker that manages service input queue. The code creates a connection to a JMX MBeanServer on initial request message and caches it for subsequent lookups. If the broker is configured to not use jmx, the optimization is not performed and every message is processed. Such requests fail when a reply is attempted and the temp queue doesnt exists due to client termination. The code supports: tcp, http, as well as failover in the broker url. The default jmx port used for creating connection to broker's MBeanServer is 1099. To override this, add this property: -Dactivemq.broker.jmx.port=XXX to the service startup command Long GC causes UIMA AS service to loose broker connection and marks the client as dead -- Key: UIMA-1726 URL: https://issues.apache.org/jira/browse/UIMA-1726 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Fix For: 2.3AS When the JVMs GC takes a long time, the UIMA AS fails to validate the broker connection and proceeds to close it as if the broker died. It seems that the long GC freezes the jvm and prevents the low level socket pinging to work correctly. This pinging is a mechanism by which the low level AMQ code relies upon to detect a broker failure. In this case, the broker is actually fine. The side effect of the above is that the UIMA AS service falsely adds the client to the DoNotProcess list. This is an optimization that was recently added that prevents wasting processing cycles while handling CASes that are known to have come from clients that had gone away. Each CAS origin is checked against that list and if there is a match the CAS is thrown away. It seems that we need a better mechanism to detect broker failure. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1751) Fix NPE while looking up MessageProducer
Fix NPE while looking up MessageProducer Key: UIMA-1751 URL: https://issues.apache.org/jira/browse/UIMA-1751 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jerry Cwiklik ActiveMQMessageSender throws NPE in getMessageProducer() sometimes when the UIMA AS client is stopping. A race condition seems to be the cause. A thread doing a send tries to dereference engine object after the engine was forced to stop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1751) Fix NPE while looking up MessageProducer
[ https://issues.apache.org/jira/browse/UIMA-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1751. --- Resolution: Fixed Modified getMessageProducer() in ActiveMQMessageSender to check the state of the engine before returning the Producer. Fix NPE while looking up MessageProducer Key: UIMA-1751 URL: https://issues.apache.org/jira/browse/UIMA-1751 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jerry Cwiklik ActiveMQMessageSender throws NPE in getMessageProducer() sometimes when the UIMA AS client is stopping. A race condition seems to be the cause. A thread doing a send tries to dereference engine object after the engine was forced to stop. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1752) Fisheye for Repository
Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1752) Fisheye for Repository
[ https://issues.apache.org/jira/browse/UIMA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850231#action_12850231 ] Marshall Schor commented on UIMA-1752: -- Do you know the process to do this? Are there any downsides to doing it? Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1752) Fisheye for Repository
[ https://issues.apache.org/jira/browse/UIMA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850245#action_12850245 ] Brandon Fish commented on UIMA-1752: The license download can be found here: http://www.atlassian.com/software/fisheye/pricing.jsp?type=opensource Installation guides for Atlassian Products are well documented: http://confluence.atlassian.com/display/FISHEYE/FishEye+Installation+Guide I don't see any downsides, you just need a server. Installation is very quick. There may be some configuration required so Fisheye knows your projects' layout but this is easy as well. Then you just wait for it to index your repository. Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1752) Fisheye for Repository
[ https://issues.apache.org/jira/browse/UIMA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850261#action_12850261 ] Brandon Fish commented on UIMA-1752: I also noticed Atlassian is hosting for ActiveMQ: http://fisheye6.atlassian.com/browse/activemq Maybe there is a possibility to do the same for UIMA. Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1752) Fisheye for Repository
[ https://issues.apache.org/jira/browse/UIMA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850270#action_12850270 ] Brandon Fish commented on UIMA-1752: From http://fisheye6.atlassian.com/: FishEye on Apache Projects This FishEye instance is proudly brought to you by Atlassian and Contegix. Please feel free to experiment with Crucible using the DEMO project. Ping support if you would like a Crucible project for your project. We can set default reviewers, restrict users who can create reviews, and other useful things. FishEye 6 contains Subversion repositories from Apache. Other hosted FishEye repositories can be found: * FishEye 1 SourceForge CVS repositories. * FishEye 2 Miscellaneous repositories. * FishEye 3 SourceForge Subversion repositories. * FishEye 4 Java.net Subversion repositories. * FishEye 5 Java.net CVS repositories. * FishEye 6 Apache Subversion Repositories. Adding an Apache Repo Atlassian is now running a mirror of the Apache SVN repository which makes it a simple matter for us to add an Apache project to this instance. If you would like to have an Apache project listed here: Create a support request at Atlassian Support(http://support.atlassian.com/) in the FishEye project. Please use the Public Hosting component for your request. Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1405) Uima AS not allowing deployment of more than one deployment descriptor in the same jvm
[ https://issues.apache.org/jira/browse/UIMA-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jerry Cwiklik closed UIMA-1405. --- Resolution: Won't Fix Uima AS not allowing deployment of more than one deployment descriptor in the same jvm -- Key: UIMA-1405 URL: https://issues.apache.org/jira/browse/UIMA-1405 Project: UIMA Issue Type: Bug Components: Async Scaleout Affects Versions: 2.3AS Reporter: Jerry Cwiklik Assignee: Jerry Cwiklik Priority: Minor Uima AS fails with ResourceInitializationException when one tries to deploy more than one deployment descriptor using deployAsyncService script. The problem is that components in generated spring context files are deployed into a single Spring container. But each spring context files defines singleton objects that are not meant to be used externally. An example of such non-shared singleton would the InProcessCache. It is meant to be shared by components defined in a single context file. There are few possibly solutions here: 1) modify dd2spring to assign unique names to spring beans to prevent sharing across context files. 2) modify uima-as deployer to deploy each context file in a separate spring container 3) find a way to prevent spring from sharing singleton objects across context files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1752) Fisheye for Repository
[ https://issues.apache.org/jira/browse/UIMA-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12850423#action_12850423 ] Marshall Schor commented on UIMA-1752: -- looks like FishEye 6 has no incubator projects. We've graduated, but are still waiting to get set up as a top level project. I think it best to wait till that happens to move on this. Fisheye for Repository -- Key: UIMA-1752 URL: https://issues.apache.org/jira/browse/UIMA-1752 Project: UIMA Issue Type: New Feature Components: Website Reporter: Brandon Fish Setup a Fisheye source code search and browser for the repository. This would be useful to new people to the project for locating classes, example code and packages. It is free for open source projects and ActiveMQ has one setup already. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
