How to disable distributed transaction in Weblogic 8.1?

          Hi I'm using WL8.1 running EJB. I wish to disable distributed transaction, whatever
          that is. It is preventing me from doing and AutoCommit(true) in my database. Please
          help. Thanks!

You cannot disable transactions if you are using entity EJBs but you can
          get your connections from a non-TX DataSource (just define a regular
          DataSource and not TXDataSource in your configuration) and then those
          connections will not be transaction aware so you'll be able to do
          setAutoCommit(true) in fact it might already be the default setting when
          you get the connection.
          Regards,
          Dejan
          Fred wrote:
          >Hi I'm using WL8.1 running EJB. I wish to disable distributed transaction, whatever
          >that is. It is preventing me from doing and AutoCommit(true) in my database. Please
          >help. Thanks!
          >
          >

Similar Messages

How to implement Distributed Transaction

Hi,
We are using Jsp/Struts/Bc4j application model. JHeadstart 9.0.5.1.
We have the Distributed transaction issue. There are 2 BC4J Application Modules (AM1 and AM2), each with its own DB connection, Entity and View Objects. In a special case, when record is inserted via AM1, there have to be record created in the DB, via AM2.
What is the recommended approach to do that? We can't define AM2 as submodule of AM1, because, when instantiated (in the corresponding doDML method on the entity in AM1), it will try to use the connection of AM1, which is wrong. When (which event), and how to instantiate AM2 (ensure write connection), get corresponding View Object, create the other record, and commit everything in one transaction? Btw, we can not use DB link.
Regards,
Vladimir

Hi Vladimir,
It seems to me that this is a generic BC4J issue, independent of JHeadstart. You could post it at the JDeveloper forum at http://otn.oracle.com/discussionforums/jdev.html.
My suggestion (though I'm not sure it would work) would be to explicitly instantiate AM2 at the time you need it within AM1, with code like this:
String amDef = "test.AM2";
String config = "AM2Local";
ApplicationModule am =
Configuration.createRootApplicationModule(amDef,config);
ViewObject vo = am.findViewObject("TestView");
// Work with your appmodule and view object here
Configuration.releaseRootApplicationModule(am,true);By the way, in JDeveloper 10g you can get this piece of code by typing bc4jclient followed directly by Ctrl+Enter.
Hope this helps,
Sandra Muller
JHeadstart Team
Oracle Consulting

How to Increase distributed Transaction parameter value in oracle 10g r2

Hello,
Can you please let me know how to increase the value of Distributed Transaction Parameter in oralce 10g R2
Thanks
Usman

Why do you want to increase this?
If you are getting ORA-02042, you have to reduce the number of concurrent distributed transactions you are running or restart your database to clear existing ones.

How to configure distributed transaction in Oracle Database Gateway for ODBC? (ORA-02047)

I am connecting from Oracle to another database server (MS SQL Server, DB2 the error message is the same) through an ODBC connection using Oracle SQL Developer. (This is how I set up)
I want to query the schema of a non-Oracle database using the data dictionary mapping of the Oracle Database Gateway for ODBC.
This works well:
select * from all_tables@katimssql;
But this doesn't:
create table alltables_mssql as
select * from all_tables@katimssql;
Output:
Error report:
SQL Error: ORA-00604: error occurred at recursive SQL level 1
ORA-02047: cannot join the distributed transaction in progress
ORA-06512: at "SYS.HS$_DDTF_SQLTABLES", line 58
ORA-06512: at line 1
Does anyone know the solution of this?
Thanks in advance,
Kata
Details:
Oracle Database 11g Express Edition Release 11.2.0.2.0
Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (X64)
ODBC Driver: SQL Server Native Client 11.0 (32 bit)
initkatimssql.ora:
HS_FDS_CONNECT_INFO=katimssql
HS_FDS_TRACE_LEVEL = ON
HS_TRANSACTION_MODEL = READ_ONLY_AUTOCOMMIT
I tried these, none of them worked, the error message is the same.
HS_FDS_TRACE_LEVEL = off
HS_TRANSACTION_MODEL = SINGLE_SITE
HS_TRANSACTION_MODEL = READ_ONLY_AUTOCOMMIT
HS_TRANSACTION_MODEL = READ_ONLY

Hi Kata,
this won't work as the ALL_TABLES is not a table that exists in your SQl Server - instead it is a "mimicked" table. This means the gateway will check if you have on your SQL Server a table called all_tables and when there's no table it will start an internal mechanism to check out what sort of tables exist in your SQL Server database. So the gateway is starting internally another transaction to get details from the foreign database and DG4ODBC can't participate in distributed transactions at all. Instead of using all_tables you have to use a real SQL Server table like SQ Server sys.objects or sys.tables.
- Klaus

Distributed Transaction in weblogic 5.1

Hi all,
Does Weblogic 5.1 support Distributed Transactions?.

While they aren't java-specific, if you're looking for XA/2PC details,
these 2 are good:
Transaction Processing: Concepts and Techniques (Morgan Kaufmann Series
in Data Management Systems)
by Jim Gray, Andreas Reuter
Principles of Transaction Processing
by Philip A. Bernstein, Eric Newcomer (Contributor)
5.1 does not support XA or 2 phase-commit. However, it does allow
multiple cluster members to enlist in the same transaction as long as
all database access goes through the same JDBC connection.
WLS 6.0 and later do support XA and 2PC.
-- Rob
chandrasekar wrote:
Hi all,
Does Weblogic 5.1 support Distributed Transactions?.Please suggest me some
books or documentation regarding Distributed Transactions, and about the XA compliant
resources.

How to disable SSL renegotiation in weblogic 10.3

Hi,
Can someone advise how to disable the SSL renegotiation in weblogic 10.3 server with jdk 1.6.0_35-b10 or 1.6.0_07-b06?
I tried to set up below properties when starting up weblogic server. But didn't work.
-Dweblogic.security.disableNullCipher=true -Dweblogic.ssl.AllowUnencryptedNullCipher=false -Dweblogic.security.ssl.enable.renegotiation=false -Dssl.debug=true -Dsun.security.ssl.allowUnsafeRenegotiation=false -Dsun.security.ssl.allowLegacyHelloMessages=false
Really appreciate if anyone can give any advise.

Thanks PratikS.
I tried to apply such patch in weblogic10.3.0. But got below NoSuchMethodError. Any idea? Any other patch needed?
<Jun 3, 2013 1:25:49 PM CST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoSuchMethodError:weblogic.protocol.ServerChannel.getConfig()Lweblogic/management/configuration/NetworkAccessPointMBean;
java.lang.NoSuchMethodError: weblogic.protocol.ServerChannel.getConfig()Lweblogic/management/configuration/NetworkAccessPointMBean;
at weblogic.security.utils.SSLContextManager.getChannelSSLContext(SSLCon
textManager.java:234)
at weblogic.security.utils.SSLContextManager.getSSLServerSocketFactory(S
SLContextManager.java:89)
at weblogic.server.channels.DynamicSSLListenThread.<init>(DynamicSSLList
enThread.java:59)
at weblogic.server.channels.DynamicListenThreadManager.createListener(Dy
namicListenThreadManager.java:289)
at weblogic.server.channels.DynamicListenThreadManager.start(DynamicList
enThreadManager.java:129)
Truncated. see log file for complete stacktrace
>

How to design Distributed transaction?

Hi
I have distributed transaction that involve MQ and two oracle database. In both database I have stroed procedure that have their own rollback points. My requirement is that either both database shoulb committed or none.
For this to implement I have a MDB that calls SP on first database and without commiting any thing it comes back to MDB and again Calls SP on second database and again come back to MDB and call1 SP on database1..
But problem is when I am calling 2nd database SP and if any thing goes wrong inside SP then its implicit rollback is not working. To overcome this I put this 2nd database logic in another EJB with RequiresNew. But then problem is that if MDB transaction is rolled back then 2nd database transaction is not getting roollbacked.
Please suggest any solution to overcome this.
Server is Websphere 6.0
Database is: Oracle 10g
Datasource: XA
Q: MQ 6.0
Thanks

I think you can use Java Trasaction API that is independent of the Resources and will give you more flexibility to handle trasactions
This link may be helpful
http://www.onjava.com/pub/a/onjava/2001/05/23/j2ee.html

How to implement Distributed Transactions in ADF?

Scenario:
when selected rows and submitted action from UI, following happens
1) For the selected rows, information will get fetched from database and a message will get formed and will get posted in JMS queue
2) once step1 is successful, corresponding record will get logically deleted
Implementation details:
Environment: Oracle ADF , Weblogic server
Step1: Created UI with Multi selection
Step2: getting selected row key information and calling a custom AM method (exposed as client interface) from managed bean passing selected row key info
step3: implementing following logic in AM method
while(keyList.hasNext()
1) getting View object for the given key and populating message
2) Posting the mesage in JMS queue configured in weblogic using JMS Helper classes written
3) updating the delete flag in VO
Problem statement:
In Step3 after sub step 2 executed, suppose if database is down substep3 will not get executed
because of which a record will get displayed again back in UI and when selected again a duplicated message will be sent to the concerned external system
I'm very new to ADF. Can anyone please help me on how to achieve this using ADF?
Much Appreciated,
Indu

Thanks Vinod for your reply
at substep 2 getting record from database and populating message and posting it to jms queue
at substep 3 if post is successful the updating database indiacting this message has been sent by updating delete flag
if i update database first and then if send message, In case of JMS exception(Can be Queue failures) my record will get updated and i cannot see record back in UI
So both these opertions has to be happened in in single Transaction.Either both has to be happened or both has to be rolled back
database and JMS are different resources. How ADF handles these XA transactions?
Thanks,
indu

ADF- Jdev11.1.1.6 Business Components supports distributed transaction ?

Hi ,
I'm using Jdeveloper 11.1.1.6 release 1 . How to implement distributed transaction in ADF business component level.
In my scenario i need to perform A Single transaction with two different database . I do need to role back both if either one fails (Distributed Transactions) . How could i achieve this in ADF business component. Does ADF has any built-in support for Distributed transactions.
Could anybody advice me .
Thanks in Advanced .

Thanks for your response !!! What is the best alternative i can choose to achieve Distributed Transaction in ADF Application , if there is no inbuilt support for it in BC?
Edited by: 994058 on Mar 15, 2013 7:16 AM
Edited by: 994058 on Mar 15, 2013 7:18 AM

Distributed transaction error in WL 7.1

Hi,
I'm trying to set-up distributed transactions for weblogic. We have a requirement
to go against 2 different databases within a single transaction.
My config.xml looks like:
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="1" MaxCapacity="2" Name="PAWSPool"
Properties="user=STARTESTDATA;url=jdbc:oracle:thin:@s0489dev.dev.schwab.com:1521:ACSTAR;password=STARTESTDATA;dll=ocijdbc9;protocol=thin"
RefreshMinutes="5" ShrinkingEnabled="true"
SupportsLocalTransaction="true" Targets="sps_space"
TestConnectionsOnReserve="true" TestTableName="DUAL"
URL="jdbc:oracle:thin:@s0489dev.dev.schwab.com:1521:ACSTAR"/>
<JDBCTxDataSource JNDIName="jdbc/paws"
Name="PAWSDataSource" PoolName="PAWSPool" Targets="sps_space"/>
and the pseduo code that produces the problem looks like this:
UserTransction.begin(); //assume valid lookup in jndi occurred already
Connection con = dataSource.getConnection(); //datsource obtained from jndi lookup
PreparedStatement ps = con.prepareStatement("sql string");
the error
HELP!!!!!

what is the error ? if you could cut and paste the log / stdout that shows
the error that could be useful.
Also did youmean to say you are using WLS7.0SP1?
sree
"John Byrnes" <[email protected]> wrote in message
news:3f1af184$[email protected]..
>
Hi,
I'm trying to set-up distributed transactions for weblogic. We have arequirement
to go against 2 different databases within a single transaction.
My config.xml looks like:
<JDBCConnectionPool CapacityIncrement="1"
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
InitialCapacity="1" MaxCapacity="2" Name="PAWSPool"
Properties="user=STARTESTDATA;url=jdbc:oracle:thin:@s0489dev.dev.schwab.com:
1521:ACSTAR;password=STARTESTDATA;dll=ocijdbc9;protocol=thin"
RefreshMinutes="5" ShrinkingEnabled="true"
SupportsLocalTransaction="true" Targets="sps_space"
TestConnectionsOnReserve="true" TestTableName="DUAL"
URL="jdbc:oracle:thin:@s0489dev.dev.schwab.com:1521:ACSTAR"/>
<JDBCTxDataSource JNDIName="jdbc/paws"
Name="PAWSDataSource" PoolName="PAWSPool" Targets="sps_space"/>
and the pseduo code that produces the problem looks like this:
UserTransction.begin(); //assume valid lookup in jndi occurred already
Connection con = dataSource.getConnection(); //datsource obtained fromjndi lookup
PreparedStatement ps = con.prepareStatement("sql string");
the error
HELP!!!!!

Lock held by in-doubt distributed transaction

          I'm having an intermittent problem in our server where a distributed transaction
          between WebLogic JMS (6.1 sp3) and Oracle (using the 9.1.2 XA driver) doesn't
          complete and subsequent attempts to access the rows in question result in:
          java.sql.SQLException: ORA-01591: lock held by in-doubt distributed transaction
          4.33.52658
          Has anybody else seen anything like this?


          Rao,
          The BEA patch is CR095835_610SP4. Apparently there is a corresponding patch for
          SP3 as well. When configuring the jdbc connection pool set XaSetTransactionTimeout
          = true and
          XaTransactionTimeout = yourTimeoutValueInSeconds. This will instruct the Transaction
          manager to set the timeout value on Oracle's XAResource during the two-phase commit
          process. I believe Oracle refers to the timeout value as SesTm.
          Cheers,
          Tony
          "Rao Boppana" <[email protected]> wrote:
          >
          >We are currently facing the same problem. Could you let us know more
          >details about
          >the patch BEA put out to fix this? Is there a patch #/bug #? We are currently
          >running SP4, Oracle 9.2.3 using 9.2.0.1 drivers. We really cannot set
          >our JTA
          >timeout to less than 1 minute and hence we are left with option2. Any
          >help would
          >be greatly appreciated.
          >
          >
          >"Tony Necakov" <[email protected]> wrote:
          >>
          >>Jane,
          >>Thanks for the reply. After talking to Oracle support, we believe we've
          >>discovered
          >>the cause of the problem. Apparently, setting the JTA transaction timeout
          >>does
          >>not affect the default timeout from Oracle's point of view. Consequently,
          >> XA
          >>transactions exceeding 1 minute (Oracle's default) were being marked
          >>by Oracle
          >>as in-doubt. Subsequent commits or rollback from the transaction manager
          >>were
          >>being ignored. The solution is to either knock the JTA timeout value
          >>to something
          >>below Oracle's default or install a BEA patch which allows the transaction
          >>manager
          >>to set the timeout on the Oracle resource manager.
          >>
          >>"Jane Sampson" <[email protected]> wrote:
          >>>Hi Tony,
          >>>
          >>>Yes, I believe there were some problems with 8.1.7. I believe it requires
          >>>an Oracle patch AND a JDriver patch (if you are using the WebLogic
          >JDriver).
          >>>Open a case with support for details.
          >>>
          >>>Thanks,
          >>>
          >>>Jane
          >>>BEA Support
          >>>
          >>>
          >>>"Tony Necakov" <[email protected]> wrote in message
          >>>news:[email protected]...
          >>>>
          >>>> We're seeing the same intermittent problem with Oracle 8.1.7.2 and
          >>>8.1.7.4. The
          >>>> problem occurs with WLS 6.1 service pack 3 and service pack 4.
          >>>>
          >>>> "Jane Sampson" <[email protected]> wrote:
          >>>> >Hi Tim,
          >>>> >
          >>>> >There is an issue has been reported for Oracle 9.2.0.1 Database/Oracle
          >>>> >9.2.0.1 Thin Driver and exhibits this behavior and is being address
          >>>by
          >>>> >both
          >>>> >BEA and Oracle. I would suggest you open a case with Customer Support
          >>>> >and
          >>>> >mention CR090816. It could be the same problem.
          >>>> >
          >>>> >Thanks,
          >>>> >
          >>>> >Jane
          >>>> >BEA Support
          >>>> >
          >>>> >"Tim Dawson" <[email protected]> wrote in message
          >>>> >news:[email protected]...
          >>>> >>
          >>>> >> I'm having an intermittent problem in our server where a distributed
          >>>> >transaction
          >>>> >> between WebLogic JMS (6.1 sp3) and Oracle (using the 9.1.2 XA
          >driver)
          >>>> >doesn't
          >>>> >> complete and subsequent attempts to access the rows in question
          >>>result
          >>>> >in:
          >>>> >>
          >>>> >> java.sql.SQLException: ORA-01591: lock held by in-doubt distributed
          >>>> >transaction
          >>>> >> 4.33.52658
          >>>> >>
          >>>> >> Has anybody else seen anything like this?
          >>>> >
          >>>> >
          >>>>
          >>>
          >>>
          >>
          >

Distributed transaction Management

How Oracle8i manage distributed transaction?

Unfortunately to manage transactions over web services there is no viable solution available in market. All implementations come with restrictions e.g. Metro works with only EJBs on Glassfish, JBossTS works on JBoss but not with JAX-WS, Atomikos supports only Axis as of now.
1. See explanation above.
2. Yes, it can be but conditions mentioned above are applied :-)
3. [www.oasis-open.org/committees/ws-tx/|www.oasis-open.org/committees/ws-tx/]
4. Unfortunately as of now I do not see an easy way to this problem.

Does Oracle 8.1.5 with weblogic 6.1 sp2 suppports Distributed Transactions ---A really night Mare

          Which version of jdbc thin driver should i use to achieve distributed transaction
          with oracle 8.1.5 in weblogic 6.1 sp2
          right now if iam using the driver classes provided in weblogic.jar iam gettig the
          following Exception
          AccountBean.ejbCreate( id = accountId, initial balance = $ 3000.0)
          java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured
          in the transaction branch start(
          ) failed on resource 'OracleXAPool' Unexpected error during start for XAResource
          'OracleXAPool': null
          at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
          at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
          at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
          at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
          at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
          at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
          at examples.ejb.basic.beanManaged.AccountBean.ejbCreate(Unknown Source)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_Impl.ejbCreate(AccountBean_g1748h_Impl.java:172)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.ejb20.manager.DBManager.create(DBManager.java:492)
          at weblogic.ejb20.manager.DBManager.remoteCreate(DBManager.java:462)
          at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:190)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl.create(AccountBean_g1748h_HomeImpl.java:76)
          at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy126.create(Unknown Source)
          at examples.wtc.atmi.simpapp.ToupperBean.putMessage(ToupperBean.java:194)
          at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.putMessage(ToupperBean_8roqg7_EOImpl.java:284)
          at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unknown
          Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Regards
          Ranga Rao


          Oracle Server 8.1.5 does not provide support for 2PC.
          Full XA support is provided from version 8.1.7.
          Sergi
          "Lawrence" <[email protected]> wrote:
          >
          >Ranga,
          >Please use classes12.zip for this.If you still find problem, please let
          >me know.
          >Thanks
          >Lawrence
          >
          >"Ranga Rao" <[email protected]> wrote:
          >>
          >>
          >>Which version of jdbc thin driver should i use to achieve distributed transaction
          >>with oracle 8.1.5 in weblogic 6.1 sp2
          >>
          >>right now if iam using the driver classes provided in weblogic.jar iam
          >gettig
          >>the
          >>following Exception
          >>
          >>////////////////////////////////////////////////////////////////////////////////////////////
          >>AccountBean.ejbCreate( id = accountId, initial balance = $ 3000.0)
          >>java.sql.SQLException: XA error: XAER_RMERR : A resource manager error
          >has
          >>occured
          >>in the transaction branch start(
          >>) failed on resource 'OracleXAPool' Unexpected error during start for XAResource
          >>'OracleXAPool': null
          >> at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1044)
          >> at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1010)
          >> at weblogic.jdbc.jta.Connection.getXAConn(Connection.java:148)
          >> at weblogic.jdbc.jta.Connection.prepareStatement(Connection.java:226)
          >> at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
          >> at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
          >> at examples.ejb.basic.beanManaged.AccountBean.ejbCreate(Unknown
          >>Source)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_Impl.ejbCreate(AccountBean_g1748h_Impl.java:172)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.ejb20.manager.DBManager.create(DBManager.java:492)
          >> at weblogic.ejb20.manager.DBManager.remoteCreate(DBManager.java:462)
          >> at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:190)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl.create(AccountBean_g1748h_HomeImpl.java:76)
          >> at examples.ejb.basic.beanManaged.AccountBean_g1748h_HomeImpl_WLSkel.invoke(Unknown
          >>Source)
          >> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          >> at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
          >> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          >> at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:158)
          >> at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
          >> at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
          >> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:253)
          >> at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:220)
          >> at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          >> at $Proxy126.create(Unknown Source)
          >> at examples.wtc.atmi.simpapp.ToupperBean.putMessage(ToupperBean.java:194)
          >> at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl.putMessage(ToupperBean_8roqg7_EOImpl.java:284)
          >> at examples.wtc.atmi.simpapp.ToupperBean_8roqg7_EOImpl_WLSkel.invoke(Unknown
          >>Source)
          >> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
          >> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:257)
          >> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
          >> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>/////////////////////////////////////////////////////////////////////////////////
          >>
          >>Regards
          >>Ranga Rao
          >>
          >>
          >

How to disable a field in a standard transaction

Good day,
Can any one tell me , with an example of , how to disable (the field should not allow any input ) a parameter or a select option in a standard transaction.

Probably the only way to achieve this is by creating transaction variants:
In the SAP Reference IMG, you can create transaction variants. Choose Basis Components ® Application Personalization ® Tailoring of Application Transactions ® Configure Transaction-Related Display Values for Fields (Transaction SHD0). Transaction variants allow you to preset values for fields in a transaction, set field attributes, or hide entire screens.
To execute a transaction variant, you define a variant transaction using the Transaction Maintenance transaction (SE93).
Once you have entered a transaction code and short description, choose transaction type Transaction with variant (Variant transaction).
To define a variant, enter the name of the transaction and the name of the variant. You can then use the new transaction code to start the special variant of the transaction.
Steps :-
Transaction SHD0 - Create a variant for the required transaction bychanging the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 you canname it as ZA02). Next allocate the transaction variant to this varianttransaction.

Weblogic 5.1, Distributed Transaction and Oracle Database Link

We are planning to add a new functionality to run in Weblogic server and it
needs to update tables in two different Oracle databases. Since we are using
Weblogic 5.1 and it is unrealistic to upgrade to 6.1 in short term, we have
to deal with the fact that distributed transaction is not supported by JTS
on 5.1.
One workaround we can think of is to utilize Oracle database link. Instead
of having two connection pools, the application talks to only one database
and access the tables on the other ones through Oracle database link.
Therefore, when a session bean tries to update two tables on database 1 in
one transaction, one of the tables is just a link to the other database. We
hope that even though distributed transaction is not supported by JTS in
Weblogic 5.1, but since it is supported by Orable, it would work.
Do you think the above workaround would work? Does anyone have experience on
something like that?
Thanks in advance,
David Chen
[email protected]

Hi. You should be able to use any JDBC driver with WebLogic 5.1.
It may be the JVM that complains, if you use too old a JVM...
Joe Weinstein at BEA Systems

How to disable distributed transaction in Weblogic 8.1?

Similar Messages

Maybe you are looking for