Will weblogic support 2 Phase support for MDB (Container Managed)

The Transaction is not rolling back when i am throwing an EJB exception during the update of the database
          Followed the below steps
          0) Created a XAConnectionPool (Oracle XA thin Driver)
          1) Created a DataSource for the above pool
          2) Created a QueueConnection factory with XA checked
          3) Deployed a MDB with Transaction Support as Required
          4) When the Database is throwing an exception the message is not rolled back /
          Any idea why this is happening?Will Weblogic 81 supports Container Management for MDB for 2PC transactions?
          i have Oracle driver in the weblogic start classpath and using getting the connection to the DB from the weblogic pool

- Of course WebLogic supports 2PC - and has for years.
          - There's no need to configure a JMS connection factory - the MDB's default choice is transaction capable.
          - See MDB doc for details on how to configure transactional MDBs.
          (hint: two descriptor settings are required)
          http://edocs.bea.com/wls/docs81/ejb/message_beans.html
          - FYI: You may want to consider upgrading to 9.1:
          * Can pause MDBs
          * Can pause destinations
          * Can view individual messages on the console
          * much higher file store performance
          * JDBC LLR option (faster than pure XA 2PC)
          * MDB transaction batching (speeds up XA - documentation is missing but will be in place soon)

Similar Messages

HT201071 When will RAW support for Pentax K3 be available for OSX and Aperture 3, finally? Really very much waiting for it!!!

When will RAW support for Pentax K3 be available for OSX and Aperture 3, finally? Really very much waiting for it!!!

We're all other users here, so can't answer that question. You can request it by submitting feedback here:
http://www.apple.com/feedback/

Any idea when Lightroom will have support for 5D Mark III?

Any idea when Lightroom will have support for 5D Mark III?

palashb wrote:
Thanks Geoff and Jeff.
On the regular LR updates, will the update be for LR3 also or just for LR4?
Thx.
I don't immediately recall a time when the previous version of LR was updated after the next version was released.

When Java 1.5 will be supported for EP7.0?

Hi!
We have 2 questions:
1) When Java 1.5 will be supported for EP7.0?
2) When will EP7.1 be released? And, EP7.1 would need Java 1.5?
Thanks! Points!

Hi,
1) When Java 1.5 will be supported for EP7.0?
>> Never. NW 7.0 uses NW Java AS 7.0 which is compatiple with Java 1.4 only
2) When will EP7.1 be released? And, EP7.1 would need Java 1.5?
>> currently NW CE 7.1 is released and a member of the NW 7.1 family. PI 7.1 is also released but full NW 7.1 will be announced at Q2 2008, but not sure when will ve GA. Ofcource this release will be the one which is fully compatiple with Java 1.5
regards

Any idea when we will get support for Java 7.5 in Safari?

I'm in school for a degree in software engineering and Java is a big part of it. As a regular Mac user who uses Safari as his main browser, it's disappointing that adoption of the latest Java versions in Safari seem to be lacking. Is there any way to get Safari to look at the latest versions of Java instead of being stuck on Java 1.6?
Thanks in advance for any help! :-)

Apple has kept up to date (more recently) with the latest releases of Java 6 (1.6.0_33), which is the current public release of Java. You can install the development Java 7 runtime from Oracle (currently on build 5), but this will not support many features and functions of the final release. All future updates to Java will be issued and maintained by Oracle as it's done on other platforms. Apple will not be offering an in-house Java runtime after Java SE 6. You can get the latest Java updates here: http://www.oracle.com/technetwork/java/javase/downloads/index.html

Information on Weblogic support for TANDEM

Dear all,
I would like to know whether Weblogic supports Tandem with Guardian OS. I need
to integrate applications in TANDEM, IBM OS/390 and Windows OS.
Please let me know if this possible.
Regards,
Virinchi K V N

S-23167: The support for Parlay X comes from Wysdom's MAP-OS 5.3 based on the BEA
WebLogic Platform 8.1 and not from BEA itself:
(http://www.wysdom.biz/news_archive3.html)
"Gennady Dosovitsky" <[email protected]> wrote:
>
I am looking for the information related to support Parlay/OSA specifications
(www.parlay.org)
by Weblogic.
Please respond if you have heard/known something on that.
Thanks.
Gennady

JDeveloper Weblogic support for IE 10

Hi,
Which Jdeveloper and Weblogic versions support IE 10?
We are using Jdev 11.1.1.4.0 and it does not support IE 9.
Thanks in advance!

Oracle WebLogic 10.3.4
http://www.oracle.com/technetwork/developer-tools/jdev/index-091111.html
no support for IE 10

Weblogic support for Parlay/OSA protocol

I am looking for the information related to support Parlay/OSA specifications (www.parlay.org)
by Weblogic.
Please respond if you have heard/known something on that.
Thanks.
Gennady

S-23167: The support for Parlay X comes from Wysdom's MAP-OS 5.3 based on the BEA
WebLogic Platform 8.1 and not from BEA itself:
(http://www.wysdom.biz/news_archive3.html)
"Gennady Dosovitsky" <[email protected]> wrote:
>
I am looking for the information related to support Parlay/OSA specifications
(www.parlay.org)
by Weblogic.
Please respond if you have heard/known something on that.
Thanks.
Gennady

Any idea when Lightroom 4 will have support for the new Canon 5D Mark III?

I have a new Canon 5D Mark III. When can we expect support for this camera in Lightroom 4?

It's already in the DNG converter that's posted along with ACR 6.7 Beta. That indicates probably the next version.

Any word on when HTML5 will be supported for deployment of FileMaker WebDirect?

Databases deployed through FileMaker's new WebDirect do not render properly in Firefox, apparently due to lack of support for HTML5. We deploy this on both Windows and Mac. -- Victor

I used to use FileMaker back in the day... when web publishing was primitive at best.
Do you know whether there is a publicly viewable demo site online that a volunteer could use to examine this problem? I suspect it might be hard for you to provide enough detail just with text. Or perhaps you can post a screen recording illustrating the problem.

Support for Software Configuration Management(SCM) Tools

Hi!,
I am using JDevloper for my project.
I want to maintain the versions of all files in the project.Also,if all are using one Workspace on network and someone updates a file then message box got dispalyed asking for reloading buffers again.
So to avoid this and maintain versions I want to use Software Configuration Management (SCM)Tools.So does JDeveloper supports for SCM tools?If yes kindly tell me how to use it?
Thanks
Amit
null

Hi,
The upcoming release of JDeveloper (3.2) has support for SCM. In this release, support has been integrated with Oracle's own SCM product, Oracle Repository. In future releases, other SCM products (e.g. CVS) will be supported.
When JDeveloper 3.2 is released (should be available at the end of Nov / start of Dec), the installation guide will have full details on how to install the Oracle Repository and use the SCM integration in JDeveloper.
In 3.1 or earlier, a custom addin exists for JDeveloper that can be used to support SCM systems (see JDeveloper documentation on OTN). However, this is not as tightly integrated as the new SCM support coming in 3.2.
Brian
JDeveloper SCM Team

Weblogic 10.3 not suporting for MDB to connect remote Weblogic JMS server

Hi,
I have a problem with MDB deployed on Weblogic 10.3.It's simple MDB which is communicating with remote weblogic JMS server. I am getting below exception. could some one help how to resolve this issue.
<Apr 14, 2009 11:28:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ReceiverFromDocumentum is unable to con
nect to the JMS destination: FMAContractOutboundQueue. The Error was:
[EJB:011013]The Message-Driven EJB attempted to connect to the JMS connection factory with the JNDI name: FMAConnectionFacto
ry. However, the object with the JNDI name: FMAConnectionFactory is not a JMS connection factory. NestedException Message is
:weblogic.jms.client.JMSConnectionFactory cannot be cast to javax.jms.XAConnectionFactory>
-Sreekanth

I recall that this particular warning message is sometimes misleading about the root cause of the problem, an issue that I think has been fixed in a patch. The actual problem can be various:
* The MDB is configured to be transactional, the connection factory exists, but the connection factory isn't configured to be "XA enabled". (I think this is the most likely problem).
* The connection factory doesn't exist.
* The object in JNDI with the specified connection factory name isn't actually a connection factory.
* The dest object in JNDI with the specified name isn't actually a javax.jms.Destination
Note that its unusual to configure the connection factory name for an MDB that consumes from WebLogic JMS. The default name iis usually sufficient unless custom tuning is required on the connection factory. See the MDB section of the EJB developer guide for more information.
Tom

MDB container managed transaction demarcation not working in wls 6.1 beta

I have an MDB which sends the messages it receives onto another JMS
          destination within the onMessage method. These messages are not sent to
          the JMS destination unless I explicitly use a transacted session for the
          destination and subsequently commit the session. If I set the transacted
          parameter to Session as false the messages are sent. If I set the
          transacted parameter to true the messages will only be output if the
          session is committed. This is the standard behaviour for a JMS session
          but this is not the correct behaviour for an MDB running with
          container-managed transaction demarcation.
          For a start the transacted parameter to session should be ignored when
          run in the context of a container transaction and the commit method
          should thrown an exception as it is not allowed within the context of a
          container transaction.
          This is the MDB code and the deployment descriptor: -
          public class MessageBean implements MessageDrivenBean, MessageListener
          private String topicName = null;
          private TopicConnectionFactory topicConnectionFactory = null;
          private TopicConnection topicConnection = null;
          private TopicSession topicSession = null;
          private Topic topic = null;
          private TopicPublisher topicPublisher = null;
          private TextMessage textMessage=null;
          private transient MessageDrivenContext messageDrivenContext = null;
          private Context jndiContext;
          public final static String
          JMS_FACTORY="weblogic.examples.jms.TopicConnectionFactory";
          public final static String
          TOPIC="weblogic.examples.jms.exampleTopic";
          public MessageBean()
          public void setMessageDrivenContext(MessageDrivenContext
          messageDrivenContext)
          this.messageDrivenContext = messageDrivenContext;
          public void ejbCreate()
          public void onMessage(Message inMessage)
          try
          jndiContext = new InitialContext();
          topicConnectionFactory =
          (TopicConnectionFactory)jndiContext.lookup(JMS_FACTORY);
          topic = (Topic) jndiContext.lookup(TOPIC);
          topicConnection =
          topicConnectionFactory.createTopicConnection();
          topicConnection.start();
          // The transacted parameter should be ignored in the context of a
          container tx
          topicSession = topicConnection.createTopicSession(true,
          Session.AUTO_ACKNOWLEDGE);
          topicPublisher = topicSession.createPublisher(topic);
          textMessage = (TextMessage)inMessage;
          topicPublisher.publish(inMessage);
          // this is illegal in a container transaction
          topicSession.commit();
          topicConnection.close();
          catch (JMSException je)
          throw new EJBException(je);
          catch (NamingException ne)
          throw new EJBException(ne);
          public void ejbRemove()
          <?xml version="1.0" encoding="UTF-8"?>
          <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          <ejb-jar>
          <enterprise-beans>
          <message-driven>
          <display-name>MessageBean</display-name>
          <ejb-name>MessageBean</ejb-name>
          <ejb-class>MessageBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <message-driven-destination>
          <destination-type>javax.jms.Queue</destination-type>
          </message-driven-destination>
          <security-identity>
          <description></description>
          <run-as>
          <description></description>
          <role-name></role-name>
          </run-as>
          </security-identity>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>MessageBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>Required</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>


Please see the response in the EJB newsgroup.
          Also, could you kindly only post to a single newsgroup?
          Thanks.
          "Jimmy Johns" <[email protected]> wrote in message
          news:[email protected]...
          > I have an MDB which sends the messages it receives onto another JMS
          > destination within the onMessage method. These messages are not sent to
          > the JMS destination unless I explicitly use a transacted session for the
          >
          > destination and subsequently commit the session. If I set the transacted
          >
          > parameter to Session as false the messages are sent. If I set the
          > transacted parameter to true the messages will only be output if the
          > session is committed. This is the standard behaviour for a JMS session
          > but this is not the correct behaviour for an MDB running with
          > container-managed transaction demarcation.
          >
          > For a start the transacted parameter to session should be ignored when
          > run in the context of a container transaction and the commit method
          > should thrown an exception as it is not allowed within the context of a
          > container transaction.
          >
          > This is the MDB code and the deployment descriptor: -
          >
          > public class MessageBean implements MessageDrivenBean, MessageListener
          > {
          > private String topicName = null;
          > private TopicConnectionFactory topicConnectionFactory = null;
          > private TopicConnection topicConnection = null;
          > private TopicSession topicSession = null;
          > private Topic topic = null;
          > private TopicPublisher topicPublisher = null;
          > private TextMessage textMessage=null;
          > private transient MessageDrivenContext messageDrivenContext = null;
          >
          > private Context jndiContext;
          >
          > public final static String
          > JMS_FACTORY="weblogic.examples.jms.TopicConnectionFactory";
          > public final static String
          > TOPIC="weblogic.examples.jms.exampleTopic";
          >
          > public MessageBean()
          > {
          > }
          >
          > public void setMessageDrivenContext(MessageDrivenContext
          > messageDrivenContext)
          > {
          > this.messageDrivenContext = messageDrivenContext;
          > }
          >
          > public void ejbCreate()
          > {
          > }
          >
          > public void onMessage(Message inMessage)
          > {
          > try
          > {
          > jndiContext = new InitialContext();
          > topicConnectionFactory =
          > (TopicConnectionFactory)jndiContext.lookup(JMS_FACTORY);
          > topic = (Topic) jndiContext.lookup(TOPIC);
          > topicConnection =
          > topicConnectionFactory.createTopicConnection();
          > topicConnection.start();
          > // The transacted parameter should be ignored in the context of a
          > container tx
          > topicSession = topicConnection.createTopicSession(true,
          > Session.AUTO_ACKNOWLEDGE);
          > topicPublisher = topicSession.createPublisher(topic);
          > textMessage = (TextMessage)inMessage;
          > topicPublisher.publish(inMessage);
          > // this is illegal in a container transaction
          > topicSession.commit();
          > topicConnection.close();
          > }
          > catch (JMSException je)
          > {
          > throw new EJBException(je);
          > }
          > catch (NamingException ne)
          > {
          > throw new EJBException(ne);
          > }
          > }
          >
          > public void ejbRemove()
          > {
          > }
          > }
          >
          >
          >
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          >
          > <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise
          > JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
          >
          > <ejb-jar>
          > <enterprise-beans>
          > <message-driven>
          > <display-name>MessageBean</display-name>
          > <ejb-name>MessageBean</ejb-name>
          > <ejb-class>MessageBean</ejb-class>
          > <transaction-type>Container</transaction-type>
          > <message-driven-destination>
          > <destination-type>javax.jms.Queue</destination-type>
          > </message-driven-destination>
          > <security-identity>
          > <description></description>
          > <run-as>
          > <description></description>
          > <role-name></role-name>
          > </run-as>
          > </security-identity>
          > </message-driven>
          > </enterprise-beans>
          > <assembly-descriptor>
          > <container-transaction>
          > <method>
          > <ejb-name>MessageBean</ejb-name>
          > <method-name>*</method-name>
          > </method>
          > <trans-attribute>Required</trans-attribute>
          > </container-transaction>
          > </assembly-descriptor>
          > </ejb-jar>
          >
          >
          >
          >
          >
          >
          >
          >

MDB Container Managed Transaction and Log4J

Hi,
I'm programming and MDB that reads and updates a database then sends out an HTTP Post and logs using log4j. I've read that when an MDB is configured as CMT or container managed transaction and the OnMessage method executes without errors, the transaction is implicitly commited. You can rollback the transaction by explicitly calling setRollbackOnly() or when a RuntimeException has been thrown. My worry is that after I have sent out an HTTP POST (a transaction has been completed) I would have to log a transaction completion using log4j. My problems is if log4j throws a RuntimeException thereby rolling back my transaction which shouldn't be the case. What I have done is to catch all Exceptions (and swallow them) whenever I log using log4j after I have sent out an HTTP POST succesfully (since my transaction should be complete by then). Is this a correct workaround?
Thanks :)

Your approach is correct. If you think, Log4J might throw errors, swallow the exceptions and try not to roll back.

Are Execute Threads supported for MDB in WL 7?

          WL6 used the default execute queue to service MDBs. Does WL7 allow a "named" execute-queue
          to service MDBs?
          Thanks
          Raj


Hi Raj,
          No. But funny you should ask. This feature will be available
          in the next release (although it did not make it into the beta).
          And, according to my sources, it likely will be back-ported to 7.0
          in the near term. Contact customer support.
          Tom, BEA
          Raj wrote:
          > WL6 used the default execute queue to service MDBs. Does WL7 allow a "named" execute-queue
          > to service MDBs?
          >
          > Thanks
          > Raj

Will weblogic support 2 Phase support for MDB (Container Managed)

Similar Messages

Maybe you are looking for