Ant deploy problem

Hi, there,
I'm new to Jave Web Service application developer, I've encounter a problem when I deploy the example "C:\jwstutorial13\examples\gs" , but both "ant build" and "ant package" are successful, when run "ant deploy", I see the following message:
C:\jwstutorial13\examples\gs>ant deploy
Buildfile: build.xml
deploy:
BUILD FAILED
file:C:/jwstutorial13/examples/common/targets.xml:41: java.io.IOException: Server returned HTTP response code: 403 for URL: http://localhost:8080/admin/deploy?path=%2Fgs
pls help me, thanks!!!!

The problem is that you haven't set the build properties and path variables as described in the tutorial preface:
http://java.sun.com/webservices/docs/1.3/tutorial/doc/About.html#wp63742
See the section Building the Examples

Similar Messages

  • Is there a way of changing the jdevappunknown_ folder that Ant deploys to?

    Using Ant DeployESBSuitcase doesn't work when deploying Projects with dependencies.
    Steps to re-create error:
    Create a JDeveloper ESB Project called ‘ProjectB’ and add file adapter called ‘WriteFile’ to write a file. Deploy this project using JDeveloper.
    Create another JDeveloper ESB Project called ‘ProjectA’ and add a file adapter called ‘ReadFile’ to read a file.
    From ProjectA’s routing service add a routing rule and use ‘Browse Target Service Operation’ (Gear wheel icon) and select the deployed ProjectB_WriteFile service.
    Deploy ProjectA using JDeveloper.
    Use Ant to create a deploymentplan file for both projects by running the ExtractESBDeploymentPlan target.
    Note: As these projects are saved under their own directory structure
    C:\Workspace\Local\ProjectA and C:\Workspace\Local\ProjectB you will need to copy the ..\ProjectB\ProjectB_WriteFile.wsdl to the ProjectA folder.
    Confirm that ProjectA and ProjectB Ant build files DeployESBSuitcase properties (esbMetadataServerHost and esbMetaServerPort) point to another server other than the one you have just deployed ProjectA and ProjectB to using JDeveloper. i.e. a clean server that doesn’t know about these Projects
    Deploy ProjectB using Ant’s DeployESBSuitcase target.
    Deploy ProjectA using Ant’s DeployESBSuitcase target.
    An error is now thrown
    C:\Workspace\Local\ProjectA>ant DeployESBSuitcase
    Buildfile: build.xml
    DeployESBSuitcase:
    [echo] Deploying ESB Project ProjectA to serverx
    [deployESBSuitcase] Deployment Attempt Response :
    [deployESBSuitcase] <deploymentSummary>
    [deployESBSuitcase] <message>Entity Deployment Failed</message>
    [deployESBSuitcase] <errors>
    [deployESBSuitcase] <error code="1049" severity="5">
    [deployESBSuitcase] <description>WSDL "esb:///ESB_Projects/Local_ProjectB/ProjectB_WriteFile.wsdl" of service "DefaultSystem.ProjectB_WriteFile" is invalid or unaccessible. Following error is thrown by WSDL Parser : WSDL Parsing Failed: org.apache.slide.structure.ObjectNotFoundException: No object found at /files/ESB_Projects/Local_ProjectB</description>
    [deployESBSuitcase] <fix>Ensure that the WSDL is accessible and valid. If the problem persists, Contact Oracle Support.</fix>
    [deployESBSuitcase] </error>
    [deployESBSuitcase] </errors>
    [deployESBSuitcase] </deploymentSummary>
    [deployESBSuitcase]
    [deployESBSuitcase] Deployment Failed ...Unhandled Exception
    [deployESBSuitcase] java.lang.Exception: Deployment attempt failed, please review deployment attempt response above
    [deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:128)
    [deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:175)
    [deployESBSuitcase] at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.execute(DeployESBSuitcaseTask.java:510)
    [deployESBSuitcase] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [deployESBSuitcase] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [deployESBSuitcase] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [deployESBSuitcase] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [deployESBSuitcase] at java.lang.reflect.Method.invoke(Method.java:585)
    [deployESBSuitcase] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    [deployESBSuitcase] at org.apache.tools.ant.Task.perform(Task.java:348)
    [deployESBSuitcase] at org.apache.tools.ant.Target.execute(Target.java:357)
    [deployESBSuitcase] at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [deployESBSuitcase] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    [deployESBSuitcase] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [deployESBSuitcase] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [deployESBSuitcase] at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    [deployESBSuitcase] at org.apache.tools.ant.Main.runBuild(Main.java:758)
    [deployESBSuitcase] at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [deployESBSuitcase] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    [deployESBSuitcase] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    BUILD FAILED
    java.lang.Exception: Deployment attempt failed, please review deployment attempt response above
    at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:128)
    at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:175)
    at oracle.tip.esb.client.anttasks.DeployESBSuitcaseTask.execute(DeployESBSuitcaseTask.java:510)
    at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    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:585)
    at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
    at org.apache.tools.ant.Task.perform(Task.java:348)
    at org.apache.tools.ant.Target.execute(Target.java:357)
    at org.apache.tools.ant.Target.performTasks(Target.java:385)
    at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
    at org.apache.tools.ant.Main.runBuild(Main.java:758)
    at org.apache.tools.ant.Main.startAnt(Main.java:217)
    at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    Total time: 2 seconds
    C:\Workspace\Local\ProjectA>
    This error is thrown as ProjectB’s wsdl file cannot be found under esb:///ESB_Projects/Local_ProjectB/ProjectB_WriteFile.wsdl.
    This is due to Ant deploying ProjectB under …\ESB_Projects\jdevappunknown_ rather than …\ESB_Projects\Local_ProjectB
    When deploying ESB projects from JDeveloper they are created under the following structure: <Oracle_Home>\integration\esb\oraesb\artifacts\store\metadata\files\ESB_Projects\<JDev_Workspace>\<Project_Name>
    However when using the Ant target DeployESBSuitcase ALL projects are deployed to the same folder:
    <Oracle_Home>\integration\esb\oraesb\artifacts\store\metadata\files\ESB_Projects\jdevappunknown_
    Is there a way of changing the jdevappunknown folder used by Ant deployments?
    Edited by: user2000 on Apr 27, 2009 3:37 PM

    James,
    Following my steps above I don't get anything in the deploymentPlan for either ProjectA or ProjectB which includes a WSDL URL I can modify.
    ProjectA includes the ProjectB_WrieFile.esbsv file which contains the following line:
    <wsdlURL>esb:///ESB_Projects/Local_ProjectB/ProjectB_Write.wsdl</wsdlURL>
    Is there something I can change which will mean when I regenerate the deploymentPlan it will include the WSDL location?
    Thanks
    Alistair
    Edited by: user2000 on Apr 28, 2009 11:55 AM
    I've included Both Deployment Plans:
    ProjectA Deployment Plan
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <deploymentPlan>
    <serviceDeploymentPlan qname="DefaultSystem.ProjectA_ReadFile" status="ENABLED">
    <parent type="system" qname="DefaultSystem"/>
    <properties>
    <jcaOperation>
    <property value="Read" name="LogicalDirectory"/>
    <property value="oracle.tip.adapter.file.inbound.FileActivationSpec" name="ActivationSpec"/>
    <property value="Archive" name="LogicalArchiveDirectory"/>
    <property value="true" name="DeleteFile"/>
    <property value=".*\.txt" name="IncludeFiles"/>
    <property value="60" name="PollingFrequency"/>
    <property value="0" name="MinimumAge"/>
    <property value="true" name="OpaqueSchema"/>
    </jcaOperation>
    <jcaAddress>
    <property value="eis/FileAdapter" name="location"/>
    <property value="*.txt" name="UIincludeWildcard"/>
    </jcaAddress>
    </properties>
    </serviceDeploymentPlan>
    <serviceDeploymentPlan qname="DefaultSystem.ProjectA_ReadFile_RS" status="ENABLED">
    <parent type="system" qname="DefaultSystem"/>
    <properties>
    <serviceDefinition>
    <property value="ProjectA_ReadFile.wsdl" name="wsdlURL"/>
    </serviceDefinition>
    </properties>
    </serviceDeploymentPlan>
    <serviceDeploymentPlan qname="DefaultSystem.ProjectB_WriteFile" status="ENABLED">
    <parent type="system" qname="DefaultSystem"/>
    <properties>
    <jcaOperation>
    <property value="Write" name="LogicalDirectory"/>
    <property value="oracle.tip.adapter.file.outbound.FileInteractionSpec" name="InteractionSpec"/>
    <property value="ProjectB_%SEQ%.txt" name="FileNamingConvention"/>
    <property value="1" name="NumberMessages"/>
    <property value="true" name="OpaqueSchema"/>
    </jcaOperation>
    <jcaAddress>
    <property value="eis/FileAdapter" name="location"/>
    </jcaAddress>
    </properties>
    </serviceDeploymentPlan>
    </deploymentPlan>
    Project B Deployment Plan
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <deploymentPlan>
    <serviceDeploymentPlan qname="DefaultSystem.ProjectB_WriteFile" status="ENABLED">
    <parent type="system" qname="DefaultSystem"/>
    <properties>
    <jcaOperation>
    <property value="Write" name="LogicalDirectory"/>
    <property value="oracle.tip.adapter.file.outbound.FileInteractionSpec" name="InteractionSpec"/>
    <property value="ProjectB_%SEQ%.txt" name="FileNamingConvention"/>
    <property value="1" name="NumberMessages"/>
    <property value="true" name="OpaqueSchema"/>
    </jcaOperation>
    <jcaAddress>
    <property value="eis/FileAdapter" name="location"/>
    </jcaAddress>
    </properties>
    </serviceDeploymentPlan>
    </deploymentPlan>

  • Java EE Tutorial ant deploy

    Hi
    I have a problem when using the ant deploy command in the hello1 app in the tutorial. I get an error:
    BUILD FAILED
    E:\dev\javaeetutorial5\examples\bp-project\app-server-ant.xml:417: Property javaee.server.passwordfile not specified. Please
    specify the javaee.server.passwordfile property in 'bp-project/build.properties'.
    You will also need to ensure that the passwordfile is present and contains
    AS_ADMIN_PASSWORD.
    can any one point me in the direction for correcting this? Where do i find the password file so i can add it to the app-server-ant.xml file
    Thank you for any help.

    E:\dev\javaeetutorial5\examples\bp-project\app-server-
    ant.xml:417: Property javaee.server.passwordfile not
    specified. Please
    specify the javaee.server.passwordfile
    property in 'bp-project/build.properties'.
    You will also need to ensure that the
    passwordfile is present and contains
    AS_ADMIN_PASSWORD.
    point me in the direction for correcting this? Where
    do i find the password file so i can add it to the
    app-server-ant.xml file
    hank you for any help.Create a password file, say password.txt with the following line
    AS_ADMIN_PASSWORD=<substitue your admin password, most probably adminadmin>
    Open bp-project/build.properties and update the following line
    javaee.server.passwordfile=<absolute path to password.txt, example: c:/appserver/password.txt>
    It is preferrable to create the file password.txt under a directory which has no spaces.
    If bp-project/build.properties does not exist, copy bp-project/build.properties.sample to bp-project/build.properties and update it based on your application server installation.
    - sreeni

  • Ant mappingtool problem

    Greetings
    I have a problem using the mappingtool from ant
    with kodo 3.0.0b1.
    I realize that some ant integration problems are
    being fixed in beta2 but I hadn't seen this
    problem mentioned so I thought I'd let you know...
    Please let me know if I'm doing something wrong.
    Note that it seems to work fine when I use the
    commandline mappingtool utility.
    The ant tasks are set up as follows:
    <taskdef name="mappingtool"
    classname="kodo.jdbc.ant.MappingToolTask"
    classpathref="kodo-tool-classpath" />
    <target name="killdb" depends="deploy-runtime" description="Drop JDO specific tables" >
    <mappingtool action="drop" ignoreErrors="true">
    <fileset refid="all-jdo-files" />
    <classpath refid="runtime-path" />
    </mappingtool>
    </target>
    When I execute this target, I see the following exception:
    killdb:
    [mappingtool] java.lang.IllegalAccessError: tried to access method serp.util.ReferenceMap.removeExpired()V from class com.solarmetric.jdbc.ConnectionPoolImpl
    [mappingtool] at com.solarmetric.jdbc.ConnectionPoolImpl.getConnection(ConnectionPoolImpl.java:120)
    [mappingtool] at com.solarmetric.jdbc.PoolingDataSource.getConnection(PoolingDataSource.java:230)
    [mappingtool] at com.solarmetric.jdbc.DelegatingDataSource.getConnection(DelegatingDataSource.java:128)
    [mappingtool] at kodo.jdbc.schema.DataSourceFactory$DefaultsDataSource.getConnection(DataSourceFactory.java:235)
    [mappingtool] at kodo.jdbc.sql.DBDictionaryFactory.getDBDictionary(DBDictionaryFactory.java:169)
    [mappingtool] at kodo.jdbc.conf.JDBCConfigurationImpl.getDBDictionary(JDBCConfigurationImpl.java:489)
    [mappingtool] at kodo.jdbc.schema.DataSourceFactory.configureDataSource(DataSourceFactory.java:136)
    [mappingtool] at kodo.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:759)
    [mappingtool] at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource(JDBCConfigurationImpl.java:842)
    [mappingtool] at kodo.jdbc.conf.JDBCConfigurationImpl.getDataSource2(JDBCConfigurationImpl.java:851)
    [mappingtool] at kodo.jdbc.schema.SchemaTool.<init>(SchemaTool.java:64)
    [mappingtool] at kodo.jdbc.meta.MappingTool.newSchemaTool(MappingTool.java:186)
    [mappingtool] at kodo.jdbc.meta.MappingTool.getSchemaTool(MappingTool.java:176)
    [mappingtool] at kodo.jdbc.meta.MappingTool.run(MappingTool.java:774)
    [mappingtool] at kodo.jdbc.ant.MappingToolTask.executeOn(MappingToolTask.java:136)
    [mappingtool] at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
    [mappingtool] at org.apache.tools.ant.Task.perform(Task.java:319)
    [mappingtool] at org.apache.tools.ant.Target.execute(Target.java:309)
    [mappingtool] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [mappingtool] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [mappingtool] at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
    [mappingtool] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [mappingtool] at org.apache.tools.ant.Main.start(Main.java:196)
    [mappingtool] at org.apache.tools.ant.Main.main(Main.java:235)

    Thanks for your response, but this wasn't the problem.
    I don't have (never had) serp.jar lying around.
    serp appears to be in both kodo-jdo.jar and
    kodo-jdo-runtime.jar but no other jar files...
    Before running ant, my CLASSPATH is set to
    "nf.jar:ojdbc14.jar"
    (nf.jar contains the kodo.properties file -
    required here to pick up license key, etc)
    I printed out the CLASSPATH being used inside my
    ant target and it is as follows:
    antExtensions.jar:
    common.jar: (one of mine)
    gnu-getopt.jar:
    j2ee.jar:
    jakarta-commons-collections-2.1.jar:
    jakarta-commons-lang-1.0.1.jar:
    jakarta-commons-logging-1.0.2.jar:
    jakarta-commons-pool-1.0.1.jar:
    jakarta-oro-2.0.7.jar:
    jakarta-regexp-1.1.jar:
    jca1.0.jar:
    jdbc-hsql-1_7_0.jar:
    jdbc2_0-stdext.jar:
    jdo1_0.jar:
    jndi.jar:
    jta-spec1_0_1.jar:
    junit-3.8.1.jar:
    kodo-jdo-runtime.jar:
    kodo-jdo.jar:
    log4j-1.2.8.jar:
    nf.jar: (one of mine)
    ojdbc14.jar:
    sax.jar:
    wl-startup.jar:
    xalan.jar:
    xercesImpl.jar:
    xml-apis.jar
    Abe White wrote:
    If you still have the serp.jar that shipped with previous versions of
    Kodo in your classpath, make sure you remove it. Kodo 3 bundles the
    serp classes within the kodo jar.
    Was that the problem?

  • Ant deploy fails

    I installed configured the Java Web Services Dev Pack 1.0_01. I built installed and tested the HelloWorld Java-RPC example without any problem. Next I tried creating a new Web Service but when I try to deploy it I get the following error:
    C:\Projects\MyRPCTest\source>ant deploy
    Buildfile: build.xml
    deploy:
    BUILD FAILED
    Total time: 1 second
    C:\Projects\MyRPCTest\source\build.xml:14: java.io.IOException: Server returned
    HTTP response code: 403 for URL: http://localhost:8080/lmrp/deploy?path=%2Flmrp-jaxrpc
    Has anyone seen this error and know a solution?

    Figured it out. I changed my build.xml to point build.properties in Java Web Services directory.
    <property file="/jwsdp-1_0_01/docs/tutorial/examples/jaxrpc/common/build.properties"/>

  • OSM Ant deployment failing

    Hi All,
    I am trying to automate the OSM Ant deployment by using the default build.xml provided with the OSM. However while trying to deploy the par file I am running into some database errors it seems.
    I have attached the logs. Can some one help me diagnose the issue?
    Thanks,
    Manish Joshi

    Hi David,
    I had faced the exact same situation, when the build machine could not access the xsd urls used in development/source checked in to source control.
    We could not fix that by making the build machine see the dev urls - as in our case the build machine was the final deployment target.
    The work around we used was a bit messy - it involved using a shell script and a text based config file. The shell script would search and replace urls in the source code based on the config file, after checking out from source control. Then the suitcase gets built fine but the deployment plan would be redundant.
    Maybe you could open a SR, requesting a more rational design for BPEL compilation/attaching deployment plan - if the deployment plan could be applied as a part of compilation step itself before validatiing the schemas etc, then it would solve this problem.
    Thanks,
    Shanmu.
    http://www.prshanmu.com/articles/

  • 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

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

  • Jvmargs not being placed in jnlp file by ant deploy task

    Hi
    I have an ant deploy task as given below. I run ant to produce the jnlp file. Everything works ok, EXCEPT the jvmargs, and the enclosing platform element, are not copied into the jnlp file.
    Is this the intended behaviour?
    thanks
    graham
    -- ant task ---
    <project name="BuildInfoView" xmlns:fx="javafx:com.sun.javafx.tools.ant">
    <taskdef
         resource="com/sun/javafx/tools/ant/antlib.xml"
         uri="javafx:com.sun.javafx.tools.ant"
         classpath="/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/lib/ant-javafx.jar"/>
    <fx:deploy
    outdir="../installation/bin"
         outfile="infoview"
    width="800"
         height="500"
         embeddedWidth="100%"
         embeddedHeight="100%">
         <fx:application
              name="Infoview"
              mainClass="com.ods.infoview.Main">
         </fx:application>
         <fx:info
              title="InfoView"
              description="InfoView"
              vendor="OrangeDog">
         </fx:info>
         <fx:permissions elevated="true"/>
         <fx:platform javafx="2.2+">
         <fx:jvmarg value="-Xmx400"/>
         </fx:platform>
    <!--
    cacheCertificates="true"/>
    -->
         <fx:resources>
              <fx:fileset dir="../gradle/output/"/>
         </fx:resources>
    </fx:deploy>
    </project>

    There is a FAQ note about this
    http://java.sun.com/products/javawebstart/faq.html#72
    Bill

  • 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

  • Error while reading deployment; Deployment problem

    Hi,
    I have written an ANT script that basically deploys a .war file to a remote
    server. both the machines are UNIX based. Iam using wls8.1
    My build.xml file looks like this:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1 on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" remote="true" source="../applications/proxymon/proxy.war"
    name="
    myapp" user="system" password="g00db33r" verbose="true" adminurl="t3://153.2.255.51:8001"
    debug="t
    rue" targets="TestMon"/>
    </target>
    </project>
    But when iam running this script, iam getting this error:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -name myapp -source
    /export/home/beamon/applications/proxymon/proxy.war -targets TestMon -adminurl
    t3://153.2.255.51:8001 -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.management.ManagementRuntimeException:
    weblogic.management.ApplicationException: [J2EE:160029]I/O error while reading
    deployment - java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war.
    [wldeploy] java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:191)
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:155)
    [wldeploy] at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:467)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
    [wldeploy] at sun.reflect.GeneratedMethodAccessor480.invoke(Unknown Source)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    BUILD SUCCESSFUL
    Total time: 9 seconds
    Please give some solutions..........this is urgent for me. I really appreciate
    your time on this.
    -s

    I believe you need to go into your config.xml and add
    ClusterConstraintsEnabled="false" attribute to the Domain element.
    ie.
    <Domain ClusterConstraintsEnabled="false" ...
    Let me know if that doesn't do the trick.
    -- Rob
    steve wrote:
    Thanks Rob. I also wanted to deploy an application to a cluster that would basically
    contain 6 managed servers ....and now and as you just said, the Deployment would
    fail if any one among these 6 is down......could be please recall and let me know
    what is this parameter that i need to set so that even if there is any one/more
    servers are down, still the Deployment could be achieved succesfully.
    I really appreciate your advises on this .......thanks again.
    -steve
    Rob Woollen <[email protected]> wrote:
    Steve wrote:
    i started the server ....and everything went fine.
    Question: suppose i have a cluster of 6 managed server, then do i alsoneed to
    have all my 6 managed server up and runnning so as to have the Deploymentcompleted
    ?By default, the deployment fails if any of the targets are not running.
    I believe there is an option to force it to deploy even if some
    of
    the targets are not up, but I don't recall the option. It isn't usually
    what you want.
    Question: How can i target deploying an application to a cluster usingANT script
    as in my build.xml file. i.e i wanted to target to a cluster ratherthan to a
    single server.Just say targets="name of your cluster". If you're unsure of your
    cluster's name. Search for <Cluster> in your config.xml and you should
    find it.
    -- Rob
    Thanks aton .....steve Gurnett
    Rob Woollen <[email protected]> wrote:
    That error indicates the Server or cluster TestMon is not currently
    running.
    -- Rob
    Steve wrote:
    Hi,
    All I wanted to do is to deploy an application called "proxy.war"
    from
    a machine
    called "A" to a machine called "B".
    Iam running this ant script on machine "A".
    Now as you just suggested.... this is how my build.xml file looks
    like:
    "build.xml" 13 lines, 468 characters
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" source="../applications/ppmon/proxy.war"name="myapp"
    user="system" password="g00db3
    3r" verbose="true" adminurl="t3://153.2.255.51:8001" upload=true debug="true"
    targets="TestMon"/>
    </target>
    </project>
    This is the Exception that iam getting now:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -verbose -upload -noexit -namemyapp -source
    /export/home/beamon/applications/ppmon/proxy.war -targets TestMon
    -adminurl
    t3://153.2.255.51:8001
    -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Initiated Task: [5] [Deployer:149026]Deploy applicationmyapp on TestMon.
    [wldeploy] Task 5 failed: [Deployer:149026]Deploy application myappon TestMon.
    [wldeploy] Deployment failed on Server TestMon
    [wldeploy] dumping Exception stack
    [wldeploy] weblogic.management.ManagementException: [Management:149311]Therequest
    to deploy "myapp" to server "TestMon" will be deferred till the serverbecomes
    active.
    [wldeploy] at weblogic.management.deploy.MasterDeployer.failTaskifServerNotUp(MasterDeployer.java:838)
    [wldeploy] at weblogic.management.deploy.MasterDeployer.createTask(MasterDeployer.java:747)
    [wldeploy] at weblogic.management.deploy.DeploymentTaskRuntime.start(DeploymentTaskRuntime.java:646)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.Deployer$DeployerException:
    Deployment exit status=1
    BUILD SUCCESSFUL
    Total time: 12 seconds
    any ideas ??????Please Help !
    -steve
    Rob Woollen <[email protected]> wrote:
    I believe remote=true means that the files should be resolved on
    the
    server rather that on the local client. Basically it gives you away
    to
    pass a relative path in and have the server use that relative pathon
    its file system.
    It doesn't sounds like remote=true is what you want. If the
    client/server share a filesystem (eg a network filesystem) then you
    don't need to specify any options.
    If you want the client's copy of proxy.war uploaded to the server,then
    set upload=true
    -- Rob
    Steve wrote:
    Hi,
    I have written an ANT script that basically deploys a .war file
    to
    a remote
    server. both the machines are UNIX based. Iam using wls8.1
    My build.xml file looks like this:
    <?xml version="1.0" encoding="iso-8859-1"?>
    <project name="dev" default="all" basedir=".">
    <!-- This is configurations for deploying an application on wls8.1on win2000
    machine -->
    <target name="deploy-mailClient">
    <wldeploy action="deploy" remote="true" source="../applications/proxymon/proxy.war"
    name="
    myapp" user="system" password="g00db33r" verbose="true" adminurl="t3://153.2.255.51:8001"
    debug="t
    rue" targets="TestMon"/>
    </target>
    </project>
    But when iam running this script, iam getting this error:
    ant deploy-mailClientBuildfile: build.xml
    deploy-mailClient:
    [wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -namemyapp -source
    /export/home/beamon/applications/proxymon/proxy.war -targets TestMon-adminurl
    t3://153.2.255.51:8001 -user system -password g00db33r -deploy
    [wldeploy] DeploymentData : Delete Files:false
    [wldeploy] Timeout :3600000
    [wldeploy] Targets:
    [wldeploy] Files:
    [wldeploy] null
    [wldeploy]
    [wldeploy] Unpexpected Error Initializing Deployer: weblogic.management.ManagementRuntimeException:
    weblogic.management.ApplicationException: [J2EE:160029]I/O error
    while
    reading
    deployment - java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war.
    [wldeploy] java.io.FileNotFoundException: No such path: /export/home/beamon/applications/proxymon/proxy.war
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:191)
    [wldeploy] at weblogic.j2ee.J2EEUtils.getDeploymentInfo(J2EEUtils.java:155)
    [wldeploy] at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:467)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
    [wldeploy] at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
    [wldeploy] at sun.reflect.GeneratedMethodAccessor480.invoke(UnknownSource)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
    [wldeploy] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    [wldeploy] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
    [wldeploy] at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
    Source)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    [wldeploy] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    [wldeploy] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    [wldeploy] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    [wldeploy] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    [wldeploy] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    [wldeploy] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    [wldeploy]
    BUILD SUCCESSFUL
    Total time: 9 seconds
    Please give some solutions..........this is urgent for me. I reallyappreciate
    your time on this.
    -s

  • Ejb and jsproc deployment problems

    Am trying to deploy the java stored procedure (jsp) example
    (jsproc subdirectory in acmevideo directory) and the enterprise
    java bean (ejb) example (ejb subdirectory in acmevideo
    directory). Both use the business and util subdirectries of
    acmevideo directory. These examples are provided with
    JDeveloper.
    In the case of the jsp example, the files compile fine in
    JDeveloper. The deployment profile file is created okay using
    the Stored Procedure Profile Wizard. But when the jsp is
    attempted to be deployed by right clicking the deployment
    profile file menu in JDeveloper, the following errors appear:
    SQL error during creation of acmevideo/util/DataWrapper
    ORA-00922 - missing or invalid option
    SQL error during creation of acmevideo/business/TitleQueries
    ORA-00922 - missing or invalid option
    Is there a corrective action for these errors? Are the details
    recorded in any log so that these errors can be troubleshooted?
    In the case of the jbe example, the files compile fine in
    JDeveloper. The deployment profile file is created okay using
    the EJB Profile Wizard. But when the jsp is attempted to be
    deployed by right clicking the deployment profile file menu in
    JDeveloper, the following happens:
    The message indicating that the deployment will take a few
    minues continues to show forever. There is no completion,
    and one is forced to cancel the process.
    This happens when using the port settings of 1521, 1526 (Oracle
    listener ports) or 2651 (OAS ORB port). Specifying the service
    or omitting it yeilds the same results.
    Is there a corrective action for this? Are the details recorded
    in any log so that these errors can be troubleshooted?
    For both the situations, is the classpath variable need to set
    outside the JDeveloper environment?
    Also am not able to locate the Oracle 8i CORBA and Enterprise
    Java Beans Developer's Guide and the Oracle 8i Java Stored
    Procedure Developer's Guide referenced in Building Java
    Applications for Oracle 8i anywhere.
    Would appreciate any help in this area.
    null

    : Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
    We have ;) But I guess that doesn't count... Please have a look
    at the online demo for Enterprise JavaBeans on this technet
    website. You can get there through the JDeveloper Tech Info page.
    Please open a new thread if that doesn't help you.
    Thanks,
    -Roel.
    phil gulesian (guest) wrote:
    : mark tomlinson (guest) wrote:
    : : pretty sure the first one is a bug that is fixed in a later
    : : build of JDeveloper (JSP deployment problem).
    : : As for the EJB deployment problem, here is the way to catch
    : what
    : : is really going on (in the Beta build -- this will be done
    much
    : : better in the production build):
    : : -edit the jdeveloper.ini (in the BIN directory), in the
    : : [environment] section add:
    : : LogConsole=1
    : : -edit the jdeveloper.properties file (in the LIB directory)
    : : change the line :
    : : jdeveloper.logOutput=nul
    : : to
    : : jdeveloper.logOutput=-
    : : Now when you run JDeveloper, you will get an output onsole
    : : window for the JVM running JDeveloper. You will be able to
    see
    : : the deployment messages for the EJB wizard being sent to this
    : : console. This will allow you to troubleshoot what is
    happening.
    : I had the same experience as Bansi (above) when I tried to
    deploy
    : a simple ejb. Following your suggestions about looking in the
    : output console window for the JVM, I observed the message
    : "PropertyEditor for borland.sql.dataset.ProcedureDescriptor
    could
    : not be registered ........" A subsequent search found no
    : ProcedureDescriptor in the borland.sql.dataset package.
    : Has anyone been able to deploy an ejb from JDeveloper2 (Beta)?
    null

Maybe you are looking for

  • Define Global Variable in XSLt

    H, Please let me know how to define Global Variable in XSLT. I have define a variable under for-each and i want to use that variable after for-each. Please suggest on the same. Thanks, Pradeep

  • Imac freezes with horizontal green lines

    My Imac crashed the other day with green lines horizontally across the screen, the mouse would react and move around, but could not open any apps. We took it to get repaired at Core Mac and he said it worked fine. We brought it home today and it cras

  • Projects tab: Library - year filter

    This is just something I got curious about this evening. I have all the normal projects, folders, light tables etc that you build up over time - but - there are also the ones right under library - see this image if I'm not being clear: http://idisk.m

  • Modeling: how to place Material Grp in Material Master TABLE instead of DIM

    Hi, I just completed a review of the "...Modeling with BI" document and I will appreciate some clarification on the following: Some key points leading to question: --"..In order to cover all requirements, master tables in a BI Data model are NOT link

  • Solaris language settings

    hi how to change the language in solaris 10 x86. i have installed the hindi language. i want to change to english