CRIO deployment problem error: -1967357951

Hi,
When I connect to my cRIO-9073 an error message show up that it could not find all the libaries.
When I Ignore this and continue i am unable to load my VI's on the host PC and the real-time target.
I think I have installed all the necessary software on the cRIO.
A description of the problem can be found in the attached PDF.
The labview program can be found in attachement.
Best regards,
Jasper 
Solved!
Go to Solution.
Attachments:
cRIO deployment problem.pdf ‏329 KB
cRIO deployment problem.pdf ‏329 KB
Open loop BLDC control V11_02V2.zip ‏652 KB

Hello Jasper,
I have seen this issue before in combination with a (availible) memory problem on the controller. I can see you have quite a lot installed on the cRIO controller. The cRIO-9073 is around already for a couple of years and is limited in terms of avaiable memory comparing to our newer controllers. I saw you are using LabVIEW 2013 which has a bigger footprint then the LabVIEW versions that where around when the cRIO-9073 saw the daylight. I would advise to format the controller and only install the bare minimum which your application needs to the controller and try again. That way we can check whether this issue arrizes from a memory issue or something else.
Regards,
Rik Prins, CLD
Applications Engineering Specialist Northern Europe, National Instruments
Please tip your answer providers with kudos.
Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

Similar Messages

  • JavaFX application deployment problem - Error: Unable to load resource

    I am developing my first JavaFX application. When I install the jnlp and jar files on my web server I have no problems using the application from either my development machine (Windows XP) or my test machines (Windows XP & Mac OS X). However, one person evaluating the application reports getting the following error:
    Error: Unable to load resource: http://dl.javafx.com/1.3/javafx-rt-windows-i586__V1.3.0_b412.jar
    What are the possible causes of this problem and how can they be resolved?

    If being able to redistribute the JavaFX runtime is important to you, make sure you let Oracle know. Personally I'd prefer to host it myself or bundle it with an application installer. Being forced to rely on dl.javafx.com isn't acceptable for me.
    [http://javafx.uservoice.com/forums/33584-official-javafx-feedback-forum/suggestions/403105-allow-us-to-distribute-the-javafx-runtime-binary?ref=title]
    Edited by: jptech on Jun 18, 2010 8:36 PM

  • RE: [iPlanet-JATO] Re: Deployment problem

    Chidu,
    I think that you are mired in the very common confusion of the default
    behavior of the ApplicationServletBase.parsePathInfo() which will determine
    the controlling/handling ViewBean via a URL design pattern. Lets take a look
    at the URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    is decomposed as follows:
    /NASApp -> well, this is long story but is absolutely necessary, welcome to
    iAS
    /MigtoolboxSampleAppWar -> is the web application name, taken as the name of
    the WAR file when there is no EAR file (this allows the Servlet/JSP
    container to deferences the web application root under
    <ias>/APPS/modules/MigtoolboxSampleAppWar) I think this part of the URL is
    called th Context Path
    /MigtoolboxSample -> is the Servlet Path, and will either directly reference
    or match a Servlet Mapping
    for instance
    <servlet-mapping>
    <servlet-name>MigtoolboxSampleServlet</servlet-name>
    <url-pattern>/MigtoolboxSample/*</url-pattern>
    </servlet-mapping>
    tells the Servlet Container that the Servlet Path
    /MigtoolboxSample
    maps to the Module Servlet MigtoolboxSampleServlet
    This is how EVERY request makes its way to the "front controller" pattern in
    JATO. It is fundamental to JATO Applicatioan that every request pass
    through the ModuleServlet.
    every else on the URL past the Servlet Path is the PATH INFO. Based on this
    understanding, you will see why the
    ApplicationServletBase.parsePathInfo()
    is so important. In parsePathInfo() the PATH INFO is compared to the design
    pattern
    /VIEWBEANNAME*
    to determine the handling ViewBean from the first String Token in the path
    info. For instance, the starting URL of the Sample Application is
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage
    The PATH INFO is [IndexPage]
    and IndexPage[ViewBean] is the handling ViewBean. Therefore, any simiarl
    URL like
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.matt
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.mike
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.chidu
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.XXX
    will all result in the same handling View Bean
    IndexPageViewBean
    It is very important to understand that you CANNOT hit the JATO JSPs
    directly. You must hit the "front controller" ModuleServlet which will
    always delegate control to the handling ViewBean (a la, the "service to
    workers" pattern)
    You can attempt to hit the JSP directly but you need the right J2EE URL
    /NASApp/MigtoolboxSampleAppWar/MigtoolboxSampleApp/MigtoolboxSample/IndexPag
    e.jsp
    this URL will directly hit the JSP. However, you will recieve an error
    because the JATO framework quickly determines that there is no
    RequestContext in the HttpRequest attributes and assumes that the "front
    controller" was bypassed. Try it. You will get ERROR.
    Lets go back to what you are trying to do, place Models and Viewbeans in
    separate directories. I recommend that you move the Models. Models are
    ONLY referenced by TYPE via the ModelManager, the compiler will ensure that
    your code is correct and matches the packages, file locations, import
    statements, etc. ViewBeans, on the other hand are related to the
    ModuleServlet their are contained in and are loaded via type names according
    to a design pattern.
    if you want to separate models and Viewbean then simply move the Model and
    make sure everything compiles.
    you cannot move the ViewBeans
    if you do want to move the JSP peers of the Viewbeans, then you can put them
    anywhere in the web application doc root. When you do, update the
    DEFAULT_DISPLAY_URL as Mike suggested
    matt
    -----Original Message-----
    From: Mike Frisino [mailto:<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217193234150166091061">Michael.Frisino@S...</a>]
    Sent: Thursday, July 26, 2001 10:48 PM
    Subject: Re: [iPlanet-JATO] Re: Deployment problem
    Chidu,
    Did you have it running fine in the original default configuration, before
    you started changing things around? The URL should not access the .jsp
    directly. The URL should look more like this
    "/NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage", without the
    .jsp.
    Also, please read the "Migration Tech Notes" document that is
    linked to the
    main doc index page. There is some information in there related
    to trying to
    run the sample application under iAS (see Tech Note 4 in
    particular, "Note
    on running the iMT "MigtoolboxSample" in iPlanet Application Server )
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164140244063078048234051197">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 7:27 PM
    Subject: [iPlanet-JATO] Re: Deployment problem
    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166136158139046209">iPlanet-JATO@y...</a>, "Mike Frisino" <<a href="/group/SunONE-JATO/post?protectID=174176219122158198138082063148231088239026066196217130152150">Michael.Frisino@S...</a>> wrote:
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message thatyou recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <<a href="/group/SunONE-JATO/post?protectID=219015020150194233215218164036129208">chidusv@y...</a>>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look forthe
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>
    <a href="/group/SunONE-JATO/post?protectID=210083235237078198050118178206047166215146166214017110250006230056039126077176105140127082088124241215002153">[email protected]</a>

    Hi Mike,
    I tried changing the url in all the viewbeans to reflect the new sub-
    directory for the viewbeans(I have placed the jsps and viewbeans in
    a sub-directory under MigtoolboxSampleApp/MigtoolboxSample). But I'm
    still not able to get access to the jsps. I basically see the
    message "GX Error Socket Error Code missing!!" error on the browser
    thrown by iPlanet, but the log doesn't tell me anything. Does the url
    which I give to access the jsp change accordingly, i.e., should I
    give something other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp.
    If I try to use any other url other
    than /NASApp/MigtoolboxSampleAppWar/MigtoolboxSample/IndexPage.jsp, I
    see the FileNotFoundException in the log.
    I guess I'm still missing something.
    Thanks for your help.
    --Chidu.
    --- In iPlanet-JATO@y..., "Mike Frisino" <Michael.Frisino@S...> wrote:
    >
    Chidu.
    Did you also adjust the following member in each of the ViewBeans?
    public static final String DEFAULT_DISPLAY_URL=
    "/jatosample/module1/Index.jsp";
    Try adjusting this to be consistent with your new hierarchy.
    Also, if you still have problems, send us the error message that you recieve
    when you try to access the page. That would help.
    ----- Original Message -----
    From: <chidusv@y...>
    Sent: Thursday, July 26, 2001 4:48 PM
    Subject: [iPlanet-JATO] Deployment problem
    Hi,
    We have a requirement to seperate the models and viewbeans and
    keep
    them in seperate directories. Is it possible to seperate the
    viewbeans and models not be in the same directory?
    I tried seperating the two in the MigtoolboxSampleApp application
    provided by JATO. I changed the package and import statements
    accordingly in the viewbeans, jsps and the models. But when I
    deployed the application, I'm not able to access the Index page or
    any of the jsps. Does the ApplicationServletBase always look for the
    viewbean in the same path as that of the module servlet?
    Any help will be appreciated.
    Thanks,
    Chidu.
    [email protected]

  • Deployment Problems of Enterprise Application in NWDS 7.1

    Hello Everyone,<br>
    <br>
    I am having a problem when trying to deploy an application I made to the server. The project consists of two DCs, one which is an Enterprise Application and the other is a Web Module. I have configured the web module to be a dependency of the Enterprise application, so that the .war file generated from the Web Module DC is contained within the .ear file created when the Enterprise Application DC is built. The only dependency that the Web Module DC has is "engine.jee5.facade," which is there by default when it is created. I have not added any code to either DC, because I was just trying to test if I could deploy something to the server before I got into that. When I build the Enterprise Application DC, both DCs build successfully (because of the dependency). When I deploy the Enterprise Application DC, I get an "[ERROR CODE DPL.DC.5089]" error message. When I checked the SDN for what that error code means, I get sent to <a href="http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58">http://wiki.sdn.sap.com/wiki/display/JSTSG/(JSTSG)(Deploy)Problems-P58</a>, which is pretty vague.
    I did try to see if I could deploy the .ear by itself, without the war file within it (by removing the dependency on the Enterprise Application DC) and that seemed to work ok. Its just seems to be when the Web Module is a dependency of the Enterprise Application is when it fails. I have included the error message I get from NWDS below. Thanks in advance for any help you can offer.                                                                                <br>                                                                                <br>                                                                                SUMMARY<br>                
    ~~~~~~~~~~~~~~~~~~~<br>
    Successfully deployed:           0<br>
    Deployed with warnings:           0<br>
    Failed deployments:                1<br>
    ~~~~~~~~~~~~~~~~~~~<br>
    ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it. <br>
    <br>
    1. File:C:\Develop\workspace.jdi\2\DCs\sap.com\test\sgj_ent_app_test_three\_comp\gen\default\deploy\sap.comtestsgj_ent_app_test_three.ear<br>
         Name:test~sgj_ent_app_test_three<br>
         Vendor:sap.com<br>
         Location:PDI_J2EETST1_D<br>
         Version:20100716152020<br>
         Deploy status:Aborted<br>
         Version:HIGHER<br>
    <br>
         Description:<br>
              1. [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.<br>
    <br>
    Exception:<br>
    com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
    Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:715)
         at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:226)
         at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:112)
         at com.sap.ide.eclipse.j2ee.engine.deploy.view.deploy.action.DeployAction$DeployActionJob.run(DeployAction.java:222)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [sap.com_test~sgj_ent_app_test_three].
    ; nested exception is:
         com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3297] An error occurred during deployment of [sdu id: [sap.com_test~sgj_ent_app_test_three]
    sdu file path: [/usr/sap/DM1/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/192/sap.comtestsgj_ent_app_test_three.ear]
    version status: [HIGHER]
    deployment status: [Admitted]
    description: []
    ]. Cannot update it.
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:81)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         ... 8 more
    Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:426)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         ... 11 more
    Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5089] Exception during generating components of [sap.com/test~sgj_ent_app_test_three] application in [servlet_jsp] container.
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:496)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         ... 12 more
    Caused by: java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException:
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:73)
         at com.sap.engine.services.security.restriction.Restrictions.checkPermission(Restrictions.java:54)
         at com.sap.engine.services.security.server.AuthenticationContextImpl.setProperty(AuthenticationContextImpl.java:533)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.initSecurityConfiguration(SecurityUtils.java:722)
         at com.sap.engine.services.servlets_jsp.server.deploy.util.SecurityUtils.createSecurityResources(SecurityUtils.java:143)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.initXmls(DeployAction.java:778)
         at com.sap.engine.services.servlets_jsp.server.deploy.DeployAction.deploy(DeployAction.java:301)
         at com.sap.engine.services.servlets_jsp.server.deploy.UpdateAction.makeUpdate(UpdateAction.java:340)
         at com.sap.engine.services.servlets_jsp.server.deploy.WebContainer.makeUpdate(WebContainer.java:341)
         at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.makeUpdate(ContainerWrapper.java:279)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:490)
         at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
         at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:197)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:525)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:424)
         at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.update(ApplicationDeployer.java:67)
         at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:110)
         at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
         at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
         at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    Edited by: Savin on Aug 5, 2010 10:25 PM
    Edited by: Savin on Aug 5, 2010 10:26 PM
    Edited by: Savin on Aug 5, 2010 10:31 PM
    Edited by: Savin on Aug 5, 2010 5:27 PM
    Edited by: Savin on Aug 5, 2010 5:38 PM
    Edited by: Savin on Aug 5, 2010 5:44 PM

    Hi Veera/Abhi
    I have installed MinDB and all the required files on the PDA. It is synchronizing with the middleware.
    On my NWDS PDA  Simulator , the application is appearing but when i click on the application there is no data and it is giving exception
    2009-02-11 13:02:40 ...  (com.sap.tc.mobile.cfs.pers.PersistenceManager:release resultset) Thread: Finalizer Error: java.sql.SQLException: Result set is closed
    Madhu--
    Please find my ans to the following points mentioned by you
    1) BASIS SWCV must be assigned in the Distribution Model Software Component Version tab of the device.
    It is assigned
    2) Activate the "DISTRIBUTE_USER_DETAILS" Rule in the admin.
    Rule is activated
    3) Activate the "DISTRIBUTE_USER_AUTHORIZATIONS" Rule in the admin.
    Rule is activated
    4) Make sure that you have installed the following components in the following sequence in the PDA
    - Creme
    - MinDB/DB2e
    - PDA_eswt_container
    - PDA Runtime.
    Client is  installed in this sequence only. I referrred to help.sap.com while installing
    the application should atleast work in the NWDS PDA simulator. My basic problem is it is not picking  up the data. giving the above mentioned error.
    Regards
    Priya

  • 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.

  • Message Driven Bean deployment problem in SAILFIN b12

    Hi,
    I am a fresh learner in EJB technology and have been experiencing a deployment problem while attempting to deploy a very simple message driven bean, that does nothing basically, to a SAILFIN (b12) application server instance. I am using NetBeans 5.5.1 to form the message driven bean but I deploy the bean manually on a Linux terminal. The following is the code of the bean:
    package trial.mdb;
    import javax.annotation.Resource;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    @MessageDriven(mappedName = "jms/MDB1", activationConfig = {
    @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    public class MDB1 implements MessageListener {
    /** Creates a new instance of MDB1 */
    public MDB1() {
    public void onMessage(Message message) {
    I got the following message after deployment attempt:
    "Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [TrialMDB]. Please refer to the server log for more details."
    The verifier does not give any error, warning or failure message and it states "com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;" in the server log. Below, I have stated the content of the server log. I am novice in EJB technology particularly in message driven beans so any help will be appreciated. Thanks a lot in advance.
    --faydemir
    The content of the server log:
    [#|2008-01-02T16:25:11.106+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|Verifying: [ _home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ]|#]
    [#|2008-01-02T16:25:11.286+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;_RequestID=c8eac819-597f-454b-b189-1ad5a88770ac;|
    STATIC VERIFICATION RESULTS
    NUMBER OF FAILURES/WARNINGS/ERRORS
    # of Failures : 0
    # of Warnings : 0
    # of Errors : 0
    END OF STATIC VERIFICATION RESULTS
    |#]
    [#|2008-01-02T16:25:11.286+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.avk.tools.verifier|_ThreadID=23;_ThreadName=Thread-41;|No errors found in the archive.|#]
    [#|2008-01-02T16:25:11.367+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=23;_ThreadName=Thread-41;|deployed with moduleid = TrialMDB|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;MDB1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|MDB00017: [MDB1]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.441+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1]|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|appId=TrialMDB moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_TrialMDB ejbName=MDB1|#]
    [#|2008-01-02T16:25:11.443+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : jms/MDB1
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
    at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
    at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
    at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
    at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
    at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
    at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
    at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
    at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
    at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
    at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
    at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
    at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
    at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
    at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
    at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
    at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
    at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
    at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
    at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
    at $Proxy1.invoke(Unknown Source)
    at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
    at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
    at com.sun.enterprise.deployment.client.DeploymentClientUtils.startApplication(DeploymentClientUtils.java:154)
    at com.sun.enterprise.deployment.client.DeployAction.run(DeployAction.java:535)
    at java.lang.Thread.run(Thread.java:619)
    |#]
    [#|2008-01-02T16:25:11.445+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=24;_ThreadName=Thread-40;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-02T16:25:11.446+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=24;_ThreadName=Thread-40;Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ;_RequestID=59330d0c-6ffd-48d6-9c99-a25e98b13700;|ADM1075:Error on listening event:[Error while loading EJB module [TrialMDB]. Please refer to the server log for more details. ]|#]

    Hi thank you for your answer. I did not create any jms resource in the application server because my message driven bean was not implementing the MessageListener interface. Since it did not work in that way, I added the MessageListenerInterface to the bean and formed the necessary jms resources usuing the admin console of the SAILFIN but it keeps giving the same message both on the linux terminal and the server log.
    Let me explain my situation in a more detailed way. I am developing a JCA based resource adapter (i.e.) connector. The inbound module of the connector listens on a specific port for incoming messages from a server (EIS). The port property is defined in the connector's deployment descriptor. When a message reaches, the connector delivers it to the a message driven bean whose code is indicated in the following:
    package com....;
    import com....ra.facade.InboundListener;
    import javax.ejb.ActivationConfigProperty;
    import javax.ejb.MessageDriven;
    import javax.jms.Message;
    import javax.jms.MessageListener;
    import java.util.logging.*;
    * Entity class InboundMessageReceiverMDB
    * @author efikayd
    @MessageDriven(
    mappedName = "InboundMessageReceiverMDB",
    messageListenerInterface = com......ra.facade.InboundListener.class,
    activationConfig = {
    @ActivationConfigProperty(
    propertyName = "listenerPort", propertyValue = "12345"),
    @ActivationConfigProperty(
    propertyName="ConnectionFactoryJndiName", propertyValue="RAjms/MyQCF"),
    @ActivationConfigProperty(
    propertyName="DestinationName", propertyValue="MyQueue"),
    @ActivationConfigProperty(
    propertyName="DestinationType", propertyValue="javax.jms.Queue")
    public class InboundMessageReceiverMDB implements InboundListener, MessageListener {
    private static final Logger logger = Logger.getLogger("com.xyz.inbound.InboundMessageReceiverMDB");
    /** Creates a new instance of InboundMessageReceiverMDB */
    public InboundMessageReceiverMDB() {
    public void onMessage(Message message) {
    public void receiveMessage(String message) {
    logger.log(Level.SEVERE, "CLASS: " + getClass().getName() + "METHOD: receiveMessage() ==> Message received...: " + message);
    The listener interface is the following:
    package com...ra.facade;
    public interface InboundListener{
    public void receiveMessage(String message);
    I have set the JMS resource and the destination resource properties on the admin console in the following manner:
    ConnectionFactory:
    JNDI Name: RAjms/MyQCF
    Pool Name: RAjms/MyQCF
    Type: javax.jms.ConnectionFactory
    Status: enabled
    Property1 ==> Name: DestinationType Value: javax.jms.Queue
    Property2 ==> Name: DestinationName Value: MyQueue
    Destination (i.e. queue):
    JNDIName: MyQueue
    Physical Destination Name: MyQueue
    status: enabled
    Property1 ==> Name: DestinationType Value:javax.jms.Queue
    Property2 ==> Name: DestinationName Value:MyQueue
    Although I created the JMS resources as above I am getting the same problems.Do you think the above configuration is fine and appropriate to the activation configuration definitions in my message driven bean code? Am I missing something on this configuration? Below, I have indicated the message that I got on the linux terminal when I attempt to deploy the message driven bean and the related server log. They are same as what I posted before (i.e. JMS resource cannot be created...). Thank you very much in advance for your help.
    Kind regards,
    faydemir
    PS: The 'restart' command in the following linux terminal outcome basically makes a call to a bash script which deploys the message driven bean to the SAILFIN application server. The resource adapter instance is already deployed on the application server before attempting to deploy the message driven bean.
    WHILE DEPLOYING:
    ws2089 [11:29am] [home/efikayd/bin] -> ./restart
    Command deploy executed successfully with following warning messages: Error occurred during application loading phase. The application will not run properly. Please fix your application and redeploy.
    WARNING: com.sun.enterprise.deployment.backend.IASDeploymentException: Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details.
    ws2089 [11:29am] [home/efikayd/bin] ->
    SERVER LOG:
    [#|2008-01-03T11:29:00.542+0100|INFO|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Application server startup complete.|#]
    [#|2008-01-03T11:29:09.482+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar;|ADM1006:Uploading the file to:[/tmp/s1astempdomain1server-1825660455/InboundReceiverMDBModule.jar]|#]
    [#|2008-01-03T11:29:12.399+0100|INFO|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=18;_ThreadName=Thread-32;|deployed with moduleid = InboundReceiverMDBModule|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;InboundMessageReceiverMDB;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|MDB00017: [InboundMessageReceiverMDB]: Exception in creating message-driven bean container: [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.739+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb.mdb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|com.sun.enterprise.connectors.ConnectorRuntimeException
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|EJB5090: Exception in creating EJB container [com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB]|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.container.ejb|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|appId=InboundReceiverMDBModule moduleName=_home_efikayd_SAILFINB12_sailfin_domains_domain1_applications_j2ee-modules_InboundReceiverMDBModule ejbName=InboundMessageReceiverMDB|#]
    [#|2008-01-03T11:29:12.742+0100|SEVERE|sun-appserver9.1|javax.enterprise.system.core.classloading|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|LDR5004: UnExpected error occured while creating ejb container
    com.sun.enterprise.connectors.ConnectorRuntimeException: JMS resource not created : InboundMessageReceiverMDB
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.getPhysicalDestinationFromConfiguration(ActiveJmsResourceAdapter.java:1528)
         at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:1379)
         at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:170)
         at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:209)
         at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:280)
         at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:537)
         at com.sun.enterprise.server.EJBModuleLoader.doLoad(EJBModuleLoader.java:171)
         at com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:245)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:233)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:188)
         at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:420)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:1004)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:991)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:470)
         at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:182)
         at com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
         at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:230)
         at com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
         at com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
         at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:920)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:591)
         at com.sun.enterprise.deployment.phasing.PEDeploymentService.start(PEDeploymentService.java:635)
         at com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.start(ApplicationsConfigMBean.java:773)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:381)
         at com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:364)
         at com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
         at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)
         at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
         at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:90)
         at $Proxy1.invoke(Unknown Source)
         at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:304)
         at com.sun.enterprise.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:174)
         at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:69)
         at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:155)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:122)
         at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:193)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:738)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
         at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:411)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:290)
         at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:271)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:202)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:94)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:206)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:150)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:632)
         at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:577)
         at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:571)
         at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1080)
         at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:271)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:568)
         at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
         at com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
         at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
         at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)
    |#]
    [#|2008-01-03T11:29:12.745+0100|WARNING|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|CORE5020: Error while loading ejb module|#]
    [#|2008-01-03T11:29:12.747+0100|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=17;_ThreadName=httpWorkerThread-4848-1;Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ;_RequestID=feb08bff-27af-402a-9fd5-b77b8bb5f046;|ADM1075:Error on listening event:[Error while loading EJB module [InboundReceiverMDBModule]. Please refer to the server log for more details. ]|#]

  • MDB Deployment Problem in JBoss 4.0.3SP1

    Hi All,
    I am upgrading my App Server from JBoss 323 to JBoss 403.
    I had some MDBs, that are running successfully in JBoss 323.
    But when I tried to redeploy them(after recompiling with jdk1.5), I am facing few issues with them.
    First of all, I have a MDB whose destination was in some other Jboss server instance. That means I am trying to connect my destination "Queue" as remotely. At that time it is thorowing exception like as follows at my server startup time.......
    2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter:                     java:/Server1JMSProvider
    2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter:                     org.jboss.jms.jndi.JNDIProviderAdapter@20dcb7
    2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
    2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory:                     org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
    2006-04-17 07:17:15,191 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection:                     Connection@10751758[token=ConnectionToken:null/b3e21fe26fd3b44f4a0c5bb69995e669                     rcvstate=STOPPED]
    2006-04-17 07:17:15,472 DEBUG [org.jboss.mq.referenceable.SpyDestinationObjectFactory]                     SpyDestinationObjectFactory->getObjectInstance()
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: QUEUE.DLQ
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@106989e
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: [u]xxxQueue[/u]
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for LifecycleMDB
    2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory:                                         org.jboss.mq.SpyXAConnectionFactory@1ebe8ec
    2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/null
    2006-04-17 07:17:15,488 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created XAQueueConnection:                                         Connection@13605872[token=ConnectionToken:null/ea8d256e12a297e358803b37d7bfee4d                               rcvstate=STOPPED]
    2006-04-17 07:17:15,488 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
    2006-04-17 07:17:15,488 WARN  [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not find the queue                                         destination-jndi-name=queue/[u]xxxQueue[/u]
    2006-04-17 07:17:15,488 WARN  [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destination not found: queue/[u]xxxQueue[/u]                               reason: javax.naming.NameNotFoundException: [u]xxxQueue[/u] not bound
    2006-04-17 07:17:15,488 WARN  [org.jboss.ejb.plugins.jms.JMSContainerInvoker] creating a new temporary destination:                               queue/[u]xxxQueue[/u]
    2006-04-17 07:17:15,488 DEBUG [org.jboss.mq.server.jmx.DestinationManager] Attempting to create destination:                                    jboss.mq.destination:service=Queue,name=xxxQueue; type=org.jboss.mq.server.jmx.Queue
    2006-04-17 07:17:15,488 INFO  [org.jboss.mq.server.jmx.Queue.xxxQueue] Registration is not done -> stop
    2006-04-17 07:17:15,488 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected:
    org.jboss.deployment.DeploymentException: Error during queue setup; - nested throwable: (javax.management.MBeanException)
         at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:39)My jboss.xml was
    <jboss>
       <enterprise-beans>
          <message-driven>
             <ejb-name>LifecycleMDB</ejb-name>
             <destination-jndi-name>queue/xxxQueue</destination-jndi-name>
             <invoker-bindings>
               <invoker>
                 <invoker-proxy-binding-name>server1-message-driven-bean</invoker-proxy-binding-name>
               </invoker>
             </invoker-bindings>
             <resource-ref>
                <res-ref-name>jms/QueueFactory</res-ref-name>
                <jndi-name>UIL2XAConnectionFactory</jndi-name>
             </resource-ref>
          </message-driven>
       </enterprise-beans>
       <invoker-proxy-bindings>
           <invoker-proxy-binding>
             <name>server1-message-driven-bean</name>
             <invoker-mbean>default</invoker-mbean>
             <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
             <proxy-factory-config>
             <JMSProviderAdapterJNDI>Server1JMSProvider</JMSProviderAdapterJNDI>
             <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
             <CreateJBossMQDestination>true</CreateJBossMQDestination>
                <MaximumSize>15</MaximumSize>
                <MaxMessages>1</MaxMessages>
                <MDBConfig>
                   <ReconnectIntervalSec>10</ReconnectIntervalSec>
                   <DLQConfig>
                      <DestinationQueue>queue/DLQ</DestinationQueue>
                      <MaxTimesRedelivered>10</MaxTimesRedelivered>
                      <TimeToLive>0</TimeToLive>
                   </DLQConfig>
                </MDBConfig>
             </proxy-factory-config>
          </invoker-proxy-binding>
      </invoker-proxy-bindings>
    </jboss>and my deployment file consist of the following code
    <server>
    <!-- The JMS provider loader -->
      <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
          name="jboss.mq:service=JMSProviderLoader,name=Server1MQProvider">
        <attribute name="ProviderName">Server1JMSProvider</attribute>
        <attribute name="ProviderAdapterClass">
          org.jboss.jms.jndi.JNDIProviderAdapter
        </attribute>
        <!-- The combined connection factory -->
        <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
        <!-- The queue connection factory -->
        <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
        <!-- The topic factory -->
        <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
        <!-- Uncomment to use HAJNDI to access JMS-->
        <attribute name="Properties">
           java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
           java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
           java.naming.provider.url=jnp://SERVER:1499
        </attribute>
      </mbean> 
    </server>

    Did you find a solution to this problem?

  • Terracotta: application deploy problem (WLP 9.2)

    hi,
    when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
    has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
    regards,
    erik
    log snippet:
    ####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
    Unable to deploy EJB: netuix.jar from netuix.jar:
    There are 1 nested errors:
    java.io.IOException: Compiler failed executable.exec:
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
    public final class ProducerPersistenceManager_7vyoe8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
    public final class BookDefinitionManager_1xzrxc_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
    public final class PortletCategoryManager_uhkdka_Impl
    [MORE CLASSES HERE]
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
    public final class PortalDefinitionManager_d875a8_Impl
    ^
    D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
    public final class PageDefinitionManager_c4el9c_Impl
    ^
    Note: Some input files use or override a deprecated API.
    Note: Recompile with -Xlint:deprecation for details.
    Note: Some input files use unchecked or unsafe operations.
    Note: Recompile with -Xlint:unchecked for details.
    25 errors
         at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
         at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
         at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
         at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
         at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
         at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
         at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
         at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
         at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
         at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
         at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
         at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
         at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
         at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
         at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
         at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
         at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

  • Deployment problem to the managed server in 11.1.1.1..

    Our deployment problem still continue. We can deploy at last one application to the admin server.
    We can see ADF domain ans jsf libs in deployment list
    But for managed server following error occurs.
    Even we tried small new application.
    But error is the same.
    An error occurred during activation of changes, please see the log for details.
    weblogic.management.DeploymentException:
    oracle.mds.lcm.weblogic.WLLifecycleListener
    Failure occurred in the execution of deployment request with ID '1247067738026' for task '16'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: oracle.jsp.next, Specification-Version: 11.1.1, Implementation-Version: 11.1.1 for Application Application1_application1
    Jul 8, 2009 6:45:10 PM EEST J2EE Info BEA-160170 Imported library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.1.0 for Application Application1_application1

    last error we take is (we are not even use MDS customisation)
    Failure occurred in the execution of deployment request with ID '1247124709107' for task '2'. Error is: 'weblogic.management.DeploymentException: ' weblogic.management.DeploymentException: at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:171) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) java.lang.ClassNotFoundException: oracle.mds.lcm.weblogic.WLLifecycleListener at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:135) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:99) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117) at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:103) at weblogic.application.internal.flow.HeadLifecycleFlow.createListeners(HeadLifecycleFlow.java:172) at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:277) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:609) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:185) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:53) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

  • BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction, so I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now I receive the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
    start() failed on resource 'OracleDB' Unexpected error during start for XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

    Hi Klaus,
    if you want to implement a global transaction over two different JDBC Resource Managers
    (update on both + 2PC) they have to be both XA compliant.
    Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
    for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
    and configuring a TXDataSource with "enable two-phase commit" = true (but only one
    non-XA JDBC driver at a time can participate in a distributed transaction).
    Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
    transactions or distributed transactions without XA drivers as well (using a single
    resource manager).
    But if you want to update multiple resource managers in the same transaction using
    EJBs, this is a "global" transaction, and WL server fully supports it.
    But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
    Sergi
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    >
    Hi Sergi, hello world,
    thanks a lot for this message. So the conclusion is that I hava no chance
    at all
    to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
    a prerequisite
    for EJB are XA-transactions.
    Is this conclusion correct.
    Many thanks again
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    distributed transaction (XA) features require version
    Oracle8i release 8.1.6 or later of the Oracle server.
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hi Sergi,
    1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
    2.) I didn´t use a special driver but that that was delivered with thewls
    server
    in the package "weblogic.jar".
    Could I enable you helping me with this information?
    Best wishes
    Klaus
    "Sergi Vaz" <[email protected]> wrote:
    Hi Klaus,
    which
    1) Oracle server version (I don't think it's a 8.3.2.)
    2) Oracle JDBC driver version
    are you you using ?
    Sergi
    "Klaus Dirlewanger" <[email protected]> wrote:
    Hello anybody,
    learnt XA being necessary if more than one sql command in transaction,so
    I changed
    my entries to the following:
    <JDBCConnectionPool
    DriverName="oracle.jdbc.xa.client.OracleXADataSource"
    Name="OracleDB"
    Password="{3DES}iKOCmvzSc6g="
    Properties="user=osv"
    Targets="osvServer"
    TestConnectionsOnReserve="false"
    URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
    <JDBCTxDataSource
    JNDIName="JNDINameOracleOSV-DB"
    Name="OracleDataSource"
    PoolName="OracleDB"
    Targets="osvServer"/>
    We set up on a database ORACLE 8.3.2.
    Now, with the non-XA-driver there was no deployment problem, but now
    I
    receive
    the
    following error message on the server output:
    Unable to deploy EJB: CourseDateEJB from osv.jar:
    The Container-Managed Persistence Entity EJB failed while creating itsSQL
    Type Map.
    The error was:
    XA error: XAER_RMERR : A resource manager error has occured in the transaction
    branch
    start() failed on resource 'OracleDB' Unexpected error during start
    for
    XAResource
    'OracleDB': null
         at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
         at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
         at weblogic.j2ee.Application.deploy(Application.java:247)
         at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
         at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
         at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
         at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
         at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
         at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
         at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Many thanks if s.b. could help me.
    Klaus

  • J2ee Deployment problem

    Hi All,
    I created a simple j2ee appl .
    I deployed that ......
    It shows some error like this
    12:12:42 PM /userOut/deploy (com.tssap.j2ee.ui.core.deploy.DeployThreadManager) [Deploy Thread] ERROR:
    Finished deployment of file:C:/Documents and Settings/Nageswar_Mandapati/Documents/SAP/workspace/myEarProject/myEarProject.ear
    Deploy exception : Server epl did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server epl at port 50018: Connection refused: connect
    Inner exception was : Server epl did not accept login request as admin on port 50018. Details: ERROR: Could not establish connection to server epl at port 50018: Connection refused: connect
    Deploy with SDM
    ==> Host is : epl
    ==> Port is : 50018
    Pls help me...
    SDM node not started and it is only red color.
    regards
    BHI

    I assume you are working on Windows. If not use the appropriate UNIX commands to stop and start SAP (stopsap j2ee; startsap).
    On Windows go to your management console and stop the Instance 00. Restart the instance again. After startup look in the process list to make sure SDM is running correctly and the node should be green. If not take a look at your startup logs to identify the problem.

  • Deployment failed error - need of five star - please answer this

    Dear All ,
    One of 100 error iam facing daily on LV 8.0
    I have made my project in my laptop and started the application  it work fine in laptop .
    but same .lvlib file i have transfered to server (only modification i did is in the shared variable) iam receiveing deployment failed error .
    Please find the attachment and give some hint to solve this problem.
    Attachments:
    deployment error.jpg ‏74 KB

    ramji,
    I think the following kb How Do I Deploy Network Shared Variables From a Compiled Executable? may provide some help. When building your executable, make sure you include your lvlib that contains yoru shared variable in the "support files" section of the application builder. Also, try including your lvlib in the data directory instead of the actually exe itself. Let us know. thanks!
    Chris c
    Chris Cilino
    National Instruments
    LabVIEW Product Marketing Manager
    Certified LabVIEW Architect

  • JDeveloper11g deployment problem

    Dear All....
    I am new to JDeveloper 11g. I created an ADF application, and run it. i got this error.
    :\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.88\DefaultDomain\bin\startWebLogic.cmd
    [waiting for the server to complete its initialization...]
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;D:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;D:\Oracle\MIDDLE~1\JDK160~1\lib\tools.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic_sp.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.jar;D:\Oracle\MIDDLE~1\modules\features\weblogic.server.modules_10.3.0.0.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\webservices.jar;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.5/lib/ant-all.jar;D:\Oracle\MIDDLE~1\modules\NETSFA~1.0_1/lib/ant-contrib.jar;D:\Oracle\Middleware\jdeveloper\modules\features\adf.share_11.1.1.jar;;D:\Oracle\MIDDLE~1\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\xqrl.jar;;
    PATH=D:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\native;D:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\native;D:\Oracle\MIDDLE~1\patch_cie660\profiles\default\native;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\bin;D:\Oracle\MIDDLE~1\modules\ORGAPA~1.5\bin;D:\Oracle\MIDDLE~1\JDK160~1\jre\bin;D:\Oracle\MIDDLE~1\JDK160~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;D:\SQLCLNT;D:\Oracle\MIDDLE~1\WLSERV~1.3\server\native\win\32\oci920_8
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    java version "1.6.0_05"
    Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
    Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode)
    Starting WLS with line:
    D:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Djbo.34010=false -Xverify:none -da -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracle\MIDDLE~1\JDEVEL~1\system\SYSTEM~1.88\DEFAUL~1 -Doracle.home=D:\Oracle\Middleware\jdeveloper -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\JDEVEL~1\system\SYSTEM~1.88\DEFAUL~1\config\oracle\jps-config.xml -Doracle.dms.context=OFF -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1030\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_jdev1111\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_cie660\profiles\default\sysext_manifest_classpath -Dweblogic.Name=DefaultServer -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy weblogic.Server
    <Mar 4, 2009 10:53:54 AM IST> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
    D:\Oracle\Middleware\patch_wls1030\profiles\default\sysext_manifest_classpath\weblogic_ext_patch.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ja.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\beehive_ko.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_CN.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\beehive_zh_TW.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ja.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_ko.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_CN.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\p13n_wls_zh_TW.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ja.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\testclient_ko.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_CN.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\testclient_zh_TW.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ja.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_ko.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_CN.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\tuxedocontrol_zh_TW.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ja.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\workshop_ko.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_CN.jar;D:\Oracle\Middleware\wlserver_10.3\L10N\workshop_zh_TW.jar>
    <Mar 4, 2009 10:53:55 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 10.0-b19 from Sun Microsystems Inc.>
    <Mar 4, 2009 10:53:55 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for CR380042 Thu Sep 11 13:33:40 PDT 2008
    WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
    WebLogic Server Temporary Patch for CR381265 Wed Oct 08 10:15:58 PDT 2008
    WebLogic Server Temporary Patch for CR380913 Wed Oct 15 13:24:22 PDT 2008
    WebLogic Server Temporary Patch for CR381739 Tue Oct 21 14:06:14 IST 2008
    WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 >
    <Mar 4, 2009 10:53:56 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Mar 4, 2009 10:53:56 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Mar 4, 2009 10:53:56 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.88\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.>
    <Mar 4, 2009 10:53:59 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 4, 2009 10:54:01 AM IST> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddi was not deployed. Error: [Deployer:149158]No application files exist at 'D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.>
    <Mar 4, 2009 10:54:01 AM IST> <Warning> <Deployer> <BEA-149617> <Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158]No application files exist at 'D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.>
    <Mar 4, 2009 10:54:02 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Mar 4, 2009 10:54:02 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Mar 4, 2009 10:54:03 AM IST> <Warning> <Server> <BEA-002611> <Hostname "T3-2.bs-cochin.com", maps to multiple IP addresses: 10.201.1.37, 127.0.0.1>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.201.1.37:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "DefaultServer" for domain "mydomain" running in Development Mode>
    <Mar 4, 2009 10:54:03 AM IST> <Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 10.201.1.37, 127.0.0.1>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Mar 4, 2009 10:54:03 AM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    Can anyone help me...
    Resmi

    Hi,
    No Frank. This problem making me also in trouble...at first time i hv succussfully run the application with killing all the java program in my system. But the in the second it is not sucess...
    The target link is not getting
    Plz check my log...
    WebLogic Server Temporary Patch for 7372756 Fri Sep 12 17:05:44 EDT 2008
    WebLogic Server Temporary Patch for CR381265 Wed Oct 08 10:15:58 PDT 2008
    WebLogic Server Temporary Patch for CR380913 Wed Oct 15 13:24:22 PDT 2008
    WebLogic Server Temporary Patch for CR381739 Tue Oct 21 14:06:14 IST 2008
    WebLogic Server 10.3 Mon Aug 18 22:39:18 EDT 2008 1142987 &gt;
    &lt;Mar 7, 2009 4:18:28 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to STARTING&gt;
    &lt;Mar 7, 2009 4:18:28 PM IST&gt; &lt;Info&gt; &lt;WorkManager&gt; &lt;BEA-002900&gt; &lt;Initializing self-tuning thread pool&gt;
    &lt;Mar 7, 2009 4:18:29 PM IST&gt; &lt;Notice&gt; &lt;Log Management&gt; &lt;BEA-170019&gt; &lt;The server log file C:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.88\DefaultDomain\servers\DefaultServer\logs\DefaultServer.log is opened. All server side log events will be written to this file.&gt;
    &lt;Mar 7, 2009 4:18:34 PM IST&gt; &lt;Notice&gt; &lt;Security&gt; &lt;BEA-090082&gt; &lt;Security initializing using security realm myrealm.&gt;
    &lt;Mar 7, 2009 4:18:39 PM IST&gt; &lt;Warning&gt; &lt;Deployer&gt; &lt;BEA-149617&gt; &lt;Non-critical internal application uddi was not deployed. Error: [Deployer:149158|http://forums.oracle.com/forums/]No application files exist at 'C:\ORACLE\MIDDLE~1\WLSERV~1.3\server\lib\uddi.war'.&gt;
    &lt;Mar 7, 2009 4:18:39 PM IST&gt; &lt;Warning&gt; &lt;Deployer&gt; &lt;BEA-149617&gt; &lt;Non-critical internal application uddiexplorer was not deployed. Error: [Deployer:149158|http://forums.oracle.com/forums/]No application files exist at 'C:\ORACLE\MIDDLE~1\WLSERV~1.3\server\lib\uddiexplorer.war'.&gt;
    &lt;Mar 7, 2009 4:18:42 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to STANDBY&gt;
    &lt;Mar 7, 2009 4:18:42 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to STARTING&gt;
    &lt;Mar 7, 2009 4:18:43 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application1 is not versioned.&gt;
    Mar 7, 2009 4:18:43 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:18:45 PM oracle.as.jmx.framework.PortableMBeanFactory setJMXFrameworkProviderClass
    INFO: JMX Portable Framework initialized with platform SPI "class oracle.as.jmx.framework.wls.spi.JMXFrameworkProviderImpl"
    &lt;Mar 7, 2009 4:18:59 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application19 is not versioned.&gt;
    Mar 7, 2009 4:18:59 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:04 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Application9 is not versioned.&gt;
    Mar 7, 2009 4:19:04 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:05 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application DashBoard_html is not versioned.&gt;
    Mar 7, 2009 4:19:05 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:06 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Dashboard-0403 is not versioned.&gt;
    Mar 7, 2009 4:19:06 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:27 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Login is not versioned.&gt;
    Mar 7, 2009 4:19:27 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:36 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application LoginOnly is not versioned.&gt;
    Mar 7, 2009 4:19:36 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:36 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Login_21022009 is not versioned.&gt;
    Mar 7, 2009 4:19:36 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:36 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Login_Old is not versioned.&gt;
    Mar 7, 2009 4:19:36 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:37 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application New-Dashboard is not versioned.&gt;
    Mar 7, 2009 4:19:37 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:48 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application NewLogin is not versioned.&gt;
    Mar 7, 2009 4:19:48 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:48 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application OptionallyQueryBasedOnURLParameter is not versioned.&gt;
    Mar 7, 2009 4:19:48 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:52 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ReferenceLogin is not versioned.&gt;
    Mar 7, 2009 4:19:52 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:19:52 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application Sample-Downloaded is not versioned.&gt;
    Mar 7, 2009 4:19:52 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:20:02 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:20:02 PM IST&gt; &lt;Warning&gt; &lt;J2EE&gt; &lt;BEA-160195&gt; &lt;The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application TestJith is not versioned.&gt;
    Mar 7, 2009 4:20:17 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Application1/z60kl9/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:17 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Application1/z60kl9/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:17 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Application1/z60kl9/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    ADF Library non-OC4J post-deployment (millis): 16
    &lt;Mar 7, 2009 4:20:20 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'Application9'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:20 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:20:20 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'DashBoard_html'.
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:349)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
    Truncated. see log file for complete stacktrace
    weblogic.common.ResourceException: g5psDS is already bound
    at weblogic.jdbc.common.internal.RmiDataSource.start(RmiDataSource.java:387)
    at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:136)
    at weblogic.jdbc.common.internal.DataSourceManager.createAndStartDataSource(DataSourceManager.java:97)
    at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:346)
    at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:20 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:20:22 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/4nrnrt/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:22 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/4nrnrt/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:22 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/4nrnrt/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:24 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/yiq2vs/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:24 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/yiq2vs/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:24 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Dashboard-0403/yiq2vs/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    DefaultServer startup time: 121734 ms.
    DefaultServer started.
    ADF Library non-OC4J post-deployment (millis): 16
    Mar 7, 2009 4:20:27 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Login/nvio4y/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:27 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Login/nvio4y/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:27 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/Login/nvio4y/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:28 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:20:28 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'LoginOnly'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    &lt;Mar 7, 2009 4:20:28 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'Login_21022009'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:28 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    &lt;Mar 7, 2009 4:20:28 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'Login_Old'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:28 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:20:30 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/New-Dashboard/lvaw6l/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:30 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/New-Dashboard/lvaw6l/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:30 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/New-Dashboard/lvaw6l/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    &lt;Mar 7, 2009 4:20:30 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'NewLogin'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:30 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:20:31 PM oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImpl setLifecycleContextBuilder
    WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adf.controller.faces.lifecycle.ADFPhaseListener'.
    &lt;Mar 7, 2009 4:20:32 PM IST&gt; &lt;Error&gt; &lt;Deployer&gt; &lt;BEA-149231&gt; &lt;Unable to set the activation state to true for the application 'ReferenceLogin'.
    weblogic.application.ModuleException: Context path '/login' is already in use by the module: login application: Application19
    at weblogic.servlet.internal.WebAppModule.initAndValidateContextPath(WebAppModule.java:1076)
    at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:908)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:423)
    at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:182)
    Truncated. see log file for complete stacktrace
    >
    Mar 7, 2009 4:20:32 PM oracle.adf.share.config.ADFConfigFactory cleanUpApplicationState
    INFO: Cleaning up application state
    Mar 7, 2009 4:20:36 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGraph" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/TestJith/lea4zh/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 3. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:36 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfDvtGauge" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/TestJith/lea4zh/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 7. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    Mar 7, 2009 4:20:36 PM oracle.adfinternal.view.faces.partition.FeatureUtils _addFeatures
    WARNING: A duplicate definition for the feature "AdfRichPivotTable" has been found at zip:C:/Oracle/Middleware/jdeveloper/system/system11.1.1.0.31.51.88/DefaultDomain/servers/DefaultServer/tmp/_WL_user/TestJith/lea4zh/war/WEB-INF/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. A feature with the same name was originally defined at zip:C:/Oracle/Middleware/jdeveloper/dvt/lib/dvt-faces.jar!/META-INF/adf-js-features.xml, line 11. This may indicate that multiple copies of the same jar file are present on the class path. Ignoring the new feature definition.
    &lt;Mar 7, 2009 4:20:36 PM IST&gt; &lt;Notice&gt; &lt;Log Management&gt; &lt;BEA-170027&gt; &lt;The Server has established connection with the Domain level Diagnostic Service successfully.&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to ADMIN&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to RESUMING&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Warning&gt; &lt;Server&gt; &lt;BEA-002611&gt; &lt;Hostname "Conti1", maps to multiple IP addresses: 192.168.1.12, 127.0.0.1&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;Server&gt; &lt;BEA-002613&gt; &lt;Channel "Default[1]" is now listening on 127.0.0.1:7101 for protocols iiop, t3, ldap, snmp, http.&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;Server&gt; &lt;BEA-002613&gt; &lt;Channel "Default" is now listening on 192.168.1.12:7101 for protocols iiop, t3, ldap, snmp, http.&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000331&gt; &lt;Started WebLogic Admin Server "DefaultServer" for domain "DefaultDomain" running in Development Mode&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Warning&gt; &lt;Server&gt; &lt;BEA-002611&gt; &lt;Hostname "localhost", maps to multiple IP addresses: 192.168.1.12, 127.0.0.1&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000365&gt; &lt;Server state changed to RUNNING&gt;
    &lt;Mar 7, 2009 4:20:38 PM IST&gt; &lt;Notice&gt; &lt;WebLogicServer&gt; &lt;BEA-000360&gt; &lt;Server started in RUNNING mode&gt;-----

  • Software Update Deployment - Job error (0x80072f0c) received for assignment

    I'm deploying a software update to my test clients but half of them failed with error below;
    UpdateStore.log -
    Failed to refresh sync message. Error = 0x87d00310. 
    WUAHandler.log
    OnSearchComplete - Failed to end search job. Error = 0x80072f0c. 
    Scan failed with error = 0x80072f0c. 
    Updates Deployment
    Job error (0x80072f0c) received for assignment ({0F2CA22F-BB7A-4ED8-9794-15AB24B83E09}) action
    Do you have any recommendation ?

    Since no one has replied to this post, I recommend that you contact Microsoft Support (CSS) directly, they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Deployment problems on AIX

              Hi!
              I have a connector and a demo setup to exercise it, using a Servlet and an EJB
              to access the connector. This works flawlessly under NT 4.0. When I try to deploy
              the same thing under AIX 4.3 everything seems to work smoothly, i.e. the connector
              starts and creates an initial ManagedConnection (I can see it from the logs),
              the EJB deploys without errors, and JNDI names are properly entered. But when
              I try to run the servlet I get the initial page, then when I try to send data
              to the EJB I get the following exception. Any idea what's causing this? I've never
              seen this on NT.
              javax.resource.ResourceException: Problem granting connection request to a Manag
              edConnectionFactory which does not exist in connection pool. Check your MCF's
              ha
              shcode()
              at java.lang.Exception.<init>(Exception.java:44)
              at javax.resource.ResourceException.<init>(ResourceException.java:73)
              at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
              n(ConnectionPoolManager.java:133)
              at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
              ection(ConnectionManagerImpl.java:20)
              at no.gar.connector.api.GarConnectionFactory.getConnection(Unknown Sourc
              e)
              at no.gar.distrib.DistribEJB.getCCIConnection(DistribEJB.java:265)
              at no.gar.distrib.DistribEJB.execute(DistribEJB.java:169)
              at no.gar.distrib.DistribEJBImpl.execute(DistribEJBImpl.java:110)
              at no.gar.distrib.DistribEJBEOImpl.execute(DistribEJBEOImpl.java:31)
              at no.gar.distrib.DistribEJBEOImpl_WLSkel.invoke(DistribEJBEOImpl_WLSkel
              .java:108)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:373)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:237)
              at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              andler.java:118)
              at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDis
              patcher.java:115)
              at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:
              88)
              at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:10
              8)
              at no.gar.distrib.DistribEJBEOImpl_WLStub.execute(DistribEJBEOImpl_WLStu
              b.java:309)
              at no.gar.distrib.DistribServlet.doGet(DistribServlet.java:67)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:213)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
              rvletContext.java:1265)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
              pl.java:1622)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              java.lang.NullPointerException
              at no.gar.distrib.DistribEJB.execute(DistribEJB.java:170)
              at no.gar.distrib.DistribEJBImpl.execute(DistribEJBImpl.java:110)
              at no.gar.distrib.DistribEJBEOImpl.execute(DistribEJBEOImpl.java:31)
              at no.gar.distrib.DistribEJBEOImpl_WLSkel.invoke(DistribEJBEOImpl_WLSkel
              .java:108)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:373)
              at weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:237)
              at weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              andler.java:118)
              at weblogic.rmi.internal.BasicRequestDispatcher.dispatch(BasicRequestDis
              patcher.java:115)
              at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:
              88)
              at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:10
              8)
              at no.gar.distrib.DistribEJBEOImpl_WLStub.execute(DistribEJBEOImpl_WLStu
              b.java:309)
              at no.gar.distrib.DistribServlet.doGet(DistribServlet.java:67)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
              at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
              at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
              pl.java:213)
              at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
              rvletContext.java:1265)
              at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
              pl.java:1622)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    TopLink requires reflective access to run. It is possible you need to configure your java policy file with the following permission for TopLink and the applications that use it.
    //grant permission for OracleAS TopLink to use reflection
    permission java.lang.reflect.ReflectPermission "suppressAccessChecks";

Maybe you are looking for

  • How do I sync multiple email accounts on ipad

    So I'm now, dubiously, the lucky owner of iPad mini with up to date software and iMac with latest software. It now seems apple have decided they don't want me to use more than one email account and so have stopped me being able to sync them ? Even fo

  • Itunes library won't load to ipod mini after ipod to new computer transfer

    I got a new computer and was able to transfer my ipod music into itunes; however, now my ipod has gone blank and it will not load the songs from itunes back onto the ipod. The ipod shows up on itunes, but has no songs listed. It shows that it is empt

  • Very nice and highly functional iPhone 4 case providing total protection

    Marware C.E.O. Flip-Vue Leather case for iPhone 4 The C.E.O. Flip-Vue™ for iPhone® 4 is a slim, genuine leather flip-top holster that provides the perfect balance between total protection and convenient access. The leather and suede design is unique

  • Removing hyperlink border around image/auto forward

    I made an image on a webpage into a hyperlink. However, I would like to remove the visual hyperlink border...the one that is blue before you visit it, and purple afterwards. How can I do this? And on a related note, how can I set the hyperlink to aut

  • Am I able to use one catalog in both pse 8 and 11

    I have restored PSE 11 onto my computer, but wonder if and how, I can also use this same catalogue on PSE 8, which is also installed on the same computer.  I would therefore have 2 back-ups, and in some respects I prefer PSE 8 to work on.  Having onc