Suspending transactions

          Hi. I'm running WL 6.1 sp1, connecting to an oracle db. There are several places
          in my application where information, including exception error messages, is being
          logged to the db. The problem is that when an exception occurs, the transaction
          is being rolled back and the database logging is being lost. The solution I found
          was to use the TransactionManager to suspend the transaction before the logging
          occurs and then resume it afterwards.
          I couldn't find anything in this newsgroup about suspending transactions, so I
          thought I'd write to ask if anyone else has tried this, and if it worked well
          for them. Any suggestions of other ways to get around my problem would also be
          greatly appreciated.
          Thanks in advance.
          -Brad

There is a logging API in weblogic and also in the upcoming JDK 1.4 release.
          As Deyan suggests you can also use a non-transactional and/or alternate data
          source for logging exceptions. Alternatively you could extract the data from
          the log files and store it as a separate process.
          "Brad Geddes" <[email protected]> wrote in message
          news:3c6d72de$[email protected]..
          >
          > Hi. I'm running WL 6.1 sp1, connecting to an oracle db. There are several
          places
          > in my application where information, including exception error messages,
          is being
          > logged to the db. The problem is that when an exception occurs, the
          transaction
          > is being rolled back and the database logging is being lost. The solution
          I found
          > was to use the TransactionManager to suspend the transaction before the
          logging
          > occurs and then resume it afterwards.
          >
          > I couldn't find anything in this newsgroup about suspending transactions,
          so I
          > thought I'd write to ask if anyone else has tried this, and if it worked
          well
          > for them. Any suggestions of other ways to get around my problem would
          also be
          > greatly appreciated.
          >
          > Thanks in advance.
          >
          > -Brad

Similar Messages

How to view pending transactions?

I have a problem where for some reason, things that should be rolled back when ocirollback is called, aren't. I'd like the user to be able to see a list of pending transactions, on that connection, but I haven't had any luck. All I find are posts about tables that I don't have.
I wish I could tell you what version of Oracle I have, but I don't even know. rpm -qa | grep -i oracle turns up empty. I can tell you that lsb_release -a gives
LSB Version: :core-3.0-ia32:core-3.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch
Distributor ID: RedHatEnterpriseAS
Description: Red Hat Enterprise Linux AS release 4 (Nahant Update 8)
Release: 4
Codename: NahantUpdate8

Make sure that every ociexecute call uses OCI_DEFAULT, else the active transaction in the connection will be committed.
Make sure that your application isn't doing DDL, e.g. CREATE TABLE, since this will commit the active transaction.
Pending transactions are shown in v$transaction, which may (or should) not be visible to normal users.
By "list of pending transactions, on that connection" do you means list of SAVEPOINTS, or are you suspending transactions via
a transaction manager or even by DBMS_XA?
Use <?php phpinfo(); ?> and check you have a recent version of the PHP OCI8 extension. 1.3 onwards is OK, 1.4 onwards is good.
You can get the latest source from http://pecl.php.net/package/oci8

How to move pending transactions to next period

Hi
i need to close the period but it show's there are 9 pending transactions, how can i sweep them to next period.
is there any concurrent program to do the process.
regards
Arif

Make sure that every ociexecute call uses OCI_DEFAULT, else the active transaction in the connection will be committed.
Make sure that your application isn't doing DDL, e.g. CREATE TABLE, since this will commit the active transaction.
Pending transactions are shown in v$transaction, which may (or should) not be visible to normal users.
By "list of pending transactions, on that connection" do you means list of SAVEPOINTS, or are you suspending transactions via
a transaction manager or even by DBMS_XA?
Use <?php phpinfo(); ?> and check you have a recent version of the PHP OCI8 extension. 1.3 onwards is OK, 1.4 onwards is good.
You can get the latest source from http://pecl.php.net/package/oci8

J2EE / JMS Controlling transaction in util.jar

Hi all experts!
I've a delicate problem where I want to handle transactions transparently for EJBs in my util jar. I�m familiar with the other alternatives (MDBs etc) and using them in other parts of the solution but they can�t be used here (need a synchronous request-reply).
The description is a bit long but please bare with me, hopefully it is clear and understandable.
Summary:
Why can't I use a UserTransaction in a utility.jar when called from a EJB using container managed transaction.
Senario:
transport_util.jar:
Transport utility package contains no EJBs, just simple java classes (to make usage / deployment more simple for the users of the util.jar).
The EJBs use an ApplicationFacade in the transport_util.jar (not a EJB just a java class) providing a high level communication API for JMS transport, encapsuling JMS specific code, and providing the simple transport primitives:
- void send(Object data) : writing fire and forget messages to JMS Queue
- Object requestReply(Object data) : sending a request message and waiting
synchronously for a reply message. Not pretty when using messaging but
necessary in this solution.
AnyEJB.jar:
The �client� using the transport primitives in transport_util.jar. The transport_util.jar is included in the EAR application as a utility.jar. The EJBs can use either Container (CMT) or Bean Managed Transactions (BMT). The transport_util.jar shouldn�t set any limitations.
Problem:
The problem arise when a �client� EJB under CMT calls the requestReply function in the API. The message is written to the JMS Queue by the transport_util before it starts to listen for a reply, on a in Queue, which will be returned to the caller. The request message is nerver delivered to the recipient who there for won�t produce a reply.
Why? Because it is written to the JMS Queue inside a transaction (implicit from the calling EJB) which has not been committed (and shouldn�t from the clients perspective) before the API starts to listen for the reply. No delivery until commit! The transactional parameter isn�t valid when inside a application server
My idea of a solution:
Start a new UserTransaction, putTx, inside the requestReply function to halt the callers transaction (J2EE doesn�t support nested trans) and use it around the put operation. After a successful put the putTx could be committed, without affecting the callers transaction, which would lead to the message being sent to the recipient and finally a reply could arrive. Only one big problem.:
I get a naming exception when trying to lookup the UserTransaction through JNDI if the calling EJB use CMT but not if it uses BMT. Why? Is there a workaround?
InitialContext ctxt = new InitialContext();
UserTransaction putTx = ctxt.lookup(�java:comp/UserTransaction�)
putTx.begin();
// Put message on queue
putTx.commit();
// Try read reply from queue
Infrastructure:
- IBM WebSpehere Application Server 5
- IBM WebSpehere MQ 5.3
- Java 1.3
Exception excerpt:
Error occurred while handling transaction
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O javax.naming.NameNotFoundException: Name "comp/UserTransaction" not found in context "java:".
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O      at com.ibm.ws.naming.ipbase.NameSpace.lookup(NameSpace.java:1003)
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O      at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1211)
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O      at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1203)
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O      at com.ibm.ws.naming.urlbase.UrlContext.lookup(UrlContext.java:1257)
[2003-09-04 17:06:47:479 CEST] 7f8389dc SystemOut O      at javax.naming.InitialContext.lookup(InitialContext.java:359)
/Best regards
Jesper

If anyone else have the same problem....
After a great tip from a colleague a good solution if found!
By getting hold of the TransactionManger from the ApplicationServer it is possible to suspend an ongoing transaction, start a new one and commit it and restart the suspended transaction again.
Looking up the TransactionManger differs a lot from AppServer to AppServer. To find out how it is done on yours take a peak in the code of any of bigger persistence frameworks (I looked at Hibernate).
So in pseudo code:
// Error checks not in code to keep it short
// Look up the TransactionManager
TransactionManager mgrTx = //
// Suspend callers Tx
Transaction callerTx = mgrTx.suspend();
// Start new transaction for the work to be performed
// outside the callers transaction
mgrTx.begin();
// Perform transacted work .....
// Commit
mgrTx.commit();
// Reassign the callers transaction to the thread and activate if
mgrTx.resume(callerTx);/J

SYSTEM SUSPEND COMMAND

제품 : ORACLE SERVER
작성날짜 : 2003-08-04
ALTER SYSTEM SUSPEND 명령은 모든 instance에서 query 뿐 아니라 모든 I/O(datafile,
control file, and file header)를 suspend시킴으로서 현재의 transaction에 상관없이
데이타베이스의 복사가 가능하다. 다른 instance를 suspend하고 있는 동안 새로운
instance를 start하지 않도록 한다. 이것은 새로운 instance는 suspend되지 않기때문이다
정상적인 database 작업을 계속하고자 한다면 alter system resume명령을 주면 된다.
suspend/resume은 디스크나 화일을 mirror하여 split할수 있도록 하는데 유용할수 있다.
만약 writes가 발생하는 동안에 현재의 데이타베이스로부터 mirrored disk를 split할수
없는 시스템을 사용하고 있다면 suspend/resume을 사용하여 가능하도록 할수 있다.
suspended database의 복사는 commit되지 않은 내용을 가지고 있을수 있기때문에
suspend/resume은 일반적인 shutdown 작업의 간편한 대체수단이 아니다.
SUSPEND/RESUME 문장은 각기 다른 instance에서 수행할 수 있다. 예를 들면
만약 instance 1, 2, 3이 running 중이고 instance 1에서 SUSPEND 명령을 수행한 후
instance 1,2 또는 3 모두에서 resume 명령을 수행할 수 있다.
** SUSPEND와 RESUME 명령을 수행하는 단계
1. ALTER TABLESPACE BEGIN BACKUP명령을 이용하여 database tablespace를
hot backup mode에 놓는다.
2. 만약 DISK write가 발생하는 상황에서 mirror를 split하는데 문제가 있다면
ALTER SYSTEM SUSPEND명령을 수행한다.
3. MIRROR를 split한다.
4. database를 다시 진행하기 위하여 ALTER SYSTEM RESUME 명령을 사용한다.
5. ALTER TABLESPACE END BACKUP 명령을 수행함으로써 tablespace의 hot backup mode
에서 정상 모드로 변환한다.
6. 일반적인 백업에서와 같이 control file과 online redolog들을 백업 받는다.
Note: SUSPEND 명령을 tablespace를 hot backup mode로 전환하는 것의 대체용으로
사용하지 않는다.
Reference Documents
<Note:91059.1>

제품 : ORACLE SERVER
작성날짜 : 2003-08-04
ALTER SYSTEM SUSPEND 명령은 모든 instance에서 query 뿐 아니라 모든 I/O(datafile,
control file, and file header)를 suspend시킴으로서 현재의 transaction에 상관없이
데이타베이스의 복사가 가능하다. 다른 instance를 suspend하고 있는 동안 새로운
instance를 start하지 않도록 한다. 이것은 새로운 instance는 suspend되지 않기때문이다
정상적인 database 작업을 계속하고자 한다면 alter system resume명령을 주면 된다.
suspend/resume은 디스크나 화일을 mirror하여 split할수 있도록 하는데 유용할수 있다.
만약 writes가 발생하는 동안에 현재의 데이타베이스로부터 mirrored disk를 split할수
없는 시스템을 사용하고 있다면 suspend/resume을 사용하여 가능하도록 할수 있다.
suspended database의 복사는 commit되지 않은 내용을 가지고 있을수 있기때문에
suspend/resume은 일반적인 shutdown 작업의 간편한 대체수단이 아니다.
SUSPEND/RESUME 문장은 각기 다른 instance에서 수행할 수 있다. 예를 들면
만약 instance 1, 2, 3이 running 중이고 instance 1에서 SUSPEND 명령을 수행한 후
instance 1,2 또는 3 모두에서 resume 명령을 수행할 수 있다.
** SUSPEND와 RESUME 명령을 수행하는 단계
1. ALTER TABLESPACE BEGIN BACKUP명령을 이용하여 database tablespace를
hot backup mode에 놓는다.
2. 만약 DISK write가 발생하는 상황에서 mirror를 split하는데 문제가 있다면
ALTER SYSTEM SUSPEND명령을 수행한다.
3. MIRROR를 split한다.
4. database를 다시 진행하기 위하여 ALTER SYSTEM RESUME 명령을 사용한다.
5. ALTER TABLESPACE END BACKUP 명령을 수행함으로써 tablespace의 hot backup mode
에서 정상 모드로 변환한다.
6. 일반적인 백업에서와 같이 control file과 online redolog들을 백업 받는다.
Note: SUSPEND 명령을 tablespace를 hot backup mode로 전환하는 것의 대체용으로
사용하지 않는다.
Reference Documents
<Note:91059.1>

Excellent resources about EJB Transactions

Is there any good (better, excellent) web resource (or book) about EJB Transactions, covering topics like
- Flat Transactions vs. Nested Transaction
- Using EJB EntityBeans & Hibernate together: pay attention to Transaction Isolation
- Transaction Isolation examples, especially when having suspended transactions?
Thank you for any hint.
Michael

Nothing's better than Google.
Rich

Split 837 file at claims level biztalk 2010

I have deployed the 837p muti schema, no singlr schema. The receive location used edi recive pipe line. Send port xml receive pipeline. I didn't change anything on the schema used default one.
I have created the parties and agreement.
I want to debatch the incoming 837 at the claim lable. How ever when I drop the 837 file to input folder i get x12 interchange error
Error encountered during parsing. The X12 interchange with id '000045398', with sender id '521854809 ', receiver id '061057387 ' had the following errors:
Error: 1 (Miscellaneous error)
16: Invalid Control Standard Identifier
Error: 2 (Field level error)
SegmentID: ISA
Position in TS: 1
Data Element ID: ISA11
Position in Segment: 11
Data Value: ^
7: Invalid code value

Please make sure that, in the party configuration under the 'Inbound batch processing Option" -Split interchange as Transaction Sets-Suspend Transaction Sets on Error is selected.
Valid transactions will route as normal and invalid ones will be routed based on the failed message routing(for this Enable routing for failed messages at the Receive port).
To know more details about Spilitting a batched EDI interchange, have a look at the below MSDN link
http://msdn.microsoft.com/en-us/library/bb246013(v=bts.10).aspx
http://stackoverflow.com/questions/8827380/debatching-837-files-with-multiple-claim
Thanks
Abhishek

Is this TRUE or FALSE ?

Hi all,
Pls tell me whether this sentence is true or false.
A transaction used by a BMT bean MUST have been started by the bean.
In book this question is marked as false, but as far as I think it should be true.
Pls update.
Regards,
Sanjeev

As it's written I would say it's true as well.
Bean-managed transactions are only allowed for session beans(stateful and stateless) and message-driven beans. Furthermore, if there is any client transaction context propagated on the call to the BMT bean, the container is required to suspend the client tx before calling the business method. So, BMT beans cannot inherit client transactions.
For BMT stateless session beans and message-driven beans, there cannot be an active user transaction when the business method completes. If there is, the container is required to treat it as an error.
The slightly more interesting case is for stateful session beans. For BMT SFSBs, it's o.k. for the transaction to still be active when the business method returns. In that case, the container suspends the tx and assoicates it with the SFSB. Whenever the SFSB is invoked again, the previously associated transaction is resumed before the business method is called. ( The same rule holds for client transactions. If there is one, it will be suspended and resumed when the business method completes. ) However, even if the container resumes a previously suspended transaction before invoking the SFSB, it can only be a transaction that was started by that bean.
--ken

Call Enterprise Bean (or Database) from private Method in Session-Bean

Hi Everybody,
I've a question regarding the possibility to call an dependency injected EJB in an private method of a session bean.
Imagine the following.
@Stateless
public class SomeBean implements SomeLocal{
   @EJB
   private AnotherLocal anotherBean;
   /** Will be called from a web-app via delegate layer */
   @TransactionAttribute(TransactionAttribute.RequiresNew)
   public void someBusisnessMethod(){
       String something = this.getSomeThing();
       //Do more
   private String getSomeThing(){
      return anotherBean.aMethodWhichCallsTheEntityManager();
}I've to refactor code with uses such Call-Hierachy and I want to know whether this is a correct way? Somebody told me that such stuff should not be made, and I quess he told me an explanation, why not to do such stuff, but unfortunally I've forgotten that. Do someone have a suggestion why not to do this? Could it blow the application to hell? Is there any difference to the following code (The way I would have done it)?
@Stateless
public class SomeBean implements SomeLocal{
   @EJB
   private AnotherLocal anotherBean;
    @Resource
    private SessionContext sessionContext;
   /** Will be called from a web-app via delegate layer */
   @TransactionAttribute(TransactionAttribute.RequiresNew)
   public void someBusisnessMethod(){
       SomeLocal self = this.sessionContext.getBusinessObject(SomeLocal.class);
       String something = self.getSomeThingBusinessMethod();
       //Do more
   @TransactionAttribute(TransactionAttribute.Required)
   public String getSomeThingBusinessMethod(){
      return anotherBean.aMethodWhichCallsTheEntityManager();
}

Found the answer by myself....
Here it is if someone might have the same question:
http://stackoverflow.com/questions/3381002 or if the link may down sometime the content of the answer...
>
The motivation here is that most EJB implementations work on proxies. You wouldn't be too far off in thinking of it as old-school AOP. The business interface is implemented by the EJB container, quite often via a simple java.lang.reflect.Proxy, and this object is handed to everyone in the system who asks for the ejb via @EJB or JNDI lookup.
The proxy is hooked up to the container and all calls on it go directly to the container who will preform security checks, start/stop/suspend transactions, invoke interceptors, etc. etc. and then finally delegate the call to the bean instance -- and of course do any clean up required due to any exceptions thrown -- then finally hand the return value over through the proxy to the caller.
Calling this.foo() directly, or passing 'this' to a caller so they can make direct calls as well, will skip all of that and the container will be effectively cut out of the picture. The 'getBusinessObject(Class)' method allows the bean instance to essentially get a proxy to itself so it can invoke its own methods and make use of the container management services associated with it -- interceptors, transaction management, security enforcement, etc.
written by David Blevins

OSB and async BPEL Process

Hi all,
I have a problem configuring the osb to use an asynchronous bpel process.
Made the following steps:
1.) Created one Proxy Service for invoking the bpel process
2.) Created one Proxy Service for callback
3.) Created one Business Service which has the following config:
General Configuration
Service Type: Web Service [...]
Transport Configuration
Protocol: bpel-10g
Load Balancing Algorithm: none
Endpoint URI
opmn://STSCHROE-de:6003/home/orabpel/eudlr/Antrag_pruefen
Retry Count 0
Retry Iteration Interval 30
Retry Application Errors Yes
BPEL-10G Transport Configuration
Role      Asynchronous Client
Callback Proxy      EUDLR/ProxyService/AntragPruefenCallbackGateway
Service Account EUDLR/BusinessService/SOA Suite
Suspend Transaction? No
Dispatch policy      default
Products:
Oracle Service Bus 10gR3
Oracle SOA Suite 10.1.3.3.1
Problem:
I get the following Error, when I execute the proy service:
The invocation resulted in an error: java.lang.reflect.UndeclaredThrowableException.
The consolte window tells the following error
22.01.2009 13:10:14 oracle.j2ee.rmi.RMIMessages EXCEPTION_ORIGINATES_FROM_THE_REMOTE_SERVER
WARNUNG: Exception returned by remote server: {0}
com.evermind.server.rmi.RMIConnectionException: Disconnected: com.oracle.bpel.client.AbstractIdentifier; local class incompatible: stream classdesc serialVersionUID = -4389351842028223514, local class serialVersionUID = 3174123903773674079
at com.evermind.server.rmi.RmiCallQueue.notifyQueuedThreads(RmiCallQueue
.java:70)
at com.evermind.server.rmi.RMIClientConnection.notifyQueuedThreads(RMICl
ientConnection.java:208)
at com.evermind.server.rmi.RMIClientConnection.resetState(RMIClientConne
ction.java:147)
at com.evermind.server.rmi.RMIConnection.receiveDisconnect(RMIConnection
.java:236)
at com.evermind.server.rmi.RMIClientConnection.receiveDisconnect(RMIClie
ntConnection.java:176)
at com.evermind.server.rmi.RMIConnection.handleOrmiCommand(RMIConnection
.java:208)
at com.evermind.server.rmi.RMIClientConnection.processReceivedCommand(RM
IClientConnection.java:276)
at com.evermind.server.rmi.RMIConnection.handleCommand(RMIConnection.jav
a:152)
at com.evermind.server.rmi.RMIConnection.listenForOrmiCommands(RMIConnec
tion.java:127)
at com.evermind.server.rmi.RMIConnection.run(RMIConnection.java:107)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:830)
at java.lang.Thread.run(Thread.java:619)
Is there a solution for this problem?

You need to follow below steps...
add a java parameter to the OSB server. Go to domains\osb_domain\bin folder and edit the setDomainEnv file and add this line to this file. set JAVA_PROPERTIES=-Dplatform.home=%WL_HOME% -Dwls.home=%WLS_HOME% -Dweblogic.home=%WLS_HOME% -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
Step 2 is to replace the bpel jars in the bpel transport ear. Go folder osb_10.3\lib\transports and open bpel10gtransport.ear and replace the following jar files orabpel.jar, orabpel-common.jar , xmlparserv2.jar and oc4jclient.jar with the ones you can find in the soa suite 10.1.3 home.

Information on the Weblogic JMS behaviour

          Hi,
          The WL(5.1,SP6) JMS specification says
          "A Session created with CLIENT_ACKNOWLEDGE relies on the client to call an acknowledge
          method on a received message. Once this method is called, the Session acknowledges
          all messages received since the last acknowledgement. This allows the client to receive
          and process a batch of messages and then acknowledge them all with one call."
          This means that if there are messages m1,m2,m3 in the queue, I can receive all the
          messages and by acknowledging the third message, i acknowledge the other two.
          My requirement is that I should not lose any messages. So is there any way i can
          preserve the other two in the Queue.
          Thanks
          Kiran


Hi Kiran,
          See in-line.
          Kiran Pratap wrote:
          > Hi,
          >
          > The WL(5.1,SP6) JMS specification says
          > "A Session created with CLIENT_ACKNOWLEDGE relies on the client to call an acknowledge
          > method on a received message. Once this method is called, the Session acknowledges
          > all messages received since the last acknowledgement. This allows the client to receive
          > and process a batch of messages and then acknowledge them all with one call."
          >
          > This means that if there are messages m1,m2,m3 in the queue, I can receive all the
          > messages and by acknowledging the third message, i acknowledge the other two.
          >
          > My requirement is that I should not lose any messages. So is there any way i can
          > preserve the other two in the Queue.
          >
          You are not losing messages - your app has seen them. But anyway, there is no
          simple way to do this. For a couple of ideas, check out
          http://e-docs.beasys.com/wls/docs61/faq/jms.html#252701
          (I'm not sure if WL 5.1 supports suspending transactions, so the transactional approach
          may not work...)
          FYI: Just to make the issue anti-intuitive ;-), the JMS spec requires that all messages
          the session
          has received, not just the messages before the given message, be acknowledged when a
          message is acknowledged. This was determined in a clarification with javasoft.
          WebLogic 5.1 does not do this but continues to do "ack-prev". WebLogic 6.x+ does
          "ack-all",
          but is tunable on the connection factory (acknowledge-all vs. acknowledge-prev option),
          the WL 6.x legacy default connection factories (from 5.1) also do "ack-prev".
          Tom
          >
          > Thanks
          > Kiran

Trasaction problem when migrate ejb application from oc4j 10.1.2 to 10.1.3

When i migrate my ejb application from oc4j 10.1.2 to 10.1.3
in application log i found following many exceptions:
where is problem? on AS 10.1.2 all works fine.
javax.transaction.SystemException: Transaction state is COMMITTED and therefore can not be suspended, transaction
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransaction.suspend(ApplicationServerTransaction.java:356)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionManager.suspend(ApplicationServerTransactionManager.java:541)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EJBTransactionManager.suspend(EJBTransactionManager.java:186)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EJBTransactionManager.suspendLocal(EJBTransactionManager.java:163)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.BeanPool.suspend(BeanPool.java:588)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.BeanPool.destroyContext(BeanPool.java:460)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.BeanPool.releaseContext(BeanPool.java:306)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.BMPOrionEntityBeanPool.releaseContext(BMPOrionEntityBeanPool.java:72)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EntityEJBHome.releaseContextInstance(EntityEJBHome.java:114)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EntityEJBHome.passivateAndRelease(EntityEJBHome.java:182)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EntityEJBObject.releaseContext(EntityEJBObject.java:402)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EntityEJBObject.removeFromCacheNew(EntityEJBObject.java:336)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EntityEJBObject.endTransaction(EntityEJBObject.java:178)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionSynchronization.endTransaction(ApplicationServerTransactionSynchronization.java:198)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionSynchronization.freeEjbResources(ApplicationServerTransactionSynchronization.java:179)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionSynchronization.afterCompletion(ApplicationServerTransactionSynchronization.java:677)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransaction.callSynchronizationAfterCompletion(ApplicationServerTransaction.java:1215)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionManager.freeResources(ApplicationServerTransactionManager.java:394)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransaction.doCommit(ApplicationServerTransaction.java:282)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransaction.commit(ApplicationServerTransaction.java:162)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ApplicationServerTransactionManager.commit(ApplicationServerTransactionManager.java:472)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:143)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:57)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermindhttp://Oracle Containers for J2EE 10g (10.1.3.4.0) .server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
any idea?
Thanks. J.

java.lang.NoSuchMethodError: java.lang.String oracle.adf.model.BindingContext.findBindingContainerIdByPath(java.lang.String) at oracle.adf.controller.v2.struts.actions.DataAction.mappingCreate
Refer Steve's blog
http://radio-weblogs.com/0118231/stories/2006/02/28/notesOnMigratingAdfstruts1012ApplicationsTo1013.html

Strange NPE in the TransactionManager.forceResume()

Has anyone seen this exception?
          java.lang.NullPointerException
          at
          weblogic.transaction.internal.TransactionManagerImpl.getThreadProp(TransactionManagerImpl.java:1670)
          at
          weblogic.transaction.internal.TransactionManagerImpl.associateTxWithThread(TransactionManagerImpl.java:1640)
          at
          weblogic.transaction.internal.TransactionManagerImpl.internalResume(TransactionManagerImpl.java:1465)
          at
          weblogic.transaction.internal.TransactionManagerImpl.forceResume(TransactionManagerImpl.java:469)
          We get a reference on the Weblogic Transaction Manager in the server,
          call forceSuspend(), then do some DB work and when we try to resume the
          suspended transaction we get the NPE.
          This is in WLS 7.0 SP4 on Windows
          Thanks,
          Dejan


Your renderer is as I suspected the culprit.... I have made some quick changes (without testing):
class myCellRenderer extends DefaultTableCellRenderer {
   public Component getTableCellRendererComponent(JTable table, Object value, boolean isSelected, boolean hasFocus, int row, int column) {
      if (value == null ) setText("");
      setIcon( null );
      setBackground( Color.white );
      if (column != 0 ) {
         if (value instanceof Integer ) {
            int sevInt = ((Integer) value).intValue() ;
            setHorizontalAlignment( JCENTER );
            if (sevInt == 4 ) {
               setIcon( servDownImage );
               setText( "" );
            } else if (sevInt == 5 ) {
               setIcon( servUpImage );
               setText( "" );
      if ((row % 2) == 0) {
         setBackground(Color.white);
      } else {
         setBackground(new Color(229, 229, 229));
      if (isSelected) {
         setBackground(new Color(180, 180, 180));
      return this;
}Try it and see ....
;o)
V.V.

EJB3 : suspend JTA transaction does not release the connection in the XA DS

Hi all,
I did a test and after suspending a JTA transaction I note that in the xa datasource the activeconnection = 1.
So is it normal because I was thinking that when I suspend the transaction the teh connection is released and then after a transaction resume I could continue the transaction with another connection of the xa datasource ?
Thank you for all..
Christophe.

It's a long time ago, but did you ever solve this problem?
I'm having the same issue with OSB writing to a WLS8.1 JMS queue.
I have a development OSB server which works fine.
Pete

ORA-01002 fetch out of sequence after suspend/resume transaction

Environment
- WebLogic 10.0.2.0
- Oracle thin driver 10.2.0.2.0
I iterate throw elements of ResultSet. During that global transaction is suspended and resumed. Then invoking of next on ResultSet caused following exception “java.sql.SQLException: ORA-01002: fetch out of sequence”.
I found that similar problem was reported in older WLS version ORA-01002 fetch out of sequence
Do you have any idea how I can fix it?
Best regards,
Adam

OK, to get to the complete explanation, I suggest you open
an official support case. And I'm not trying to avoid the issue,
but fetching millions of rows out of the database to process
them outside is the wrong way to go. I highly recommend
DBMS-side logic in stored procedures to do the raw data processing.

Suspending transactions

Similar Messages

Maybe you are looking for