Generics in EJBs - ejbc fails in 9.0b

I have some SLSBs with typed collections such as
Map<String,String> someMethod (Collection<Integer> on);
in the local interface. The bean implementation implements this signature exactly. On startup, I'm getting messages like
...\EJBCompilerCache\-kbnb8wqnh8qy\Bean_4hmzpt_Impl is not abstract and does not override abstract someMethod(java.util.Collection) in Bean_4hmzpt_Intf
public final class Bean_4hmzpt_Impl
The signature in the WebLogic generated interface does not include my types, i.e., Map someMethod (Collection on), thus the error is expected. What's going on here?
Any ideas or help would be appreciated.

I'm using WLS9.2 MP2.
are Generics in EJB 2.x supported?
<Stephan Kesper> wrote in message news:[email protected]..
yupp, me too on 9.0. Unfortunately we are implementing a product on JBoss
where this is not an issue. Hence we are unable to support weblogic as
platform. Does any body know, if this is going to be fixed?

Similar Messages

Java Generics in Ejbs WebLogic 9.2 MP1 WindowsXP Sun JDK

Hi guys,
I tried to deploy our application on Weblogic Server 9.2 MP1 (Windows, Sun JDK) and during deployment I have this error see bellow.
Can somebody tell me what is the problem with generics and EJB compiler?
Is necessary to add any path or change any server settings?
Thanks for help
Robert
location: interface
...daoadapter_DaoAdapter_rge4uk_Intf
public void batchPersist(java.util.List<T> arg0);
^
...daoadapter_DaoAdapter_rge4uk_Intf.java:20: cannot find symbol
symbol : class T
location: interface
2 errors
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperatio
n.java:189)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:87)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:718)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1185)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:247)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:15
7)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(Deploymen
tReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiv
erCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCal
lbackDeliverer.java:45)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Thanks Matt for your answer.
But I don't finish my testing :)
I tried to deploy the same application on Weblogic 9.2 MP2 and then MP3 (sun jdk domain) and I didn't have problem with generics (application was correctly deployed and running).
Then something was fixed in newer versions or may be bea guys support more then is in EJB 2.x specification.
My next step, I'll try to deploy it on Jrockit domain and I give a note to conference what happen, may be it can help to somebody else.
Thanks
Robert

IDOC_AAE sender channel shows Commit fault: ASJ:ejb 005043 [Failed in component error]

Hello All.
We have a scenario IDOC to JDBC [ async-sync] scenario. And we have used Async/sync bridge using request response bean module.
Now the issue is that when IDOC is triggered from ECC it shows Commit fault:ASJ:ejb 005043[failed in component] error in SM58.
And if we click on "execute LUW" option the IDOC message reaches PI and gets processed successfully.
Could you please let me know how to fix this.
Thanks,
Jane

Hi Avinash,
NWA logs shows the following error :
[JRA]Couldn't start ResourceAdapter Servers with properties {jco.server.gwhost=essdev03, jco.server.progid=SAPRDB670POALEFEDEX, jco.server.gwserv=sapxxxx}, cause: JCo server is currently running. Current server state is ALIVE
Global [startApp] operation of application [sap.com/ClonedRA_xi~idoc~RA_~MCK_RDA_D~IDOC_Out_CLMLeadData] failed with errors on server process [2664350].
Thanks,
Jane

Idoc stuck in Sm58 Commit fault: ASJ.ejb.005043 (Failed in component:

Hi All,
We have an IDoc to File scenario and IDoc is stuck in tRFC with the error :Commit fault: ASJ.ejb.005043 (Failed in component:sap.com/com.sap.aii.ad
This is the new PI box and IDoc is triggered for the first time.
RFC destination is created for PI Java Stack as we are using ICO.
PI Version: 7.31
Regards,
Mani

Hello,
If you still receive the error after the above recommendations please go to the NWA logs and traces in PI and provide the corresponding error message from the developer trace.
Also check the configuration as per the following link has been done:
Configuring PI 7.30 Java IDoc Adapter
Kind regards,
Sarah

No client notification if EJB store fails

We are using Oracle EJB's with bean managed persistence. The client app ends a transaction using the usertransaction.commit and doesn't get any exception if a update failed.
How can we make shure that the client gets an exception if an update fails ?
Thanks in advance

Thanks for taking out the time... really appreciate it.
The problem is as follows:
Entity EJB:
Bean managed Persistence:
Transaction Attribute: Required
Home Interface:------------------------------
import java.rmi.*;
import javax.ejb.*;
import com.derigen.common.*;
public interface DerigenFuturesBean extends EJBObject {
public FuturesBean getDbObject() throws EJBException;
public void setDbObject(FuturesBean newDbObject) throws EJBException;
Remote Interface:----------------------------
import java.rmi.*;
import javax.ejb.*;
import com.derigen.common.*;
public interface DerigenFuturesBeanHome extends EJBHome {
public DerigenFuturesBean create(FuturesBean newDbObject) throws RemoteException, CreateException;
public DerigenFuturesBean findByPrimaryKey(DerigenPK primaryKey) throws RemoteException, FinderException;
Bean Class:----------------------------------
import javax.ejb.*;
import java.sql.*;
import com.derigen.common.*;
public class DerigenFuturesBeanBean implements EntityBean{
EntityContext ctx;
FuturesBean dbObject;
Connection conn;
String iString = "insert into future_deals (ID,TRADE_DATE,BUY_SELL_FLAG,CONTRACTS,CMD_ID,FM_MTH_ID,TO_MTH_ID,PRICE,BROKER_CP_ID,BROKER_RATE,CHA_CP_ID,CHACCT_ID,CHA_RATE,BOOK_ID,SPECULATIVE_HEDGE_FLAG) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)";
String uString = "update future_deals set TRADE_DATE = ?,BUY_SELL_FLAG = ?,CONTRACTS = ?,CMD_ID = ?,FM_MTH_ID = ?,TO_MTH_ID = ?,PRICE = ?,BROKER_CP_ID = ?,BROKER_RATE = ?,CHA_CP_ID = ?,CHACCT_ID = ?,CHA_RATE = ?,BOOK_ID = ?,SPECULATIVE_HEDGE_FLAG = ? where ID = ?";
String dString = "delete future_deals where ID = ?";
String sString = "SELECT FD.ID,to_char(FD.TRADE_DATE,\'DD-MON-YY\'),FD.BUY_SELL_FLAG,FD.CONTRACTS,FD.CMD_ID,CMD.CODE,FD.FM_MTH_ID,FMMTH.CODE,FD.TO_MTH_ID,TOMTH.CODE,FD.PRICE,FD.BROKER_CP_ID,BRKCP.CODE,FD.B ROKER_RATE,FD.CHA_CP_ID,CHACP.CODE,FD.CHACCT_ID,CHACCT.CODE,FD.CHA_RATE,FD.BOOK_ID,BOOK.CODE,FD.SPECULATIVE_HEDGE_FLAG FROM FUTURE_DEALS FD, COMMODITIES CMD, MONTHS FMMTH, MONTHS TOMTH, COUNTERPARTIES BRKCP, COUNTERPARTIES CHACP, CLEARINGHOUSE_ACCOUNTS CHACCT, TRADING_BOOKS BOOK WHERE FD.ID = ? AND FD.CMD_ID = CMD.ID AND FD.FM_MTH_ID = FMMTH.ID AND FD.TO_MTH_ID = TOMTH.ID AND FD.BROKER_CP_ID = BRKCP.ID AND FD.CHA_CP_ID = CHACP.ID AND FD.CHACCT_ID = CHACCT.ACCOUNT_ID AND FD.CHA_CP_ID = CHACCT.CP_ID AND FD.BOOK_ID = BOOK.ID";
String idString = "select id from future_deals where id = ?";
String sqString = "select fd_seq.nextval from dual";
PreparedStatement iStmt;
PreparedStatement idStmt;
PreparedStatement uStmt;
PreparedStatement dStmt;
PreparedStatement sStmt;
public DerigenFuturesBeanBean() {
public DerigenPK ejbCreate(FuturesBean newDbObject) throws CreateException {
dbObject = newDbObject;
try {
dbObject.setPrimaryKey(new FuturesPK(getIdFromSequence()));
if (((FuturesPK) dbObject.getPrimaryKey()).getId().equals("0"))
throw new CreateException("ID could not be retrieved from sequence.");
getConn();
iStmt = conn.prepareStatement(iString);
iStmt.setString(1, ((FuturesPK) dbObject.getPrimaryKey()).getId());
iStmt.setString(2, dbObject.getTradedate());
iStmt.setString(3, dbObject.getBuysellflag());
iStmt.setString(4, dbObject.getContracts());
iStmt.setString(5, dbObject.getCmdid());
iStmt.setString(6, dbObject.getFmmthid());
iStmt.setString(7, dbObject.getTomthid());
iStmt.setString(8, dbObject.getPrice());
iStmt.setString(9, dbObject.getBrokercpid());
iStmt.setString(10, dbObject.getBrokerrate());
iStmt.setString(11, dbObject.getChacpid());
iStmt.setString(12, dbObject.getChacctid());
iStmt.setString(13, dbObject.getCharate());
iStmt.setString(14, dbObject.getBookid());
iStmt.setString(15, dbObject.getSpechedgeflag());
int a = iStmt.executeUpdate();
iStmt.close();
return dbObject.getPrimaryKey();
} catch (SQLException se) {
throw new CreateException(se.getMessage());
public void ejbPostCreate(FuturesBean newDbObject) {
public DerigenPK ejbFindByPrimaryKey(DerigenPK primaryKey) throws FinderException {
FuturesPK pk = (FuturesPK) primaryKey;
try {
getConn();
idStmt = conn.prepareStatement(idString);
idStmt.setString(1, pk.getId());
ResultSet rs = idStmt.executeQuery();
if (!rs.next())
throw new FinderException("Record does not exist.");
rs.close();
idStmt.close();
return pk;
} catch (SQLException se) {
throw new FinderException(se.getMessage());
public void ejbActivate() {
public void ejbLoad() throws EJBException {
FuturesPK pk = (FuturesPK) ctx.getPrimaryKey();
dbObject = new FuturesBean();
dbObject.setPrimaryKey(pk);
try {
getConn();
sStmt = conn.prepareStatement(sString);
sStmt.setString(1, pk.getId());
ResultSet rs = sStmt.executeQuery();
if (rs.next()) {
dbObject.setTradedate(rs.getString(2));
dbObject.setBuysellflag(rs.getString(3));
dbObject.setContracts(rs.getString(4));
dbObject.setCmdid(rs.getString(5));
dbObject.setCmd(rs.getString(6));
dbObject.setFmmthid(rs.getString(7));
dbObject.setFmmonth(rs.getString(8));
dbObject.setTomthid(rs.getString(9));
dbObject.setTomonth(rs.getString(10));
dbObject.setPrice(rs.getString(11));
dbObject.setBrokercpid(rs.getString(12));
dbObject.setBroker(rs.getString(13));
dbObject.setBrokerrate(rs.getString(14));
dbObject.setChacpid(rs.getString(15));
dbObject.setClearinghouse(rs.getString(16));
dbObject.setChacctid(rs.getString(17));
dbObject.setClearinghouseaccount(rs.getString(18));
dbObject.setCharate(rs.getString(19));
dbObject.setBookid(rs.getString(20));
dbObject.setBook(rs.getString(21));
dbObject.setSpechedgeflag(rs.getString(22));
dbObject.setOlds();
rs.close();
sStmt.close();
} catch (SQLException se) {
throw new EJBException(se.getMessage());
public void ejbPassivate() {
public void ejbRemove() throws EJBException {
FuturesPK pk = (FuturesPK) ctx.getPrimaryKey();
try {
getConn();
dStmt = conn.prepareStatement(dString);
dStmt.setString(1, pk.getId());
int a = dStmt.executeUpdate();
dStmt.close();
} catch (SQLException se) {
throw new EJBException(se.getMessage());
public void ejbStore() throws EJBException {
try {
getConn();
uStmt = conn.prepareStatement(uString);
uStmt.setString(1, dbObject.getTradedate());
uStmt.setString(2, dbObject.getBuysellflag());
uStmt.setString(3, dbObject.getContracts());
uStmt.setString(4, dbObject.getCmdid());
uStmt.setString(5, dbObject.getFmmthid());
uStmt.setString(6, dbObject.getTomthid());
uStmt.setString(7, dbObject.getPrice());
uStmt.setString(8, dbObject.getBrokercpid());
uStmt.setString(9, dbObject.getBrokerrate());
uStmt.setString(10, dbObject.getChacpid());
uStmt.setString(11, dbObject.getChacctid());
uStmt.setString(12, dbObject.getCharate());
uStmt.setString(13, dbObject.getBookid());
uStmt.setString(14, dbObject.getSpechedgeflag());
uStmt.setString(15, ((FuturesPK) dbObject.getPrimaryKey()).getId());
int a = uStmt.executeUpdate();
uStmt.close();
} catch (SQLException se) {
throw new EJBException(se.getMessage());
public void setEntityContext(EntityContext ctx) {
this.ctx = ctx;
public void unsetEntityContext() {
this.ctx = null;
private String getIdFromSequence() throws SQLException {
getConn();
String idFromSeq = "0";
Statement stmt = conn.createStatement();
ResultSet rs = stmt.executeQuery(sqString);
if (rs.next())
idFromSeq = rs.getString(1);
return idFromSeq;
public FuturesBean getDbObject() {
return dbObject;
public void setDbObject(FuturesBean newDbObject) {
dbObject = newDbObject;
public void getConn() throws SQLException {
if (conn == null)
conn = new oracle.jdbc.driver.OracleDriver().defaultConnection();
XML Deployment Descriptor:-------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "ejb-jar.dtd">
<ejb-jar>
<enterprise-beans>
<entity>
<description>Entity Bean (Bean-managed Persis tence)</description>
<display-name>DerigenFuturesBean</display-name>
<ejb-name>DerigenFuturesBean</ejb-name>
<home>distributed.DerigenFuturesBeanHome</home>
<remote>distributed.DerigenFuturesBean</remote>
<ejb-class>distributedserver.DerigenFuturesBeanBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>com.derigen.common.DerigenPK</prim-key-class>
<reentrant>False</reentrant>
</entity>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<description>no description</description>
<role-name>PUBLIC</role-name>
</security-role>
<method-permission>
<description>no description</description>
<role-name>PUBLIC</role-name>
<method>
<ejb-name>DerigenFuturesBean</ejb-name>
<method-name>*</method-name>
</method>
</method-permission>
<container-transaction>
<description>no description</description>
<method>
<ejb-name>DerigenFuturesBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Oracle Specific Deployment Descriptor:-------
<?xml version = '1.0' encoding = 'UTF-8'?>
<!DOCTYPE oracle-descriptor PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN" "oracle-ejb-jar.dtd">
<oracle-descriptor>
<mappings>
<ejb-mapping>
<ejb-name>DerigenFuturesBean</ejb-name>
<jndi-name>test/DerigenFuturesBean</jndi-name>
</ejb-mapping>
</mappings>
</oracle-descriptor>
I have left out code for the generic/primary key classes, if you need that code too, please let me know.
As you can see ejbStore does an update and supposing it fails because the value being updated is too large or the tablespace fills up etc. I would expect to recieve an exception at the client side, but that doesn't happen.
Again I appreciate all the help.
Ashish.
null

WebLogic 8.1 ejbc failing under JDK 1.5

Hi,
when I invoke ejbc from my Ant build script I get a 'class file has wrong version 49.0, should be 47.0' message.
I'm compiling with JDK 1.5 and using ejbc from WebLogic 8.1 on Windows XP SP1.
I'm pretty sure I don't have any JDK 1.3 references anywhere as I updated the weblogic.jar file and the EJBs compile with javac.
Does anyone have any ideas, thanks in advance
James

WL 8.1 doesnt support Tiger. I have heard that WL 9.0 - Diablo does.

EJB Verification FAILED

Hello there.
First of all: I've been watching all the suitable topics and still no solution.
the problem is: 12 hours ago jBoss stopped to deploy project's .jar and beans.
Logger writes smth like:
-- ERROR -- Unexpected error javax.naming.NameNotFoundException: GSessionBean not boundthat's why servlet (using struts tm) gives:
root cause
java.lang.NoClassDefFoundError: org/jdom/ContentXDoclet and Packaging into .jar (I use Eclipse IDE) run successefully, but jBoss deployment failed:
Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@f904b43d { url=file:/C:/java/eclipse/jboss-3.2.2/server/default/deploy/infoserver.jar }
deployer: org.jboss.ejb.EJBDeployer@e5f46e
status: Deployment FAILED reason: Verification of Enterprise Beans failed, see above for error messages.
state: FAILEDnew jBoss doesn't help...I believe that people could help...I'm sitting there already for 12 hours and still no solution....

Hi There
After seeing the few lines of code......
The first thing i wanted to know is this:
1.Is your session beans home interface is mapped to a
JNDI name.yes
2. If mapped have you declared correctly in your
web.xml fileyes
..because it 've been working before correctly....I made one more deploy and...
3.How are u calling the session bean....a snippet of
the code...on login action:
GSession bean = GHelper.getGSessionInstance();in GHelper:
     public static ee.gennet.interfaces.GSession getGSessionInstance() throws NamingException, RemoteException,CreateException{
          ee.gennet.interfaces.GSession myBean =
          ((ee.gennet.interfaces.GSessionHome) getContext().lookup(
                         ee.gennet.interfaces.GSessionHome.JNDI_NAME)).create();
          return myBean;
     }>
Pl.check this and let me know....

EJB Generation failed

Hi All,
I am trying to build a small J2EE application using JBoss and Eclipse.
Inorder to get the required classes, interfaces when i go to Lomboz J2EE and click Generate EJB classes I get the following error message.
Make sure the jar file containing the ejbdoclet class is on the classpath speified in the taskdef that defined {2}. These classes are needed inorder to generate correct output.
Please help me sooon.
Thanks in Advance.

I tried a simpler version, it failed to import. No weblogic-ejb-jar.xml file generated. The ejb-jar.xml is empty:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"><display-name>Test</display-name></ejb-jar>
And got UnableToConvertTypeException.

EJB lookup failing in DCM managed Oracle AS clustering

Hi
My purpose is to test DCM managed Oracle AS clustering:
For that I have two Oracle Application servers installed in two different machines with
Version: 10.1.2.0.2 and Installation Type as J2EE and Web Cache
I created an OracleAS File-based Farm and associated both the instances of AS to the cluster. Then I created One OC4J instance called InstanceOne on the cluster and deployed my Application ear onto the cluster.I also configued web Application and EJB Application State Replication the with OracleAS Cluster (OC4J).
My Application has one Ejb module and a web module. My stateless Session bean is Spring framework implemented and I am trying to load the Spring Context lookup from the Struts Action Class by using WebApplicationContext.
My spring context looks like this
<bean id="jndiTemplate"
class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">com.evermind.server.rmi.RMIInitialContextFactory</prop>
<prop key="java.naming.provider.url">opmn:ormi://<server host>:InstanceOne/<Application Name></prop>
<prop key="java.naming.security.principal">oc4jadmin</prop>
<prop key="java.naming.security.credentials">admin</prop>
<prop key="oracle.j2ee.naming.cache.timeout">30</prop>
<prop key="Dedicated.Connection">yes</prop>
<prop key="Dedicated.RMIcontext">false</prop>
<prop key="LoadBalanceOnLookup">true</prop>
</props>
</property>
</bean>
<bean id="service"
class="org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean">
<property name="jndiTemplate">
<ref bean="jndiTemplate"/>
</property>
<property name="jndiName">
<value>MyServiceEJB</value>
</property>
<property name="cacheHome">
<value>false</value>
</property>
<property name="refreshHomeOnConnectFailure">
<value>true</value>
</property>
<property name="businessInterface">
<value>com.my.springejb.MyBusinessInterface</value>
</property>
</bean>
When I give only one server lookup like
opmn:ormi://<server host1>:InstanceOne/<Application Name>
then lookup is working, But by giving two servers in cluster, like opmn:ormi://<server host1>:InstanceOne/<Application Name>, opmn:ormi://<server host2>:InstanceOne/<Application Name>
I am getting error like this
06/12/01 19:27:41 java.lang.NumberFormatException: For input string: "InstanceOne"
06/12/01 19:27:41 at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
06/12/01 19:27:41 at java.lang.Integer.parseInt(Integer.java:468)
06/12/01 19:27:41 at java.lang.Integer.parseInt(Integer.java:518)
06/12/01 19:27:41 at com.evermind.server.rmi.RMIInitialContextFactory.getInitialContext(RMIInitialContextFactory.java:237)
06/12/01 19:27:41 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
06/12/01 19:27:41 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
06/12/01 19:27:41 at javax.naming.InitialContext.init(InitialContext.java:219)
06/12/01 19:27:41 at javax.naming.InitialContext.<init>(InitialContext.java:195)
06/12/01 19:27:41 at org.springframework.jndi.JndiTemplate.createInitialContext(JndiTemplate.java:105)
06/12/01 19:27:41 at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:83)
06/12/01 19:27:41 at org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.create(SimpleRemoteStatelessSessionProxyFactoryBean.java:19)
My intension of testing is, if I make one server instance (InstanceOne) down then my lookup should divert all ejb calls to the other server in the cluster, which is not happening at all, and I am getting Server SHUT DOWN exception in the server.
Can anybody please let me know, whether the approach is correct and is there any problem with Spring lookup which does not support multiple host lookup or anything I am missing in my steps, as I am following the Oracle Application Server High Availability Guide 10g Release 2 (10.1.2)

you can find an running sample from :
http://javahowto.blogspot.com/2007/12/calling-weblogic-ejb-3-from-jruby-and.html
In weblogic, local ejb don't appear in the jndi tree, but , it can be founded ...
It works into 10.0 and 10.3
Cheers !

Simple ejb project fails to run but debugs OK

OK, here's my first foray into the world of EJB3:
It's trivial to be sure.
==== SessionBean.java===
package sess;
import javax.ejb.Stateless;
@Stateless
public class SessionBean implements SessionRemote, SessionLocal {
    public String hello(String world) {
        String val = "hello " + world;
        System.out.println("bean says: " + val);
        return val;
}=====SessionRemote.java====
package sess;
import javax.ejb.Remote;
@Remote
public interface SessionRemote {
    String hello(String world);
}and the grande application is this:
=====Main.java====
package toyproj;
import javax.ejb.EJB;
import sess.SessionRemote;
public class Main {
    @EJB
    static private SessionRemote sess;
    public static void main(String[] args) {
        System.out.println(sess.hello("world"));
}I've done all this in Netbeans 6.1 and I can deploy the session bean OK. Now here's the rub: The "application client" gets a NullPointerException as if the session object didn't get injected at all. If I run it in "debug mode", it runs OK though.
Have I made an obvious mistake?

yeah, it's bizarre. I just re-created a brand new project with same contents on a different computer (at home now) and get the same result. I feel i'm missing something simple! Forgot to say, it's GlassFish 2.1 and Java 1.6.
anyway here's the appclient output with stack trace:
init:
deps-jar:
compile:
library-inclusion-in-archive:
dist:
deps-jar:
compile:
library-inclusion-in-archive:
Building jar: /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist/ToyProject-app-client.jar
dist:
pre-run-deploy:
Redeploying /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist/ToyProject-app-client.jar
Start registering the project's server resources
Finished registering server resources
While redeploying, trying to stop the application in target server completed successfully
While redeploying, trying to remove reference for application in target server completed successfully
deployment started : 0%
deployment finished : 100%
Deploying application in domain completed successfully
Trying to create reference for application in target server completed successfully
Trying to start application in target server completed successfully
Deployment of application ToyProject-app-client completed successfully
All operations completed successfully
Enable of ToyProject-app-client in target server completed successfully
Enable of application in all targets completed successfully
All operations completed successfully
post-run-deploy:
run-deploy:
Copying 1 file to /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist
run-tool:
24-Jul-2008 19:33:10 com.sun.enterprise.appclient.MainWithModuleSupport <init>
WARNING: ACC003: Application threw an exception.
java.lang.NullPointerException
        at toyproject.Main.main(Main.java:8)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:266)
        at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:449)
        at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:259)
        at com.sun.enterprise.appclient.Main.main(Main.java:200)
Exception in thread "main" java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
        at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:461)
        at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:259)
        at com.sun.enterprise.appclient.Main.main(Main.java:200)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:266)
        at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:449)
        ... 2 more
Caused by: java.lang.NullPointerException
        at toyproject.Main.main(Main.java:8)
        ... 8 more
Java Result: 1
run-jar:
run-display-browser:
run:
BUILD SUCCESSFUL (total time: 11 seconds)When I print out the SessionBean itself, it prints "null".
I guess server output isn't helpful since the server never even gets contacted here, and when i "debug" it does the right thing. Anyway the fish doesn't spew errors, just a torrent of messages about deploying and stuff.
This is the appclient output when "Debug"
init:
init:
deps-jar:
compile:
library-inclusion-in-archive:
dist:
deps-jar:
compile:
library-inclusion-in-archive:
Building jar: /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist/ToyProject-app-client.jar
dist:
pre-run-deploy:
Redeploying /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist/ToyProject-app-client.jar
Start registering the project's server resources
Finished registering server resources
While redeploying, trying to stop the application in target server completed successfully
While redeploying, trying to remove reference for application in target server completed successfully
deployment started : 0%
deployment finished : 100%
Deploying application in domain completed successfully
Trying to create reference for application in target server completed successfully
Trying to start application in target server completed successfully
Deployment of application ToyProject-app-client completed successfully
All operations completed successfully
Enable of ToyProject-app-client in target server completed successfully
Enable of application in all targets completed successfully
All operations completed successfully
post-run-deploy:
run-deploy:
Copying 1 file to /home/seb/NetBeansProjects/ToyProject/ToyProject-app-client/dist
debug-tool:
Non-existing path "/home/seb/glassfish-v2ur2/lib/dom.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/xalan.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/xercesImpl.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/jaxrpc-impl.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/saaj-impl.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/jaxr-impl.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/relaxngDatatype.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/xsdlib.jar" provided.
Non-existing path "/home/seb/glassfish-v2ur2/lib/fscontext.jar" provided.
Have no FileObject for /home/seb/glassfish-v2ur2/lib/dom.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/xalan.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/xercesImpl.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/jaxrpc-impl.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/saaj-impl.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/jaxr-impl.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/relaxngDatatype.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/xsdlib.jar
Have no FileObject for /home/seb/glassfish-v2ur2/lib/fscontext.jar
Listening for transport dt_socket at address: 9009
Attached JPDA debugger to localhost:9009
hello world
debug-jar:
debug:
BUILD SUCCESSFUL (total time: 16 seconds)as you see i do get some errors about missing file or what but it runs OK.

@EJB injection fails in 11gR1?

Hi !
I can't get the @EJB injection to work on 11g R1. Is there any known issues?
I tried this example : http://glassfish.java.net/javaee5/ejb/examples/Sless.html
but the Weblogic server only gives NullpointerExeption.
Is there any additional code that need to be added ?
Regards, reZer

Hi,
I am having exactly the same problem with my application.
Have your resolved this and how. I think may be the EJB jar
is not being deployed. The Java naming directory interface(JNDI)
to which you used the initialiseContext to insert the works for me too.
But the @EJB injection does not work. You provided the JNDI name
for Accountcontroller and that works but it won't work with injection.
You only provide the client with the JNDI of the session bean only
if you are using a stand alone client. But if you are running the client
as an application client, you need to use the @EJB injection.
I am also stack looking for solution.
Thanks
eve

Ejb lookups fail from threads spawned from servlet

Hello,
We have a servlet from which we are spawning a thread. In the thread we are
trying to do a JNDI lookup for the database resource / EJBs. It does not
work as if it is not able to find the context t do the lookup.
I thought that the threads are spawned in the same JVM and context, so why
does the lookup not work.
Please need to figure out a solution to this problem, we need to call some
business logic in the EJBS from the thread and we do not want to do RMI-IIOP
lookups becuase they could be slower.
Appreciate your help in advance.
Regards,
Sakib

Custom threading is not supported. I think a workaround was posted on
this alias (search for custom threading), where you can call the
proprietary API's of the container to recreate the context, but I'm
pretty sure that it's not a supported or recommended solution.
The better (and more scalable) solution is to avoid spawning your own
threads.
David
Sakib Mehasanewala wrote:
Hello,
We have a servlet from which we are spawning a thread. In the thread we are
trying to do a JNDI lookup for the database resource / EJBs. It does not
work as if it is not able to find the context t do the lookup.
I thought that the threads are spawned in the same JVM and context, so why
does the lookup not work.
Please need to figure out a solution to this problem, we need to call some
business logic in the EJBS from the thread and we do not want to do RMI-IIOP
lookups becuase they could be slower.
Appreciate your help in advance.
Regards,
Sakib

EJB projects failed after server restart

Hi Experts,
I had deployed some Web Dynpro projects and EJB projects. But everytime after server restarts or SDM restarts, the EJB projects will gone. I have to redeploy the EJB projects to make the WDP projects works, or else the WDP projects will hit nullpointer which saying not able to find the specific EJB.
Any idea?
Thanks & Regards,
Sarah

Thanks
wawoodwa , this command solved my problem!!!
On other sites I found command:
"Update-MailboxDatabaseCopy –Identity ‘DB2’ –CatalogOnly" it was not working, I got the same error as OldSchoola.

EJB clustering fail over problem.

          I have setup 2 server cluster, WL5.1 patch 6 on NT. when client make calls to EJBs , you can see these 2 server load balancing (Round-Robin). after I stop one server in it, I got null pointer exception at client. what did I miss ?
          Thanks in advance,
          java.lang.NullPointerException
          at weblogic.rjvm.RJVMFinder.isThisHost(RJVMFinder.java:340)
          at weblogic.rjvm.RJVMFinder.isHostedByLocalRJVM(RJVMFinder.java:314)
          at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:151)
          at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
          at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:19
          at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:14
          at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
          at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
          at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
          at javax.naming.InitialContext.init(InitialContext.java:218)
          at javax.naming.InitialContext.<init>(InitialContext.java:194)
          at com.avinamart.ApplicationServices.ServiceManager.getInitialContext(ServiceManager.java:66)
          at com.avinamart.ApplicationServices.ServiceManager._getApplicationService(ServiceManager.java:117)
          at com.avinamart.ApplicationServices.ServiceManager.getOrganizationService(ServiceManager.java:210)
          at com.avinamart.WebInterface.EPASSServicesReference.getOrganizationService(EPASSServicesReference.java:77
          at com.avinamart.WebInterface.EPASSReferences.getBusinessUserStruct(EPASSReferences.java:367)
          at com.avinamart.WebInterface.EPASSReferences.getUserPath(EPASSReferences.java:200)
          at jsp_servlet._en._detail_95_org._jspService(_detail_95_org.java:326)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


What's the url for your lookup?
          Is it mapped to one server or multiple servers?
          - Prasad
          Tony Lu wrote:
          > I have setup 2 server cluster, WL5.1 patch 6 on NT. when client make calls to EJBs , you can see these 2 server load balancing (Round-Robin). after I stop one server in it, I got null pointer exception at client. what did I miss ?
          >
          > Thanks in advance,
          >
          > java.lang.NullPointerException
          > at weblogic.rjvm.RJVMFinder.isThisHost(RJVMFinder.java:340)
          > at weblogic.rjvm.RJVMFinder.isHostedByLocalRJVM(RJVMFinder.java:314)
          > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:151)
          > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
          > at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:19
          > at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:14
          > at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:123)
          > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
          > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
          > at javax.naming.InitialContext.init(InitialContext.java:218)
          > at javax.naming.InitialContext.<init>(InitialContext.java:194)
          > at com.avinamart.ApplicationServices.ServiceManager.getInitialContext(ServiceManager.java:66)
          > at com.avinamart.ApplicationServices.ServiceManager._getApplicationService(ServiceManager.java:117)
          > at com.avinamart.ApplicationServices.ServiceManager.getOrganizationService(ServiceManager.java:210)
          > at com.avinamart.WebInterface.EPASSServicesReference.getOrganizationService(EPASSServicesReference.java:77
          > at com.avinamart.WebInterface.EPASSReferences.getBusinessUserStruct(EPASSReferences.java:367)
          > at com.avinamart.WebInterface.EPASSReferences.getUserPath(EPASSReferences.java:200)
          > at jsp_servlet._en._detail_95_org._jspService(_detail_95_org.java:326)
          > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          > at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
          > at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
          > at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:247)
          > at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
          > at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

EJB - Remote EJB - Transaction Fails to Commit

I have an SLSB running on an instance of WebLogic 8.1.5 and has a method with a transaction attribute of Required. It calls another SLSB running on another WebLogic 8.1.5 that runs on a remote server and that EJB has a method with a transaction attribute of Required. When the first SLSB completes its call to the second EJB and gets all the data returned back to it, the first SLSB method completes and WebLogic attempts to commit the transaction. When this happens, it appears that the transaction on the second box does not commit and times out. The first SLSB has a transaction timeout of 30 seconds and the second SLSB has a transaction timeout of 500 seconds.
I found this article that relates to secure communication between WebLogic instances:
http://forums.bea.com/bea/message.jspa?messageID=400005264&tstart=0
Our credentials match on both boxes and the -Dweblogic.transaction.SecurityInteropMode=value did not do anything.
This is the error that we see in our log files:
[DEBUG] 2007-06-13 08:52:33,766 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
.ape.dao.hipaaauth.AuthResponseDAOJdbcImpl : ADDING AuthResponse - SANDB
OX-488
[DEBUG] 2007-06-13 08:52:33,776 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
.ape.dao.hipaaauth.RejectResponseDAOJdbcImpl : ADDING RejectResponse for e
vent- 4570 reject type=7B
javax.transaction.TransactionRolledbackException: Exception while commiting Tx : BEA1-00360416CD7939
F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledback(EJBRuntimeUtils.java:2
02)
at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:90)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:343)
at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
Session_p1z9z7_EOImpl.java:56)
at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6985)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
92)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
... 2 more
<Jun 13, 2007 8:56:32 AM PDT> <Error> <EJB> <BEA-010026> <Exception occurred during commit of transa
ction Name=[EJB com.foo.ape.ejb.ReceiptHandlerSessionEJB.handleEvent(java.lang.String)],X
id=BEA1-00360416CD7939F523D3(25864837),Status=Rolling Back. [Reason=weblogic.transaction.internal.Ti
medOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=243,seconds
left=10,XAServerResourceInfo[medMgmtDbPool]=(ServerResourceInfo[medMgmtDbPool]=(state=rolledback,as
signed=ccsServer),xar=medMgmtDbPool,re-Registered = false),XAServerResourceInfo[ccsDbPool]=(ServerRe
sourceInfo[ccsDbPool]=(state=rolledback,assigned=ccsServer),xar=ccsDbPool,re-Registered = false),SCI
nfo[ccs+ccsServer]=(state=rolledback),SCInfo[DeersDirect2+Deers]=(state=rolling-back),properties=({w
eblogic.transaction.name=[EJB com.foo.ape.ejb.ReceiptHandlerSessionEJB.handleEvent(java.l
ang.String)]}),local properties=({weblogic.jdbc.jta.ccsDbPool=weblogic.jdbc.wrapper.TxInfo@c11d39, w
eblogic.jdbc.jta.medMgmtDbPool=weblogic.jdbc.wrapper.TxInfo@659b02}),OwnerTransactionManager=ServerT
M[ServerCoordinatorDescriptor=(CoordinatorURL=ccsServer+141.177.53.164:7101+ccs+t3+, XAResources={JM
S_FileStore, ccsDbPool, medMgmtDbPool, plcDbPool, JMS_jmsStore, pfDbPool, beneDbPool, cmsextDbPool,
pfuDbPool, pfcDbPool},NonXAResources={})],CoordinatorURL=ccsServer+141.177.53.164:7101+ccs+t3+): web
logic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3 - with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3]
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java
:1684)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.
java:311)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:228
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:320)
at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
Session_p1z9z7_EOImpl.java:56)
at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6985)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
92)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
.>
[FATAL] 2007-06-13 08:56:32,037 [ExecuteThread: '23' for queue: 'weblogic.kernel.Default'] com.foo
.ape.web.ReceiptHandlerServlet : ReceiptHandlerServlet caugh
t exception javax.transaction.TransactionRolledbackException Exception while commiting Tx : BEA1-003
60416CD7939F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123
seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3javax.transaction.TransactionRolledbackException: Exception while commiting
Tx : BEA1-00360416CD7939F523D3: weblogic.transaction.internal.TimedOutException: Transaction timed
out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
; nested exception is:
weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledback(EJBRuntimeUtils.java:2
02)
at weblogic.ejb20.internal.EJBRuntimeUtils.throwRemoteException(EJBRuntimeUtils.java:90)
at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:343)
at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:168)
at com.foo.ape.ejb.ReceiptHandlerSession_p1z9z7_EOImpl.handleEvent(ReceiptHandler
Session_p1z9z7_EOImpl.java:56)
at com.foo.ape.web.ReceiptHandlerServlet.doPost(ReceiptHandlerServlet.java:103)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.jav
a:1072)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:6985)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:38
92)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2766)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: weblogic.transaction.internal.TimedOutException: Transaction timed out after 123 seconds
BEA1-00360416CD7939F523D3
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:160
0)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(Se
rverTransactionManagerImpl.java:1147)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1
882)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManage
rImpl.java:1064)
at weblogic.transaction.internal.WLSTimer.trigger(WLSTimer.java:31)
at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
... 2 more

IIOP is Internet InterORB protocol. The standard from CORBA used for distributed objects communication. This indicates to you that under the covers ejb's use CORBA protocol (iiop). This is so to ensure interoperability between vendors & technologies that invoke distributed objects. t3 is weblogic proprietary. t3 stands fro tengah protocol. Again while using transactions over distributed middleware/over wire then weblogic or any other vendor support iiop over t3 etc. With iiop protocol you are always covered ( as it is industry standard ) while this may not be the case with t3.

Generics in EJBs - ejbc fails in 9.0b

Similar Messages

Maybe you are looking for