Error Configuring BEA Weblogic Server v9.2

I'm using Eclipse 3.4 (Ganymede) with the new Enterprise Pack for Eclipse. When I try to create a New Server Runtime Environment for Weblogic 9.2, I get the following error:
"RE is selected, but the path is invalid."
The path is D:\export\webapps\sbea\weblogic92 which is correct because I successfully used that with Eclipse 3.3 with BEA Weblogic Weblogic 9.2 runtime that you could access from Eclipse 3.3.

I was able to fix this by uninstalling all BEA products and re-installing WLS 9.2M1.

Similar Messages

  • An internal error occurred during: "Starting BEA WebLogic Server v8.1 at lo

    Hi,
    On "Start the server in debug mode"
    file .log
    eclipse.buildId=I20090611-1540
    java.version=1.6.0_13
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=es_AR
    Command-line arguments: -os win32 -ws win32 -arch x86
    !ENTRY org.eclipse.core.jobs 4 2 2009-08-05 12:29:57.060
    !MESSAGE An internal error occurred during: "Starting BEA WebLogic Server v8.1 at localhost".
    !STACK 0
    java.lang.NullPointerException
         at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.findWorkshopJspDebuggerLaunchConfigurationDelegate(GenericWeblogicServerBehaviour.java:477)
         at oracle.eclipse.tools.weblogic.legacy.GenericWeblogicServerBehaviour.setupLaunch(GenericWeblogicServerBehaviour.java:226)
         at org.eclipse.jst.server.generic.core.internal.ExternalLaunchConfigurationDelegate.launch(ExternalLaunchConfigurationDelegate.java:101)
         at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
         at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
         at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:696)
         at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3057)
         at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3007)
         at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:294)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    OS= Windows XP SP2
    Eclipse Java Version= 1.6.0_13
    Workspace Java Version= 1.4.2_08
    BEA Weblogic= 8.1.6
    Eclipse= 3.5.0
    WTP= 3.1.0
    Project Facets= Dynamic Web Module 2.3
    Java= 1.4
    Tanks and sorry my English.
    Gustavo

    I am also experiencing the same NullPointerException when launching Weblogic 8.1 in debug mode within Eclipse 3.5. Is there any anticipated fix for this issue, or a bugtraq record that we can follow to know when the issue is addressed? I do not expect JSP debugging to work (as it wasn't available with Weblogic 8.1 under Eclipse 3.4 either) - BUT right now I cannot debug ANY server-side code within Weblogic 8.1 in Eclipse 3.5 as the server cannot start in debug mode at all.
    Many thanks.

  • Bea weblogic server 6.1 - Failure in process sockets - Java.lang.NoSuchmethod Error

    Hi
    I have installed the BEA weblogic server 6.1 service pack 4 as part of PIA (PeopleSoft
    Internet Architecture) installation for PeopleSoft 8.8.
    After starting the weblogic server, When I type the
    http://localhost:12080 (http port number 12080) ideally it should take me to
    the BEA home page, but it is throwing an error in the log file.
    " Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
    Your help is very much appreciated.
    Any pointers are welcome.
    Thanks
    Aswartha

    I had similar problems with my install of Weblogic 6.1 sp4. I am installing PS
    HRMS 8.8 sp1
    and PeopleTools 8.44 Patch 2 (Patch 2 is required for install) Peoplesoft sent
    me Weblogic 8.1
    with my new Tools 8.44. This version and installation is light years ahead of
    Weblogic 6.1. If
    you are able to load the new version of Weblogic and Tuxedo, it is worth it.
    If not, you may want to check to see if your JAR file was installed correctly.
    (The new version
    of WL doesn't make you unzip your JAR files for the install.)
    In the command line for unzipping the JAR file, make sure you type the phrase
    EXACTLY as
    shown IT IS CASE SENSITIVE. I messed with this for two hours until I saw that
    I wasn't putting
    a capital letter in one of the words where I should have been.
    Hope this helps.
    "Aswarth" <[email protected]> wrote:
    >
    Hi
    I have installed the BEA weblogic server 6.1 service pack 4 as part of
    PIA (PeopleSoft
    Internet Architecture) installation for PeopleSoft 8.8.
    After starting the weblogic server, When I type the
    http://localhost:12080 (http port number 12080) ideally it should take
    me to
    the BEA home page, but it is throwing an error in the log file.
    " Failure in Process sockets - Get Data Java.lang.nosuchmethod error"
    Your help is very much appreciated.
    Any pointers are welcome.
    Thanks
    Aswartha

  • Trouble defining BAM Enterprise Message Source for BEA WebLogic Server

    Hi all,
    I've just started to play a little with Oracle BAM Architect.
    I've WLS 10.0 and Oracle BAM Architect 10g release 3.
    On Oracle BAM Architect I've defined an Enterprise Message Source for BEA WebLogic Server as follows:
    Name: ALSBSource
    Owner: ...
    Type: BEA WebLogic Server
    Initial context factory: weblogic.jndi.WLInitialContextFactory
    JNDI Service Provider URL: t3://mypc:7001
    TopicConnectionFactory name: com.myConnectionFactory
    Topic name: com.myBAMTopic
    JMS message type: TextMessage
    Durable subscriber name: BAMSubscriber
    Client ID: BAMSubscriber
    Name | Flow name | Type | Max size | Formatting
    content | BAM | String | 1024 | (none)
    On WLS 10.0 I've defined the required JMS stuff.
    On Oracle Design Studio I've defined a plan that includes:
    - an Oracle BAM Enterprise Message Receiver from which I've selected the above 'ALSBSource' Enterprise Message Source
    - a simple Grid
    I've connected the BAM Enterprise Message Receiver to the Grid and clicked on 'Update' button.
    When I try to publish a message on 'com.myBAMTopic' I don't see anything on the grid defined in the Oracle Design Studio.
    The first question is about the definition of an Enterprise Message Source for BEA WebLogic Server in the Oracle BAM Architect.
    I did not change the Oracle BAM Architect classpath or Oracle Design Studio classpath adding the weblogic.jar, because no error has been raised during the configuration of the message source and the plan. Should I update Oracle classpath with the weblogic.jar ?
    Did I forget any other step ?
    I thank you in advance for any feedback.
    Regards
    ferp

    ferp - I got this to work with
    JNDI Service Provider URL: http://localhost
    When I add the port
    JNDI Service Provider URL: http://localhost:23891
    I cannot get my EMS to start.
    Hopefully this should fix your issue.
    Sudeep.

  • Error , while stopping Weblogic server 5.1

    Hello,
    Encountered the following error while stopping the bea Weblogic server 5.1 on
    AIX 4.3. Seeking for Valuable solution / Suggestion.
    Submitting shutdown command to Weblogic Server on Port 80.
    Failed to connect to t3://10.72.111.15:80 due to :
    [Weblogic.rmi. Unexpected Exception: Marshalling
    -with nested exception:
    [Weblogic.rjvm.PeerGoneException:
    -with nested exception:
    [Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception creating
    response stream] - with nested exception:
    [java.io.InvalidClassException:
    weblogic.security.acl.internal.AuthenticatedUser;Local Class not compatible: Stream
    Classdesc serialVersionUID=6699361079932480379
    local class serialVersionUID=2825328378974757378]]]]

    Narayan,
    Can you provide more information on the configuration, JDK, Service Pack
    level and also manner in which you shutdown the server.
    Can you try using the following command to shutdown the server
    java weblogic.Admin URL SHUTDOWN system password
    http://www.weblogic.com/docs51/admindocs/weblogicserver.html#shutdown
    Also make sure you set the classpath before running this command
    If you are testing with any service pack prior to sp8, I would suggest you
    test with the latest service pack for WebLogic Server 5.1 which is sp10.
    If you need just the service pack for WLS 5.1 , you will need to have a
    websupport login and password. Please refer to this url for more
    information on this.
    http://contact.bea.com/bea/www/BEACustRegLogin.jsp
    http://websupport.bea.com/custsupp/
    Hope this helps
    Raj Alagumalai
    "Narayan" <[email protected]> wrote in
    news:3ba61ba3$[email protected]:
    >
    Hello,
    Encountered the following error while stopping the bea Weblogic server
    5.1 on AIX 4.3. Seeking for Valuable solution / Suggestion.
    Submitting shutdown command to Weblogic Server on Port 80.
    Failed to connect to t3://10.72.111.15:80 due to :
    [Weblogic.rmi. Unexpected Exception: Marshalling
    -with nested exception:
    [Weblogic.rjvm.PeerGoneException:
    -with nested exception:
    [Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception
    creating response stream] - with nested exception:
    [java.io.InvalidClassException:
    weblogic.security.acl.internal.AuthenticatedUser;Local Class not
    compatible: Stream Classdesc serialVersionUID=6699361079932480379
    local class serialVersionUID=2825328378974757378]]]]

  • Error while stopping Weblogic server

    I have created a new domain and installed my application here, after deplotyment when i stop teh server it throws the following exception:
    Cannot shutdown a server when using a BootIdentify file AND running in Production mode
    I have created boot.properties file also.still it is throwing this error,.I am not getting any clue on this error, there is no clear details availablei n the archives also , so please advise.
    Thanks
    Vishy

    Narayan,
    Can you provide more information on the configuration, JDK, Service Pack
    level and also manner in which you shutdown the server.
    Can you try using the following command to shutdown the server
    java weblogic.Admin URL SHUTDOWN system password
    http://www.weblogic.com/docs51/admindocs/weblogicserver.html#shutdown
    Also make sure you set the classpath before running this command
    If you are testing with any service pack prior to sp8, I would suggest you
    test with the latest service pack for WebLogic Server 5.1 which is sp10.
    If you need just the service pack for WLS 5.1 , you will need to have a
    websupport login and password. Please refer to this url for more
    information on this.
    http://contact.bea.com/bea/www/BEACustRegLogin.jsp
    http://websupport.bea.com/custsupp/
    Hope this helps
    Raj Alagumalai
    "Narayan" <[email protected]> wrote in
    news:3ba61ba3$[email protected]:
    >
    Hello,
    Encountered the following error while stopping the bea Weblogic server
    5.1 on AIX 4.3. Seeking for Valuable solution / Suggestion.
    Submitting shutdown command to Weblogic Server on Port 80.
    Failed to connect to t3://10.72.111.15:80 due to :
    [Weblogic.rmi. Unexpected Exception: Marshalling
    -with nested exception:
    [Weblogic.rjvm.PeerGoneException:
    -with nested exception:
    [Weblogic.utils.AssertionError: **** ASSERTION FAILED ***** [Exception
    creating response stream] - with nested exception:
    [java.io.InvalidClassException:
    weblogic.security.acl.internal.AuthenticatedUser;Local Class not
    compatible: Stream Classdesc serialVersionUID=6699361079932480379
    local class serialVersionUID=2825328378974757378]]]]

  • [BEA WEBLOGIC SERVER 5.1 sp8] performance pack load problem ....

    Hi,
    I am trying to use the weblogic server performance pack on BEA WEBLOGIC SERVER 5.1
    sp8.
    As explained in the following doc : http://www.weblogic.com/docs51/admindocs/tuning.html#performance%20packs
    I use the following configuration :
    weblogic.properties : weblogic.system.nativeIO.enable=true
    LD_LIBRARY_PATH is set to "/bea/weblogic/wls510_sp8/lib/solaris"
    Technical environement : SunOS 5.8 Generic_108528-06
    But when I restart the server I have the following message :
    "Mo Jun 03 18:19:06 CEST 2002:<A> <Posix Performance Pack> Could not initialize POSIX
    Performance Pack.
    Mo Jun 03 18:19:06 CEST 2002:<E> <Performance Pack> Unable to load performance pack,
    using Java I/O."
    Could you help me on this point, please ?

    I think my Q is not clear. I shall explain how the application works. I am having application based on Swings and that is a website building program. User has options like ading an image into their site with an element called 'Image' available as part of the system. Then user can either select an image from the picture gallery provided or can upload his own image.
    Now, if the user is uploading a picture that has space in name ( we use a servlet program to upload the image into user directory), it will get uploaded. But when the swing program tries to paint the image in the Image element ( It is essentially a JLabel ), the program is sending a request to the WL server. Since the URL contains space in name, server returns error. Even if do URL Encoding, it will add %20 in the URL and still WL will report error saying that file not found. It seems that WL is unable to process requests that has space in the URL.
    If any one has any solution to this, please help..
    Liju

  • Error while starting weblogic server

    Hi, I am getting following error while starting weblogic server
    Unexpected Signal : 11 occurred at PC=0x40170bc5 Function name=fill_in_stack_trace__19java_lang_ThrowableG6HandleP6Thread
    Library=/bea/jdk131/jre/lib/i386/client/libjvm.so
    Current Java thread: at java.lang.Throwable.fillInStackTrace(Native Method) at
    java.lang.Throwable.<init>(Throwable.java:78) at java.lang.Error.<init>(Error.java:37)
    at java.lang.LinkageError.<init>(LinkageError.java:29) at java.lang.IncompatibleClassChangeError.<init>(IncompatibleClassChangeError.java:29)
    at java.lang.AbstractMethodError.<init>(AbstractMethodError.java:30)
    Environment : Weblogic 6.0 Sp2 on Linux Red hat 7.1
    jdk 1.31
    TIA
    Ashwani

    Hi,
    1)Could you please try logging into sqlplus using using the below command :-
        sqlplus "/ as sysdba"
    2)Execute the below command to check if the password in expired :-
      select username, account_status, expiry_date, where username='MDS username';
    3)Change the password if the password has been expired by following the below command :-
       alter user <user> identified by <password>;
    4)Once the above steps are followed please login into the Weblogic Admin Console and follow the below steps:-
        + Go to DataSources ---> Select the MDS schema ----> change the password which was given in step no.3
        + Restart the Weblogic once again.
    5)Lets us know the result.
    Regards,
    Prakash.

  • Problem in running application(using ADF) on BEA Weblogic Server

    Hi..,
    I am Gunardy Sutanto from Indonesia. Currently, I had a problem in deploying application which is using ADF framework in BEA Weblogic Server(WLS 8.1). I also add all the libraries which were required for running this application. But I found some error when I ran this application. About the error message that I found from log file which is generated by BEA Weblogic Server 8.1, herewith I attach the detail of the error message :
    <Error> <HTTP> <BEA-101020> <[ServletContext(id=27825828,name=bp_presentment,context-path
    =/bp_presentment)] Servlet failed with Exception
    oracle.jbo.PCollException: JBO-28030: Could not insert row into table PS_TXN, collection id 16,408, persistent id 1
    at oracle.jbo.PCollException.throwException(PCollException.java:39)
    at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1845)
    at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
    at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
    at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
    at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
    at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
    at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
    at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
    at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
    at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
    at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
    at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
    at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
    at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
    at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    ## Detail 0 ##
    java.lang.ClassCastException
    at oracle.jbo.pcoll.OraclePersistManager.updateBlobs(OraclePersistManager.java:1613)
    at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1832)
    at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
    at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
    at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
    at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
    at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
    at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
    at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
    at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
    at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
    at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
    at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
    at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
    at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
    at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
    at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
    at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    I hope this is enough for somebody for solving this problem. If someone have the solution for this problem, please contact me by e-mail to [email protected].
    Thanks,
    Gunardy

    I already set the value for jbo.server.internal_connection and then deployed to Weblogic Server. When I was tested the application, all the records from table had shown on the screen but I found the application can't insert row to table PS_TXN. I I want to know it always happened?
    Herewith I attach the detail log from log file which was generated by Weblogic Server:
    oracle.jbo.PCollException: JBO-28030: Could not insert row into table PS_TXN, collection id 162, persistent id 1     at oracle.jbo.PCollException.throwException(PCollException.java:39)
         at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1845)
         at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
         at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
         at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
         at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
         at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
         at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
         at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
         at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
         at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
         at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
         at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
         at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    ## Detail 0 ##
    java.lang.ClassCastException
         at oracle.jbo.pcoll.OraclePersistManager.updateBlobs(OraclePersistManager.java:1613)
         at oracle.jbo.pcoll.OraclePersistManager.insert(OraclePersistManager.java:1832)
         at oracle.jbo.pcoll.PCollNode.passivateElem(PCollNode.java:561)
         at oracle.jbo.pcoll.PCollNode.passivate(PCollNode.java:684)
         at oracle.jbo.pcoll.PCollNode.passivateBranch(PCollNode.java:643)
         at oracle.jbo.pcoll.PCollection.passivate(PCollection.java:461)
         at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:294)
         at oracle.jbo.server.DBSerializer.passivateRootAM(DBSerializer.java:277)
         at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(ApplicationModuleImpl.java:5119)
         at oracle.jbo.server.ApplicationModuleImpl.passivateState(ApplicationModuleImpl.java:5011)
         at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7741)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:3923)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(ApplicationPoolImpl.java:2161)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1261)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:717)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:634)
         at oracle.jbo.common.ws.WSApplicationModuleImpl.endRequest(WSApplicationModuleImpl.java:2672)
         at oracle.adf.model.bc4j.DCJboDataControl.endRequest(DCJboDataControl.java:1283)
         at oracle.adf.model.servlet.ADFBindingFilter.invokeEndRequest(ADFBindingFilter.java:300)
         at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:249)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    Besides that, I found new error when I was starting Weblogic Server. Herewith, I attach the detail of the error message:
    java.lang.NoClassDefFoundError: org/apache/commons/collections/FastHashMap$KeySet
         at org.apache.commons.collections.FastHashMap.keySet(Unknown Source)
         at org.apache.struts.action.ActionServlet.destroyDataSources(ActionServlet.java:769)
         at org.apache.struts.action.ActionServlet.destroy(ActionServlet.java:431)
         at weblogic.servlet.internal.ServletStubImpl$ServletDestroyAction.run(ServletStubImpl.java:1086)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:569)
         at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:596)
         at weblogic.servlet.internal.ServletStubImpl.destroyServlet(ServletStubImpl.java:581)
         at weblogic.servlet.internal.WebAppServletContext.destroyServlets(WebAppServletContext.java:5797)
         at weblogic.servlet.internal.WebAppServletContext.destroy(WebAppServletContext.java:5675)
         at weblogic.servlet.internal.ServletContextManager.removeContext(ServletContextManager.java:187)
         at weblogic.servlet.internal.HttpServer.unloadWebApp(HttpServer.java:706)
         at weblogic.servlet.internal.WebAppModule.destroyContexts(WebAppModule.java:764)
         at weblogic.servlet.internal.WebAppModule.rollback(WebAppModule.java:742)
         at weblogic.j2ee.J2EEApplicationContainer.rollbackModule(J2EEApplicationContainer.java:2942)
         at weblogic.j2ee.J2EEApplicationContainer.rectifyClassLoaders(J2EEApplicationContainer.java:1429)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1176)
         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
         at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2634)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2584)
         at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2506)
         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:833)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:542)
         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    >
    So, I need someone to sove this problem. I am looking forward for hearing from you.
    Thanks,
    Gunardy

  • **** ASSERTION FAILED **** Error while starting WebLogic Server 7.0

    Hi,
    I am getting following error while starting WebLogic Server 7.0 for the first
    time. Can anybody help me it this?
    Error is:
    ==================================================
    Enter username to boot WebLogic server:system
    Enter password to boot WebLogic server:
    Starting WebLogic Server...
    <May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
    on C:\bea\user_projects\mydomain\.\config.xml>
    <May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "myserver" for domain "m
    ydomain">
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initializatio
    n exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Fac
    tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.
    UnknownHostException: Unknown protocol: 'JNP'] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    >
    ==================================================

    I don't know what could cause this error.
    I would suggest you take this upto [email protected]
    Kumar
    Ajay Jadhav wrote:
    Hi,
    I am getting following error while starting WebLogic Server 7.0 for the first
    time. Can anybody help me it this?
    Error is:
    ==================================================
    Enter username to boot WebLogic server:system
    Enter password to boot WebLogic server:
    Starting WebLogic Server...
    <May 9, 2003 4:27:47 PM IST> <Notice> <Management> <140005> <Loading configurati
    on C:\bea\user_projects\mydomain\.\config.xml>
    <May 9, 2003 4:28:04 PM IST> <Notice> <Security> <090082> <Security initializing
    using realm myrealm.>
    <May 9, 2003 4:28:04 PM IST> <Notice> <WebLogicServer> <000327> <Starting WebLogic
    Admin Server "myserver" for domain "m
    ydomain">
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    <May 9, 2003 4:28:14 PM IST> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initializatio
    n exception
    Throwable: weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot
    intialize Resource Manager Connection Fac
    tory resources because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.
    UnknownHostException: Unknown protocol: 'JNP'] ]
    weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Cannot intialize
    Resource Manager Connection Factory resour
    ces because could not get JNDI context: javax.naming.ServiceUnavailableException
    [Root exception is java.net.UnknownHost
    Exception: Unknown protocol: 'JNP'] ]
    at weblogic.j2ee.RMCFactoryDeployer.<init>(RMCFactoryDeployer.java:50)
    at weblogic.j2ee.J2EEService.initialize(J2EEService.java:93)
    at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
    at weblogic.Server.main(Server.java:32)
    ==================================================

  • Getting error while starting weblogic server in jdeveloper

    getting an error while starting weblogic server in jdeveloper
    IN LOG(its shows following):
    <Jul 25, 2013 7:19:15 PM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode>
    <Jul 25, 2013 7:19:15 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Jul 25, 2013 7:19:15 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    User 'principals=[weblogic, Administrators]' has administration role. All tasks by adminstrators must go through an Administration Port.
    **** Authentication error while connecting to application server IntegratedWebLogicServer. Please check settings.
    **** Failed to complete start-up of application server IntegratedWebLogicServer.
    [Server Instance IntegratedWebLogicServer is shutting down.  All applications currently running will be terminated and undeployed.]
    [Forcing termination of IntegratedWebLogicServer]
    taskkill /F /PID 1620
    Process exited.
    PLs help me

    User, please tell us your jdev version!
    Somehow your credentials are corrupted. Two possible solution:
    1) open your system11.1.1.xxxx folder open the DefaultDomain\servers\DefaultServer\security folder and edit the boot.properties file. Remove the '(AES)...' part after username and password and write the new ones e.g. username=weblogic', password='Welcome1'. Save the file and try to start the integrated server again. Once the server starts the entries are encoded again.
    2) if 1) does not work, remove the whole DefaultDomain folder and create a new WLS instance inside jdev.
    Timo

  • Deployment Manager Error with Oracle Weblogic Server 10.3.1

    I have installed Identity Manager 9.1.0.2 (patch upgraded from 9.1.0.1) on OEL 5.3 64bit and Weblogic 10.3.1
    Database:Oracle 11gR2 (remote machine).
    **I am aware that IM 9.1.0.2 is not certified on Weblogic 10.3.1 (it is only certified on 10.3),
    The installation was successful and OIManager is up and running. Able to create Users, Resources etc. as well.
    As part of configuring OIM Connectors tried to Import .xml file using Import option from Deployment Management section as below and the following error was displayed.
    "Either your session timed out or you are trying to access a page without logging in".
    Did all workarounds like enabling java, changing browsers, restarting machine etc as per the below discussion but in vain.
    Deployment Manager Error with Oracle Weblogic Server
    Can any one suggest any workaround or solution for this problem.
    Or atleast can any one confirm there is no Identity manager available on this date which is compatible with 10.3.1? and cannot be continued further.
    Thanks in Advance
    Sudheer
    Edited by: SudheerPrabhala on Oct 20, 2009 1:26 AM

    You are facing this issue because you're using a non certified combination.
    Other folks who tried to use OIM in 10.3.1 ended up in the same problem you're facing.

  • Fatal error on installation Weblogic server

    I am following the instruction from -> http://www.oracle-base.com/articles/11g/GridControl11gR1InstallationOnOEL5.php#java_installation
    Step ->Middleware Installation
    Grid Control 11g Release 1 no longer bundles the middleware components, so we must install the WebLogic Server before we can proceed with the Grid Control installation. The installation is started with the following command, run as the "oracle" user.
    When I come to Choose Product Installation Directories -- clicking next gives error window "A fatal error has occured. This application will terminate".Please can
    The files unzipped for Weblogic are
    [oracle@ccoshs02xvoem01 11gr2grid]$ ls -lrt
    total 1096356
    drwxr-xr-x 3 oracle oinstall 4096 Oct 10 2006 com
    -rw-r--r-- 1 oracle oinstall 1441 Jan 11 2007 NOTICE.txt
    -rw-r--r-- 1 oracle oinstall 11358 Jan 11 2007 LICENSE.txt
    -rw-r--r-- 1 oracle oinstall 4891 Jan 11 2007 CHANGES.txt
    drwxr-xr-x 3 oracle oinstall 4096 Jan 11 2007 strings
    drwxr-xr-x 4 oracle oinstall 4096 Feb 19 2007 workshop
    drwxr-xr-x 4 oracle oinstall 4096 Feb 19 2007 images
    drwxr-xr-x 3 oracle oinstall 4096 Mar 20 2007 javax
    drwxr-xr-x 12 oracle oinstall 4096 Mar 20 2007 schemaorg_apache_xmlbeans
    drwxr-xr-x 2 oracle oinstall 4096 Mar 20 2007 repackage
    drwxr-xr-x 4 oracle oinstall 4096 Mar 20 2007 org
    -rw-r--r-- 1 oracle oinstall 4573 Jul 8 2009 stringsubs.xsd
    -rw-r--r-- 1 oracle oinstall 7102 Jul 8 2009 registry.xslt
    drwxr-xr-x 4 oracle oinstall 4096 Jun 3 2010 wcf
    -rw-r--r-- 1 oracle oinstall 1752 Dec 17 22:27 wizard.xml
    drwxr-xr-x 2 oracle oinstall 4096 Dec 17 22:27 native
    -rw-r--r-- 1 oracle oinstall 2951 Dec 17 22:27 lpr.xml
    -rw-r--r-- 1 oracle oinstall 71384 Dec 17 22:27 gpr.xml
    -rw-r--r-- 1 oracle oinstall 385707 Dec 17 22:27 com.bea.cie.gpr-xbean_3.0.1.0.jar
    -rw-r--r-- 1 oracle oinstall 462395 Dec 17 22:27 com.bea.cie.gpr-impl_3.0.1.0.jar
    drwxr-xr-x 3 oracle oinstall 4096 Dec 17 22:28 sizeinfo
    drwxr-xr-x 4 oracle oinstall 4096 Dec 17 22:28 archives
    drwxr-xr-x 6 oracle oinstall 4096 Dec 17 22:28 resources
    -rw-r--r-- 1 oracle oinstall 430344 Dec 17 22:28 installer.jar
    drwxr-xr-x 3 oracle oinstall 4096 Dec 17 22:28 META-INF
    -rw-r--r-- 1 oracle oinstall 1119969142 Jan 28 09:17 wls1034_generic.zip
    drwxr-xr-x 4 oracle oinstall 4096 Jan 28 11:22 patch
    [oracle@ccoshs02xvoem01 11gr2grid]$ java -jar installer.jar
    I have downloaded wls1034_generic zipped file from oracle
    http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html
    Oracle WebLogic Server 11gR1 (10.3.4) + Coherence -
    Package Installer --- Generic: 1 GB File1
    some one help me with Oracle Grid Control installation

    Looks like you already got your answer on the database forum? fatal error on Installating Weblogic Server to install OEM
    If so please change your post here as answered.
    Eric

  • Welcome to the BEA WebLogic Server Version 6.0 Beta Program!

    Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
    We are very excited about this beta program and appreciate your
    participation. In the past, our public betas have been very well received
    by our developer community. So, we have once again organized a public beta
    program to enable everyone to preview our latest release.
    We do ask that you follow a few guidelines:
    -- There will be no voice, e-mail, or fax support for this beta through the
    technical support organization. All questions, bug reports, or comments on
    the beta program should be directed to to the WebLogic beta newsgroups at
    news://newsgroups.bea.com. These newsgroups are:
    weblogic.developer.interest.60beta.transaction
    weblogic.support.install.60beta
    weblogic.developer.interest.60beta.ejb
    weblogic.developer.interest.60beta.clustering
    weblogic.developer.interest.60beta.security
    weblogic.developer.interest.60beta.jdbc
    weblogic.developer.interest.60beta.jms
    weblogic.developer.interest.60beta.performance
    weblogic.developer.interest.60beta.misc
    weblogic.developer.interest.60beta.servlet
    weblogic.developer.interest.60beta.jsp
    weblogic.developer.interest.60beta.tools
    weblogic.developer.interest.60beta.rmi-iiop
    weblogic.developer.interest.60beta.management
    weblogic.developer.interest.60beta.management.console
    weblogic.developer.interest.60beta.management.general_and_jmx
    weblogic.developer.interest.60beta.internationalization
    weblogic.developer.interest.60beta.xml
    weblogic.developer.interest.60beta.jndi
    weblogic.developer.interest.60beta.documentation
    weblogic.developer.interest.60beta.javamail
    -- Please remember that this release is currently beta code. This means that
    it should not be put into production deployments until the final release
    occurs.
    -- It is very likely that this release will contain bugs and errors. This is
    the nature of beta code. Please the patient with us as we do our best to fix
    any problems that we find. We will do our absolute best to make sure that
    your issues are addressed as soon as possible.
    -- Please do not post any issues relevant to the beta on the standard
    newsgroups also available at news://newsgroups.bea.com.
    -- Please use the newsgroup for all communication and do not contact any BEA
    employees directly. They have been instructed to direct you to comment only
    via the newsgroup.
    -- Please review previous posts in the newsgroups before posting. If you
    locate a bug or need to ask a question, it is very likely that it will have
    been asked before.
    -- Please do not post on the newsgroup using hostile or profane language.
    Inappropriate posts will be removed and offenders will be blocked from the
    beta program.
    Thank you again for your support and participation. We very much appreciate
    all that you will be doing to make this release of the BEA WebLogic Server
    as great as possible.
    Michael Girdley
    BEA Systems Inc

    Welcome to the BEA WebLogic Server Version 6.0 Beta Program!
    We are very excited about this beta program and appreciate your
    participation. In the past, our public betas have been very well received
    by our developer community. So, we have once again organized a public beta
    program to enable everyone to preview our latest release.
    We do ask that you follow a few guidelines:
    -- There will be no voice, e-mail, or fax support for this beta through the
    technical support organization. All questions, bug reports, or comments on
    the beta program should be directed to to the WebLogic beta newsgroups at
    news://newsgroups.bea.com. These newsgroups are:
    weblogic.developer.interest.60beta.transaction
    weblogic.support.install.60beta
    weblogic.developer.interest.60beta.ejb
    weblogic.developer.interest.60beta.clustering
    weblogic.developer.interest.60beta.security
    weblogic.developer.interest.60beta.jdbc
    weblogic.developer.interest.60beta.jms
    weblogic.developer.interest.60beta.performance
    weblogic.developer.interest.60beta.misc
    weblogic.developer.interest.60beta.servlet
    weblogic.developer.interest.60beta.jsp
    weblogic.developer.interest.60beta.tools
    weblogic.developer.interest.60beta.rmi-iiop
    weblogic.developer.interest.60beta.management
    weblogic.developer.interest.60beta.management.console
    weblogic.developer.interest.60beta.management.general_and_jmx
    weblogic.developer.interest.60beta.internationalization
    weblogic.developer.interest.60beta.xml
    weblogic.developer.interest.60beta.jndi
    weblogic.developer.interest.60beta.documentation
    weblogic.developer.interest.60beta.javamail
    -- Please remember that this release is currently beta code. This means that
    it should not be put into production deployments until the final release
    occurs.
    -- It is very likely that this release will contain bugs and errors. This is
    the nature of beta code. Please the patient with us as we do our best to fix
    any problems that we find. We will do our absolute best to make sure that
    your issues are addressed as soon as possible.
    -- Please do not post any issues relevant to the beta on the standard
    newsgroups also available at news://newsgroups.bea.com.
    -- Please use the newsgroup for all communication and do not contact any BEA
    employees directly. They have been instructed to direct you to comment only
    via the newsgroup.
    -- Please review previous posts in the newsgroups before posting. If you
    locate a bug or need to ask a question, it is very likely that it will have
    been asked before.
    -- Please do not post on the newsgroup using hostile or profane language.
    Inappropriate posts will be removed and offenders will be blocked from the
    beta program.
    Thank you again for your support and participation. We very much appreciate
    all that you will be doing to make this release of the BEA WebLogic Server
    as great as possible.
    Michael Girdley
    BEA Systems Inc

  • Integrating WebSphere MQ 5.3 with BEA Weblogic Server 9.2 3M

    I am trying to integrate WebSphere MQ 5.3 with BEA WebLogic Server 9.2 3M. I have found the guide:
    Integrating WebSphere MQ 6 with BEA Weblogic Server 10 using Weblogic Server's Foreign (JMS) Server feature [http://ibswings.blogspot.com/]. I have done all steps according this guidance.
    I have made modification since, WebLogic Server 9.2 3M does not support EJB 3.0, I am using EJB 2.1, any changes that have been made is create ejb-jar.xml file and configure it according next guide
    At the final step when I am deploying service-jar-files (for ex. ejb.jar), I am able to complete this procedure.
    When I am starting service (for ex. ejb.jar) from Deployments I am facing a wall: exception appears
    weblogic.application.ModuleException: Exception starting module: EJBModule(EJB)
    Unable to deploy EJB: EJB.jar from EJB.jar:
    com/ibm/mq/jmqi/system/JmqiComponent
    at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:505)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:18
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    java.lang.NoClassDefFoundError: com/ibm/mq/jmqi/system/JmqiComponent
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
    at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
    at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
    at com.ibm.msg.client.wmq.factories.WMQFactoryFactory.createProviderXAConnectionFactory(WMQFactoryFactory.java:388)
    at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.setProviderFactory(JmsConnectionFactoryImpl.java:170)
    at com.ibm.mq.jms.MQConnectionFactory.&lt;init&gt;(MQConnectionFactory.java:240)
    at com.ibm.mq.jms.MQQueueConnectionFactory.&lt;init&gt;(MQQueueConnectionFactory.java:76)
    at com.ibm.mq.jms.MQXAQueueConnectionFactory.&lt;init&gt;(MQXAQueueConnectionFactory.java:69)
    at com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory.getObjectInstance(MQXAQueueConnectionFactoryFactory.java:77)
    at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
    As you can see weblogic complains about com.ibm.mq.jmqi.system.JmqiComponent, I googled JmqiComponent but dose not exists which is strange :P. Has anybody what is a reason for such a behaviour.

    Hello.
    I would ditch the foreign JMS approach. There is a detailed example of how to use the resource adapter for the same goal here:
    WebSphere MQ resource adapter  and Weblogic - how?
    While Oracle supports foreign JMS, IBM won't. The only pattern that both IBM and Oracle support is resource adapter.
    Let me know, if you need more guidance.
    -Adrian

Maybe you are looking for