[EMF Transaction] Exception during rollback

On a number of occasions we have faced some exception during rollback, if our code encounters an exception while processing the transaction.
Here is a very typical example:
org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException: index=1, size=1
at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.java:602)
at org.eclipse.emf.common.notify.impl.NotifyingListImpl.doRemove(NotifyingListImpl.java:756)
at org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:707)
at org.eclipse.emf.ecore.change.impl.ListChangeImpl.process(ListChangeImpl.java:546)
at org.eclipse.emf.ecore.change.impl.ListChangeImpl.apply(ListChangeImpl.java:476)
at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:701)
at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.process(FeatureChangeImpl.java:611)
at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:518)
at org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:493)
at org.eclipse.emf.ecore.change.impl.ChangeDescriptionImpl.apply(ChangeDescriptionImpl.java:300)
at org.eclipse.emf.transaction.util.CompositeChangeDescription.apply(CompositeChangeDescription.java:104)
at org.eclipse.emf.transaction.impl.TransactionImpl.doRollback(TransactionImpl.java:570)
at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:417)
at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
at org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
This seems to be caused by an attempt to remove an element from a list. Debugging here is showing that the rollback is trying to apply the undo changes produced by the transaction recorder. But the element that it is attempting to remove doesn't exist in the list, and thus the error. I suspect that this is because when the initial exception occurred that this command had not been executed yet. If that is the case, I would expect the rollback to have a way to check for the commands that have completed and to reverse them, but to ignore any commands that have never completed yet. Is it what I might be saying and what is the solution?
I'm adding below portion of the stacktrace that represents the original exception that triggered the rollback. This might help a bit in understanding the situation.
Caused by: java.lang.ClassCastException: ....
at com.castortech.util.emf.VersioningUtils.runInCompositeOperation(VersioningUtils.java:83)
at org.eclipse.sirius.table.business.internal.dialect.TableDialectServices.refresh(TableDialectServices.java:272)
at org.eclipse.sirius.business.internal.dialect.DialectManagerImpl.refresh(DialectManagerImpl.java:106)
at org.eclipse.sirius.business.api.dialect.command.RefreshRepresentationsCommand.doExecute(RefreshRepresentationsCommand.java:85)
at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
at org.eclipse.emf.common.command.CompoundCommand.execute(CompoundCommand.java:261)
at org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.launchCommands(SessionEventBrokerImpl.java:251)
at org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.doExecute(SessionEventBrokerImpl.java:242)
at org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
at org.eclipse.emf.transaction.util.TriggerCommand.execute(TriggerCommand.java:113)
at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.executeTriggers(TransactionalCommandStackImpl.java:218)
at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.precommit(TransactionalEditingDomainImpl.java:712)
at org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:414)
at org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
at org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
at org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
Thanks
Alain

Hi, Alain,
Indeed, the transaction will have difficulty rolling back if the
ChangeDescription cannot successfully be applied. However, a
ChangeDescription records only changes that actually are effected in
the model. I don't know how it could record changes that haven't yet
occurred.
Does your model have custom implementations of some of these list
features, as UML2 does, that perhaps coordinate changes with other
features? Could it be that undoing some changes causes side-effects in
others that then invalidate changes recorded in those?
Or are there non-ChangeDescription-based commands being undone by the
transaction that could interfere with ChangeDescriptions?
There's not really much that a transaction can do to validate the
applicability of a ChangeDescription ... it seems to me that it's up to
the model and the commands captured by a transaction to ensure that
undo will happen correctly. Although, perhaps failed rollback could
somehow be handled more gracefully? I'm not sure.
Cheers,
Christian
On 2015-08-08 18:12:21 +0000, Alain Picard said:
> On a number of occasions we have faced some exception during rollback,
> if our code encounters an exception while processing the transaction.
> Here is a very typical example:
>
>
> org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException:
> index=1, size=1
> at org.eclipse.emf.common.util.BasicEList.remove(BasicEList.java:602)
> at
> org.eclipse.emf.common.notify.impl.NotifyingListImpl.doRemove(NotifyingListImpl.java:756)
>
> at
> org.eclipse.emf.common.notify.impl.NotifyingListImpl.remove(NotifyingListImpl.java:707)
>
> at
> org.eclipse.emf.ecore.change.impl.ListChangeImpl.process(ListChangeImpl.java:546)
>
> at
> org.eclipse.emf.ecore.change.impl.ListChangeImpl.apply(ListChangeImpl.java:476)
>
> at
> org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:701)
>
> at
> org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.process(FeatureChangeImpl.java:611)
>
> at
> org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:518)
>
> at
> org.eclipse.emf.ecore.change.impl.FeatureChangeImpl.apply(FeatureChangeImpl.java:493)
>
> at
> org.eclipse.emf.ecore.change.impl.ChangeDescriptionImpl.apply(ChangeDescriptionImpl.java:300)
>
> at
> org.eclipse.emf.transaction.util.CompositeChangeDescription.apply(CompositeChangeDescription.java:104)
>
> at
> org.eclipse.emf.transaction.impl.TransactionImpl.doRollback(TransactionImpl.java:570)
>
> at
> org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:417)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
>
> at
> org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
>
> at
> org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
>
> at
> org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
>
>
>
> This seems to be caused by an attempt to remove an element from a list.
> Debugging here is showing that the rollback is trying to apply the undo
> changes produced by the transaction recorder. But the element that it
> is attempting to remove doesn't exist in the list, and thus the error.
> I suspect that this is because when the initial exception occurred that
> this command had not been executed yet. If that is the case, I would
> expect the rollback to have a way to check for the commands that have
> completed and to reverse them, but to ignore any commands that have
> never completed yet. Is it what I might be saying and what is the
> solution?
>
> I'm adding below portion of the stacktrace that represents the original
> exception that triggered the rollback. This might help a bit in
> understanding the situation.
>
> Caused by: java.lang.ClassCastException: ....
> ...
> at
> com.castortech.util.emf.VersioningUtils.runInCompositeOperation(VersioningUtils.java:83)
>
> at
> org.eclipse.sirius.table.business.internal.dialect.TableDialectServices.refresh(TableDialectServices.java:272)
>
> at
> org.eclipse.sirius.business.internal.dialect.DialectManagerImpl.refresh(DialectManagerImpl.java:106)
>
> at
> org.eclipse.sirius.business.api.dialect.command.RefreshRepresentationsCommand.doExecute(RefreshRepresentationsCommand.java:85)
>
> at
> org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
>
> at
> org.eclipse.emf.common.command.CompoundCommand.execute(CompoundCommand.java:261)
>
> at
> org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.launchCommands(SessionEventBrokerImpl.java:251)
>
> at
> org.eclipse.sirius.business.internal.session.SessionEventBrokerImpl$PreCommitPriorityNotifyListenersCommand.doExecute(SessionEventBrokerImpl.java:242)
>
> at
> org.eclipse.emf.transaction.RecordingCommand.execute(RecordingCommand.java:135)
>
> at
> org.eclipse.emf.transaction.util.TriggerCommand.execute(TriggerCommand.java:113)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.executeTriggers(TransactionalCommandStackImpl.java:218)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.precommit(TransactionalEditingDomainImpl.java:712)
>
> at
> org.eclipse.emf.transaction.impl.TransactionImpl.commit(TransactionImpl.java:414)
>
> at
> org.eclipse.emf.transaction.impl.TransactionalCommandStackImpl.doExecute(TransactionalCommandStackImpl.java:70)
>
> at
> org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:165)
>
> at
> org.eclipse.emf.transaction.impl.AbstractTransactionalCommandStack.execute(AbstractTransactionalCommandStack.java:219)
>
> at
> org.eclipse.emf.emfstore.internal.client.transaction.EMFStoreTransactionalCommandStack.execute(EMFStoreTransactionalCommandStack.java:52)
>
>
>
> Thanks
> Alain

Similar Messages

Distributed Environment - Exception during commit of transact

The Application is deployed in 3 machines (Win2K) in Weblogic 6.1 SP2 with Oracle
8i as the Database - Presentation EAR file in one machine, Business Logic EAR
file in second machine and Persistence EAR file in the third machine. The Database
is also in the third machine. Tx Datasource is configured in all the 3 weblogic
instances to point to the Database.
The application has a 'Save' operation in which case the EJB in the Business Logic
Layer connects to the Datasource of the Persistence Layer. The following error
is seen in the console of the second machine (Business Logic) while Saving.
<Error> <EJB> <Exception during commit of transact
ion Name=[EJB com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB.proc
ess(reefwork.bp.BusinessProcessEvent)],Xid=1:d4f44d847f28edb9(7225037),Status=Ro
lled back. [Reason=javax.transaction.SystemException: Aborting prepare because
s
ome resources could not be assigned],numRepliesOwedMe=0,numRepliesOwedOthers=0,s
econds since begin=1,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connec
tion]=(state=new,assigned=none),SCInfo[mydomain+myserver]=(state=rolledback),pro
perties=({weblogic.transaction.name=[EJB com.toontown.matchmaker.ejb.service.Bus
inessProcessGatewayEJB.process(reefwork.bp.BusinessProcessEvent)], weblogic.jdbc
=t3://130.10.11.30:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDesc
riptor=(CoordinatorURL=myserver+130.10.7.94:7001+mydomain+, Resources={})],Coord
inatorURL=myserver+130.10.7.94:7001+mydomain+): javax.transaction.SystemExceptio
n: Aborting prepare because some resources could not be assigned
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:924)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1566)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Aborting prepare because some resources
could not be assigned - with nested exception:
[javax.transaction.SystemException: Aborting prepare because some resources coul
d not be assigned]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Please note that 130.10.7.94 is the IP of Business Logic Layer and 130.10.11.30
is the IP of Persistence Layer.
Thanks!

Try changing the server name on either on persistence machine or business logic
machine
"Devika" <[email protected]> wrote:
>
>
The Application is deployed in 3 machines (Win2K) in Weblogic 6.1 SP2
with Oracle
8i as the Database - Presentation EAR file in one machine, Business Logic
EAR
file in second machine and Persistence EAR file in the third machine.
The Database
is also in the third machine. Tx Datasource is configured in all the
3 weblogic
instances to point to the Database.
The application has a 'Save' operation in which case the EJB in the Business
Logic
Layer connects to the Datasource of the Persistence Layer. The following
error
is seen in the console of the second machine (Business Logic) while Saving.
<Error> <EJB> <Exception during commit of transact
ion Name=[EJB com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB.proc
ess(reefwork.bp.BusinessProcessEvent)],Xid=1:d4f44d847f28edb9(7225037),Status=Ro
lled back. [Reason=javax.transaction.SystemException: Aborting prepare
because
s
ome resources could not be assigned],numRepliesOwedMe=0,numRepliesOwedOthers=0,s
econds since begin=1,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connec
tion]=(state=new,assigned=none),SCInfo[mydomain+myserver]=(state=rolledback),pro
perties=({weblogic.transaction.name=[EJB com.toontown.matchmaker.ejb.service.Bus
inessProcessGatewayEJB.process(reefwork.bp.BusinessProcessEvent)], weblogic.jdbc
=t3://130.10.11.30:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDesc
riptor=(CoordinatorURL=myserver+130.10.7.94:7001+mydomain+, Resources={})],Coord
inatorURL=myserver+130.10.7.94:7001+mydomain+): javax.transaction.SystemExceptio
n: Aborting prepare because some resources could not be assigned
at weblogic.transaction.internal.TransactionImpl.abort(TransactionImpl.java:924)
at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1566)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:218)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Aborting prepare because some
resources
could not be assigned - with nested exception:
[javax.transaction.SystemException: Aborting prepare because some resources
coul
d not be assigned]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(
TransactionImpl.java:1475)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:263)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:190)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:231)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl.process(BusinessProcessGatewayEJB_yd4d11_EOImpl.java:46)
at com.toontown.matchmaker.ejb.service.BusinessProcessGatewayEJB_yd4d11_
EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Please note that 130.10.7.94 is the IP of Business Logic Layer and 130.10.11.30
is the IP of Persistence Layer.
Thanks!

Transaction doesn't rollback

Hello guys,
I 've a trouble and I'm not able to solve it..Ineed your help...
I have a jsf application.
I need to execute several insert query into a mysql db in a transaction, so operation must be accomplished only if all query are successfully executed.
To solve this issue I thinked to store prepared statement into an arraylist and passing it to a method that execute queries...if at least one query gives exception transaction must be rollback.
So in my code I've
ArrayList list = new ArrayList(); //collects prepared statements
PreparedStatement ps= conn.prepareStatement(....);
list.add(ps);
String result= Helper.executeTransaction(list);//I call static method to execute queries in transaction.Issue is that if a query fails during execution, exception is thrown but transaction is not rollback..so queries that has been successfully executed write into db...
This is method to execute transaction...
public static String executeTransaction(ArrayList ps) {
 Connection conn = null;
 String result = "success";
 String allgood = "false";
 try {
 conn = Singleton.getInstance().getInstance().getDataSource().getConnection();
 } catch (SQLException ex) {
 Logger.getLogger(Helper.class.getName()).log(Level.SEVERE, null, ex);
 List results = new ArrayList();
 try {
 conn.setAutoCommit(false);
 } catch (SQLException ex) {
 Logger.getLogger(Helper.class.getName()).log(Level.SEVERE, null, ex);
 for (int i = 0; i < ps.size(); i++) {
 try {
 int nrows = ((java.sql.PreparedStatement) ps.get(i)).executeUpdate();
 allgood = "true";
 results.add(allgood);
 } catch (Exception z) {
 z.printStackTrace();
 allgood = "false";
 results.add(allgood);
 for (int j = 0; j < results.size(); j++) {
 if ((results.get(j)).equals("false")) {
 try {
 conn.rollback();
 } catch (SQLException ex) {
 Logger.getLogger(Helper.class.getName()).log(Level.SEVERE, null, ex);
 result = "failure";
 return result;
 try {
 conn.commit();
 } catch (SQLException ex) {
 Logger.getLogger(Helper.class.getName()).log(Level.SEVERE, null, ex);
 return result;
 }Debugging code seems like system arrives to conn.rollback(), but it seems like after executing correctly query data are written in the db without waiting for other queries, to estabilish if commit or rollback.
Where is the error?
Please help me

Hello guys,
thanks for your replies...
but issue isn't still clear to me...
Please correct me if I'm wrong.
Basing on what I understood from your answers I evaluated my code but I'm not able what I miss..
I set
conn.setAutoCommit(false);that mean that data are not entered into db before commit is run..
I stored all prepared statement in a list (and I think it's ok)..I iterate on list executing prepared statement and I store a boolean for each query execution (why data are entered into db if I set conn.setAutoCommit(false)?
Next I read list of boolean, if I find a "FALSE" I run
conn.rollback();
It seems correct to me...could you help me with my code?
Or at least more explanation...
Thanks

Timeout during rollback processing

I am getting the "Timeout during rollback processing (javax.transaction.SystemException)" exception in the JMS application on WebLogic 8.1. The JMS provider is Tibco EMS 4.3. I am using XAQueueConnectionFactory. The JTA timeout configured in WebLogic is 120s. This exception occurs after some time once the server/application is started even though the application has not processed any JMS messages.
I also noticed that the number of total transactions and number of rolledback transactions in WebLogic (server->Monitoring->JTA) keep on increasing even though there is no message to process. I am not sure if this is expected behavior of JTA.
Can someone please help?

Hi,
The reason due to which I did not put stack trace earlier is, I'm using an open source ESB called Mule. So, the root cause of the problem could be in Mule or WebLogic. I am not sure about it. I'm also checking the issue on Mule forum, but any clue from this forum would be really great. The stack trace is
02:00:46,562 ERROR [jmsXAQueueConnector.QUALIFIED.receiver.3] ? (?:?) -
Message : Transaction rollback failed
Type : org.mule.transaction.TransactionRollbackException
Code : MULE_ERROR-92098
JavaDoc : http://mule.codehaus.org/docs/apidocs/org/mule/transaction/TransactionRollbackException.html
Exception stack is:
1. Timeout during rollback processing (javax.transaction.SystemException)
weblogic.transaction.internal.ServerTransactionImpl:393 (http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/transaction/SystemException.html)
2. Transaction rollback failed (org.mule.transaction.TransactionRollbackException)
org.mule.transaction.XaTransaction:123 (http://mule.codehaus.org/docs/apidocs/org/mule/transaction/TransactionRollbackException.html)
Root Exception stack trace:
javax.transaction.SystemException: Timeout during rollback processing
at weblogic.transaction.internal.ServerTransactionImpl.internalRollback(ServerTransactionImpl.java:393)
at weblogic.transaction.internal.ServerTransactionImpl.rollback(ServerTransactionImpl.java:350)
at org.mule.transaction.XaTransaction.doRollback(XaTransaction.java:118)
at org.mule.transaction.AbstractTransaction.rollback(AbstractTransaction.java:116)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:81)
at org.mule.providers.TransactedPollingMessageReceiver.poll(TransactedPollingMessageReceiver.java:110)
at org.mule.providers.jms.TransactedJmsMessageReceiver.poll(TransactedJmsMessageReceiver.java:154)
at org.mule.providers.PollingMessageReceiver.run(PollingMessageReceiver.java:71)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:643)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
at java.lang.Thread.run(Thread.java:534)
********************************************************************************

Transaction Locking during multiple Webservice - persistent webs sessions

Hi All, 
 
Yesterday evening we had a discussion concerning ESA architecture. We want to create (web)services for accessing the SAP business objects (using XI) and use these (web)services via visual composer, webdynpro or custom java development. 
 
It does not seem a big problem to perform creations and reads of transaction, but when we want to change objects, we saw some problems concerning locking/commiting and rollbacks. 
 
From our GUI we would like to be able to go in edit mode and from that moment on, the transaction should be locked. We then want to change certain parameters and commit only when we push the save button. 
 
We can invoke a webservice wich tries to lock the transaction, but at the moment the XI scenario is completed (=the lock is created), the program at SAP side (=proxy in our case) is also finished and the lock is automaticly removed. How can we do locking, when using webservices via XI? 
 
The problem of the rollback and commit we can partially solve by putting more logic in the GUI, but we don't want to do that. How can we do a change of a business object and remember this change without doing a commit on the SAP system.... . Same problem for the rollback. 
 
Is there a away to keep a session "alive" during multiple webservice calls or to simulate it? Every webservice invokation happens in a different context...isn't it? 
 
 
Just to make it a bit more clear. 
 
Suppose we create 6 service related to the business object bupa (business partner). 
- read 
- change 
- commit 
- rollback 
- lock 
- unlock. 
 
We create a GUI which uses these services. 
 
Step1: we want to see bupa in detail, so the read webservice is called and the retrieved details are shown in the GUI 
Step2: we want to go in edit mode, so the lock webservice is called to lock the bupa. The bupa should stay locked, untill the unlock is called. Here occurs the problem. The webservice lock is called, XI will trigger the proxy on the SAP system. This proxy will lock the bupa. As soon as the proxy-program is completed, the bupa lock will automaticly be removed ... . We want to keep this lock! 
Step3: we change the bupa using the change webservice. Only the user who locked the bupa should be able to change it. 
Problem concerning the locking occurs: standard we don't know who locked the bupa (this is done by the generic RFC user, configured in sm59). Should we pass some kind of GUID towards the proxy and build some additional logic to know which end-user in fact locked it... . Using the userid isn't sufficient, because a user could logon multiple time simultanously. 
 
Another problem is that we want to change the bupa, without having to do a commit yet.De commit should be called only when pushing the save button. When the proxy is ended and we did not do a commit, the changes are lost normally ... . 
 
What we in fact want to do is Simulate the bsp behaviour. 
Step4:We want to perform a save of the things we changed or a reset. This means the commit or rollback webservice is called. 
Step5: We want to unlock the bupa by calling the unlock webservice. 
 
 
Please give me your comments. 
 
Kind regards 
Joris 
 
Note: Transaction Locking during multiple Webservice "sessions".
Message was edited by:
Joris Verberckmoes

There are multiple strategies how to resolve this. They require that the last change time is available in the changed object, and also that the client keeps the value of the change time when it read the data.
1. First one wins
Immediately before posting the changes, the current change time is read from the server. In case it is different from the client buffer, then the client changes are discarted.
Example:
1. Client A reads data
2. Client B reads data
3. Client B changes its buffer
4. Client B checks if server change time has changed (result is no)
5. Client B writes his changes to the server
6. Client A changes its buffer
7. Client A checks if server change time has changed (result is yes)
8. Client A discarts its changes
2. Last one wins
Easy. Client just writes his changes to the server, overwriting any changes that might have occured since it read the data.
Example:
1. Client A reads data
2. Client B reads data
3. Client B changes its buffer
4. Client B writes his changes to the server
5. Client A changes its buffer
6. Client A writes its changes to the server -> changes from client B are lost
3. Everybody wins
Most complicated. In case of concurrent changes, the client is responsible for merging his changes with the changes from other clients and to resolve any conflicts.
Example:
1. Client A reads data
2. Client B reads data
3. Client B changes its buffer
4. Client B checks if server change time has changed (result is no)
5. Client B writes his changes to the server
6. Client A changes its buffer
7. Client A checks if server change time has changed (result is yes)
8. Client A merges its changes with changes from client B
9. Client A writes his changes to the server
"Last one wins" is definitely not water-proof. But even with the other strategies, data can potentially get lost in the short timeframe when the change time is checked and the actual update.
To make it more secure, server support is required. E.g. the client could pass the change time from its read access to the server. The server can then reliably reject the update if the change data has been updated in beetween by another client.

HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE

Hi,
I am getting the following error in XI 3.0 SP12.
This error is occured in the Call Adapter step.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>108</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when receiving by HTTP (error code: 108, error text: )</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
and in the trace of that messages the error is as follows:
System_Error HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE
The scenario is a BPM in which calling a BAPI using RFC adapter Synchronously and after getting the response from BAPI generating a file for that response data.
I think message is failing in receiving response from BAPI.
Kindly reply me back ASAP.
Thanks
Gopesh

Hi,
Can you check SICF services are active or not. in Transaction SICF.
Also Check the HTTP ports (using transaction SMICM choose Services),
Check RFC adapter Configuration, Gateway, etc
Regards,
moorthy

Jbo-26066 Error during rollback error

Hi All,
I ve developed an application which runs fine 95% of the time..but few times it throws this exception. Im unable to find out the possible reason behind this.
The exception does not point to any of my code.
Pls help me on this..
Thanks,
Sreeram
oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.DMLException, msg=JBO-26066: Error during rollback.
     at oracle.jbo.common.ampool.ApplicationPoolImpl.resetApplicationModule(ApplicationPoolImpl.java:1388)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doUnmanagedCheckin(ApplicationPoolImpl.java:1181)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1093)
     at oracle.apps.fnd.framework.OAApplicationPoolImpl.releaseApplicationModule(OAApplicationPoolImpl.java:342)
     at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:662)
     at oracle.apps.fnd.framework.webui.OAHttpSessionCookieImpl.releaseApplicationModule(OAHttpSessionCookieImpl.java:533)
     at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:584)
     at oracle.apps.fnd.framework.OASessionCookieHelper.timeoutApplicationModule(OASessionCookieHelper.java:317)
     at oracle.apps.fnd.framework.webui.OAHttpSessionCookieImpl.timeout(OAHttpSessionCookieImpl.java:612)
     at oracle.jbo.http.HttpSessionCookieImpl.timeout(HttpSessionCookieImpl.java:146)
     at oracle.jbo.http.HttpContainer.fireTimeout(HttpContainer.java:512)
     at oracle.jbo.http.HttpContainer.timeout(HttpContainer.java:232)
     at oracle.jbo.http.HttpContainer.valueUnbound(HttpContainer.java:300)
     at com.evermind.server.http.EvermindHttpSession.destroy(EvermindHttpSession.java:289)
     at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:234)
     at com.evermind.server.http.HttpApplication.checkSessionTimeouts(HttpApplication.java:6375)
     at com.evermind.server.http.HttpSite.checkSessionTimeouts(HttpSite.java:979)
     at com.evermind.server.http.SessionTimeoutTask.checkSessionTimeouts(SessionTimeoutTask.java:171)
     at com.evermind.server.http.SessionTimeoutTask.run(SessionTimeoutTask.java:145)
     at com.evermind.util.TaskManager.run(TaskManager.java:181)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)
## Detail 0 ##
oracle.jbo.DMLException: JBO-26066: Error during rollback.
     at oracle.jbo.server.DefaultTxnHandlerImpl.handleRollback(DefaultTxnHandlerImpl.java:153)
     at oracle.jbo.server.DBTransactionImpl.doRollback(DBTransactionImpl.java:4177)
     at oracle.jbo.server.DBTransactionImpl.rollback(DBTransactionImpl.java:2140)
     at oracle.apps.fnd.framework.server.OADBTransactionImpl.rollback(OADBTransactionImpl.java:747)
     at oracle.jbo.server.ApplicationModuleImpl.resetState(ApplicationModuleImpl.java:3930)
     at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.beforeRelease(OAApplicationModuleImpl.java:862)
     at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.beforePoolCheckin(OAApplicationModuleImpl.java:793)
     at oracle.apps.fnd.framework.server.OAApplicationModuleImpl.resetState(OAApplicationModuleImpl.java:951)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.resetApplicationModule(ApplicationPoolImpl.java:1369)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doUnmanagedCheckin(ApplicationPoolImpl.java:1181)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(ApplicationPoolImpl.java:1093)
     at oracle.apps.fnd.framework.OAApplicationPoolImpl.releaseApplicationModule(OAApplicationPoolImpl.java:342)
     at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:662)
     at oracle.apps.fnd.framework.webui.OAHttpSessionCookieImpl.releaseApplicationModule(OAHttpSessionCookieImpl.java:533)
     at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(SessionCookieImpl.java:584)
     at oracle.apps.fnd.framework.OASessionCookieHelper.timeoutApplicationModule(OASessionCookieHelper.java:317)
     at oracle.apps.fnd.framework.webui.OAHttpSessionCookieImpl.timeout(OAHttpSessionCookieImpl.java:612)
     at oracle.jbo.http.HttpSessionCookieImpl.timeout(HttpSessionCookieImpl.java:146)
     at oracle.jbo.http.HttpContainer.fireTimeout(HttpContainer.java:512)
     at oracle.jbo.http.HttpContainer.timeout(HttpContainer.java:232)
     at oracle.jbo.http.HttpContainer.valueUnbound(HttpContainer.java:300)
     at com.evermind.server.http.EvermindHttpSession.destroy(EvermindHttpSession.java:289)
     at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:234)
     at com.evermind.server.http.HttpApplication.checkSessionTimeouts(HttpApplication.java:6375)
     at com.evermind.server.http.HttpSite.checkSessionTimeouts(HttpSite.java:979)
     at com.evermind.server.http.SessionTimeoutTask.checkSessionTimeouts(SessionTimeoutTask.java:171)
     at com.evermind.server.http.SessionTimeoutTask.run(SessionTimeoutTask.java:145)
     at com.evermind.util.TaskManager.run(TaskManager.java:181)
     at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:803)
     at java.lang.Thread.run(Thread.java:534)

Sreeram,
You can log a SR against Oracle for this. Looks like the database connection is getting closed before the rollback code could be executed. By any chance are you leaving the session idle for long when this behaviour is attributed? May be some setting in the instance can make sure the database connections last longer. So SR is the way for it.. my thought.
Regards
Sumit

Container Managed XA transaction failing to rollback

 We are running two distributed instances of WL 6.0 SP1, each with their own domain,
 each accessing their own Oracle 8.1.5 database instance.
 Server 1 has the following transaction configuration:
 JDBC Transaction Pool Driver - weblogic.jdbc.oci.xa.XADataSource
 Server 2 is using the oracle thin driver, a non-XA datasource, as it's JDBC datasource.
 The JDBCTxDataSource has the attribute 'EnableTwoPhaseCommit' set to 'true'.
 The deployment descriptor's <transaction-type> is set to 'container' and the <trans-attribute>
 is set to 'required' in both of the server's session beans.
 A test is performed where server 1 calls a method on server 2, via the remote
 interface, to insert a record in server 2's database. A call is then made to
 a session bean in Server 1 to insert a record in server 1's database. In the call
 to Server 1's bean a system level error, 'EJBException', is thrown to test if
 the XA transaction driver will rollback the record inserted during the initial
 call to server 2 - it does not. However, if the method sessionContext.setRollbackOnly()
 is explicity called in the catch () block of server 1's method, where the call
 to server 2 was made, the rollback is successful on server 2.
 Is there a problem using the oracle thin driver or can the problem be related
 to the version of Oracle we are using, 8.1.5 and the fact it does not support
 JDBC 2.0? An additional note - if all goes well both data sources are successfully
 updated.
 Thanks,
 Keith Denson


 We are running two distributed instances of WL 6.0 SP1, each with their own domain,
 each accessing their own Oracle 8.1.5 database instance.
 Server 1 has the following transaction configuration:
 JDBC Transaction Pool Driver - weblogic.jdbc.oci.xa.XADataSource
 Server 2 is using the oracle thin driver, a non-XA datasource, as it's JDBC datasource.
 The JDBCTxDataSource has the attribute 'EnableTwoPhaseCommit' set to 'true'.
 The deployment descriptor's <transaction-type> is set to 'container' and the <trans-attribute>
 is set to 'required' in both of the server's session beans.
 A test is performed where server 1 calls a method on server 2, via the remote
 interface, to insert a record in server 2's database. A call is then made to
 a session bean in Server 1 to insert a record in server 1's database. In the call
 to Server 1's bean a system level error, 'EJBException', is thrown to test if
 the XA transaction driver will rollback the record inserted during the initial
 call to server 2 - it does not. However, if the method sessionContext.setRollbackOnly()
 is explicity called in the catch () block of server 1's method, where the call
 to server 2 was made, the rollback is successful on server 2.
 Is there a problem using the oracle thin driver or can the problem be related
 to the version of Oracle we are using, 8.1.5 and the fact it does not support
 JDBC 2.0? An additional note - if all goes well both data sources are successfully
 updated.
 Thanks,
 Keith Denson

MSS-mySAP ERP 2004-PCR- Processing exception during a "Render" operation

HI,
When i navigate to the Personnel Change request,select an employee and select the scenario,say promotion,i get the error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "Render" operation.Request start time: Tue May 09 16:41:47 IST 2006com.adobe.ProcessingError: Invalid XDP error while configuring the XMLForm module.Please validate the form template and try again: com.adobe.document.xmlform.InvalidXDPException:
After activating the ADS Trace,the deafult trace displays the following
1.5#0013D486EEA9004E0000001A00000D50000413A81B84E899#1147512643993#com.adobe.AdobeDocumentServices#com.adobe/AdobeDocumentServices#com.adobe.AdobeDocumentServices#ADSUser#615#SAP J2EE Engine JTA Transaction : [0ffffff8effffffc43e000ffffff86]###24f7cbf0e26311dab6b10013d486eea9#SAPEngine_Application_Thread[impl:3]_30##0#0#Error#1#/System/Server#Plain###Error while parsing form template: C:
WINNT
Temp
adobewa_J2E_00_575593923
DM805001759176685846.dir
DM-4339515885940827304.tmp
java.lang.Exception: SAX exception while extracting properties from form template: C:
WINNT
Temp
adobewa_J2E_00_575593923
DM805001759176685846.dir
DM-4339515885940827304.tmp Application: PcrApplication Form: http://<server name>:50000/webdynpro/dispatcher/sap.com/msspcr/PcrApplication/wd_key0_1147512638024/unknown Client: 1
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Bad PUBLIC declaration(:main:, row:1, col:22)(:main:, row=1, col=22) -> com.sap.engine.lib.xml.parser.ParserException: Bad PUBLIC declaration(:main:, row:1, col:22): Trans(Sat May 13 15:00:42 IST 2006)#
#1.5#0013D486EEA9004E0000001C00000D50000413A81BE28C3F#1147512650134#com.adobe.AdobeDocumentServices#com.adobe/AdobeDocumentServices#com.adobe.AdobeDocumentServices#ADSUser#615#SAP J2EE Engine JTA Transaction : [0ffffff8effffffc43e000ffffff86]###2a5eb360e26311dab9e10013d486eea9#SAPEngine_Application_Thread[impl:3]_30##0#0#Error#1#/System/Server#Plain###Processing exception during a "Render" operation.
Request start time: Sat May 13 15:00:42 IST 2006
com.adobe.ProcessingError: Invalid XDP error while configuring the XMLForm module.
Please validate the form template and try again:
com.adobe.document.xmlform.InvalidXDPException: IDL:com/adobe/document/xmlform/InvalidXDPException:1.0
I have done the following steps:
1)Copied the current scenario customizing from client 000 to the current client using transaction QISR_SM29 (object lists P46C_ISR_SCENARIO and AX8_ISR_SCENARIOX).
2)Indicated the server on which the Web applications (Web Dynpro) are located in the IMG of the mySAP ERP system under Cross-Application Components> Internet/Intranet Services> Internal Service Request> Scenario Definition> Define Scenarios --> Details --> Additional Data for Scenario.
If i preview the forms via transaction SFP, say form ISR_FORM_SPPM
The form is displayed in German.
What all configuration eneds to be done?how to resolve the Error?
Regards,
Malika

Hi Malika
upgrade the SP level to 11. (mandatory)
u also upgrade ur SP level of R3 ECC 5.0 with help of BASIS
don't use that link provide in note 849730.
download it from following.
service.sap.com/swdc->sap support package ->entry by application group-> sap application components->sap ERP ->sap erp 2004 ->entry by components ->sap xss (self services)
from SAP ESS 100 download following file.
ESS11P_5-10002965.sca Patch 5 for SAP ESS 100 SP11
https://smpdl.sap-ag.de/~swdc/012002523100000684532006D/ESS11P_5-10002965.sca?_ACTION=DL_DIRECT
from SAP MSS 100 download the following file
MSS11_0-10002964.sca SP11 for SAP MSS 100
https://smpdl.sap-ag.de/~swdc/012002523100000037692006D/MSS11_0-10002964.sca?_ACTION=DL_DIRECT
from SAP PCUI GP 100 download following.
PCUIGP011P_1-20000568.sca Patch for SP11 of SAP PCUI_GP 100
https://smpdl.sap-ag.de/~swdc/012002523100000287102006D/PCUIGP011P_1-20000568.sca?_ACTION=DL_DIRECT
regards,
kaushal

Cannot change transaction isolation during distributed transaction

Hi All,
When ever the IPortalComponent session expires my application is throwing Null pointer exception. So I am catching the NullPointer exception and then reloading the page again. It is working in frontend without any issues.
But in the error log monitor(nwa) I can see the below error when reloading the page after component session expires.
Cannot change transaction isolation during distributed transaction and when the connection is shared. DataSource name: "PRODB2
As per my knowledge I understood that this is happening beacuse application is trying to recreate a new connection pool while one pool instance is alive.
If this is correct can any one tell me how to destory the pool of current session when reloading the page.
Thanks in Advance,
Chinna.

What was the solution to the problem ?

Javax.transaction.RollbackException: Transaction marked for rollback

Hello all,
This is my first topic/question in the forums. I am relatively novice with J2EE programming so please pardon my ignorance. I have spend several hours thying to figure out the following issue.
So here is the scenario. I have a JSF ManagedBean called SymbolProcessBean. Here is part of its declaration
@PersistenceContext(name = "persistence/LogicalName", unitName = "MantisPU")
public class SymbolProcessBean {
@Resource
private UserTransaction utx;
}The Bean is callef by a h:command from a jsp page
<h:commandLink action="#{symbolProcessBean.processSymbol}" value="Process"/>In part of the process the Bean read data from a webpage and persists them in a MySQL database. Here is the loop:
 try {
 // Create a URL for the desired page
 String urlStr = "http://ichart.finance.yahoo.com/table.csv?s=" + this.selectedSymbol.getTicker();
 if (firstNewDay != null)
 urlStr += "&a=" + firstNewDay.get(Calendar.MONTH) +
 "&b=" + firstNewDay.get(Calendar.DATE) +
 "&c=" + firstNewDay.get(Calendar.YEAR);
 URL url = new URL(urlStr);
 // Read all the text returned by the server
 BufferedReader in = new BufferedReader(new InputStreamReader(url.openStream()));
 String str;
 outText = in.readLine() + " "; // Discard first line
 Context ctx = (Context) new InitialContext().lookup("java:comp/env");
 utx.begin();
 em = (EntityManager) ctx.lookup("persistence/LogicalName");
 SimpleDateFormat formatter = new SimpleDateFormat("yyyy-MM-dd");
 while ((str = in.readLine()) != null) {
 // Use togenizer to parse comma separated fields
 StringTokenizer strtok = new StringTokenizer(str, ",");
 // Read the data from the line
 Date recordDate = formatter.parse(strtok.nextToken());
 Float open = Float.valueOf(strtok.nextToken());
 Float high = Float.valueOf(strtok.nextToken());
 Float low = Float.valueOf(strtok.nextToken());
 Float close = Float.valueOf(strtok.nextToken());
 Integer volume = Integer.valueOf(strtok.nextToken());
 Float adj_close = Float.valueOf(strtok.nextToken());
 // Set the PriceRecord data members
 PriceRecord pr = new PriceRecord();
 pr.setSymbol(this.selectedSymbol);
 pr.setRecordDate(recordDate);
 pr.setOpen(open);
 pr.setHigh(high);
 pr.setLow(low);
 pr.setClose(close);
 pr.setVolume(volume);
 pr.setAdjClose(adj_close);
 // Create Record
 em.persist(pr);
 this.selectedSymbol.getPriceRecordCollection().add(pr);
 // Add record string to output text
 outText += str + " ";
 in.close();
 this.selectedSymbol = em.merge(this.selectedSymbol);
 utx.commit();
 } catch (Exception e) {
 utx.rollback();
 throw e;
 }All this works fine on the first invocation of the command link and the Bean reads the data from yahoo for a Stock symbol and persists into the database. When the command link is clicked again for a different stock then the utx.commit(); throws a "javax.transaction.RollbackException: Transaction marked for rollback" exception. NOTE that when I redeploy the application and run it again it will work. But it works only the first time. The second time it will throw the exception.
I am not sure why this happens. I looked in the create() methods of the autogenerated JPA Controllers (PriceRecordJpaController) and they allways commit the transaction. Why would it fail in my case? Is there a way to "refresh" the transaction?
Thank you in advance.
Edited by: kkyriako on Nov 11, 2009 10:37 PM

Thank you for your responses. I had no idea that when a runtime exception is thrown the transaction will be marked for rollback. The getCause of the exception is null however I got the following stack trace from the GlashFish log:
WARNING:
Local Exception Stack:
Exception [EclipseLink-7197] (Eclipse Persistence Services - 1.0.1 (Build 20080905)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Null primary key encountered in unit of work clone [ejb.entities.PriceRecord[idPriceRecord=null]].
 at org.eclipse.persistence.exceptions.ValidationException.nullPrimaryKeyInUnitOfWorkClone(ValidationException.java:1305)
 at org.eclipse.persistence.descriptors.changetracking.DeferredChangeDetectionPolicy.calculateChanges(DeferredChangeDetectionPolicy.java:84)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.calculateChanges(UnitOfWorkImpl.java:557)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1320)
 at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:2848)
 at org.eclipse.persistence.internal.sessions.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:223)
 at org.eclipse.persistence.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:157)
 at org.eclipse.persistence.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:68)
 at com.sun.enterprise.transaction.JavaEETransactionImpl.commit(JavaEETransactionImpl.java:411)
 at com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.commit(JavaEETransactionManagerSimplified.java:843)
 at com.sun.enterprise.transaction.UserTransactionImpl.commit(UserTransactionImpl.java:198)
 at ejb.logic.SymbolProcessBean.accessURLData(SymbolProcessBean.java:165)
 at ejb.logic.SymbolProcessBean.processSymbol(SymbolProcessBean.java:182)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.sun.el.parser.AstValue.invoke(AstValue.java:187)
 at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:297)
 at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
 at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
 at javax.faces.component.UICommand.broadcast(UICommand.java:387)
 at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
 at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
 at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
 at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
 at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
 at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:431)
 at org.apache.catalina.core.StandardWrapperValve.preInvoke(StandardWrapperValve.java:462)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:139)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:186)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
 at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:96)
 at com.sun.enterprise.web.PESessionLockingStandardPipeline.invoke(PESessionLockingStandardPipeline.java:98)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:187)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:142)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:719)
 at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:657)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:651)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1030)
 at org.apache.catalina.connector.CoyoteAdapter.doService(CoyoteAdapter.java:325)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:242)
 at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:180)
 at com.sun.grizzly.http.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:633)
 at com.sun.grizzly.http.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:570)
 at com.sun.grizzly.http.DefaultProcessorTask.process(DefaultProcessorTask.java:827)
 at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:152)
 at com.sun.enterprise.v3.services.impl.GlassfishProtocolChain.executeProtocolFilter(GlassfishProtocolChain.java:71)
 at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
 at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
 at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
 at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:67)
 at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:56)
 at com.sun.grizzly.util.WorkerThreadImpl.processTask(WorkerThreadImpl.java:325)
 at com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:184)SymbolProcessBean.java:165 is the utx.commit(). The idPriceRecord is the primary key of the table. It is an autoincrement field. I do not modify it before the em.persist(pr); statement so it goes as null. However the first time when I execute the commit everything is persisted in the database. When I run a second time for a different symbol then I get the exception until I redeploy the wed site. Maybe the persistence layer does not update the idPriceRecord with the value generated by MySQL. Nuy why does that does not cause a problem the first time?

Unable to delete request from write-optimized DSO (Error during rollback)

Hi Gurus,
I am trying to delete a delta request from a Write-Optimized DSO. This request was uploaded with a DTP from another Write-optimized DSO.
The actual overall status of the request is RED and the description of that status is now: 'Error during rollback of request DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR; only rollback allowed'.
I checked the log of all Request Operations in DataStore (from the same line where the red request is now) and I see my several attemps to delete this request under a RED radiobutton with the title Rollback. The details for this error are the following:
Could not delete request data from active table
Message no. RSODSO_ROLLBACK114
Diagnosis
The system could not delete the request data from the active table of a write-optimized DataStore object.
System Response
Write-optimized DataStore object: DTFISO02
Active table: /BIC/ADTFISO0200
Request: DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR
Procedure
Search for Notes containing the key words "Delete write-optimized DSO PSA"
I am relatively new to SAP BI 7.0 and I do not know how to delete this request. Any help will be highly appreciated !!
Leticia

Hi Leticia:
Take a look at the SAP Notes below.
Note 1111065 - "701: Delta consistency check for write-optimized DSOs"
Note 1263877 - "70SP20: Delta consistency check for write-optimized DSOs"
Note 1125025 - "P17:PSA:DSO:ODSR missing in PSA process for write-opt. DSO"
Additionally, some ideas from the alternative presented on the blog by KMR might help you.
"How to generate a selective deletion program for info provider"
Regards,
Francisco Mílán.

SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processi

Hi: We are using weblogic81 sp3. Other developers in my office ran the same porgram and got no errors.
My startWebLogic.cmd are configured exactly same as theirs.
My startWebLogic classpath:
set CLASSPATH=%WL_HOME%\server\lib\ojdbc14.jar;%WL_HOME%\server\lib\CR122067_81sp3.jar;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%;%JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
I keep getting this webservice error.
SOAP Fault:javax.xml.rpc.soap.SOAPFaultException: Exception during processing: w
eblogic.xml.schema.binding.DeserializationException: mapping lookup failure. typ
e=['java:language_builtins.util']:ArrayList schema context=TypedSchemaContext{ja
vaType=[Ljava.lang.Object;} (see Fault Detail for stacktrace)
Detail:
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webse
rvice/fault/1.0.0">weblogic.xml.schema.binding.DeserializationException: mapping
lookup failure. type=['java:language_builtins.util']:ArrayList schema context=T
ypedSchemaContext{javaType=[Ljava.lang.Object;}
at weblogic.xml.schema.binding.RuntimeUtils.lookup_deserializer(RuntimeU
tils.java:461)
thank you for your help

we used castor to do xml mapping

Error - "Exception during parsing of upload document"

Hi,
I am getting following error when trying to upload data with my custom integrator:
"The upload process has completed with errors. Press Close to return to the document and fix the errors.
Upload processing did not complete
Exception during parsing of upload document"
My custom integrator was created for UPDATE mode with view AP_HOLDS_V and Release_Holds API. I also added Standalone Query (to limit downloaded data to not released holds and user releaseable). Layout contains only API parameters fields (however I had some context fields, but error message was the same then).
I am quite new to Web ADI and I still don't have full understanding, maybe someone can also answer following questions:
- what is mapping needed for? is this to map view/table fields with the layout field?
- how does integrator know which layout field should be mapped with parameters of API?
- is there no web adi template to modify columns assigned to interface? is this only possible with UPDATE commands?
- where is bne log file stored?
I would appreciate if someone can help. I was even debugging VBA macro to see if that error is on client or server side, but it looks like it is on the server side.
Regards
Piotr

Any idea what this error message means?
6/20/12 5:45 AM CRITICAL ERROR BneUploader::Exception - going to tollback
6/20/12 5:45 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:45 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Error trying to check whether the job will be importing.
6/20/12 5:46 AM ERROR BneAsyncUploadPage.renderPage Parameter value is not a Boolean.
6/20/12 5:46 AM CRITICAL ERROR BneUploader.processUpload(), fatal exception: java.lang.ArrayIndexOutOfBoundsException: 8
6/20/12 5:46 AM CRITICAL ERROR java.lang.ArrayIndexOutOfBoundsException: 8
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.setupColumnNameMapping(BneRefPLSQLUpload.java:531)
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.preparePLSQLStatement(BneRefPLSQLUpload.java:371)
     at oracle.apps.bne.integrator.upload.BneRefPLSQLUpload.doUpload(BneRefPLSQLUpload.java:249)
     at oracle.apps.bne.integrator.upload.BneSAXUploader.processDeepestLevel(BneSAXUploader.java:2320)
     at oracle.apps.bne.integrator.upload.BneSAXUploader.startElement(BneSAXUploader.java:1178)
     at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:175)
     at oracle.apps.bne.integrator.upload.BneUploader.processUpload(BneUploader.java:309)
     at oracle.apps.bne.integrator.upload.BneAbstractUploader.processUpload(BneAbstractUploader.java:117)
     at oracle.apps.bne.integrator.upload.async.BneAsyncUploadThread.run(BneAsyncUploadThread.java:141)
Edited by: PiotrekJ on 22-Jun-2012 01:59

"Server Exception during PPR" While selecting a row in a table

Hi everyone
I have a table inside the "detailStamp" facet of another table
Whenever i select a row in this inner table, i get an NullPointerException
Has anybody seen this behaviour before?
Here's the full log for this error:
[2008-08-19T13:12:20.109-03:00] [adfinternal] [ERROR] [] [view.faces.config.rich.RegistrationConfigurator] [tid: 12] [ecid: 0000HjRjFfU000000000000000030e0M700000000H,0] [APP: current-workspace-app] Server Exception during PPR, #3[[
java.lang.NullPointerException
     at oracle.adfinternal.view.faces.model.binding.RowDataManager.setRowKey(RowDataManager.java:122)
     at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding$FacesModel.setRowKey(FacesCtrlHierBinding.java:507)
     at org.apache.myfaces.trinidad.component.UIXCollection.setRowKey(UIXCollection.java:423)
     at org.apache.myfaces.trinidad.component.UIXCollection.setClientRowKey(UIXCollection.java:653)
     at org.apache.myfaces.trinidad.component.UIXCollection.setCurrencyString(UIXCollection.java:570)
     at org.apache.myfaces.trinidad.component.UIXCollection.invokeOnComponent(UIXCollection.java:1052)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:139)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.invokeOnComponent(ContextSwitchingComponent.java:139)
     at oracle.adf.view.rich.component.fragment.UIXPageTemplate.invokeOnComponent(UIXPageTemplate.java:175)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponent.invokeOnComponent(UIComponent.java:681)
     at javax.faces.component.UIComponentBase.invokeOnComponent(UIComponentBase.java:650)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._fixClientIds(LifecycleImpl.java:785)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:263)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:178)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:15)
     at oracle.adfinternal.view.faces.webapp.rich.SharedLibraryFilter.doFilter(SharedLibraryFilter.java:135)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:281)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:69)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:281)
     at oracle.adfinternal.view.faces.activedata.ADSFilter.doFilter(ADSFilter.java:85)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:281)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:241)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:198)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:141)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at com.evermind.server.http.EvermindFilterChain.doFilter(EvermindFilterChain.java:17)
     at oracle.security.jazn.oc4j.JAZNFilter$3.run(JAZNFilter.java:434)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:308)
     at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:452)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:583)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:334)
     at com.evermind.server.http.HttpRequestHandler.doDispatchRequest(HttpRequestHandler.java:942)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:843)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:658)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:626)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:417)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:189)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:163)
     at oracle.oc4j.network.ServerSocketReadHandler$ClientRunnable.run(ServerSocketReadHandler.java:275)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     at java.lang.Thread.run(Thread.java:595)
]]

I am also facing similar issue. Please help
Caused by: java.lang.NullPointerException
at oracle.adfinternal.view.faces.model.binding.RowDataManager.setRowKey(RowDataManager.java:122)
at oracle.adfinternal.view.faces.model.binding.FacesCtrlHierBinding$FacesModel.setRowKey(FacesCtrlHierBinding.java:507)
at org.apache.myfaces.trinidad.component.UIXCollection.setRowKey(UIXCollection.java:423)
at org.apache.myfaces.trinidad.component.UIXCollection.processSaveState(UIXCollection.java:247)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:215)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at org.apache.myfaces.trinidad.component.TreeState.saveState(TreeState.java:175)
at org.apache.myfaces.trinidad.component.UIXComponentBase.processSaveState(UIXComponentBase.java:848)
at javax.faces.component.UIComponentBase.processSaveState(UIComponentBase.java:1094)
at org.apache.myfaces.trinidadinternal.application.StateManagerImpl._saveSerializedView(StateManagerImpl.java:284)
at org.apache.myfaces.trinidadinternal.application.StateManagerImpl.saveView(StateManagerImpl.java:144)
at com.sun.faces.application.ViewHandlerImpl$WriteBehindStateWriter.flushToWriter(ViewHandlerImpl.java:897)
at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:184)
at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:178)
at org.apache.myfaces.trinidadinternal.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:176)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._renderResponse(LifecycleImpl.java:627)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:245)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:205)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245)

[EMF Transaction] Exception during rollback

Similar Messages

Maybe you are looking for