BIRTViewer startup errors in WAS when Java 2 security is enabled

On Websphere Application Server , when Java 2 security is enabled the BIRTViewer throws up few errors at the time of startup

[4/4/11 15:49:14:847 BST] 0000000a FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /p8880/logs/ffdc/server1_764b764b_11.04.04_15.49.14.8396342556118287165467.txt com.ibm.ws.security.core.SecurityManager 180
[4/4/11 15:49:14:850 BST] 0000000a SecurityManag W SECJ0314W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. Refer to the InfoCenter for further information.

Permission:

was.repository.root : Access denied (java.util.PropertyPermission was.repository.root write)

Code:
org.eclipse.osgi.framework.internal.core.FrameworkProperties in {file:/p8880/installedApps/myNode01Cell/BIRTReportViewer.ear/BIRTReportViewer.war/WEB-INF/platform/plugins/org.eclipse.osgi_3.6.1.R36x_v20100806.jar}

The details of the stacktrace are attached.
This issue however seems to go away when the following steps are taken
[/list]In the config.ini of the BIRTViewer add an entry
eclipse.security=null
[/list] Include a was.policy file and provide explicit permission to the BIRTViewer application as java.security.AllPermission

This seems to be more a hack rather than a fix and also having the eclipse.security=null entry does not seem to work in Tomcat .
What are the implications of the above hack? If you can provide some info on any possible side effects , would be greatly helpful

Cheers
Vijay

Find more posts tagged with

Comments

JasonW

Have you looked over this bug?
https://bugs.eclipse.org/bugs/show_bug.cgi?id=182161

Jason

VijayTS

Hi Jason ,

I did go over the defect you mentioned . It seems to be that having eclipse.security=null ,resolves the issue to a certain extent . I wanted to clarify about the repercussions of having this entry , I could not find documentation which talks about having this entry ,and also giving specific permissions in the was.policy . If this fix/hack is the right way to go about .. should it be documented ? I can provide the detailed documentation as needed

Thanks in advance
Vijay

JasonW

Vijay,

It would be good if you could add your notes to the bug and also add to the birt wiki.
Here:
http://wiki.eclipse.org/BIRT/FAQ
You may just want to add an entry under deployment.

Thanks

Jason