CeBIT, anyone?
Michael and I will be at CeBIT this year. If you're there and want to meet us, drop us a line. --Thilo
[jira] Created: (UIMA-751) extend the UIMA logging interface to retrieve the root logger
extend the UIMA logging interface to retrieve the root logger - Key: UIMA-751 URL: https://issues.apache.org/jira/browse/UIMA-751 Project: UIMA Issue Type: New Feature Components: Core Java Framework Affects Versions: 2.2.1 Reporter: Michael Baessler Priority: Minor Currently UIMA applications cannot manipulate the root logger settings only the UIMA framework logger (org.apache.uima) settings. This means that e.g. the CVD or any other application cannot change effectively the log level using an API. This only works if within the application only components are running the have the same namespace as the UIMA framework logger (org.apache.uima). In that case the sub loggers have the org.apache.uima logger as root logger. But it doesn't work for annotators that have another namespace sicne in that case they have another root logger. With the root logger extension UIMA applications can retrieve the real root logger and can manipulate the setting on it. But this should only used if the application has full control about the whole JVM. This should not be used if the application is integrated into another application that use the same logging system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Next bugfix release for Apache UIMA
Does anyone has the time to look at this issue now? I would like to start with the release in the next weeks so that we get it out in March. If nobody has the time, I don't think the issue is important enough to wait with the release. Other opinions? -- Michael Eddie Epstein wrote: Hi Michael, The next release should also address the opennlp part of https://issues.apache.org/jira/browse/UIMA-475 Actually, the bug shows up with 2.2.1 but I cannot reproduce it on the current svn code. Since nobody has specifically fixed this bug it will require more investigation. Eddie On Feb 4, 2008 10:47 AM, Michael Baessler [EMAIL PROTECTED] wrote: Hi, we have two major items where projects are waiting for, so we should consider to make the next bugfix release. The major items are: - capabilityLanguageFlow performance fix - FeaturePath implementation Probably there are some other open issues that should be fixed before starting the next release. When searching JIRA I see: UIMA-739Use compressed form of eclipse update site, and support multiple releases UIMA-734Check and possibly update docs for capability language flow to say not to depend on subtyping UIMA-733it is possible to load a type system descriptor that redefines the super type of the DocumentAnnotation UIMA-727Result Specifications not being passed to imbedded Pears UIMA-704adjustExamplePaths.bat creates broken .classpath for uimaj-examples UIMA-680CAS is not unlocked on Errors UIMA-657Eclipse Update site should keep previous versions UIMA-687Remove redundant notifyAll when calling casPool.releaseCas (...) UIMA-643TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null UIMA-282Work well with Apache logging (Log4J) I think most of them should be fixed before the next release. Other opinions? Since the next release will also be a bug fix release I would suggest to rename the version number from 2.3 to 2.2.2. Would it be feasible to have the release in March? So we have some time for fixing the open issues before we start the release cycle which will take us about 5 weeks after code freeze. -- Michael
Re: CPE Memory Problem
Eddie, so which JVM did you use to produce the problem? I understand 1.6.0_02 fixed it, but which one didn't work? Thanks. Eddie Epstein wrote: Hi Marisol, After installing opennlp on Apache UIMA v2.2.1, I was able to reproduce the problem using OpenNLPParser with both documentAnalyzer and cpeGui. However, I had some problems reproducing this problem between an environment with the 2.2.1 SDK jars vs. a development environment using the latest code in svn. Turns out the difference between working and not working was the JRE. JRE= jre1.6.0_02 continued working on repeated runs. Hope this can help you, Eddie On Feb 5, 2008 1:13 PM, Marisol B. Gamboa [EMAIL PROTECTED] wrote: I'm having a problem reallocating memory after CollectionProcessingEngine process completes. The cpeGui seems to have the same problem. I'm loading the OpenNLP models into a CPE for processing documents and if I want to setup another process without killing the GUI or the JVM the memory form the last CPE is never garbage collected. Has anyone encountered this and is there a fix? Marisol
[jira] Closed: (UIMA-752) rename uima-ee to uima-as in SVN
[ https://issues.apache.org/jira/browse/UIMA-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-752. --- Resolution: Fixed Renames: uima-ee - uima-as (this is not a project, but is the top directory for all the uima-as projects) uimacpp-ee - uimacpp-as uima-ee-distr - uima-as-distr uima-ee-docbooks - uima-as-docbooks uimaj-ee - uimaj-as uimaj-ee-activemq - uimaj-as-activemq uimaj-ee-core -uimaj-as-core uimaj-ee-jms - uimaj-as-jms rename uima-ee to uima-as in SVN Key: UIMA-752 URL: https://issues.apache.org/jira/browse/UIMA-752 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Marshall Schor Assignee: Marshall Schor Based on mail thread discussion, we are renaming uima-ee to uima-as. The repository projects names are being updated to be consistent with this. After this change, please recheck-out the projects under ther new names. Some fixes beyond SVN renaming will probably also be needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-752) rename uima-ee to uima-as in SVN
rename uima-ee to uima-as in SVN Key: UIMA-752 URL: https://issues.apache.org/jira/browse/UIMA-752 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Marshall Schor Assignee: Marshall Schor Based on mail thread discussion, we are renaming uima-ee to uima-as. The repository projects names are being updated to be consistent with this. After this change, please recheck-out the projects under ther new names. Some fixes beyond SVN renaming will probably also be needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-750) fix UIMA version error on download page
fix UIMA version error on download page --- Key: UIMA-750 URL: https://issues.apache.org/jira/browse/UIMA-750 Project: UIMA Issue Type: Bug Components: Website Reporter: Michael Baessler Assignee: Michael Baessler Apache UIMA 2.1.1-incubating was released on 21-Dec-2007 and may not be available on all mirrors for a few days The version is wrong... but I think the entire note can be removed now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-282) Work well with Apache logging (Log4J)
[ https://issues.apache.org/jira/browse/UIMA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler updated UIMA-282: -- Fix Version/s: 2.3 Work well with Apache logging (Log4J) - Key: UIMA-282 URL: https://issues.apache.org/jira/browse/UIMA-282 Project: UIMA Issue Type: Wish Components: Core Java Framework Affects Versions: 2.1, 2.2, 2.2.1 Reporter: Greg Holmberg Assignee: Michael Baessler Priority: Minor Fix For: 2.3 Attachments: Log4jLogger_impl.java, Log4jLogger_impl.java, TestLog4jLogger_impl.java, TestLog4jLogger_impl.java UIMA uses the standard java.util.logging (JUL). Most of my company's code used Apache Log4J, so we have a problem merging the messages from the two logging packages. Given that UIMA is now an Apache project, I think it makes sense that it work with Apache logging. Two options occur to me: 1. Change all the logging calls in the code (perhaps Eclipse refactoring tools can help with that). Here's some discussion on migrating: http://www.oreillynet.com/onjava/blog/2005/12/migrating_from_jdk_logging_to.html You could convert either to Log4J ( http://logging.apache.org/log4j/docs ) or to Apache Jakarta Commons Logging ( http://jakarta.apache.org/commons/logging ), which would allow UIMA to be configured to use either JUL or Log4J. 2. Write/find a JUL Handler that re-directs to Log4J. Here's an example: http://home.gwu.edu/~amrinder/chainsawHandler/UsingChainsawWithJDKLogging.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-282) Work well with Apache logging (Log4J)
[ https://issues.apache.org/jira/browse/UIMA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler resolved UIMA-282. --- Resolution: Fixed Hi, I think the integration is done, can please anyone else check if it works as expected? I think some of you already have an production environment that use Log4j. -- Michael Work well with Apache logging (Log4J) - Key: UIMA-282 URL: https://issues.apache.org/jira/browse/UIMA-282 Project: UIMA Issue Type: Wish Components: Core Java Framework Affects Versions: 2.1, 2.2, 2.2.1 Reporter: Greg Holmberg Assignee: Michael Baessler Priority: Minor Attachments: Log4jLogger_impl.java, Log4jLogger_impl.java, TestLog4jLogger_impl.java, TestLog4jLogger_impl.java UIMA uses the standard java.util.logging (JUL). Most of my company's code used Apache Log4J, so we have a problem merging the messages from the two logging packages. Given that UIMA is now an Apache project, I think it makes sense that it work with Apache logging. Two options occur to me: 1. Change all the logging calls in the code (perhaps Eclipse refactoring tools can help with that). Here's some discussion on migrating: http://www.oreillynet.com/onjava/blog/2005/12/migrating_from_jdk_logging_to.html You could convert either to Log4J ( http://logging.apache.org/log4j/docs ) or to Apache Jakarta Commons Logging ( http://jakarta.apache.org/commons/logging ), which would allow UIMA to be configured to use either JUL or Log4J. 2. Write/find a JUL Handler that re-directs to Log4J. Here's an example: http://home.gwu.edu/~amrinder/chainsawHandler/UsingChainsawWithJDKLogging.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work stopped: (UIMA-742) Cumulative fixes to synch apache svn with the latest changes
[ https://issues.apache.org/jira/browse/UIMA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-742 stopped by Marshall Schor. Cumulative fixes to synch apache svn with the latest changes Key: UIMA-742 URL: https://issues.apache.org/jira/browse/UIMA-742 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Jerry Cwiklik Assignee: Marshall Schor Attachments: uimaj-ee-activemq-patch.patch, uimaj-ee-activemq-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-jms-patch.patch, uimaj-ee-jms-patch.patch Fixes: - refactored uima ee client to use single thread for sending CASes. - synchronized uima ee client APIs - moved jms objects (Session, Message, Producer, Destination) to concrete implementation of uima ee client (activemq) - postpone sending getMeta request to remote delegates until all listener threads are fully initialized - modified controller API to support adding and calling listeners when initialization is completed - added support for storing temp queue information in the endpoint object - fixed cleanup in the uimaCppServiceController - fixed retry logic in the error handler - fixed continueOnError logic in the error handler - fixed initialHeapSize setting in the contrioller - added host IP to the reply message and modified the client code to log the IP - modified the listener code to log endpoint name when the listener fails - added support for logging uima ee version on startup - refactored uima ee client code to use SpringContainerDeployer to deploy spring context files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
a link to add to your list of UIMA resources on the web page
Hi, Thank you for providing links to UIMA component repositories at your webpage http://incubator.apache.org/uima/external-resources.html - very helpful! Here is link you can add for a BioNLP specific UIMA Component Repository: http://bionlp-uima.sourceforge.net. Thanks, Helen Johnson -- Helen L. Johnson Sr. Professional Research Assistant Center for Computational Pharmacology University of Colorado Health Sciences Center phone: 720-209-2588 fax: 303-724-7570 email: [EMAIL PROTECTED] web: http://compbio.uchsc.edu/ccp/Hunter_lab/Johnson
[jira] Closed: (UIMA-748) Multiple notfications sent to registered listeners.
[ https://issues.apache.org/jira/browse/UIMA-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-748. --- Resolution: Fixed Applied the most recent patch 748-1. Multiple notfications sent to registered listeners. --- Key: UIMA-748 URL: https://issues.apache.org/jira/browse/UIMA-748 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Attachments: UIMA-748-1.patch, UIMA-748.patch Multiple notfications sent to registered listeners. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-743) Add new testcases to test new features
[ https://issues.apache.org/jira/browse/UIMA-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-743. --- Resolution: Fixed Latest patch applied. Add new testcases to test new features -- Key: UIMA-743 URL: https://issues.apache.org/jira/browse/UIMA-743 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Jerry Cwiklik Assignee: Marshall Schor Attachments: uimaj-ee-testcases-patch.patch, uimaj-ee-testcases-patch.patch Add new testcases and resources to test new features in uima ee -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-742) Cumulative fixes to synch apache svn with the latest changes
[ https://issues.apache.org/jira/browse/UIMA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor closed UIMA-742. --- Resolution: Fixed 3 latest patches committed. Cumulative fixes to synch apache svn with the latest changes Key: UIMA-742 URL: https://issues.apache.org/jira/browse/UIMA-742 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Jerry Cwiklik Assignee: Marshall Schor Attachments: uimaj-ee-activemq-patch.patch, uimaj-ee-activemq-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-jms-patch.patch, uimaj-ee-jms-patch.patch Fixes: - refactored uima ee client to use single thread for sending CASes. - synchronized uima ee client APIs - moved jms objects (Session, Message, Producer, Destination) to concrete implementation of uima ee client (activemq) - postpone sending getMeta request to remote delegates until all listener threads are fully initialized - modified controller API to support adding and calling listeners when initialization is completed - added support for storing temp queue information in the endpoint object - fixed cleanup in the uimaCppServiceController - fixed retry logic in the error handler - fixed continueOnError logic in the error handler - fixed initialHeapSize setting in the contrioller - added host IP to the reply message and modified the client code to log the IP - modified the listener code to log endpoint name when the listener fails - added support for logging uima ee version on startup - refactored uima ee client code to use SpringContainerDeployer to deploy spring context files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (UIMA-742) Cumulative fixes to synch apache svn with the latest changes
[ https://issues.apache.org/jira/browse/UIMA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor reassigned UIMA-742: --- Assignee: Marshall Schor Cumulative fixes to synch apache svn with the latest changes Key: UIMA-742 URL: https://issues.apache.org/jira/browse/UIMA-742 Project: UIMA Issue Type: Improvement Components: Async Scaleout Affects Versions: 2.2.1 Reporter: Jerry Cwiklik Assignee: Marshall Schor Attachments: uimaj-ee-activemq-patch.patch, uimaj-ee-activemq-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-core-patch.patch, uimaj-ee-jms-patch.patch, uimaj-ee-jms-patch.patch Fixes: - refactored uima ee client to use single thread for sending CASes. - synchronized uima ee client APIs - moved jms objects (Session, Message, Producer, Destination) to concrete implementation of uima ee client (activemq) - postpone sending getMeta request to remote delegates until all listener threads are fully initialized - modified controller API to support adding and calling listeners when initialization is completed - added support for storing temp queue information in the endpoint object - fixed cleanup in the uimaCppServiceController - fixed retry logic in the error handler - fixed continueOnError logic in the error handler - fixed initialHeapSize setting in the contrioller - added host IP to the reply message and modified the client code to log the IP - modified the listener code to log endpoint name when the listener fails - added support for logging uima ee version on startup - refactored uima ee client code to use SpringContainerDeployer to deploy spring context files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Next bugfix release for Apache UIMA
Hi Michael, The next release should also address the opennlp part of https://issues.apache.org/jira/browse/UIMA-475 Actually, the bug shows up with 2.2.1 but I cannot reproduce it on the current svn code. Since nobody has specifically fixed this bug it will require more investigation. Eddie On Feb 4, 2008 10:47 AM, Michael Baessler [EMAIL PROTECTED] wrote: Hi, we have two major items where projects are waiting for, so we should consider to make the next bugfix release. The major items are: - capabilityLanguageFlow performance fix - FeaturePath implementation Probably there are some other open issues that should be fixed before starting the next release. When searching JIRA I see: UIMA-739Use compressed form of eclipse update site, and support multiple releases UIMA-734Check and possibly update docs for capability language flow to say not to depend on subtyping UIMA-733it is possible to load a type system descriptor that redefines the super type of the DocumentAnnotation UIMA-727Result Specifications not being passed to imbedded Pears UIMA-704adjustExamplePaths.bat creates broken .classpath for uimaj-examples UIMA-680CAS is not unlocked on Errors UIMA-657Eclipse Update site should keep previous versions UIMA-687Remove redundant notifyAll when calling casPool.releaseCas (...) UIMA-643TypeSystemUtil.type2TypeDescription() throws NPE when the superType is null UIMA-282Work well with Apache logging (Log4J) I think most of them should be fixed before the next release. Other opinions? Since the next release will also be a bug fix release I would suggest to rename the version number from 2.3 to 2.2.2. Would it be feasible to have the release in March? So we have some time for fixing the open issues before we start the release cycle which will take us about 5 weeks after code freeze. -- Michael
[jira] Updated: (UIMA-748) Multiple notfications sent to registered listeners.
[ https://issues.apache.org/jira/browse/UIMA-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhavani Iyer updated UIMA-748: -- Attachment: UIMA-748-1.patch Previous patch did not match up. Multiple notfications sent to registered listeners. --- Key: UIMA-748 URL: https://issues.apache.org/jira/browse/UIMA-748 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Attachments: UIMA-748-1.patch, UIMA-748.patch Multiple notfications sent to registered listeners. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-750) fix UIMA version error on download page
[ https://issues.apache.org/jira/browse/UIMA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Baessler closed UIMA-750. - Resolution: Fixed fix UIMA version error on download page --- Key: UIMA-750 URL: https://issues.apache.org/jira/browse/UIMA-750 Project: UIMA Issue Type: Bug Components: Website Reporter: Michael Baessler Assignee: Michael Baessler Apache UIMA 2.1.1-incubating was released on 21-Dec-2007 and may not be available on all mirrors for a few days The version is wrong... but I think the entire note can be removed now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (UIMA-752) rename uima-ee to uima-as in SVN
[ https://issues.apache.org/jira/browse/UIMA-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-752 started by Marshall Schor. rename uima-ee to uima-as in SVN Key: UIMA-752 URL: https://issues.apache.org/jira/browse/UIMA-752 Project: UIMA Issue Type: Improvement Components: Async Scaleout Reporter: Marshall Schor Assignee: Marshall Schor Based on mail thread discussion, we are renaming uima-ee to uima-as. The repository projects names are being updated to be consistent with this. After this change, please recheck-out the projects under ther new names. Some fixes beyond SVN renaming will probably also be needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
