PQ48011: AFTER MIGRATING FROM WAS 3.02 TO 3.5 CUST IS GETTING INVALID BEAN OR EXCEPTION ERRORS.


APAR

APAR status
Closed as user error.

Error description
Getting an " INVALID BEAN OR STATE EXCEPTION "
This is under JAVARMI server exception...
remote exception occured in the server thread.
"CURRENT EQUALS DESTROYED EXPECTED
EQUALS _____ ". Caller only sees this occur when a
browser session sends in two request at the same time.
If he single threads the request he does not see this.
This is an existing app. that the cust migrated from V.3.02.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This is not a valid usage of a stateful session bean - you can
not have multiple (concurrent) calls to a stateful session
bean while a transaction is in flight.  Until the first method
call completes, no other transactional calls can be accepted.
Here is the section of the EJB 1.1 spec (6.6.4):
6.6.4 Restrictions for transactions:Here is the section of the EJB 1.1 spec (6.6.4):
The state diagram implies the following restrictions on transaction scoping of the client invoked busi-ness methods. The restrictions are enforced by the container and must be observed by the client programmer. A session bean instance can participate in at most a single transaction at a time. If a session bean instance is participating in a transaction, it is an error for a client to invoke a method on the session object such that the transaction attribute in the deployment descriptor would cause the container to execute the method in a different transaction context or in an unspecified transaction context. The container throws the java.rmi.RemoteException to the client in such a case. If a session bean instance is participating in a transaction, it is an error for a client to invoke the remove method on the session object's remote or home interface object. The container must detect such an attempt and throw the javax.ejb.RemoveException to the client. The container should not mark the client's transaction for rollback, thus allowing the client to recover.
6.6.4 Restrictions for transactions:The state diagram implies the following restrictions ontransaction scoping of the client invoked busi-ness methods.The restrictions are enforced by the container and must beobserved by the client programmer. A session bean instance canparticipate in at most a single transaction at a time.If a session bean instance is participating in a transaction,it is an error for a client to invoke a method on the sessionobject such that the transaction attribute in the deploymentdescriptor would cause the container to execute the method in adifferent transaction context or in an unspecified transactioncontext. The container throws the java.rmi.RemoteException tothe client in such a case. If a session bean instance isparticipating in a transaction, it is an error for a client toinvoke the remove method on the session object's remote or homeinterface object. The container must detect such an attempt andthrow the javax.ejb.RemoveException to the client. Thecontainer should not mark the client's transaction forrollback, thus allowing the client to recover.
APAR information
APAR numberPQ48011
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED USE
PENoPE
HIPERNoHIPER
Submitted date2001-04-19
Closed date2001-05-08
Last modified date2001-05-08

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros

Fix information
APAR is sysrouted TO one or more of the following:Modules/Macros

Applicable component levels











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ48011
IBM Group: Software Group
Modified date: 2001-05-08