How the ejb is bound to JNDI name

I am very new to Oracle App server. In weblogic, we declare the jndi-name of an EJB in weblogic-ejb-jar.xml file.
I did not see this in OC4J.
Actualli I have written a simple stateful session bean and trying to access it through a standalone java client. But don't know what to look up in JNDI.
HELP PLEASE!!!!!!!!!

Hi Vinay,
Your question has been asked (and answered) many times previously in this forum. (However, when I tried searching the forum archives, I only got three results!?!)
The below code shows how to perform a lookup of the "home" interface of an EJB from a stand-alone, non-deployed java client:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,
        "com.evermind.server.rmi.RMIInitialContextFactory");
props.put(Context.PROVIDER_URL,"ormi://<host>/<app_name>");
props.put(Context.SECURITY_PRINCIPAL,"admin");
props.put(Context.SECURITY_CREDENTIALS,"<admin_password>");
new InitialContext(props).lookup("<home_name>");where "<host>" is the name of the machine where OC4J is running;
"<app_name>" is the name you gave to the application when you deployed it;
"<admin_password>" is the password for the "admin" user (that you supplied when you installed OC4J);
"<home_name>" is the value of the "<ejb-name>" element from your "ejb-jar.xml" file.
I have assumed that you have not set up any special security for your application -- otherwise you need to change the values for the SECURITY_PRINCIPAL and SECURITY_CREDENTIALS properties.
I have also assumed that you are using the stand-alone version of OC4J.
Good Luck,
Avi.

Similar Messages

  • [EJB:011055]Error deploying the EJB with error that JNDI name already inuse

    Hi,
    I have written a trivial application consisting of 4 stateless beans and 1 MDB. The ear is developed from some code generator tool and works fine if I directly deploy on weblogic server 812.
    But in order to learn Weblogic Workshop I created new Application and EJB project. Then I imported the EJB jar and provided other source files.
    From Weblogic Workshop I could generate the ear successfully. But while trying to deploy the ear I get the following exception :
    <16/03/2005 10:02:38 PM GMT+05:30> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application hsbc.
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: prepare failed for MCAppBEAN.jar
    Module: MCAppBEAN.jar Error: Exception preparing module: EJBModule(MCAppBEAN.jar,status=NEW)
    Unable to deploy EJB: StatelessBean from MCAppBEAN.jar:
    <b>[EJB:011055]Error deploying the EJB 'StatelessBean(Application: hsbc, EJBComponent: MCAppBEAN.jar)', the JNDI name 'StatelessBeanHSBC' is already in use. You mu
    st set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor for this EJB before it can be deployed.</b> at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2556)
    at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
    at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
    at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
    at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    --------------- nested within: ------------------
    <b>Can someone tell where have I made the mistake?</b>
    thanks in advance.

    Try to undeploy and un target the applcation via WLS console and they try to deploy it again. Or just try to redeploy it.

  • How the ejb know about an authenticated user?

    Hi
    perhaps it is a dummy question but I didn't find any explicit answer.
    I'd like to know how the ejb can know if a user belongs to a role.
    For example if I want to access my ejb with a servlet, and this servlet is protected
    (access allowed only for group customer)
    and in my bean's deployment descriptor I have protected one method with the security
    role customer)
    What I am wondering is when the user is authenticated in the servlet as a customer
    and then try to access the method how the ejb knows that this user is in the group
    customer??
    Is this information included in the http session or in the initialcontext created
    in the servlet or somewhere else??
    thanks for your help
    romain

    Romain - I think the answer to your question is that the information
    identifying the user is passed into the initial context parameters. Weblogic
    uses this to propagate the security context from the servlet container to
    the ejb container.
    cheers,
    Markus
    "romain" <[email protected]> wrote in message
    news:3b0e8b23$[email protected]..
    >
    Hi
    perhaps it is a dummy question but I didn't find any explicit answer.
    I'd like to know how the ejb can know if a user belongs to a role.
    For example if I want to access my ejb with a servlet, and this servlet isprotected
    (access allowed only for group customer)
    and in my bean's deployment descriptor I have protected one method withthe security
    role customer)
    What I am wondering is when the user is authenticated in the servlet as acustomer
    and then try to access the method how the ejb knows that this user is inthe group
    customer??
    Is this information included in the http session or in the initialcontextcreated
    in the servlet or somewhere else??
    thanks for your help
    romain

  • How to lookup EJB3 beans using JNDI names without defining ejb-ref in DD?

    Hi Kenneth,
    I am just continuing the topic:
    How Lookup SLSB from other SLSB? <HELP>
    http://forum.java.sun.com/thread.jspa?threadID=5117484&tstart=0
    (my original forums account failed, so I am using new one)
    if I am not seeking portability I should be able to lookup a bean directly through JNDI without using the ejb-ref. (I just want to see how it can be done)
    http://forum.java.sun.com/thread.jspa?forumID=13&threadID=751907
    http://www.theserverside.com/discussions/thread.tss?thread_id=16402
    I am using SJSAS PE 9.0 I am failing to lookup my beans from other beans directly without ejb-ref.
    Is there some sample code to look at?
    Thanks!

    Global JNDI names are vendor-specific and not known until deployment time. That is one
    of the main reasons the Java EE component environment model defines a level of
    indirection for accessing component dependencies. It is best to use either an ejb-ref
    or @EJB annotation when accessing EJBs from a Java EE component.
    If you choose not to, you just have to make sure the global JNDI name you use matches
    the one assigned to the target EJB. We have a lot of information on how this works
    in our EJB FAQ.
    https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
    If you're still encountering an error, please provide more specifics about your application,
    the code you're using for the lookup, and the error message you're receiving. Just
    saying "my looking fails" doesn't help us diagnose the problem :-)
    --ken                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • EJB not getting bound to JNDI name using Sun App Server upon deployment

    Hello,
    I've created a very simple "HelloWorld" EJB (2.1-style) and have successfully deployed it to my local application server (Sun Java System App Server Platform Edition 9.0). I now want to invoke the EJB (I have single stateless session bean that returns a string) using a simple remote client app (the client app is executing outside of the app server within its own JVM).
    From my client app I am able to create the InitialContext object, but I get error when trying to lookup my EJB's home object. My client looks as follows:
                   jndiProperties = new Properties();
                   jndiProperties.put("java.naming.factory.initial",
                        "com.sun.jndi.cosnaming.CNCtxFactory");
                   jndiProperties.put("java.naming.provider.url",
                        "iiop://localhost:3700"); // ORB listener is listening on port 3700...
                   context = new InitialContext(jndiProperties);
                   home = context.lookup("ejb/HelloWorldEJB"); // this line throws an exception (line 54)
                   ...The exception I receive is:
                   [java] 234  ERROR [main] net.blueslate.sample.ejb.helloworld.HelloWorldClient     - javax.namin
    g.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.
    org/CosNaming/NamingContext/NotFound:1.0]
         [java]     at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
         [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
         [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
         [java]     at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
         [java]     at javax.naming.InitialContext.lookup(InitialContext.java:351)
         [java]     at net.blueslate.sample.ejb.helloworld.HelloWorldClient.main(HelloWorldClient.java:5
    4)
         [java] Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/Naming
    Context/NotFound:1.0
         [java]     at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72
         [java]     at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
         [java]     at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
         [java]     ... 4 moreHere is my ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar
         xmlns="http://java.sun.com/xml/ns/j2ee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
         version="2.1">
         <enterprise-beans>
              <session>
                   <ejb-name>HelloWorldEJB</ejb-name>
                   <home>net.blueslate.sample.ejb.helloworld.HelloWorldRemoteHome</home>
                   <remote>net.blueslate.sample.ejb.helloworld.HelloWorldRemote</remote>
                   <local-home>net.blueslate.sample.ejb.helloworld.HelloWorldLocalHome</local-home>
                   <local>net.blueslate.sample.ejb.helloworld.HelloWorldLocal</local>
                   <ejb-class>net.blueslate.sample.ejb.helloworld.impl.HelloWorldImpl</ejb-class>
                   <session-type>Stateless</session-type>
                   <transaction-type>Container</transaction-type>
              </session>
         </enterprise-beans>
    </ejb-jar>Here is my sun-ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-0.dtd">
    <sun-ejb-jar>
         <enterprise-beans>
              <ejb>
                   <ejb-name>HelloWorldEJB</ejb-name>
                   <jndi-name>HelloWorldEJB</jndi-name>
              </ejb>
         </enterprise-beans>     
    </sun-ejb-jar>I believe the root cause is that my EJB is not bound to a name within the app server. If I browse the "JNDI tree" from the app server admin console, I can see there is a root element "ejb," but there is nothing underneath. I guess I just expected to find the name of my EJB, "HelloWorldEJB." I swear I could have read somewhere in the documentation for the app server that when you deploy an EJB, the name of the EJB as specified by the "<ejb-name>" element of the ejb-jar.xml deployment descriptor gets automatically bound within the naming server to its home object.
    At this point I would appreciate any insight anyone might have regarding this problem. I suspect there is something extra I need to do when deploying my EJB so that its name gets binded to its home object; I just don't have a clue at this point what that is.
    I should also mention that I have played with the parameter passed to 'context.lookup()' - I tried passing: "ejb/HelloWorldEJB", "HelloWorldEJB", etc - nothing seems to work. FWIW, if I just pass in "ejb", I don't receive an exception (I was glad to see this work since the JNDI tree-view from the app server admin console shows "ejb" as one of the root-elements within the naming-tree - this indicated to me I was on the right track in my diagnosis of the problem; i.e., it's probably not a connectivity or protocol issue)
    Thank you very much for your time and help.

    Nevermind folks - I got it to work. All my configuration was correct; I had other issues with the ejb-jar file that the verifier informed me of (my previous deployments were with the verifier turned-off).

  • Application deployment order with weblogic-ejb-jar.xml and jndi-name

    I have two applicatation working on Weblogic server v. 10.3.6.
    First of them creating one ejb stateless bean and creates JNDI maping for it (in weblogic-ejb-jar.xml file):
    <weblogic-enterprise-bean>
         <ejb-name>ConfigMenegerBean</ejb-name>
         <stateless-session-descriptor>
         <stateless-session-descriptor>
              <business-interface-jndi-name-map>
              <business-remote>package.ConfigurationSessionRemote</business-remote>
              <jndi-name>ConfigMeneger</jndi-name>
              </business-interface-jndi-name-map>
         </stateless-session-descriptor>
         <enable-call-by-reference>true</enable-call-by-reference>
         <jndi-name>ConfigMeneger</jndi-name>
    </weblogic-enterprise-bean>
    Second appication have to refer for this bean by JNDI using spring been lookup :
    <jee:jndi-lookup id="configManager" jndi-name="ConfigMeneger"/>
    I changed deployment order parameter for both apllication(first=100 and second=500) in order to first app start first and share bean by jndi to another application. Unfortuantelly I got an error :
    javax.naming.NameNotFoundException: Unable to resolve 'ConfigMeneger'. Resolved ''; remaining name 'ConfigMeneger'
    How can I configure deployment order that first application make jndi mapping for bean, before the second application will use it ?

    Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
    http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
    I have tried the following actions (mentionned in the other forum messages):
    - To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
    (I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
    And you can MANUALLY update the weblogic file in your JAR archive.
    1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
    project directory.
    2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
    3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
    and swap in the weblogic-ejb-jar.xml file."
    Good Luck.

  • When the ejb been bind into jndi

    Hi,
    I am using wls7.0sp1, i can see the ejbs are deployed on the server start up,
    but when the client tried to call it, the server split out exception:
    2002-11-14 11:32:10,890 ERROR [ExecuteThread: '11' for queue: 'default'] (JNDI.java:180)
    - javax.naming.NameNotFoundException: Unable to resolve 'ims.ej
    b.MyBeanHome'. Does the wls bind the ejb when it is deployed or there is extra
    step i need to configure.
    thanks

    How can list the subcontext? with the command I can see the first part "ims".
    Kumar Allamraju <[email protected]> wrote:
    >
    java weblogic.Admin -url {admin or managed server url} -username system
    -password weblogic LIST
    The above command will LIST the entries from WLS jndi tree. You may
    want to run the above command against admin & managed servers and see
    if it lists your EJB or not.
    Kumar
    Jen wrote:
    The log file shows ejb deployed. here i attched the log file. The onlything i
    can see the abnormal from the log file is the first line (actuallyis on console
    only), what that means?
    And line:
    "####<Nov 14, 2002 1:58:41 PM PST> <Info> <Cluster> <jen0> <myserver1><main>
    <kernel identity> <> <000101> <Cannot resolve ClusterAddress: :7003,:7005>".
    I have an admin server and two clustered managed server on one box.The question
    is I use nostage for both admin and managed server, the ejbs are under\applications
    directory, this might be a problem. Where the applications should gofor each
    managed server, or i only can use satge mode foe managed server?
    Thanks
    Rob Woollen <[email protected]> wrote:
    My guess is the deployment failed. Check the server logs. Were there
    any errors during deployment?
    You might also try the EJB examples. Are these working for you?
    -- Rob
    Jen wrote:
    Hi,
    I am using wls7.0sp1, i can see the ejbs are deployed on the serverstart up,
    but when the client tried to call it, the server split out exception:
    2002-11-14 11:32:10,890 ERROR [ExecuteThread: '11' for queue: 'default'](JNDI.java:180)
    - javax.naming.NameNotFoundException: Unable to resolve 'ims.ej
    b.MyBeanHome'. Does the wls bind the ejb when it is deployed or thereis extra
    step i need to configure.
    thanks------------------------------------------------------------------------
    <Nov 14, 2002 1:58:15 PM PST> <Warning> <Management> <141087> <Unrecognized
    property: system.name>
    ####<Nov 14, 2002 1:58:15 PM PST> <Info> <Logging> <jen0> <myserver1><main> <kernel identity> <> <000000> <FileLogger Opened at C:\op\.\myserver1\myserver1.log>
    ####<Nov 14, 2002 1:58:17 PM PST> <Info> <socket> <jen0> <myserver1><main> <kernel identity> <> <000406> <NTSocketMuxer was built on Jun
    24 2002 17:35:19
    ####<Nov 14, 2002 1:58:17 PM PST> <Info> <socket> <jen0> <myserver1><main> <kernel identity> <> <000408> <Allocating 2 NT reader threads>
    ####<Nov 14, 2002 1:58:31 PM PST> <Info> <Security> <jen0> <myserver1><main> <kernel identity> <> <090142> <The weblogic keystore provider
    DefaultKeyStore in realm myrealm cannot be used for trusted (root) CAs
    because its trusted (root) CA keystore was not configured.>
    ####<Nov 14, 2002 1:58:31 PM PST> <Notice> <Security> <jen0> <myserver1><main> <kernel identity> <> <090082> <Security initializing using realm
    myrealm.>
    ####<Nov 14, 2002 1:58:31 PM PST> <Notice> <WebLogicServer> <jen0><myserver1> <main> <kernel identity> <> <000328> <Starting WebLogic
    Managed Server "myserver1" for domain "op">
    ####<Nov 14, 2002 1:58:31 PM PST> <Info> <WebLogicServer> <jen0> <myserver1><main> <kernel identity> <> <000214> <WebLogic Server "myserver1" version:
    WebLogic Server 7.0 SP1 Mon Sep 9 22:46:58 PDT 2002 206753
    WebLogic XMLX Module 7.0 SP1 Mon Sep 9 22:54:41 PDT 2002 206753
    (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
    (c) 1999, 2000, 2001 BEA Systems, Inc.>
    ####<Nov 14, 2002 1:58:31 PM PST> <Info> <WebLogicServer> <jen0> <myserver1><main> <kernel identity> <> <000215> <Loaded License : C:\bea\license.bea>
    ####<Nov 14, 2002 1:58:31 PM PST> <Info> <RJVM> <jen0> <myserver1><main> <kernel identity> <> <000520> <Network Configuration
    Cluster Participant: true
    Cluster Name: mycluster
    Cluster Multicast Address: 237.0.0.1
    Cluster Multicast Port: 7777
    Cluster Multicast Interface: not configured
    Cluster Multicast TTL (max hops): 1
    Cluster Multicast Send Delay: 12 ms
    Cluster Multicast Buffer Size: 65536
    Native Socket IO Enabled: true
    Reverse DNS Allowed: false
    Network Channel: Default
    Listen Address: not configured
    Listen Port: 7003
    SSL Listen Port: 7004
    External DNS Name: not configured
    Cluster Address: :7003,:7005
    Protocol(s): T3,T3S,HTTP,HTTPS,IIOP,IIOPS
    Tunneling Enabled: false
    Outgoing Enabled: true
    Admin Traffic Only: false
    Admin Traffic OK: true
    Channel Weight: 50
    Accept Backlog: 50
    Login Timeout: 5000 ms
    Login Timeout SSL: 25000 ms
    Message Timeout HTTP: 60000 ms
    Message Timeout T3: 60000 ms
    Message Timeout IIOP: 60000 ms
    Idle Timeout IIOP: 60000 ms
    Max Message Size HTTP: 10000000
    Max Message Size T3: 10000000
    Max Message Size IIOP: 10000000
    ####<Nov 14, 2002 1:58:35 PM PST> <Info> <IIOP> <jen0> <myserver1><main> <kernel identity> <> <002014> <IIOP subsystem enabled.>
    ####<Nov 14, 2002 1:58:41 PM PST> <Info> <Cluster> <jen0> <myserver1><main> <kernel identity> <> <000101> <Cannot resolve ClusterAddress:
    :7003,:7005>
    ####<Nov 14, 2002 1:58:42 PM PST> <Info> <XML> <jen0> <myserver1> <main><kernel identity> <> <130036> <Initializing XMLRegistry.>
    ####<Nov 14, 2002 1:58:44 PM PST> <Info> <JDBC> <jen0> <myserver1><main> <kernel identity> <> <001007> <INITIALIZING DONE issued.>
    ####<Nov 14, 2002 1:58:44 PM PST> <Info> <Connector> <jen0> <myserver1><main> <kernel identity> <> <190000> <Initializing J2EE Connector Service>
    ####<Nov 14, 2002 1:58:44 PM PST> <Info> <Connector> <jen0> <myserver1><main> <kernel identity> <> <190001> <J2EE Connector Service initialized
    successfully>
    ####<Nov 14, 2002 1:58:46 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040090> <Deployed 4 default connection factories.>
    ####<Nov 14, 2002 1:58:46 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040305> <JMS service is initialized and in the
    standby mode.>
    ####<Nov 14, 2002 1:58:46 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101128> <Initializing HTTP services.>
    ####<Nov 14, 2002 1:58:46 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101133> <Initializing WEB server myserver1>
    ####<Nov 14, 2002 1:58:47 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101052> <[HTTP myserver1] Initialized>
    ####<Nov 14, 2002 1:58:47 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101135> <myserver1 is the default web server>
    ####<Nov 14, 2002 1:58:47 PM PST> <Info> <J2EE> <jen0> <myserver1><main> <kernel identity> <> <160037> <J2EE service initializing>
    ####<Nov 14, 2002 1:58:50 PM PST> <Info> <Deployer> <jen0> <myserver1><main> <kernel identity> <> <149207> <The Deployment Slave is initializing>
    ####<Nov 14, 2002 1:58:51 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101201> <uddi:uddi loading descriptor>
    ####<Nov 14, 2002 1:58:52 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101059> <[HTTP] Loading uddi from WAR file:
    .\myserver1\.internal\uddi.war>
    ####<Nov 14, 2002 1:58:53 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101202> <uddi:uddi preparing>
    ####<Nov 14, 2002 1:58:55 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101201> <wl_management_internal1:wl_management_internal1
    loading descriptor>
    ####<Nov 14, 2002 1:58:55 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101059> <[HTTP] Loading wl_management_internal1
    from WAR file: .\myserver1\.internal\wl_management_internal1.war>
    ####<Nov 14, 2002 1:58:55 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101202> <wl_management_internal1:wl_management_internal1
    preparing>
    ####<Nov 14, 2002 1:58:56 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101201> <uddiexplorer:uddiexplorer loading
    descriptor>
    ####<Nov 14, 2002 1:58:56 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101059> <[HTTP] Loading uddiexplorer from
    WAR file: .\myserver1\.internal\uddiexplorer.war>
    ####<Nov 14, 2002 1:58:56 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101202> <uddiexplorer:uddiexplorer preparing>
    ####<Nov 14, 2002 1:58:59 PM PST> <Info> <EJB> <jen0> <myserver1> <main><kernel identity> <> <010008> <EJB Deploying file: Case.jar>
    ####<Nov 14, 2002 1:58:59 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Case cannot be
    redeployed while the server is running. com.ims.ejb.CaseBean is located
    in the server's classpath.>
    ####<Nov 14, 2002 1:58:59 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Caser cannot be
    redeployed while the server is running. com.ims.ejb.CaseBean is located
    in the server's classpath.>
    ####<Nov 14, 2002 1:58:59 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Case cannot be
    redeployed while the server is running. com.ims.ejb.CaseBean is located
    in the server's classpath.>
    ####<Nov 14, 2002 1:59:00 PM PST> <Info> <EJB> <jen0> <myserver1> <main><kernel identity> <> <010008> <EJB Deploying file: Submit.jar>
    ####<Nov 14, 2002 1:59:00 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Submit cannot
    be redeployed while the server is running. com.ims.ejb.SubmitBean is
    located in the server's classpath.>
    ####<Nov 14, 2002 1:59:00 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Submit cannot
    be redeployed while the server is running. com.ims.ejb.SubmitBean is
    located in the server's classpath.>
    ####<Nov 14, 2002 1:59:00 PM PST> <Warning> <EJB> <jen0> <myserver1><main> <kernel identity> <> <010001> <EJB Deployment: Submit cannot
    be redeployed while the server is running. com.ims.ejb.SubmitBean is
    located in the server's classpath.>
    ####<Nov 14, 2002 1:59:07 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101201> <myapp:myapp loading descriptor>
    ####<Nov 14, 2002 1:59:07 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101060> <[HTTP] Loading "HTTP" from directory:
    "C:\op\.\applications\myapp">
    ####<Nov 14, 2002 1:59:08 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101202> <myapp:myapp preparing>
    ####<Nov 14, 2002 1:59:14 PM PST> <Info> <DRS> <jen0> <myserver1> <main><kernel identity> <> <002504> <Slave for DataIdentifier DataIdentifierID:
    1 registered with DRS with version 0>
    ####<Nov 14, 2002 1:59:16 PM PST> <Info> <Deployer> <jen0> <myserver1><main> <kernel identity> <> <149215> <The Slave Deployer did not receive
    an initial update after 2,000 milliseconds.>
    ####<Nov 14, 2002 1:59:16 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101206> <uddi:uddi activating>
    ####<Nov 14, 2002 1:59:17 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101209> <uddi:uddi ready>
    ####<Nov 14, 2002 1:59:17 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101208> <uddi:uddi starting>
    ####<Nov 14, 2002 1:59:17 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101206> <wl_management_internal1:wl_management_internal1
    activating>
    ####<Nov 14, 2002 1:59:17 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101209> <wl_management_internal1:wl_management_internal1
    ready>
    ####<Nov 14, 2002 1:59:18 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101208> <wl_management_internal1:wl_management_internal1
    starting>
    ####<Nov 14, 2002 1:59:18 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101206> <uddiexplorer:uddiexplorer activating>
    ####<Nov 14, 2002 1:59:18 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101209> <uddiexplorer:uddiexplorer ready>
    ####<Nov 14, 2002 1:59:18 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101208> <uddiexplorer:uddiexplorer starting>
    ####<Nov 14, 2002 1:59:18 PM PST> <Info> <Deployer> <jen0> <myserver1><main> <kernel identity> <> <149208> <The Deployment Slave is initialized>
    ####<Nov 14, 2002 1:59:18 PM PST> <Notice> <Cluster> <jen0> <myserver1><main> <kernel identity> <> <000138> <Listening for announcements from
    cluster mycluster on 237.0.0.1:7777>
    ####<Nov 14, 2002 1:59:18 PM PST> <Notice> <Cluster> <jen0> <myserver1><main> <kernel identity> <> <000133> <Waiting to synchronize with other
    running members of mycluster>
    ####<Nov 14, 2002 1:59:48 PM PST> <Notice> <Cluster> <jen0> <myserver1><main> <kernel identity> <> <000134> <Discovered and synchronized with
    0 other running members of mycluster>
    ####<Nov 14, 2002 1:59:49 PM PST> <Info> <JTA> <jen0> <myserver1> <main><kernel identity> <> <110441> <Opening transaction log with driver version
    "j1.0" and synchronous write policy "Cache-Flush". For information on
    synchronous write policies, refer to the weblogic.management.configuration.ServerMBean
    javadoc or console on-line help.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JDBC> <jen0> <myserver1><main> <kernel identity> <> <001007> <RESUMING ... issued.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JDBC> <jen0> <myserver1><main> <kernel identity> <> <001007> <RESUMING DONE issued.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040108> <User connection factory "MessageDrivenBeanConnectionFactory"
    is started.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040108> <User connection factory "QueueConnectionFactory"
    is started.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040108> <User connection factory "TopicConnectionFactory"
    is started.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040108> <User connection factory "DefaultConnectionFactory"
    is started.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <JMS> <jen0> <myserver1> <main><kernel identity> <> <040306> <JMS service is active now.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101129> <Initializing Web services.>
    ####<Nov 14, 2002 1:59:50 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101238> <HTTP log rotation is size based
    for the webserver: myserver1>
    ####<Nov 14, 2002 1:59:51 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101051> <[HTTP myserver1] started>
    ####<Nov 14, 2002 1:59:51 PM PST> <Info> <Deployer> <jen0> <myserver1><main> <kernel identity> <> <149209> <The Deployment Slave is resuming>
    ####<Nov 14, 2002 1:59:51 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101133> <Initializing WEB server myserver1>
    ####<Nov 14, 2002 1:59:51 PM PST> <Info> <EJB> <jen0> <myserver1> <main><kernel identity> <> <010009> <EJB Deployed EJB with JNDI name ims.ejb.CaseHome..>
    ####<Nov 14, 2002 1:59:52 PM PST> <Info> <EJB> <jen0> <myserver1> <main><kernel identity> <> <010009> <EJB Deployed EJB with JNDI name ims.ejb.SubmitHome.>
    ####<Nov 14, 2002 1:59:58 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101206> <myapp:myapp activating>
    ####<Nov 14, 2002 1:59:59 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101209> <myapp:myapp ready>
    ####<Nov 14, 2002 1:59:59 PM PST> <Info> <HTTP> <jen0> <myserver1><main> <kernel identity> <> <101208> <myapp:myapp starting>
    ####<Nov 14, 2002 2:00:02 PM PST> <Info> <Deployer> <jen0> <myserver1><main> <kernel identity> <> <149210> <The Deployment Slave is resumed>
    >

  • How to bound a JNDI reference to MySQL driver?

    Hi.
    Hi.
    I am trying to write a simple J2EE application that would use Entety EJB with bean persisatance. I have downloaded driver from the www.mysql.org, copied it to the lib/system directory and modified J2EE_CLASSPATH in bin/userconfig.bat. I am using reference implementation server and with deploytool in �tools/serverconfiguration/datasourses/standard� I am specifying driver: org.gjt.mm.mysql.Driver or com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource and in datasourses in JNDI Name I write �jdbc/mydb� and in JDBC URL �jdbc:mysql://localhost:3306/this�, problem comes up when I try to reference �jdbc/mydb� from an entity bean, during deployment process of application it says that it is not bound
    Binding name:`java:comp/env/jdbc\persondb`
    Warning: Reference reference java:comp/env/jdbc\persondb is using a JNDI name that is not bound: jdbc\mydb
    I do not get it, what I am doing wrong? Please help me to find out how to bind a JNDI name to MySQL

    Hi! I had the same problem, too. I�m Brazilian and I�ve been learning the English language yet, but I�ll try to describe how to configure J2EE with MySQL.
    I am using MySQL version 4.1.7 with J2EE version 1.3 on Windows XP Professional. The driver version of MySQL is 3.0.16.
    You have to configure the following two files:
    - <J2EE_HOME>\bin\setenv.bat
    - <J2EE_HOME>\config\resource.properties
    Do the following steps:
    1) Copy the JAR file of MySQL driver (mysql-connector-java-3.0.16-ga-bin.jar) to <J2EE_HOME>\lib directory.
    2) In <J2EE_HOME>\bin directory open the setenv.bat file and analize the code. It is not hard to understand the code, it is just the classpath configuration of J2EE. After understand it, add a reference of MySQL driver (mysql-connector-java-3.0.16-ga-bin.jar), that was copied to <J2EE_HOME>\lib directory.
    3) Run the <J2EE_HOME>\bin\j2eeadmin.bat to configure the resource.properties file.There are two command lines to be executed, as below:
    - j2eeadmin.bat -addJdbcDriver <CLASS NAME OF THE DRIVER>
    - j2eeadmin.bat -addJdbcDatasource <JNDI NAME> <URL>
    For example:
    - j2eeadmin.bat -addJdbcDriver "com.mysql.jdbc.Driver"
    - j2eeadmin.bat -addJdbcDatasource "jdbc/mysql/test" "jdbc:mysql://localhost/test?user=username&password=pass"
    4) After run j2eeadmin.bat, the resource.properties file will be modified. But when I did it and when I executed the verbose command to start J2EE, some error messages was exhibited. So I decided to open the resource.properties file and I noticed that the character "\" was added erroneously in a lot of places of the code. It did not seem correct, so I decided to remove these characters replacing them. I was right! After I did it, I run verbose again and no more message error ocurred. I think it is a bug of J2EE.
    Finish! I modified the datasource JNDI to access MySQL and then I run my EAR application. No problems occurred. My application is running succesfully.
    Good luck!

  • Tell how to deployee the EJB 3.0 program in JBoss(netbean5.5 IDE)

    my error when i compile
    ===============================================================================
    JBoss Bootstrap Environment
    JBOSS_HOME: C:\Program Files\jboss-4.0.5.GA\bin\\..
    JAVA: C:\Program Files\Java\jdk1.5.0_11\bin\java
    JAVA_OPTS: -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts="localhost|127.0.0.1|abc" -Dhttps.proxyHost= -Dhttps.proxyPort= -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
    CLASSPATH: C:\Program Files\Java\jdk1.5.0_11\lib\tools.jar;C:\Program Files\jboss-4.0.5.GA\bin\\run.jar
    ===============================================================================
    10:33:12,406 INFO [Server] Starting JBoss (MX MicroKernel)...
    10:33:12,406 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
    10:33:12,406 INFO [Server] Home Dir: C:\Program Files\jboss-4.0.5.GA
    10:33:12,406 INFO [Server] Home URL: file:/C:/Program Files/jboss-4.0.5.GA/
    10:33:12,406 INFO [Server] Patch URL: null
    10:33:12,406 INFO [Server] Server Name: Orchids
    10:33:12,406 INFO [Server] Server Home Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids
    10:33:12,406 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/
    10:33:12,468 INFO [Server] Server Log Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids\log
    10:33:12,468 INFO [Server] Server Temp Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids\tmp
    10:33:12,468 INFO [Server] Root Deployment Filename: jboss-service.xml
    10:33:13,593 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
    10:33:13,593 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc.
    10:33:13,593 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
    10:33:15,796 INFO [Server] Core system initialized
    10:33:25,250 INFO [WebService] Using RMI server codebase: http://abc:8083/
    10:33:25,500 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
    10:33:35,703 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://192.168.1.22:3873/]
    10:33:49,796 INFO [ServiceEndpointManager] WebServices: jbossws-1.0.3.SP1 (date=200609291417)
    10:33:52,031 INFO [SnmpAgentService] SNMP agent going active
    10:33:54,312 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000000E8000102000000000D3139322E3136382E312E323200000DC8000000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000006000000000000000010000000000000024000000200000007E00000000000000010000000D3139322E3136382E312E323200000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
    10:33:54,812 INFO [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E466163746F72794578743A312E30000000000200000000000000E8000102000000000D3139322E3136382E312E323200000DC8000000144A426F73732F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000006000000000000000010000000000000024000000200000007E00000000000000010000000D3139322E3136382E312E323200000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
    10:33:56,312 INFO [Embedded] Catalina naming disabled
    10:33:56,406 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
    10:33:56,406 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
    10:33:57,796 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
    10:33:57,796 INFO [Catalina] Initialization processed in 1390 ms
    10:33:57,796 INFO [StandardService] Starting service jboss.web
    10:33:57,812 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.20
    10:33:57,875 INFO [StandardHost] XML validation disabled
    10:33:57,906 INFO [Catalina] Server startup in 110 ms
    10:33:58,281 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
    10:33:59,312 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
    10:34:00,906 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
    10:34:01,218 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp61906jbossws-context-exp.war/
    10:34:02,578 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
    10:34:05,984 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
    10:34:07,968 INFO [MailService] Mail Service bound to java:/Mail
    10:34:08,453 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
    10:34:08,671 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
    10:34:08,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
    10:34:08,937 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
    10:34:09,109 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
    10:34:09,187 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
    10:34:09,312 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
    10:34:09,359 INFO [QuartzResourceAdapter] start quartz!!!
    10:34:09,468 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
    10:34:09,578 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
    10:34:09,578 INFO [RAMJobStore] RAMJobStore initialized.
    10:34:09,593 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
    10:34:09,718 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
    10:34:09,718 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
    10:34:11,812 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
    10:34:12,359 INFO [A] Bound to JNDI name: queue/A
    10:34:12,359 INFO Bound to JNDI name: queue/B
    10:34:12,375 INFO [C] Bound to JNDI name: queue/C
    10:34:12,375 INFO [D] Bound to JNDI name: queue/D
    10:34:12,375 INFO [ex] Bound to JNDI name: queue/ex
    10:34:12,406 INFO [testTopic] Bound to JNDI name: topic/testTopic
    10:34:12,406 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
    10:34:12,406 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
    10:34:12,406 INFO [testQueue] Bound to JNDI name: queue/testQueue
    10:34:12,921 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
    10:34:13,000 INFO [DLQ] Bound to JNDI name: queue/DLQ
    10:34:14,734 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ven' to JNDI name 'java:ven'
    10:34:14,796 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ven1' to JNDI name 'java:ven1'
    10:34:14,859 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=newJNDI' to JNDI name 'java:newJNDI'
    10:34:14,906 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=mySqlDS' to JNDI name 'java:mySqlDS'
    10:34:14,937 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=venkat' to JNDI name 'java:venkat'
    10:34:15,687 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
    10:34:15,750 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/deploy/mysql-ds.xml
    org.jboss.deployment.DeploymentException: Could not parse dd; - nested throwable: (org.xml.sax.SAXParseException: The element type "local-tx-datasource" must be terminated by the matching end-tag "</local-tx-datasource>".)
    at org.jboss.deployment.XSLSubDeployer.findDd(XSLSubDeployer.java:231)
    at org.jboss.deployment.XSLSubDeployer.init(XSLSubDeployer.java:161)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:490)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: org.xml.sax.SAXParseException: The element type "local-tx-datasource" must be terminated by the matching end-tag "</local-tx-datasource>".
    at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
    at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
    at org.jboss.deployment.XSLSubDeployer.findDd(XSLSubDeployer.java:227)
    ... 68 more
    10:34:16,812 INFO [Ejb3Deployment] EJB3 deployment time took: 859
    10:34:16,828 INFO [JmxKernelAbstraction] installing MBean: persistence.units:jar=EJB3.jar,unitName=EJB3PU with dependencies:
    10:34:16,828 INFO [JmxKernelAbstraction]      jboss.jca:name=ven1,service=DataSourceBinding
    10:34:17,031 WARN [ServiceController] Problem starting service persistence.units:jar=EJB3.jar,unitName=EJB3PU
    javax.naming.NameNotFoundException: ven1 not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
    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.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy56.start(Unknown Source)
    at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96)
    at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:467)
    at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317)
    at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy28.start(Unknown Source)
    at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
    at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
    at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
    at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
    at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy29.start(Unknown Source)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:490)
    at java.lang.Thread.run(Thread.java:595)
    10:34:18,062 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=EJB3.jar,name=TestFacade,service=EJB3 with dependencies:
    10:34:18,062 INFO [JmxKernelAbstraction]      persistence.units:jar=EJB3.jar,unitName=EJB3PU
    10:34:18,062 INFO [EJB3Deployer] Deployed: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/deploy/EJB3.jar
    10:34:18,296 INFO [Ejb3Deployment] EJB3 deployment time took: 46
    10:34:18,296 INFO [JmxKernelAbstraction] installing MBean: persistence.units:jar=EJBModule1.jar,unitName=EJBModule1PU with dependencies:
    10:34:18,437 INFO [JmxKernelAbstraction]      jboss.jca:name=newJNDI,service=DataSourceBinding
    10:34:18,453 WARN [ServiceController] Problem starting service persistence.units:jar=EJBModule1.jar,unitName=EJBModule1PU
    javax.naming.NameNotFoundException: newJNDI not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
    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.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:

    my error when i compile
    ===============================================================================
    JBoss Bootstrap Environment
    JBOSS_HOME: C:\Program Files\jboss-4.0.5.GA\bin\\..
    JAVA: C:\Program Files\Java\jdk1.5.0_11\bin\java
    JAVA_OPTS: -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts="localhost|127.0.0.1|abc" -Dhttps.proxyHost= -Dhttps.proxyPort= -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
    CLASSPATH: C:\Program Files\Java\jdk1.5.0_11\lib\tools.jar;C:\Program Files\jboss-4.0.5.GA\bin\\run.jar
    ===============================================================================
    10:33:12,406 INFO [Server] Starting JBoss (MX MicroKernel)...
    10:33:12,406 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
    10:33:12,406 INFO [Server] Home Dir: C:\Program Files\jboss-4.0.5.GA
    10:33:12,406 INFO [Server] Home URL: file:/C:/Program Files/jboss-4.0.5.GA/
    10:33:12,406 INFO [Server] Patch URL: null
    10:33:12,406 INFO [Server] Server Name: Orchids
    10:33:12,406 INFO [Server] Server Home Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids
    10:33:12,406 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/
    10:33:12,468 INFO [Server] Server Log Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids\log
    10:33:12,468 INFO [Server] Server Temp Dir: C:\Program Files\jboss-4.0.5.GA\server\Orchids\tmp
    10:33:12,468 INFO [Server] Root Deployment Filename: jboss-service.xml
    10:33:13,593 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
    10:33:13,593 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03,Sun Microsystems Inc.
    10:33:13,593 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
    10:33:15,796 INFO [Server] Core system initialized
    10:33:25,250 INFO [WebService] Using RMI server codebase: http://abc:8083/
    10:33:25,500 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
    10:33:35,703 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://192.168.1.22:3873/]
    10:33:49,796 INFO [ServiceEndpointManager] WebServices: jbossws-1.0.3.SP1 (date=200609291417)
    10:33:52,031 INFO [SnmpAgentService] SNMP agent going active
    10:33:54,312 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E3000000000000200000000000000E8000102000000000D3139322E3136382E312E323200000DC8000000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000006000000000000000010000000000000024000000200000007E00000000000000010000000D3139322E3136382E312E323200000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
    10:33:54,812 INFO [CorbaTransactionService] TransactionFactory: [IOR:000000000000003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E466163746F72794578743A312E30000000000200000000000000E8000102000000000D3139322E3136382E312E323200000DC8000000144A426F73732F5472616E73616374696F6E732F46000000050000000000000008000000004A414300000000010000001C00000000000100010000000105010001000101090000000105010001000000210000006000000000000000010000000000000024000000200000007E00000000000000010000000D3139322E3136382E312E323200000DC900400000000000000000001004010008060667810201010100000000000000000000000000000000000000000000002000000004000000000000001F0000000400000003000000010000002000000000000000020000002000000004000000000000001F0000000400000003]
    10:33:56,312 INFO [Embedded] Catalina naming disabled
    10:33:56,406 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
    10:33:56,406 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
    10:33:57,796 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
    10:33:57,796 INFO [Catalina] Initialization processed in 1390 ms
    10:33:57,796 INFO [StandardService] Starting service jboss.web
    10:33:57,812 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.20
    10:33:57,875 INFO [StandardHost] XML validation disabled
    10:33:57,906 INFO [Catalina] Server startup in 110 ms
    10:33:58,281 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
    10:33:59,312 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
    10:34:00,906 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
    10:34:01,218 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp61906jbossws-context-exp.war/
    10:34:02,578 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
    10:34:05,984 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
    10:34:07,968 INFO [MailService] Mail Service bound to java:/Mail
    10:34:08,453 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
    10:34:08,671 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
    10:34:08,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
    10:34:08,937 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
    10:34:09,109 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
    10:34:09,187 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
    10:34:09,312 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
    10:34:09,359 INFO [QuartzResourceAdapter] start quartz!!!
    10:34:09,468 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
    10:34:09,578 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
    10:34:09,578 INFO [RAMJobStore] RAMJobStore initialized.
    10:34:09,593 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
    10:34:09,718 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
    10:34:09,718 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
    10:34:11,812 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
    10:34:12,359 INFO [A] Bound to JNDI name: queue/A
    10:34:12,359 INFO Bound to JNDI name: queue/B
    10:34:12,375 INFO [C] Bound to JNDI name: queue/C
    10:34:12,375 INFO [D] Bound to JNDI name: queue/D
    10:34:12,375 INFO [ex] Bound to JNDI name: queue/ex
    10:34:12,406 INFO [testTopic] Bound to JNDI name: topic/testTopic
    10:34:12,406 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
    10:34:12,406 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
    10:34:12,406 INFO [testQueue] Bound to JNDI name: queue/testQueue
    10:34:12,921 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
    10:34:13,000 INFO [DLQ] Bound to JNDI name: queue/DLQ
    10:34:14,734 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ven' to JNDI name 'java:ven'
    10:34:14,796 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=ven1' to JNDI name 'java:ven1'
    10:34:14,859 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=newJNDI' to JNDI name 'java:newJNDI'
    10:34:14,906 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=mySqlDS' to JNDI name 'java:mySqlDS'
    10:34:14,937 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=venkat' to JNDI name 'java:venkat'
    10:34:15,687 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
    10:34:15,750 ERROR [MainDeployer] Could not initialise deployment: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/deploy/mysql-ds.xml
    org.jboss.deployment.DeploymentException: Could not parse dd; - nested throwable: (org.xml.sax.SAXParseException: The element type "local-tx-datasource" must be terminated by the matching end-tag "</local-tx-datasource>".)
    at org.jboss.deployment.XSLSubDeployer.findDd(XSLSubDeployer.java:231)
    at org.jboss.deployment.XSLSubDeployer.init(XSLSubDeployer.java:161)
    at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:490)
    at java.lang.Thread.run(Thread.java:595)
    Caused by: org.xml.sax.SAXParseException: The element type "local-tx-datasource" must be terminated by the matching end-tag "</local-tx-datasource>".
    at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
    at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
    at org.jboss.deployment.XSLSubDeployer.findDd(XSLSubDeployer.java:227)
    ... 68 more
    10:34:16,812 INFO [Ejb3Deployment] EJB3 deployment time took: 859
    10:34:16,828 INFO [JmxKernelAbstraction] installing MBean: persistence.units:jar=EJB3.jar,unitName=EJB3PU with dependencies:
    10:34:16,828 INFO [JmxKernelAbstraction]      jboss.jca:name=ven1,service=DataSourceBinding
    10:34:17,031 WARN [ServiceController] Problem starting service persistence.units:jar=EJB3.jar,unitName=EJB3PU
    javax.naming.NameNotFoundException: ven1 not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
    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.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy56.start(Unknown Source)
    at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96)
    at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:467)
    at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317)
    at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy28.start(Unknown Source)
    at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
    at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
    at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92)
    at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
    at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy29.start(Unknown Source)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy8.deploy(Unknown Source)
    at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
    at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
    at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:490)
    at java.lang.Thread.run(Thread.java:595)
    10:34:18,062 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:jar=EJB3.jar,name=TestFacade,service=EJB3 with dependencies:
    10:34:18,062 INFO [JmxKernelAbstraction]      persistence.units:jar=EJB3.jar,unitName=EJB3PU
    10:34:18,062 INFO [EJB3Deployer] Deployed: file:/C:/Program Files/jboss-4.0.5.GA/server/Orchids/deploy/EJB3.jar
    10:34:18,296 INFO [Ejb3Deployment] EJB3 deployment time took: 46
    10:34:18,296 INFO [JmxKernelAbstraction] installing MBean: persistence.units:jar=EJBModule1.jar,unitName=EJBModule1PU with dependencies:
    10:34:18,437 INFO [JmxKernelAbstraction]      jboss.jca:name=newJNDI,service=DataSourceBinding
    10:34:18,453 WARN [ServiceController] Problem starting service persistence.units:jar=EJBModule1.jar,unitName=EJBModule1PU
    javax.naming.NameNotFoundException: newJNDI not bound
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
    at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
    at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
    at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
    at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
    at javax.naming.InitialContext.lookup(InitialContext.java:351)
    at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
    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.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:

  • How to externalize JNDI name (setting JNDI name dynamically)

    Hi,
    In adapters such as ftp, database, we have to specify the jndi name. This binds the adapter to a particular jndi name. While this is certainly better than binding the adapter directly to the physical resource, I was wondering if it is possible to have even more flexibililty- setting the jndi name dynamically.
    Basically my requirement is to develop a web service that reads a file from a FTP location. I know I can externalize the filename and directory, but I am wondering how to set the ftp location dynamically.
    http://darwin-it.blogspot.com/2008/03/configuration-of-ftp-synchronous-get.html provides the answer if I wish to set the hostname, portname, user id and password.
    But I want to setup the FTP adapter in AS, and then use that JNDI name in my service. Is it possible...I am using SOA 10.1.3.3
    Regards,
    Amit

    I was able to access the files. Thanks.
    The example shows how to use the header properties in file adapter, and it sets the filename and directory elements dynamically....this I already knew.
    <copy>
    <from variable="inputVariable" part="payload"
    query="/client:PassFilePropertiesDynamicallyProcessRequest/client:FileName"/>
    <to variable="outHeader" part="outboundHeader"
    query="/ns2:OutboundFileHeaderType/ns2:fileName"/>
    </copy>
    <copy>
    <from variable="inputVariable" part="payload"
    query="/client:PassFilePropertiesDynamicallyProcessRequest/client:Location"/>
    <to variable="outHeader" part="outboundHeader"
    query="/ns2:OutboundFileHeaderType/ns2:directory"/>
    </copy>
    What I want to know is, what is the element to be added in the ftpAdapterOutboundHeader.wsdl that denotes the FTP Location (which is different from the directory).
    I guess your next update which would talk about FTP adapter, would clarify things.
    Thanks for your replies,
    Amit

  • Conflicts binding EJB to JNDI names

    Hi everyone, I'm having a problem to run an application client due to JNDI errors during the binding of EJB modules.
    I'm using NetBeans 5.5 and Sun Java Application Server 9 PE.
    the server log shows these messages:
    SEVERE| Exception in creating EJB container [javax.naming.NameAlreadyBoundException: Use rebind to override]
    SEVERE| appId=+CorpTour+ moduleName=+Tour+_jar ejbName=+reservationBean+
    SEVERE| Jndi name conflict found in [+CorpTour+]. Jndi name [+reservationRemote+] for bean [+reservationBean+] is already in use.
    SEVERE| Naming exception while creating EJB container: javax.naming.NameAlreadyBoundException: Use rebind to override
    here the components are:
    Enterprise application: CorpTour
    EJB: Tour
    Session Bean: reservationBean
    Session Bean remote interface: reservationRemote
    I created all the EJB calls using the IDE assitant so I don't know what's wrong.
    Another thing is that the IDE created the application-client.xml file but not the ejb-jar file.
    I would reeeeally appreciate any help on this problem. Thanks in advance

    What version of WLS are you using?
    Bart Jenkins, Globeflow SA
    "Rafal Mantiuk" <[email protected]> wrote in message
    news:[email protected]..
    Can I do a thing like this:
    -) I deploy an EJB on a server A.
    -) I bind the EJB that is deployed on the server A to jndi on a server
    B. The EJB is not deployed on server B.
    -) Web client that runs on server B can lookup the EJB in its local
    jndi. However all calls go to the server A.
    Server A and B are not in the cluster.
    Rafal

  • Setting EJB JNDI name

    Hi all !
    I have one EJB application which needs to be run in two different containers (GlassFish
    and Weblogic)
    One issue I have faced is the JNDI binding. When I deploy my EJB, the jndiBinding of @RemoteBinding
    is not used:
    @Stateless
    @RemoteBinding(jndiBinding="UserManagerEJB/remote")
    public class UserManagerBean implements UserManagerEJB{
    rather the EJB is bound at JAR_NAME_jarUserManagerBean_UserManagerEJB
    is it possible to bind the EJB at "UserManagerEJB/remote" so that it's portable between the two App. servers?
    thanks
    Frank

    I could not find RemoteBinding in the following doc :-
    Link :[http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ejb30/annotations.html]
    I wonder whether this would work. I am not sure whether this is implemented.

  • Deployed EJB Not Bound

    I deplyed a simple EJB on S17AS. The server.log tells me it is deployed successful.
    CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1017ca1
    CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@9d5793
    LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
    The relevant simpleEjb.jar_verified.txt is as follows
         Test Name : tests.ejb.ias.ASEjbJndiName
         Test Assertion :
         Test Description : PASSED [AS-EJB ejb] : jndi-name is simpleHome
    However, the server log did not indicate the EJB is bound even if I set the log level to finest.
    Therefore when I tried to access it, I get the following error
    Exception in thread "main" javax.naming.NameNotFoundException: No object bound f
    or java:comp/env/ejb/simpleHome
    at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.j
    ava:116)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at HelloClient.main(HelloClient.java:61)
    The client code is as follows
    String JNDIName = "java:comp/env/ejb/simpleHome";
    myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(
                   initContext.lookup(JNDIName), GreeterDBHome.class);
    The sun-ejb-jar.xml is as follows
    <?xml version="1.0" encoding="UTF-8"?>
    <!--
    Copyright 2002 Sun Microsystems, Inc. All rights reserved.
    -->
    <!DOCTYPE sun-ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN' 'http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd'>
    <sun-ejb-jar>
    <enterprise-beans>
    <name>simpleEjb.jar</name>
    <ejb>
    <ejb-name>simpleEJB</ejb-name>
    <jndi-name>simpleHome</jndi-name>
    <is-read-only-bean>false</is-read-only-bean>
                   <bean-pool>
                        <steady-pool-size>2</steady-pool-size>
                        <resize-quantity>5</resize-quantity>
                        <max-pool-size>20</max-pool-size>
                        <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
                   </bean-pool>
    </ejb>
    </enterprise-beans>
    </sun-ejb-jar>
    I tried to use lookup for both "java:comp/env/ejb/simpleHome" and "java:comp/env/simpleHome". None succeed.
    Does anyone know why the ejb is deployed successful but not bound?
    Sha

    Hi, Parsuram,
    I did restart the server and the error is the same.
    Here is the sample code. I did not change them. Only the names in deployment descriptors are modified.
    Below is the info.
    *************************Remote Interface
    Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
    package samples.jdbc.simple.ejb;
    * Remote interface for the GreeterDBEJB. The remote interface defines all possible
    * business methods for the bean. These are the methods going to be invoked remotely
    * by the servlets, once they have a reference to the remote interface.
    * Servlets generally take the help of JNDI to lookup the bean's home interface and
    * then use the home interface to obtain references to the bean's remote interface.
    public interface GreeterDB extends javax.ejb.EJBObject {
    * Returns the greeting String such as "Good morning, John"
         * @return the greeting String
    public String getGreeting() throws java.rmi.RemoteException;
    *************************Home Interface
    Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
    package samples.jdbc.simple.ejb;
    * Home interface for the GreeterDB EJB. Clients generally use home interface
    * to obtain references to the bean's remote interface.
    public interface GreeterDBHome extends javax.ejb.EJBHome {
    * Gets a reference to the remote interface to the GreeterDBBean.
         * @exception throws CreateException and RemoteException.
    public GreeterDB create() throws java.rmi.RemoteException, javax.ejb.CreateException;
    *************************Bean Class
    Copyright � 2002 Sun Microsystems, Inc. All rights reserved.
    package samples.jdbc.simple.ejb;
    import java.util.*;
    import java.io.*;
    * A simple stateless session bean which generates the greeting string for jdbc-simple
    * application. This bean implements the business method as declared by the remote interface.
    public class GreeterDBBean implements javax.ejb.SessionBean {
    private javax.ejb.SessionContext m_ctx = null;
    * Sets the session context. Required by EJB spec.
         * @param ctx A SessionContext object.
    public void setSessionContext(javax.ejb.SessionContext ctx) {
    m_ctx = ctx;
    * Creates a bean. Required by EJB spec.
    public void ejbCreate() {
    System.out.println("ejbCreate() on obj " + this);
    * Removes a bean. Required by EJB spec.
    public void ejbRemove() {
    System.out.println("ejbRemove() on obj " + this);
    * Loads the state of the bean from secondary storage. Required by EJB spec.
    public void ejbActivate() {
    System.out.println("ejbActivate() on obj " + this);
    * Keeps the state of the bean to secondary storage. Required by EJB spec.
    public void ejbPassivate() {
    System.out.println("ejbPassivate() on obj " + this);
    * Required by EJB spec.
    public void GreeterDBBean() {
    * Returns the Greeting String based on the time
    * @return the Greeting String.
    public String getGreeting() throws java.rmi.RemoteException {
    System.out.println("GreeterDB EJB is determining message...");
    String message = null;
    Calendar calendar = new GregorianCalendar();
    int currentHour = calendar.get(Calendar.HOUR_OF_DAY);
    if(currentHour < 12) message = "morning";
    else {
    if( (currentHour >= 12) &&
    (calendar.get(Calendar.HOUR_OF_DAY) < 18)) message = "afternoon";
    else message = "evening";
    System.out.println("- Message determined successfully");
    return message;
    ************************ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!--
    Copyright 2002 Sun Microsystems, Inc. All rights reserved.
    -->
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <display-name>simple</display-name>
    <ejb-name>simpleEJB</ejb-name>
    <home>samples.jdbc.simple.ejb.GreeterDBHome</home>
    <remote>samples.jdbc.simple.ejb.GreeterDB</remote>
    <ejb-class>samples.jdbc.simple.ejb.GreeterDBBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Bean</transaction-type>
    </session>
    </enterprise-beans>
    </ejb-jar>
    ************************sun-ejb-jar.xml
    <sun-ejb-jar>
    <enterprise-beans>
    <name>simpleEjb.jar</name>
    <ejb>
    <ejb-name>simpleEJB</ejb-name>
    <jndi-name>ejb/simpleHome</jndi-name>
    <is-read-only-bean>false</is-read-only-bean>
                   <bean-pool>
                        <steady-pool-size>2</steady-pool-size>
                        <resize-quantity>5</resize-quantity>
                        <max-pool-size>20</max-pool-size>
                        <pool-idle-timeout-in-seconds>3600</pool-idle-timeout-in-seconds>
                   </bean-pool>
    </ejb>
    </enterprise-beans>
    </sun-ejb-jar>
    ************************Assemble Info
    C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar cvf simpleEjb.jar *
    added manifest
    ignoring entry META-INF/
    adding: META-INF/ejb-jar.xml(in = 710) (out= 350)(deflated 50%)
    adding: META-INF/sun-ejb-jar.xml(in = 803) (out= 424)(deflated 47%)
    adding: samples/(in = 0) (out= 0)(stored 0%)
    adding: samples/jdbc/(in = 0) (out= 0)(stored 0%)
    adding: samples/jdbc/simple/(in = 0) (out= 0)(stored 0%)
    adding: samples/jdbc/simple/ejb/(in = 0) (out= 0)(stored 0%)
    adding: samples/jdbc/simple/ejb/GreeterDB.class(in = 210) (out= 168)(deflated 20%)
    adding: samples/jdbc/simple/ejb/GreeterDBBean.class(in = 1441) (out= 734)(deflated 49%)
    adding: samples/jdbc/simple/ejb/GreeterDBHome.class(in = 257) (out= 177)(deflated 31%)
    C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>jar tf simpleEJB.jar
    META-INF/
    META-INF/MANIFEST.MF
    META-INF/ejb-jar.xml
    META-INF/sun-ejb-jar.xml
    samples/
    samples/jdbc/
    samples/jdbc/simple/
    samples/jdbc/simple/ejb/
    samples/jdbc/simple/ejb/GreeterDB.class
    samples/jdbc/simple/ejb/GreeterDBBean.class
    samples/jdbc/simple/ejb/GreeterDBHome.class
    ******************************** Deployment Info
    server1: Applications: EJB Modules: simpleEjb
    EJB Module Name: simpleEjb
    Location: C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1
    ******************************** simplEJB.jar_verified.txt
    STATIC VERIFICATION RESULTS
         NUMBER OF FAILURES/WARNINGS/ERRORS
         # of Failures : 0
    # of Warnings : 1
         # of Errors : 0
         Test Name : tests.ejb.ias.ASEjbJndiName
         Test Assertion :
         Test Description : PASSED [AS-EJB ejb] : jndi-name is ejb/simpleHome
         WARNINGS :
         Test Name : tests.ejb.businessmethod.BusinessMethodException
         Test Assertion : Enterprise bean business method throws RemoteException test
         Test Description : For [ module_simpleEjb#simpleEjb#simpleEJB ]
    For EJB Class [ samples.jdbc.simple.ejb.GreeterDBBean ] business method [ getGreeting ]
    Error: Compatibility Note: A public business method [ getGreeting ] was found, but EJB 1.0 allowed the business methods to throw the java.rmi.RemoteException to indicate a non-application exception. This practice is deprecated in EJB 1.1 ---an EJB 1.1 compliant enterprise bean should throw the javax.ejb.EJBException or another RuntimeException to indicate non-application exceptions to the Container.
    *********************** server log (no binding info)
    [05/Jan/2003:17:07:19] FINE ( 1760): [EJBClassPathUtils] EJB Class Path for [simpleEjb] is ...
    [C:\Sun\AppServer7\domains\domain1\server1\applications\j2ee-modules\simpleEjb_1, C:\Sun\AppServer7\domains\domain1\server1\generated\ejb\j2ee-modules\simpleEjb]
    [05/Jan/2003:17:07:20] FINE ( 1760): Loading StatelessSessionContainer...
    [05/Jan/2003:17:07:20] FINE ( 1760): [BaseContainer] Registered EJB [simpleEJB] with MBeanServer under name [ias:instance-name=server1,mclass=stateless-session-bean,name=simpleEJB,root=root,standalone-ejb-module=simpleEjb,type=monitor]
    [05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_RemoteHomeImpl_Tie", codebase = ""
    [05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
    [05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBHome_Stub", codebase = ""
    [05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDBBean_EJBObjectImpl_Tie", codebase = ""
    [05/Jan/2003:17:07:20] FINE ( 1760): main: name = "samples.jdbc.simple.ejb._GreeterDB_Stub", codebase = ""
    [05/Jan/2003:17:07:20] FINE ( 1760): [Pool-ejb/simpleHome]: Added PoolResizeTimerTask...
    [05/Jan/2003:17:07:20] FINE ( 1760): Created container with uinque id: 68275827784351744
    [05/Jan/2003:17:07:20] FINE ( 1760): Application deployment successful : com.sun.ejb.containers.StatelessSessionContainer@1083717
    [05/Jan/2003:17:07:20] INFO ( 1760): LDR5010: All ejb(s) of [simpleEjb] loaded successfully!
    [05/Jan/2003:17:07:22] FINE ( 1760): Started 48 request processing threads
    [05/Jan/2003:17:07:22] INFO ( 1760): CORE3274: successful server startup
    [05/Jan/2003:17:07:22] FINE ( 1760): The server is now ready to process requests
    [05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@10613aa
    [05/Jan/2003:17:07:22] INFO ( 1760): CORE3282: stdout: ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1f52460
    [05/Jan/2003:17:07:22] INFO ( 1760): CORE5053: Application onReady complete.
    *********************** Client class
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.naming.NamingException;
    import java.util.Properties;
    import java.util.Hashtable;
    import javax.ejb.*;
    import java.sql.*;
    import javax.sql.*;
    import samples.jdbc.simple.ejb.*;
    public class HelloClient {
         public static void main(String[] args) throws Exception {
    javax.ejb.Handle beanHandle;
    GreeterDBHome myGreeterDBHome;
    GreeterDB myGreeterDBRemote;
    InitialContext initContext = null;
    Hashtable env = new java.util.Hashtable(1);
    initContext = getContextInfo();
    String JNDIName = "java:comp/env/ejb/simpleHome";
    System.out.println("- Looking up: " + JNDIName);
    myGreeterDBHome = (GreeterDBHome) javax.rmi.PortableRemoteObject.narrow(initContext.lookup(JNDIName), GreeterDBHome.class);
    myGreeterDBRemote = myGreeterDBHome.create();
              String theMessage = myGreeterDBRemote.getGreeting();
    myGreeterDBRemote.remove();
         public static InitialContext getContextInfo() {
         InitialContext ctx = null;
         String url = "iiop://1st:3700";
         String fac = "com.sun.enterprise.naming.SerialInitContextFactory";
    try {
         Properties props = new Properties();
         props.put(Context.INITIAL_CONTEXT_FACTORY, fac);
         props.put(Context.PROVIDER_URL, url);
              ctx = new InitialContext(props);
         catch (NamingException ne){
    System.out.println("We were unable to get a connection to " +
    " the application server at " + url);
    ne.printStackTrace();
    return ctx;
    *********************** Running Client from command line
    C:\Sun\AppServer7\samples\jdbc\simple\assemble\jar>java HelloClient
    - Looking up: java:comp/env/ejb/simpleHome
    Exception in thread "main" javax.naming.NameNotFoundException: No object bound for java:comp/env/ejb/simpleHome
    at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:116)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at HelloClient.main(HelloClient.java:34)

  • Accessing Distributed destination JNDI Names Web

    I am using WebLogic Full Client with Weblogic 10.3. I would like to obtain the JNDI names of the physical members of a Distributed Destination. Weblogic Documentation recommends doing:
    "you must look up the JNDI name or the member name using the weblogic.jms.extensions.JMSModuleHelper class uddMakeName and uddMemberJNDIName APIs"
    http://download.oracle.com/docs/cd/E11035_01/wls100/jms/dds.html#wp1314556
    When I attempt to do the same using the Weblogic full client, I get a class not found exception where a QueueBean class is not found.
    Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/j2ee/descriptor/wl/QueueBean
         at com.overstock.jms.weblogic.ConfigurationMBeanHelper.main(ConfigurationMBeanHelper.java:150)
    Caused by: java.lang.ClassNotFoundException: weblogic.j2ee.descriptor.wl.QueueBean
    What is the best way to obtain JNDI names of distributed destinations when using Weblogic Full Client? Any code snippets would be valuable.
    Thanks.

    I think there are a variety of ways to crack this nut. Here are a couple of ideas:
    One option would be to write a server side proxy that the client can invoke. For example, a simple EJB (stateless session bean). Another option would be write client-side JMX calls that query either the runtime mbeans or config mbeans to get a list of JMS servers and/or UDD members.
    All of these options may require that the domain's administrative server be up and running (not sure). The runtime mbean options would only yield active members.
    Tom

  • WLS10.3.1 : How to overload the jndi name of a stateless EJB

    Hi,
    I am trying to overload the jndi name of a stateless bean defined in an application by using a weblogic-ejb-jar.xml descriptor file.
    This does not work.
    The ear contains a jar that have a weblogic-ejb-jar.xml file in its META-INF directory. The file is :
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar
    xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldBean</ejb-name>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>TOTO</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    This is the code of my bean :
    package test;
    import javax.ejb.Local;
    import javax.ejb.Remote;
    import javax.ejb.Stateless;
    @Stateless( name = "HelloWorldBean", mappedName="HWBean")
    @Local( IHelloWorldLocal.class)
    @Remote( IHelloWorldRemote.class)
    public class HelloWorldBean implements IHelloWorldLocal, IHelloWorldRemote
    public void sayHello(String name) {
    System.out.println( "Hello " + name + "!!!!");
    The bean implements the following interfaces :
    package test;
    public interface IHelloWorldRemote extends IHelloWorld {
    package test;
    public interface IHelloWorldLocal extends IHelloWorld {
    package test;
    public interface IHelloWorld {
    public void sayHello( String name);
    When i browse the JNDI tree, i see the bean registered with the mapped name attribute (HWBean#test.IHelloWorldRemote) but i don't see any bean registered with the name provided by the weblogic-ejb-jar.xml (TOTO)
    My standalone client can't perform a lookup using the JNDI name 'TOTO' but reaches the bean when using 'HWBean#test.IHelloWorldRemote'
    It seem's that the overload of the Jndi name using the weblogic-ejb-jar file descriptor doesn't work.
    Can you help me to solve the problem.
    Thanks.

    Thank you, my sample works fine with the following weblogic-ejb-jar.xml :
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorldBean</ejb-name>
    <enable-call-by-reference>true</enable-call-by-reference>
    <stateless-session-descriptor>
    <business-interface-jndi-name-map>
    <business-remote>test.IHelloWorldRemote</business-remote>
    <jndi-name>TOTO</jndi-name>
    </business-interface-jndi-name-map>
    </stateless-session-descriptor>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

Maybe you are looking for

  • HT4927 Why can't we restore a single photo in iPhoto anymore?

    The loss of this functionality has been anoying and I sincerely hope that Apple brings it back someday. It makes Time Machine a lot less useful for customers and also potentially leads to the loss of more data. It used to be that you could restore a

  • How can I get a file to automatically open on startup?

    I have a WORD file with my internet passwords that I want to automatically open when I start the computer. I did this once, but I can't remember how to do it. I've checked the System Preferences and the Finder, but I can't find any way to do it again

  • Sales order debit memo quantity.

    Posted on behalf of a colleague - I had created a sales order of quantity 25, and then create the partial  delivery and invoice of 24 . When I create the debit memo req w.r.t to the sales order it is also getting created for quantity 24. Now I have c

  • Question about muti-line block

    Hello, I have a multi-row block in a form and I want to know If it's possible to limite the user to don't create a new line when he click on a empty one. I got a button to do the job of adding a new line. Also, it is possible to avoid the loose of a

  • Photoshop CC Smart Sharpen Optimization

    What is the best laptop configuration (CPU, GPU, Memory, SSD) to optimize speed of Photoshop CC's smart sharpen feature?