EJB calling Spring Bean with non XA Datasources causing Rollback Exception

We have an EJB CMT with Required calling a spring bean (@Transactional Propagation.NOT_SUPPORTED). This is causing an Rollback Exception saying 2 phase commit must be enabled. The EJB has to write to datasource 1, but the Spring Bean is ready only on Data Source 2. The Data Sources are set to use Non XA Driver with Support Global Transaction enabled for One phase commit. Any help is appreciated.

Similar Messages

Create XA MultiDataSource with Non-XA DataSource(support global txn)

I have two datasources DataSource1 and DataSource2. Since my driver doesnt support XA, I am Emulating XA for these two data sources.
Now, I want to create a Multi Data Source and add these two data sources. Is there anyway I can Emulate XA for this Multi Data Source?

Thanks for your quick reply Joe.
The target for this multipool is single managed server(not a cluster). wee have a lot of resources like MQ, AQ,ORacle etc in the transaction. This datasource is for Tandem jdbc. We dont have XA jdbc driver for this and thats the reason we are emulating the XA.
We were using weblogic 9.2 and there we were able to setup XA Multipool with non xa pools (with XA emulated) without any issues. and now we are migrating to weblogic 9.2
This is what i did in weblogic 9.2 console.
1. Created DataSource1 and DataSource2. Both have GloablTrasactionSupport enabled with Emulate XA
2. Created a MultiDataSource. During creation, I selected non-XA driver and from the data source page, I added DataSource1 and DataSource2. (If I select XA driver, then the datasource selection page wont show DataSource1 and DataSource2 since it is non-XA)
The MultiDataSource is deployed without any issues. but when my application try to get a connection from MultiDataSource, it is throwing below exception.
Sep 8, 2008 1:09:03 AM CDT> <Error> <EJB> <BEA-010080> <An error occurred while attempting to process a message inside a message-driven bean: weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl
JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = Multi_DataSource_XA
Exception is : weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl
JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = Multi_DataSource_XA
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1782)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:463)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
     at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:320)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:517)
     at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:533)
     at java.lang.Thread.run()V(Unknown Source)
>
Jiji

Calling a Bean with parameters

I would like to be able to call a JSF managed bean with a call such as
How can I code to use a href directly to call a faces managed bean method without using listener?
Thanks in advance.

Take a look at: http://blog.exadel.com/?p=19
This is a article how to use struts-like action to manage next steps
Sergey : http://jsfTutorials.net

BC4J with non-SQL datasource

Hi
Is it possible to use BC4J with non-SQL, non-relational datasources? For example, we are exploring the possibility of using a file-based XML datastore (NOT the XDB) as the back-end for some ADF screens.
Thanks,
Sean

BC4J is designed for SQL databases.
http://www.oracle.com/technology/products/jdev/collateral/tutorials/903/j2ee_bc4j/prnt/j2ee_bc4j.html#bc4j-faq

EJB 3 JNDI lookup with WL 12c (12.1.1) Exception

Hi all,
I'm trying to lookup an EJB inside my application with the following code :
Context ctx = new InitialContext();
ctx.lookup("java:module/MyEJB");
it throws this Exception :
javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:118)
     at javax.faces.component.UICommand.broadcast(UICommand.java:315)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
     at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
     Truncated. see log file for complete stacktrace
Caused By: javax.faces.el.EvaluationException: javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at javax.faces.component.UICommand.broadcast(UICommand.java:315)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
     Truncated. see log file for complete stacktrace
Caused By: javax.naming.NamingException [Root exception is java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:86)
     at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:466)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:256)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:170)
     Truncated. see log file for complete stacktrace
Caused By: java.rmi.RemoteException: weblogic.ejb.container.internal.StatelessLocalObject; nested exception is:
     java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject
     at weblogic.jndi.internal.WLEventContextImpl.copyObject(WLEventContextImpl.java:384)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:251)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:406)
     at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:170)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
     Truncated. see log file for complete stacktrace
Caused By: java.io.NotSerializableException: weblogic.ejb.container.internal.StatelessLocalObject
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158)
     Truncated. see log file for complete stacktrace
i'm using WL 12c, JDK 1.6.29.
regards.

I can't upload all the project, but i will upload the [required files|http://dl.dropbox.com/u/79750638/WLForum.7z] .
inform me if you need more info.
thanks

WSIF calling EJB 3.0 beans, with JAXB 2.0.2 as the JavaSerializer

I'm working with SOA suite (10.1.3.1.0 [build #0 ]), and I am trying to allow my BPEL processes to call my EJB 3.0 stateless session beans via WSIF.
This works fine when I am passing primitives (strings, dates and so-forth) between BPEL and my EJB's using WSIF.
However I want to be able to pass my 'business objects" across the BPEL/EJB boundary directly. I started off by following the BPEL cookbook article "Using WSIF for Integration" which was usefull in showing how to use JAXB 1.x generated classes across the BPEL/EJB boundary.
However in the project I am working on we want to use JAXB 2.0 as it allows us to create an XML schmea binding directly from our existing "business objects".
So I am using the knowlege gained in the article mentioned above to implement a custom JavaSerializer for my bpel process that will use JAXB 2.0. My custom JavaSerilizer is being invoked correctly, when I invoke my BPEL process, but it is unable to load the correct JAXB (2.0.2) classes - it keeps getting the JAXB 1.0 classes that come standard with oracle.
My debug code that prints out the classloaders for my serializers (and parent classloaders) reports the following:
06/09/05 11:18:18 CustomSerializer.serialize
06/09/05 11:18:18 Classloader =oracle.bpel.common:10.1.3
06/09/05 11:18:18 Classloader =api:1.4.0
06/09/05 11:18:18 Classloader =jre.extension:0.0.0
06/09/05 11:18:18 Classloader =jre.bootstrap:1.5.0_06
The Jaxb classes it is loading a coming from classloader:
06/09/05 11:18:18 JAXBContext classloader =oracle.xml:10.1.0_2
My question is how do I get the JAXB 2.0 classes in my classpath?
Thanks,
Dave Oram

Hello,
About WSIF, we are currently working on a WSIF-EJB30 binding that will allow you to direclty annotate the session ben and get the EJB exposed as SOAP and WSIF binding out of the box.
This will be available in OracleAS 10.1.3.1 production.
Regards
Tugdual Grall

Dependency inject a EJB 2.x bean with EJB3

Hi there
I have an old EJB3 2.x bean deployed on my server, that is registered in JNDI with the name "abc/xyz/ItemLookup_v35".
Now I wrote a EJB3 SFSB bean and I want to access the old bean using dependency injection. I tried it with the annotation
@EJB(mappedName = "abc/xyz/ItemLookup_v35")
private ItemLookupRemote itemRemote;but it wasn't working. How can I explicitly set the JNDI name of an old bean, that I want to lookup for?
Any help is appreciated!
Regards,
Stephan
Edited by: MasterRefactorer on Jun 27, 2008 7:31 AM

You can use @EJB to access 2.x Remote views, but the field type has to be the Home interface.
@EJB(mappedName = "abc/xyz/ItemLookup_v35")
private ItemLookupHome itemHome;

Jsp 2.0 tagfile with name-from-attribute causes jasper exception

hello there, i'm messing around with jsp 2.0 tag files and can't get this simple example to work (tried it for hours in variations ...)
the tag file:
<%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core" %>
<%@ attribute name="v" required="true" %>
<%@ variable name-from-attribute="v" variable-class="java.lang.Long" alias="a" scope="AT_END" %>
<c:set var="a" value="${123}"/>
<p> TAG: ${v} = ${a} </p>the jsp file:
<%@ taglib prefix="demo" tagdir="/WEB-INF/tags/demo" %>
<demo:varAttr v="x"/>
<p> JSP: x = ${x} </p>exception :
org.apache.jasper.JasperException: Unable to compile class for JSP
root cause:
java.lang.RuntimeException: org.apache.jasper.JasperException: /WEB-INF/tags/demo/varAttr.tag(3,1) The attribute directive (declared in line 2 and whose name attribute is "v", the value of this name-from-attribute attribute) must be of type java.lang.String, is "required" and not a "rtexprvalue".
... and so on
everything else works fine (name-given attribute).
i use tomcat 5.9.
any ideas? maybe somebody could try my example on a different installation.
thank you in advance for any help, because i ran out of ideas.

The attribute "v" is not allowed to take runtime expressions if you are using it with a name-from-attribute.
rtexprvalue defaults to true, so you must explicitly make it false.
<%@ attribute name="v" required="true" rtexprvalue="false" %>Cheers,
evnafets

Using Spring beans from EJB MDB

I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message.
The problem is I cannot get the spring context to load properly, since the MDBean it self is initialized(constructor called) only when it receives the first message from the broker, thus It's "too late" to initialize the spring context. What I want to do is load the spring context when the EJB is deployed in the Java EE container. So, is there a way I can call a some method, class, anything when the EJB is deployed in the container. Can I do something with a deployment descriptor?
I am using glassfish V2 UR1, EJB 3.0, Spring 2.0.7 The project is deployed as a jar.

Miku wrote:
I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message. Why not make it a real service? Spring's contract first web services are a very nice way to go. It hides the fact that you're using a message-driven component for processing, too.
%

EJB Stateless Session Bean Transactions

I have a stateless session bean.
Its deployment descripter references a JDBC DataSource.
It uses container managed transactions.
If I make JDBC calls, within a business method
of this stateless session bean, with the referred datasource, is it attached
to a container managed transaction?

If I make JDBC calls, within a business method
of this stateless session bean, with the referred
datasource, is it attached
to a container managed transaction?IIRC, yes. For CMT, the container will roll back any JDBC actions carried out by a method if it fails.

Concept: How can I handle a hole in a non-sap datasource?

Hello,
I want to discuss here a problem with non-sap datasource:
We load data from oracle db with db-connect technique. Each record we load has an idate(record is created) and a udate(record is changed). Based on the udate we create a kind of delta load:
The udate is selection criteria of the Infopackage(full upload)
In the start routine of the transferrule we detect the oldest udate and store it to the tvarc table. This UDATE is the low selection criteria for udate of the next load. So we reload only the records, which are change after the last load.
The data are transferred to ODS (overwrite) and so on..
That works perfect!
But now we find out, that in this non-sap datasource its possible to delete records directly. In SAP we have usually the procedure that a reversal document is created to delete a record(for example FI documents). In fact this non-sap datasource creates a hole in the database. A record is deleted > no udate change -> no change in BW. That means the record is still in BW!
Do you had a similar problem? Or do you have an idea how we could fix this problem.
I can not load all data every day by full upload that needs to much time more than 2 million data from five different datasources.
Thank you for your attention
Ralf

Hello,
To close my post, here is my solution:
- ODS A is filled by delta using the UDATE field.
- ODS B is filled by full upload. It contents only the key fields of ODS A (load needs
only 20 minutes)
- ODS C is filled by ODS A(only key fields) per full upload. In the startroutine of the
update rule is a check: Delete all data, which are in ODS B.
Result is: ODS C contents only the data, which have to be deleted in ODS A.
- Full upload ODS C to ODS A. Set in the start routine recordmode to 'R'.
Result is: these records are delete from the ODS A and change log of ODS A is
updated.
Before the next load the content of ODS B and C is deleted.
(cool picture:)
..........CUBE X
..............|
.(delta)....|
..............|........ODS C(diff. A - B)
..............|........|....|
..............|..(R).|....|.\ (check)
..............|........|....|..\
............ODS A....ODS B(keys)
.(delta)...|................| (full)
..........non sap systems
It's followed the principle of Sudhi's idea. But I did it not with PSA, because I have five different DataSources, so I need five calls to identify the records, which have to be deleted and five calls to edit the PSA ....
In this way I load everything in ODS and do the procedure only once time.
All the best Ralf

DelegatingVariableResolver not resolving Spring beans

I'm developing an application using ADF UI + Spring using Jdveloper11g and deploying it to Weblogic 10.3. I'm creating beans in Spring and injecting them into ADF as managed beans(via faces-config.xml). My faces-config.xml looks like:
-------------snip-----------------------
<?xml version="1.0" encoding="windows-1252"?>
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
<variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
</application>
<managed-bean>
<managed-bean-name>engineAspect</managed-bean-name>
<managed-bean-class>com.x.EngineAspect</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>engineAspect</property-name>
<value>#{engineAspect}</value>
</managed-property>
</managed-bean>
</faces-config>
-------------snip-----------------------
I'm using a backing bean to call a method on the engineAspect bean when some action happens in the UI. But, the line System.out.println(engineAspect); in the backing bean always prints a null. The backing bean has getter and setter for this field. Yet, the bean is not resolved from Spring. Any ideas what may be missing from the configuration?

Miku wrote:
I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message. Why not make it a real service? Spring's contract first web services are a very nice way to go. It hides the fact that you're using a message-driven component for processing, too.
%

Spring bean creation fails when statefull ejb created in other component

Hi All,
We have two components A and B. A creates stateful ejb as well calls B.
B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
Error creating bean with name 'dataSource' defined in file ....
Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
This happens only when A is using stateful beans.
when the flow uses A's stateless beans this is working fine.
For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
Env: Weblogic 10.3.2
Thanks and Regards
Veeramani

Hi All,
We have two components A and B. A creates stateful ejb as well calls B.
B inturn loads the beans using spring. While component B is trying to create the beans the following error is coming:
Error creating bean with name 'dataSource' defined in file ....
Invocation of init method failed; nested exception is java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators]
This happens only when A is using stateful beans.
when the flow uses A's stateless beans this is working fine.
For stateful beans, we are setting the Initialcontext. Has anyone faced this issue.
Env: Weblogic 10.3.2
Thanks and Regards
Veeramani

CMP Entity Bean with ejb-ql finder methods and INFORMIX database

Hi,
I have some CMP Entity Beans with finder methods defined in ejb-ql. In my ejb-jar, within <entity> definitions I have something like:
    <entity>
      <abstract-schema-name>BeanName</abstract-schema-name>
      <cmp-field><field-name>fieldOne</field-name></cmp-field>
      <cmp-field><field-name>fieldTwo</field-name></cmp-field>
      <query>
        <query-method>
          <method-name>findAll</method-name>
          <method-params></method-params>
        </query-method>
        <ejb-ql>SELECT OBJECT(o) FROM BeanName o</ejb-ql>
      </query>
    <entity>
And in persistent.xml:
<db-properties>
     <data-source-name>datasource_name</data-source-name>
</db-properties>
<entity-bean>
     <ejb-name>BeanName</ejb-name>
     <table-name>table_name</table-name>
     <field-map key-type="NoKey">
     <field-name>fieldOne</field-name>
     <column><column-name>column_one</column-name></column>
      </field-map>
     <field-map key-type="NoKey">
     <field-name>fieldTwo</field-name>
     <column><column-name>column_two</column-name></column>
      </field-map>
      <finder-descriptor>
          <method-name>findAll</method-name>
          <method-params/>
     </finder-descriptor>
Once deployed, on server side, I can found a java source file (with corresponding compiled class file) in path:
j2ee/cluster/server0/apps/companyName/MyEARApp/EJBContainer/temp/temp38837373733/route/to/package/
with names:
BeanName0_0pm.java
BeanName0_0PM.class
and the generated java file contains this code:
public java.util.Enumeration ejbFindAll() throws javax.ejb.FinderException, javax.ejb.EJBException {
    TransactionContext tc = pm.getTransactionContext();
    Connection conn = null;
    PreparedStatement pSt = null;
    ResultSet ejb_rs = null;
    int status = javax.transaction.xa.XAResource.TMSUCCESS;
    try {
      conn = pm.getConnectionForFindMethod();
      pSt = conn.prepareStatement("SELECT \"O\".\"COLUMN_ONE\",\"O\".\"COLUMN_TWO\", FROM \"TABLE_NAME\" \"O\"");
      ejb_rs = pSt.executeQuery();
I'm trying to call this method but it throws a SQLException when preparing the statement.
It seems that Informix does not like this SQL syntax because of upper case names, doble quotes on table alias, or something else.
When editing persistent.xml in netweaver, I can define the element <datasource-vendor> as ORACLE, SAPDB, MS_SQL_SERVER, DB2_UDB_AS400 or DB2_UDB_OS390 but INFORMIX is not an accepted value.
Is there any way to define how this SQL query is build?
Thanks in advance.

The return type of the finder method defined in the remote home interface is either the entity bean's remote interface or a collection of objects implementing the entity bean's remote interface. The return type of the finder method defined in the local home interface is either the entity bean's local interface or a collection of objects implementing the entity bean's local interface

Javax.ejb.ObjectNotFoundException: Bean with primary key '555' was not foun

When I delete a particular entity bean instance, i get the following exception:
javax.ejb.ObjectNotFoundException: Bean with primary key '555' was not found by 'findByPrimaryKey'.
But, the instance is being deleted from the database.
Anyone please help,
Thank u,
Seshu

Greetings,
When I delete a particular entity bean instance, i get
the following exception:
javax.ejb.ObjectNotFoundException: Bean with primary
key '555' was not found by 'findByPrimaryKey'.Interesting. How is your client calling the bean's remove method? Directly or through its home? Is it calling findByPrimaryKey before or after the call to remove? What is the PrimaryKey class type of your bean? Is the client passing a correct instance? All are things to be considered when troubleshooting your application. If more assistance is required, then seeing the relevant source code would be more helpful.
But, the instance is being deleted from the database.As is generally to be expected. No?
Anyone please help,
Thank u,
SeshuRegards,
Tony "Vee Schade" Cook

EJB calling Spring Bean with non XA Datasources causing Rollback Exception

Similar Messages

Maybe you are looking for