Configure Weblogic to force JTA transactions to commit.
Hello Everyone,
I have a webservice running on a Tomcat Server and connected to an Oracle DB.
Data is being selected, pulled out and send through the weblogic JMS client.
This data is marked as sent but my code is restricted by the system´s design and is not allowed to commit the transactions. This is responsibility of the Weblogic’s JTA layer.
Here is the problem: my code is being called every minute and it is retrieving records that should already be marked.
And worst: the Java webservice code can’t be modified by client’s request.
How can I setup my Weblogic server to ensure the mark?
Is there any other place I should look?
Thanks in advance.
M.
Edited by: 914451 on Feb 15, 2012 5:17 AM
The configuration for JTA can be found in the admin console. The domain configuration, JTA tab shows how JTA is configured.
On the deployments, monitoring tab you can find all the subsystems runtime information. What you are probably interested in
is the JDBC (data sources and connection pooling). Here you can enable (by clicking on customize this table) how many active
connections are present at the current moment. When the active connections keep growing (or the leaked connection count)
there is probably never any commit or rollback issued (and maybe worse the connections are not returned to the pool)
When the third party is using EJB's, you see information about the transaction in the monitoring, EJBs tab. Here also you
need to customize the table to add the transactions committed, rolled back, timed out attributes.
The specific JTA information for a particular server (to which the application is deployed) can be found in the environment, servers, server_name,
monitoring, JTA. Here you see different tabs, such as Summary (that gives you an overview of the transactions). There is also an Transactions
tab that gives you the possibility the commit, roll back transactions.
When you want to get behind what is really going on you have to know what the third party is doing.
Similar Messages
-
Doubts on nonxa oracle datasources in Weblogic JTA transaction
I am doing some studying on XA transaction handling in weblogic 10.3.6. I read a lot materials on web saying that can't enlist more than 1 non xa datasources inside one single XA transaction, so I am doing a simple test: trying to update one record in one oracle database, and inserting one record in another.
The test code is below:
@Stateless(mappedName = "nativeQueryTest")
@TransactionManagement(TransactionManagementType.CONTAINER)
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class DaoEjb implements .... {
@PersistenceContext(unitName="nonxa.unit")
private EntityManager nonXAPC;
@PersistenceContext(unitName="another.nonxa.unit")
private EntityManager anotherNonXAPC;
@Override
public void doUpdateWithNonXaDss() {
Employee l_entity = nonXAPC.find(Employee.class, "tom");
l_entity.setAge(new Random().nextInt());
Department l_dep = new Department();
l_dep.setName("dept" + new Random().nextInt());
l_dep.setEmployeeNum(new Random().nextInt());
anotherNonXAPC.persist(l_dep);
The persistence unit definitions are:
<persistence-unit name="nonxa.unit" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>nonxa.ds</jta-data-source>
<class>entity.Employee</class>
<exclude-unlisted-classes>true</exclude-unlisted-classes>
<properties>
<property name="eclipselink.target-database" value="Oracle" />
<property name="eclipselink.jdbc.batch-writing" value="Oracle-JDBC" />
<property name="eclipselink.target-server" value="WebLogic_10" />
<property name="eclipselink.logging.parameters" value="true" />
<property name="eclipselink.logging.logger" value="ServerLogger" />
</properties>
</persistence-unit>
<persistence-unit name="another.nonxa.unit" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>another.nonxa.ds</jta-data-source>
<class>entity.Department</class>
<exclude-unlisted-classes>true</exclude-unlisted-classes>
<properties>
<property name="eclipselink.target-database" value="Oracle" />
<property name="eclipselink.jdbc.batch-writing" value="Oracle-JDBC" />
<property name="eclipselink.target-server" value="WebLogic_10" />
<property name="eclipselink.logging.parameters" value="true" />
<property name="eclipselink.logging.logger" value="ServerLogger" />
</properties>
</persistence-unit>
For the two data sources, they are pointed to two different oracle databases on two different physical servers. I use "oracle.jdbc.OracleDriver" as the drivers, and also make sure that "Support Global Transaction" options un-selected.
I used a simple client to invoke the EJB, and saw the method completes without any error: the first record is updated and second record is inserted! Therefore I am really confused:
1) is the JTA transaction XA or not in my small EJB?
2) if it's XA, why can I use two non-XA datasources inside this XA transaction?Why do you think this should fail? Looks to me like you have two isolated transactions going on that have no relation to each other.
-
Weblogic 7 SP5 SQL Exceptions follow a JTA transaction timeout
I have a problem in Weblogic 7 SP5 that was not happening in SP2. I'm using the
Weblogic jDriver (weblogic.jdbc.mssqlserver4.Driver)
I have a transaction that times out due to JTA transaction timeout, and then gets
marked for rollback. For several minutes after the timeout, I get many SQL Exceptions
with bogus messages like "invalid column name" when the column name is, in fact,
correct.
Then the weblogic log file shows "Exception during rollback of transaction" (javax.transaction.SystemException:
Heuristic hazard). Next, the connection is tested on reserve, this test fails,
and the connection is refreshed. As soon as the connection is refreshed, I stop
getting SQL exceptions and everything starts working correctly again.
It seems like the transaction timeout is making the connection go bad, and somehow
other requests are using this bad connection before the transaction finishes rolling
back. What could the problem be? Some excerpts from my app log and weblogic log
are below.
com.workpoint.server.ejb.WorkPointEJBException: The transaction is no longer active
- status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 901 seconds
Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17109:68c10765ba68aaaa(12114044),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=901,seconds left=60,activeThread=Thread[WorkQueueThread[q=1, qName=ProcReleaseTaskWorkers,
id=6],5,WorkQueueGroup[id=1, name=ProcReleaseTaskWorkers]],ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=ended,assigned=none,xar=weblogic.jdbc.jts.Connection@18cd616,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=active),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+)]'.
No further JDBC access is allowed within this transaction.SQL Command = INSERT
INTO WP_PROCI_NODE_HIST (NODE_HIST_ID, NODE_HIST_DB, PROCI_ID, PROCI_DB, PROCI_NODE_ID,
PROCI_NODE_DB, NODE_ITERATION, NODE_STATE_ID, ROW_VERSION, LU_ID, LU_DATE) VALUES
weblogic.jdbc.mssqlserver4.TdsException: Invalid column name 'user_fname'.
[from weblogic log]
####<Jun 17, 2004 8:14:16 AM MDT> <Error> <EJB> <EDWARDS> <edwards-s1> <WorkQueueThread[q=1,
qName=ProcReleaseTaskWorkers, id=7]> <kernel identity> <> <010025> <Exception
during rollback of transaction Name=[EJB com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],Xid=17439:68c10765ba68aaaa(31878774),Status=Rolled
back. [Reason=weblogic.transaction.internal.AppSetRollbackOnlyException],HeuristicErrorCode=XA_HEURHAZ,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=3,seconds left=57,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=rolledback,assigned=edwards-s1,xar=weblogic.jdbc.jts.Connection@15e1b7e,re-Registered
= false),SCInfo[DomainManager+edwards-s1]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
com.storeperform.taskmgr.ejb.procrelease.ProcReleaseBean.distributeToOrgUnit(com.storeperform.taskmgr.values.DistributionUnit)],
weblogic.jdbc=t3://10.10.3.17:7001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+,
Resources={})],CoordinatorURL=edwards-s1+10.10.3.17:7001+DomainManager+t3+): javax.transaction.SystemException:
Heuristic hazard: (weblogic.jdbc.jts.Connection, HeuristicHazard, (javax.transaction.xa.XAException:
I/O exception while talking to the server, java.io.EOFException))
####<Jun 17, 2004 8:14:17 AM MDT> <Warning> <JDBC> <EDWARDS> <edwards-s1> <ExecuteThread:
'8' for queue: 'default'> <kernel identity> <> <001094> <A connection from pool
"sp_connection_pool" was tested during reserve with the SQL "select 1" and failed:
weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the server,
java.io.EOFException
...[stack trace omitted]...
This connection will now be refreshed.>Brad Swanson wrote:
According to BEA's documentation, the jDriver is deprecated (no longer supported)
in WLS 7 SP5. Not sure when they stopped supporting it, but sometime after SP2,
apparently. Our solution, unfortunately, was to stay with SP2. Using the newer,
supported JDBC driver would presumably fix the problem, but we didn't have time
to do a full regression test with a different driver.Hi, no. The jDriver is deprecated, not unsupported. For WLS releases that contain
the jDriver it will be supported for as long as we support the WLS release!
Deprecation just means that we may choose to not supply that driver in any future
release, and will not support it in that or any subsequent release.
Practically, much depends on which jDriver you're using. In decreasing order
of practical support we have: The weblogic.jdbc.oci.Driver to Oracle: We do actively
continue to fix bugs in it. The weblogic.jdbc.mssqlserver4.Driver: Very unlikely that
we will fix any new problem with it. The weblogic.jdbc.ifmx.Driver: Even less
likely that we will do anything with it...
I hope that makes it better for you.
Joe -
How to have the JTA transaction in ServiceEndpoint interface java method
Hi,
I have query how to have the JTA transaction in SEI(Service endpoint interface) generated by WSDL.
I have a MDMListener (using MDM API) which looks for a recordchange in MDM repository which needs to be send to PI7.1 via soap request.
1) I had imported the WSDL from ESR(PI) and generated outside-in proxy.
2) Created ejb3.0 stateless session bean using NWDS
3) Created web service client application by generating the WSDL again (by Generate client)
4)Added a method callPI()with Service and i set the context with endpointaddress property as the soap location of the sender agreement configured in PI7.1.
The damean thread listener(EventDispatcher) looks for MDM record change and it calls the method callPI() from ejbsession bean by lookup to transfer the record to PI7.1 system via webservices(web method). I hit the below error.
Exception com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Status of ( SAP J2EE Engine JTA Transaction : 06223ffffffa20048fffffffe ) should be active, but it is STATUS_COMMITTED = 3.
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronizationWithoutStatusChecks(TransactionImpl.java:672)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronization(TransactionImpl.java:641)
at com.sap.engine.services.ts.transaction.TxLevelSynchronizations.addSynchronization(TxLevelSynchronizations.java:118)
at com.sap.engine.services.ts.transaction.TxManagerImpl.registerSynchronization(TxManagerImpl.java:829)
at com.sap.transaction.TxManager.registerSynchronization(TxManager.java:303)
at com.sap.engine.messaging.runtime.j2ee.sapengine.SAPTransactionManager.registerSynchronization(SAPTransactionManager.java:126)
at com.sap.engine.messaging.impl.util.tx.TxController.<init>(TxController.java:83)
//Method in the ejb stateless session bean
@WebServiceRef (name="DistributeMasterDataService") DistributeMasterDataService service;
@RelMessagingNW05DTOperation(enableWSRM=true)
public void callPi(DistributeMasterDataRequestType req) {
port.distributeMasterDataOutA(req);// the distributeMasterDataOutA is the method available in SEI..Here is the issue on JTA
For the first time the message(req object)transmits to the PI successfully,but for the second call i hit this JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3.
I tried chanding the transactionmanagement from container to bean.
@TransactionManagement(value=TransactionManagementType.BEAN)
@TransactionAttribute(value=TransactionAttributeType.REQUIRES_NEW)
I wanted to know how can i have the JTA transaction status in SEI(service enpoint interface)java method distributeMasterDataOutA.Since it is an interface i dont know what annotation can be used.
If its possible i can try this UserTransaction,
http://help.sap.com/saphelp_nw04/helpdata/de/f6/7a8df922db4ab79342b46c48dac7d0/content.htm
ut.begin() & ut.commit(),so that everytime this method is called it will treat as a new transaction..
Let me know if you need more details??,Any idea provided would be great.
Thanks
SabarinathanHello everybody,
The issue resolved,we need to have the bean management transaction type and not the container.
and the transactionattribute value as Requires New
rgds
Sabarinathan
Edited by: Sabarinathan Selvaraj on May 12, 2009 2:17 PM -
Coherence and EclipseLink - JTA Transaction Manager - slow response times
A colleague and I are updating a transactional web service to use Coherence as an underlying L2 cache. The application has the following characteristics:
Java 1.7
Using Spring Framework 4.0.5
EclipseLink 12.1.2
TopLink grid 12.1.2
Coherence 12.1.2
javax.persistence 12.1.2
The application is split, with a GAR in a WebLogic environment and the actual web service application deployed into IBM WebSphere 8.5.
When we execute a GET from the server for a decently sized piece of data, the response time is roughly 20-25 seconds. From looking into DynaTrace, it appears that we're hitting a brick wall at the "calculateChanges" method within EclipseLink. Looking further, we appear to be having issues with the transaction manager but we're not sure what. If we have a local resource transaction manager, the response time is roughly 500 milliseconds for the exact same request. When the JTA transaction manager is involved, it's 20-25 seconds.
Is there a recommendation on how to configure the transaction manager when incorporating Coherence into a web service application of this type?Hi Volker/Markus,
Thanks a lot for the response.
Yeah Volker, you are absolutely right. the 10-12 seconds happens when we have not used the transaction for several minutes...Looks like the transactions are moved away from the SAP buffer or something, in a very short time.
and yes, the ABAP WP's are running in Pool 2 (*BASE) and the the JAVA server, I have set up in another memory pool of 7 GB's.
I would say the performance of the JAVA part is much better than the ABAP part.
Should I just remove the ABAP part of the SOLMAN from memory pool 2 and assign the JAVA/ABAP a separate huge memory pool of say like 12-13 GB's.
Will that likely to improve my performance??
No, I have not deactivated RSDB_TDB in TCOLL from daily twice to weekly once on all systems on this box. It is running daily twice right now.
Should I change it to weekly once on all the systems on this box? How is that going to help me?? The only thinng I can think of is that it will save me some CPU utilization, as considerable CPU resources are needed for this program to run.
But my CPU utilization is anyway only like 30 % average. Its a i570 hardware and right now running 5 CPU's.
So you still think I should deactivate this job from daily twice to weekly once on all systems on this box??
Markus, Did you open up any messages with SAP on this issue.?
I remember working on the 3.2 version of soultion manager on change management and the response times very much better than this as compared to 4.0.
Let me know guys and once again..thanks a lot for your help and valuable input.
Abhi -
Hi,
I am currently porting an application from Websphere 3.5 to Weblogic 6.1.
I have an Oracle 8.1.7 database.
I have a problem when rollbacking JTA transaction.
I have a session bean manipulating Entity beans (CMP & BMP) within a single
method.
This method creates beans and then update them.
The issue is that during the update, the application generates an exception
(system or applicative). The method rollbacks the transaction, but if I look
in the database, the insert requests are not rollbacked !
I have tried two different approach:
1) container manage transaction: I catch the exception and then call
setRollbackOnly()
2) bean manage transaction: I retrieve the user transaction, and apply the
rollback on exception.
What's wrong with that ? This actually works fine on Websphere.
Regards
Jacques DesmazieresMake sure that you are using a TxDataSource and not a plain DataSource.
(This is configured in the console.)
-- Rob
Jacques Desmazieres wrote:
Hi,
I am currently porting an application from Websphere 3.5 to Weblogic 6.1.
I have an Oracle 8.1.7 database.
I have a problem when rollbacking JTA transaction.
I have a session bean manipulating Entity beans (CMP & BMP) within a single
method.
This method creates beans and then update them.
The issue is that during the update, the application generates an exception
(system or applicative). The method rollbacks the transaction, but if I look
in the database, the insert requests are not rollbacked !
I have tried two different approach:
1) container manage transaction: I catch the exception and then call
setRollbackOnly()
2) bean manage transaction: I retrieve the user transaction, and apply the
rollback on exception.
What's wrong with that ? This actually works fine on Websphere.
Regards
Jacques Desmazieres -
JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3
Hi,
I have query how to have the JTA transaction in SEI(Service endpoint interface) generated by WSDL.
I have a MDMListener (using MDM API) which looks for a recordchange in MDM repository which needs to be send to PI7.1 via soap request.
1) I had imported the WSDL from ESR(PI) and generated outside-in proxy.
2) Created ejb3.0 stateless session bean using NWDS
3) Created web service client application by generating the WSDL again (by Generate client)
4)Added a method callPI()with Service and i set the context with endpointaddress property as the soap location of the sender agreement configured in PI7.1.
The damean thread listener(EventDispatcher) looks for MDM record change and it calls the method callPI() from ejbsession bean by lookup to transfer the record to PI7.1 system via webservices(web method). I hit the below error.
Exception com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Status of ( SAP J2EE Engine JTA Transaction : 06223ffffffa20048fffffffe ) should be active, but it is STATUS_COMMITTED = 3.
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronizationWithoutStatusChecks(TransactionImpl.java:672)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.registerSynchronization(TransactionImpl.java:641)
at com.sap.engine.services.ts.transaction.TxLevelSynchronizations.addSynchronization(TxLevelSynchronizations.java:118)
at com.sap.engine.services.ts.transaction.TxManagerImpl.registerSynchronization(TxManagerImpl.java:829)
at com.sap.transaction.TxManager.registerSynchronization(TxManager.java:303)
at com.sap.engine.messaging.runtime.j2ee.sapengine.SAPTransactionManager.registerSynchronization(SAPTransactionManager.java:126)
at com.sap.engine.messaging.impl.util.tx.TxController.<init>(TxController.java:83)
//Method in the ejb stateless session bean
@WebServiceRef (name="DistributeMasterDataService") DistributeMasterDataService service;
@RelMessagingNW05DTOperation(enableWSRM=true)
public void callPi(DistributeMasterDataRequestType req) {
port.distributeMasterDataOutA(req);// the distributeMasterDataOutA is the method available in SEI..Here is the issue on JTA
For the first time the message(req object)transmits to the PI successfully,but for the second call i hit this JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3.
I tried chanding the transactionmanagement from container to bean.
@TransactionManagement(value=TransactionManagementType.BEAN)
@TransactionAttribute(value=TransactionAttributeType.REQUIRES_NEW)
I wanted to know how can i have the JTA transaction status in SEI(service enpoint interface)java method distributeMasterDataOutA.Since it is an interface i dont know what annotation can be used.
If its possible i can try this UserTransaction,
http://help.sap.com/saphelp_nw04/helpdata/de/f6/7a8df922db4ab79342b46c48dac7d0/content.htm
ut.begin() & ut.commit(),so that everytime this method is called it will treat as a new transaction..
Let me know if you need more details??,Any idea provided would be great.
Thanks
Sabarinathan
Edited by: Sabarinathan Selvaraj on May 7, 2009 12:31 PM
Edited by: Sabarinathan Selvaraj on May 7, 2009 12:32 PMHi,
May be i have not mention the issue clearly.Let me know mention the issue with details.
I have a MDMListener (using MDMPI) which looks for a recordchange in MDM repository which needs to be send to PI7.1 via soap request.
1) I had imported the WSDL from ESR(PI) and generated outside-in proxy.
2) Created ejb3.0 stateless session bean using NWDS
3) Created web service client application by generating the WSDL again (by Generate client)
4)Added a method callPI()with Service and i set the context with endpointaddress property as the soap location of the sender agreement configured in PI7.1.
@WebServiceRef (name="DistributeMasterDataService") DistributeMasterDataService service;
@RelMessagingNW05DTOperation(enableWSRM=true)
public void callPi(DistributeMasterDataRequestType req) {
port.distributeMasterDataOutA(req);// the distributeMasterDataOutA is a method available in SEI
For the first time the message(req object)transmits to the PI successfully,but for the second call i hit this JTA Transaction :status should be active, but it is STATUS_COMMITTED = 3.
I tried chanding the transactionmanagement from container to bean.
@TransactionManagement(value=TransactionManagementType.BEAN)
@TransactionAttribute(value=TransactionAttributeType.REQUIRES_NEW)
I wanted to know how can i have the JTA transaction status in SEI(service enpoint interface)java method distributeMasterDataOutA.Since it is an interface i dont know what annotation can be used.
If its possible i can try this UserTransaction, ut.begin() & ut.commit(),so that everytime this method is called it will treat as a new transaction..
Let me know if you need more details??,Any idea provided would be great.
Thanks
Sabarinathan -
JTA Transaction log circular collision
Greetings:
Just thought I'd share some knowledge concerning a recent JTA-related
issue within WebLogic Server 6.1.2.0:
On our Production cluster, we recently ran into the following critical
level problem:
<Jan 10, 2003 6:00:14 PM EST> <Critical> <JTA> <Transaction log
circular collision, file number 176>
After numerous discussions with BEA Support, it appears to be a (rare)
race condition within the tlog file. It was also noted by BEA during
their testing of WebLogic 7.0.
Some additional research lead to an MBean attribute under *WebLogic
Server 7.0* entitled, "CheckpointIntervalSeconds". The documentation
states:
~~~~
Interval at which the transaction manager creates a new transaction
log file and checks all old transaction log files to see if they are
ready to be deleted. Default is 300 seconds (5 minutes); minimum is 10
seconds; maximum is 1800 seconds (30 minutes).
Default value = 300
Minimum = 10
Maximum = 1800
Configurable = Yes
Dynamic = Yes
MBean class = weblogic.management.configuration.JTAMBean
MBean attribute = CheckpointIntervalSeconds
~~~~
After searching for a equivalent setting under WebLogic Server
6.1.2.0, nothing was found and a custom (unsupported) patch was
created to change this hardcoded setting under 6.1:
from
... CHECKPOINT_THRESHOLD_MILLIS = 5 * 60 * 1000;
to
... CHECKPOINT_THRESHOLD_MILLIS = 10 * 60 * 1000;
within com.bea.weblogic.transaction.internal.ServerTransactionManagerImpl.
If you'd like additional details, feel free to contact me via e-mail
<[email protected]> or by phone +1.404.327.7238. Hope this
helps!
Brian J. Mitchell
BEA Systems Administrator
TRX
6 West Druid Hills Drive
Atlanta, GA 30329 USA
Hi 783703,
As Sridhar suggested for your problem you have to set transaction-time out in j2ee/home/config/transaction-manager.xml.
If you use Idempotent as false for your partnerlinks, BPEL PM will store the status till that invoke(Proof that this invoke gets executed).
So better to go for increasing the time instead of going for idempotent as it has some side effects.
And coming to dehydration ....Ideally performance will be more if there are no much dehydration poitns in our process. But for some scenarios it is better to have dehydration(ex: we can know the status of the process...etc)
Dehydration store will not get cleared after completion of the process. Here dehydration means ....it will store these dtails in tables(like Cube_instance,cube_scope...etc).
Regards
PavanKumar.M -
JTA transaction unexpectedly rolled back
I have a Spring Java web app deployed on OC4J 10.1.3.3 using Toplink as the container managed persistence. When my app is launched a named query is executed that uses JPQL to load up collections of objects. It is failing with the subject line exception.
org.springframework.transaction.UnexpectedRollbackException: JTA transaction unexpectedly rolled back (maybe due to a timeout); nested exception is javax.transaction.RollbackException: Timed out
If, however, I then modify the URL and force an action that will re-execute the same query, it works fine.
Any ideas on which configuration settings I should investigage/change to enable this to work the first time through?
I am not dealing with large collections here. At this point, there are 11 main objects that have children/parents. Re-execution of the query happens very fast.
Thank you!
GinniHello,
It sounds like its not the query itself that is taking too long, but all the processing done before the query in the same transaction scope. The error is that the transaction is timing out, so you should start by checking when the transaction is started and if the timeout value needs to be increased to cover the time this process is taking, or if the transaction can be made smaller or broken up into smaller peices. Or, if the query is just returning data that isn't going to be modified, if a transaction is required at all.
Best Regards,
Chris -
9.2 Web Services Participating in JTA Transactions?
If I set up a web service using JWS in Weblogic 9.2, and make this available to clients, is it possible to set up the web service so that it participates in a pre-existing JTA transaction (Transaction Required type setup)?
In other words, if the client is a Transaction Required EJB and it uses the new web service, do the two share the same transaction, such that if the client rolls back, anything that occurred in the web service is also rolled back?
If this is possible, I would appreciate any references to examples that do this.
Thanks,
ken clarkHello,
From your description it looks like the SAP ME web services are configured correctly on NW side.
The problem is most likely in SAPMEINT/MII configuration. Because the authentication properties for SAP ME web services are not configured in the transaction directly.
These properties are configured in MII Administration Menu -> Security Services -> Credential Editor. The name is SAPMEINT_ME_AUTH
Thanks
Ivan -
Hi,
I'm using TOPLINK in WebLogic 10.3.0 environment.
Toplink session.xml is configured to use external transaction menager (the JTA).
My Methods using Toplink work in a JTA transaction created by a JMS MDB:
In order to avout JTA Transactions to Time-out, is it possible to create a new local transaction (the same happening in EJB when RequireNew is the transaction attribute) suspending the main (JTA exernal) transaction?
How should I proceed?
Thank you very much.
L.DTopLink will hook into the currently active JTA transaction, and cannot control the transaction itself. You will need to look in WebLogic docs on how to suspend and resume JTA transactions:
http://docs.oracle.com/cd/E28280_01/web.1111/e13731/jtaapi.htm
I don't believe suspending a transaction will avoid a timeout issue though, so you might want reevaluate what is going on within your MDB and potentially break it into multiple transactions. -
SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana
I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
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:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
; nested exception is:
javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 moreHi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha. -
JTA transaction is aborting due to an user rollback fault
Hi,
While testing the ReceiptEBS on EM, we are getting given error, few minutes before EBS was working fine.
Error -
The selected operation CreateReceiptList could not be invoked.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Global retry rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a new
JTA transaction upon catching this fault.
This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine to roll
back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.
There is no action recommended.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Global retry rollback fault thrown.
The current JTA transaction is aborting due to an user rollback fault being thrown. The upstream component should retry in a
new JTA transaction upon catching this fault.
This exception was caused by a global retry fault being thrown from downstream component. The user had directed the BPEL engine
to roll back the current JTA transaction and retry within new JTA transactions for the specified number of times and retry interval.
There is no action recommended.Hi,
This seems to be a timeout error during JTA transaction. Some of my suggestions are
1. Put a timeout value in the partner link properties.
2. Set the timeout parameter for JTA under Domain configuration in console.
Regards,
Rahul -
Can I just confirm that if a method in an EJB has a JTA transactional context specified
by container-managed transaction demarcation, then the transaction context will be
propagated to any method that it calls in any other Java class. I just wanted to
be sure because we have all our SQL handling in separate Data Access classes whose
methods are called from the EJBs.
Thanks
Yes. Make sure that you are using a Transactional DataSource or the WebLogic JTS Driver to
access the connection pool...
Dave wrote:
> Can I just confirm that if a method in an EJB has a JTA transactional context specified
> by container-managed transaction demarcation, then the transaction context will be
> propagated to any method that it calls in any other Java class. I just wanted to
> be sure because we have all our SQL handling in separate Data Access classes whose
> methods are called from the EJBs.
> Thanks
-
This resource participates in a JTA transaction
Hi ,everybody,please help me solve the following question:
com.sap.engine.services.dbpool.exceptions.BaseSQLException: Cannot commit JDBC transaction from this connection of "mysqlds" DataSource. This resource participates in a JTA transaction.
Thank you!Hi,Isaias Cristian Barroso.Thank you for your answer,These are my codes in the EJB in the follow.Please help me,Thank you!
public class DBConnection {
private static final String DATABASE_JNDI_PROVIDER = "com.sap.engine.services.jndi.InitialContextFactoryImpl";
public static Connection getConnection() throws Exception {
try {
Connection conn = null;
java.util.Properties properties = null;
properties = new java.util.Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY,
DATABASE_JNDI_PROVIDER);
InitialContext jndiCntx = new InitialContext(properties);
DataSource ds = (DataSource) jndiCntx.lookup("jdbc/mysqlAS");
conn = ds.getConnection();
return conn;
} catch (Exception e) {
e.printStackTrace();
Session Bean implementation class PersonManager
@WebService(endpointInterface="com.thitech.personmanager.PersonManagerRemote", portName="PersonManagerPort", serviceName="PersonManagerService",
targetNamespace="http://thitech.com/personmanager/")
@Stateless
public class PersonManager implements PersonManagerRemote, PersonManagerLocal {
Default constructor.
public PersonManager() {
// TODO Auto-generated constructor stub
@Override
public String insertPerson(int personId, String name, String ***, int age,
String email, String address) {
PersonInfo pi = new PersonInfo();
ArrayList list = new ArrayList();
PreparedStatement pstm = null;
Connection conn =null;
String returnType=null;
try {
conn = DBConnection.getConnection();
conn.setAutoCommit(false);
String sql = "insert into personinfo values(?,?,?,?,?,?)";
pstm=conn.prepareStatement(sql);
pstm.setInt(1, personId);
pstm.setString(2, name);
pstm.setString(3, ***);
pstm.setInt(4, age);
pstm.setString(5, email);
pstm.setString(6, address);
pstm.executeUpdate();
conn.commit();
returnType="success";
} catch (Exception e) {
e.printStackTrace();
} finally {
if (pstm != null) {
try {
pstm.close();
} catch (SQLException e) {
e.printStackTrace();
DBConnection.closeConnection(conn);
return returnType;
Best regards
Maybe you are looking for
-
Unable to capture condition type in delivery document
There are deliveries in production server, for the same destination zone, in which, for some deliveries, the condition Z52L is not determined and for some other deliveries, the condition Z52L is determined although the condition record for its plant
-
Photoshop CC / Nikon Coolscan V ED compatibility in Windows 7 64 bit.
I managed to install a Nikon Coolscan V ED slide scanner in Windows 7 64 bit by first installing Vuescan, then Nikon Scan, but disallowing the installation of Nikon Scan drivers. Photoshop 7 sees the scanner in the file/import menu and previews, scan
-
The events I create on my Iphone 4 are not syncing with iCal.
Everything was fine until I updated the software on the phone to the iOS 5 and now I notice that events which I originated on my phone will not sync with my computer's iCal. I believe that things which are on my ICal will sync with my phone but not
-
Symantec AntiVirus LiveUpdate hangs my mac mini intel
Hello. I have an intel mac mini running mac osx 10.4.6 I installed norton antivirus corporate edition (site-licensed at my university) and all worked well. That is, it did until I installed the firmware update on the mini. Since then, when I try to r
-
Does anyone know how to turn off alerts for incoming emails and only have alerts for incoming phone messages?