EJB EAR deployment for weblogic 9.2

Hello!
I already have the EJB3.0 application which I would like to deploy. After preparing the .ear file I tried to deploy it with the Administration console. I received the error message, and I found a workaround : [url http://forums.bea.com/bea/thread.jspa?threadID=600016992&tstart=0]here (@dev2dev). When I tried the console deployment, I received the following error message:
<11.12.2006 14.49 Uhr CET> <Error> <Deployer> <BEA-149265> <Failure occured in the execution of deployment request with ID '1165844945693' f
or task '3'. Error is: 'weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
        at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
        Truncated. see log file for complete stacktrace
java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
ate is [END_DOCUMENT]
        at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
        at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
        at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
        at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
        at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
        Truncated. see log file for complete stacktrace
>
<11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'app5'.
>
<11.12.2006 14.49 Uhr CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(app5.jar)
        at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:394)
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
        at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
        Truncated. see log file for complete stacktrace
java.lang.IllegalStateException: getLocalName() may only be called on a START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE event, the current st
ate is [END_DOCUMENT]
        at weblogic.xml.stax.XMLStreamReaderBase.getLocalName(XMLStreamReaderBase.java:524)
        at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
        at javax.xml.stream.util.StreamReaderDelegate.getLocalName(StreamReaderDelegate.java:216)
        at com.bea.xbean.richParser.XMLStreamReaderExtImpl.getLocalName(XMLStreamReaderExtImpl.java:1294)
        at com.bea.staxb.runtime.internal.UnmarshalResult.getLocalName(UnmarshalResult.java:867)
        Truncated. see log file for complete stacktrace
>I would just like to mention, that it is not really self-explaining. Can somebody help me and explain me what does this error mean?
Also, is there a document describing the complete deployment process for wl9.2?
Thank you.
Konstantin

MIK wrote:
I have a question about weblogic-ejb-jar.xml file entries.
weblogic 9.1 server says it is invalid while deploying my file
my file is as under,
<?xml version="1.0"?><!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems,
Inc.//DTD WebLogic 8.1.0 EJB//EN'
'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/910"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/910
http://www.bea.com/ns/weblogic/910/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
          <ejb-name>MessageAccess</ejb-name>
          <message-driven-descriptor>
<resource-adapter-jndi-name>SystemModule-test</resource-adapter-jndi-name>
          </message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
can anybody help what is wrong with it?the error I get is this,
[EJB:011023]An error occurred while reading the deployment descriptor.
The error was:
Unmarshaller failed.
at
weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:957)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:317)
at
weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
at
weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
and XMLSPY also says that weblogic-ejb-jar.xml is invalid and the error
there is,
Root element '<weblogic-ejb-jar' not defined in DTD/Schema.

Similar Messages

  • Failed EAR deployment in WebLogic Server - Unexpected exception caught

    Hello
    I have a problem when deployment EAR file in WebLogic server, my application use KODO for persistence.
    This error only occurs when deployment from EAR file, when deployment from simple webapp directory the error not occurs.
    In properties variable load attributes of database connection from jdo.properties file
    PersistenceManagerFactory pmf = JDOHelper.getPersistenceManagerFactory(properties);
    javax.jdo.JDOFatalInternalException: Unexpected exception caught.
    at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1193)
    at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
    at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:701)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1616)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    NestedThrowablesStackTrace:
    java.lang.reflect.InvocationTargetException
    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:592)
    at javax.jdo.JDOHelper$16.run(JDOHelper.java:1965)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.jdo.JDOHelper.invoke(JDOHelper.java:1960)
    at javax.jdo.JDOHelper.invokeGetPersistenceManagerFactoryOnImplementation(JDOHelper.java:1166)
    at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:808)
    at javax.jdo.JDOHelper.getPersistenceManagerFactory(JDOHelper.java:701)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1616)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2761)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
    at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:139)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
    at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
    at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    Caused by: <1.0.0-SNAPSHOT-SNAPSHOT fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdb
    c.kernel.KodoJDBCBrokerFactory". See the nested exception for details.
    at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:93)
    at kodo.jdo.PersistenceManagerFactoryImpl.getPersistenceManagerFactory(PersistenceManagerFactoryImpl.java:41)
    at kodo.jdbc.runtime.JDBCPersistenceManagerFactory.getPersistenceManagerFactory(JDBCPersistenceManagerFactory.java:22)
    ... 52 more
    Thanks for help.

    I managed to resolve the issue myself. Here are the details, in case anyone is interested:
    I modified the weblogic-application.xml (present under my application EAR>META-INF folder) to include org.hibernate.* and javax.persistence.* packages. Restarted the servers and redeployed the EAR (exploded). I don't see the errors anymore and the deployment was successful.
    <prefer-application-packages>
                <package-name>org.hibernate.*</package-name>
                <package-name>javax.persistence.*</package-name>
            </prefer-application-packages>

  • Please help me about jdeveloper application deployment for weblogic

    At the beginning I just thought after developing an adf application then just deploy it as a .ear file and deploy it in the weblogic console and everything will be ok.But in fact I got a lot of problems. Then I got a tutorial for that and I do what it said step by step but some new problems occured. This is the tutorial I mentioned: [How-To: ADF Deployment Guide|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.htm]
    Now could somebody tell how did you deploy your adf application?
    Here is the errors I got.
    This is the install packege and the OS I use:
    1. CentOS 6.3_x64 + jdeveloper11123.jar(include wls10.3.5) + adr(package name is ofm_appdev_generic_11.1.1.6.0_disk1_1of1.zip)[and just now I used a solaris11 vm from oracle and install jdeveloper11.1.2.3, the same probem occured as in CentOS.]
    2. Win7_x64 + jdeveoper11123.exe(include wls10.3.5) + adr mentioned above
    Here is the problems I get:
    in the case 1,after I install the jdeveloper(using sun jdk 1.7), the weblogic seems to be well though I didn't configure a domain.But after I open an
    application(which I get from the oracle jdeveloper tutorial demo,which works well in my Win7 env) and I run it, the integrated weblogic can't get
    started. Firstly in the console it said the -jrocket identifier is not recognized, then I modify the setDomainEnv.sh and the startWebLogic.sh file in the
    integrated wls domain (the one in the .jdeveloper directer) to set the JAVA_VM variable to -server.After that another problem came out: when the
    wls goes to status "starting",it is blocked and I turn to the system monitor it shows that a java thread using more than 1GB of memory of my system
    and occupy 150% of my cpu(it's a double-core computer). I wait for about 5 minutes when a error came said "PermSize is too small".then I modify the
    setDomainEnv.sh file again to set the PermSize to be 1024m and MaxPermSize to be 2048.(the variable name is something like that, maybe not the
    exactly right. I think you can understand which one it is.) But the problem is still there.
    then in the case 2.Firstly the jdev and the integrated wls works well, but when i deploy an application which works well to a ear file and deploy it to a
    standalone wls(10.3.5) it never works.the error is something referrence/dependences libraries is not found.Then I tried to new a server connection to
    the standalone wls and I got the tutorial [how_to_deploy_adf|http://www.oracle.com/webfolder/technetwork/jdeveloper/howto/11114/managedserver/wlsadfms.html] , as the tutorial said I patch my standalone
    wls with the adr and everything goes ok, no error reported.Then I tried the new server in the new machine under the manage of the adminserver and apply the
    adf template in the localhost:port/em console. But after I restart the new server(by the console and then by the stop+startweblogic.bat file) the server is running
    while the application in the new server is just "Unavailable". I tried this for three times in three computer, two of them are running win7,the other one is running winxp.
    I don't know what is wrong and I am totally a newbie about this. Somebody please help me.Thanks a lot!
    regard,Neo.

    Neo,
    there are a couple of problems. First of all, jdev comes with it'S own jdk bundled in the product (jdk 1.6_x). Next thing is if you use JDev 11.1.2.3.0 to build an application you must use a wls 10.3.5 or 10.3.6 where you need to install the correct runtime onto. In your case you first install adf runtime 11.1.1.6.0 and then you need to install two patches which update the adf runtime to 11.1.2.3.0. These spathes are only available via support.oracle.com, meaning you need asupport contract to get them.
    More information you can find in my blog http://tompeez.wordpress.com/2011/09/14/jdeveloper-versions-vs-weblogic-server-versions/
    The rest of your problems go away once you have installed the right adf runtime on your server.
    Timo

  • EAR Deployment in Weblogic 5.1

    I am working with Weblogic 5.1 Service Pack 3. I can't find any information
    regarding how to configure WL5.1 to use an Enterprise Archive (.ear) file.
    This file is part of the J2EE spec. Does anyone out there know if WL5.1
    supports this type of file? If so, do you know how to configure Weblogic?
    Your help is appreciated.
    -sean

    Thank you for your reply.
    -sean
    "Kumar Allamraju" <[email protected]> wrote in message
    news:[email protected]..
    EAR files are currently not supported in this release.
    Kumar
    Sean Scott wrote:
    I am working with Weblogic 5.1 Service Pack 3. I can't find any
    information
    regarding how to configure WL5.1 to use an Enterprise Archive (.ear)file.
    This file is part of the J2EE spec. Does anyone out there know if WL5.1
    supports this type of file? If so, do you know how to configureWeblogic?
    >>
    Your help is appreciated.
    -sean

  • ANNOUNCE:::::::: EJB job scheduler for Weblogic

    Paramus, NJ - June 26, 2001 - Indus Consultancy Services today announced
    an upgrade release of its Java scheduling product. Kronos Enterprise
    Scheduler is a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    As a J2EE application, Kronos Enterprise Scheduler is able to achieve a
    high degree of portability, scalability, and reliability, features which
    are critical to an enterprise system.
    Additionally, Kronos Enterprise Scheduler provides a comprehensive set
    of scheduling options, powerful holiday definitions, job dependencies,
    administrative alerts, J2EE security integration, monitoring
    capabilities, Web and "rich client" user interfaces, and an open
    developer API. The combination of these features make Kronos Enterprise
    Scheduler one of the most complete solutions on the market today.
    Version 2.10 contains a number of minor enhancements and bug fixes and
    is a free upgrade for current customers.
    For more information on Kronos, please visit our products page at
    www.indcon.com

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • KRONOS - EJB Job scheduler for Weblogic

    Paramus, NJ - February 22, 2002 - Indus Consultancy Services (ICS) today
    announced the latest in a series of improvements to Kronos Enterprise
    Scheduler, a full-featured job scheduling system written for the
    Enterprise Java (J2EE) environment.
    This version fixes some minor bugs reported by customers, and adds a new
    security feature to control user visibility to jobs, tasks, and
    schedules. A new environment setting allows the Kronos Enterprise
    Scheduler administrator to restrict users to seeing only those items
    which they have created. Administrators still have full visibility to
    all items.
    ICS is also proud to have Kronos Enterprise Scheduler competing in the
    Java Developer's Journal 2002 Readers' Choice Awards. Every year, Java
    Developer's Journal holds voting for products in a variety of
    categories. This year, Kronos Enterprise Scheduler is nominated in
    three of those categories:
    · Best Java Application (Standing as of 2/22/02 : 16th out of 69
    products with votes.)
    · Best Java Component (Standing as of 2/22/02 : 10th out of 26 products
    with votes.)
    · Most Innovative Java Product (Standing as of 2/22/02 : 21st out of 63
    products with votes.)
    To vote, visit the Java Developer's Journal website at
    <http://www.sys-con.com/java/readerschoice2002>
    To find out more about Kronos Enterprise Scheduler, and learn why
    companies around globe are selecting this powerful product to handle
    their scheduling needs, visit the ICS website at <http://www.indcon.com>
    and request a FREE 30-day evaluation.
    © 2002 Indus Consultancy Services, Inc. All rights reserved. Java and
    all Java-based marks are trademarks or registered trademarks of Sun
    Microsystems, Inc. in the U.S. and other countries. All other product
    and company names are trademarks of their respective owners.

    I would hope that BEA will step up and develop a replacement for their
    deprecated APIs. It is unfair to ask their customers to buy something they
    got previously for free. I also understand that the future EJB spec will
    contain scheduling features.

  • Calling EJB deployed on Weblogic 10.3 from WebSphere Application Server 6

    Hi,
    We are trying to call an EJB(2.1) deployed in Weblogic 10.3 from WebSphere Application Server 6.
    The problem is that the jars containing Weblogic's initial context factory are compiled with JDK5. (Client jar was built as per [http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html] .)
    WebSphere is still running on JDK1.4.
    Therefore when trying to get the InitialContext to lookup up the bean we get major/minor version errors because of the compiler level mismatch.
    Has anyone faced a scenario like this and come up with a solution?
    Are there 1.4 jars for Weblogic 10.3 out there?
    Any help?
    Thanks

    Hi Dan,
    Yes I am using EJB 3. I saw this thread earlier also but :
    1. In my case I am not calling the EJB 3.0 methods directly. I am using a java client (Cataloged as a Java Class Library) which does the lookup and calls the EJB methods. (I am not cataloging and calling the EJB 3.0 methods directly).
    2. It is working perfectly fine when the EJB is deployed in Weblogic 10.0 or 10.2.
    I am very much new to this so please bear with my small and silly questions! Thanks a lot for you help !
    Cheers !
    Rajat

  • Help me to invoke an EJB deployed in weblogic

    Hi,
    I have these EJB's deployed in weblogic. Im not able to invoke it...coz of these roles and permissions associated with it...here's my code and the o/p i got
    import java.security.Principal;
    import java.util.Hashtable;
    import javax.ejb.SessionContext;
    import javax.naming.Context;
    import javax.naming.InitialContext;
    import javax.rmi.PortableRemoteObject;
    import com.convergys.geneva.j2ee.product.ProductPK;
    import com.convergys.geneva.j2ee.product.ProductSession;
    import com.convergys.geneva.j2ee.product.ProductSessionHome;
    import com.convergys.geneva.j2ee.product.ProductSessionImpl;
    public class invoke {
    public static void main(String args[]) {
         com.convergys.geneva.j2ee.product.ProductSessionHome productSessionHomeobj = null;
         com.convergys.geneva.j2ee.product.ProductSession productSession = null;
    try {
         Hashtable env = new Hashtable();
         com.convergys.geneva.j2ee.product.ProductPK ProductPK1=new ProductPK(1);
         env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
         env.put(Context.PROVIDER_URL, "t3://172.20.212.252:10000" );
         env.put(Context.SECURITY_PRINCIPAL,"wlsadmin");
         env.put(Context.SECURITY_CREDENTIALS,"wlsadmin");
         InitialContext ic = new InitialContext(env);
              System.out.println("Got Initial context" + ic);
    Object sless = ic.lookup("Convergys/ECA/Product");
    System.out.println("Value of the sless object is :" + sless);
         productSessionHomeobj = (ProductSessionHome) PortableRemoteObject.
    narrow(sless, ProductSessionHome.class);
         System.out.println("before");
         SessionContext ses = null;
    productSession = productSessionHomeobj.create();
         productSession.readAllProductAttributeData_5_1(ProductPK1,1);
    } catch(Exception e) {
    e.printStackTrace();
    and the o/p i got is
    Got Initial contextjavax.naming.InitialContext@e1d5ea
    Value of the sless object is :IOR:000000000000004a524d493a636f6d2e636f6e7665726779732e67656e6576612e6a3265652e70726f647563742e50726f6475637453657373696f6e486f6d653a303030303030303030303030303030300000000000000100000000000003fc000102000000000f3137322e32302e3231322e3235320000271000000000008c0042454108010300000000077365727665720000000000000000004a524d493a636f6d2e636f6e7665726779732e67656e6576612e6a3265652e70726f647563742e50726f6475637453657373696f6e486f6d653a303030303030303030303030303030300000000000000433333800000000014245412a000000100000000000000000441358834f7da8d000000006000000010000002c00000000000100200000000300010020000100010501000100010100000000030001010000010109050100010000001900000047000000000000003f687474703a2f2f3137322e32302e3231322e3235323a31303030302f6265615f776c735f696e7465726e616c2f636c61737365732f4543412e656172402f00000000001f000000040000000300000020000000040000000100000021000000580000000000000001000000000000002200000000004000000000000806066781020101010000001f0401000806066781020101010000000f7765626c6f67696344454641554c5400000000000000000000000000000000004245410300000248000000000000000c726f756e642d726f62696e000100000000000016436f6e7665726779732e4543412e50726f64756374000000000000010000004a524d493a636f6d2e636f6e7665726779732e67656e6576612e6a3265652e70726f647563742e50726f6475637453657373696f6e486f6d653a303030303030303030303030303030300000000000000100000000000001ac000102000000000f3137322e32302e3231322e3235320000271000000000008c0042454108010300000000077365727665720000000000000000004a524d493a636f6d2e636f6e7665726779732e67656e6576612e6a3265652e70726f647563742e50726f6475637453657373696f6e486f6d653a303030303030303030303030303030300000000000000433333800000000014245412a000000100000000000000000441358834f7da8d000000005000000010000002c00000000000100200000000300010020000100010501000100010100000000030001010000010109050100010000001900000047000000000000003f687474703a2f2f3137322e32302e3231322e3235323a31303030302f6265615f776c735f696e7465726e616c2f636c61737365732f4543412e656172402f00000000001f000000040000000300000020000000040000000100000021000000580000000000000001000000000000002200000000004000000000000806066781020101010000001f0401000806066781020101010000000f7765626c6f67696344454641554c540000000000000000000000000000000000000000004f7da8d0
    before
    java.rmi.AccessException: CORBA NO_PERMISSION 0 Maybe; nested exception is:
         org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: Maybe
         at com.sun.corba.se.impl.javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
         at javax.rmi.CORBA.Util.mapSystemException(Unknown Source)
         at com.convergys.geneva.j2ee.product._ProductSessionHome_Stub.create(Unknown Source)
         at invoke.main(invoke.java:46)
    Caused by: org.omg.CORBA.NO_PERMISSION: vmcid: 0x0 minor code: 0 completed: Maybe
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at java.lang.Class.newInstance0(Unknown Source)
         at java.lang.Class.newInstance(Unknown Source)
         at com.sun.corba.se.impl.protocol.giopmsgheaders.MessageBase.getSystemException(Unknown Source)
         at com.sun.corba.se.impl.protocol.giopmsgheaders.ReplyMessage_1_2.getSystemException(Unknown Source)
         at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.getSystemExceptionReply(Unknown Source)
         at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.processResponse(Unknown Source)
         at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(Unknown Source)
         at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.invoke(Unknown Source)
         at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source)
         ... 2 more
    Is there some kind of security in ejb?. If so how can do it? Kindly help

    Hi,
    Some improvement regarding the code. I found i had to use the logincontext to login to the session so i had modified my code like this which for the most part i got from this blog(http://weblogic-wonders.com/weblogic/2010/06/15/jaas-login-in-weblogic-server/)
    here's the code....
    public class invoke {
    public static void main(String args[]) {
         com.convergys.geneva.j2ee.product.ProductSessionHome productSessionHomeobj = null;
         com.convergys.geneva.j2ee.product.ProductSession productSession = null;
    try {
         Hashtable env = new Hashtable();
         com.convergys.geneva.j2ee.product.ProductPK ProductPK1=new ProductPK(1);
         env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
         env.put(Context.PROVIDER_URL, "t3://172.20.212.252:10000" );
         env.put(Context.SECURITY_PRINCIPAL,"wlsadmin");
         env.put(Context.SECURITY_CREDENTIALS,"wlsadmin");
         InitialContext ic = new InitialContext(env);
              System.out.println("Got Initial context" + ic);
              LoginContext lc = new LoginContext("wlsadmin", new invoke.CallbackHandler("wlsadmin","wlsadmin", "t3://172.20.212.252:10001"));
              System.out.println("LoginContext:: ");
    Object sless = ic.lookup("Convergys/ECA/Product");
    System.out.println("Value of the sless object is :" + sless);
         productSessionHomeobj = (ProductSessionHome) PortableRemoteObject.
    narrow(sless, ProductSessionHome.class);
         System.out.println("before");
         SessionContext ses = null;
    productSession = productSessionHomeobj.create();
         productSession.readAllProductAttributeData_5_1(ProductPK1,1);
    } catch(Exception e) {
    e.printStackTrace();
    private static final class CallbackHandler implements javax.security.auth.callback.CallbackHandler
    private String userid;
    private String password;
    private String url;
    public CallbackHandler(String userid, String password, String url)
    this.userid = userid;
    this.password = password;
    this.url = url;
    public void handle(Callback[] callbacks) throws UnsupportedCallbackException
    for (int i = 0; i < callbacks.length; i++)
    if (callbacks[i] instanceof TextOutputCallback)
    TextOutputCallback toc = (TextOutputCallback)callbacks;
    System.err.println("JAAS callback: " + toc.getMessage());
    else if (callbacks[i] instanceof NameCallback)
    NameCallback nc = (NameCallback)callbacks[i];
    nc.setName(userid);
    else if (callbacks[i] instanceof PasswordCallback)
    PasswordCallback pc = (PasswordCallback)callbacks[i];
    pc.setPassword(password.toCharArray());
    else if (callbacks[i] instanceof weblogic.security.auth.callback.URLCallback)
    URLCallback uc = (URLCallback)callbacks[i];
    uc.setURL(url);
    else
    System.out.println(callbacks[i] + "Unrecognized Callback");
    throw new UnsupportedCallbackException(callbacks[i], "Unrecognized Callback");
    but stilli get the error
    java.lang.SecurityException: Unable to locate a login configuration
         at com.sun.security.auth.login.ConfigFile.<init>(Unknown Source)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
         at java.lang.reflect.Constructor.newInstance(Unknown Source)
         at java.lang.Class.newInstance0(Unknown Source)
         at java.lang.Class.newInstance(Unknown Source)
         at javax.security.auth.login.Configuration$3.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.Configuration.getConfiguration(Unknown Source)
         at javax.security.auth.login.LoginContext$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.login.LoginContext.init(Unknown Source)
         at javax.security.auth.login.LoginContext.<init>(Unknown Source)
         at invoke.main(invoke.java:51)
    Caused by: java.io.IOException: Unable to locate a login configuration
         at com.sun.security.auth.login.ConfigFile.init(Unknown Source)
         ... 15 more

  • Deployment plan fails for weblogic-ejb-jar.xml

    FILE FOR PLAN TO ACT ON:
    application.ear\ReferenceTableSession.jar\META-INF\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>referencetablesession</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
    </pool>
    <stateless-clustering>
    <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    <trans-timeout-seconds>150</trans-timeout-seconds>
    </transaction-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
    </weblogic-enterprise-bean>
    <transaction-isolation>
    <isolation-level>TransactionReadCommitted</isolation-level>
    <method>
    <ejb-name>referencetablesession</ejb-name>
    <method-name>*</method-name>
    </method>
    </transaction-isolation>
    </weblogic-ejb-jar>
    DEPLOYMENT PLAN:
    <?xml version='1.0' encoding='utf-8'?>
    <deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
    <application-name>application.ear</application-name>
    <variable-definition>
    <variable>
    <name>VAR_referencetablesession</name>
    <value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>ReferenceTableSession.jar</module-name>
    <module-type>ejb</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-ejb-jar</root-element>
    <uri>META-INF/weblogic-ejb-jar.xml</uri>
    <variable-assignment>
    <name>VAR_referencetablesession</name>
         <xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
    <operation>replace</operation>
    </variable-assignment>
    </module-descriptor>
    </module-override>
    <config-root>servers/AdminServer/upload</config-root>
    </deployment-plan>
    ERROR FROM CONSOLE:
    Message icon - Error An error occurred during activation of changes, please see the log for details.
    Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
    Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
    ERROR FROM LOG:
    <Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
    at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
    at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
    at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
    Thanks,
    Rob
    Edited by: user11337024 on Oct 5, 2009 2:31 PM

    FILE FOR PLAN TO ACT ON:
    application.ear\ReferenceTableSession.jar\META-INF\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>referencetablesession</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    <initial-beans-in-free-pool>0</initial-beans-in-free-pool>
    </pool>
    <stateless-clustering>
    <stateless-bean-is-clusterable>true</stateless-bean-is-clusterable>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    <trans-timeout-seconds>150</trans-timeout-seconds>
    </transaction-descriptor>
    <enable-call-by-reference>true</enable-call-by-reference>
    <jndi-name>XYZ_ejb/ProviderMaintSvc/referencetablesession</jndi-name>
    </weblogic-enterprise-bean>
    <transaction-isolation>
    <isolation-level>TransactionReadCommitted</isolation-level>
    <method>
    <ejb-name>referencetablesession</ejb-name>
    <method-name>*</method-name>
    </method>
    </transaction-isolation>
    </weblogic-ejb-jar>
    DEPLOYMENT PLAN:
    <?xml version='1.0' encoding='utf-8'?>
    <deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd">
    <application-name>application.ear</application-name>
    <variable-definition>
    <variable>
    <name>VAR_referencetablesession</name>
    <value>ejb/ProviderClaimOnlineSvc/referencetablesession</value>
    </variable>
    </variable-definition>
    <module-override>
    <module-name>ReferenceTableSession.jar</module-name>
    <module-type>ejb</module-type>
    <module-descriptor external="false">
    <root-element>weblogic-ejb-jar</root-element>
    <uri>META-INF/weblogic-ejb-jar.xml</uri>
    <variable-assignment>
    <name>VAR_referencetablesession</name>
         <xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="referencetablesession"\]/jndi-name</xpath>
    <operation>replace</operation>
    </variable-assignment>
    </module-descriptor>
    </module-override>
    <config-root>servers/AdminServer/upload</config-root>
    </deployment-plan>
    ERROR FROM CONSOLE:
    Message icon - Error An error occurred during activation of changes, please see the log for details.
    Message icon - Error Exception preparing module: EJBModule(ReferenceTableSession.jar) [EJB:011023]An error occurred while reading the deployment descriptor. The error was: Unmarshaller failed.
    Message icon - Error Bean already exists: "[email protected]f2(/WeblogicEnterpriseBeans[referencetablesession])"
    ERROR FROM LOG:
    <Oct 2, 2009 1:08:25 PM CDT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor servers/ms34/tmp/_WL_user/ProviderClaimOnlineSvc/y1anoa/ReferenceTableSession.jar/META-INF/weblogic-ejb-jar.xml of module ReferenceTableSession.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.mergeDescriptorBeanWithPlan(AbstractDescriptorLoader2.java:703)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:776)
    at weblogic.ejb.spi.EjbJarDescriptor.parseWeblogicEjbJarBean(EjbJarDescriptor.java:160)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLEjbJarXMLWithSchema(EjbDescriptorReaderImpl.java:719)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.parseWLDD(EjbDescriptorReaderImpl.java:541)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWeblogicEjbJarXML(EjbDescriptorReaderImpl.java:380)
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:191)
    at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
    at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1198)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:380)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.RedeployOperation.createAndPrepareContainer(RedeployOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.RedeployOperation.doPrepare(RedeployOperation.java:122)
    Thanks,
    Rob
    Edited by: user11337024 on Oct 5, 2009 2:31 PM

  • Deploying EJB EARs to Weblogic -- need help with descriptor file?

    I posted this in a different area... maybe it will help to post here.
    Hi all...
    Can someone give me a hand with getting the descriptor correct? I find lots of information about the structure of the XML file, but not much on what needs to go in it.
    If I deploy with it i the default state I don't get that error... but I can't dig my beans out with JNDI.
    I also notice that the class is not the generated class I would expect (and see on other deployments) but is "com.java.proxy.PROXY"
    Here is the top of my bean...
    package f17.ejb.creditdata;
    import javax.ejb.SessionContext;
    import javax.ejb.Stateful;
    @Stateful(name = "creditScoreData", mappedName = "f17.ejb.creditData-creditScoreData")
    public class creditScoreDataBean implements creditScoreData {
    This is my weblogic-ejb-jar.xml as it stands:
    <?xml version = '1.0' encoding = 'windows-1252'?>
    <weblogic-ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                      xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-ejb-jar http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd"
                      xmlns="http://www.bea.com/ns/weblogic/weblogic-ejb-jar">
      <weblogic-enterprise-bean>
        <ejb-name>creditScoreDataBean</ejb-name>
        <stateful-session-descriptor>
          <business-interface-jndi-name-map>
            <business-remote>creditScoreData</business-remote>
            <jndi-name>creditScoreData</jndi-name>
          </business-interface-jndi-name-map>
        </stateful-session-descriptor>
        <ejb-reference-description>
          <ejb-ref-name>creditScoreData</ejb-ref-name>
          <jndi-name>f17.ejb.creditdata.creditScoreData</jndi-name>
        </ejb-reference-description>
        <jndi-name>f17.ejb.creditdata.creditScoreData</jndi-name>
      </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

    I figure this out.. wanted to delete the thread.. but I can't find that option. lol

  • A Tip for using EJB 3.0 with WebLogic Ant Tasks

    I started out writing this up as a problem, but then I found the answer so I'm, posting a tip instead.
    When I tried to write an EJB [stateless] using EJB 3.0 in my legacy Weblogic ear project I started getting this error:
    <pre>
    No EJBs found in the ejb-jar file 'test'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    </pre>
    This is why: wlcompile will put the class files in the App-Inf/classes directory unless it finds an ejb-jar.xml file in the META-INF directory for the module it is working on. With EJB 3.0, I wasn't using an ejb-jar.xml file because it was unnecessary. Later, Appc runs and it complains <b>because there are no classes module directory, they went into the shared ear folder instead.</b>
    Here's I how it working again: Use javac [not wlcompile] to compile the EJB 3.0 module and make sure that the class files go into the correct module directory. Then you can use wlappc to generate all the associated files for the EJB. I have sucessfully deployed an ear file that uses both EJB 2.x and EJB 3.0 with this approach.
    I wish Weblogic's own ejb3.0 sample application used their split directory deployment.
    Good Luck.
    John Aronson

    Hi John,
    I am working on development an enterprise application using EJB 3.0 on Weblogic 10.
    While developing, I am keeping all my classes (from ejb's as well as web) into APP-INF/classes directory. It is working fine for Web and ejb 2.0 packages, but ejb 3.0 packages, I get the following error when I keep my ejb 3.0 beans classes in APP-INF/classes directory.
    No EJBs found in the ejb-jar file 'customer'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    One solution is to keep the classes under customer ejb directory, but I wan tto keep all the classes in APP-INF/classes directory so that when using Eclipse IDE I can output all compiled sources into APP-INF/classes directory.
    Has anyone faced this situation? Any suggestions to fix this issue?

  • WebLogic 10 and EJB 3.0 for Message Driven Bean

    Hi,
    I am trying to deploy Message Driven Bean using EJB3.0 on weblogic 10. I am using annotations and don't want to use deployment descriptors.
    The Bean class:
    CalculatorBean.java
    import javax.ejb.*;
    import javax.jms.*;
    import java.sql.Timestamp;
    import java.util.StringTokenizer;
    @MessageDriven(activationConfig =
    @ActivationConfigProperty(propertyName="destinationType",
    propertyValue="javax.jms.Queue"),
    @ActivationConfigProperty(propertyName="destination",
    propertyValue="queue/mdb")
    public class CalculatorBean implements MessageListener {
    public void onMessage (Message msg) {
    TextMessage tmsg=null;
    try {
    if (msg instanceof TextMessage) {
    tmsg = (TextMessage) msg;
    System.out.println
    ("MESSAGE BEAN1: Message received: "
    + tmsg.getText());
    } else {
    System.out.println
    ("Message of wrong type1: "
    + msg.getClass().getName());
    catch (JMSException e) {
    e.printStackTrace();
    catch (Throwable te) {
    te.printStackTrace();
    My client:
    import javax.naming.*;
    import javax.naming.InitialContext;
    import java.text.*;
    import javax.jms.*;
    public class MsgClient {
    public static void main(String args[])
    QueueConnection cnn=null;
    QueueSender sender=null;
    QueueSession sess=null;
    Queue queue=null;
    try {
    java.util.Properties p = new java.util.Properties();
    p.put("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
    p.put("java.naming.provider.url","t3://10.6.74.79:7001");
    Context ctx=new InitialContext(p);
    //InitialContext ctx=new InitialContext(p);
    queue = (Queue)ctx.lookup("queue/mdb");
    QueueConnectionFactory factory = (QueueConnectionFactory)ctx.lookup("ConnectionFactory");
    cnn = factory.createQueueConnection();
    sess= cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
    sender = sess.createSender(queue);
    TextMessage message = sess.createTextMessage();
    message.setText("This is message by Gurumurthy" );
    System.out.println("Sending message: " +message.getText());
    sender.send(message);
    sess.close();
    catch (Exception e)
    e.printStackTrace();
    I am compiling and creating jar file for this class. Then I am creating a .ear file for this.
    The meta-inf/application.xml contains the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/j2ee" version="1.4"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com /xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">
    <display-name>MDBWorking1</display-name>
    <description>Application description</description>
    <module>
    <ejb>MDBWorking1.jar</ejb>
    </module>
    </application>
    I don't want to use deployment descriptor (ejb-jar.xml or weblogic-ejb-jar-xml), because I want to utilize the annotation feature of EJB3.0
    So, after creating the .ear file for this, and try to deploy on weblogic 10, I get the following error:
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(MDBWorking1.jar) Unable to deploy EJB: CalculatorBean from MDBWorking1.jar: [EJB:011113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
    Substituted for missing class [EJB - 11113]Error: The Message Driven Bean 'CalculatorBean(Application: MDBWorking1, EJBComponent: MDBWorking1.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
    How to solve this?
    Note:
    I don't want to use Deployment Descriptor and all I want to use is EJB3.0's annotation feature.
    Thanks,
    Guru

    Dear gurubbc,
    I don't know if it still matters to you but you can use the javax.ejb.MessageDriven annotation to point your bean on your queue. I had the same issue like you but i could not solve it properly by switchihg to weblogic.ejb.MessageDriven.
    Use the following annotation and it should work out:
    @MessageDriven
    (mappedName = "queue/mdb",
    name = "CalculatorBean",
    activationConfig = {
    @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
    Here you can see that the mappedName is the JNDI name of the queue you are trying to connect to. The name is the name for your Bean, and the only property passed is the destination type.
    Hope this helps.
    Cheers,
    Istvan

  • Error while deploying EAR file on weblogic

    When i deploy an EAR file on weblogic 10.3 i get the following.
    Please tell how to rectify it?
    Unable to access the selected application.
    Exception in AppMerge flows' progression
    Exception in AppMerge flows' progression
    [J2EE:160161]Error while parsing the Application descriptors for Portal-0.0.1-SNAPSHOT.ear: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee: at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234) at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221) at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292) at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260) at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774) at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745) at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:754) at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:307) at weblogic.application.compiler.CompilerCtx.setApplicationDescriptor(CompilerCtx.java:131) at weblogic.application.compiler.AppcUtils.setDDs(AppcUtils.java:142) at weblogic.application.compiler.flow.DescriptorParsingFlow.compile(DescriptorParsingFlow.java:57) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49) at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94) at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47) at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36) at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96) at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:142) at weblogic.utils.compiler.Tool.run(Tool.java:158) at weblogic.utils.compiler.Tool.run(Tool.java:115) at weblogic.application.compiler.AppMerge.merge(AppMerge.java:154) at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:79) at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:60) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:184) at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:151) at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:646) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:459) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64) at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:168) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58) at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:251) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1170) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106) at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:107) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:180) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:168) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:223) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:178) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341) at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332) at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:164) at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:139) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:377) at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:253) at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:194) at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:266) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200) at weblogic.work.ExecuteThread.run(ExecuteThread.java:172) .

    Hi,
    Can you please paste your "application.xml" file, Looks like you are using a Wrong DTD/XSD declaration in this file or May be ou are using Wrong Tags in this file.
    The Standard "application.xml" should look something like below, as described in the following link: http://middlewaremagic.com/weblogic/?p=1952
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4">
    <description>Test EAR Example</description>
    <display-name>TestEAR Example</display-name>
    <module>
    <ejb>EJB1.jar</ejb>
    </module>
    <module>
    <web>
    <web-uri>WebApp1.war</web-uri>
    <context-root>WebApp1ContextRoot</context-root>
    </web>
    </module>
    </application>
    NOTE: please make sure that you donot change the order of the <display-name> Tag....Sometimes it causes Parsing failure as yours.
    Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic/?p=1952 (Middleware Magic Is Here)

  • Error in deploying .ear file in weblogic 6.1

    Hi
    i had deployed an ear file named ProjectBroker.ear using hte weblogic console
    and it was working fine .i had made changes to the ejb bean file and hence tried
    redeploy it,though on the console it shows that it is deployed it , i'm not able
    to access the ejb methods ,also when i start the server it gives me the following
    error ---
    <Mar 11, 2002 11:22:32 AM IST> <Error> <J2EE> <Error deploying application web-s
    ervices: Cannot deploy WebAppServletContext(5197502,web-services,/ProjectBroker)
    on myserver because WebAppServletContext(5450599,web-services,/ProjectBroker)
    i
    s already registered for path /ProjectBroker>
    java.lang.reflect.UndeclaredThrowableException: weblogic.j2ee.DeploymentExceptio
    n: Cannot deploy WebAppServletContext(5197502,web-services,/ProjectBroker) on
    my
    server because WebAppServletContext(5450599,web-services,/ProjectBroker) is alre
    ady registered for path /ProjectBroker
    could any one help me out on this issue
    Rgds
    ravi

    Hi Ivaylo,
    to answer your first question, the EAR that I am trying
    to deploy gets created as part of the publish step. When
    I look in the application.xml file of this EAR I see a
    version attribute with value of 1.4 in the application
    tag, can we assume that this implies J2EE 1.4 compliancy?
    One thing about this generated EAR is that it does not
    include any java code (VM or otherwise). When I generate
    the EAR by hand (by exporting the EJB project as an EAR
    file there is a JAR for the actual java code put in
    there, but when generating the EAR via publish there is
    only some xml and manifest stuff put in the EAR, with the
    result that it's only 2KB or so in size. I have specified
    a J2EE module dependency from the Enterprise Application
    project to the EJB project, but is there something else I
    need to do to ensure that the java code (jar) gets
    included in the EAR of the Enterprise Application when
    attempting to deploy via publish?
    Thanks for the other suggest, "Import J2EE Archive".
    However, I am having difficulty locating this button.
    When I look at the "Deploy View" window I see on the left
    the Workspace and External Deployable Archives trees,
    and on the right there are "Setting for Updating
    SCAs/SDAs" radio buttons, as well as "Error Strategy"
    radio buttons, but no "Import J2EE Archive" button.
    Thanks for the info about SDM by the way, I was wondering
    why I was not able to launch it (there is still a remote
    gui shortcut, which should probably go away).

  • EJB deployment in weblogic 8.1

    I am new to EJB's. I have truly tried to research and solve this problem. I am trying to deploy a simple EJB in wls 8.1.
    Here are snippets of ejb-jar.xml, web.xml, and weblogic-ejb-jar.xml:
    ejb-jar.xml:
    <ejb-jar>
    <enterprise-beans>
    <session>
    <display-name>UserScanSystems</display-name>
    <ejb-name>com.myCo.util.UserScanSystems</ejb-name>
    <home>com.myCo.util.UserScanSystemsHome</home>
    <remote>com.myCo.util.UserScanSystemsRemote</remote>
    <ejb-class>com.myCo.util.UserScanSystemsBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>com.myCo.util.UserScanSystems</ejb-name>
    <method-intf>Remote</method-intf>
    <method-name>*</method-name>
    </method>
    <trans-attribute>NotSupported</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml:
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>com.myCo.util.UserScanSystems</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </pool>
    <stateless-clustering>
    <stateless-bean-is-clusterable>True</stateless-bean-is-clusterable>
    </stateless-clustering>
    </stateless-session-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>com.myCo.util.UserScanSystems</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    in web.xml:
    <ejb-ref>
    <ejb-ref-name>ejb/UserScanSystems</ejb-ref-name>
    <ejb-ref-type>Session</ejb-ref-type>
    <home>com.myCo.util.UserScanSystemsHome</home>
    <remote>com.myCo.util.UserScanSystemsRemote</remote>
    <ejb-link>com.myCo.util.UserScanSystems</ejb-link>
    </ejb-ref>
    When I deploy I receive an error message that the ejb-link com.myCo.util.UserScanSystems could not be resolved. com.myCo.util.UserScanSystems is both the ejb-name in ejb-jar.xml and weblogic-ejb-jar.xml and the jndi-name in weblogic-ejb-jar.xml. I have tried another [unique] name for ejb-name but still receive the same problem. I am primarily deploying into an exploded webapp but have also tried deploying ear and war files using >../ejb/ejb.jar#com.myCo.util.UserScanSystems as a relative path to the jar containing the EJB but same type of error.
    what is the ejb-link supposed to be? the jndi-name in weblogic-ejb-jar.xml ? (In my case it's both jndi and ejb-name)
    What am I missing?
    Exception:weblogic.management.ApplicationException: activate failed for dts Module: dts Error: weblogic.management.DeploymentException: Could not setup environment - with nested exception: [weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'com.myCo.util.UserScanSystems' declared in the ejb-ref or ejb-local-ref 'ejb/UserScanSystems' in the application module 'dts' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct.] weblogic.deployment.EnvironmentException: [J2EE:160101]Error: The ejb-link 'com.myCo.util.UserScanSystems' declared in the ejb-ref or ejb-local-ref 'ejb/UserScanSystems' in the application module 'dts' could not be resolved. The target EJB for the ejb-ref could not be found. Please ensure the link is correct. at weblogic.deployment.EnvironmentBuilder.addEJBLinkRef(EnvironmentBuilder.java:664)
    Note that once the exploded version of application fails I can goto the weblogic console and deploy the EJB using the jar file that gets approot/ejb/ejb.jar but subsequnt deploy attempts at the application still fail.
    If anyone has a working example and could post ejb-jar.xml, pertaining piece of web.xml, and weblogic-ejb-jar.xml that would be GREAT!

    Refer to the ejb-link section in the ejb-local-ref.
    http://edocs.bea.com/wls/docs81/webapp/web_xml.html#1020090
    <ejb-link>../ejb.jar/#com.myCo.util.userScanSystems</ejb-link>

Maybe you are looking for

  • Creating a DVD from camcorder video tape

    Hi all, I am tasked with creating a DVD from some of my dads camcorder tapes. Can anyone provide a simple advice list. I assume that iDVD (which i have never used) will be the software to use? Look forward to hearing from you helpful and intelligent

  • Can't drag and drop songs into a new playlist

    I can't seem to drag and drop songs from my itunes library into a new playlist in order to burn a cd.  Any suggestions?  I've tried closing out and restarting but that didn't work.  thanks!

  • Effects only works on first page when viewed in IE 8

    I use the drop shadow and bevel effects on all of my sites, and I've found that when I view my site pages in Internet Explorer 8, the effects only shows up on the first page. I set up all effects on the MASTER page, so they should appear on all of my

  • Airport in one room, printer in another - What Next?

    Sorry if the topic subject is confusing, but I don't know how else to word it. My AEBS is in my living room where my cable modem is. I have a printer that I want to use wirelessy throughout the apartment, but it is in the other room, too far away to

  • Lumia 625 Apps wont connect to the internet

    So i have just purchased a Lumia 625 as a replacement phone untill upgrade. For some reason none of of the pre installed apps or ones i have downloaded will conect to the internet, this includes, Amazon, Facebook, MyEE, LloydsBank, Barclays Bank I ei