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>

Similar Messages

EJB deployed in Weblogic 10.3 invoking CORBA

Hello,
we are running an EJB3 application deployed in WebLogic 10.3 that must communicate with CORBA.
We're having the following exception when trying to submit an WorkOrder.
javax.ejb.EJBException: EJB Exception: ; nested exception is:
org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: No; nested exception is: org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: No
org.omg.CORBA.MARSHAL: vmcid: 0x0 minor code: 0 completed: No
at weblogic.corba.idl.RemoteDelegateImpl.postInvoke(RemoteDelegateImpl.java:477)
at weblogic.corba.idl.RemoteDelegateImpl.invoke(RemoteDelegateImpl.java:384)
at weblogic.corba.idl.RemoteDelegateImpl.invoke(RemoteDelegateImpl.java:341)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at pt.vodafone.indev.esm.SMSProvExt._WorkOrderIntfStub.submit(_WorkOrderIntfStub.java:183)
at pt.vodafone.in.business.WorkOrderFacade.createWorkOrder(WorkOrderFacade.java:227)
I've searched the forum for similar problems and the solution was to include the wlfullclient.jar in client classpath.
I've done that already however the problem persists. (maybe it's necessary to configure some IIOP parameters)
Anyone have any clue for this problem?
Thanks in advance.
Regards.

Hi,
include wls-api.jar in your classpath and provide me an update...
Regards.
Kal.

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

EJB Deployment in WebLogic 8.1 very very urgent

Hi
In order deploy EJB application in Weblogic 8.1, is it necessary to compile
the application in WebLogic.ejbc. I did not find such files in WebLogic 8.1
In weblogic 7.0 versiion has such files.
The present procedure is as follows.
1. Create a jar file contains all class files.
2. Create a jar file contains class jar files, plus .xml files
3. Deploy into weblogic 8.1 server EJB Deployment utility.
==================
Please help me.
Murali

They are reccomended because the next step going from your simple single EJB
to anything interesting, like adding more EJB's adding web-apps, adding
web-services etc etc involves ears. If the setup and overhead for an EAR is
easy, then just start there.
But no if you just doing helloworld you of course dont have to ears.
cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fc0560e$[email protected]..
>
"Mark Griffith" <[email protected]> wrote:
You can still run ejbc from the command line its still there. And you
can
still run weblogic.Deployer. (I dont ever reccomend jaring up in dev,
it
just takes longer, do exploded its easier and faster).
But ear's are easy, see:So ears are recommended even if you're just doing EJBs (e.g., a simpleHello World)
and no web apps (none needed for the Hello World or a PC client)?
http://www.niffgurd.com/mark/work/blog/
Cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fbfd6c6$[email protected]..
My understanding is ejbc has been deprecated and replaced with appc.Moreover,
BEA is encourgaging developers to deploy ear files. All I want todo is
to use
ant to deploy a jar file with a single EJB in it. I'm not findingthe WL
documentation
very helpful. Hopefully, you'll have better luck than I.
"skmurali" <[email protected]> wrote:
Hi
In order deploy EJB application in Weblogic 8.1, is it necessary
to compile
the application in WebLogic.ejbc. I did not find such files in
WebLogic
8.1
In weblogic 7.0 versiion has such files.
The present procedure is as follows.
1. Create a jar file contains all class files.
2. Create a jar file contains class jar files, plus .xml files
3. Deploy into weblogic 8.1 server EJB Deployment utility.
==================
Please help me.
Murali

EJB deployed but doesnt show up in JNDI tree on weblogic

Hi,
I have a sample EJB deployed on weblogic 10.3 server. My Bean class contains following code.
========================================================================
@Stateless (mappedName = "DemoEJB")
@TransactionManagement(TransactionManagementType.BEAN)
public class DemoBean implements SessionBean {
     static final boolean verbose = true;
     private transient SessionContext ctx;
     private transient Properties props;
     @SuppressWarnings("deprecation")
     @Override
     public void setSessionContext(SessionContext ctx) throws EJBException,
               RemoteException {
          // TODO Auto-generated method stub
          if (verbose)
          System.out.println("setSessionContext called");
          this.ctx = ctx;
          props = ctx.getEnvironment();
     public String demoSelect()
throws RemoteException
return("hello world");
===========================================================================
I have created a jar file for the above class using eclipse and deployed it on weblogic. I can see the EJB in the <Deployment> on weblogic but it doesnt appear in <EJB> on JNDI tree view. Therefore i cannot access it from my client code (also written in Eclipse IDE).
I will appreciate any guidance in this regard.
Thanks
Regards,
Awais

Hi,
i have the same problem with yours
This is my annotation with EJB3.0:
@Stateless(mappedName="ConSession")
@Remote(ConBeanRemote.class)
@Local(ConBean.class)
and i have a weblogic-ejb-jar.xml to define my jndi name
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-ejb-jar"
          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/ejb-jar_3_0.xsd
          http://www.bea.com/ns/weblogic/weblogic-ejb-jar
          http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
     <ejb-name>ConSession</ejb-name>
<stateless-session-descriptor>
     <business-interface-jndi-name-map>
          <business-remote>com.staffware.ConBeanRemote</business-remote>
          <jndi-name>ConSession#com/staffware/ConBeanRemote</jndi-name>
          </business-interface-jndi-name-map>
          </stateless-session-descriptor>
          <local-jndi-name>com/ConfigurationManagerBeanLocal</local-jndi-name>
     </weblogic-enterprise-bean>
</weblogic-ejb-jar>
[ the most important：　I also have specify JNDI in a java file like this
          beanRemoteJNDIs.put("ConBeanRemote","ConSession#com/staffware/ConBeanRemote");
          beanLocalJNDIs.put("ConBean","java:comp/env/com/ConBean");
and i can find the ConSession#com/staffware/ConBeanRemote in the jndi tree . but it shows like Multilevel directory tree
and when i login the website and click the button
.another error comes out :
13:35:55,046 ERROR [EJBDelegate] Unable to lookup reference java:comp/env/com/ConBean for ConBean!
javax.naming.LinkException: [Root exception is javax.naming.LinkException: [Root exception is javax.naming.NameNotFoun
dException: While trying to look up /app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home in /app/webapp/CO
M/18328287.; remaining name '/app/ejb/CONFIG-ejb-2/0/jar#ConfigurationManagerSession/local-home']; Link Remaining Name:
'java:app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home']; Link Remaining Name: 'com/ConBean'
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:104)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:884)
at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:187)
what should i do ?
and should i specify the jndi name in the java file . the JNDI name defined in the weblogic is right?
can you help me ?
thanks very much in advance!

EJB communication between weblogic and websphere

Hello:
I have weblogic 7.1 instance running in machine A and websphere running in machine B. I want to make a call to the ejb deployed from weblogic to websphere. Any experience in this would be very helpful. Or pl. post the procedure.
Thx in advance.

I don't think that there is any magic here, although I've never tried it.
All you need is the compiled EJBHome and EJBObject interfaces in the
classpath of the calling EJB, get an InitialContext in the JNDI namespace of
the target EJB container using the name of the JNDI InitialContext Factory,
do a lookup on the bean making sure to do a PortableRemoteObject.narrow when
you are casting the Home stub with the vendor specific version of
PortableRemoteObject(and that may be the real trick), call the appropriate
create method, and you are rolling.
I guess the question becomes how to make sure that when you are calling
PortableRemoteObject.narrow on the Home stub, that you get the vendor
specific version for the EJB container and JNDI namespace from which you are
doing the lookup.
I guess the answer is, I'm guessing. Have you tried it?
bill
"nebs om" <[email protected]> wrote in message
news:30035468.1103738722864.JavaMail.root@jserv5...
Hello:
I have weblogic 7.1 instance running in machine A and websphere runningin machine B. I want to make a call to the ejb deployed from weblogic to
websphere. Any experience in this would be very helpful. Or pl. post the
procedure.
>
Thx in advance.

Ejb deployment - classloader question

Hi Guys
I have a very basic question regarding EJB deployment in Weblogic 6.1 sp2.
Is it possble to create an EAR file such that -
1>it contains a WAR file [of servlets/jsps/client classes] - A
2>a jar file containing our core server classes[not EJBs] - B
3>a jar file containing EJBs - C
here A and C are definitely getting loaded by different class loaders - I want
the classloader for B to be parent of the classloaders for A and C - so that both
A and C can see B. - is this possible by some EAR/Weblogic specific way.
OR
the best solution is to place the B in the main classpath and deploy the C and
A in an EAR?
thanks
Anamitra

Inline.
Anamitra wrote:
Hi Guys
I have a very basic question regarding EJB deployment in Weblogic 6.1 sp2.
Is it possble to create an EAR file such that -
1>it contains a WAR file [of servlets/jsps/client classes] - A
2>a jar file containing our core server classes[not EJBs] - B
3>a jar file containing EJBs - C
here A and C are definitely getting loaded by different class loaders - I want
the classloader for B to be parent of the classloaders for A and C - so that both
A and C can see B. - is this possible by some EAR/Weblogic specific way.Made possible by placing B in the ear at the root level and referring to B with the
Class-Path manifest directive in the ejb jar file for C. This will put B in the ejb
classloader's classpath making it visible to C and to A since the classloader for C
is the parent of the classloader for A. Which, is the recommended way.
>
OR
the best solution is to place the B in the main classpath and deploy the C and
A in an EAR?
This works, but the classfiles in B are now static for the uptime of the server. If
you want to make changes in B, you must restart the server. If you configure it the
way described above, you can reload the B classes by redeploying the application ear.
>
thanks
AnamitraHere is the link with all of the info:
http://edocs.bea.com/wls/docs61/programming/packaging.html#1029830
Bill

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.

Steps to deploy an ejb application and running an ejb client in weblogic server6.1

steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet

Hi.
Check out the beanManaged example that ships with WLS and read the accompanying docs. This
is a simple EJB with a servlet that invokes it.
Michael
shekhar sachdev wrote:
steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
if the client is an simple java application and if the client is a servlet--
Michael Young
Developer Relations Engineer
BEA Support

Memory leak in a client using EJBs deployed in a Bea Weblogic 10.0.0 cluste

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

Hi all,
We are having a memory leak in a client using stateless EJBs deployed in cluster. The client is a Tomcat 6.0.18 with java 6 but it is reproduced using Tomcat 5 with java 5. The client is calling a Weblogic Server 10.0 making
calls to an EJB deployed in cluster that has two instances installed in two different machines.
The client works fine if we shutdown one of the server instances and so when the client is using only one instance.
Resuming the environment:
Client Side:
1 HP-Itanium machine with HP-UX.
1 Tomcat 6 with java 6 (reproduced with java 5)
Bea Weblogic client (wlclient.jar) for Weblogic 10.0.0
Server Side:
2 HP-Itanium machines with HP-UX
Bea Weblogic Server 10.0.0 installed in both machines
An unique domain
Two Bea instances (one per machines) associated to a Bea Cluster
EJBs deployed in both instances
We have monitored the memory consumed in Tomcat and we have noticed that the VM memory PS OLD GEN grows up permanently when we make tests having the two server side Bea Instances up. We have extended
the memory VM parameters in Tomcat client till 1G and it's only a way to delay the end: the free memory is empty, the GC is not able to free no more byte and the CPU is 100% consumed by the GC work. At the end Tomcat Client
doesn't accept more http petitions and must be restarted.
Besides, we have studied the VM memory in Tomcat using jmap and importing it using Eclipse Memory Analyzer. We have seen some strange memory blocks of several Mbytes that are always growing up and that are stored
under data structures in the package com.sun.corba:
com.sun.corba.se.impl.legacy.connection.SocketFactoryConnectionImpl (4.5Mb)
|
-> com.sun.corba.se.impl.transport.CorbaResponseWaitingRoomImpl
|
-> java.util.Hashtable
|
-> java.util.Hashtable$Entry
|
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
-> java.util.Hashtable$Entry
Has anybody any idea about this problem?
Thanks in advance.

EJB Deployment error in Weblogic 8.1 very urgent

Hi
Mark I forgot to send my error message. So I am sending again.
Sorry for the trouble.
Murali
[weblogicerr1.txt]

They are reccomended because the next step going from your simple single EJB
to anything interesting, like adding more EJB's adding web-apps, adding
web-services etc etc involves ears. If the setup and overhead for an EAR is
easy, then just start there.
But no if you just doing helloworld you of course dont have to ears.
cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fc0560e$[email protected]..
>
"Mark Griffith" <[email protected]> wrote:
You can still run ejbc from the command line its still there. And you
can
still run weblogic.Deployer. (I dont ever reccomend jaring up in dev,
it
just takes longer, do exploded its easier and faster).
But ear's are easy, see:So ears are recommended even if you're just doing EJBs (e.g., a simpleHello World)
and no web apps (none needed for the Hello World or a PC client)?
http://www.niffgurd.com/mark/work/blog/
Cheers
mbg
"Christopher R. Gardner" <[email protected]> wrote in message
news:3fbfd6c6$[email protected]..
My understanding is ejbc has been deprecated and replaced with appc.Moreover,
BEA is encourgaging developers to deploy ear files. All I want todo is
to use
ant to deploy a jar file with a single EJB in it. I'm not findingthe WL
documentation
very helpful. Hopefully, you'll have better luck than I.
"skmurali" <[email protected]> wrote:
Hi
In order deploy EJB application in Weblogic 8.1, is it necessary
to compile
the application in WebLogic.ejbc. I did not find such files in
WebLogic
8.1
In weblogic 7.0 versiion has such files.
The present procedure is as follows.
1. Create a jar file contains all class files.
2. Create a jar file contains class jar files, plus .xml files
3. Deploy into weblogic 8.1 server EJB Deployment utility.
==================
Please help me.
Murali

Weblogic EJB Deployment Descriptor

Hi,
Can someone help me in learning how to write weblogic specific deployment descriptors for EJBs ??? Where can I find good tutorial or help. I am new to EJB.
Thank you in advance

Why not search http://bea.com and see what pops up. I searched their site for "EJB deployment descriptors" and got quite a few hits.

Hi i when i am trying to deploy an EJB module on weblogic server i get the

Hi all,
when i am trying to deploy an EJB module on weblogic server i get the the following exception on the server.
Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
[Deployer:149033]preparing application test on myserver
[Deployer:149033]failed application test on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application test on myserver.: Exception:weblogic.management.ApplicationException: prepare failed for test Module: test Error: Exception preparing module: EJBModule(test,status=NEW) Unable to deploy EJB: D:\bea\weblogic81b\server\bin\myserver\upload\test.jar from test.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'HelloBean' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:525) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.(MBeanDeploymentInfoImpl.java:230) at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1256) at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:449) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:2792) at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1478) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1136) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:975) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2571) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2523) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2453) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:820) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:536) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:494) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread

Hi, i am also facing the same problem.......
my ejb-jar.xml is
<?xml version="1.0" encoding="UTF-8"?>
<!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 >
<description><![CDATA[No Description.]]></description>
<display-name>Generated by XDoclet</display-name>
<enterprise-beans>



<entity >
<description><![CDATA[Description for Account]]></description>
<display-name>Name for Account</display-name>
<ejb-name>Account</ejb-name>
<home>com.app.j2ee.bmp.interfaces.AccountHome</home>
<remote>com.app.j2ee.bmp.interfaces.Account</remote>
<local-home>com.app.j2ee.bmp.interfaces.AccountLocalHome</local-home>
<local>com.app.j2ee.bmp.interfaces.AccountLocal</local>
<ejb-class>com.app.j2ee.bmp.ejb.AccountBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.app.j2ee.bmp.interfaces.AccountPK</prim-key-class>
<reentrant>False</reentrant>
          <resource-ref>
          <res-ref-name>jdbc/ejbPool</res-ref-name>
          <res-type>javax.sql.DataSource</res-type>
          <res-auth>Container</res-auth>
          </resource-ref>
</entity>
</enterprise-beans>



<assembly-descriptor >










<container-transaction>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Local</method-intf>
          <method-name>*</method-name>
          </method>
          <method>
          <ejb-name>Account</ejb-name>
          <method-intf>Remote</method-intf>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
     </container-transaction>
</assembly-descriptor>
</ejb-jar>

Can Oracle SQL Flavor be used When BC4J is deployed in WebLogic as EJB?

Hi,
Does anybodys know if Oracle SQL Flavor can be used When BC4J is deployed in WebLogic as EJB?
We succeeded in deploying BC4J to WebLogic 7.0 & 6.0, but we had to select the SQL92 option for SQL Flavor when the first BC package is created in a project. Selecting Oracle option for SQL Flavor will cause EJB to fail, and client get a ClassCastException.
We still want to use Oracle SQL, is it possible to use it with WebLogic?
Thanks.

We figured out that Oracle SQL Flavor can be used with WebLogic, but only with DB connections created from JDBC URL, not work with DB connections from WebLogic connection pool.

EJB deployment in weblogic 8.1

Similar Messages

Maybe you are looking for