Anupa Unni

Greenhorn
+ Follow
since Jun 26, 2001
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
In last 30 days
0
Forums and Threads

Recent posts by Anupa Unni

Hi,
We are using WAS 3.5.4 in windows 2000 platform with DB2 as database.We tried deploying the entity bean (bean managed)through admin console.Though the deployment took place we could n't enter the datasource for it was disabled in the admin console.
As a result when we try running the client ,we get the following
exception

java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
com.ibm.ejs.container.UncheckedException: ; nested exception is:
java.lang.SecurityException
com.ibm.ejs.container.UncheckedException: ; nested exception is:
java.lang.SecurityException
java.lang.SecurityException
Can anyone put some light into this matter?I am seriously stuck up at this point.
regards,
anupa
23 years ago
Hi,
I've a doubt as to if WebSphere supports Oracle on Unix?
regards,
Anupa
23 years ago
Hi Susana,
Try to make these settings .
Modify the admin.config file, changing entries as follows:
From
com.ibm.ejs.sm.adminServer.dbDriver=jdbc.idbDriver
To:
com.ibm.ejs.sm.adminServer.dbDriver=COM.ibm.db2.jdbc.app.DB2Driver
From:
com.ibm.ejs.sm.adminServer.dbUser=
To:
com.ibm.ejs.sm.adminServer.dbUser=db2admin
where db2admin is the appropriate database user name.
From:
com.ibm.ejs.sm.adminServer.dbPassword=
To:
com.ibm.ejs.sm.adminServer.dbPassword=db2admin
where db2admin is the appropriate database password.
From:
com.ibm.ejs.sm.adminServer.dbUrl=jdbc:idb:c:/WebSphere/AppServer/bin/was.prp
To:
com.ibm.ejs.sm.adminServer.dbUrl=jdbc:db2:was
Modify the entry that points to the database driver:
com.ibm.ejs.sm.adminserver.classpath
For example, change from
c:/WebSphere/AppServer/lib/idb.jar
To
c:/SQLLIB/java12/db2java.zip
The remainder of this step is specific to migration from Instant DB to DB2. FYI, the migration assistant does not perform the following changes, even in the case of Instant DB to DB2 migration.
Locate the entry:
com.ibm.ejs.sm.util.process.Nanny.path
and add an entry for the database installation root, such as c:\\SQLLIB\\bin for DB2 on Windows NT.
Remove the entries:
com.ibm.ejs.sm.adminServer.connectionPoolSize=1
com.ibm.ejs.sm.adminServer.dbSchema=
Modify the file:
product_installation_root/bin/setupCmdLine
(setupCmdLine.sh on UNIX)
Modify the entry from:
SET DB2DRIVER=c:\WebSphere\AppServer\lib\idb.jar
To:
SET DB2DRIVER=c:\SQLLIB\java\db2java.zip
as appropriate for the location of the database driver.
Set the DB2_HOME entry:
DB2_HOME=/home/db2inst1
as appropriate for the installation root of the database product.
Modify the administrative server startup script:
Change from:
DB_TYPE=InstantDB
To:
DB_TYPE=DB2
Change from:
DBUSERID=
To:
DBUSERID=db2inst1
Change from:
DB_INSTANCE_HOME=
To:
DB_INSTANCE_HOME=/home/db2inst1
Modify product_installation_root/properties/initial_setup.config:
Change from:
<config-file>product_installation_root/hosts/default_host/WSsamplesIDB_app/WSsamplesIDB_app_create.xml</config-file>
To:
<config-file>product_installation_root/hosts/default_host/WSsamples_app/WSsamples_app_create.xml</config-file>
Change from:
<value>jdbc:ibd</value>
To:
<value>jdbc:db2</value>
Change from:
<value>product_installation_root/lib/idb.jar</value>
To:
<value>home/db2inst1/sqllib/java/db2java.zip</value>
<value>product_installation_root/bin/myidb.prp</value>
To:
<value>WAS</value>
where WAS is the name of the DB2 database.
Also create a datasource and corresponding driver in the admin console.
Hope this will work for u.
Regards,
Anupa


23 years ago
Hi,
I have set the transaction to TX_supported for the BMP entity bean .Or should it rather be Tx_bean managed?Does it have such a big impact?
Regards,
Anupa
23 years ago
Hi,
Now the situation is that I could deploy and run the bean.But when i am trying to run the Client program I get the following error.
Entered getInitialContext()
JNDI passed
ini value is : javax.naming.InitialContext@d93802c3
got initial context now looking up
narrowing....
jndi success...pp.EmpId is E003
Caught an unexpected exception!
java.rmi.ServerException: RemoteException occurred in server thread; nested exce
ption is:
com.ibm.ejs.container.UncheckedException: ; nested exception is:
java.lang.SecurityException
com.ibm.ejs.container.UncheckedException: ; nested exception is:
java.lang.SecurityException
java.lang.SecurityException
What could be this security exception?
Regards,
Anupa
[This message has been edited by Anupa Unni (edited July 10, 2001).]
23 years ago
hi,
I could successfully deploy a entity bean(BMP).
But when I try to run the same by rightclicking and giving 'start',it gives the following Initialisation failed alert with
7/10/01 9:50 AM : WARNING [Nodename/Default Server]: Failed to start the bean "sorry" com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.ejs.container.IllegalBMTxAttrException
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.ejs.container.IllegalBMTxAttrException
com.ibm.ejs.container.IllegalBMTxAttrException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.io.IOException.<init>(IOException.java:37)
at java.rmi.RemoteException.<init>(RemoteException.java:48)
at com.ibm.ejs.EJSException.<init>(EJSException.java:56)
at com.ibm.ejs.container.ContainerException.<init>(ContainerException.java:47)
at com.ibm.ejs.container.IllegalBMTxAttrException.<init>(IllegalBMTxAttrException.java:46)
at com.ibm.ejs.container.BeanMetaData.setAttrs(BeanMetaData.java:584)
at com.ibm.ejs.container.BeanMetaData.<init>(BeanMetaData.java:327)
at com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1048)
at com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:990)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startBean(ActiveEJBContainer.java:535)
at com.ibm.ejs.sm.active.ActiveEnterpriseBean.startAction(ActiveEnterpriseBean.java:55)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:663)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:110)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:62)
at com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(Unknown Source)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(Unknown Source)
at com.ibm.CORBA.iiop.ORB.process(Unknown Source)
at com.ibm.CORBA.iiop.WorkerThread.run(Unknown Source)
at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:528)
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.ejs.container.IllegalBMTxAttrException
com.ibm.ejs.container.IllegalBMTxAttrException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.io.IOException.<init>(IOException.java:37)
at java.rmi.RemoteException.<init>(RemoteException.java:48)
at com.ibm.ejs.EJSException.<init>(EJSException.java:56)
at com.ibm.ejs.container.ContainerException.<init>(ContainerException.java:47)
at com.ibm.ejs.container.IllegalBMTxAttrException.<init>(IllegalBMTxAttrException.java:46)
at com.ibm.ejs.container.BeanMetaData.setAttrs(BeanMetaData.java:584)
at com.ibm.ejs.container.BeanMetaData.<init>(BeanMetaData.java:327)
at com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1048)
at com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:990)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startBean(ActiveEJBContainer.java:535)
at com.ibm.ejs.sm.active.ActiveEnterpriseBean.startAction(ActiveEnterpriseBean.java:55)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:663)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:110)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:62)
at com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(Unknown Source)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(Unknown Source)
at com.ibm.CORBA.iiop.ORB.process(Unknown Source)
at com.ibm.CORBA.iiop.WorkerThread.run(Unknown Source)
at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:528)
----- Begin backtrace for detail
com.ibm.ejs.container.IllegalBMTxAttrException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.io.IOException.<init>(IOException.java:37)
at java.rmi.RemoteException.<init>(RemoteException.java:48)
at com.ibm.ejs.EJSException.<init>(EJSException.java:56)
at com.ibm.ejs.container.ContainerException.<init>(ContainerException.java:47)
at com.ibm.ejs.container.IllegalBMTxAttrException.<init>(IllegalBMTxAttrException.java:46)
at com.ibm.ejs.container.BeanMetaData.setAttrs(BeanMetaData.java:584)
at com.ibm.ejs.container.BeanMetaData.<init>(BeanMetaData.java:327)
at com.ibm.ejs.container.EJSContainer.loadBeanMetaData(EJSContainer.java:1048)
at com.ibm.ejs.container.EJSContainer.getHomeInstance(EJSContainer.java:990)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startBean(ActiveEJBContainer.java:535)
at com.ibm.ejs.sm.active.ActiveEnterpriseBean.startAction(ActiveEnterpriseBean.java:55)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:663)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:110)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:468)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java:115)
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:62)
at com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(Unknown Source)
at com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(Unknown Source)
at com.ibm.CORBA.iiop.ORB.process(Unknown Source)
at com.ibm.CORBA.iiop.WorkerThread.run(Unknown Source)
at com.ibm.ejs.oa.pool.ThreadPool$PooledThread.run(ThreadPool.java:528)

7/10/01 9:50 AM : Command sorry.start failed.
7/10/01 9:50 AM : Command "sorry.start" failed.
Can anyone please help me out as to what could b the error due to?
thanks 'n regards,
Anupa
23 years ago
Hi,
Thanks 4 ur response.As per ur suggestion I double checked with the 2nd, 3rd, and 4th options.Everything is fine. But regarding that coding exception I'm not very sure.
So hereby enclosing the bean code.If thereis any modifications to b made do let me know.
package test2;
import java.rmi.RemoteException;
import java.util.*;
import javax.ejb.*;
import java.sql.*;
import javax.transaction.*;
import test2.*;
public class PersonBean implements EntityBean{
private String jdbcUrl, drivername, DBLogin, DBPassword, tablename;
private EntityContext entityContext = null;
private static final String DBURLProp = "jdbc:db2:was";
/**
Property used to name the database driver. The Drivername
environment property is set at deploy/install time.
Example: "sun.jdbc.odbc.JdbcOdbcDriver", or
"COM.ibm.db2.jdbc.app.DB2Driver".
*/
private static final String DrivernameProp = "COM.ibm.db2.jdbc.app.DB2Driver";
private static final String DBLoginProp = "db2admin";
private static final String DBPasswordProp = "password";
private static final String TablenameProp = "PERSONBEANTBL";
private Connection jdbcConn = null;
public String empid;
public String name;
private void makeConnection() throws RemoteException {
try {
// Open database connnection
jdbcConn = DriverManager.getConnection("jdbc:db2:was","db2admin","password");
}
catch (Exception e) {
e.printStackTrace();
throw new RemoteException();
}
}
private void checkConnection() throws RemoteException {
if (jdbcConn == null) {
makeConnection();
}
return;
}
private void dropConnection() throws RemoteException{
try {
// Close and delete jdbcConn
jdbcConn.commit();
}
catch (Exception e) {
// Could not commit
System.out.println("cantCommit");
e.printStackTrace();
}
finally {
try {
jdbcConn.close();
}
catch (Exception e) {
// Could not drop connection
System.out.println("dropFailed");
e.printStackTrace();
}
jdbcConn = null;
}
}
private void getEnvProps() throws RemoteException {
drivername="COM.ibm.db2.jdbc.app.DB2Driver";
tablename="PERSONBEANTBL";
DBLogin="d2admin";
DBPassword="password";
}
public PersonPrimary ejbCreate(String empid,String name)
throws CreateException, RemoteException {
this.empid=empid;
this.name = name;
makeConnection();
// INSERT into the database
try {
String sqlString = "INSERT INTO PERSONBEANTBL (empid , name) VALUES (?,?)";
PreparedStatement sqlStatement = jdbcConn.prepareStatement(sqlString);
sqlStatement.setString(1, empid);
sqlStatement.setString(2, name);
// Execute query
int updateResults = sqlStatement.executeUpdate();
if (updateResults != 1) {
// Either fewer than or more than one row was deleted
throw(new CreateException());
}
}
catch (Exception e) {
// Error occurred during data update
throw(new RemoteException());
}
return null;
}
public PersonPrimary ejbPostCreate(String empid,String name){
//
return null;
}
public PersonPrimary ejbFindByPrimaryKey (PersonPrimary pp)
throws FinderException, RemoteException {
boolean wasFound = false;
boolean foundMultiples = false;
makeConnection();
try {

String sqlString =
"SELECT name FROM PERSONBEANTBL WHERE empid = ?";
PreparedStatement sqlStatement = jdbcConn.prepareStatement(sqlString);
String keyValue = pp.empid;
sqlStatement.setString(1, keyValue);
// Execute query
ResultSet sqlResults = sqlStatement.executeQuery();
// Advance cursor (even though there should be only one item)
// wasFound is set to true if there is one
wasFound = sqlResults.next();
// foundMultiples will be true if more than one is found.
foundMultiples = sqlResults.next();
}
catch (Exception e) {
// Throw a resonable exception.
throw(new RemoteException());
}
dropConnection();
if (wasFound && !foundMultiples) {
return pp;
}
else {
String foundStatus = null;
if (!wasFound) {
System.out.println("Line 183");
}

if (foundMultiples) {
System.out.println("Line 188");
}
throw(new FinderException(foundStatus));
}
}
public void ejbLoad () throws RemoteException {
// Get data from database
try {
PersonPrimary pp = (PersonPrimary) entityContext.getPrimaryKey();
empid = pp.empid;
}
catch (Exception ex) {
ex.toString();
}
checkConnection();
try {
// SELECT from database
String sqlString = "SELECT name FROM PERSONBEANTBL WHERE empid = ?";
PreparedStatement sqlStatement = jdbcConn.prepareStatement(sqlString);
sqlStatement.setString(1, empid);
// Execute query
ResultSet sqlResults = sqlStatement.executeQuery();
// Advance cursor (even though there should be only one item)
sqlResults.next();
// Pull out results
name=sqlResults.getString(1);
}
catch (Exception e) {
// Something happened while loading data.
throw(new RemoteException());
}
}
public void ejbActivate() throws RemoteException {
PersonPrimary pp = (PersonPrimary) entityContext.getPrimaryKey();
empid = pp.empid;
checkConnection();
}
public void ejbPassivate() throws RemoteException {
// Deactivate the bean and drop its database connections
dropConnection();
}
public void ejbRemove() throws RemoteException {
checkConnection();
// Delete the appropriate row in table.
try {
// DELETE from DB.
String sqlString = "DELETE FROM PERSONBEANTBL WHERE empid=?";
PreparedStatement sqlStatement = jdbcConn.prepareStatement(sqlString);
sqlStatement.setString(1, empid);
// Execute query
int updateResults = sqlStatement.executeUpdate();
if (updateResults != 1) {
// Either fewer than or more than one row was deleted
throw(new RemoteException());
}
}
catch (Exception e) {
// Something happened while deleting data
throw(new RemoteException());
}
dropConnection();
}
public void ejbStore () throws RemoteException {
checkConnection();
// Overwrite data in database using data in bean
try {
// UPDATE database
String sqlString = "UPDATE PERSONBEANTBL SET name = ? WHERE "
+ "empid = ?";
PreparedStatement sqlStatement = jdbcConn.prepareStatement(sqlString);
sqlStatement.setString(1, name);
// Execute query
int updateResults = sqlStatement.executeUpdate();
if (updateResults != 1) {
// Either fewer than or more than one row was updated
throw(new RemoteException());
}
}
catch (Exception e) {
// Throw a resonable exception.
throw(new RemoteException());
}
}
public String getname() {
return name;
}
public void setname(String name) {
this.name=name;
}

public void setEntityContext(EntityContext ctx) throws RemoteException {
entityContext = ctx;
try {
getEnvProps();
// Load the applet driver for DB2
Class.forName("COM.ibm.db2.jdbc.app.DB2Driver");
}
catch (Exception e) {
System.out.println("PersonBean");
//e.printStackTrace();
System.exit(1);
}
}
public void unsetEntityContext() throws RemoteException {
entityContext = null;
}
}
Thanxs 'n regards,
Anupa
------------------
23 years ago
Hi,
Well today I was trying out with a BMP bean.But I couldn't deploy the bean.
The error obtained is given below.
Exception:
Deployment[Open] failed:
EJBDeploy: setupWorkingDir(): Setting up working directory C:\WebSphere\AppServer\deployedEJBs\PBMPOUTWorkingDir
EJBDeploy: open(): Processing jar file C:\PersonalBMP\PBMPOUT.jar
EJBJar: processJar(): Extracting jar file C:\PersonalBMP\PBMPOUT.jar to directory C:\WebSphere\AppServer\deployedEJBs\PBMPOUTWorkingDir\__ejbjar
EJBJar: processJar(): Parsing manifest file for deployment descriptors
Found Sure.ser
EJBJar: loadJarClasses(): Adding all classes in .jar file to custom class loader
EJBJar: processJar(): Deserializing deployment descriptors
Sure.ser
EJBDeploy: open(): Verifying EJB test2.PersonBean
com.ibm.ejs.sm.exception.DeploymentException: Deployment[Open] failed:
EJBDeploy: setupWorkingDir(): Setting up working directory C:\WebSphere\AppServer\deployedEJBs\PBMPOUTWorkingDir
EJBDeploy: open(): Processing jar file C:\PersonalBMP\PBMPOUT.jar
EJBJar: processJar(): Extracting jar file C:\PersonalBMP\PBMPOUT.jar to directory C:\WebSphere\AppServer\deployedEJBs\PBMPOUTWorkingDir\__ejbjar
EJBJar: processJar(): Parsing manifest file for deployment descriptors
Found Sure.ser
EJBJar: loadJarClasses(): Adding all classes in .jar file to custom class loader
EJBJar: processJar(): Deserializing deployment descriptors
Sure.ser
EJBDeploy: open(): Verifying EJB test2.PersonBean
--------
com.ibm.ejs.sm.client.command.ExecutionException: Error during deploying jar file.
at com.ibm.ejs.sm.client.RepositoryOpException.<init>(RepositoryOpException.java:51)
at com.ibm.ejs.sm.client.command.ExecutionException.<init>(ExecutionException.java:63)
at com.ibm.ejs.sm.client.command.DeployJarCommand.execute(DeployJarCommand.java:86)
at com.ibm.ejs.sm.client.command.CommandManager$ExecutionThread.run(CommandManager.java:282)

I wonder what could b the problem this time?
Regards,
Anupa

23 years ago
Hi,
When we created WAS the problem was solved.But the mystery still remains as to how did that WAS database vanish from DB2!
Well I am not working 4 Yahoo.
Regards,
Anupa
23 years ago
Hi ,
Well u had given the apt solution. We were under the misconception that WAS (database)was there.
But then that database was missing from the control centre.
I think we have added the database and not created it in DB2.
So could that b the problem which we faced in between?
Anyway Thanx for ur quick response.
Regards,
Anupa
23 years ago
Hi ,
Thanx 4 ur quick response.
As u mentioned in ur reply I went to the log file and hereby enclosing the valid data.
[01.06.20 21:17:42:694 GMT+05:30] 4c3a3b9b ActiveServerP A Starting server: "Default Server"
[01.06.20 21:17:42:905 GMT+05:30] 4c3a3b9b ActiveServerP A Started server: "Default Server" (pid "2512")
[01.06.20 21:54:45:641 GMT+05:30] 4c3a3b9b ActiveServerP A Stopped server: "Default Server" (pid "2512")
[01.06.20 21:55:00:402 GMT+05:30] 4c213b9b ActiveServerP A Starting server: "Default Server"
[01.06.20 21:55:00:432 GMT+05:30] 4c213b9b ActiveServerP A Started server: "Default Server" (pid "2556")
[01.06.20 22:04:59:734 GMT+05:30] 4c2c3b9b ActiveServerP A Stopped server: "Default Server" (pid "2556")
[01.06.20 22:05:16:788 GMT+05:30] 4c2b3b9b ActiveServerP A Starting server: "Default Server"
[01.06.20 22:05:16:818 GMT+05:30] 4c2b3b9b ActiveServerP A Started server: "Default Server" (pid "2592")
[01.06.20 22:05:25:341 GMT+05:30] 4c2b3b9b ActiveEJBServ W Failed to initialize a server: "Default Server" com.ibm.ejs.sm.exception.ActiveObjectInitException
----- Begin backtrace for subexception[0]
java.io.InvalidClassException: Test.PersonalBean; Local class not compatible: stream classdesc serialVersionUID=7909771757910354319 local class serialVersionUID=-7984388476250405742
----- Begin backtrace for subexception[1]
java.io.InvalidClassException: Test.PersonalBean; Local class not compatible: stream classdesc serialVersionUID=7909771757910354319 local class serialVersionUID=-7984388476250405742
[01.06.20 22:05:49:696 GMT+05:30] 4cd63b9b ActiveServerP A Stopped server: "Default Server" (pid "2592")
[01.06.20 22:05:56:936 GMT+05:30] 4c3a3b9b ActiveServerP A Starting server: "Default Server"
[01.06.20 22:05:56:956 GMT+05:30] 4c3a3b9b ActiveServerP A Started server: "Default Server" (pid "2500")
[01.06.20 22:07:53:874 GMT+05:30] 4c213b9b ActiveServerP A Stopped server: "Default Server" (pid "2500")
[01.06.22 12:19:18:574 GMT+05:30] d597d102 AdminServer A Initializing WebSphere Administration server
[01.06.22 12:19:18:614 GMT+05:30] 8b235101 DrAdminServer A DrAdmin available on port 1,072
[01.06.22 12:19:18:805 GMT+05:30] d597d102 AdminServer A Your temporary product license expires on Aug 18, 2001, IBM suggests that you purchase a production license now in order to avoid any disruption. Please contact your local IBM representative or visit www.software.ibm.com to purchase this product from Shop IBM.
[01.06.22 12:19:51:011 GMT+05:30] 3e89510c ActiveServerP A Starting server: "Default Server"
[01.06.22 12:19:51:982 GMT+05:30] 3e89510c ActiveServerP A Started server: "Default Server" (pid "2268")
[01.06.22 12:20:08:486 GMT+05:30] d597d102 AdminServer A WebSphere Administration server open for e-business
[01.06.22 17:12:00:968 GMT+05:30] 3eb2510c ActiveServerP A Stopped server: "Default Server" (pid "2268")
[01.06.22 17:16:28:823 GMT+05:30] 3ebf510c ActiveServerP A Starting server: "Default Server"
[01.06.22 17:16:28:863 GMT+05:30] 3ebf510c ActiveServerP A Started server: "Default Server" (pid "2580")
[01.06.22 17:39:40:674 GMT+05:30] 3e89510c ActiveServerP A Stopped server: "Default Server" (pid "2580")
[01.06.22 17:41:04:375 GMT+05:30] 3eb2510c ActiveServerP A Starting server: "Default Server"
[01.06.22 17:41:04:395 GMT+05:30] 3eb2510c ActiveServerP A Started server: "Default Server" (pid "2480")
[01.06.22 17:41:16:212 GMT+05:30] 3eb2510c ActiveEJBServ W Failed to initialize a server: "Default Server" com.ibm.ejs.sm.exception.ActiveObjectInitException
----- Begin backtrace for subexception[0]
com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for subexception[1]
com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for subexception[2]
com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for subexception[3]
com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for subexception[4]
com.ibm.websphere.csi.CSIException: failed to get home instance; nested exception is:
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.container.ContainerException: loading bean meta data failed; nested exception is:
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.websphere.csi.CSIException: persister creation failed; nested exception is:
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
com.ibm.ejs.persistence.EJSPersistenceException: ; nested exception is:
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
----- Begin backtrace for detail
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1001N "WAS:WAS" is not a valid database name. SQLSTATE=2E000
What could be wrong as per this?
regards,
Anupa
[This message has been edited by Anupa Unni (edited July 04, 2001).]
23 years ago
Hi,
I was able to deploy and run a session and entity bean(CMP)successfully.Then I was trying to deploy and run a entity bean(BMP).Mean while I tried stopping WAS and tried restarting. But now it is showing service specific error 10
Is this because of the trial pack -evaluation copy that i am using?Is there any limitations like not more than a fixed number of beans can b deployed or anything of that sort while using the evaluation copy?.....No changes to admin.config or any other property file have been made after successfully deploying and running CMP entity bean.
What could be the reason of this abnormal behaviour of the server?
Regards,
Anupa

23 years ago