Roll back configure replace firewall configuration

configure replace
I have been working on ASA's for a will and when I need to revert back to the startup configuration I always need to reboot the ASA since copy run start just over writes the run. I seen that there is a configure replace command but with my 5525x running 9.2.1 I do not have the option:
ASA-HA-WEB(config)# configure ?
configure mode commands/options:
WORD Configure from HTTP:
http(s)://[<user>:<password>@]<location>[:<port>]/<pathname>.
Place IPv6 address within square brackets if a port is
specified.
factory-default Configure from factory-default
memory Configure from memory
net Configure from tftp
exec mode commands/options:
terminal Configure using terminal/console
Is there something I need to do to enable this?

Copy off a configuration you want to revert to to the local disk0: - i.e.:
copy run disk0:/good-config.txt
Then you can use it to copy over the running-config at any time:
copy disk0:/good-config.txt run
You can similarlyuse a network-based location and tftp but that depends on reachability to the store location.

Similar Messages

Unable to install AppleMobileDevise.Rolling back -- Errors before AMDS could be configured.

Unable to install AppleMobileDevise.Rolling back --> Message : Errors before AMDS could be configured.

"the installer encountered errors before iTunes could be configured".
That message sometimes comes at the end of a chain of error messages? If you get earlier error messages prior to that one, could you let us know what the earlier errors say, please?

Folders rolling back in finder view in 10.6 connected to a 10.6 server.

I have a server 10.6 with all updates and some times when i connect from 10.6.8 clients by AFP some folders roll back automatically any ideas?

By default the Windows Server 2008 will not have the Line Printer Daemon Service installed and running. With the Server 2008 configured with the Print Services role you need to select the TCP/IP Print Server (LPDSVC) service which allows computers that are using the Line Printer Remote (LPR) service to print to shared printers on this server. The Select Role Services wizard also creates an inbound TCP exception on port 515 for LPD in the Windows Firewall with Advanced Security.
With this enabled you should then be able to use the LPD queue you created on the Mac's to print to the Windows shared queue. Note that the Queue Name on the Mac will be the name of the share used on Windows. A good tip is to keep the share name short and without spaces.
Note that when you type the IP followed by \HP4015, you are connecting via RPC/SMB. For Windows this is known as Point & Print and while the Mac can connect to this same queue, you cannot use the same procedure. Instead you can use the Windows icon within the Add Printer browser to browse the workgroup then the computer name. When selected you often have to enter user credentials saved on Windows to then see the printer share. When the queue creation is completed you then can print but often have to authenticate every time you print. This is why LPD is preferred. The other thing is that with SMB connections, you often cannot use the vendors driver for consumer products. But if this HP is a LaserJet that supports PostScript then there won't be the same limitation.
Pahu

Rolling back from OIM version 11g to 9.1.0.2

Experts,
OIM version upgrade from 9.1.0.2 to 11g(11.1.1.5) need to be rolled back due to some error.
Just wanted to know views of experts.
Following steps have been completed so far of the upgrade guide [http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10129/upgrade_oim.htm].
•Task 1: Identify and Prepare Oracle Database for Oracle Identity Manager 11g (Optional)
•Task 2: Use the Repository Creation Utility to Create the Schema in the Database
•Task 3: Install Oracle Fusion Middleware
•Task 4: Use Upgrade Assistant to Upgrade the Oracle Identity Manager Schema
•Task 5: Create a WebLogic Domain for Oracle Identity Manager
•Task 6: Start the WebLogic Administration Server
•Task 7: Configure Oracle Identity Manager Server 11g
•Task 8: Configure Node Manager to Start Managed Servers
•Task 9: Start the SOA Managed Server
•Task 10: Start the Oracle Identity Manager Managed Server
•Task 11: Stop the Oracle Identity Manager Managed Server
Rollback strategy:-
1. Delete extra schemas(SOA MDC etc) created during Task2
2. Restoring the OIM DB schema (of version 9.1.0.2) from backup.
3. Updating back path and variables environment with old values
4. Starting the weblogic and OIM application from old Middleware_home and OIM_HOME.
Experts,
Above rollback strategy would be enough or should i take some other point in consideration.
If you can think of any other thing please share..
Thanks,
Manohar

Yes your strategies seems fine. for dropping schema you can RCU as well.
for restore, Drop all the entities manually from oim db schema So you don't have any grant issue while importing old 10g dump
--nayan

TS3212 Itunes 10.7 Rolls back installation after attempting to install on Windows Vista 64bit.

I downloaded the version in this link, presumably for Vista 64:
http://support.apple.com/kb/DL1577 . It goes through the process but rolls back the installaion and reports "error in installation". I turned off kaspersky Suite but got the sam emessage. Any ideas?

To clarify, I already have iTunes 10.6. Also, I just checked back on the iTunes installer (the manual one) and it now says: "iTunes Installer Completed
The installer encountered errors before iTuens could be configured.
Errors occurred during installation. Your system has not been modified.
Please run the installer again, or click Finish to exit."

Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back

Re-Posting message with more information.
Toplink 9.0.4.8 and JTS not rolling back transaction
Hi
Scenario:
I have a session bean (EJB1) calling a session bean (EJB2).
When an EJB1 is called, EJB1 persists data on to Table1 in database.
And EJB1 makes multiple calls to EJB2 to create entries in three different tables. Trans-attribute is set as required on both EJBS.
Problem:
EJB1 gets a Runtime Exception while inserting the data into TABLE1 (ORA-12899: value too large for column), EJB1 transaction is rollback, but all other transactions related to EJB2 are getting committed. I assume that they should roll back too.
Also, I did JAD on external transaction controller and listener and noticed that there is a transaction associated to each call. Meaning EJB1 had Transaction T1 and EJB2 had T2, T3, and T4 for the subsequent calls. When EJB1 is getting runtime exception in the method beforeCompletion(), the it calls rollbackGlobalTransaction() which is calling T1.setRollbackonly(). But not on on T2, T3, and T4 rollback
Am I missing anything?
Please help me
Here are my configuration details:
The datasource configuration:
<data-source name="myTxDataSource"
class="com.evermind.sql.OrionCMTDataSource"
location="jdbc/myTxDataSourceCoreDS"
xa-location="jdbc/xa/myTxDataSourceXADS"
ejb-location="jdbc/myTxDataSourceDS"
pooled-location="jdbc/myTxDataSourcePooledDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="duser"
password="d123"
url="jdbc:oracle:thin:@localhost:1521:ORCL"
inactivity-timeout="30"
/>
Sessions.xml
<login>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
<datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
<user-name>duser</user-name>
<encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
<encrypted-password>22F7AFE6F6B9672435537CE1189E123DD62D1A19DF561D1E</encrypted-password>
<uses-native-sequencing>true</uses-native-sequencing>
<uses-external-connection-pool>true</uses-external-connection-pool>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
Toplink Helper class that is used by both EJB's
This one uses SessionBroker. here is how it is initialized:
SessionManager manager = SessionManager.getManager();
sessionBroker = (SessionBroker) manager.getSession(xmlLoader,
sessionBrokerName, this.getClass().getClassLoader());
Oracle9iJTSExternalTransactionController extController = new Oracle9iJTSExternalTransactionController();
sessionBroker.setExternalTransactionController(extController);
It has common following commong methods:
public UnitOfWork getUnitOfWork() {
UnitOfWork uow = sessionBroker.getActiveUnitOfWork();
return uow;
public Object create(Object o)
UnitOfWork uow = getUnitOfWork();
uow.registerNewObject(o);
// added so that the assigned sequence number will be available before the commit happens
uow.assignSequenceNumber(o);
return o;
}

A couple of this appear different in your sessions.xml. To do what you want you need to configure TopLink to:
1. Use an external XT controller - requires flag to be set and controller provided
2. Use the OC4J data source - requires flag to be set and data source name provided
I notice that your sessions.xml has both a data source name as well as a direct connection URL.
Here is a sample that shows the proper settings for the external TX and data source usage:
<?xml version = '1.0' encoding = 'UTF-8'?>
<!DOCTYPE toplink-configuration PUBLIC "-//Oracle Corp.//DTD TopLink Sessions 9.0.4//EN" "sessions_9_0_4.dtd">
<toplink-configuration>
 <session>
 <name>default</name>
 <project-xml>META-INF/tlMap1.xml</project-xml>
 <session-type>
 <server-session/>
 </session-type>
 <login>
 <datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
 <platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
 <uses-external-connection-pool>true</uses-external-connection-pool>
 <uses-external-transaction-controller>true</uses-external-transaction-controller>
 </login>
 <external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
 <enable-logging>true</enable-logging>
 <logging-options>
 <print-thread>false</print-thread>
 <print-date>false</print-date>
 </logging-options>
 </session>
</toplink-configuration>Doug

Toplink 9.0.4.8 and JTS on OAS 10.1.2.0.0 and 10.1.2.0.2 not rolling back t

Toplink 9.0.4.8 and JTS not rolling back transaction
Hi
Scenario:
I have a session bean (EJB1) calling a session bean (EJB2).
When an EJB1 is called, EJB1 persists data on to Table1 in database.
And EJB1 makes multiple calls to EJB2 to create entries in three different tables. Trans-attribute is set as required on both EJBS.
Problem:
EJB1 gets a Runtime Exception while inserting the data into TABLE1 (ORA-12899: value too large for column), EJB1 transaction is rollback, but all other transactions related to EJB2 are getting committed. I assume that they should roll back too.
Also, I did JAD on external transaction controller and listener and noticed that there is a transaction associated to each call. Meaning EJB1 had Transaction T1 and EJB2 had T2, T3, and T4 for the subsequent calls. When EJB1 is getting runtime exception in the method beforeCompletion(), the it calls rollbackGlobalTransaction() which is calling T1.setRollbackonly(). But not on on T2, T3, and T4 rollback
Am I missing anything?
Please help me
Here are my configuration details:
The datasource configuration:
<data-source name="myTxDataSource"
class="com.evermind.sql.OrionCMTDataSource"
location="jdbc/myTxDataSourceCoreDS"
xa-location="jdbc/xa/myTxDataSourceXADS"
ejb-location="jdbc/myTxDataSourceDS"
pooled-location="jdbc/myTxDataSourcePooledDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="duser"
password="d123"
url="jdbc:oracle:thin:@localhost:1521:ORCL"
inactivity-timeout="30"
/>
Sessions.xml
<login>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<connection-url>jdbc:oracle:thin:@localhost:1521:orcl</connection-url>
<datasource>jdbc/DimpleTxDataSourceCoreDS</datasource>
<user-name>duser</user-name>
<encryption-class-name>oracle.toplink.internal.security.JCEEncryptor</encryption-class-name>
<encrypted-password>22F7AFE6F6B9672435537CE1189E123DD62D1A19DF561D1E</encrypted-password>
<uses-native-sequencing>true</uses-native-sequencing>
<uses-external-connection-pool>true</uses-external-connection-pool>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
Toplink Helper class that is used by both EJB's
This one uses SessionBroker. here is how it is initialized:
SessionManager manager = SessionManager.getManager();
sessionBroker = (SessionBroker) manager.getSession(xmlLoader,
sessionBrokerName, this.getClass().getClassLoader());
Oracle9iJTSExternalTransactionController extController = new Oracle9iJTSExternalTransactionController();
sessionBroker.setExternalTransactionController(extController);
It has common following commong methods:
public UnitOfWork getUnitOfWork() {
UnitOfWork uow = sessionBroker.getActiveUnitOfWork();
return uow;
public Object create(Object o)
UnitOfWork uow = getUnitOfWork();
uow.registerNewObject(o);
// added so that the assigned sequence number will be available before the commit happens
uow.assignSequenceNumber(o);
return o;
}

Doug, Andrei and others
I found the problem. I have a Delegate that provides access to all EJBS. This delegate is used by both the webtier and middle tier.It is written in a generic fashion so that the web server and middle tier does not have to be co-located in one container. getInitialContext() which is implemented as follows:
private static Context getInitialContext() throws NamingException
// Get InitialContext for Embedded OC4J.
// The embedded server must be running for lookups to succeed.
// actual code reads from the external parameters
String contextFactory = "com.evermind.server.rmi.RMIInitialContextFactory";
String principal = "admin";
String passwd = "admin123";
String providerURL = "ormi://localhost:3201/shc";
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, contextFactory);
env.put(Context.SECURITY_PRINCIPAL, principal);
env.put(Context.SECURITY_CREDENTIALS, passwd);
env.put(Context.PROVIDER_URL, providerURL);
env.put("dedicated.rmicontext","true");
return new InitialContext(env);
When the EJB1 tries to look up for EJB2, container thinks that the call is from outside the container and it is starting a new transaction.
When I changed the EJB1 to look up EJB2 to get the context as shown below,every thing seems to rolling back.
private static Context getInitialContext() throws NamingException
return new InitialContext();
Thanks again for pointing me in the right direction.
I will post the same message in other threads.
Raju

Transaction rolled back......soa 11g

I have a bpel process 1 which calls bpel process 2. Bpel process 2 is a file write. In my instance bpel process 2 is called and the file is written successfully. but bpel process 1 gets errored out with no errors being displayed. The bpel process 1 has a red colour at the point where it invokes the child process. and also a line saying transaction rolled back.
But there is no error in the child process instance
Please do suggest me the solution.

The issue may be due to the transaction timeout, verify the configured timeouts and the processing time of the process B.
Try increasing Sync Max Time Out and the other timeouts accordingly and test it.
Refer the below URL for the details of configuring the timeouts.
http://www.albinsblog.com/2011/11/oracle-soa-11g-configure-transaction_20.html
Regards
Albin I

RuntimeException in OnMessage() does not roll back

          Hello All, I have a transacted queue, the consumer is a java application. I configured
          an error queue for that queue. If I rollback manually in OnMessage(), the rolled
          back messages go into the error queue. However, if I have a RuntimeException,
          the last message (which has caused the exception) remains in the main queue pending
          and does not go into the error queue. I thought a RuntimeException causes a rollback().
          I use WLS 8.1. Any idea?
          Zoltan


Hi Zoltan,
          A runtime causes a rollback in an MDB, per the J2EE
          spec, but a runtime exception does NOT cause a rollback
          on a regular async client. The JMS specification is ambiguous
          on the latter - thus the difference.
          Instead, the message is
          redelivered once, and then, if it fails again,
          the message is no longer delivered
          and is implicitly committed on the next call
          to session.commit(). In your
          case, I highly recommend explicitly forcing the rollback.
          Tom
          Zoltan Pinter wrote:
          > Hello All, I have a transacted queue, the consumer is a java application. I configured
          > an error queue for that queue. If I rollback manually in OnMessage(), the rolled
          > back messages go into the error queue. However, if I have a RuntimeException,
          > the last message (which has caused the exception) remains in the main queue pending
          > and does not go into the error queue. I thought a RuntimeException causes a rollback().
          > I use WLS 8.1. Any idea?
          >
          > Zoltan

Rolled back JTA TX marked active/inflight

          Hello. I am writing a message driven bean that utilizes container managed transaction
          demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          The MDB relays message information to a legacy system. If the legacy system is
          down, I want to retry message delivery at a later point, so I mark the current
          transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          This causes the EJB container to continually call onMessage() with my message
          beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          however, are marked as active/inflight by the WLS transaction manager, leading
          to resource starvation and inability to create transactions because of an overflow
          of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          although the JTA monitoring tools clearly indicate that the TX has been rolled
          back.
          Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          Please cc: me if you respond as well
          Thanks,
          Alex
          ---- snippets follow ----
          Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          page
          Name Status Servers Resources Properties
          (key=value)
          (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          alexd {JMS_jmsStoreTest=rolledback} (none)
          And a listing of the JTA monitoring info
          Total Transactions: 45060
          Total Committed: 131
          Total Rolled Back: 44929
          Timeout Rollbacks: 0
          Resource Rollbacks: 0
          Application Rollbacks: 44929


I know this is fixed in WLS 6.1's GA release. Basically, the problem is
          that the EJB container is marking the transaction for rollback where it
          should be rolling it back. That's why you have so many tx's in-flight.
          They are waiting to time-out.
          -- Rob
          Alex DeNeui wrote:
          >
          > Hello. I am writing a message driven bean that utilizes container managed transaction
          > demarcation for the onMessage method (letting the container worry about msg acknowledgement).
          >
          > The MDB relays message information to a legacy system. If the legacy system is
          > down, I want to retry message delivery at a later point, so I mark the current
          > transaction as rolled back (via the setRollbackOnly() method in my MessageDrivenContext).
          > This causes the EJB container to continually call onMessage() with my message
          > beans, creating a large amount of rolled back exceptions. These rolled back transactions,
          > however, are marked as active/inflight by the WLS transaction manager, leading
          > to resource starvation and inability to create transactions because of an overflow
          > of the "Active Transaction" watermark (configurable in mydomain->JTA->Active Transactions),
          > although the JTA monitoring tools clearly indicate that the TX has been rolled
          > back.
          >
          > Eventually these "rolled back exceptions" are purged from the Inflight Transaction
          > list, and I can once again create transactions. Any ideas on how to fix this/workarounds/bugfixes?
          >
          > Please cc: me if you respond as well
          >
          > Thanks,
          > Alex
          >
          > ---- snippets follow ----
          >
          > Here is a snippet from the mydomain->myserver->Monitoring->JTA->Inflight Transactions
          > page
          > -----------------
          > Name Status Servers Resources Properties
          > (key=value)
          > (none) Rolled back. [Reason = weblogic.transaction.internal.AppSetRollbackOnlyException]
          > alexd {JMS_jmsStoreTest=rolledback} (none)
          > -----------------
          >
          > And a listing of the JTA monitoring info
          > -----------------
          > Total Transactions: 45060
          > Total Committed: 131
          > Total Rolled Back: 44929
          > Timeout Rollbacks: 0
          > Resource Rollbacks: 0
          > Application Rollbacks: 44929
          > ------------------
          Coming Soon: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnweblogic.com

Avoid transaction roll back using exception handler

Hi everybody!
I've created a proxy service in OSB using a DB adapter for polling from a database table. I've configured the service to be transactional with same transaction for reponse. The proxy has a route node that routes to a business service created from a db adapter for storing the polled data. Insert table has a db trigger associated wich raises a custom exception in certain cases. I need to catch that exception in the route exception handler to avoid the full transaction to be marked rolled back. For this, I've setup a response with failure action in the handler.
After testing the service I realized that it's not working as expected as transaction is being rolled back when the trigger raises the exception (so registry is not marked as polled in source table).
Could anyone explain me which action should be taken to avoid a rollback when handling exception?
Best regards,
Daniel.

Hi Athhek,
If I set reply with success then both route node and system error handlers are executed. I get following response metadata
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
</con:metadata>
and also following error reaches system handler:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382050</con:errorCode>
<con:reason>
Expected active transaction, actual transaction status: Marked Rollback
</con:reason>
<con:location>
<con:path>response-pipeline</con:path>
</con:location>
</con:fault>
When I set reply with error only route node handler is executed but I still get
<con:metadata xmlns:con="http://www.bea.com/wli/sb/test/config">
<tran:response-code xmlns:tran="http://www.bea.com/wli/sb/transports">1</tran:response-code>
</con:metadata>
Thank you.

Transaction not rolled back

 Configuration:
 - WLS 5.10 SP8
 - Oracle 8.1.6
 - TX DataSource connected to a Connection pool of oracle JDBC connections
 I have a stateless session with a method register() that performs three insert operations in the oracle database via a connection fetched from tha TX Datasource object.
 The method register has been marked with the transaction attribute required.
 I recieve a SQLException from Oracle when trying to insert in one of the three tables and want to rollback the transaction.
 I have tried to use setRollBackOnly(), throw an EJB exception
 and i get the following message from WLS:
 java.sql.SQLException: ORA-00001: unique constraint (ISACOWN.UK_ISIS_REFERENCE2) violated
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
 at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java, Compiled Code)
 at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java, Compiled Code)
 at oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1235)
 at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java, Compiled Code)
 at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
 at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1353)
 at oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java, Compiled Code)
 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java, Compiled Code)
 at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java, Compiled Code)
 at weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java:47)
 at weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedStatementImpl.java:54)
 at weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedStatement.java:55)
 at net.astrazeneca.cmi.data.Crud.execDML(Crud.java:283)
 at net.astrazeneca.cmi.data.dao.MolStructDAO.insertIsisRef(MolStructDAO.java:136)
 at net.astrazeneca.cmi.data.dao.MolStructDAO.insert(MolStructDAO.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
 at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
 at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 ti jan 23 11:12:20 GMT+01:00 2001: <EJB JAR deployment F:\Projects\MolStructureDS\MolStructureDS.jar> Transaction: '980237619834_1326' rolled back
 due to EJB exception:
 javax.ejb.EJBException
 at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
 Anybody got an idea ? at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
 at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
 at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 ti jan 23 11:12:20 GMT+01:00 2001:<E> <Adapter> Exception thrown by rmi server: [-3565031217135527434S157.96.215.53:[7001,7001,7002,7002,7001,-1]/466]
 javax.ejb.EJBException
 at net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStructureDSEOImpl.java, Compiled Code)
 at net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(MolStructureDSEOImpl_WLSkel.java, Compiled Code)
 at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java, Compiled Code)
 at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java, Compiled Code)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java, Compiled Code)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled Code)
 No matter what I have tried so far the two inserts that are OK are commited in Oracle. What I want is to make all three inserts in the transaction rolled back.
 Anybody got an idea ?


 Yes, all through the same connection and the connection is from a TX data source in
 WLS 5.1 with SP8
 But.... I do NOT fetch the connection inside the transaction..but I didn't think
 that was nescessery... is it ?
 When I tried this and checked the JDBC log the auto-commit was turned to off and
 everything worked smoothly.
 /Paul
 "Cameron Purdy" <[email protected]> wrote:
 >All through the same connection? And the connection is from a tx data
 >source? And auto-commit is off?
 >
 >If so, then someone is committing the transaction.
 >
 >Is this 5.1?
 >
 >--
 >Cameron Purdy
 >Tangosol, Inc.
 >http://www.tangosol.com
 >+1.617.623.5782
 >WebLogic Consulting Available
 >
 >
 >"Paul Eriksson" <[email protected]> wrote in message
 >news:[email protected]...
 >>
 >> I've already tried this but still... the tho first inserts are commited
 >and the third that causes the rollback of course is not.
 >>
 >> /P
 >>
 >> "Cameron Purdy" <[email protected]> wrote:
 >> >Don't set rollback only, just throw a runtime exception (like
 >EJBException).
 >> >
 >> >--
 >> >Cameron Purdy
 >> >Tangosol, Inc.
 >> >http://www.tangosol.com
 >> >+1.617.623.5782
 >> >WebLogic Consulting Available
 >> >
 >> >
 >> >"Paul Eriksson" <[email protected]> wrote in message
 >> >news:[email protected]...
 >> >>
 >> >> Configuration:
 >> >>
 >> >> - WLS 5.10 SP8
 >> >> - Oracle 8.1.6
 >> >> - TX DataSource connected to a Connection pool of oracle JDBC
 >connections
 >> >>
 >> >> I have a stateless session with a method register() that performs three
 >> >insert operations in the oracle database via a connection fetched from
 >tha
 >> >TX Datasource object.
 >> >>
 >> >> The method register has been marked with the transaction attribute
 >> >required.
 >> >>
 >> >> I recieve a SQLException from Oracle when trying to insert in one of
 >the
 >> >three tables and want to rollback the transaction.
 >> >>
 >> >>
 >> >> I have tried to use setRollBackOnly(), throw an EJB exception
 >> >> and i get the following message from WLS:
 >> >>
 >> >>
 >> >> java.sql.SQLException: ORA-00001: unique constraint
 >> >(ISACOWN.UK_ISIS_REFERENCE2) violated
 >> >>
 >> >> at
 >> >oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
 >> >> at oracle.jdbc.oci8.OCIDBAccess.check_error(OCIDBAccess.java,
 >> >Compiled Code)
 >> >> at oracle.jdbc.oci8.OCIDBAccess.executeFetch(OCIDBAccess.java,
 >> >Compiled Code)
 >> >> at
 >> >oracle.jdbc.oci8.OCIDBAccess.parseExecuteFetch(OCIDBAccess.java:1235)
 >> >> at
 >> >oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java,
 >> >Compiled Code)
 >> >> at
 >>
 >>oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232
 >)
 >> >> at
 >>
 >>oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:
 >1
 >> >353)
 >> >> at
 >> >oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java,
 >Compiled
 >> >Code)
 >> >> at
 >>
 >>oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.jav
 >a
 >> >, Compiled Code)
 >> >> at
 >>
 >>oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStat
 >e
 >> >ment.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.jdbc20.pool.PreparedStatement.executeUpdate(PreparedStatement.java
 >:
 >> >47)
 >> >> at
 >>
 >>weblogic.jdbc20.rmi.internal.PreparedStatementImpl.executeUpdate(PreparedSt
 >a
 >> >tementImpl.java:54)
 >> >> at
 >>
 >>weblogic.jdbc20.rmi.SerialPreparedStatement.executeUpdate(SerialPreparedSta
 >t
 >> >ement.java:55)
 >> >> at net.astrazeneca.cmi.data.Crud.execDML(Crud.java:283)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dao.MolStructDAO.insertIsisRef(MolStructDAO.java:1
 >3
 >> >6)
 >> >> at
 >> >net.astrazeneca.cmi.data.dao.MolStructDAO.insert(MolStructDAO.java,
 >Compiled
 >> >Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
 >..
 >> >java, Compiled Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
 >t
 >> >ureDSEOImpl.java, Compiled Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
 >S
 >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
 >a
 >> >pter.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
 >e
 >> >r.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
 >> >Compiled Code)
 >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> >Code)
 >> >> ti jan 23 11:12:20 GMT+01:00 2001: <EJB JAR deployment
 >> >F:\Projects\MolStructureDS\MolStructureDS.jar> Transaction:
 >> >'980237619834_1326' rolled back
 >> >> due to EJB exception:
 >> >> javax.ejb.EJBException
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
 >..
 >> >java, Compiled Code)
 >> >>
 >> >> Anybody got an idea ? at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
 >t
 >> >ureDSEOImpl.java, Compiled Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
 >S
 >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
 >a
 >> >pter.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
 >e
 >> >r.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
 >> >Compiled Code)
 >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> >Code)
 >> >>
 >> >> ti jan 23 11:12:20 GMT+01:00 2001:<E> <Adapter> Exception thrown by
 >rmi
 >> >server:
 >> >[-3565031217135527434S157.96.215.53:[7001,7001,7002,7002,7001,-1]/466]
 >> >>
 >> >> javax.ejb.EJBException
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDS.register(MolStructureDS
 >..
 >> >java, Compiled Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl.register(MolStruc
 >t
 >> >ureDSEOImpl.java, Compiled Code)
 >> >> at
 >>
 >>net.astrazeneca.cmi.data.dataservice.MolStructureDSEOImpl_WLSkel.invoke(Mol
 >S
 >> >tructureDSEOImpl_WLSkel.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAd
 >a
 >> >pter.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandl
 >e
 >> >r.java, Compiled Code)
 >> >> at
 >>
 >>weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java,
 >> >Compiled Code)
 >> >> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
 >Compiled
 >> >Code)
 >> >>
 >> >>
 >> >>
 >> >> No matter what I have tried so far the two inserts that are OK are
 >> >commited in Oracle. What I want is to make all three inserts in the
 >> >transaction rolled back.
 >> >>
 >> >> Anybody got an idea ?
 >> >
 >> >
 >>
 >
 >

Error 131 Transaction rolled back by lock wait timeout

Hello all,
I was trying to run apriori, and then HANA writer in my database.
Apriori executes directly, and then I configure and try to execute HANA Writer. But it keeps executing for more than half an hour, and then gives the following error: Error 131 Transaction rolled back by lock wait timeout. Lock timeout occurs while waiting TABLE_LOCK of mode EXCLUSIVE.
Bimal suggested me to reduce the data to be analysed, so then I reduced it to a pretty small part and executed again.
It gave me the same error after more than 30 minutes waiting executing.
after having this error, I tried just execute apriori, but with a filter of 5 transactions and than it worked. After that I tried to visualize the results, and got the following error:
It means that my HANA memory is full?
I got the view from HANA:
Regards!
Error 131 Transaction rolled back by lock wait timeout

Hi Jurgen,
I'm a developper for PAL from Shanghai team.
Could you please provide some details information about this case:
- How many records did you use ?
- What’s the value of “MIN_SUPPORT” and “MIN_CONFIDENCE” did you use ?
The algorithm of apriori will consume much memory when the input data is very large and min_support is low.
So I suggest you set “MIN_SUPPORT” and “MIN_CONFIDENCE” as 0.9 firstly, check if it can output result.
Thanks,
Peng

RFC Message Listeners giving "Roll Back Fault " Error

Hi ,
I have configured message listeners in SAP MII to collect control recipe from R/3 using "control_recipe_download". The connection l is working fine but when I try to push the message from R/3 I get an error "Roll Back Fault Not defined type of Handler class" in SM58.
Error Msg in MII log : " [JRA]asynch call CONTROL_RECIPE_DOWNLOAD with TID=AADDF85A47D14ED4ABC8E377 to dest. XMIIRFC01 on system can't be handled by StatefulSynchronousMessageListener"
I have updated the message listeners and restarted the NW server after creating the process message rule.So any other thing I need to check?
SAP Version : SAP R/3 4.6
SAP MII 12.2
Rgds,
Arun
Edited by: arun kurup on Nov 29, 2011 8:02 PM

Spot on Mike ...I had let the binding value blank and after setting it to XMII the messages are coming in MII
But anyways I have three RFC listeners for three different RFC destination but all the message are going to the third listener "XMIIRFC03" !!! The program id , listener update has all been done....I have asked for an server restart hope this solves it.
MII 12.2 with SP2 patch 8 deployed on NW 7.3 SP5.
We have the SAP upgrade on and will be connecting MII to new system soon till then its 4.6
Thanks for helping.
Rgds,
Arun

Help with frozen process, retry delay and transaction rolled back

Hi all,


Is there a way to create a JPD that will be able to retry a specific logic for several times with delay in between and freeze on the last retry. Also, at the same time, not rollback any database commits?


I have tried several ways to approach this but did not work.


1) create a JPD with transaction block with start node = "freeze on failure". Set retry count and delay in the transaction block. The outcome is, the JPD freezes, retries correctly, unfreezed properly, but all DB transactions are rolled back


2) create a JPD without transaction block, and set start node with "freeze on failure", group the nodes that I would like to perform retry and in the exception path add in the retry count. Use timer in the exception path to introduct the delay. The outcome of this is: JPD freezes, retries correctly, unfreezed INCORRECTLY (when trying to unfreeze this process, it will start at the ontimeout method of the timer and does not start from the beginning of the jpd), DB transactions are commited correctly


Any help or suggestions would be much appreciated...

Thanks!


Carol

The issue may be due to the transaction timeout, verify the configured timeouts and the processing time of the process B.
Try increasing Sync Max Time Out and the other timeouts accordingly and test it.
Refer the below URL for the details of configuring the timeouts.
http://www.albinsblog.com/2011/11/oracle-soa-11g-configure-transaction_20.html
Regards
Albin I

Roll back configure replace firewall configuration

Similar Messages

Maybe you are looking for