[
https://issues.apache.org/jira/browse/LUCENE-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-4337:
----------------------------------
Attachment: LUCENE-4337.patch
Attached is a patch that works around some problems:
- the JMX problem: Unfortunately this is all messy, as Java's RMI servers by
default always bind to 0.0.0.0 and use their own hostname to find the IP
address when creating bean proxies (see
http://weblogs.java.net/blog/emcmanus/archive/2006/12/multihomed_comp.html,
there is also a JDK bug open about that). The workaround was to use a
SocketFactory and a sysprop. The good thing of this fix is that now my Windows
Box does not always pop up a Firewall Requester when TestJmxMonitoredMap is
running...
- The TIKA Problem with BouncyCastle was solved by adding another permission
The remaining issue is only *one* test spawning the MultiCore example server
and writing to files inside the example server, which they should not do in
tests. My idea would be to copy the example server to a tmpDir and start it
from there?
> Create Java security manager for forcible asserting behaviours in testing
> -------------------------------------------------------------------------
>
> Key: LUCENE-4337
> URL: https://issues.apache.org/jira/browse/LUCENE-4337
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.1, 5.0, 4.0
> Reporter: Greg Bowyer
> Assignee: Greg Bowyer
> Attachments: LUCENE-4337.patch, LUCENE-4337.patch
>
>
> Following on from conversations about mutation testing, there is an interest
> in building a Java security manager that is able to assert / guarantee
> certain behaviours
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
