Re: Rollbacks at database level throws exception in Geronimo
Hi, I am using the provided TranQL connectors for the datasource and the problem I faced seemed to be connected with the TranQL connector which seems to be setting auto commit to true. I was asked to file a JIRA on this ( http://issues.apache.org/jira/browse/GERONIMO-2576). There have been not any responses to that and I also could not make any headway into the issue so far. Thanks and regards, Vimalan On 11/28/06, Meenakshi [EMAIL PROTECTED] wrote: Hi Arunanthisivam, Were you able to debug the problem? I am also facing a similar error wherein I have set autocommit to false in the application and I am using DB2 9.1 universal JDBC drivers...and I get the same error..as below: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. at com.ibm.db2.jcc.c.p.rollback(p.java:752) at com.ibm.db2.jcc.c.gc.rollback(gc.java:162) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanupTransactions (WSRdbManagedConnectionImpl.java:3663) at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.cleanup (WSRdbManagedConnectionImpl.java:3143) at com.ibm.ejs.j2c.MCWrapper.cleanup(MCWrapper.java:1416) at com.ibm.ejs.j2c.FreePool.returnToFreePool(FreePool.java:475) at com.ibm.ejs.j2c.PoolManager.release(PoolManager.java:1598) at com.ibm.ejs.j2c.MCWrapper.releaseToPoolManager(MCWrapper.java :2237) at com.ibm.ejs.j2c.LocalTransactionWrapper.afterCompletion (LocalTransactionWrapper.java:1228) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.informSynchronizations (LocalTranCoordImpl.java:1488) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.cleanup (LocalTranCoordImpl.java:1196) at com.ibm.ws.LocalTransaction.LocalTranCoordImpl.end (LocalTranCoordImpl.java:1301) at com.ibm.ejs.csi.TranStrategy.commit(TranStrategy.java:731) at com.ibm.ejs.csi.BeanManaged.postInvoke(BeanManaged.java:343) at com.ibm.ejs.csi.TransactionControlImpl.postInvoke (TransactionControlImpl.java:581) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3876) at com.ibm.ejs.container.EJSContainer.postInvoke (EJSContainer.java:3698) at com.ibm.websphere.startupservice.EJSRemoteStatefulAdminServiceStartup_36ac1ed1 . start(Unknown Source) at com.ibm.websphere.startupservice._AppStartUp_Stub.start (_AppStartUp_Stub.java:252) at com.ibm.ws.startupservice.StartBeanInfo.start (StartBeanInfo.java:287) at com.ibm.ws.startupservice.StartUpModule.appStart (StartUpModule.java:152) at com.ibm.ws.startupservice.StartUpApplication.start (StartUpApplication.java:105) at com.ibm.ws.startupservice.StartUpService.stateChanged (StartUpService.java:461) at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged (ApplicationMgrImpl.java:1247) at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent (DeployedApplicationImpl.java:1112) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:232) at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState (DeployedApplicationImpl.java:227) at com.ibm.ws.runtime.component.DeployedApplicationImpl.start (DeployedApplicationImpl.java:826) at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication (ApplicationMgrImpl.java:948) at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run (ApplicationMgrImpl.java:2114) at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run (WsComponentImpl.java:340) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1499) Please let me know if you got the solution to the problem. Thanks, Meenakshi
Rollbacks at database level throws exception in Geronimo
Hi, I am sending this mail again as no one has answered my previous mail, I am restating the problem I am facing and also have attached a sample to recreate the problem. I have a stateless session EJB which accesses a DB2 datasource created using the tranql generic connector. This uses the container managed transaction. I am also using the DB2 9.1 universal JDBC drivers. For methods dealing with datasource related operations I have set sessionContext.setRollBackOnly() within the catch block of SQLException.This throws exceptions when there have to be rollbacks at the database level. For example trying to insert a duplicate record throws the following exception:- com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10114][10307] Invalid operation: Explicit COMMIT or ROLLBACK is not allowed when in auto-commit mode. I have created an example to illustrate this and have attached the source with this mail. I think this is something related to Tranql. Is there any way to turn auto commit off? Can anyone please suggest a way around this? I have stuck with this for some time now. Thanks and regards, Vimalan SessionTestBean.java Description: Binary data SessionTestClient.java Description: Binary data SessionTestRemote.java Description: Binary data SessionTestRemoteHome.java Description: Binary data ?xml version=1.0 encoding=UTF-8? openejb-jar xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1; dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1; dep:moduleId dep:groupIdTest/dep:groupId dep:artifactIdTest/dep:artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies dep:dependency groupIdjdbc/groupId artifactIdTest/artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:dependency /dep:dependencies dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment enterprise-beans session ejb-nameSessionTestBean/ejb-name jndi-nameSessionTestBean/jndi-name resource-ref ref-nametestDataSource/ref-name resource-linkjdbc/Test/resource-link /resource-ref /session /enterprise-beans /openejb-jar ?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 display-nameTest/display-name enterprise-beans session description![CDATA[stateless test session bean]]/description ejb-nameSessionTestBean/ejb-name homecom.test.ejb.SessionTestRemoteHome/home remotecom.test.ejb.SessionTestRemote/remote ejb-classcom.test.ejb.SessionTestBean/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type resource-ref res-ref-nametestDataSource/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref /session /enterprise-beans assembly-descriptor method-permission description![CDATA[Method permission description]]/description unchecked/ method description![CDATA[Method permission for Session Test Bean]]/description ejb-nameSessionTestBean/ejb-name method-name*/method-name /method /method-permission container-transaction method ejb-nameSessionTestBean/ejb-name method-name*/method-name /method trans-attributeRequired/trans-attribute /container-transaction /assembly-descriptor /ejb-jar
tranql local connecter (unable to rollback as auto-commit is true)
Hi, I have a datasource (for DB2) that is created using the tranql-local-connecter (generic one, because the org.tranql.connector.db2.LocalMCF class for db2 is not bundled in the db2 binary). Anyway the problem I encounter is not related to this. It seems that tranql seems to be setting autocommit to true. This raises problems in my applcation as I have to rollback the operation on certain save operations for some objects based on some condition ( e.g duplicate). But since autocommit is set to true the DB2 driver (universal DB2 driver) is complaining that I cannot perform an explicit rollback. Is there any way around this? Being able to roll back the operation on database level is crtiticalto the application I am using. - Vimalan
problems when refering same local EJB in different dependent EARs
Hi,I am running into some problems in the following scenario. I am deploying two different EARs in which among other EJBs there is the same local EJB (same class). Only the JNDI name of this local EJB differs in these EARs. I am able to refer to the correct local EJB in the second EAR by using ejb-ref and the JNDI name in other application servers (namely WebSphere) and this works fine. But the problem in Geronimo is that I have to make the second EAR dependant on the first EAR as the second EAR is dependent on some artifacts in the first EAR. Now whenever I try to refer to the local EJB in the second EAR, the EJB that gets looked up is the local EJB from the first EAR. Even when I have changed the ejbname of the local EJB in the second EAR and reflected that change in the ejb-link, the EJB that keeps getting looked up is the EJB from the first EAR. This causes some serious problems in the application as some initializations are going on in the child EAR that is not refletected in the EJB from the parent EAR that is getting called. Is there any way around this? I have attached a sample scenario with this, the local EJB only differs in the attached EARs slightly to display different messages to illustrate this scenario.This was tested in Geronimo 1.0 and 1.1.1. Thanks and regards,Vimalan helloworld1.ear Description: Binary data helloworld2.ear Description: Binary data
Re: Failure when looking up an EJB consecutively
Hi Lasantha,
I had a look at your example andit differs in the following. Setting up the initial context and lookup,narrowing, creationas well as the remote bean method invocation are all within the same loop, and also the home object is narrowed using
PortableRemoteObject.narrow. I am providing you with some sample code below. I suggest you modify your code as below to reproduce this error. (if it works the first time which I doubt, pleaserun again it will throw up the error). We are currently testing this on Geronimo
1.1.1.
for(int i=0;i1000;i++){ Properties properties = new Properties(); properties.setProperty(java.naming.factory.initial,org.openejb.client.RemoteInitialContextFactory);
properties.setProperty(java.naming.provider.url,127.0.0.1:4201); properties.setProperty(java.naming.security.principal,system);
properties.setProperty(java.naming.security.credentials,manager); try { InitialContext ic = new InitialContext(properties); Object o = ic.lookup
(SessionTestBean); SessionTestRemoteHome sessionTestRemoteHome = (SessionTestRemoteHome)PortableRemoteObject.narrow(o,SessionTestRemoteHome.class); SessionTestRemote sessionTestRemote =
sessionTestRemoteHome.create(); sessionTestRemote.display(); }catch(NamingException e) { e.printStackTrace(); } catch (RemoteException e) { e.printStackTrace
(); } catch (CreateException e) { e.printStackTrace(); } }
On 9/26/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote:
Hi Vimalan,I tested this problem with a 2000 consecutive requests in Geronimo v 1.1.1. But it doesn't happen to me at all. You can test it with the EJB samples application in
http://cwiki.apache.org/GMOxDOC11/ejb-sample-application.html replacing following files. We might able to help you if you are more specific and share your code with us.
Regards,Lasantha Ranaweera
Arunanthisivam Vimalathithen wrote:
Hi,
I am havinga problem inan application I am trying to port to WebSphere community edition which basically uses Geronimo 1.0 (This problem exists in the latest version of Geronimo (1.1.1)as well). The client I am using looks up the service numerous times consecutively and invokes the services. The problem happens when this has gone past more than 630 times, the client simply fails to look up and produces the following error:
java.rmi.RemoteException: Cannot access server: /127.0.0.1:4201 Exception: ; nested exception is:
java.io.IOException: Cannot access server: /127.0.0.1:4201 Exception: java.net.BindException
: Address already in use: connect
The same error can be produced by looking up and invoking a simple hello world EJB in a loop of 700 times. This happens in the latest release of Geronimo(sometimes the loop might need to be increased to 1000).Any work arounds to this?
Thanks and regards,
Vimalan
Re: Refering an EJB deployed in 2nd EAR
Hi Lasantha, What is the corresponding syntax for Geronimo 1.0? Thanks and regards, Vimalan On 9/26/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote: Hi Siraj,Yes it is the problem. When I add the dependencies to the geronimo-application.xml I can deploy two EARs without any error. Please find the attached geronimo-application.xml of helloworld1.ear. Regards,Lasantha RanaweeraSiraj Mohamed wrote: Hi, I am attaching two ears. Thanks, Siraj -Original Message- From: Lasantha Ranaweera [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 26, 2006 3:17 PM To: user@geronimo.apache.org Subject: Re: Refering an EJB deployed in 2nd EAR Hi, I think in your first openejb-jar.xml (HelloWorld1) you haven't mention the dependency of HelloWorld2. Post your two ears if you can't find the problem still. Regards, Lasantha Ranaweera Siraj Mohamed wrote: Hi, I tried it out in G 1.1.1 version but it fails. I have two EAR applications (say helloworld1.ear and helloworld2.ear) and I refer hellword2 ejb in helloworld1 ejb. This is helloworld1 ejb's openejb-jar.xml looks like. ?xml version=1.0 encoding=UTF-8? openejb-jar xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1 dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1 dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdHelloBean1/dep:artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment enterprise-beans session ejb-nameHelloBean1/ejb-name jndi-nameejb/helloworld1/jndi-name ejb-ref ref-nameejb/helloworld2/ref-name ejb-linkHelloBean2/ejb-link /ejb-ref /session /enterprise-beans /openejb-jar And also this is the segment of the ejb-jar.xml of helloworld1 ejb. enterprise-beans session descriptionno description/description display-nameHelloBean1/display-name ejb-nameHelloBean1/ejb-name homeejb.helloworld1.HelloHome1/home remoteejb.helloworld1.Hello1/remote ejb-classejb.helloworld1.HelloBean1/ejb-class session-typeStateless/session-type transaction-typeContainer/transaction-type ejb-ref id=EJBRemoteRef_1 ejb-ref-nameejb/helloworld2/ejb-ref-name ejb-ref-typeSession/ejb-ref-type homeejb.helloworld2.HelloHome2/home remoteejb.helloworld2.Hello2/remote /ejb-ref /session /enterprise-beans This is helloworld2 ejb's openejb-jar.xml looks like. ?xml version=1.0 encoding=UTF-8? openejb-jar xmlns=http://www.openejb.org/xml/ns/openejb-jar-2.1 dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1 dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdHelloBean2/dep:artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment enterprise-beans session ejb-nameHelloBean2/ejb-name jndi-nameejb/helloworld2/jndi-name /session /enterprise-beans /openejb-jar I am getting following error when I tried to deploy helloworld1.ear, provided that helloworld2.ear has already been deployed. Deployment failed: Error processing 'remote' element for EJB Reference 'ejb/helloworld2' for module 'helloworld1-ejb.jar': Remote interface class not found: ejb.helloworld2.Hello2 This is my geronimo-application.xml for the helloworld1.ear ?xml version=1.0 encoding=UTF-8? application xmlns=http://geronimo.apache.org/xml/ns/j2ee/application-1.1 dep:environment xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.1 dep:moduleId dep:groupIddefault/dep:groupId dep:artifactIdHello1/dep:artifactId dep:version1.0/dep:version dep:typecar/dep:type /dep:moduleId
Re: Failure when looking up an EJB consecutively
Hi Lasantha,
I might be able to escape the initialization in an example as I have mentioned below, but in a production environment scenario where there is a factory whichinvokes the clientclass that doesthe property initialization within it andprovides access to the EJB thiswill not be practical at all. I also need the narrow because this application should run on other application servers other than Geronimo as well. This sample secenario works well without any errors in the other application servers. Is there any other way to avoid this?
Thanks and regards,
Vimalan
On 9/26/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote:
Hi Vimalan,I just tried to re generate your error in my machine with the attached sample application. Check out is it the same scenario as yours. But I couldn't regenerate your problem. It looks the Exception is a network related one. Also I would like to add some comments to this scenario too.
1. The spec says you should narrow, but when using the org.openejb.client.RemoteInitialContextFactory, you never have to. We use dynamic proxies which don't require narrowing. 2. You might be able to escape from this Exception if you take property initialization to the out side of for loop. I would think it would be more practical scenario.
Regards,Lasantha RanaweeraArunanthisivam Vimalathithen wrote:
Hi Lasantha,
I had a look at your example andit differs in the following. Setting up the initial context and lookup,narrowing, creationas well as the remote bean method invocation are all within the same loop, and also the home object is narrowed using
PortableRemoteObject.narrow. I am providing you with some sample code below. I suggest you modify your code as below to reproduce this error. (if it works the first time which I doubt, pleaserun again it will throw up the error). We are currently testing this on Geronimo
1.1.1.
for(int i=0;i1000;i++){ Properties properties = new Properties(); properties.setProperty(java.naming.factory.initial,org.openejb.client.RemoteInitialContextFactory);
properties.setProperty(java.naming.provider.url,127.0.0.1:4201); properties.setProperty
(java.naming.security.principal,system); properties.setProperty(java.naming.security.credentials,manager); try { InitialContext ic = new InitialContext(properties);
Object o = ic.lookup (SessionTestBean); SessionTestRemoteHome sessionTestRemoteHome = (SessionTestRemoteHome)PortableRemoteObject.narrow(o,SessionTestRemoteHome.class); SessionTestRemote sessionTestRemote =
sessionTestRemoteHome.create(); sessionTestRemote.display(); }catch(NamingException e) { e.printStackTrace(); } catch (RemoteException e) { e.printStackTrace
(); } catch (CreateException e) { e.printStackTrace(); } }
On 9/26/06, Lasantha Ranaweera [EMAIL PROTECTED]
wrote:
Hi Vimalan,I tested this problem with a 2000 consecutive requests in Geronimo v 1.1.1. But it doesn't happen to me at all. You can test it with the EJB samples application in
http://cwiki.apache.org/GMOxDOC11/ejb-sample-application.html replacing following files. We might able to help you if you are more specific and share your code with us.
Regards,Lasantha Ranaweera
Arunanthisivam Vimalathithen wrote:
Hi,
I am havinga problem inan application I am trying to port to WebSphere community edition which basically uses Geronimo 1.0 (This problem exists in the latest version of Geronimo (1.1.1)as well). The client I am using looks up the service numerous times consecutively and invokes the services. The problem happens when this has gone past more than 630 times, the client simply fails to look up and produces the following error:
java.rmi.RemoteException: Cannot access server: /127.0.0.1:4201 Exception: ; nested exception is:
java.io.IOException: Cannot access server: /127.0.0.1:4201 Exception: java.net.BindException
: Address already in use: connect
The same error can be produced by looking up and invoking a simple hello world EJB in a loop of 700 times. This happens in the latest release of Geronimo(sometimes the loop might need to be increased to 1000).Any work arounds to this?
Thanks and regards,
Vimalan
Failure when looking up an EJB consecutively
Hi, I am havinga problem inan application I am trying to port to WebSphere community edition which basically uses Geronimo 1.0 (This problem exists in the latest version of Geronimo (1.1.1)as well). The client I am using looks up the service numerous times consecutively and invokes the services. The problem happens when this has gone past more than 630 times, the client simply fails to look up and produces the following error: java.rmi.RemoteException: Cannot access server: /127.0.0.1:4201 Exception: ; nested exception is: java.io.IOException: Cannot access server: /127.0.0.1:4201 Exception: java.net.BindException : Address already in use: connect The same error can be produced by looking up and invoking a simple hello world EJB in a loop of 700 times. This happens in the latest release of Geronimo(sometimes the loop might need to be increased to 1000).Any work arounds to this? Thanks and regards, Vimalan
Re: Getting a reference to a remote EJB
Hi, Yes, I have done all this (parent ear being deployed and started, indicated as parent through the parent ID, etc) and experimented with the EJb syntax as well, but all of that does not seem to be working. - Vimalan On 9/5/06, Kanchana Welagedara [EMAIL PROTECTED] wrote: If you want to set EAR one to be a parent of (G 1.0) or dependency of (G 1.1)EAR two. That should ensure that EAR one is started first and that theEJB classes in EAR one are exposed to the components running in EAR two.So the first step is to configure the parent or dependency tomake sure the classes are there, did u do more experimentation to get the EJB reference syntax right. On 9/5/06, Lasantha Ranaweera [EMAIL PROTECTED] wrote: Hi Vimalan,This is a problem in the Geronimo 1.1 version. According to the community it did work for Geronimo 1.0 and not with 1.1. They are hoping to fix this issue in v 1.1.1 . If I am wrong hope somebody in community will correct me.I haven't come across version as you mentioned in Geronimo. Can you please explain how did you get this version of Geronimo ?Regards,Lasantha Ranaweera Arunanthisivam Vimalathithen wrote: Hi Lasantha, Many thanksfor your feedback on the MDB problem. I hope you can provide me insight to another problem I am facing. I need to get a reference to a remote EJB deployed in one EAR from another EJB deployed in another EAR. I have tried adding a target-name tag in the ejb-ref tag in the openejb-jar.xml and refered to the GBean to identify the EJB but that also fails. However deployment proceeds properly if I pakage the jar containing the EJB in the same EAR. I am using geronimo 1.0.1.2 . Thanks and regards, Vimalan
MDB deployment problems
Hi, I am trying to deploy an EAR containing MDB I have deployed a JMS resource (ActiveMQ RAR) seperately. But when I deploy the MDB (parentId in openejb-jar.xml for MDB refers to deployed JMS resource),I get an java.lang.ClassNotFoundException : org.activemq.ra.ActiveMQActivationSpec error. Why is this? Does the JMS resource also have to deployed as part of the MDB ear? Thanks and regards, Vimalan
Re: Refering an EJB deployed in another EAR
Hi, I am using WebSphere Community Edition 1.0.1.2, what would the syntax look like here? Thanks and regards, - Vimalan On 8/29/06, David Jencks [EMAIL PROTECTED] wrote: The intention in g 1.1.1 is that if A is a dependency of B then anejb-link in B will find the appropriately named ejb in A.This is only likely to work if all ejbs have different names so you don'tneed the moduleLocation#ejbname syntax.I think I tested this, but it could still be broken despite my bestrecollections.thanks david jencksOn Aug 28, 2006, at 1:19 PM, Aaron Mulder wrote: Is this for Geronimo 1.0 or Geronimo 1.1?The bottom line is that you want to set EAR A to be a parent of (G 1.0) or dependency of (G 1.1) EAR B.That should ensure that EAR A is started first and that the EJB classes in EAR A are exposed to the components running in EAR B. There was a bug in G 1.1 (fixed in the upcoming G 1.1.1 ) that related to EJB references, but I don't remember whether it would impact this case.So the first step is to configure the parent or dependency to make sure the classes are there, and then we may need a little experimentation to get the EJB reference syntax right. Thanks,Aaron On 8/28/06, Arunanthisivam Vimalathithen [EMAIL PROTECTED] wrote: Hi, How can you refer an EJB that is deployed in another EAR. For example I have an EAR called ear a which contains an EJB ejb a, I want to refer this EJB from another EJB (ejb b) which is packaged and deployed in another EAR ear b. Currently I cannot seem to find any other way other than packaging ejb a in ear b as well. Is there any way to avoid this? Thanksa and regards, Vimalan.
Refering an EJB deployed in another EAR
Hi, How can you refer an EJB that is deployed in another EAR. For example I have an EAR calledear awhich contains an EJB ejb a, I want to refer this EJB from another EJB (ejb b) which is packaged and deployed in another EAR ear b. Currently I cannot seem to find any other way other than packaging ejb a in ear b as well. Is there any way to avoid this? Thanksa and regards, Vimalan.
