JNDI not found deploy bpel in cluster

Hi I have this problem:
I install BPEL CLuster in two hosts: mtier01 and mtier02 and I have a lbr (balancer) in front of this servers (mtier01 and 02).
I deploy bpel using bpel console and I get a error:
JNDI not found.
I read log: log.xml of bpel, and it tell me:
port request of opmn not open of lbr, i need change configuration of host and port opmn for mtier01 and mtier02 (it is open in this hosts).
I don´t now why bpel or OC4J_SOA need port opmn of lbr01 (not safe, i can´t open).
If i use ANT i tell which host and port need for deploy.
* j2ee.hostname
*opmn.requestport
*http.hostaname
What can i do in the configuration of bpel for resolve tis problem?
Thanks.
Maximiliano

How i you installe the cluster, followed the documentation?
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28941/soa.htm
Marc

Similar Messages

  • JNDI not found when trying to communicate from websphere to weblogic server

    Hi,
    we have a J2EE application in which the client is a standalone program or may reside in any of the application server. But our EJB component is deployed in the weblogic server.
    Earlier the client program which contacts the EJB is a standalone program and it uses the weblogic initial context factory and t3 protocol and we will have the weblogic.jar in the classpath.
    but there is a new requirement as our new client is in websphere and it has to contact the weblogic server through IIOP protocol and websphere initial context factory. Please let me know what i need to do?
    Since iam new to websphere and i am having no clue to establish the communication. I tried to use both IIOP protocol and wesphere initial context factory.but still i get exception as the JNDI name not found.
    Guidance is appreciated.
    Thanx in advance.

    To be in same page, iam running the client program using the IBM jre and using all the websphere client jars set in classpath. This program conatins intial context factory as "com.ibm.websphere.naming.WsnInitialContextFactory" and provider url as "iiop://hostname:portnumber" it contacts the EJB bean method which is hosted on the weblogic server on the "hostname" machine. When it tries to contact i get the errror as
         "javax.naming.NameNotFoundException: Context: , name: java.iecc.env.ejb.elf.client_new(My JNDI name): First component in name java.iecc.env.ejb.elf.client_new not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]"

  • Provider not found deploying en VS 2013

    Hi all,
    On a fresh PC install, I installed VS2013 and created a single 1 table, One screen lightswitch html app.
    Triyng to make a deploy package fails with the error :
    provider 'LightSwitchApplication' not found .... visit :
    http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_PROVIDER_NOT_FOUND
    Searching results with solutions for VS2012 only (uncheck box for prerequisites while deploying)
    3 days on that issue !!
    Any help will be apreciated
    Thank's,
    Frederic 

    I was using right clic, build on the server folder! (I shoud have done that from the LS folder).
    To bad loosing 3 days on that !!
    I hope this will help someone. 
    Glad that you've solved this issue, thanks for sharing your experience.
    Best regards,
    Angie
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Instance not found in BPEL Console until Process finished

    I have two services on the server, where one (asynchronous) service is calling another (synchronous) service multiple times.
    WHen creating an instance in the BPEL Console, this instance is nowhere to be found. When trying to see the flow, an error message occurs in the console and on the BPEL server window:
    ORABPEL-02152
    Instanz in Datenquelle nicht gefunden.
    Die Prozessdomõne konnte die Instanz mit dem Schl³ssel "226865cd4e81777c:1a001ff
    :10c814abd65:-7f83" nicht aus der Datenquelle abrufen.
    Stellen Sie sicher, dass sich der Schl³ssel "226865cd4e81777c:1a001ff:10c814abd6
    5:-7f83" auf eine g³ltige Instanz bezieht, die gestartet und nicht aus der Proze
    ssdomõne entfernt wurde.
    at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:314)
    at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:262)
    at com.collaxa.cube.engine.data.AdminFinder.lookupInstanceByConversationId(AdminFinder.java:235)
    at com.collaxa.cube.ejb.impl.FinderBean.lookupInstanceByConversationId(FinderBean.java:177)
    at IFinderBean_StatelessSessionBeanWrapper42.lookupInstanceByConversationId(IFinderBean_StatelessSessionBeanWrapper42.java:669)
    at com.oracle.bpel.client.Locator.lookupInstance(Locator.java:420)
    at displayInstance.jspService(_displayInstance.java:111)
    at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
    at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
    at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
    at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
    at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
    at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
    at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
    at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
    at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
    at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
    at java.lang.Thread.run(Thread.java:534)
    Interestingly, the instances of the (synchronous) service, which are called from the mysterious service, are visible all the time and the flow can be viewed while these services are processed.
    Does anybody have an idea why this is happening?
    Thank you,
    Nina

    Hi,
    I don't understand this behaviour in detail, by now. Could you please state if this is correct?
    1. I call an async bpel process A.
    2. The message is put in the delivery queue.
    3. My client is free again, not blocking.
    4. Process A does not show up in Console by now. (If I would call checkpoint(), it would do).
    5. A worker takes the message and instantiates the Process A.
    6. Process A instance is running now, calling some sync processes.
    7. NO dehydration so far.
    8. Process A does not show up in Console by now. The called subprocess (sync) do show up, if they are completed.
    9. Loop to 6, until Process A ends and makes callback to client.
    10. After sending callback, Process A shows up in Console.
    11. Now I can monitor, what HAS happened.
    I understand, that you can't commit your process data, until a regular dehydration point is reached.
    But consequence: I can't even SEE that there exists a process instance from A, until it worked through all the steps above. I just see a swarm of sub processes without an existing parent.
    That's the behaviour, you call "intended"?
    Workaround would be to do dehydration after each bpel invoke activity. Do you see a problem in doing this?
    Thanks in advance!
    Torsten

  • Servlet Action not found , deploying the war file in Tomcat5.0.28

    Hi,
    I face the error servletAction ot found , when deplying the war on my system.I am using win98. when I run the struts-blank.war file is working fine .
    So please help me.
    I have also another probelm in Netbean 4.1
    I fixed the error of out of space by incresing the Dos memory
    Now the server is Started but it is not. able to deploy the war . This problem is happening using Netbean4.1 in windows98 system.
    it shows error in build-impl.xml file
    that error is
    It highlights the following line of build-impl.xml
    <nbdeploy debugmode="*false*" clientUrlPart="*${client.urlPart}*"
    forceRedeploy="*${forceRedeploy}*" />
    sp please help me, I am struggling for last 2 days.
    cheers,
    Manoranjan

    Hello,
    under NW7.1 the SDM is no longer availible.
    We do not have a NWDS and the deployment of the ear file by unsing JSPM failes even after renaming it into a .sca and .sda file.
    The solution in our case was to deploy the ear file by using telnet. (sounds unbelivable - but it works)
    telnet localhost 5<sys#>008
    user/PW
    Detaild help by using the man command
    DEPLOY....
    It took us half a day to figure out how it works.....

  • Getting JNDI not found on MySql/Tomcat

    Has anyone gotten ADF to work with MySql/Tomcat? I think I finially have the app working in Tomcat but now I'm getting an error with my pool/JNDI lookup. At the tomcat console I get this;
    SEVERE: Null component Catalina:type=DataSource,path=/ediweb,host=localhost,class=javax.sql.DataSource,name="jdbc/ediconnDS"
    It looks like it can't even create a connection to MySql. My app has a context.xml in the META-INF like this;
    <Context>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
    <ResourceLink global="jdbc/ediconnDS" name="jdbc/ediconnDS" type="javax.sql.DataSource" />
    </Context>
    And in my server.xml I have this;
    <Resource name="jdbc/ediconnDB" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="root" password="password" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/freightedi"/>
    In my web.xml I have this resource-ref;
    <resource-ref>
    <description>DB Connection</description>
    <res-ref-name>jdbc/ediconnDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    I've tried putting the resource in the context.xml... all kinds of stuff, to no avail.
    I tested these connection parameters in Squirrel SQL (java jdbc based SQL tool) and it works?!
    Please help :(
    Edited by: user10419690 on Apr 15, 2009 8:51 AM

    Tomcat isn't giving any errors on boot and I have the MySql JDBC resource in it;
    in the server.xml;
         <Resource name="jdbc/ediconnDB" auth="Container" type="javax.sql.DataSource" maxActive="100" maxIdle="30" maxWait="10000" username="root" password="Slgedi01" driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/freightedi?autoReconnect=true;ultraDevHack=true;capitalizeTypeNames=true;pedantic=true"/>
    in my web.xml
    <resource-ref>
    <description>MySql Connection</description>
    <res-ref-name>jdbc/ediconnDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    in my context.xml
    <?xml version="1.0" encoding="utf-8" ?>
    <Context>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
    <ResourceLink global="jdbc/ediconnDS" name="jdbc/ediconnDS" type="javax.sql.DataSource" />
    </Context>
    The tomcat console says;
    WARNING: ADFc: JNDI failure. Unable to lookup Data Source at context java:comp/env/jdbc/ediconnDS
    oracle.jbo.DMLException: JBO-27200: JNDI failure. Unable to lookup Data Source at context java:comp/env/jdbc/ediconnDS
    at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1557)
    at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:272)
    The ADF Gui on the web page says;
    Messages for this page are listed below.
    JNDI failure. Unable to lookup Data Source at context java:comp/env/jdbc/ediconnDS
    Name ediconnDS is not bound in this Context
    Unexpected exception caught: java.lang.NullPointerException, msg=null
    Anything?

  • QueueConnectionFactory jndi not found

    I want to sent a message from a client to a MDB,
              but uo to now without much success.
              I get error like : JNDI name not known etc.
              Who knows some examples about setting up the MDB, the Client
              and the configuration of the WebLogic (8.1) part ?
              (I guess this is: QueueConnectionFactory, JMS Server, Queue)
              kind regs.
              Harry van Rijn

    did you add this name to your QueueConnection factory first?

  • URGENT! - Page not found

    Hi,
    I'm facing a major problem for my apex-application.
    In development-environment there's no problem.
    But when i deploy my app to the prodution-server, i got a Page not found for 1 page in the whole application.
    Normally, when a page is not found, you get it like this:
    Contact your application administrator.
    ERR-1016 Application "312" Page "14556" not found (requested language="nl-be")
    Ga terug naar de applicatie.
    But now I just got the Firefox/IE-error page (page not found)
    Deploying to production-server did not log any problems
    There's no branch at the start of the page. URL-format is correct (https://www.+hostingserver+.be/pls/apexsaas5/f?p=312:2061:698649154368063). The javascript part doesn't do any branch either.
    Anyone who's had the same problem?
    Thanks in advance

    Ok..
    Are you sure that there is not authorization scheme or condition applied on that page...
    Just to pinpoint the problem try to make your page Public ???
    If you edit the page of "2061", then click run icon .... your page is working fine ???
    And when you use this URL, it does not work ??
    https://www.hostingserver.be/pls/apexsaas5/f?p=312:2061
    Edit your page, and make sure that:
    Page Access Protection is "UNRESTRICTED"
    I hope that works for you...
    Best Regards,
    Fateh

  • BPEL Deployment issue - parent application (orabpel) is not found!

    Hello everyone,
    I've a got a small issue while deploying the Oracle's VocationRequest BPEL project to the my BPEL Server. It produces the following output:
    --- BEGIN ---
    parent application (orabpel) is not found!
    [deployTaskForm]
    [deployTaskForm]
    BUILD FAILED
    C:\Jdeveloper10.132\jdev\mywork\HumanWorkFlow\simplewf\build.xml:98: Error while deploying the form on server "uranus" Error message :
    java.lang.SecurityException
         at oracle.ide.IdeCore$7.checkExit(IdeCore.java:177)
         at java.lang.Runtime.exit(Runtime.java:88)
         at java.lang.System.exit(System.java:868)
         at oracle.oc4j.admin.deploy.cmdline.Oc4jAdminCmdline.executeCommand(Oc4jAdminCmdline.java:127)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployIAS(DeployForm.java:750)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployForm(DeployForm.java:548)
         at com.collaxa.cube.ant.taskdefs.DeployForm.deployForms(DeployForm.java:814)
         at com.collaxa.cube.ant.taskdefs.DeployForm.execute(DeployForm.java:840)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at oracle.jdevimpl.ant.runner.AntLauncher.launch(AntLauncher.java:321)
         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 oracle.jdevimpl.ant.runner.InProcessAntStarter.runAnt(InProcessAntStarter.java:295)
         at oracle.jdevimpl.ant.runner.InProcessAntStarter.mav$runAnt(InProcessAntStarter.java:43)
         at oracle.jdevimpl.ant.runner.InProcessAntStarter$1.run(InProcessAntStarter.java:71)
    --- END ---
    I've been looking at other resource for help but are unable to find anything which is relevant. Your time and help is much appreciated.
    Thanks and Regards,
    John

    Advanced version is when you have created the dehydration store in a database of your choice. It also creates a separate oc4j instance (oc4j_soa).
    Basic means that it installs the dehydration store into an Oracle lite database. It also stores all deployements into the oc4j instance home.
    You can check this by going to the enterprise manager and see what oc4j instances have been created. If you see home and oc4j_soa I would sugest that you have done an advanced install. If you only see the home oc4j instance I would say that you have a basic install.
    Now to answer your question. Looking at your note you are pointing the application server to the home instance. If you look at you Integration server you point this to your application server connection. This is home. If you have done an advanced install this should be oc4j_soa.
    Plan of attack.
    Check what install you have by looking at the enterprise manager.
    If it is advanced chnage your JDev connection to oc4j_soa.
    Otherwise update the post and we will go from there.
    cheers
    James

  • AIA Instal failing on Cluster AIAReadJMSNotificationProcess not found

    Hi,
    I am installing AIA on SOA 11.1.1.5 during installation I am running into below error. I am trying to install AIA on a cluster environment on HP-UX box. Need help in resolving the below I see the below in the log.
    Here is the command that I ran to begin the installation
    ant -f AIAInstallDriver.xml -DPropertiesFile=$AIA_HOME/aia_instances/AIA_01/config/AIAInstallProperties.xml -logfile $AIA_HOME/aia_instances/AIA_01/logs/FPInstall.log -DDeploymentPlan=$AIA_HOME/aia_instances/AIA_01/config/FPInstallDP.xmlAnd here is error am getting after 28+ minutes of installation progress.
         [wlst] Activation completed
         [wlst] Disconnected from weblogic server: AdminServer
         [wlst] <Jul 25, 2012 4:33:29 PM CDT> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>
         [echo]  executing Endpoint Configurator over the dir : <AIA_HOME>/Infrastructure/ErrorHandling/src/AIAErrorTaskAdministrationApp/AIAErrorTaskAdministrationProcess
         [echo] Fixing AIAErrorTaskAdministrationProcess endpoints per Oracle Support DOC 1369101.1
    BUILD FAILED
    <AIA_HOME>/Infrastructure/Install/AID/AIAExecuteDriver.xml:117: The following error occurred while executing this line:
    <AIA_HOME>/Infrastructure/Install/AID/AIAExecuteDriver.xml:64: The following error occurred while executing this line:
    <AIA_HOME>/aia_instances/AIA_01/tmp/AIDExecuteDP_temp_1892431361.xml:15: The following error occurred while executing this line:
    <AIA_HOME>/Infrastructure/Install/AID/lib/AIDDeploymentLibraryTasks.xml:160: The following error occurred while executing this line:
    <AIA_HOME>/Infrastructure/Install/AID/lib/AIDConfigurationLibraryTasks.xml:703: <AIA_HOME>/Infrastructure/ErrorHandling/src/AIAErrorTaskAdministrationApp/AIAErrorTaskAdministrationProcess/Infrastructure/ErrorHandling/src/AIAReadJMSNotificationProcessApp/AIAReadJMSNotificationProcess not found.
    Total time: 29 minutes 5 secondsFrom the logs above it's complaining about AIAReadJMSNotificationProcess not found but shouldn't the installer have took care of it.
    When I go to the Enterprise Manager I don't see any AIA related composites being deployed I do see AIA Application deployed. But the installation is failing. Any idea on what might be wrong and how to correct it and start the installation from where it ended.
    Any help is appreciated.
    Thanks

    With those informations alone it is hard to tell whats happening.
    Even if you perform a "boot -x" I would expect that your public network is getting configured, since on your described setup you should have a /etc/hostname.qfe0 and /etc/hostname.qfe4 in order to setup the IPMP group and possible test addresses. So ifconfig should show something for at least those interfaces. Since you are not even seeing lo0, I would expect several error messages on the console.
    Since no obvious reasons springs to my mind as of why you do not see this, I suggest to open a service call with Sun (if you have a support contract that is) in order to get the system(s) better analyzed. A lot more informations are necessary to understand the problem. Anything within /var/adm/messages (even the older ones) that might give a hint? Any administrative changes lately?
    Greets
    Thorsten

  • BPEL Archive directory {0} not found

    Hello,
    I have created deploy.xml,to deploy bpel processes on SOA server which is on unix based machine.
    xml is like
    <?xml version="1.0" encoding="windows-1252" ?>
    - <project default="Install" xmlns:oracle="antlib:oracle" basedir=".">
    <property name="process.dir" value="${basedir}" />
    <property name="package.dir" value="${basedir}/Package" />
    <echo>$(basedir) $(process.dir) $(package.dir)</echo>
    - <!-- Accounts Payable WorkFlow Version
    -->
    <property name="FlowVersion" value="1.0" />
    <property environment="env" />
    - <!-- First override from build.properties in process.dir, if available
    -->
    - <!-- Set bpel.home from developer prompt's environment variable BPEL_HOME
    -->
    - <condition property="bpel.home" value="${env.BPEL_HOME}">
    <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
    </condition>
    <xmlproperty file="${process.dir}/bpel/bpel.xml" />
    <property name="process.name" value="${BPELSuitcase.BPELProcess(id)}" />
    - <!-- If bpel.home is not yet using env.BPEL_HOME, set it for JDev
    -->
    - <!--      <property name"bpel.home" value="/apps/soa/product/10.1.3.1/OracleAS_1/bpel">
    -->
    <property name="bpel.home" value="C:/product/10.1.3.1/OracleAS_1/bpel" />
    <property name="bpel.home" value="${oracle.home}/integration/bpel" />
    <property file="${bpel.home}/utilities/ant-orabpel.properties" />
    <property name="bpel.home" value="${bpel.home}" />
    - <!-- import custom ant tasks for the BPEL PM
    -->
    <import file="${bpel.home}/utilities/ant-orabpel.xml" />
    - <!-- Use deployment related default properties
    -->
    - <!--
    This Task is Used to Unjar the jar file & replace the Token value,but needs to identify
    required or not. & if required from where it is get called.
    -->
    - <!-- Define the deployer URL
    -->
    <echo>Deployer URI : deployer:oc4j:opmn://${j2ee.hostname}:${opmn.requestport}/${oc4jinstancename}</echo>
    <property name="deployer.url" value="deployer:oc4j:opmn://${j2ee.hostname}:${opmn.requestport}/${oc4jinstancename}" />
    <echo>------------------------------------------------------------------- | ${env.BPEL_HOME} | Deploying to Server deployer:oc4j:opmn://${j2ee.hostname}/${oc4jinstancename} -------------------------------------------------------------------</echo>
    <property name="process" value="process1" />
    - <target name="FixURLLocations">
    <echo>------------------------------------------------------------------- | Updating Web Service Location Information | JAR file to update: ${p.jarfile} | Web Service Location base: http://${http.hostname}:${http.port} -------------------------------------------------------------------</echo>
    <delete dir="${package.dir}/temp" verbose="no" quiet="yes" failonerror="no" />
    <mkdir dir="${package.dir}/temp" />
    <mkdir dir="${package.dir}/Save" />
    <copy file="${p.jarfile}" todir="${package.dir}/Save" />
    <unjar src="${p.jarfile}" dest="${package.dir}/temp" overwrite="yes" />
    <!-- Code to replace some hardcoded values -->
    <delete file="${p.jarfile}" verbose="no" quiet="yes" failonerror="no" />
    <jar destfile="${p.jarfile}" basedir="${package.dir}/temp" update="yes" />
    <delete dir="${package.dir}/temp" verbose="no" quiet="yes" failonerror="no" />
    </target>
    <target name="Test">
    <echo>---------------------------------------------------------------- | Deploying process GWT_SP_L1WipBPELProcess ----------------------------------------------------------------</echo>
    <antcall target="FixURLLocations">
    <param name="p.jarfile" value="${package.dir}/Test.jar" />
    </antcall>
    <deployProcess user="${admin.user}" password="${admin.password}" domain="${domain}" process="${process.name}" rev="${rev}" dir="${package.dir}/output" hostname="${http.hostname}" httpport="${http.port}" verbose="${verbose}" isSSL="${isSSL}" trustStore="${trustStore}" trustPassword="${trustPassword}" />
    </target>
    <target name="Install" depends="bpel, apps_webservice">
    <tstamp />
    <echo>--------------------------------------------------------- | Deployed all process ---------------------------------------------------------</echo>
    </target>
    <target name="apps_webservice" depends="Test">
    <tstamp />
    <echo>--------------------------------------------------------- | Webserivces and application Installation completed directory "{0}" ---------------------------------------------------------</echo>
    </target>
    <target name="bpel" depends="">
    <tstamp />
    <echo>--------------------------------------------------------- | BPEL Process Installation completed ---------------------------------------------------------</echo>
    </target>
    </project>
    but when I try to run this xml using Ant It,unjar file files replaces code ,make jar again and on deploying it gives following error
    BPEL Archive directory {0} not found.
    Could you please tell me why this error is coming and how i can resolve it?

    Hello,
    Could any one help regarding this.
    Please suggest why d<deployprocess> is failing and giving BPEL Archive directory {0} not found.
    Could
    <copy file="${p.jarfile}" todir="C:\product\10.1.3.1\OracleAS_1\bpel\domains\default\deploy" />
    replace <deployprocess>
    Thanks & Regards,
    Jignya

  • EJB3.0 App deployed with warning:Object not found in lookup of JPA_DEFAULT

    Hi All ,
               I am working on NWCE7.1. I am deploying Enterprise Application DC wich is having
    1 . 3 EJB3.0 session DCs
    2.  1 JPA DC
    I am getting following warning in deployment. I have checked persistence.xml for jta-data-source , it is added. Still not working. I am getting this error after importing configuration(Track) for these DCs in my NWDS. Earlier build n deployment was working in other NWDS on other PC.
    --- Deploying file(s):
         D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
    --- Status:
         Deploy finished with warnings.
    --- Description:
                S U M M A R Y
    ~~~~~~~~~~~~~~~~~~~
    Successfully deployed:           0
    Deployed with warnings:           1
    Failed deployments:                0
    ~~~~~~~~~~~~~~~~~~~
    1. File:D:\NWDS7.1\workspace.jdi\4\DCs\asianpaints.com\erecapp\_comp\gen\default\deploy\asianpaints.com~erecapp.ear
         Name:erecapp
         Vendor:asianpaints.com
         Location:J2N_ERECTT_D
         Version:20090217100038
         Deploy status:Warning
         Version:HIGHER
         Description:
              1. Exception has been returned while the 'asianpaints.com/erecapp' was starting. Warning/Exception :
    [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
         at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
         at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
         at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
         at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
         at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
         at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
         at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
         at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
         at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
         at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
         at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
         at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
         at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
         at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
         at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
         at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
         at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
         at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
    Result
    Status:Warning

    You have to give an explicit data source in your persistence.xml to solve this error normaly.
    <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
         <persistence-unit name="YOUR_UNIT">
        <jta-data-source>DSNAME</jta-data-source>
    Frank

  • BPEL processes not available on BPEL console when deployed from JDeveloper

    Installation: SOA Suite 10.1.3.4 (Upgraded through patch) (Standalone OC4J)
    When I deploy the BPEL processes through JDeveloper, they do not show up in the BPEL console. JDeveloper does not display any error message but in fact displays successful deploy. I am able to manually deploy processes from the BPEL console itself or by dropping in the BPEL suitcase in the deploy directory.
    I noticed this issue when I tried installing AIA foundation pack 2.4. The installation showed the message below -
    Failed to read wsdl at "http://AMVAIDYA-US:8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess?wsdl", because "Failed to read WSDL from http://AMVAIDYA-US:8888/orabpel/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess?wsdl:WSDL not found".
    Make sure wsdl is valid. You may need to start the OraBPEL server, or make sure the related bpel process is deployed correctly.
    [Potential fix]: If your site has a proxy server, then you may need to configure your BPEL Server, designer and browser with your proxy server configuration settings (see tech note on http://otn.oracle.com/bpel for instructions).
    I noticed that issue is independent of AIA since I cannot deploy any BPEL process through JDeveloper (or even through using the ant deploy in JDev)
    Please help!
    Thanks
    Amol

    I did try the verbose=true option but there are no errors there. The ant deploy task shows up as successful just like it shows from the right click -> Deploy to domain on the BPEL project. I created a sample async BPEL for this - it has just one assign activity with some dummy values for output. It builds fine. If I deploy the jar file created from this manually in the console it works. But it doesnt work from JDev or Ant. Is there anything I missed during the upgrade patch from 10.1.3.1 to 10.1.3.4? I did execute all the post and pre install tasks (including the orabpel, oraesb schema updates etc)
    FYI, I can register an ESB from JDeveloper and it shows up in the ESB console.

  • Custom Objects in JNDI Not Being Replicated in Cluster

    I know this is going to end up being something really simple, but I can't find
    any docs or other posts on it.
    I have a simple two node weblogic 7.0 cluster. In a startup class that is deployed
    to the cluster I check for and create a subcontext. This subcontext will just
    hold custom objects when a node comes up. When a node does come up, one of the
    web applications binds a non-RMI custom object to the subcontext created via the
    startup class.
    Once both nodes in the cluster are up I can see via the weblogic console's "View
    JNDI tree" feature that the custom object bound on node 1 is only visible in the
    JNDI tree of node 1. Similarly the object bound on node 2 is only visible in
    the JNDI tree of node 2.
    Is the JNDI tree that is visible via the console the JNDI specific to the node
    and not the clusterwide JNDI tree? Do I have to do something special to get access
    to the cluster wide JNDI tree (for instance when creating an InitialContext)?
    Is there a way to view the cluster wide JNDI tree?
    Thanks for any information.

    Hi Matt,
    how did you compile t3 stubs,there are -clusterable or something like this
    option shat should make replicatable-aware stubs.
    "Matt" <[email protected]> wrote:
    >
    I know this is going to end up being something really simple, but I can't
    find
    any docs or other posts on it.
    I have a simple two node weblogic 7.0 cluster. In a startup class that
    is deployed
    to the cluster I check for and create a subcontext. This subcontext
    will just
    hold custom objects when a node comes up. When a node does come up,
    one of the
    web applications binds a non-RMI custom object to the subcontext created
    via the
    startup class.
    Once both nodes in the cluster are up I can see via the weblogic console's
    "View
    JNDI tree" feature that the custom object bound on node 1 is only visible
    in the
    JNDI tree of node 1. Similarly the object bound on node 2 is only visible
    in
    the JNDI tree of node 2.
    Is the JNDI tree that is visible via the console the JNDI specific to
    the node
    and not the clusterwide JNDI tree? Do I have to do something special
    to get access
    to the cluster wide JNDI tree (for instance when creating an InitialContext)?
    Is there a way to view the cluster wide JNDI tree?
    Thanks for any information.

  • JNDI Exception on re-deployment to a cluster

    I'm getting an error that I have not seen in the newsgroups so far. It
              happens when I deploy what I believe to be a properly configured clusterable
              application (.ear file) to my cluster.
              Here's my setup:
              WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
              is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
              cluster). The 1st managed server (app1) is also on Stimpy bound to
              10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
              (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
              to deploy the app. (I turned auto-deploy off because the app was getting
              deployed to the admin server automatically and throwing an error because of
              the clustered HTTP session state)
              Here's what happens.
              I start up all of the instances with no apps deployed. Everything appears
              to be running fine. No errors. I then use the console to deploy my
              application (sample1.0.ear). I select only the cluster as the target for
              the EJB and the webapp. If I try to access the app at this point I just get
              404's. I then restart all of the servers and the app gets deployed across
              the cluster with no errors. I can access everything JSPs, servlets, and an
              EJB without issue.
              My problem comes when I try to re-deploy the application. I have tried this
              using the console, and by copying the new .ear file to the applications
              directory on the admin server. I always get the same error, and it only
              shows up on "app1" the first managed server in the cluster. Below is the
              output form the log:
              Undeploying EJB Component HelloWorldEJB
              <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
              <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
              HelloWorldEJB.j
              ar>
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
              : H
              elloWorldEJB
              weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
              exc
              eption is:
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              repl
              ica-aware stub to a name that is currently bound to a replica-aware stub;
              remain
              ing name ''
              javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              replica-awar
              e stub to a name that is currently bound to a replica-aware stub; remaining
              name
              <<no stack trace available>>
              >
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
              sampl
              e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
              >
              <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
              <InvocationTargetException s
              etting attribute Deployed on MBean
              me:Name=sample1.0,Location=app3,Type=Applicat
              ionConfig to value true. Method: public void
              weblogic.management.mbeans.custom.A
              pplication.setDeployed(boolean) throws
              weblogic.management.DeploymentException,w
              eblogic.management.UndeploymentException
              weblogic.management.DeploymentException: Could not deploy:
              'HelloWorldEJB.jar':
              JNDI name in use
              at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
              at weblogic.j2ee.Application.deploy(Application.java:167)
              at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
              at
              weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
              ation.java:217)
              at
              weblogic.management.mbeans.custom.Application.setDeployed(Application
              .java:187)
              at java.lang.reflect.Method.invoke(Native Method)
              at
              weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
              anImpl.java:1136)
              at
              weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              anImpl.java:773)
              at
              weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              anImpl.java:750)
              at
              weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
              igurationMBeanImpl.java:256)
              at
              com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              ava:1356)
              at
              com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              ava:1331)
              at
              weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
              teMBeanServerImpl_WLSkel.java:1075)
              at
              weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:373)
              at
              weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              va:237)
              at
              weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              andler.java:118)
              at
              weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              .java:17)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              to b
              ind an object under the name HelloWorldHome_EO in the jndi tree. The object
              you
              have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is
              non
              clusterable and you have tried to bind more than once from two or more
              servers.
              Such objects can only deployed from one server.>
              <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              to b
              ind an object under the name HelloWorldHome in the jndi tree. The object you
              hav
              e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
              clu
              sterable and you have tried to bind more than once from two or more servers.
              Suc
              h objects can only deployed from one server.>
              Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
              As far as I know, I have not installed the EJB2.0 container. Does this get
              installed by default with sp1? Also, I quite sure that my deployment
              descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
              EJB:
              <?xml version="1.0"?>
              <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
              EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
              <weblogic-ejb-jar>
              <weblogic-enterprise-bean>
              <ejb-name>HelloWorld</ejb-name>
              <caching-descriptor>
              <max-beans-in-free-pool>100</max-beans-in-free-pool>
              </caching-descriptor>
              <clustering-descriptor>
              <home-is-clusterable>true</home-is-clusterable>
              <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
              <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
              potent>
              </clustering-descriptor>
              <jndi-name>HelloWorldHome</jndi-name>
              </weblogic-enterprise-bean>
              </weblogic-ejb-jar>
              Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
              going on here?
              

    This seems like potential redeploy/undeploy bugs. COuld you follow up with
              [email protected]
              Viresh Garg
              Principal Developer Relations Engineer
              BEA Systems
              Paul Citarella wrote:
              > I'm getting an error that I have not seen in the newsgroups so far. It
              > happens when I deploy what I believe to be a properly configured clusterable
              > application (.ear file) to my cluster.
              >
              > Here's my setup:
              > WebLogic 6.0 sp1, three instances across 2 machines. The admin server (wl1)
              > is running on Stimpy (win2kAS) on 10.10.10.21 (it is not part of the
              > cluster). The 1st managed server (app1) is also on Stimpy bound to
              > 10.10.10.22 (a virtual IP). The second managed server (app3) is on Ren
              > (also win2kAS) at 10.10.10.23. Auto-deploy is off. I am using the console
              > to deploy the app. (I turned auto-deploy off because the app was getting
              > deployed to the admin server automatically and throwing an error because of
              > the clustered HTTP session state)
              >
              > Here's what happens.
              >
              > I start up all of the instances with no apps deployed. Everything appears
              > to be running fine. No errors. I then use the console to deploy my
              > application (sample1.0.ear). I select only the cluster as the target for
              > the EJB and the webapp. If I try to access the app at this point I just get
              > 404's. I then restart all of the servers and the app gets deployed across
              > the cluster with no errors. I can access everything JSPs, servlets, and an
              > EJB without issue.
              >
              > My problem comes when I try to re-deploy the application. I have tried this
              > using the console, and by copying the new .ear file to the applications
              > directory on the admin server. I always get the same error, and it only
              > shows up on "app1" the first managed server in the cluster. Below is the
              > output form the log:
              >
              > Undeploying EJB Component HelloWorldEJB
              > <Apr 16, 2001 10:24:52 PM EDT> <Info> <J2EE> <Undeployed : sample1.0>
              > <Apr 16, 2001 10:24:53 PM EDT> <Info> <EJB> <EJB Deploying file:
              > HelloWorldEJB.j
              > ar>
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying EJB Component
              > : H
              > elloWorldEJB
              > weblogic.ejb20.EJBDeploymentException: Error deploying stateless EJB; nested
              > exc
              > eption is:
              > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > repl
              > ica-aware stub to a name that is currently bound to a replica-aware stub;
              > remain
              > ing name ''
              > javax.naming.NameAlreadyBoundException: Can't rebind anything but a
              > replica-awar
              > e stub to a name that is currently bound to a replica-aware stub; remaining
              > name
              > ''
              > <<no stack trace available>>
              > >
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <J2EE> <Error deploying application
              > sampl
              > e1.0: Could not deploy: 'HelloWorldEJB.jar': JNDI name in use
              > >
              > <Apr 16, 2001 10:24:53 PM EDT> <Error> <Management>
              > <InvocationTargetException s
              > etting attribute Deployed on MBean
              > me:Name=sample1.0,Location=app3,Type=Applicat
              > ionConfig to value true. Method: public void
              > weblogic.management.mbeans.custom.A
              > pplication.setDeployed(boolean) throws
              > weblogic.management.DeploymentException,w
              > eblogic.management.UndeploymentException
              > weblogic.management.DeploymentException: Could not deploy:
              > 'HelloWorldEJB.jar':
              > JNDI name in use
              >
              > at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:35)
              > at weblogic.j2ee.Application.deploy(Application.java:167)
              > at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:173)
              > at
              > weblogic.management.mbeans.custom.Application.setLocalDeployed(Applic
              > ation.java:217)
              > at
              > weblogic.management.mbeans.custom.Application.setDeployed(Application
              > .java:187)
              > at java.lang.reflect.Method.invoke(Native Method)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBe
              > anImpl.java:1136)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              > anImpl.java:773)
              > at
              > weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBe
              > anImpl.java:750)
              > at
              > weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Conf
              > igurationMBeanImpl.java:256)
              > at
              > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              > ava:1356)
              > at
              > com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.j
              > ava:1331)
              > at
              > weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Remo
              > teMBeanServerImpl_WLSkel.java:1075)
              > at
              > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              > va:373)
              > at
              > weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.ja
              > va:237)
              > at
              > weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestH
              > andler.java:118)
              > at
              > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
              > .java:17)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > >
              > <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              > to b
              > ind an object under the name HelloWorldHome_EO in the jndi tree. The object
              > you
              > have bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is
              > non
              > clusterable and you have tried to bind more than once from two or more
              > servers.
              > Such objects can only deployed from one server.>
              > <Apr 16, 2001 10:24:54 PM EDT> <Error> <Cluster> <Conflict start: You tried
              > to b
              > ind an object under the name HelloWorldHome in the jndi tree. The object you
              > hav
              > e bound weblogic.rmi.cluster.ClusterableRemoteObject from 10.10.10.21 is non
              > clu
              > sterable and you have tried to bind more than once from two or more servers.
              > Suc
              > h objects can only deployed from one server.>
              >
              > Here's a question. Why am I seeing "weblogic.ejb20.EJBDeploymentException"?
              > As far as I know, I have not installed the EJB2.0 container. Does this get
              > installed by default with sp1? Also, I quite sure that my deployment
              > descriptors are correct. Here's my weblogic-ejb-jar.xml for the HelloWorld
              > EJB:
              >
              > <?xml version="1.0"?>
              > <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 5.1.0
              > EJB//EN' 'http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd'>
              > <weblogic-ejb-jar>
              > <weblogic-enterprise-bean>
              > <ejb-name>HelloWorld</ejb-name>
              > <caching-descriptor>
              > <max-beans-in-free-pool>100</max-beans-in-free-pool>
              > </caching-descriptor>
              > <clustering-descriptor>
              > <home-is-clusterable>true</home-is-clusterable>
              > <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
              > <stateless-bean-methods-are-idempotent>true</stateless-bean-methods-are-idem
              > potent>
              > </clustering-descriptor>
              > <jndi-name>HelloWorldHome</jndi-name>
              > </weblogic-enterprise-bean>
              > </weblogic-ejb-jar>
              >
              > Who needs clustering anyway, damn it?! (Well...I do) Any one know what's
              > going on here?
              

Maybe you are looking for

  • CUE 8.6.10 error "login as administrator failed" message

    Hi guys, i have a new router with CUE 8.6.10 am trying to run the wizard and an error appears " "login as administrator failed" the username and password is 100% correct also the below commands exists in my configuration ip http server ip http authen

  • No fact table exists at the requested level of detail Error.

    Hi Everybody, Facing a issue on the using  Fact less Fact tables. Scenario: ======== Using two subject areas to develop a report.OBIEE 11g Fact1 --> Compensation Plan Assignments Real Time Fact2 --> Participant Detail Real Time"."Participant Details

  • Inserting a Mac command symbol into a document

    Ok, this should be so simple but it's doing my head in. Basically, I'm preparing an indesign document - specifically a clue card sheet for call centre workers who use a Mac platform. I cannot for the life of me figure out how to insert the various sy

  • Why doesn't the Radio option show up in the Library in iTunes 11?

    Everything else selected in preferences shows up in the Library (Movies, TV Shows, Tones, etc) but not Radio.  What am I missing? I also verified that there is no conflict with Parental Controls. BTW, I'm not a fan of the new look of iTunes at all. i

  • Error during Check-In of SAP-JEE, SAP-BUILDT, SAP-JTECHS

    Hello, I'm configuring a NWDI track for ESS/MSS using the cookbook documentation. I'm using a NWDI 7.0 but the ESS/MSS is deployed in a J2EE 6.40 as it is linked to a backend ECC 5.0. Now, I'm stuck at the check-in step of the cookbook. I have the fo