Topic
  • 5 replies
  • Latest Post - ‏2012-09-11T04:03:58Z by Shawn_Jiang
Imhy
Imhy
17 Posts

Pinned topic Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

‏2012-07-11T22:56:14Z |
Hello!

Unable run WASCE 3.0.0.2 server in eclipse (indigo, juno)
When i try start WASCE in eclipse i get error:
Error launching framework: org.eclipse.osgi.framework.internal.core.Framework$DuplicateBundleException: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed from: mvn:org.apache.aries.proxy/org.apache.aries.proxy/0.3

Please help.
Updated on 2012-09-11T04:03:58Z at 2012-09-11T04:03:58Z by Shawn_Jiang
  • Shawn_Jiang
    Shawn_Jiang
    154 Posts

    Re: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

    ‏2012-07-12T01:59:01Z  
    There's an issue with Juno. If you are still experience this issue with Eclipse indigo. Please tell us:

    1, OS
    2, JDK version
    3, the server.log file under your WASCE_HOME/var/log
    4, The detail steps on how can we recreate this issue.
  • Imhy
    Imhy
    17 Posts

    Re: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

    ‏2012-07-12T13:35:26Z  
    There's an issue with Juno. If you are still experience this issue with Eclipse indigo. Please tell us:

    1, OS
    2, JDK version
    3, the server.log file under your WASCE_HOME/var/log
    4, The detail steps on how can we recreate this issue.
    Hi.
    I`m using
    1. Windows 7 Enterprise 64-bit
    2. i try to use jdk 1.6.0_32 32-bit, jdk 1.7.0_04 (32-bit and 64-bit)
    3. Server log not created if i run wasce from eclipse.
    4. I use clean installation of eclipse indigo R2 Build id: 20120216-1857(32-bit and 64-bit) downloaded from eclipse.org and only WASCE v3.0.0 Server Adapter plugin installed Version: 3.0.0.v20120618-130145
    In eclipse I add new IBM WASCE v3.0 Server runtime environment. After that in "servers" tab of eclipse I select this server and press menu "Start"
  • Shawn_Jiang
    Shawn_Jiang
    154 Posts

    Re: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

    ‏2012-07-12T14:36:45Z  
    • Imhy
    • ‏2012-07-12T13:35:26Z
    Hi.
    I`m using
    1. Windows 7 Enterprise 64-bit
    2. i try to use jdk 1.6.0_32 32-bit, jdk 1.7.0_04 (32-bit and 64-bit)
    3. Server log not created if i run wasce from eclipse.
    4. I use clean installation of eclipse indigo R2 Build id: 20120216-1857(32-bit and 64-bit) downloaded from eclipse.org and only WASCE v3.0.0 Server Adapter plugin installed Version: 3.0.0.v20120618-130145
    In eclipse I add new IBM WASCE v3.0 Server runtime environment. After that in "servers" tab of eclipse I select this server and press menu "Start"
    OK, I just verified and can't recreate your issue with my win7 64bit + sun jdk7 64bit + indigo 64bit + CE 3.0.0.2 + WEP 3.0. The new created server in Eclipse can be started without any problem.

    Can you try to start the CE server with CE_HOME/bin/startup.bat script directly ?
  • Imhy
    Imhy
    17 Posts

    Re: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

    ‏2012-07-12T21:07:14Z  
    OK, I just verified and can't recreate your issue with my win7 64bit + sun jdk7 64bit + indigo 64bit + CE 3.0.0.2 + WEP 3.0. The new created server in Eclipse can be started without any problem.

    Can you try to start the CE server with CE_HOME/bin/startup.bat script directly ?
    Thank You.
    I`m completly reinstall wasce and eclipse. Now it working in eclipse indigo R2 64-bit.
    May be problem was in that i install wasce 3.0.0.2 in folder with old wasce 3.0.0.1 .
  • Shawn_Jiang
    Shawn_Jiang
    154 Posts

    Re: Bundle "org.apache.aries.proxy" version "0.3.0" has already been installed

    ‏2012-09-11T04:03:58Z  
    • Imhy
    • ‏2012-07-12T21:07:14Z
    Thank You.
    I`m completly reinstall wasce and eclipse. Now it working in eclipse indigo R2 64-bit.
    May be problem was in that i install wasce 3.0.0.2 in folder with old wasce 3.0.0.1 .
    I guess you were using WASCE under a symbolic path when you encountered the issue. If so, you might want to check this[1] out and apply the patch there.

    [1]http://www-01.ibm.com/support/docview.wss?uid=swg21609953