facebook

Error Starting Websphere Portal 7 through MEB 2013

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #339284 Reply

    bigsing90
    Member

    I am having issues starting my websphere portal 7 profile through MEB 2013 on Windows 7. The portal runtime is installed as a windows service. I can successfully start the service through windows and through RAD 8. I’ve also tried running MEB as an administrator. Below is the error i am receiving on startup, i’ve also attached my installation details and .log file.

    Thanks in advance for all your help.

    Websphere Error:

    [5/21/13 10:39:07:354 EDT] 00000000 ApplicationPa W SECJ0166W: Expand exception occurred. Skip the grant entry in app.policy file. The exception is com.ibm.ws.security.policy.Parser$ExpandException: line 67: unable to expand “com.ibm.websphere.client.applicationclient.archivedir”
    at com.ibm.ws.security.policy.ApplicationParser.expand(ApplicationParser.java:209)
    at com.ibm.ws.security.policy.ApplicationParser.parseGrantEntry(ApplicationParser.java:86)
    at com.ibm.ws.security.policy.Parser.parse(Parser.java:61)
    at com.ibm.ws.security.policy.WSDynamicPolicy.<init>(WSDynamicPolicy.java:123)
    at com.ibm.ws.security.core.distSecurityComponentImpl.initializeJava2Sec(distSecurityComponentImpl.java:1506)
    at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:348)
    at com.ibm.ws.security.core.SecurityComponentImpl.initialize(SecurityComponentImpl.java:94)
    at com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(ContainerHelper.java:1191)
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComponent(ContainerHelper.java:1098)
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComponents(ContainerHelper.java:900)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:776)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:750)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:332)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:280)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:213)
    at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
    at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:340)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
    at org.eclipse.core.launcher.Main.run(Main.java:981)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:341)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)
    .

    Attachments:
    You must be logged in to view attached files.
    #339324 Reply

    support-swapna
    Moderator

    bigsing90,

    Sorry that you are seeing this issue.

    Can you please check few more things for us ?

    1. Can you please start WAS using RAD, check the list of arguments and then launch it from MyEclipse ?
    Here are the links which give more information about getting the list of arguments :

    http://windowsxp.mvps.org/listproc.htm
    http://serverfault.com/questions/323795/display-complete-command-line-including-arguments-for-windows-process

    Copy paste the list of arguments here for us to take a look.

    2. Can you please try not to install Websphere as Windows Service and see how it works with MyEclipse ?
    3. Can you please switch to a new workspace , replicate the isssue and attach the .log file which is located at <workspace dir>/.metadata/.log.

    Let us know how it works for you.

    #339328 Reply

    bigsing90
    Member

    1) I’ve attached process lists for both RAD & MEB. Note that RAD also creates a WASService.exe

    2) I will check into this, although i may be unable to do this due to company restrictions.

    3) See attached txt file

    Something I had forgot about as I created my initial connector a week ago. Nothing was pre-populated in the websphere portal 7 connector settings. I had to manually enter the settings tab (WebSphere Portal Home, WebSphere AppServer Home, etc), the advanced settings, and the JDK.

    Attachments:
    You must be logged in to view attached files.
    #339355 Reply

    support-piotr
    Participant

    bigsing90,

    First of all, if fields weren’t autopopulated, you might have entered incorrect values, especially on the advanced page. For the rest of the values to auto populate, you need to browse for in the following order:
    1. WebSphere Portal Home (e.g. /opt/IBM/WebSphere/Portal70/PortalServer)
    2. WebSphere AppServer Home (e.g. /opt/IBM/WebSphere/Portal70/AppServer)
    3. WebSphere Profile Portal Directory (e.g. /opt/IBM/WebSphere/Portal70/wp_profile)

    It would be the best if you try with a fresh workspace.

    During the comparison of the processes arguments I’ve found that some of the paths were set incorrectly, e.g.:

    -Dcom.ibm.itp.location=C:\IBM_Portal7\WebSphere\PortalServer\bin
    

    should be

    -Dcom.ibm.itp.location=C:\IBM_Portal7\WebSphere\AppServer\bin 
    

    And

    -Djava.security.policy=C:\IBM_Portal7\WebSphere\wp_profile\properties\client.policy

    should be

    -Djava.security.policy=C:\IBM_Portal7\WebSphere\wp_profile\properties\server.policy

    You can try to correct that on the advanced page, but there might be more errors.

    Let us know if you were able to get WAS Portal up and running!

    #339378 Reply

    bigsing90
    Member

    Changing those settings has seemed to do the trick. Thanks so much for all of your help!

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: Error Starting Websphere Portal 7 through MEB 2013

You must be logged in to post in the forum log in