[Udo Held]

As you announced MyEclipse Blue Edtion 9.0m2 with WebSphere Portal 7 I tried to evaluate it.

Unfortunately I cannot start the Portal from MyEclipse IDE it comes up with:

Exception in thread “main” java.security.AccessControlException: Access denied (java.util.PropertyPermission eclipse.exitcode read)
at java.security.AccessController.checkPermission(AccessController.java:108)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:533)
at java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1286)
at java.lang.System.getProperty(System.java:383)
at java.lang.System.getProperty(System.java:367)
at org.eclipse.core.launcher.Main.run(Main.java:987)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:340)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:110)
Exception in thread “Thread-4” java.security.AccessControlException: Access denied (java.io.FilePermission C:\IBM\WebSphere\AppServer7N\profiles\wp_profile\temp\osgi_instance_location\clavis\2086095920 read)
at java.security.AccessController.checkPermission(AccessController.java:108)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:533)
at java.lang.SecurityManager.checkRead(SecurityManager.java:872)
at java.io.File.isDirectory(File.java:752)
at com.ibm.wsspi.bootstrap.WSPreLauncher.deleteEclipseInstanceArea(WSPreLauncher.java:586)
at com.ibm.wsspi.bootstrap.WSPreLauncher.onExit(WSPreLauncher.java:577)
at com.ibm.wsspi.bootstrap.WSPreLauncher$OnExit.run(WSPreLauncher.java:568)

I made the following settings in the Server Connector:
WebSphere Portal Server: Enable
Portal Home: C:\IBM\WebSphere\PortalServer
WAS Home: C:\IBM\WebSphere\AppServer7N
Profile Directory: C:\IBM\WebSphere\AppServer7N\profiles\wp_profile

Aftwards it figured out the right Node, Cell and ServerName.
I also entered the Username and Passwort.

I left the settings on the Advanced Tab unchanged. What is causing the error? I can run the portal from the command line or the RAD without problems. Its a WP 7 on WAS 7.

I also tried using a policy file I found in the profile directory, however this didn’t seem to work either. I hope I get the problem solved before the trail runs out so that I can verify the functionality.

Kind regards

[Brian Fernandes]

clavis,

Thanks for trying MyEclipse 9.0 M2. We have a bug filed against this issue and if a fix is required, we will release an update shortly.

Sometimes due to security settings you may need to run MyEclipse Blue as administrator for it to have the permissions required to start WebSphere servers. Depending on your version of Windows, you may need to right click the shortcut and select “Run as Administrator” – can you try this and let me know if it allows you to start and stop the server or if the problem still persists?

[Udo Held]

Hi,

I tried that. The VM is running Windows 7 Ultimate. I started MyEclipse with the “Run as Administrator” option. Unfortunately the error message is the same. I don’t need to start the RAD as an administrator and the portal runs from the commandline without administrator options as well.

Kind regards

[Brian Fernandes]

clavis,

Thanks for the quick reply – I have a few additional questions that should help us track this down:
1) Is your portal server installation installed as a service? If so, an you stop the service if t is started?
2) Is RAD running at the same time? Possible that RAD has started Portal server and is this locking the directory – can you ensure that portal server is shut down and RAD is not running either?
3) As a test, could you try creating a new portal server profile and point our connector to that instead – does it work?

[Brian Fernandes]

clavis,

We’d also like to double check that you have the right profile directory specified.

1) Does your profile folder “C:\IBM\WebSphere\AppServer7N\profiles\wp_profile” contain the following files
a) properties/client.policy
b) PortalServer/bin/wpscript.bat

2) Do you have another wp_profile folder at C:\IBM\WebSphere\wp_profile ?

[Udo Held]

Hmm. I thought I answered to your first questions, but I cannot see the answer here.

1) Its not running as a service.
2) I stopped the RAD before and I stopped the portal as well.
3) I’m not able to create a new profile. My portal was installed by our system engineering with some installation scripts.

Second post:

1)
a) Yes, there is a client.policy file.
b) Yes, there is a wpscript.bat.

2) No.

Kind regards

[Udo Held]

As per your indirect suggestion. I entered the complete path to the client.policy file on the Advanced Tab. I can now start the Portal Server with MyEclipse.

[Brian Fernandes]

clavis,

Good thinking and thanks for posting back. Was there some path specified to the client.policy file on the Advanced tab or was it empty? If a value was specified, do you recall roughly what it was?

[Udo Held]

Hi Brian,

it was simply empty.

Kind regards

[ofer.baranes]

I have the same problem.
When a fix would be available?
is there a workaround? can i temporarily manipulate java security files to avoid this error?
Also, the stack trace point to ‘onExit’, why? is that error as part of server shutdown?!

[Brian Fernandes]

ofer,

Do you have exactly the same problem? If not, please start a new thread.

As clavis pointed out above, the policy field on the Advanced tab was empty, and it worked after he added the path to his policy file there. Can you do the same? As far as a fix is concerned, we will look into auto populating that field with the right policy file in future versions of MyEclipse – no fix to internal working is required.

[ofer.baranes]

adding the policy file solved the problem. thanks

[Author]

Posts