[jira] Created: (UIMA-1663) All directories in UIMA distribution should be 755
All directories in UIMA distribution should be 755 -- Key: UIMA-1663 URL: https://issues.apache.org/jira/browse/UIMA-1663 Project: UIMA Issue Type: Bug Components: Build, Packaging and Test Affects Versions: 2.3, 2.3AS Reporter: Jörn Kottmann The uima-as-2.3.0-incubating-bin.tar.gz and uimaj-2.3.0-incubating-bin.tar.gz contain directories which also have write permissions for group and other set. That permissions for directories should be 755 (no write for group and other). Here is a list of the directories: apache-uima bin config apache-activemq.4.1.1 as_config examples (only uima-as) saxon I did not check uimacpp and the sandbox. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Apache Uima 2.3.0-incubating release candidate 01
Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. Everyone should recompile existing code which depends on UIMA against this RC to test if there are any problems with the generification. Jörn
Re: Apache Uima 2.3.0-incubating release candidate 01
On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall Marshall, the key you used to sign the release is unsigned. I thought there was a way to carry over the old signatures? Or can you maybe sign your new key with the old one? I haven't done this myself yet. --Thilo
Re: Apache Uima 2.3.0-incubating release candidate 01
On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall The CVD batch file is not working for me: c:\installers\uima\uima-2.3.0\apache-uima\binset UIMA_HOME=c:\installers\uima\uima-2.3.0\apache-uima c:\installers\uima\uima-2.3.0\apache-uima\bin.\cvd.bat =c:\installers\uima\uima-2.3.0\apache-uima/docs/html== was unexpected at this time. The same happens with all other batch files I tried. Am I missing anything obvious? Do I need to do more than set the UIMA_HOME variable? --Thilo
Re: Apache Uima 2.3.0-incubating release candidate 01
Thilo Goetz wrote: On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall Marshall, the key you used to sign the release is unsigned. I thought there was a way to carry over the old signatures? Or can you maybe sign your new key with the old one? I haven't done this myself yet. hmmm. I had signed the new key with the old one. I just now checked this using gpg --list-sigs for my key, and it shows (for me) that it is signed with my old key. The new key is titled Marshall I Schor (Code Signing Key 2) -- note the 2, and the old key is the same name without the 2. How did you determine that my signing key was unsigned? -Marshall --Thilo
Re: Apache Uima 2.3.0-incubating release candidate 01
Looks like a bug - investigating... -Marshall Thilo Goetz wrote: On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall The CVD batch file is not working for me: c:\installers\uima\uima-2.3.0\apache-uima\binset UIMA_HOME=c:\installers\uima\uima-2.3.0\apache-uima c:\installers\uima\uima-2.3.0\apache-uima\bin.\cvd.bat =c:\installers\uima\uima-2.3.0\apache-uima/docs/html== was unexpected at this time. The same happens with all other batch files I tried. Am I missing anything obvious? Do I need to do more than set the UIMA_HOME variable? --Thilo
Re: Apache Uima 2.3.0-incubating release candidate 01
On 11/13/2009 16:32, Marshall Schor wrote: Thilo Goetz wrote: On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall Marshall, the key you used to sign the release is unsigned. I thought there was a way to carry over the old signatures? Or can you maybe sign your new key with the old one? I haven't done this myself yet. hmmm. I had signed the new key with the old one. I just now checked this using gpg --list-sigs for my key, and it shows (for me) that it is signed with my old key. The new key is titled Marshall I Schor (Code Signing Key 2) -- note the 2, and the old key is the same name without the 2. How did you determine that my signing key was unsigned? -Marshall --Thilo Sorry, my mistake. I had neither imported nor trusted your old key, so the new one appeared non-trusted. Unsigned was wrong terminology on my part. Everything looks fine now. --Thilo
Re: Apache Uima 2.3.0-incubating release candidate 01
Marshall Schor wrote: Looks like a bug - investigating... -Marshall Here's a work-around: Edit the file %UIMA_HOME%\bin\runUimaClass.bat replace the line: @if %UIMA_CVDMAN%== set UIMA_CVDMAN=-Duima.tools.cvd.manpath.notset with @if not defined UIMA_CVDMAN set UIMA_CVDMAN=-Duima.tools.cvd.manpath.notset This last line requires that you have Windows XP or later, and that you have not explicitly disabled command extensions (they are enabled by default). I'll do the Jira, and this fix, unless someone has a more general fix. -Marshall Thilo Goetz wrote: On 11/13/2009 04:53, Marshall Schor wrote: The release candidate 01 for 2.3.0-incubating is on http://people.apache.org/~schor/uima-release-candidates/2.3.0-RC1/ It has 4 parts: uimaj - the main uima release uima-as - the uima-as add on uima-sandbox - the sandbox components being released uima-cpp - the C++ release, including several binary builds. The Release Audit Reports (RAT) are included. I'll work on posting a test plan to our wiki, probably tomorrow; meanwhile, please try it out. -Marshall The CVD batch file is not working for me: c:\installers\uima\uima-2.3.0\apache-uima\binset UIMA_HOME=c:\installers\uima\uima-2.3.0\apache-uima c:\installers\uima\uima-2.3.0\apache-uima\bin.\cvd.bat =c:\installers\uima\uima-2.3.0\apache-uima/docs/html== was unexpected at this time. The same happens with all other batch files I tried. Am I missing anything obvious? Do I need to do more than set the UIMA_HOME variable? --Thilo
[jira] Created: (UIMA-1665) UIMA AS aggregate not handling timeouts correctly for parallel delegates
UIMA AS aggregate not handling timeouts correctly for parallel delegates Key: UIMA-1665 URL: https://issues.apache.org/jira/browse/UIMA-1665 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Jerry Cwiklik Priority: Blocker Fix For: 2.3AS Burn discovered a bug in UIMA AS aggregate while handling timeouts from delegates in a parallel step. A delegate timeout that is subsequently disabled (due to error handling setting action=disable), causes error handling code to (incorrectly) double increment the count of delegates that responded. The count is maintained to determine how many delegates in a parallel step responded and if it is ok to allow the CAS to continue with the flow. This counter is incremented when a reply comes or there is a timeout. When the counter reaches the expected number, the CAS is allowed to continue on with flow. The double increment causes a CAS to continue in the flow prematurely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (UIMA-1666) CasPoolSize should equal numberOfInstances when deploying a primitive component
CasPoolSize should equal numberOfInstances when deploying a primitive component --- Key: UIMA-1666 URL: https://issues.apache.org/jira/browse/UIMA-1666 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1666) CasPoolSize should equal numberOfInstances when deploying a primitive component
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777594#action_12777594 ] Jörn Kottmann commented on UIMA-1666: - Warnings are easily overseen, wouldn't it be better to not start at all if this setting is wrong ? CasPoolSize should equal numberOfInstances when deploying a primitive component --- Key: UIMA-1666 URL: https://issues.apache.org/jira/browse/UIMA-1666 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1666) CasPoolSize should equal numberOfInstances when deploying a primitive component
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777642#action_12777642 ] Marshall Schor commented on UIMA-1666: -- I agree that warnings can be overlooked. In this case, since we recover this error with no adverse consequences, I don't see the value in not starting. We can add a comment that if the user is trying to control the size of the pool because otherwise too much memory is used, they must do it by changing the number of instances. The caspool element is needed to specify the initial CAS heap size, so the user might have this element for a legitimate reason. -Marshall CasPoolSize should equal numberOfInstances when deploying a primitive component --- Key: UIMA-1666 URL: https://issues.apache.org/jira/browse/UIMA-1666 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (UIMA-1666) CasPoolSize should equal numberOfInstances when deploying a primitive component
[ https://issues.apache.org/jira/browse/UIMA-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marshall Schor resolved UIMA-1666. -- Resolution: Fixed Fix Version/s: 2.3AS Assignee: Marshall Schor Bhavani, can you verify this fix? CasPoolSize should equal numberOfInstances when deploying a primitive component --- Key: UIMA-1666 URL: https://issues.apache.org/jira/browse/UIMA-1666 Project: UIMA Issue Type: Bug Components: Async Scaleout Reporter: Bhavani Iyer Assignee: Marshall Schor Fix For: 2.3AS When deploying a primitive component, the cas pool size should equal the number of instances. If a user explicitly sets the cas pool size in the deployement descriptor, it should be overridden and set to the number of instances and a warning log message written. If set to less than the number of instance, the user does not get the expected performance improvement and its too easy to get this wrong. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
