CacheFullException with Stateless bean

Hallo everbody,
I have a problem with a Stateless bean the log file give me this error:
javax.ejb.EJBException: Exception during transition from pooled to ready:
- with nested exception:
[weblogic.ejb20.cache.CacheFullException: Cache is at its limit of: '100' *active*
beans.]
I use this bean for several action, and just for an action I have this error.
What I can't underastand that Stateless bean get with the session and as the user
close the session the Bean have to expire, isn'it? So can't uderstand while 100
Bean still on the cache.
Could anyone help me?
Thank's a lot
Fausta

1. check thread dump ... any threads actually still busy?
2. is it stateful or is it stateless? I don't mean how do you deploy it, but
I mean which is it really? does it have any state?
3. always call remove() ... this isn't the problem (Weblogic doesn't require
remove()) but you should do so anyway.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Sachin Shah" <[email protected]> wrote in message
news:[email protected]..
>
Hi,
I have a statelesss session bean which i m using in the application.Initially
this bean was stateful bean but due to problems of timeout it was changedto stateless
bean. The problem is sometimes when i view the statistics from console, ifind
that there are max 20 beans allowed and all 20 are in use. Because ofwhich no
user can work further and i have to shutdown the server. I fail tounderstand
this cause being a stateless session bean it should be released (returnedto free
pool) as soon as the method is over. So why this behaviour. Any idea.
Thanks in Advance

Similar Messages

Performance of Session Stateless Bean in WebSphere with connection to DB

Im using WebSphere Advanced Single Server Edition Version 4.0.1. and a WebSphere DataSource to get my connections to Microsoft SQL 2000 (using netdirect's JSQLDriver).
For the EJB I set the transaction to 'requieresNew'.
For testing purposes I had been testing some code I'll be using in a Session Stateless Bean inside a servlet's method. In my servlet I use one single connection and preparedStatements to improve performance.
When I test it on the Servlet, this process takes around 3 minutes to complete, but when I put this code inside a Session Stateless Bean and call it from this servlet's method, it takes around 30 minutes to complete!. How is this possible?!
Worst of all, when the EJB ends and the process returns to the Servlet, it throws me this exception.
com.ibm.websphere.ce.cm.StaleConnectionException: class com.ibm.ejs.cm.proxy.PreparedStatementProxy is closed.
The code uses some utilities from a Framework we created, but I really doubt it affects the performance since I put such classes in a jar file and the EJB is accessing such classes correctly.
I thought that maybe I was missing something related with how I get the connection inside the EJB, but I had no luck trying to figure this out.
This is the code in my EJB, commented code was in use when this code was tested in the method of the servlet (some code has been removed or modified, so I just left the 'main' body of the code):
package cmx.ejb;
import cmx.common.*;
import java.util.*;
import qsi.sys.db.*;
import qsi.sys.util.*;
import java.rmi.*;
import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;
import java.util.*;
import javax.ejb.*;
import javax.naming.*;
import javax.rmi.*;
import javax.sql.DataSource;
* Bean implementation class for Enterprise Bean: SimuladorEJB
public class SimuladorEJBBean implements javax.ejb.SessionBean {
     private javax.ejb.SessionContext mySessionCtx;
private Context ctx;
private DataSource ds;
private static final int TCONSUMO = 4;
private static final int CARACEQ = 6;
private static final int PPRODUC = 9;
private static final int PPUNTA = 12;
private static final int UTONHR = 8;
private static final int TPRODUCC = 3;
private Vector val = null;
private Vector vecArea = null;
private String query;
private Object[] params;
private int numAreas;
private int vSecDetHE;
//All the prepared statements I'll use in my process
private PreparedStatement pstmSelectSerial = null;
private PreparedStatement pstmUpdateSerial = null;
private PreparedStatement pstmgetPPEquipos = null;
private PreparedStatement pstmgetTransfers = null;
private PreparedStatement pstmaddRProduccion = null;
private PreparedStatement pstmupdInventario = null;
private PreparedStatement pstmgetServicios = null;
private PreparedStatement pstmaddConsumo = null;
private PreparedStatement pstmgetAreaEquipos = null;
private PreparedStatement pstmfindCE = null;
private PreparedStatement pstmcontEventoLogEq = null;
private PreparedStatement pstmaddLog = null;
private PreparedStatement pstmfindCaract = null;
private PreparedStatement pstmfindComposicion = null;
private PreparedStatement pstmfindCombAlt = null;
private PreparedStatement pstmaddInventarioH = null;
private PreparedStatement pstmgetAlmMatREM = null;
private PreparedStatement pstmfindAlmacen = null;
private PreparedStatement pstmcontEventoLogAlm = null;
private PreparedStatement pstmgetAlmacenes = null;
private PreparedStatement pstmfindInvHora = null;
private PreparedStatement pstmgetPeriodoHorario = null;
private PreparedStatement pstmgetProgramaCE = null;
private PreparedStatement pstmgetProgramaPP = null;
private PreparedStatement pstmgetProgramaParo = null;
private PreparedStatement pstmgetPrograma = null;
     * getSessionContext
     public javax.ejb.SessionContext getSessionContext() {
          return mySessionCtx;
     * setSessionContext
     public void setSessionContext(javax.ejb.SessionContext ctx) {
          mySessionCtx = ctx;
     * ejbActivate
     public void ejbActivate() {
     * ejbCreate
     public void ejbCreate() throws javax.ejb.CreateException {
System.out.println("ejbCreate()");
try {
Hashtable parms = new Hashtable();
parms.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
ctx = new InitialContext(parms);
ds = (DataSource)ctx.lookup("jdbc/datasource");
}catch (Exception e){
e.printStackTrace();
     * ejbPassivate
     public void ejbPassivate() {
     * ejbRemove
     public void ejbRemove() {
System.out.println("ejbRemove()");
     pstmSelectSerial = null;
     pstmUpdateSerial = null;
     pstmgetPPEquipos = null;
     pstmgetTransfers = null;
     pstmaddRProduccion = null;
     pstmupdInventario = null;
     pstmgetServicios = null;
     pstmaddConsumo = null;
     pstmgetAreaEquipos = null;
     pstmfindCE = null;
     pstmcontEventoLogEq = null;
     pstmaddLog = null;
     pstmfindCaract = null;
     pstmfindComposicion = null;
     pstmfindCombAlt = null;
     pstmaddInventarioH = null;
     pstmgetAlmMatREM = null;
     pstmfindAlmacen = null;
     pstmcontEventoLogAlm = null;
     pstmgetAlmacenes = null;
     pstmfindInvHora = null;
     pstmgetPeriodoHorario = null;
     pstmgetProgramaCE = null;
     pstmgetProgramaPP = null;
     pstmgetProgramaParo = null;
     pstmgetPrograma = null;
public void GenerarSimulacion(int pidSimulacion, String pfini, String pffin, int cveEntidad, int cveUsuario) throws Exception{
System.out.println("GenerarSimulacion()");
System.out.println("***Simulacion " + pidSimulacion + " en proceso...***");
Calendar inicioProceso = Calendar.getInstance();//Tiempo en que empezo el Proceso
Calendar finProceso = null;//Tiempo en que termino el Proceso
     Connection cnn = null;
//boolean autoCommit = false;
     try{
     cnn = ds.getConnection();
autoCommit = cnn.getAutoCommit();
cnn.setAutoCommit(false);
     cnn.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);
pstmSelectSerial = cnn.prepareStatement("select iValor from CatConsecutivo where vcConsecutivo=?");
pstmUpdateSerial = cnn.prepareStatement("update CatConsecutivo set iValor = iValor+1 where vcConsecutivo=?");
pstmgetPPEquipos = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getPPEquipos"));
pstmgetTransfers = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getTransfers"));
pstmaddRProduccion = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.addRProduccion"));
pstmupdInventario = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.updInventario"));
pstmgetServicios = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getServicios"));
pstmaddConsumo = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.addRConsumo"));
pstmgetAreaEquipos = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getAreaEquipos"));
pstmfindCE = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findCE"));
pstmcontEventoLogEq = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.contEventoLogEq"));
pstmaddLog = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.addLog"));
pstmfindCaract = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findCaract"));
pstmfindComposicion = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findComposicion"));
pstmfindCombAlt = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findCombAlt"));
pstmaddInventarioH = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.addInventarioH"));
pstmgetAlmMatREM = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getAlmMatREM"));
pstmfindAlmacen = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findAlmacen"));
pstmcontEventoLogAlm = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.contEventoLogAlm"));
pstmgetAlmacenes = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getAlmacenes"));
pstmfindInvHora = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.findInvHora"));
pstmgetPeriodoHorario = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getPeriodoHorario"));
pstmgetProgramaCE = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getProgramaCE"));
pstmgetProgramaPP = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getProgramaPP"));
pstmgetProgramaParo = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getProgramaParo"));
pstmgetPrograma = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getPrograma"));
pstmgetAreaEquipos = cnn.prepareStatement(Manager.getParameter("cmx.admin.inicioSesion.getAreaEquipos"));
Map hmEqMat = null;
Iterator itEqMat = null;
Map.Entry meEqMat = null;
Map hmInvAlm = null;
Iterator itInvAlm = null;
Map.Entry meInvAlm = null;
Map hmPunta = null;
Iterator itPunta = null;
Map.Entry mePunta = null;
Iterator itPuntaEq = null;
HashMap hmPuntaEq = null;
Vector vecPuntaEq = null;
Iterator itPPEq = null;
HashMap hmPPEq = null;
Vector vecPPEq = null;
Iterator itCar = null;
HashMap hmCar = null;
Vector vecCar = null;
Iterator itLog = null;
HashMap hmLog = null;
Vector vecLog = null;
Iterator itCA = null;
HashMap hmCA = null;
Vector vecCA = null;
Iterator itCom = null;
HashMap hmCom = null;
Vector vecCom = null;
Iterator it = null;
HashMap hm = null;
Vector vecEv = null;
Iterator itEq = null;
HashMap hmEq = null;
Vector vecEq = null;
Vector vecSim = null;
Date d;
String sDSim = "";
Date dDiaPrevio;
String sDiaPrevio = "";
String consulta;
int vContador= 0;
int hr=0;
long vDiaPrevio = 0;
Integer idInvH;
Integer idProd;
Integer idCons;
Integer idLog;
int vCont = 0;
int vCiclo = 0;
int vArea = 0;
int vAreaAct = 0;
int vPuntaEquipo = 0;
// Periodo de Simulacion
long fini = getCurrDate(pfini);
long ffin = getCurrDate(pffin);
// Variables Generales
int vSecuencial = 0;
int vEvento = 0;
float vCostoE = 0;
int vAlmacenREM = 0;
// Variables de Transferencia
float vCantidad = 0;
int vTipoMov = 0;
int vUMedida = 0;
int vAlmacenTr = 0;
float vNIni = 0;
float vNMin = 0;
float vNMax = 0;
float vNAct = 0;
// Variables de Equipos
int vPPMaterial = 0;
int vPPEquipo = 0;
int vPPArea = 0;
int vMaterial = 0;
int vCaractEq = 0;
int vParo = 0;
int vEstatusParo = 0;
int vEstatus = 0;
float vMinPunta = 0;
float vPorcPunta = 0;
float vProporcion = 0;
float vTPH = 0;
float vGasto = 0;
float vKwNoProd = 0;
float vKwProd = 0;
int vAlmacen = 0;
// Variables de Composicion de Materiales
int vMaterialCom = 0;
float vPorcCom = 0;
float vFactorCC = 0;
int vTipoMovCom = 0;
int vUMedidaCom = 0;
int vAlmacenCom = 0;
float vNIniCom = 0;
float vNMinCom = 0;
float vNMaxCom = 0;
float vNActCom = 0;
int vMaterialCA = 0;
int vUMedidaCA = 0;
int vAlmacenCA = 0;
float vNIniCA = 0;
float vNMinCA = 0;
float vNMaxCA = 0;
float vNActCA = 0;
int vOk=0;
int h=0;
boolean vbOk=false;
boolean swArea=true;
Calendar dtH1;
vecSim = new Vector();
vecSim.add(new Integer(pidSimulacion));
for (long ld=fini; ld<=ffin; ld=getNextDate(new Date(ld), 1))
{   d = new Date(ld);
//The process which calls find(), upd(), AplicaEvento() and GetCostoEnergia() methods several times.
//The methods find() and upd() uses a util class (DataDB) which basically assigns the params to the PreparedStatement and executes it, returning the results in a Vector.
} // for ld : Dia de Simulacion
//Cerrar la transaccion
}catch (Exception e){
          System.out.println("rollback...");
               mySessionCtx.setRollbackOnly();
     System.out.println("rollback ok!");
System.out.println(e.toString());
               throw e;
}finally{
finProceso = Calendar.getInstance();
finProceso.setTime(new java.util.Date(finProceso.getTime().getTime() - inicioProceso.getTime().getTime()));
System.out.println("***Simulacion " + pidSimulacion + " procesada en: " + finProceso.get(Calendar.MINUTE) + ":" + finProceso.get(Calendar.SECOND) + "." + finProceso.get(Calendar.MILLISECOND) + ".***");
try {
if (cnn!=null && !cnn.isClosed()) {
          System.out.println("close ok?");
cnn.close();
               System.out.println("close ok!");
}catch (SQLException sqle){
sqle.printStackTrace();
System.out.println("commit ok?");
cnn.commit();
System.out.println("commit ok!");
}catch (Exception e){
e.printStackTrace();
System.out.println(e.toString());
try {
if (cnn!=null && !cnn.isClosed()) {
               System.out.println("rollback ok?");
                         cnn.rollback();
          System.out.println("rollback ok!");
}catch (SQLException sqle){
sqle.printStackTrace();
}finally{
finProceso = Calendar.getInstance();
finProceso.setTime(new java.util.Date(finProceso.getTime().getTime() - inicioProceso.getTime().getTime()));
System.out.println("Simulacion procesada en: " + finProceso.get(Calendar.MINUTE) + ":" + finProceso.get(Calendar.SECOND) + "." + finProceso.get(Calendar.MILLISECOND) + ".***");
try {
if (cnn!=null && !cnn.isClosed()) {
               System.out.println("autocommit ok?");
               cnn.setAutoCommit(autoCommit);
          System.out.println("autocommit ok!");
          System.out.println("close ok?");
cnn.close();
               System.out.println("close ok!");
}catch (SQLException sqle){
sqle.printStackTrace();
private float GetCostoEnergia(float pfKw, long plFecha, int piHora,int cveEntidad) throws Exception {
float exito = -1;
//calculations and has access to DB throught method find()
return exito;
private int AplicaEvento(int pidMaterial, int pidEvento, int pidSecuencial, int pidSimulacion, long plFecha, int piHora) throws Exception {
int exito = -1;
//calculations and has access to DB throught method find()
return exito;
private Iterator find(PreparedStatement pstm, Vector values) throws Exception {
params = (values!=null)? values.toArray() : null;
Vector data = DataDB.executeQuery(pstm, params); //This util class is in a external jar file, such util basically assigns the params to the PreparedStatement and executes it, returning the results in a Vector.
return data.iterator();
private int upd(PreparedStatement pstm, Vector values) throws Exception {
params = values.toArray();
return DataDB.executeUpdate(pstm, params); //This util class is in a external jar file, such util basically assigns the params to the PreparedStatement and executes it.
Help will be REALLY appreciated!
Thanks in advance.

Thanks Paul for your comments.
In fact, I call my EJB in the servlet just once. Im sure calling the same EJB. My project requieres it to be stateless.
This is my last log
1/2/03 13:15:00:481 CST] 17fac55b SystemOut U -ejbCreate()-
[1/2/03 13:15:00:591 CST] 17fac55b SystemOut U jdbc/xa/oye
[1/2/03 13:15:00:651 CST] 17fac55b SystemOut U -GenerarSimulacion()-
[1/2/03 13:15:00:741 CST] 17fac55b SystemOut U ***Simulacion 32 en proceso...??***
[1/2/03 13:15:01:012 CST] 17fac55b SystemOut U JSQLConnect(2.2721) Trial license - expires on:Tue Jan 07 13:01:32 CST 2003, unlimited connections
[1/2/03 13:15:01:092 CST] 17fac55b SystemOut U Connection OK!
[1/2/03 13:15:01:392 CST] 17fac55b SystemOut U PreparedStatements OK!
[1/2/03 13:15:01:402 CST] 17fac55b SystemOut U Comenzando Sim...
I forgot to mention that I create a connection (autocommit false) at the begining of my servlet, which I use throught all the servlet, then I call the EJB, and after the EJB succeds I also close the transaction in the Servlet (to commit what is on the servlet, not the EJB). Thats why I set the transaction in the EJB to requiresNew, so after the EJB ends it commits its own transaction, Am I right?.
The Exception I get I think its because the connection used in the servlet timed out while waiting for the EJB to finish.
This issue has become urgent, so please if you know why I have this problem reply ASAP.
Thanks!

SessionSynchronization methods in Stateless Bean with BMP

Hi,
Why cant we use SessionSynchronization methods in Stateless Bean with BMP?
Just cos the bean has full control over the transactions and it doesnt make sense at all or there is something more to add to this.
Thanks in advance,
Seetesh

Hi,
Why cant we use SessionSynchronization methods in
Stateless Bean with BMP?Stateless Session Bean does not miantain the state across the method call.And the Transaction control is lying within the method call.
Just cos the bean has full control over the
transactions and it doesnt make sense at all or there
is something more to add to this.I dont understand what you are trying to say here.As stateful session bean maintains the state across the method calls and maintains the conversational state which lies is as cache.The Transaction can be aborted either by making the changes to old value and throwing the Exception to client indicating regarding the failure.But this will be great lost of work hence you make(find mechanism) a recovery from the old values which should be saved.
It is for this the specification has come up with SessionSynchronization interface (useful for only Stateful) Session Bean and with (declarative Transaction) CMT.
Regards
Vicky

EJB 3.0 Stateful bean not saving state while Stateless bean is !!!

My Stateless bean is as follow:
package test;
import javax.ejb.Stateless;
@Stateless(mappedName = "StatelessBean")
public class StatelessBean implements StatelessBeanRemote {
     int counter;
     public void increment(){
          System.out.println("Stateless counter value:"+counter);
          counter++;
My Stateful bean is as follow:
package test;
import javax.ejb.Stateful;
@Stateful(mappedName = "StateFulBean")
public class StateFulBean implements StateFulBeanRemote {
     int counter;
     public void increment(){
          System.out.println("Stateful counter value:"+counter);
Client is as follows:
package test;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
public class TestClient {
     public static void main(String[] args) {
          Hashtable hashtable = new Hashtable();
          hashtable.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
          hashtable.put(Context.PROVIDER_URL, "t3://localhost:7001");
          InitialContext ic;
          try {
               ic = new InitialContext(hashtable);
               StateFulBeanRemote stateFulBeanRemote = (StateFulBeanRemote)ic.lookup("StateFulBean#test.StateFulBeanRemote");
               stateFulBeanRemote.increment();
               StatelessBeanRemote statelessBeanRemote = (StatelessBeanRemote)ic.lookup("StatelessBean#test.StatelessBeanRemote");
               statelessBeanRemote.increment();
          } catch (Exception e) {
               e.printStackTrace();
The output i am getting after running the client twice is as follows:
//first time
Stateful counter value:0
Stateless counter value:0
//second time
Stateful counter value:0
Stateless counter value:1
Shouldn't the counter values be incremented in case of Stateful bean and remain the same for Stateless bean. But the output that I am getting is the complete opposite !!!
Can anyone please explain this confusing behavior of stateless and stateful ejb 3.0 beans.

868664 wrote:
Can anyone please explain this confusing behavior of stateless and stateful ejb 3.0 beans.It is very simple: a stateless bean is ASSUMED to be stateless; you cannot keep state in a stateless bean as a contractual rule. That doesn't mean that you will fail to keep state in them at least for a little while, they are still only Java objects. Generally stateless EJBs are pooled, so you may get the same instance each time you use such an EJB, but you may just get another one. It is not dependable and the rules say don't do it - so don't do it.
A stateful bean is tied to a single client, and so can be used by a client to keep state in it. Since You are running the client application twice you are operating with two different clients and so you will get a new stateful bean each time and your code will keep printing 0. However there is also a bug in your code:
public void increment(){
System.out.println("Stateful counter value:"+counter);
}You are not incrementing anything.

Stateless Bean - scope of instance variable in EJB Timer call back function

Hi,
I would like to know on the scope of an instance variable of a Stateless Bean object,
when used in a EJB Timer call back.Let me explain this in more detail below.
I have a requirement to use a EJB Timer.
For this, I have created a stateless object since Timer creation needs to be done
from a stateless bean. I have a member variable "count" of the stateless bean class.
In the timer call back(ejbTimeout), I am able to use this count variable during
each time of the call back, and the value of this variable is also updated properly.
I have a few queries with respect to the above behaviour:
1) Does stateless bean object not get destroyed once the Timer is created from the Bean?
2) If the Bean object is not destroyed, then when does the bean object get destroyed?
3) If both (1) and (2) are not true, then can anyone explain on how the above behaviour is possible?
Thanks in advance,
Ulrich

Hi Ulrich,
The ejb timer is associated with the stateless session bean component, not with a particular bean instance. There is no formal relationship between the bean instance that called createTimer() and the bean instance on which the timer callback happens. If they're the same in your test run that's just a coincidence and not something your application should be depending on.
In the stateless session bean model, the container can create and destroy stateless session bean instances at any time. The container is free to pick any stateless session bean instance to service any client invocation or timer callback. If you need to pass context into a timer callback, one way to do it is via the timer "info" object. However, the info object is immutable so it wouldn't be a good match for a counter. You could of course always just use a database for any necessary coordinated state.
--ken

Unable to rollback using BMT in a stateless bean

Hi,
My stateless bean contains the following testing code
UserTranaction ut = null;
try{
ut = context.getUserTransaction();
ut.begin();
// get database connection from OracleDataSource
// via container
// update a recored in db
if (true)
throw new Exception();
ut.commit();
} catch (Exception e){
ut.rollback();
} finally {
// close connection
I am using oracle 817 jdbc driver and when I execute the method,
the changes in DB are not rolledback and there is no exception
thrown. My questions are
1). Is BMT really work in oc4j? Anyone try before?
2). Is there any additional conditions/setting need to be done
in order to make BMT work? such as dataSource setting, database
configuration...
3). Could anyone provide sample code with related settings?
(especially what datasoure u are using)
Thank you very much!!!

Have you already tried to load the class like this:
Thread.currentThread().getContextClassLoader.loadClass(actionName);
Instead of using the same classloader that loaded your bean implementation, it uses the classloader given to the executer thread as the context classloader.
(In many cases this will be the same, but I don't know how this is done in the implementation of your container).

JAAS and stateless bean

i have a very simple stateless bean with a single "hello" method running in WL 8.1 sp3. to test out Weblogic's behavior, i ran 2 seaparate scenarios on 2 separate occasions. in the first one, i secured all bean methods. in the 2nd one, i secured only the home's "create" mthod, while explicitely denoting all remote methods as "unchecked". next, i wrote a standalone client class where the aforemention bean's EJBHome.create() is called from within a PrivilegedAction-inherited class, while hello() method is called straight up without the use of PrivilegedAction. moreover, the hello() method also prints out the SessionContext.getCallerPrincipal().getName(). finally, an UNsecured servlet utilizing that class was deployed in Tomcat5 and another instance of Weblogic. this is where is gets interesting. when executing the standalone class or the Tomcat's servlet in both scenarios, the results are the same: both create() and hello() get called without a problem, while the latter method prints out correct principal name. however, Weblogic hosting the unsecured servlet behaves differently (and undesirably). in the first scenario where all methods are secured, create() is allowed to be executed, but calling hello() results in an insufficient privileges error. in the 2nd scenario, where only create() method is secured, Weblogic allows hello() to be called without a problem. however, the principal that it returns is "anonymous". my question is how is it possible for not only Tomcat, but even a standalone class to call a secured method without the use of PrivilegedAction and get back a correct principal? yet when absolutely identical code is called from another Weblogic instance, i cannot even obtain a correct principal despite the use of PrivilegedAction!!!
thanks!

Hi "werwer" (or is that "wer" :-),
I haven't checked the forum archives, so I may have already mentioned
this to you (or I may have already mentioned it to someone else
on this forum), but there are many resources available on the
Internet that can answer nearly all your J2EE related questions!
I would like to mention two. (If you already know about them, then
I suggest you study them. If you have already studied them and
still don't know the difference between a stateful and a stateless
session bean, then perhaps you can be a bit more specific about
what, in particular, you are having difficulty with.)
1. "Mastering Enterprise JavaBeans" by Ed Roman
A book that you can download as a PDF file.
http://www.theserverside.com/books/masteringEJB/index.jsp
(Also look for the companion book -- at the same URL -- "EJB
Design Patterns")
Note that you need to become a "member" in order to download
these books -- but registration is free.
2. "Enterprise Java Beans, 3rd Edition" by Richard Monson-Haefel
This is an online book -- that you cannot download!
http://safari.informit.com/main.asp?bookname=entjbeans3
Note that "Safari" (at "InformIT") are offering a free, two-week
trial subscription.
Hope this helps you.
Good Luck,
Avi.

Stateless Bean - Web Service Context

Is there anyway to specify the root context of a stateless bean that is also annotated as a webservice
Example
@Stateless
@Local(**)
@LocalHome(**)
@WebService(**)
@WLHttpTransports(contextPath="rootPath", serviceUri="uri")
Normally i would expect this to be accessible through http://host:port/rootPath/uri?WSDL
This format does work without the session bean if ran through Weblogics Generators, but is it possible to do the same thing with a bean? Or if it's not possible using WLHttpTransports what would the other method be?
Thank you

user8008029,
The WLS JAX-WS stack does not support all of the proprietary annotations from the JAX-RPC stack. This annotation (@WLHttpTransports) is one example. However, you can still override the context and service mapping using descriptors.
The descriptor is [weblogic-webservices.xml|http://e-docs.bea.com/wls/docs103/webserv_ref/dd.html] ...
Here is a sample:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://xmlns.oracle.com/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-webservices http://xmlns.oracle.com/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
<webservice-description>
<webservice-description-name>YourEJBService</webservice-description-name>
<webservice-type>JAXWS</webservice-type>
<port-component>
<port-component-name>YourPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>rootPath</webservice-contextpath>
<webservice-serviceuri>/uri</webservice-serviceuri>
</service-endpoint-address>
</port-component>
</webservice-description>
</weblogic-webservices>
Note: you may use the <WLHTTPTransport/> element with the [ jwsc ant task|http://e-docs.bea.com/wls/docs103/webserv_ref/anttasks.html#wp1069899] . This will build your service and automatically create the appropriate descriptors.
Ryan

Keeping alive an instance of a Stateless Bean

Hello Weblogic comunity:
I'm deploying a stateless bean with initial-beans-in-free-pool element in '1' (Weblogic 7.0). According with the EJB spec, at some moment of EJB lifecicle ejbRemove() will be called by the container removing the instance :(
Is there a way to keep 1+ instances always alive?

Hans,
"Hans Nemarich" <[email protected]> wrote in message news:19065530.1096384306132.JavaMail.root@jserv5...
Hello Weblogic comunity:
I'm deploying a stateless bean with initial-beans-in-free-pool element in '1' (Weblogic 7.0). According with the EJB spec, at somemoment of EJB lifecicle ejbRemove() will be called by the container removing the instance :(
>
Is there a way to keep 1+ instances always alive?Please check this:
http://www.viewtier.com/newsgroups/thread.jspa?threadID=23&tstart=0
Regards,
Slava Imeshev

Problem running RMI/IIOP sample (stateless bean)

Hi.
I am unable to run the RMI/IIOP stateless bean sample (Weblogic 6.1 on
Windows 2000). I have deployed the sample (iiop_ejb_stateless) and the
server is running. I checked in the admin console and the module is
deployed OK.
However, the client is unable to get the initial context and throws a
""We were unable to get a connection to the WebLogic server at
iiop://localhost:
Please make sure that the server is running."
error message on the command prompt. What could be wrong? Is there a
flag I need to throw on to get the server to enable IIOP based
connections?
Thanks in advance,
- deepak

Deepak Balakrishna <[email protected]> writes:
I am unable to run the RMI/IIOP stateless bean sample (Weblogic 6.1 on
Windows 2000). I have deployed the sample (iiop_ejb_stateless) and the
server is running. I checked in the admin console and the module is
deployed OK.
However, the client is unable to get the initial context and throws a
""We were unable to get a connection to the WebLogic server at
iiop://localhost:
Please make sure that the server is running."
error message on the command prompt. What could be wrong? Is there a
flag I need to throw on to get the server to enable IIOP based
connections?It should be on by default. Try using SP2 to see if that helps at all
(although all the examples work on all releases). Also try substituting
localhost for your machine name, W2K does some fun tricks with DNS.
andy

Transaction problem with stateless EJB and DAO

Hi,
I'm using a stateless session bean with container managed transaction and I have a method, which updates a row via CMP entity bean and then calls stored procedure, using a DAO object, which has to use the updated data. Both calls must be done in one transaction. The problem is that the stored procedure doesn't see the changes made from the update via CMP EJB, but after the method exits the changes are in the database. I'm using WebSphere 4.0.3 and DB2 7.2. Method code example in the stateless bean:
public doIt(ValueObject vo) throws ... {
OrderPosRemote opr = getOrderPosRemote();
opr.update(vo);
getDAO().recalc(vo);
} catch (DAOException daoex) {
getSessionContext().setRollbackOnly();
And in the DAO:
public boolean recalc(...) throws DAOException {
Connection conn = getConnFromDataSource();
CallableStatement cstmt = conn.prepareCall("call ...(?,?)");
cstmt.execute();
... // close cstmt and release connection to the pool
Any help will be highly appreciated !

Hi meadandale,
this was my first guess too and I set this attribute in the session bean method, then into the update method of the CMP bean and "manually" to the connection object in the DAO like this:
conn.setTransactionIsolation(Connection.TRANSACTION_READ_UNCOMMITTED);
The isolation level is set correctly (IMHO), because when I comment the line above in the DAO, an exception is thrown stating that the isolation level can't be changed within a transaction.
Unfortenully this didn't help too. Should I set some special attribute to the database or connection pool additionally ?
I don't understand what is the problem actually - it is definitely one transaction and why this doesn't work is not very clear to me ...

How to configure multiple jsp files with diff beans in faces-config.xml??

Hi All,
I have 2 seperate jsp pages one is a login page and the other is the main application page.Now i am handling both the pages with seperate Bean class with respective setter and getter methods.How can i state the same in faces-config.xml file???..
Is the below way correct???
<?xml version='1.0' encoding='UTF-8'?>

<faces-config version="1.2"
    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/web-facesconfig_1_2.xsd">
    <managed-bean>
            <managed-bean-name>LoginForm</managed-bean-name>
            <managed-bean-class>useraccess.LoginForm</managed-bean-class>
            <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <navigation-rule>
            <from-view-id>/login.jsp</from-view-id>
        <navigation-case>
            <from-action>#{LoginForm.CheckValidUser}</from-action>
            <from-outcome>success</from-outcome>
            <to-view-id>/success.jsp</to-view-id>
        </navigation-case>
        <navigation-case>
            <from-action>#{LoginForm.CheckValidUser}</from-action>
            <from-outcome>fail</from-outcome>
            <to-view-id>/fail.jsp</to-view-id>
        </navigation-case>
    </navigation-rule>
    <managed-bean>
            <managed-bean-name>DSRApplication</managed-bean-name>
            <managed-bean-class>DSRApplication.LoginForm</managed-bean-class>
            <managed-bean-scope>request</managed-bean-scope>
    </managed-bean>
    <navigation-rule>
            <from-view-id>/DSR.jsp</from-view-id>
        <navigation-case>
            <from-action>#{DSRApplication.checkValidDateInAllFields}</from-action>
            <from-outcome>alldatasuccess</from-outcome>
            <to-view-id>/success.jsp</to-view-id>
        </navigation-case>
        <navigation-case>
            <from-action>#{DSRApplication.checkValidDateInAllFields}</from-action>
            <from-outcome>datafail</from-outcome>
            <to-view-id>/fail.jsp</to-view-id>
        </navigation-case>
    </navigation-rule>
</faces-config>Thanks in advance to all.
regards,
Viswanadh.

Thanks ejp for the reply.
Since i am a beginner even i dont know the exact reason to answer you for why am i using JSP with Facelets.Kindly provide me the suggestion and valuable information you have so that i can learn.
Apart from this i want to know whether the way provided in that faces-config.xml is possible or do we have a way to make that possible???
regards,
Viswanadh.

Handling BLOBs with CMP Beans

Hi,
is there a detailed example how to handle Blob's with CMP Beans?
I'm trying to store some images in a database (Oracle 9i) using CMP Beans and Oracle iAS 9.03 and jdk 1.4.
Thanks in advance
Jens

We are currently developing a How-To on this and will put this on OTN.
1) Code snippet from Bean Class:
public abstract byte[] getPicture();
public abstract void setPicture(byte[] newPicture);
public Long ejbCreate(Long empno, byte[] newPicture)
setEmpno(empno);
setPicture(newPicture);
return empno;
public void ejbPostCreate(Long empno, byte[] newPicture)
2) Mapping in the orion-ejb-jar.xml:
<entity-deployment name="EmployeePicture" data-source="jdbc/OracleDS" table="EMPPIC">
<primkey-mapping>
<cmp-field-mapping name="empno" persistence-name="EMPNO" persistence-type="NUMBER(8)"/>
</primkey-mapping>
<cmp-field-mapping name="empno" persistence-name="EMPNO" persistence-type="NUMBER(8)"/>
<cmp-field-mapping name="picture" persistence-name="PICTURE" persistence-type="BLOB(4000)"/>
</entity-deployment>
3) Create the client to create the bean:
Long empNo =(Long) Long.valueOf(request.getParameter("EmpNo"));
String fileName =request.getParameter("ImageFileName");
InputStream is = new BufferedInputStream(new FileInputStream(fileName));
int len;
// Initialize byte array
byte byteValue[] = new byte[2048000];
len = is.read(byteValue);
EmployeePictureLocal employeePicture = empHome.create(empNo , byteValue);
out.println("Picture of Emp#:"+empNo +" successfully Loaded into DB <br> <br>");
4) Code snippet to view the image :
Long empNo =(Long) Long.valueOf(request.getParameter("EmpNo"));
out.println("Picture of Emp#"+empNo);
EmployeePictureLocal emp = empHome.findByPrimaryKey(empNo);
response.setContentType("image/jpeg");
OutputStream os = null;
os = response.getOutputStream() ;
byte[] pic = emp.getPicture();
os.write(pic);
os.close();
os = null;
Let me know if this helps
thanks
Debu

Deployment problem sdk 1.4 with entity bean

hallo!
i have a big problem with the j2ee sdk 1.4. when i want to add an entity bean to my ear-file, everything goes good, but when i put the sql-ql for the finder-method and save the file i got an error like this
xxxxxxx.ear is corrupt or cannot be read
when i dont save and will show the descriptor it generates an empty descriptor for this entity bean.
the problem is, that the deployment tool cannot generate the deployment desciptor for entity beans. with session bean there was no problems.
hope somebody can help me.
thanks

There's bug in non-U.S. locales. The workaround is described in this thread:
http://forum.java.sun.com/thread.jsp?forum=136&thread=472692&tstart=15&trange=15
-Ian Evans
Sun Microsystems
J2EE Tutorial team

Stateless bean giving error when deployed through j2ee 1.3RI

I have written a simple stateless bean and deployed through j2ee 1.3 RI
Context initial = new InitialContext(h);
Object obj = initial.lookup("SampleObject"); // SampleObject -jndi name
SampleHome home = (SampleHome)PortableRemoteObject.narrow(obj, SampleHome.class);
But when running the Client , getting the error
java.lang.ClassCastException
at com.sun.corba.se.internal.javax.rmi.PoartableRemoteObject.narrow(Unknown Source)
at javax.rmi.PortableRemoteObject.narrow(Unknown Source) at SampleClient.main(SampleClient.java:27)
Is it a system error or what

Hi sessionbean,
The most common cause of this exception is when the RMI-IIOP stubs are not found within the client's classpath. The client stubs are returned from the deployment step.
Also, it's better to use the no-arg initial context constructor "new InitialContext()" and let the J2EE 1.3 RI code bootstrap the correct naming service.
--ken

CacheFullException with Stateless bean

Similar Messages

Maybe you are looking for