OSB 11 g - management transactions @ EJB typed Trasport

Similar Questions

• Contano managed transaction, when XA transaction is complete?

  Hello
  
  I used container managed transaction. And I want to understand when an XA transaction is considered to be "started" and when he is "done"?
  
  Assume the request stream is:
  JSF GUI-> managed-> JMS-> EJB Bean-> database.
  
  are there differences if the flow of the application like this:
  JSF-> managed Bean-> JMS1-> EJB-> JMS2-> GUI EJB-> JMS3-> database.
  
  The number of transactions XA is there in this case?
  
  Could you suggest if there's around tutorial to start with the XA transaction?
  
  Thank you
  
  Edited by: CardM November 2, 2012 12:38 AM

  Yes, I did.

  It's difficult material guy, you won't get there by guessing, hacking the code and ask questions in a forum. I strongly advise to read in JTA (Java Transaction API), get a good book on EJB technology (I recommend "Enterprise Javabeans 3.1'") and a very good book on JMS (cannot advise really something here). Google is your friend, and so are the Amazon book reviews.

• JMS sender with container managed transaction ejb3

  Hi all
  
  I refer to the following link http://download.oracle.com/docs/cd/E11035_01/wls100/jms/trans.html#wp1035937
  
  I found that JTA support JMS.
  
  But I have no ' to use JTA explicitly, I want to use the container to manage the transaction. for example. within the ejb3 stateless session bean.
  
  support JMS?
  
  With respect,
  WP

  Hello

  Yes, WebLogic JMS supports JTA (alias XA, a.k.a global) transactions such as container managed transactions. There are two conditions for CMTs on SSB:

  (1) use a parameter descriptor XML or EJB annotation to turn on CMT for SSB

  (2) use a WebLogic JMS connection factory that is configured to have 'global transactions (XA) enabled.

  And I usually recommend also:

  (3) consider using a JEE 'res-ref' for the connection factory to allow reunification of the JMS resources. See "Enhanced Support for using WebLogic JMS with EJB and servlet ' (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/j2ee.htm#g1329180) and the 'integration JMS remote suppliers' FAQ (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).

  (4) avoid using a BSN to receive messages. BMD is designed to process incoming messages.

  It is also possible to have WebLogic automatically registered foreign suppliers (non-WebLogic) in WebLogic transactions. See the 'integration JMS remote suppliers' FAQ for more details (http://download.oracle.com/docs/cd/E14571_01/web.1111/e13727/interop.htm#JMSPG553).

  Kind regards

  Tom

• OSB: "MQ Queue Manager Name" customization is not possible?

  Hello
  
  We try to use a customization file to set the "MQ queue manager name" on a MQ connection, but this property does not seem to be available for customization.
  
  It is not in the export of customization to create files and to 'guess' does not work either - we tried the two 'MQ queue manager name' and 'name of the MQ connection manager.
  
  Http://download.oracle.com/docs/cd/E11036_01/alsb30/consolehelp/customization.html documentation seems to say that it is possible, if someone can give us a helping hand with a snippet of XML?
  
  -Johan

  I raised a SR and got this response:

  Generic note
  ------------------------
  Hi Johan,.

  It seems that you have encountered a known problem already entered as a bug with the following description:

  BUG 10152445 - 'CONNECTIONS MQ QUEUE MANAGER NAME' MISSING IN the CUSTOMIZATION FILE

  Description of the problem:
  -------------------------------
  .
  Customer use customization files. They have some MQ resources which
  they automate the import.
  When they create a customization file for console of the OSB, property "MQ Manager."
  Name"is missing from the generated file.

  ....

  One solution is to add this element to the hand
  .
  The connections MQ queue manager name
  
  
  MQConnection
  by default/MyResource
  
  
  xmlns: XS = "http://www.w3.org/2001/XMLSchema" > YOUR_NEW_QUEUE_MANAGER_NAME
  

  then change the entry of different element FindAndReplaceCustomizationType
  for connections MQ queue manager name.
  .
  .
  
  
  
  MQConnection
  MQ connection timeout
  The MQ Connection Pool size
  MQ version
  MQ connection port
  MQ connection string name
  MQ host connection
  The connections MQ queue manager name
  
  MQConnection
  by default/MyResource
  
  fake
  Search string
  fake
  
  Replacement string
  
  .
  ================

  The bug has been fixed in the next version baseline code, and a patch is available only for the 11.1.1.3 version. So if you use OSB 11.1.1.3 you can download the patch from MyOracle support. Please, go to the tab "Patches and updates", insert 10152445 as the patch number and click on the search"" button. When the results appear please click the patch number and you should be able to download it. Instructions to apply the patches are available by clicking on the button "readme".

  Please let me know how it goes.

• Feature of OSB with ASM managed flash_recovery_area

  Is there a way to backup ASM, use of Datasets OSB file system?
  Sound like our RMAN backups are located in the path: ++ BACKUPSETS/FRA/PROD +
  Next, I would like to back up this path using the backup of filesystem OSB? I get an error message:
  
  "the following problems have been detected in dataset /Level_0_FS_Bkp:14: path invalid include + BACKUPSETS/FRA/PROD include the path.

  Have you created a database of the selectors of backup storage? He implemented a policy allowing to define what the media and readers to use for the backup. You can create a selector for backup storage of data base for all databases, or have several per database. You can create a policy for what go full backups of media and another for incremental backups etc. OSB will then automatically to the backup policy.

  Regarding the duplication scenario, I'd do the following:

  (1) create a family of supports for duplicate records IE off site
  (2) create a replication strategy that defines when the tapes must be duplicated and which family of media etc. IE dup1
  (3) create a schedule for duplication volume analysis
  (4) create a rotation policy for how you want the band moved between sites (you must have created an office (s) where will be found tapes)
  (5) create a scan of rotation schedule
  (6) a partner policy of duplication with your media families original IE level0_family (note a political split may be associated with multiple media families)
  (7) associate the rotation policy with the media family, that you created for your tapes off-site IE off site

  Now, you'll have to management the basic strategies for the bands... so it is automated. This is described more in detail in:
  http://www.Oracle.com/technetwork/database/secure-backup/learnmore/OSB-103-TWP-166804.PDF

  Donna

• OSB job Service Manager Doesnt Butterfly

  Hello
  
  I have a requrirement to throlle the number of concurrent requests to an endpoint.
  
  So I used OSB service business where in I am calling a webservice endpoint and set up a works Manager in the console and he selected the shipping policy
  
  I have deployed the workmanager on managed server. I specified threads concurrent max 3.
  
  I tried to test and see that limitation does not really... All requests sent are sent at the same time not 3 at a time.
  
  The expected behavior is 3 first sdhud go and onc ethey complete next 3 next 3 similar. But I do not see this behavior. Please let me know if I'm all worng
  
  Here's my configuration manager work
  
  
  Type of service no matter what XML Service
  Transport configuration
  Http protocol
  Load Balancing Algorithm alternate
  URI endpoint < endpoint URI specified >
  
  Retry Count 0
  Retry interval iteration 0
  Start Application Yes errors
  Configuration of HTTP Transport
  
  Reading timeout 0
  Connection time 0
  Query HTTP POST method
  Authentication no
  Proxy server
  Follow redirections HTTP with disabilities
  Use segmented Mode streaming
  Political distribution WorkManagerTest
  Configuration of message management
  
  MTOM/XOP support disabled
  Page attachments to disk no.
  Result caching not supported
  
  
  Any suggestions on this?
  
  Published by: 791951 on March 17, 2011 07:51

  Hello

  It worked. I used Service Call Out instead of node of the road. And it worked with questions.

• How to manage transactions during the different caches

  I found in the document, we could use TransactionMap to manage a transaction for a cache. For example, we put all the books in a cache named book_cache.
  But I wonder if we can manage a transaction on different caches. For example, we have all the books in book_cache and all of the editor, then put in publisher_cache. Then we consider change a book and change a Publisher as a unit of work. How to handle this?
  
  Thanks in advance.

  Hi Ramon

  You can use key association to ensure that a set of cache entries related is included in a partition one cache. This is what we call data affinity.

  See http://coherence.oracle.com/display/COH35UG/Data+Affinity

  According to John, which will guarantee of atomicity. Here is quote from John from a previous post.

  "The only way to ensure atomicity must ensure that a transaction cover partitions. You could watch association key to ensure that related data resides in the same partition. »

  Paul

• EJB transactions

  I'm developing a Web Service using an EJB Stateless, which has a single entry point (method). There are 3 steps in this method and I want to step 1 to occur in another transaction that steps 2 and 3 (which should be in the same transaction). These "measures" include vocations EJB Stateless injected. Let me explain with a code:

  @Stateless
  @WebService(...)
  public class MyWebServiceImpl implements MyWebService {
       @EJB
       private UserBusinessBean userBusinessBean;
  
       @EJB
       private EventsBusinessBean eventsBusinessBean;
  
       @WebMethod(...)
       public MyWebServiceResult process(MyWebServiceParam param) {
            // extract data from param
            EventResult createEventResult = eventsBusinessBean.createEvent(data); // step 1
            // do some extra processing
            User user = userBusinessBean.createUser(someData); // step 2
            // do some extra processing
            EventResult updateEventResult = eventsBusinessBean.updateEvent(moreData); // step 3
       }
  }
  

  The injected EJBs 2 themselves are stateless and have injected references to stateless persons DAoC, whose function is to call stored procedures to the database.

  I need to have step 1 running in a transaction and the steps 2 and 3 running in another transaction (because if step 2 or 3 fails, the news of step 1 is already committed).

  I know that I have 2 options to implement this: container-Manager transactions or managed by users. I think that the first approach is more secure than the second, in delegating management to the container (in my case, a Weblogic Server). But I can't understand how can I use Annotations in EJB Transactions to apply this logic. Can I annotate my beans injected Business methods? And what about the BCM, do need to have too many annotations? And what are those which one should I use?

  I hope you can give me a little help in this one. Let me know if you need to know more details of my implementation.

  Basically, you need to apply the attributes of correct transaction but only at the entrance to a string of calls when it is required. If you use 'CREATE_NEW' for example, the EJB invocation will create a transaction nested of its own rather than adopt the transaction that already existed. All work done in this 'inner' transaction will be validated and will not affect the "external" transaction, which was suspended before the end of the 'inner' invocation of EJB

  A tutorial on EJB tech explain what transaction attributes exist and what they do in the world. Applying them properly instead of always just using the default (REQUIRED) can help you create a transactional environment more controlled in which you have the chance of catching transactional errors early on (for example: If you have the code for which you know a transaction MUST exist that he succeed, the 'REQUIRED' attribute is useful). You will find that this bit of micro-management, it's making it a little more difficult to apply in a first time tech EJB, but ultimately when you start to 'see the matrix' it will actually start helping you establish a code clean design. However, that takes experience.

• noob question about EJB Transactions and concurrency

  I have a web client that calls a stateless session bean. This bean contains a method that checks the data in a database tables and, if everything looks good, calls a stored procedure that updates the tables. As I understand it, placing this method in a managed transaction container should ensure only one instance of the method inside the bean can run at any time and would prevent the 2 wires of operating simultaneously.
  
  Don't I have that right?

  So without implementing any kind of Singleton, EJB Transactions, or using persistence, would just add a lock inside the stored procedure be sufficient to ensure that not more than 1 customer could be modify account at once?

  Of course, in oracle - using a select... from

  update the locks the table at line level, which means that only the line of this account will be locked. Other users can still search only the rank.

  I'm sorry--I know not how it works for the other dbs.

  You must always an ejb CMT if you have some other updates to occur with this one and you need atomicity.

  Published by: ramp on June 27, 2011 20:06

• Why Distributed Transaction error at the Message bean but not not Backing Bean?

  Hi guys,.

  * Update * I read the second post first.

  Using JDeveloper 12.1.2.0.0 and integrated WebLogic server of the same version.

  I have an ADF program where a draft of the application using JDBC in a message bean.  If I create an Application Module within the project and then sign in using its connection (java: comp/env/jdbc/MyAdfConnDS), then the code below works fine.  However, if I search connection JDBC (jdbc/MyJdbcDS), I have configured in WebLogic myself, then I distributed transaction errors.  How can I configure my JDBC connection to imitate the one who creates the AppModule?  This way I can run prepared explicitly stated and validation of the call?

  Here is my code JDBC

          conn.setAutoCommit(false);
          PreparedStatement statement = conn.prepareStatement(sql);
          statement.setLong(1, companyAccountId);
  // errors here
          statement.execute();
          conn.commit();
          statement.close();
  
  
  

  Which results in the error

  // prepared statement.
  DELETE BUSINESS_PARTNERS WHERE MASTER_TYPE_KEY = 'C' AND COMPANY_ACCOUNT_ID = ?
  java.sql.SQLException: Cannot call commit when using distributed transactions
              at weblogic.jdbc.wrapper.JTAConnection.commit(JTAConnection.java:373)
              at com.sample.myProduct.jms.clients.MyClient.deleteEntities(MyClient.java:211)
              at com.sample.myProduct.jms.clients.MyClient.importData(MyClient.java:155)
              at com.sample.myProduct.jms.beans.ImportMessageBean.onMessage(ImportMessageBean.java:91)
              at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:575)
              at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
              at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:375)
              at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4855)
              at weblogic.jms.client.JMSSession.execute(JMSSession.java:4529)
              at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3976)
              at weblogic.jms.client.JMSSession.access$000(JMSSession.java:120)
              at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5375)
              at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:550)
              at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
              at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
  
  
  

  Here is a screenshot of all the available drivers: www.williverstravels.com/JDev/Forums/Threads/3544909/drivers.png, as well as the configuration of the transaction screen www.williverstravels.com/JDev/Forums/Threads/3544909/config.png

  I've tinkered enough to feel quite strongly, it is not an error in coding, but rather something in Weblogic.  I read what I can, but I don't know how the AppModule creates connections.  I would not add an AppModule just to retrieve its data source / login information if I don't.

  Ideas?

  Obviously, your message bean is configured to participate in a global transaction (for example, a JTA transaction). It is a behavior of the default message bean, even if you have not explicitly configured. When you get and use a JDBC connection in your message bean, this connection is attached to and participates in the overall transaction message bean (because you used compatible driver Oracle XA, it is seen on the 1st screenshot in your post), so you cannot perform local validation on the JDBC connection.

  Commit / rollback in this case can only be performed on the overall transaction (if the message bean is configured with the transactions managed by container) to be automatically or manually on the UserTransaction object (if the message bean is configured with bean-managed transactions). In other words, you must remove the conn.commit () statement, which is erroneous and obsolete when it is used in your message bean. If the message bean uses transactions managed by container, the container will commit / rollback automatically at the end of the method all the resources involved in the overall transaction (including your JDBC connection). If the method completed successfully (without exception), a validation will be performed. If the method fails (i.e., it ends with an exception), a cancellation will be made. If the message bean uses bean-managed transactions, the transaction is committed/restored when you explicitly call UserTransaction.commit () or UserTransaction.rollback ().

  The code above worked in a managed bean because JSF, ADF BC or ADF Faces applications require and participate in JTA transactions, then your JDBC connection has not been attached to a global transaction and you were able to perform local validation on the JDBC connection.

  You have two options to solve the problem. It depends on if you want your operations of JDBC to be in a global transaction with the bean of the message itself and its other actions or not. If they must be in a global transaction, then just remove the conn.commit () statement from your code. If they shouldn't be in a global transaction, you must either configure the message bean not to participate in global transactions or to configure the data source to use the «of the (thin) Oracle driver...» "instead of"Oracle (XA Thin)... driver. " ». (Remember to score the DataSource DO NOT to participate in a global transaction in the 2nd page of the data source configuration dialog in the management of WLS Console).

  NB. I highly recommend that you keep the global transactions. If you choose not to use a global transaction, it can happen that you committed the JDBC operations but an exception that happens after that, so the JMS message is not removed from the queue of messages and it will be processed after that, which causes the same operations of JDBC to be played and committed twice which must be avoided.

  Dimitar

• Problem with rollback transaction with foreign JMS provider

  Hello
  
  I created a small test to validate this transaction rollback works correctly with a foreign Jms provider (Sonic). My results seem to show that this isn't, but I have my installation is perhaps incorrect so any help appreciated...
  
  In the example below, I have an MDB that uses the movements of containers managed (Transaction required) and packaging. It receives a message & then sends another message.
  
  I've explicitly forced a rollback and wait for message received and sent message are ignored. However, on my Sonic queues, I see the number of messages on the output queue (where the message is sent) regularly every restitution time is more tempted, implying the sent message is not be restored.
  
  This is my EJB code: -.
  

  @MessageDriven(description = "sample mdb using weblogic resource wrappers", name = "WLPooledSonicJmsTransactionRequiredMessageDrivenBean")
  @TransactionManagement(value = TransactionManagementType.CONTAINER)
  @Resources( {
            @Resource(name = "connectionFactoryReference", mappedName = "localconnFactoryXA", type = javax.jms.ConnectionFactory.class),
            @Resource(name = "sendDestinationRef", mappedName = "local.out.queue1", type = javax.jms.Queue.class) })
  public class WLPooledSonicJmsTransactionRequiredMessageDrivenBean implements
            MessageListener {
  
       private ConnectionFactory sendingConnectionFactory;
  
       private Queue sendDestination;
  
       @Resource
       private MessageDrivenContext mdctx;
  
       @TransactionAttribute(value = TransactionAttributeType.REQUIRED)
       public void onMessage(Message message) {
            System.out
                      .println("on message called on WLPooledSonicJmsTransactionRequiredMessageDrivenBean!!");
  
            Connection jmsConnection = null;
  
            try {
                 String deliveryCount = message
                           .getStringProperty("JMSXDeliveryCount");
                 
                 System.out.println("JMSXDeliveryCount value is: " + deliveryCount);
  
                 if (sendingConnectionFactory == null)
                      System.out.println("sendingConnectionFactory was null!!");
                 sendingConnectionFactory = (ConnectionFactory) mdctx
                           .lookup("connectionFactoryReference");
  
                 if (sendDestination == null)
                      System.out.println("sendDestination was null!!");
                 sendDestination = (javax.jms.Queue) mdctx
                           .lookup("sendDestinationRef");
  
                 jmsConnection = sendingConnectionFactory.createConnection("xxx",
                           "xxx");
                 System.out.println("Sonic version = "
                           + jmsConnection.getMetaData().getProviderVersion());
  
                 Session s = jmsConnection.createSession(false,
                           Session.AUTO_ACKNOWLEDGE);
                 System.out.println("Transaction is: "
                           + weblogic.transaction.TransactionHelper
                                     .getTransactionHelper().getTransaction());
  
  
                 MessageProducer producer = s.createProducer(null);
  
                 Message response = s.createTextMessage("My Reply");
  
                 producer.send(sendDestination, response);
                 System.out
                           .println("message sent from WLPooledSonicJmsTransactionRequiredMessageDrivenBean!");
  
                    // force a rollback for testing purposes
                 mdctx.setRollbackOnly();
  
  
            } catch (JMSException e) {
                 e.printStackTrace();
                 // reset our jndi objects
                 sendDestination = null;
                 sendingConnectionFactory = null;
                 throw new EJBException(e);
            } finally {
  
                 // Return JMS resources to the resource reference pool for later
                 // re-use.
                 // Closing a connection automatically also closes its sessions, etc.
  
                 try {
                      if (jmsConnection != null)
                           jmsConnection.close();
                 } catch (JMSException e) {
                      // reset our jndi objects but no need to tell client
                      sendDestination = null;
                      sendingConnectionFactory = null;
                 }
  
            }
  
       }
  }

  Here are the weblogic-ejb-jar, which defines the destination of reception
  

  <?xml version="1.0" encoding="UTF-8"?>
  <weblogic-ejb-jar xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd"
          xmlns="http://www.bea.com/ns/weblogic/90"
          xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
          <weblogic-enterprise-bean>
          <ejb-name>WLPooledSonicJmsTransactionRequiredMessageDrivenBean</ejb-name>
          <message-driven-descriptor>
              <pool>
                  <max-beans-in-free-pool>4</max-beans-in-free-pool>
                  <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
              </pool>
              <destination-jndi-name>localmandytest</destination-jndi-name>
              <connection-factory-jndi-name>localconnFactoryXA</connection-factory-jndi-name>
              <jms-polling-interval-seconds>30</jms-polling-interval-seconds>
          </message-driven-descriptor>
      </weblogic-enterprise-bean>
  </weblogic-ejb-jar>

  and it has been part of the weblogic log output (this message is repeated that the container attempts to deliver the message)...
  

  on message called on WLPooledSonicJmsTransactionRequiredMessageDrivenBean!!
  Session transacted? = false
  message sent from WLPooledSonicJmsTransactionRequiredMessageDrivenBean!
  <07-Oct-2010 13:09:45 o'clock BST> <Info> <EJB> <BEA-010213> <Message-Driven EJB: WLPooledSonicJmsTransactionRequiredMessageDrivenBean's transaction was rolled back. The transaction details are: 
  ......

  Published by: MandyWarren on October 7, 2010 07:05 added weblogic-ejb-jar. XML
  
  Published by: MandyWarren on October 14, 2010 14:53 in order to take account of the last changes of the code
  
  Published by: MandyWarren on October 14, 2010 15:30 - code removed for only if rollback count == 1 because it does not work
  
  Published by: MandyWarren on October 21, 2010 22:36 deleted info specific environment

  Just a quick update...

  I raised this issue to the support of Oracle who confirmed that it was a bug see their response below...

  >
  I just got an update of JMS engineering.

  They Bug 81388508142162 is the best candidate: 8138850 is for WLS 9.2.x, while 8142162 is for WLS 10.0.x.
  The fix is included in 9.2.3 WLS and WLS 10.0.2
  >

  I upgraded to 10.0 MP2 as no new patches are now provided for 10.0 MP1 and the problem was solved.

  A big thank you to everyone for their help on this.

• AQ adapter with XA transaction

  Hi all

  We have a process of OSB consuming messages from AQ and publishes the message to IBM MQ.

  Oracle AQ is configured with max_retries = 5 and retry interval = 5 sec.

  In OSB, we use XA transactions, so that an error message will be moved to the exception queue,

  also in OSB in the error handling, we call a mistake common handling framework, which records the details of the error in DB and send notification by email.

  The question arises in the event of any error, because it's XA transactions, retry is set next to the AQ, OSB process is called 5 times and that's why he's going to the block of the error and error logging DB 5 times for each attempt.

  Someone please you suggest configuration or design changes to avoid this behavior,.

  The expected behavior is:

  • Transaction must be maintained, for example in case of error, message should go to the queue of the exception.
  • error should be registered only once.

  TIA,

  Vivek

  Hi Vivek,

  The way you have designed the interface is perfectly fine, but to do a small modification.

  Whenever you get an error, you should check whether the number of delivery is > the re-delivery limit set on the queue. If the number of delivery does not reach the limit of re-delivery, then don't update the DB with the error and allow rollback transaction.  (You can use if so clause to check the County of delivery). Once the number of delivery exceeds the limit of re-delivery, then update the DB with the details of the error and push it to the dead-letter queue. (the exception queue)

  (Ex: for JMS adapter, we use these properties jca.jms.JMSRedelivered, jca.jms.JMSProperty.JMSXDeliveryCount , jca.jms.JMSProperty.JMS_BEA_RedeliveryLimit. )

  The condition would be $JMSDeliveryCount > = $JMSRedeliveryLimit + 1 and redelivered = true () )

  It will be useful.

• Problem with Update Manager

  My system is running on VMware vSphere 5.1 (most recent) U1.

  I tried to update the host ESX (host State), but it failed with the error message:

  Patches of the scene to entity rvc-esx-01

  The host returns esxupdate error code: 15. The package manager transaction is not successful. Check the Update Manager logs and logs esxupdate for more details.

  I checked the esxupdate.log and there are many messages of error as follows. Please help me to identify the problem.

  I thank you very much.

  2013 05-28 T 06: 48:27Z esxupdate: HostInfo: DEBUG: check the file system on altbootbank...

  2013 05-28 T 06: 48:27Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = "[' / sbin/dosfsck ', '-a ', '-v ',' / dev/disks/naa.600508b1001cfd08a4849f06984fd8a2:5'] ', outfile = 'None', returnoutput = 'True', timeout ="0,0 "."

  2013 05-28 T 06: 48:27Z esxupdate: HostInfo: DEBUG: dosfsck dating 1

  Output: dosfsck 2.11 (March 12, 2005)

  dosfsck 2.11, 12 March 2005, FAT32, LFN

  Check the last sector of the file system, we can access

  Content of boot sector:

  ID of the system "MSDOS5.0".

  Byte media 0xf8 (hard drive)

  512 bytes / logical sector

  4096 bytes per cluster

  2 areas

  First FAT starts at byte 1024 (sector 2)

  2 fatty acids, 16-bit entries

  128000 bytes per FAT (= 250 sectors)

  Root directory begins at byte 257024 (district 502)

  512 root directory entries

  Data area starts at byte 273408 (sector 534)

  63929 data clusters (261853184 bytes)

  64 heads, 32 sectors/track

  0 hidden sectors

  total 511968 areas

  Fats are distinguished, but seem to be intact. Using FAT first.

  imgdb.tgz

  Contains a free cluster (39115). Assuming that the expressions of folklore.

  imgdb.tgz

  File size is 32029 bytes, the length of string cluster is 0 bytes.

  Truncate a file of 0 bytes.

  s.V00

  File size is 119879581 bytes, the length of string cluster is 109858816 bytes.

  File truncation

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: an exception error esxupdate was taken:

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: Traceback (most recent call changed):

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: file ' / usr/sbin/esxupdate ", line 216, hand-held

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: cmd. Run()

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esx5update/Cmdline.py", line 144, in the term

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Transaction.py", line 243, in InstallVibsFromSources

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Transaction.py", line 345, in _installVibs

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Transaction.py", line 388, in _validateAndInstallProfile

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/HostImage.py", line 639, at the stage

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Installer/BootBankInstaller.py", line 672 in StartTransaction

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: File "/ build/mts/release/bora-1065491/bora/build/esx/release/vmvisor/sys/lib/python2.6/site-packages/vmware/esximage/Installer/BootBankInstaller.py", line 302, in Recover

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: ERROR: InstallationError: ("," there was a file system on altbootbank of error checking, see log for details ".)

  2013 05-28 T 06: 48:27Z esxupdate: esxupdate: DEBUG: < < <

  2013 05-28 T 06: 48:32Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = ' [' / sbin/esxcfg-advcfg ', '-q', '-g', ' / UserVars/EsximageNetTimeout "]', outfile = 'None', returnoutput = 'True', timeout ="0.0 ".

  2013 05-28 T 06: 48:32Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = ' [' / sbin/esxcfg-advcfg ', '-q', '-g', ' / UserVars/EsximageNetRetries "]', outfile = 'None', returnoutput = 'True', timeout ="0.0 ".

  2013 05-28 T 06: 48:32Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = ' [' / sbin/esxcfg-advcfg ', '-q', '-g', ' / UserVars/EsximageNetRateLimit "]', outfile = 'None', returnoutput = 'True', timeout ="0.0 ".

  2013 05-28 T 06: 48:32Z esxupdate: esxupdate: INFO: -.

  Command: scan

  Args: ["scan"]

  Options: {'nosigcheck': zero, 'Retry': 5, "loglevel": zero, 'cleancache': None, 'viburls': zero, 'meta': ['http://172.29.137.20:9084/vum/repository/hostupdate/csco/csco-VEM-5.1.0-metadata.zip','http://172.29.137.20:9084/vum/repository/hostupdate/vmw/vmw-ESXi-5.1.0-metadata.zip'], 'proxyurl': None, 'timeout': 30.0, "cachesize": zero, "Valentina": True, 'maintenancemode': None}

  2013 05-28 T 06: 48:32Z esxupdate: BootBankInstaller.pyc: INFO: value not recognized 'title = loading VMware ESXi' in boot.cfg

  2013 05-28 T 06: 48:32Z esxupdate: BootBankInstaller.pyc: INFO: /altbootbank/boot.cfg: bootstate goes from 0 to 3

  2013 05-28 T 06: 48:33Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = "[' / sbin/bootOption ', '-rp'] ', outfile = 'None', returnoutput = 'True', timeout ="0,0 "."

  2013 05-28 T 06: 48:33Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = "[' / sbin/bootOption ', '-ro'] ', outfile = 'None', returnoutput = 'True', timeout ="0,0 "."

  2013-05 - 28 T 06: 48:33Z esxupdate: downloader: DEBUG: download http://172.29.137.20:9084/VUM/repository/hostupdate/CSCO/CSCO-VEM-5.1.0-metadata.zip to/tmp/tmprZ4JfI...

  2013 05-28 T 06: 48:33Z esxupdate: Metadata.pyc: INFO: unknown file vendor - index.xml in the metadata file

  2013-05 - 28 T 06: 48:33Z esxupdate: downloader: DEBUG: download http://172.29.137.20:9084/VUM/repository/hostupdate/VMW/VMW-ESXi-5.1.0-metadata.zip to/tmp/tmpytjFZI...

  2013 05-28 T 06: 48:33Z esxupdate: Metadata.pyc: INFO: unknown file vendor - index.xml in the metadata file

  2013 05-28 T 06: 48:33Z esxupdate: BootBankInstaller.pyc: INFO: value not recognized 'title = loading VMware ESXi' in boot.cfg

  2013 05-28 T 06: 48:33Z esxupdate: BootBankInstaller.pyc: INFO: /altbootbank/boot.cfg: bootstate goes from 0 to 3

  2013 05-28 T 06: 48:33Z esxupdate: vmware.runcommand: INFO: RunCommand called with: args = ' [' / usr/sbin/vsish ', '-e', '-p', 'cat', ' / hardware/bios/dmiInfo "]', outfile = 'None', returnoutput = 'True', timeout ="0.0 ".

  2013 05-28 T 06: 48:33Z esxupdate: esxupdate: INFO: everything is done!

  2013 05-28 T 06: 48:33Z esxupdate: esxupdate: DEBUG: < < <

  Yes run command now below.

  dosfsck - a w /vmfs/devices/disks/naa.600508b1001cfd08a4849f06984fd8a2:5

• OSB disable Server gives the problem in internal transport after interrogation of FTP

  Hello

  We use OSB with 2 managed servers. When managed server2 is not available, we get the following error during the processing of a remote file by using the ftp adapter.

  weblogic.jms.extensions.JMSOrderException: Member chopped jmsResources! dist_wlsb.internal.transport.task.queue.ftp_auto is jmsResources! wlsb.internal.transport.task.queue.ftp_auto_2, which is not available

  We have a proxy what polls for FTP site x files.

  In the proxy configuration, FTP Transport Configuration we set the managed server ("the service managed to run the polling the external resourcel poller service') to managed server1.

  It seems that after that interrogation of the external resource and a file is discovered, the OSB will forward the request via internal transport to server2 managed. However, it is disabled / not available.

  We disabled the second node (reflected in the server on the WLS tab), why is it trying to achieve managed server2?

  Thank you

  Stefan

  Even if you have server1 as the 'managed_server' means that only the file is picked up by server1, the treatment is still unloaded on the other servers in the cluster.

  If I remember correctly, we found that a change of setting fixed this problem for us - we need set sorting by arrival to false.

• OSB Proxy Service execution Timeout

  Dear Experts,
  
  How can I configure Oracle Service Bus proxy service timeout exactly? My scenario requires several service legend.
  
  Thanks in advance.
  Mike.Di

  Mike,

  Yes, the proxy of the OSB will continue running if it has launched its own transaction until the JTA timeout / any other service call error timeout/all occurs, whichever comes first (in this case the flow moves to the error handler). If proxy is running in the context of overall transaction that began at the source and then global transaction gets abandoned, then execution of the proxy will also get abandoned.

  I'll start proxy via the test console.

  This will fall in the first case (where OSB starts its own transaction)

  Kind regards
  Anuj