DB Transaction problem in 9.0.2i

The problem is in Oracle 9iAS version 9.0.2.
Windows 2000
Oracle 8.1.7i R3 DB
When I shutdown (manualy) the server in the midle of some DB transaction, some of data are commited in the database. Everything is OK when the my application throws some Exception in the midle of transactin, no data are commited in the DB (DB rollback the transaction).
So, the server that is manualy stoped commit started transaction no matter that transaction is not finished yet.
This problem consist in both EntityEjb updating and JDBC updating DB.
Thanks in advance
Dusan Petrovic

9.0.2.0.1 is certified with XP Pro only (not Home edition), if you check on Metalink.

Similar Messages

A Major Transaction Problem!

"A" is a record which has already been inserted into a table(TBL).
"insert(Y)" is a method that inserts a given record -Y- into TBL.
"foo(X)" is a method that takes a record as a parameter and queries it on a view(VIEW). This view is a
huge select statement that selects from TBL.
Here is the problem:
insert(B);
foo( A ); /* returns true */
but
insert(B); /* B does not exist in TBL */
foo(B); /* returns false and catches an exception that "A" is not found! */
insert(Y) method is a CMP EJB method but foo(X) uses JDBC to access DBMS.
so what can cause this transaction problem?
thanks in advance,
-selcuk

Hi,
Maybe foo is running in a different transaction than insert?
Some possible causes:
-you are starting a new transaction for foo, either via the UserTransaction or via REQUIRES_NEW
-you are using a regular JDBC driver for foo instead of an XADataSource.
Did you try to set foo's transaction attribute to REQUIRED?
Best,
Guy
http://www.atomikos.com

Transaction problems

If anyone can help point me in the right direction of what I should be looking for in my configuration files for the following transaction problem. It looks like the delete is being committed one entity at a time instead of at the ened of the transaction.
I'm using OC4J, eclipselink and Spring.
I have two entities that I am trying to delete. They have a OneToOne relationship which in the underlying database (Oracle) has a deferred foreign key integrity constraint. I believe that this means that if the intities are delted in the same transaction everything should work, but if they are deleted in seperate transactions then the constraint should kick in and disallow the delete. I am using code similar to below to attempt to delete in one transaction. I am using Spring to inject an EntityManager and to control the transaction handling.
@Transactional(readOnly=true)
public class ProductServiceImpl implements ProductService{
@PersistenceContext(type = PersistenceContextType.TRANSACTION)
private EntityManager emp;
@Transactional(readOnly=false, propagation=Propagation.REQUIRES_NEW)
public void deleteProduct(Product prod){
      Object managedEntity = em.find(product.getClass(), prod.getId);
      em.remove(managedEntity);
}Spring configuration xml file
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:jee="http://www.springframework.org/schema/jee"
       xmlns:tx="http://www.springframework.org/schema/tx"
       xsi:schemaLocation="
        http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
        http://www.springframework.org/schema/jee http://www.springframework.org/schema/jee/spring-jee-2.5.xsd
        http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd">
<jee:jndi-lookup id="myEmf" jndi-name="persistence/JPA"/>
<bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/>
<bean id="txManager" class="org.springframework.orm.jpa.JpaTransactionManager">
    <property name="entityManagerFactory" ref="myEmf"/>
</bean>
<tx:annotation-driven transaction-manager="txManager"/>
<bean id="ProductService" class="ProductServiceImpl"/>
</beans>On calling the delete I get the following error message
org.springframework.transaction.TransactionSystemException -
    Could not commit JPA transaction; nested exception is
    javax.persistence.RollbackException: Exception [EclipseLink-4002]
        (Eclipse Persistence Services - 1.0 (Build SNAPSHOT - 20080508)):
    org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
    java.sql.SQLException: ORA-02091: transaction rolled back ORA-02292:
    integrity constraint (RVEL_FK) violated - child record found Error Code: 2091 Call:
    DELETE FROM RVEL_REVENUE_ELEMENT WHERE (ID = ?) bind => [6594]
    Query: DeleteObjectQuery(RevenueElement@1eafdce)I have also tried doing all this programatically, using a jndi lookup as follows
EntityManager em = null;
try{
Context ctxt = new InitialContext();
emf = (EntityManagerFactory)ctxt.lookup("jpaTest/ServerJPA");
em = emf.createEntityManager();
EntityTransaction et = em.getTransaction();
try{
    et.begin();
    em.remove(managedEntity);
    et.commit();
} finally{
    if(et != null && et.isActive()){
      et.rollback();
} catch(NamingException nme) {
} finally{
if(em != null && em.isOpen()){
    em.close();
} When debugging the error is thrown on the line
em.remove(managedEntity);before the transaction commit is called.

Thanks for the reply.
The managed entity being deleted in the call to the delete method has one to many relationship with one of the entities in the one to one relationship which then has a reference to the second entity. These references are annotated with cascade ALL.
A --> B --> C. The error is referring to entity C and its relationship back to B. The error is being thrown before the transaction is being committed.
After doing a bit more research I believe that it is caused by the lack of the following property in my persistence.xml.
<property name="eclipselink.target-server" value="OC4J_10_1_3"/>But if I put this property in then I get the errorException creating EntityManagerFactory using PersistenceProvider class org.eclipse.persistence.jpa.PersistenceProvider for persistence unit ServerJPA.

Stored procedure in a transaction problem

hello to everybody
I have an application under weblogic8.1 sp3.
I have to call an Oracle stored procedure that populate a table and I have to see the new record anly at the end of the ejb service transaction ( a Container transaction ).When the procedure terminate I see the db data before the transaction end.So I have created a XA DataSource and changed the oracle 9.2 thin drivers in oracle 9.2 thin drivers XA.But Now I receive this Oracle Error:
ORA-02089: COMMIT is not allowed in a subordinate session
Why?How Can I resolve my problem?Can Anyone Help Me?Thanks...

giorgio giustiniani wrote:
hello to everybody
I have an application under weblogic8.1 sp3.
I have to call an Oracle stored procedure that populate a table and I have to see the new record anly at the end of the ejb service transaction ( a Container transaction ).When the procedure terminate I see the db data before the transaction end.So I have created a XA DataSource and changed the oracle 9.2 thin drivers in oracle 9.2 thin drivers XA.But Now I receive this Oracle Error:
ORA-02089: COMMIT is not allowed in a subordinate session
Why?How Can I resolve my problem?Can Anyone Help Me?Thanks...It sounds like you have transactional syntax embedded in your
procedure. You can't do that and still include it in an XA
transaction.
Joe

How to prevent users from creating transactional problems?

Dear Sirs...
Using JDeveloper 10.1.2 and ADF UIX technology. If i created a web application that contains many pages. Assume the application contains pages A,B,C,D.
The end user should access the pages A then B then C then D to get the transaction executed and commited correctly.
the problem is:
1- if a user navigates from A to B to C then he press the Back button to A then he commits the transaction, the data would be stored in correctly.
2- if page C requires some preparations in page B (initalization of session variables) and the user enters page A then he changes the URL to C, then this would cause inproper execution of application and so the data would be stored incorrectly.
so how can i prevent the user from pressing the back button of the browser (which i do not think is possible) or how can i prevent him from making any errors by inproper page navigation?
thanks for any help in advance and best regards

I really don't know if this is the correct way of doing it, but we prevent navigation directly to any page within our application if the HTTP Referer header is null. If it's null, we redirect to a page that says the user should use the navigation buttons provided and not enter the page via bookmarks, history, or direct navigation via a typed in URL.

Add a New Field to Selection Screen of VL10 Transactions problem

Hello,
i have tried to add a selection field in the VL10G. I have used the docu from Gaurav Jagya (Thanks to Gaurav) an followed the steps. Here you can find the docu: Link: [http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e07c282f-e2b4-2c10-e4b3-a314fc17b6a1]
In the Step 2 , Point 4 i declare the Select option ST_MTART and use it later in Step 5 in the form USEREXIT_SELECT_OPTIONS_TRANSF.
Step 2.
4. Write the declaration of new select-option inside include ZV50RSEL_MTART.
DATA: V_MTART TYPE MARA-MTART.
SELECT-OPTIONS: ST_MTART for V_MTART.
Step 5. Transfer values from selection screen to range.
For this step, again an access key is required to modify include V50R_USEREXIT_TRANSF.
1. Open include V50R_USEREXIT_TRANSF in change mode. It will ask for an access key. Enter the same and proceed.
2. Write following line of code inside form USEREXIT_SELECT_OPTIONS_TRANSF:
CX_SELECT_OPTIONS-MTART = ST_MTART[].
When i start the VL10G it works fine, but when i start another VL10* transaction i get a dump. Example VL10:
Runtime Errors         SYNTAX_ERROR
Date and Time          20.04.2010 13:54:00
Short text
     Syntax error in program "RVV50R10C ".
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLV50R_PRE" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     The following syntax error occurred in program "RVV50R10C " in include
      "V50R_USEREXIT_TRANSF " in
     line 18:
     "field "ST_MTART unknown. .."
It dumped, because the form V50R_USEREXIT_TRANSF is used in EVERY VL10* transaction and the select-option is declared ONLY in my Z-include.
Is the someone out there, who has solved the problem? Is the an error in the docu or am i wrong?
Thanks!
Andreas

Has there been any further information on this issue in this or any other threads. I am encountering the same issue as identified by Andreas.
Thanks,
Brian

Transaction problem in ejb

Hi
I have a problem related to CMP entity beans.
I am using Oracle 9i and weblogic 6.1
Here is the description of the problem.
The transaction attribute of all the beans is set to 'Required'.
I have a PersonBean (CMP) in Person.jar mapping to Person table along with other
beans.
I have a MemberBean(CMP) in Member.jar file mapping to Member table along with
many other beans.
There is a one to many relation ship between person and member tables in Oracle
9i database :
Id in the person table is the P_Key and Person_Id in Member table is the related
foreign key.
No relationship was made between Person and Member beans as there were in two
different jar files with different deployment descriptors.
I have a stateless session bean PersonService bean.
There is a method in PersonService bean called createPerson(String name);
This method creates Person in the database using Person p = PersonHome.create(),
long personId = p.getId()..returns the primary key of the person.
PersonService calls createMember(long personId) now.
which will try to create a Member record in the database using the personId.
Now the Member bean fails to create and the transaction is rolled back with a
foreign_key violation exception.
because it cannot locate the Person EJB Primary key entry in the underlying table.
But the EJB cache is still inserted properly with Person EJB (findByPrimaryKey
works).
I feel that Member bean is not able to participate in the same transaction of
the Person bean inspite of keeping the transaction attribute to 'Required'.
When I keep the transaction of Person bean to 'RequiresNew', then the transation
of createPerson is getting committed and Member is starting a New transaction
and it gets created.
But I donot want like this.
I want all the beans to be participating in the same transaction.
According to Oracle / Weblogic documentation the default database isolation mode
Read_Committed should allow participants in transaction to see uncommitted data
while participants outside the transaction see only committed data. I have tried
other dataabase isolation modes (such as Read_Uncommitted, "Serializable") these
appear to either create other problems or not have an affect.
Any solution to this problem is highly appreciated.
Thanks
Lavanya

Previously our code was running on Weblogic where
methodA() -> Transaction Attribute -> Supports
methodB() -> Transaction Attribute -> Required
But in JBOSS in order to run the same thing we have to do
methodA() -> Transaction Attribute -> Required
methodB() -> Transaction Attribute -> Required
Any Pointers??

Transaction problem with jconn5.2

jconn5.2 and iASsp2
I am using Bean Managed Transaction in my application, start the first
transaction is fine, but once the application going to start another
transaction, errors occoured:
"the transaction onwer is not in current thread".

Hi,
I've had the very same problem with RAD.
Try to set the Transaction attribute to SUPPORTS. With SUPPORTS the EJB method will use the same transaction as the caller.
package hu.bme.ett.raktar.facade;
import hu.bme.ett.raktar.ejbs.Raktar;
import hu.bme.ett.raktar.ejbs.controller.RaktarManager;
import javax.ejb.Stateless;
import javax.ejb.TransactionAttribute;
import javax.ejb.TransactionAttributeType;
@Stateless
@TransactionAttribute(TransactionAttributeType.SUPPORTS)
public class RaktarListazas implements RaktarListazasLocal {
     RaktarManager rm = new RaktarManager();
     * Default constructor.
    public RaktarListazas() {
        // TODO Auto-generated constructor stub
    public Raktar getRaktar(long raktId) {
         return rm.findRaktarByRaktId(raktId);
    public void createRaktar(long raktId) {
         Raktar r = new Raktar();
         r.setRaktId(raktId);
         r.setRaktAzonosito("Y1RAK-01" + raktId);
         r.setMegnevezes("Elso raktaram");
         try {
               rm.createRaktar(r);
          } catch (Exception e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
}Cheers,
Viktor

Global transaction problem with JDriver/Oracle and Oracle XA

We are haveing serious problems with Container Managed Transactions on Bea 6.1
and Oracle with EJB having set "Required" for all methods. We have tried in vain
to make it work with JDriver as well as OracleXAClient. Both fail at sometime
during the execution throwing "Not called in cotext of global transaction" (with
JDriver) OR "XAER_PROTO : Routine was invoked in an
inproper context start() failed on resource 'OracleXAPool'" (this one with oracle
XA).
1.) Weblogic JDriver-XA:
DatabaseMetaData metaData = dataSource.getJDBCConnection.getMetaData();
ResultSet resultSet = metaData.getTables(null, null, tableName.toUpperCase(),
new String[]{"TABLE"});
This fails immmediately saying that it was not called from global transaction.
Interesting thing is that with OracleXA, it doesnt say this exception at this
check point.
2) Oracle XA
Okie, we couldnot read through the CLOB using it so for reading CLOB, we used
direct jdbc connection and then did away with it. Now all next sql queries were
executed against oracle pool using XA data source with OracleXAClient. But at
some point we again ran into the problem "XAER_PROTO : Routine was invoked in
an
inproper context start() failed on resource 'OracleXAPool'"
3 Oracle Thin Driver
everything always works with it.

AFAIR this issue was resoved by moving tx opreations out from non-tx
methods.
Regards,
Slava
"Apurb Kumar" <[email protected]> wrote in message
news:[email protected]...
Jawad,
It would be nice if you can post the full stack trace error message. Didyou try moving to
the latest service pack (sp2) for WLS6.1.
Thanks,
Jawad Mahmood wrote:
Yes we had correctly set TXDataSource and let it to point to the right
connection
pool each time and it worked well with oracle thin driver but not whenwe switched
the pool to JDriver or OracleXAClient. Note that we could aways confirmthat pool
was successfully created alongwith we could retrieve connection from itvia TXDatSource,
things gave problem after we attempted to do what i had mentioned in mylast posting.
>>
Also with JBoss 2.4.4 things work pretty well. So couldnt be our codeproblem.
"Slava Imeshev" <[email protected]> wrote:
Jawad,
Did you set up TxDataSource?
Regards,
Slava Imeshev
"Jawad Mahmood" <[email protected]> wrote in message
news:[email protected]...
We are haveing serious problems with Container Managed Transactionson
Bea 6.1
and Oracle with EJB having set "Required" for all methods. We havetried
in vain
to make it work with JDriver as well as OracleXAClient. Both fail atsometime
during the execution throwing "Not called in cotext of global
transaction"
(with
JDriver) OR "XAER_PROTO : Routine was invoked in an
inproper context start() failed on resource 'OracleXAPool'" (this onewith
oracle
XA).
1.) Weblogic JDriver-XA:
DatabaseMetaData _metaData =
_dataSource.getJDBCConnection.getMetaData();
ResultSet resultSet = metaData.getTables(null, null,tableName.toUpperCase(),
new String[]{"TABLE"});
This fails immmediately saying that it was not called from globaltransaction.
Interesting thing is that with OracleXA, it doesnt say this exceptionat
this
check point.
2) Oracle XA
Okie, we couldnot read through the CLOB using it so for reading CLOB,we
used
direct jdbc connection and then did away with it. Now all next sqlqueries
were
executed against oracle pool using XA data source with
OracleXAClient.
But
at
some point we again ran into the problem "XAER_PROTO : Routine wasinvoked
in
an
inproper context start() failed on resource 'OracleXAPool'"
3 Oracle Thin Driver
everything always works with it.
Apurb Kumar

CNE5 transaction problem in Upgrade ECC5.0

I have problem in the transaction CNE5 . this transaction is working in 4.6b but its showing dump in ECC5.0. saying ABAP errror.we r upgrading from 4.6b to ECC5.o
Can u plz help me
Thanks

its saying
12.11.2005 07:30:41 bissap1 120 C CREATE_OBJECT_CLASS_NOT_FOUND CX_SY_CREATE_OBJECT_ERROR CL_EXIT_MASTER================CP 1

Not posted Treasury transactions- problem with new Business area (NewGL)

Hi all,
I have to change the Treasury account assignment objects due to a restructure. Currently, all TR transactions are assigned to one business area only.
In future, there will be 3 (different) business areas.
I have added new products, transaction tpyes etc and I have made further customising
settings. It looks ok and I can enter new transactions, settle and post them.
Problems I do have with already existing deals (fixed term and Forex transactions).
In here I get posting errors with message:
Balancing field "Business Area" in line item 001 not filled
Message no. GLT2201
I have added additional account assignment references for the new Business Areas
and assigned to product types and account assignment
What happens when I create a deal?
Is that information (product type/ transaction/ account assignment) alreaedy stored in a table and used, when processing the deal further?
Can I somehow change that original assignment per deal now?
I think my problem lies in that the system wants to use the old assignment but also the new and it comes to conflict in field business area.
Any hints much appreciated and will be reqarded as usual.
Thanks
Hein

Assign Business area in the following step (ECC 6.0)
SPRO - Financial Supply Chain Management - Treasury and Risk Management - Transaction Manager - General Settings - Accounting - Link to Other Accounting Components - Allocate Additional Account Assignments to Account Assignment References
Kalyan

Transaction problems in Stateless EJB

I have problems as follows. my client is a servlet which call method B in stateless ejb, In side of method B, there is a loop from which antoher method C in this same ejb is called repeatedly. I want each call of method C being a separate transaction. I can not make this work. the final result will always be one transaction from for loop. I set the transaction attribute as Requires for method B, and Requires New for method C. Please offer some help.
Thanks.
void ejbMethodB(){
where(mycondition)
ejbMethodC()
I like to make each call of ejbMethodC be a standalone transaction instaed of the running results from the whole loop being a transaction

First of all, thank you so much for your time.
I also doubt the problem is Resin. But "Required" attribut works fine. The following is the coding:
EJB implementation:
//mehtodB
public RequestResult getDailyCreateUpdateInfo(Request request)
throws RemoteException, ProcessException
boolean testFlag = false;
List resultList = null;
ClaimsDAO dao = null;
Map mapRequestData = getRequestData(request);
int num = 0;
InterfacePushProcess push_process = (InterfacePushProcessRemote)(mySessionCtx.getEJBLocalObject());
try {
//Call DAO and get Student, ExchangeVisitor and their dependent information
dao = (ClaimsDAO) getEntityObject(ClaimsDAO.class.getName());
dataPushBO = new ClaimsDataImpl(mapRequestData);
//get the list of categories for DOS or US-VISIT
interdataList = dataPushBO.createCategoryList();
Iterator iterator = interdataList.iterator();
System.out.println("before invokeTransacprocess. ");
//testing
this.invokeTransacProcess();
//process all the categories for DOS or US-VISIT
while(iterator.hasNext())
interconfigData = (InterfaceDataConfig) iterator.next();
processOneCategory(mapRequestData, interconfigData, dao);
} catch (Exception e) {
mySessionCtx.setRollbackOnly();
log.logp(Level.SEVERE, classname, "getDailyCreateUpdateInfo", e.getMessage());
Object[] args = createExceptionArgs();
args[0] = request.getName();
throw new ProcessException(IMessage.ENTITY_POPULATION_FAILED, args, e);
return new RequestResult(request, resultList);
//mehtodC
public void processOneCategory(Map reqmap, InterfaceDataConfig interconfigData, ClaimsDAO dao)
throws ProcessException
List pageList = null;
String fileType = interconfigData.getGroupName(); //student, dep etc
String countKey = interconfigData.getCountKey();
String logKey = interconfigData.getIDKey();
UserTransaction trans = null;
int count = 0;
boolean process = false;
String groupname = interconfigData.getGroupName();
log.logp(Level.INFO, classname, "processOneCategory() ", "group name = " + groupname);
try
Context ct = new InitialContext();
trans = (UserTransaction) ct.lookup("java:comp/UserTransaction");
trans.begin();
String startTime = convert.getTimestamp();
log.logp( Level.INFO, classname, "processOneCategory() ", "processing start time: "+startTime);
pageList = processOnePage(interconfigData, dao);
if (pageList.isEmpty())
log.info("There are no records which need be processed.");
else
do
try
this.displayResult(pageList);
process = pageOutputProcessor(reqmap, interconfigData, pageList);
pageList.clear();
pageList = this.processOnePage(interconfigData, dao);
} catch (Exception ex) {
mySessionCtx.setRollbackOnly();
String msg = "Error while processing one page : " + ex.getMessage();
log.logp(Level.SEVERE, classname, "processOneCategory() ", msg);
throw new ProcessException(msg);
} while (!pageList.isEmpty());
//testing separate transaction
if(groupname.equalsIgnoreCase("STUDENT"))
trans.commit();
else
trans.rollback();
} catch (Exception t) {
mySessionCtx.setRollbackOnly();
String m = "Error when processing results from ClaimsDAO's : " + t.getMessage();
log.logp(Level.SEVERE, classname, "processOneCategory() ", m);
throw new ProcessException(m);
} finally {
I put both methods: getDailyCreateUpdateInfo and processOneCategory in remote interface so I can use your suggested method to reference the EJB instance.
Servlet Client call "getDailyCreateUpdateInfo" method (the transaction attribute is Required) in which call processOneCategory(,,) method (transaction attribute is RequiresNew).
I put some testing code to see if I can achieve the separate transaction in each call of mehtod processOneCategory(,,) , it does not work. If I use Bean Managed Transaction, it works right away. My app. server is Resin 2.1.4.
Again, Thank you.
Mark

Transaction problem, Unable to start RSA1

Hello every one:
I am not able to start RSA1 transaction in our BW system.
RSA1 transaction hangs. Can some one tell me how to trouble shoot please.
Regards,
KG

Balkrishna
BW 3.5, Sql Server 2003. We just upgraded support packs to SP18.
This is the only transaction that has been affected. When Executing RSA1,
If you look at sm66, it sits on TBTCO table for ever. There are no short dumps or errors in database or system logs. This is the only transaction that has issues.
Because of this behavior I applied note 924198, however the problem still there.
Regards,
KG

Transaction Problem - Timeout

Folks
I am experiencing a Transaction timeout error on a supposed non-transacted method.
Here's the scoop. The Stateless Session bean MemberManager has the Transaction
Attribute set either as "SUPPORTS" or "REQUIRED". Gets and Finds are set to "SUPPORTS"
The Entity beans MemberBean and PolicyHolderBean have all method transaction
attributes set to SUPPORTS. As you can tell transaction mgt is handled at the
SBlevel.
<container-transaction>
<method>
<ejb-name>MemberManager</ejb-name>
<method-name>getMemberModel</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>MemberBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>PolicyHolderBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Supports</trans-attribute>
</container-transaction>
The call to MemberManager.getMemberModel is thus non-transacted. Yet I recieve
(from time to time) a Transaction timeout on the PolicyHolderBean.findByPrimaryKey.
(FYI there is a 1:1 CMR relationship between Member and PolicyHolder). The stack
trace follows. Any help is appreciated. Why is this being transacted?
####<Sep 23, 2002 2:12:43 PM EDT> <Error> <com.hmcng.service.job.AbstractJob>
<HMCAPPSVR3> <NextGen3> <Thread-111> <> <21104:3b4203690f8f04a5> <000000> <abstractjob.generate.exception.exception:
letterservice.updatejobstatuserror.remoteexception: Message was not sent because
transaction is not active. Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Rolled
back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed
out after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=66,seconds left=10,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=NextGen3),SCInfo[hmc_letters+NextGen3]=(state=rolledback),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)>
####<Sep 23, 2002 2:12:43 PM EDT> <Error> <com.hmcng.service.job.AbstractJob>
<HMCAPPSVR3> <NextGen3> <Thread-111> <> <21104:3b4203690f8f04a5> <000000> <abstractjob.generate.exception:
memberservice.getmembermodel.remoteexception: member.unable.to.find.member: Problem
in findByPrimaryKey while preparing or executing statement: 'weblogic.jdbc.rmi.SerialPreparedStatement@14b404':
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)]). No further
JDBC access is allowed within this transaction.
java.sql.SQLException: The transaction is no longer active (status = Rolling Back.
[Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out
after 33 seconds
Name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],Xid=21104:3b4203690f8f04a5(3304037),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=33,seconds left=30,activeThread=Thread[Thread-111,2,main],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[hmc_letters+NextGen3]=(state=active),properties=({ISOLATION
LEVEL=2, weblogic.transaction.name=[EJB com.hmcng.member.entity.MemberBean.findByPrimaryKey(java.lang.Integer)],
weblogic.jdbc=t3://172.25.64.69:7901, LOCAL_ENTITY_TX=true}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+,
Resources={})],CoordinatorURL=NextGen3+172.25.64.69:7901+hmc_letters+)]). No further
JDBC access is allowed within this transaction.
at weblogic.jdbc.jts.Connection.checkIfRolledBack(Connection.java:508)

          "Jeremy Meyer" <[email protected]> wrote:
          >I am running WL 6.0 on Win NT 4.0 SP 6
          >
          >I am having a problem with a transaction timing out while doing some stuff
          >with EJBs. They do some calculations that can take a few minutes and thus
          >the transactions must last that long but they are timing out after 30
          >seconds. I went to the console and changed the timeout time to a higher
          >setting. This seemed to work but then when I did the same thing a little
          >while later it timed out after 30 seconds again. I look at the console and
          >it says the timeout time is 180 seconds. Any thoughts on what I am doing
          >wrong/why it is acting this way? Thanks.
          Ugh. This is a known problem. As it turns out, EJB's deployment descriptor defaults
          to 30 seconds if a timeout value is not specified. It then overrides the JTA subsystem's
          default timeout settings.
          The workaround is to always specify a valid transaction timeout in the EJB's DD,
          and not to let it default.
          -Sriram

Single transaction problem

Hi Gurus,
I have a scenario in Portal where I need to publish SAP Transactions in EP such a way that user can execute this particular transaction only & no other transactios.For that I have created SAP transaction Iview & SAP IAC IVIEW in portal and set the ~SINGLETRANSACTION parameter to 1 in the webgui for transaction iview and in the ITS sub element for IAC Iview.
By setting that user is able to do one transaction only but after the transaction complete it is showing "Logged Off Successfully"....its not even showing message generated by SAP like "document saved or order created".
Please give your expert suggestion to avoid the problem.
Regards
Indranil

Hi Michael,
I think I have not explain my problem properly.See,I have some ECC transactions which I have published in portal via transaction Iview & IAC component Iview.To give the user access to the one transaction only & not to go back to the mySAP menu I set the ~Singletransaction parameter to 1 in the WebGui.
Now when the user complete the transaction instead of showing "Document Saved or Order created" it is showing Logged Off from Web Application Server.I would like to show the messages generated by SAP & give the user access for single transaction.
Regards
Indranil

DB Transaction problem in 9.0.2i

Similar Messages

Maybe you are looking for