[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15630967#comment-15630967
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 92f56ea9dd72d935c21aadae6a20ee23fa9c3cf8 in lucene-solr's branch
refs/heads/apiv2 from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=92f56ea ]
LUCENE-7135: only use OS_ARCH if we couldn't access sun.arch.data.model
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628957#comment-15628957
]
Michael McCandless commented on LUCENE-7135:
One nice side effect of this 2 day accident was it caused e.g. our nightly geo
benchmark https://people.apache.org/~mikemccand/geobench.html to use
{{NIOFSDirectory}} instead of {{MMapDirectory}}, so we get to see at least for
this benchmark how much better {{MMapDirectory}} is!
I'm working on nightly benchmarks for the sparse case, preview here:
https://people.apache.org/~mikemccand/lucenebench/sparseResults.html#search_sort_qps
There's an even bigger drop in that benchmark, which is what made me think
there might be an issue with this change in the first place. Benchmarking is
important :)
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628916#comment-15628916
]
Michael McCandless commented on LUCENE-7135:
No worries [~amake], stuff happens :) I'm just glad we caught it before 6.3.0
was out.
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628674#comment-15628674
]
Aaron Madlon-Kay commented on LUCENE-7135:
--
Very sorry about that!
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628575#comment-15628575
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit a66a44513ee8191e25b477372094bfa846450316 in lucene-solr's branch
refs/heads/branch_6_3 from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a66a445 ]
LUCENE-7135: only use OS_ARCH if we couldn't access sun.arch.data.model
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628567#comment-15628567
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 92f56ea9dd72d935c21aadae6a20ee23fa9c3cf8 in lucene-solr's branch
refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=92f56ea ]
LUCENE-7135: only use OS_ARCH if we couldn't access sun.arch.data.model
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628568#comment-15628568
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 97c97838022efcac8ccbcffb5edf5735605fdf17 in lucene-solr's branch
refs/heads/branch_6x from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=97c9783 ]
LUCENE-7135: only use OS_ARCH if we couldn't access sun.arch.data.model
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628559#comment-15628559
]
Michael McCandless commented on LUCENE-7135:
There is a bug in the logic here: it marks a 64 bit JVM as 32 bit!
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628264#comment-15628264
]
Michael McCandless commented on LUCENE-7135:
OK I backported this for 6.3.0
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15628262#comment-15628262
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 08526f581edef098cd94e899beef2a0fff95535c in lucene-solr's branch
refs/heads/branch_6_3 from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=08526f5 ]
LUCENE-7135: work around security manager when checking for 32/64 bit JVM
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 5.5.4, 6.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622548#comment-15622548
]
Michael McCandless commented on LUCENE-7135:
Woops, thanks [~shalinmangar], I fixed it.
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 5.5.4, 6.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622532#comment-15622532
]
Shalin Shekhar Mangar commented on LUCENE-7135:
---
This issue is marked for 6.3 but it was not backported to branch_6_3. So the
fix version should be 6.4
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622457#comment-15622457
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit f9e2f0c5b65b389e330a16657396a922e47fce1d in lucene-solr's branch
refs/heads/branch_6x from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f9e2f0c ]
LUCENE-7135: add issue number in CHANGES.txt
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15622456#comment-15622456
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 2baad4c22d05a1fcc4a09044eae868b6a5bfe1cf in lucene-solr's branch
refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=2baad4c ]
LUCENE-7135: add issue number in CHANGES.txt
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620854#comment-15620854
]
Aaron Madlon-Kay commented on LUCENE-7135:
--
Understood. Thanks!
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3, 5.5.4
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620849#comment-15620849
]
Aaron Madlon-Kay commented on LUCENE-7135:
--
Thanks very much for your help, ~mikemccand.
Is there any hope for a backport to 5? I suspect it will take a long time for
our dependencies to move up.
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620814#comment-15620814
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 96372be35c7c7d937561ce5d526d688ab447cd86 in lucene-solr's branch
refs/heads/branch_6x from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=96372be ]
LUCENE-7135: work around security manager when checking for 32/64 bit JVM
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Fix For: master (7.0), 6.3
>
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15620812#comment-15620812
]
ASF subversion and git services commented on LUCENE-7135:
-
Commit 813b6855656ecd50a7a28376822bd7b65154cee8 in lucene-solr's branch
refs/heads/master from Mike McCandless
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=813b685 ]
LUCENE-7135: work around security manager when checking for 32/64 bit JVM
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15619694#comment-15619694
]
Michael McCandless commented on LUCENE-7135:
> That's precisely what my patch does.
Woops, sorry, I did not look closely enough: you're right!
OK I think this is a good approach ... I'll push soon. Thanks [~amake]!
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15619692#comment-15619692
]
Michael McCandless commented on LUCENE-7135:
> That's precisely what my patch does.
Woops, sorry, I did not look closely enough: you're right!
OK I think this is a good approach ... I'll push soon. Thanks [~amake]!
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15619342#comment-15619342
]
Aaron Madlon-Kay commented on LUCENE-7135:
--
> Maybe we should only do this on fallback
That's precisely what my patch does.
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15615391#comment-15615391
]
Michael McCandless commented on LUCENE-7135:
Is {{OS_ARCH.contains("64"))}} really a safe way to determine if we are running
in a 64 bit JVM? Maybe we should only do this on fallback, if the security
manager doesn't let us do {{System.getProperty("sun.arch.data.model")}}?
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15600560#comment-15600560
]
Aaron Madlon-Kay commented on LUCENE-7135:
--
Since there has been no action on this issue, we were forced to publish our
patched version:
- https://bintray.com/omegat-org/maven/lucene-core
- Available in JCenter as {{compile 'org.omegat.lucene:lucene-core:5.2.1'}}
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (LUCENE-7135) Constants check for JRE bitness causes SecurityException under WebStart
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278502#comment-15278502
]
Trejkaz commented on LUCENE-7135:
-
I see this when running our unit tests also. Evidently somewhere up the call
chain there is some code we don't trust calling us. We then call Lucene, which
ultimately calls this stuff.
(We're bitten by LUCENE-6923 as well, because we are still on 5.4.)
> Constants check for JRE bitness causes SecurityException under WebStart
> ---
>
> Key: LUCENE-7135
> URL: https://issues.apache.org/jira/browse/LUCENE-7135
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/other
>Affects Versions: 5.5
> Environment: OS X 10.11.4, Java 1.8.0_77-b03 (under WebStart)
>Reporter: Aaron Madlon-Kay
> Attachments: LUCENE-7135.diff
>
>
> I have an app that I deploy via WebStart that uses Lucene 5.2.1 (we are
> locked to 5.2.1 because that's what [LanguageTool|https://languagetool.org/]
> uses).
> When running under the WebStart security manager, there are two locations
> where exceptions are thrown and prevent pretty much all Lucene classes from
> initializing. This is true even when we sign everything and specify
> {{}}.
> # In {{RamUsageEstimator}}, fixed by LUCENE-6923
> # In {{Constants}}, caused by the call
> {{System.getProperty("sun.arch.data.model")}} (stack trace below).
> {code}
> Error: Caused by: java.security.AccessControlException: access denied
> ("java.util.PropertyPermission" "sun.arch.data.model" "read")
> Error:at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
>
> Error:at
> java.security.AccessController.checkPermission(AccessController.java:884)
> Error:at
> java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> Error:at
> com.sun.javaws.security.JavaWebStartSecurity.checkPermission(Unknown Source)
> Error:at
> java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1294)
> Error:at java.lang.System.getProperty(System.java:717)
> Error:at org.apache.lucene.util.Constants.(Constants.java:71)
> Error:... 34 more
> {code}
> The latter is still present in the latest version. My patch illustrates one
> solution that appears to be working for us.
> (This patch, together with a backport of the fix to LUCENE-6923, seems to fix
> the issue for our purposes. However if you really wanted to make my day you
> could put out a maintenance release of 5.2 with both fixes included.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
