You are not logged in.
Pages: 1
If we set the following configuration in the X-EventCollector Connector section:
<sxi:ReadNewOnly>Yes</sxi:ReadNewOnly>
what we see is that X-EventCollector hangs. However if you look in the X:\SXI\X-EventCollector\bin directory you will see an error.log file. The top line will look something like this:
java.security.AccessControlException: access denied org.apache.derby.security.SystemPermission( "engine", "usederbyinternals" )
To address this issue edit the java.policy file which can be found in the C:\SXI\jre\lib\security directory.
Add the following line to the bottom of the grant { section.
permission org.apache.derby.security.SystemPermission "engine", "usederbyinternals";
Your policy file should end looking something like this:
permission java.util.PropertyPermission "java.vm.vendor", "read";
permission java.util.PropertyPermission "java.vm.name", "read";
permission org.apache.derby.security.SystemPermission "engine", "usederbyinternals";
};
Offline
When using Red Hat Open JDK with XLayer V2.
To address the issue with X-EventCollector not work, edit the java.policy file which can be found in the C:\SXI\jre\jre\lib\security directory.
Add the following line to the bottom of the grant { section.
permission org.apache.derby.security.SystemPermission "engine", "usederbyinternals";
Your policy file should end looking something like this:
permission java.util.PropertyPermission "sun.security.pkcs11.disableKeyExtraction", "read";
permission org.apache.derby.security.SystemPermission "engine", "usederbyinternals";
};
Offline
Pages: 1