Probs in Deploying EJB in weblogic 8.1

have Made a simple ejb example printing helloworld ,but i m stuck in deployment.what i have done is used meta-inf in the application to store ejb-jar,why m i getting compllation errors inspite of the fact tht the build is successful,i m working in weblogic 8.1.I have already placed meta-inf in src that has pooja folder containing all 3 java files ,and then used the command jar cvf myHello ejb.jar src META-INF and it is giving manifest info i have compared it from a book it is correct,can u plz tell how can i run my ejb once i placed them home ,remote,implemnt,client in pooja folder in src .
i m getting compile time errs in CreateException,EJBHome,EJBObject,SessionBean :cannot resolve symbol
and javax.ejb.* that it does not exist.

Hi,
Sounds like your java compiler does not know about J2EE classes.
Try adding weblogic.jar is in your CLASSPATH
or
javac -classpath weblogic.jar *.java
Regards
Alexandre

Similar Messages

Deploying EJB on Weblogic

Hi,
Can anyone please send the step by step detailed instructions for deploying EJBs on Weblogic 6.1 app server. Please send it to my email id [email protected]
Any supporting code will be greatly appreciated.
Thanks.

Why don't you check out the excellent instructions that BEA makes available from their support site:
Specific to your current question:
http://edocs.bea.com/wls/docs61/ejb/index.html
and even more specific:
http://edocs.bea.com/wls/docs61/ejb/deploy.html#1050867
And more general info:
http://edocs.bea.com/wls/docs61/index.html

Error deploying EJB in weblogic 7.0

Hello
I am trying to deploy EJB 2.0, to Weblogic 7.0 server on IBM machine and i am
getting this following error. Previously I have tested deploying the same EJB
to weblogic 7.0 server on my local PC which based on Windows, and everything seems
Ok.
Unable to deploy EJB: DACEJB.jar from DACEJB.jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath, /bea/weblogic700/server/bin/tmp_ejbsmeap01ibm7001myserver/-1spvbzuqlvq3z:/bea/weblogic700/server/bin/DACEJB.jar:/usr/java131/jre/lib/rt.jar:/usr/java131/jre/lib/i18n.jar:/usr/java131/jre/classes:/CMS/CORP/config/:/bea/weblogic700:/bea/weblogic700/server/lib/crack.jar:/bea/weblogic700/server/lib/classes12_g.jar:/bea/weblogic700/server/lib/HostMsgDriverV2.1_oracle.jar:/bea/weblogic700/server/lib/aal2wrap.jar:/bea/weblogic
700/server/lib/log4j.jar:/bea/weblogic700/server/lib/Opta2000.jar:/bea/weblogic700/server/lib/xmlx.jar:/bea/weblogic700/server/lib/VelisAuth.jar:/bea/weblogic700/server/lib/jython.jar:/usr/java131/lib/tools.jar:/bea/weblogic700/server:/bea/weblogic700/server/lib/weblogic_sp.jar:/bea/weblogic700/server/lib/weblogic.jar:,
-d, tmp_ejbsmeap01ibm7001myserver/-
        at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java(Compiled
Code))
        at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
        at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:490)
        at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:793)
        at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1242)
        at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:242)
        at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java(Compiled
Code))
        at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java(Compiled
Code))
        at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java(Compiled
Code))
        at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java(Compiled
Code))
        at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java(Compiled
Code))
        at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)


This may happen because javac is not available to weblogic.
Make sure that PATH environment variable used to start the server includes path to Java SDK bin dir with javac in it.
Regards,
Slava Imeshev
"Jennifer" <[email protected]> wrote in message news:[email protected]...
>
Hello
I am trying to deploy EJB 2.0, to Weblogic 7.0 server on IBM machine and i am
getting this following error. Previously I have tested deploying the same EJB
to weblogic 7.0 server on my local PC which based on Windows, and everything seems
Ok.
Unable to deploy EJB: DACEJB.jar from DACEJB.jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath,
/bea/weblogic700/server/bin/tmp_ejbsmeap01ibm7001myserver/-1spvbzuqlvq3z:/bea/weblogic700/server/bin/DACEJB.jar:/usr/java131/jre/lib/rt.jar:/usr/java131/jre/lib/i18n.jar:/usr/java131/jre/classes:/CMS/CORP/config/:/bea/weblogic700:/bea/weblogic700/server/lib/crack.jar:/bea/weblogic700/server/lib/classes12_g.jar:/bea/weblogic700/server/lib/HostMsgDriverV2.1_oracle.jar:/bea/weblogic700/server/lib/aal2wrap.jar:/bea/weblogic>700/server/lib/log4j.jar:/bea/weblogic700/server/lib/Opta2000.jar:/bea/weblogic700/server/lib/xmlx.jar:/bea/weblogic700/server/lib/VelisAuth.jar:/bea/weblogic700/server/lib/jython.jar:/usr/java131/lib/tools.jar:/bea/weblogic700/server:/bea/weblogic700/server/lib/weblogic_sp.jar:/bea/weblogic700/server/lib/weblogic.jar:,> -d, tmp_ejbsmeap01ibm7001myserver/->>>         at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java(Compiled> Code))>         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)>         at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:490)>         at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:793)>         at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1242)>         at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:242)>         at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java(Compiled> Code))>         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java(Compiled> Code))>         at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java(Compiled> Code))>         at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java(Compiled> Code))>         at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java(Compiled> Code))>         at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)>         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))>         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)>

Error deploying EJB on weblogic: Unable to set the transaction attribute

Hi,
I'm trying to deploy an application in WL10.3.2 and an error occurred during activation of changes.
Here is the error message from the log file:
<Jun 6, 2011 1:28:27 PM MDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'serverEAR-2' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
weblogic.application.ModuleException: Exception preparing module: EJBModule(serverEJB-2.8.0.jar)
Unable to deploy EJB: C:\oracle\Middleware\user_projects\domains\base_domain\servers\Server_3\tmp\_WL_user\serverEAR-2\1zw7ao\serverEJB-2.8.0.jar from serverEJB-2.8.0.jar:
Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:454)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
     Truncated. see log file for complete stacktrace
Caused By: weblogic.ejb.container.deployer.DeploymentDescriptorException: Unable to set the transaction attribute for method 'saveActionGroup(EditableActionGroup)' on EJB 'ViewBean'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Remote interface for this EJB.
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processCTs(MBeanDeploymentInfoImpl.java:1502)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.processSpecificMethodCTs(MBeanDeploymentInfoImpl.java:1472)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:773)
     at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:259)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1190)
     Truncated. see log file for complete stacktrace
Please help me...Thanks.

In your ejb-jar.xml you are referring to a method saveActionGroup(EditableActionGroup) which is not defined in your remote interface.
Maybe you have made some typo in the configuration. Check your transaction section, i.e.,
<container-transaction>
            <method>
                <ejb-name>ViewBean</ejb-name>
                <method-name>saveActionGroup</method-name>
                <method-params>
                    <method-param>package.EditableActionGroup</method-param>
                </method-params>
            </method>
            <trans-attribute>Required</trans-attribute>
</container-transaction>or something similar. See if the defined methods are corresponding to the methods defined in the remote interface.

Package and deploy ejb in weblogic 10.3.4?

When I deploy my EAR file then the EJBs contained within do not show up in the weblogic consoles JNDI viewer. I made a simple testcase with a local interface and a stateless impl class, nothing else.
Interface class:
package test;
import javax.ejb.Local;
@Local
public interface TestLocal {
     public String hello();
Impl class:
package test.impl;
import javax.ejb.Stateless;
import testl.TestLocal;
@Stateless(name="test", mappedName="test")
public class TestImpl implements TestLocal {
     @Override
     public String hello() {
          return "hello";
Thats all the ejb jar contains. Its packaged in an EAR file with an META-INF/application.xml containing:
<?xml version="1.0" encoding="UTF-8"?>
<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5">
<display-name>myapp</display-name>
<module>
<web>
<web-uri>web-0.0.1-SNAPSHOT.war</web-uri>
<context-root>/web</context-root>
</web>
</module>
<module>
<ejb>ejb-0.0.1-SNAPSHOT.jar</ejb>
</module>
<library-directory>lib</library-directory>
</application>
Am I missing something in my packaging? I have no EJB descriptor but that should be OK with java ee 5.

I found out weblogic dosent expose local interfaces in the global jndi tree because its not required by ejb 3.0 (but will be in 3.1?). I had to add this to web.xml:
     <ejb-local-ref>
          <ejb-ref-name>ejb/Test</ejb-ref-name>
          <local>test.TestLocal</local>
     </ejb-local-ref>
Now I can get hold of the bean from the war using :
TestLocal test = (TestLocal) ctx.lookup("java:comp/env/ejb/Test");

Deploying EJB in Weblogic 8.1 very very urgent

Hi
I had followed the logic Mr Mark has told me. But it did not work. Please
the attached files.
1. I had copied all of my class files into META-INF directory.
my SampleObject.jar file contains as follows.
jar -tvf SampleObject.jar gives
.META-INF
.Sample.class, SampleHome.class, SampleBean.class, SampleClient.class and
ejb-jar.xml,
weblogic-ejb-jar.xml files.
I did not package my class files. instead i had deployed it in META-INF.
Further I made one more attempt as follows.
My server is called myserver.
so I copied all of my class files, SampleObject.jar files into the following
directory.
C:\bea\user_projects\domains\mydomain\myserver\upload directory. This is the
directory
where weblogic copies the SampleObject.jar files.
It did not work at all.
Please help me.
I am failing for the past five days . Treat this as very urgent.
Thanks in advance.

Murali:
I suggest you start with something simple that works. And then go from
there, modifing it one bit at a time and ensuring that it still works. Your
jar tf output is all munched up so it is hard to follow. I suggest you
start with
$WL_HOME/samples/server/examples/src/examples/splitdir/helloWorldEar/
See how it builds the ear and the ejb jars and go from there.
You can do:
ant ear
and
examine the contents from there.
Alternatively you can use Workshop to build an EJB as well.
PS. Your classes dont go into META-INF. But rather than go through the
entire exercise of getting your app working I suggest as noted above you
start from a known and modify.
cheers
mbg
"Murali" <[email protected]> wrote in message
news:3fc08518$[email protected]..
>
Hi
I had followed the logic Mr Mark has told me. But it did not work.Please
the attached files.
1. I had copied all of my class files into META-INF directory.
my SampleObject.jar file contains as follows.
jar -tvf SampleObject.jar gives
.META-INF
.Sample.class, SampleHome.class, SampleBean.class, SampleClient.classand
ejb-jar.xml,
weblogic-ejb-jar.xml files.
I did not package my class files. instead i had deployed it in META-INF.
Further I made one more attempt as follows.
My server is called myserver.
so I copied all of my class files, SampleObject.jar files into thefollowing
directory.
C:\bea\user_projects\domains\mydomain\myserver\upload directory. This isthe
directory
where weblogic copies the SampleObject.jar files.
It did not work at all.
Please help me.
I am failing for the past five days . Treat this as very urgent.
Thanks in advance.

Deploying EJB on weblogic 5.1

Hi All:
I am relatively new to EJBs and their deployment. I hv developed a small EJB application with a session bean. When I try to compile it using "java weblogic.ejbc", I get the following error:
java weblogic.ejbc j.jar s.jar
org.xml.sax.SAXException: Could not locate a local resource corresponding to public Id -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN.
Is the XML DOCTYPE header correct?
at weblogic.ejb.deployment.xml.EJBEntityResolver.resolveEntity(EJBEntityResolver.java:55)
at com.sun.xml.parser.ExternalEntity.getInputSource(ExternalEntity.java:46)
at com.sun.xml.parser.Parser.pushReader(Parser.java:2748)
at com.sun.xml.parser.Parser.externalParameterEntity(Parser.java:2500)
at com.sun.xml.parser.Parser.maybeDoctypeDecl(Parser.java:1136)
at com.sun.xml.parser.Parser.parseInternal(Parser.java:480)
at com.sun.xml.parser.Parser.parse(Parser.java:283)
at weblogic.xml.dom.SunDOMParser.getDocument(SunDOMParser.java:69)
at weblogic.xml.dom.DOMParser.getDocument(DOMParser.java:102)
at weblogic.ejb.deployment.dd.DescriptorLoader.<init>(DescriptorLoader.java:151)
at weblogic.ejbc.runBody(ejbc.java:298)
at weblogic.utils.compiler.Tool.run(Tool.java:80)
at weblogic.ejbc.main(ejbc.java:353)
--------------- nested within: ------------------
Received SAXException from Sun Parser: org.xml.sax.SAXException: Could not locate a local resource corresponding to public Id -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN.
Is the XML DOCTYPE header correct?
at weblogic.xml.dom.SunDOMParser.getDocument(SunDOMParser.java:72)
at weblogic.xml.dom.DOMParser.getDocument(DOMParser.java:102)
at weblogic.ejb.deployment.dd.DescriptorLoader.<init>(DescriptorLoader.java:151)
at weblogic.ejbc.runBody(ejbc.java:298)
at weblogic.utils.compiler.Tool.run(Tool.java:80)
at weblogic.ejbc.main(ejbc.java:353)
ERROR: Received SAXException from Sun Parser: org.xml.sax.SAXException: Could not locate a local resource corresponding to public Id -//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN.
Is the XML DOCTYPE header correct?
My ejb-jar.xml file looks like below:
<?xml version="1.0"?>
<!DOCTYPE ejb-jar PUBLIC
"-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"
"http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<ejb-name>IDBean</ejb-name>
<home>IDCommon.IDHome</home>
<remote>IDCommon.ID</remote>
<ejb-class>IDCommon.IDBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<enterprise-beans>
<assembly-descriptor>
<security-role>
<role-name></role-name>
</security-role>
<method-permission>
<role-name></role-name>
<method>
<ejb-name>IDBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<method>
<ejb-name>IDBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
I would deeply appreciate any help/advise in this regard as my head is really blowing up..
Thanx a ton in advance..
Rgds,
J

Hi,
Can you try deploying it by chaning the content of the DOCTYPE element to
<!DOCTYPE ejb-jar PUBLIC
'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN'
'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>.
and let me know whether you are able to deploy after that or not. you can mail me at [email protected]
Regards
Mahe

How to hot deploy EJB in Weblogic?

Hi all,
We use Weblogic 10.3 and EJB3.
EJB has been build as ear and deployed in the server. And other deployed modules in server calls that.
But the modification of EJB need to be rebuilt and restart the server.
Does Weblogic support hot deploy for EJB? Do we need plugin or something else for this feature?
Thanks a lot.

Hi,
The production redeployment strategy/hot deployment is supported for:
a. Standalone Web Application (WAR) modules and Enterprise applications (EARs) whose clients access the application via a Web application (HTTP).
b. Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.
c. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.
Production redeployment is not supported for:
a. Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.
b. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC for Oracle WebLogic Server.
c. Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.
d. Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.
Please check the below Doc
http://docs.oracle.com/cd/E14571_01/web.1111/e13702/redeploy.htm#
Hope this answers your question!!
Thanks,
Vijaya

Trouble accessing a deployed EJB on WebLogic 6.1

I have "installed and deployed" an EJB jar file as directed in the WebLogic documentation. However, when I then try to reference the Remote or Home interfaces from a JSP page, I get a compile error that neither could be found. For example, it doesn't like the "(Company)" in the class-cast:company = (Company)companyHome.findByPrimaryKey( pkValue );I am using WebLogic 6.1 and the "deployment steps" I have followed are:
1) Coded and complied the bean implementation, remote interface, and home interface;
2) created an ejb-jar.xml deployment descriptor file;
3) created a weblogic-ejb-jar.xml deployment descriptor;
4) ran jar on the 3 class files and 2 xml files;
5) ran the weblogic.ejbc utility on the above jar file;
6) installed the EJB by uploading the jar file from step 5 through the admin console;
7) set the appropriate server as the target of the EJB deployment.
All these steps proceeded without issue, but as I mentioned before, I am unable to reference any of the elements of the EJB deployment.
Is there something I missed? Did I do some steps incorrectly? Has anyone run into this before? What was the resolution?
Thanks in advance for any help...

HI
I WOULD TRY MY LEVEL BEST TO SOLVE UR PROBLEM IF U CAN EXPLAIN UR PROBLEM A LITTLE MORE BRIEFLY.
MY MAIL ADDRESS: [email protected]
After a little more fact finding, I found that the
remote and home interfaces must be made seperately
available to WebLogic's JSP engine (thanks to an EJB
newsgroup post). So I added an additional step to the
list above by taking the home and remote interface
class files and copying them over to the webapp's
WEB-INF/classes directory and ensuring that this
directory is in the CLASSPATH during WebLogic
startup.
It is still not able to resolve the reference, though.
Any other thoughts?

Deployment procedure in weblogic 6.0 server

Hi i worked in weblogic 5.1 server.
can you explain the deployment steps in weblogic6.0 server

Hi Raj.
There are 3 different situations for you to deploy EJBs into WLS 6.*:
1) Deploying EJBs at WebLogic Server Startup.
2) Deploying EJBs on a Running WebLogic Server.
3) Deploying New EJBs into a Running Environment.
as you can find all the details on http://edocs.bea.com/wls/docs61/ejb/deploy.html#1050867.
We suggest to use WLS6.1 on line doc since it is revamped version.
If you have a particular question for WLS 6.0 EJB deployment, we support you to open
an eval support case to BEA Weblogic support.
Thanks.
Ji Zhang
Developer Relations Engineer
BEA Support

Error while deploying EJB 1.1 on Weblogic 10.3.0.0

I am trying to deploy an EJB (1.1) jar which is succesfully running on JBoss5.0 on WebLogic 10.3.0.0; I am getting following Error while deploying the jar on weblogic;
Exception preparing module: EJBModule(ejb_RemoteServicesEjb) Unable to deploy EJB: RemoteServicesEjb.jar from RemoteServicesEjb.jar: There are 1 nested errors: weblogic.ejb.container.compliance.ComplianceException: In EJB com.package.ejbimpl.RemoteServicesEjb, the throws clause for ejbCreate method ejbCreate() contains exceptions that are NOT in the throws clause of the corresponding home interface method. at weblogic.ejb.container.compliance.HomeInterfaceChecker.checkCreateMethodsMatchBeanCreates(HomeInterfaceChecker.java:365) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.ejb.container.compliance.EJBComplianceChecker.check(EJBComplianceChecker.java:337) at weblogic.ejb.container.compliance.EJBComplianceChecker.checkDeploymentInfo(EJBComplianceChecker.java:286) at weblogic.ejb.container.ejbc.EJBCompiler.complianceCheckJar(EJBCompiler.java:952) at weblogic.ejb.container.ejbc.EJBCompiler.checkCompliance(EJBCompiler.java:920) at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:246) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:552) at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:519) at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:393) at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:715) at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:618) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1154) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:425) 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.SingleModuleDeployment.prepare(SingleModuleDeployment.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.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Does anybody knows what must be going wrong?
Can't I deploy EJB 1.1 jar directly on Weblogic 10.3.0.0 or I need to change or configure something before doing it?

Does the ejbCreate() method of the com.package.ejbimpl.RemoteServicesEjb class have an exception on it's throws clause that is not present on the ejbCreate() method of your home interface? If so, does the error go away if you add the exception to the home's ejbCreate() method? In general, you want checked exceptions in a throws clause to match between the interface declaration of the method and the implementation of the method on the bean class.
- Matt

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.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.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.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.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

Weblogic Server 8.1 giving weird error while deploying EJB

Hi All,
I am using weblogic8.1 server with service pack 4.
I am trying to deploy an entitybean (ejb2.0) specification. I am getting following error.
==========================================================
[Deployer:149033]preparing application sum.LDN on MyServer
[Deployer:149033]failed application sum.LDN on MyServer
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application sum.LDN on MyServer.:
Exception:weblogic.management.ApplicationException: prepare failed for sumEJB.jar
Module: sumEJB.jar Error: Exception preparing module: EJBModule(sumEJB.jar,status=NEW)
Unable to deploy EJB: sumEJB.jar from sumEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
In bean com.csfb.csar.sum.ods.TradeSetlmtMapping, the abstract method, getHandle(), does not correspond to any container-managed field and is not implemented in the bean class or any of its superclasses.
In bean com.csfb.csar.sum.ods.TradeSetlmtMapping, the abstract method, getEJBHome(), does not correspond to any container-managed field and is not implemented in the bean class or any of its superclasses.
In bean com.csfb.csar.sum.ods.TradeSetlmtMapping, the abstract method, isIdentical(javax.ejb.EJBObject), does not correspond to any container-managed field and is not implemented in the bean class or any of its superclasses.
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:255)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:476)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:407)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:493)
at weblogic.ejb20.deployer.EJBDeployer.compileJar(EJBDeployer.java:784)
at weblogic.ejb20.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:700)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1339)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
==========================================================
This is very surprising error I am getting. Because getHandle(), getEJBHome(), isIdentical() are no where declared in business interface extending EJBObject.
Descriptor File is perfectly fine.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
<weblogic-rdbms-bean>
<ejb-name>com.csfb.csar.sum.ods.TradeSetlmtMapping</ejb-name>
<data-source-name>com.csfb.csar.ODSDataSource</data-source-name>
<table-map>
<table-name>ODS_CNS_ELIGIBLE_TRADES</table-name>
<field-map>
<cmp-field>auditCreatedDate</cmp-field>
<dbms-column>STAMP_ADD_DTIME</dbms-column>
</field-map>
<field-map>
<cmp-field>auditCreatedBy</cmp-field>
<dbms-column>PROCESS_ADD_ID</dbms-column>
</field-map>
<field-map>
<cmp-field>transId</cmp-field>
<dbms-column>TRANS_ID</dbms-column>
</field-map>
<field-map>
<cmp-field>transVersId</cmp-field>
<dbms-column>TRANS_VERS_ID</dbms-column>
</field-map>
<field-map>
<cmp-field>transItemSequenceId</cmp-field>
<dbms-column>TRANS_ITEM_SEQUENCE_ID</dbms-column>
</field-map>
<field-map>
<cmp-field>externalReference</cmp-field>
<dbms-column>EXTERNAL_REFERENCE</dbms-column>
</field-map>
<field-map>
<cmp-field>setLmtStatus</cmp-field>
<dbms-column>SETLMT_STATUS</dbms-column>
</field-map>
<field-map>
<cmp-field>setLmtDate</cmp-field>
<dbms-column>SETLMT_DATE</dbms-column>
</field-map>
<field-map>
<cmp-field>stampUpdateDtime</cmp-field>
<dbms-column>STAMP_UPDATE_DTIME</dbms-column>
</field-map>
</table-map>
<weblogic-query>
<query-method>
<method-name>findAll</method-name>
<method-params/>
</query-method>
</weblogic-query>
</weblogic-rdbms-bean>
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Please Help..

<p>I could not find any documentation that suggested LIMIT or OFFSET where supported. Some of our developers needed to use limit, in the end all I could suggest was using a dynamic query and setting the maximum number of results see here
.</p>
<p>
Hussein Badakhchani</br>
</p>

Log4j error while deploying EJB 3.0 in weblogic 10

Hi Friends,
I am migrating an application EJB from 2.0 to 3.0 annotations.
The log4j-1.2.3 for the project is configured in this way, it is added to the startWeblogic.cmd in weblogic 10 as :
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dlog4j.configuration=log4j.properties
Now i am trying to deploy my EAR file that contains an EJB 3.0 Project and a Web project , it gives following error while deployment.
###<Jan 29, 2010 8:21:01 PM EST> <Warning> <Deployer> <ALPITSWXP00001> <wlw-pricingdev-s10> <[STANDBY] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1264814461242> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception preparing module: EJBModule(streamlinesuspenseEJB.jar)
[EJB:011023]An error occurred while reading the deployment descriptor. The error was:
org.apache.log4j.spi.RootCategory.<init>(Lorg/apache/log4j/Level;)V.
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:452)
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.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.NoSuchMethodError: org.apache.log4j.spi.RootCategory.<init>(Lorg/apache/log4j/Level;)V
at org.apache.log4j.LogManager.<clinit>(LogManager.java:113)
at org.apache.log4j.Logger.getLogger(Logger.java:124)
at com.jmfamily.common.log.LogManager.getLogger(LogManager.java:33)
at com.jmfamily.common.log.LogManager.getLogger(LogManager.java:42)
at com.jmfamily.jma.contract.ejb.SuspendedContractSOBean.<clinit>(SuspendedContractSOBean.java:33)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at weblogic.ejb.container.dd.xml.EjbAnnotationProcessor.processWLSAnnotations(EjbAnnotationProcessor.java:1699)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.processWLSAnnotations(EjbDescriptorReaderImpl.java:346)
at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:192)
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.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
If i remove the "set JAVA_OPTIONS=%JAVA_OPTIONS% -Dlog4j.configuration=log4j.properties" from the weblogic statrup script and install the EAR it will be installed , but the logger is not initialized.
If the option "set JAVA_OPTIONS=%JAVA_OPTIONS% -Dlog4j.configuration=log4j.properties" added to the startup script and i deployed the OLD EJB 2.0 app , it is installed successfully, but it didnt let me deploy EJB 3.0 app.
I am hitting my head around it for a day now, no success so far..
Please provide you suggestions , thanks a lot to all in advance.
Thanks
Sachin

Does the ejbCreate() method of the com.package.ejbimpl.RemoteServicesEjb class have an exception on it's throws clause that is not present on the ejbCreate() method of your home interface? If so, does the error go away if you add the exception to the home's ejbCreate() method? In general, you want checked exceptions in a throws clause to match between the interface declaration of the method and the implementation of the method on the bean class.
- Matt

Deploying EJB 3.0 MDB on Weblogic 10.3

My MDB is as follows:
package test;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
@MessageDriven(mappedName = "mdb01/queue01",
          activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
public class MDB implements MessageListener {
     public void onMessage(Message message) {
          System.out.println("Received Message: " + message);
While deploying it on WebLogic 10.3 I get the below error:
javax.naming.NameNotFoundException: While trying to lookup 'mdb01.queue01' didn't find subcontext 'mdb01'. Resolved ''; remaining name 'mdb01/queue01'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
Please advise what configurations I should do in WebLogic in order to deploy this MDB.

on WebLogic console, go to the "general" tab of your server's page, and click on "view JNDI tree". there you can see whether your queue has been deployed to the server.
if not there, verify that the queue has been properly targeted. it can be tricky, and I suggest you to use subdeployments.

Probs in Deploying EJB in weblogic 8.1

Similar Messages

Maybe you are looking for