RE: [JBoss-user] Re: "removing bean lock and it has tx set" - question
We are getting a similar error (see below) from a Stateless Session bean using JBoss 3.0.2. We are also using the "Required" transaction attribute. The error occurs after the following sequence of events: 1) create some data using entity beans, via a session facade 2) Shutdown JBoss 3) Restart JBoss 4) Remove the data using entity beans, via a session facade Are we possibly doing something wrong or is this related to the same bug? Regards Chris This is the error message: 2002-10-10 14:37:50,699 ERROR [com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean] Failed due to remote exception removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; nested exception is: javax.ejb.TransactionRolledbackLocalException: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set! javax.transaction.TransactionRolledbackException: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; nested exception is: javax.ejb.TransactionRolledbackLocalException: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set!; CausedByException is: removing bean lock and it has tx set! at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:230) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:178) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:60) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:203) at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313) at org.jboss.ejb.Container.invoke(Container.java:720) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:111) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) at $Proxy61.removeJob(Unknown Source) at com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean.clearCache(ERPTestManagerBean.java:661) at com.yambay.mdrover.erp.proxy.session.ERPTestManagerBean.runTestCase ... -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Friday, 11 October 2002 7:40 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Re: "removing bean lock and it has tx set" - question Hi Michael, I've applied the fix to the 2.4 branch. Regards, Adrian >From: Michael Rudorfer <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: [JBoss-user] Re: "removing bean lock and it has tx set" - question >Date: Fri, 11 Oct 2002 10:47:28 +0200 > >Did I get you right, Bill? > >You think that this is a bug in Jboss, not a problem with >me, using transactions in a wrong way? > >Michael > >Bill Burke wrote: > > > Can you log a bug on this, copy this email, and assign to me? > > > > patriot1burke > > > > Thanks, > > > > Bill > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of Michael > > > Rudorfer > > > Sent: Thursday, October 10, 2002 11:38 AM > > > To: [EMAIL PROTECTED] > > > Subject: [JBoss-user] "removing bean lock and it has tx set" - >question > > > > > > > > > Hi there! > > > > > > I have the following problem: > > > > > > I am using Jboss 2.4.6 with CMP (jaws) and Container > > > Managed Transaction. > > > I have a Stateful Session bean with a bussiness method, > > > that utilizes entity beans. The transaction type of that bussiness > > > method is set to "required". When there are many entity beans > > > to be accessed, jboss crashes with the follwing error message: > > > > > > [16:22:34,047,AttributeDetailBean] TRANSACTION ROLLBACK EXCEPTION: > > > javax.transaction.TransactionRolledbackException: removing bean lock >and > > > it has tx set!; nested exception is: > > > java.lang.IllegalStateException: removi
RE: [JBoss-user] M-N relationship error -xdoclet
I believe you should be using relation rather than target-relation. target-relation is for uni-directional relationships where you need to specify both sides of the relationship on one getter method. Everything else looks ok to me. I am using m-n relationships with JBoss 3.0.2 and xdoclet 1.1.2 and it is working ok. Here are my xdoclet tags for an m-n relationship... /** * * @ejb:relation *name="Job-TechObject" *role-name="TechObject-has-many-Jobs" * * @jboss:relation *related-pk-field="id" *fk-column="JobId" * * @jboss:relation-table *table-name="Job_TechObject" * * @ejb:interface-method */ public abstract Collection getJobs(); /** * Retrieve the Collection of TechObjects that the Job involves. * For example, TechObjects to be inspected. * * @return Returns a Collection of TechObjectLocal (local interfaces * to TechObjects) that this Job involves. * * @ejb:relation *name="Job-TechObject" *role-name="Job-involves-many-TechObjects" * * @ejb:interface-method * * @jboss:relation *related-pk-field="id" *fk-column="TechObjectId" * * @jboss:relation-table *table-name="Job_TechObject" * **/ public abstract Collection getTechObjects(); Have a look at the xdcolet generated ejb-jar.xml and jbosscmp-jdbc.xml files and make sure that xdoclet is generating what you expect. Regards Chris -Original Message- From: Victor Batista [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 24 September 2002 5:19 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] M-N relationship error -xdoclet Hello! I am having problems while creating a M-N relationship using xdoclet. I am using jboss3.0.0 with bundled Tomcat 4.0.3. I am also using xdoclet 1.1.2. Do i need to get the latest xdcolet from CVS? I am getting the following exception for both roles: org.jboss.deployment.DeploymentException: Both roles of a relation-table mapped relationship must have key fields: ejb-relation-name=User-Role My xdoclet tags are: UserBean: # @ejb:relation name="User-Role" role-name="User-Has-Many-Roles" @jboss:relation-table table-name="xpto" @jboss:target-relation related-pk-field="id" fk-column="roleid" # where "id" is the name of the primary key on the Role bean and "roleid" is the name of the column in the relation table (xpto). RoleBean: # @ejb:relation name="User-Role" role-name="Role-Has-Many-Users" @jboss:relation-table table-name="xpto" create-table="true" remove-table="true" @jboss:target-relation related-pk-field="id" fk-column="userid" # where "id" is the name of the primary key on the User bean and "userid" is the name of the column in the relation table (xpto). I have tried with "jboss:relation" instead of "jboss:target-relation" but with the same results. Can any one help me, please? Thank you in advance, Victor Batista --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] MySql with Jboss 3.0.1
Title: MySql with Jboss 3.0.1 I am having problems deploying mysql-service.xml (MySql Datasource) using Jboss 3.0.1. This worked fine in 3.0.0, but now I get the folllowing error: I have attached the mysql-service.xml file. 05:00:51,079 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()' Cause: Incomplete Deployment listing: Packages waiting for a deployer: Incompletely deployed packages: MBeans waiting for classes: MBeans waiting for other MBeans: [ObjectName: jboss.jca:service=LocalTxCM,name=MySqlDS state: CONFIGURED I Depend On: jboss.jca:service=LocalTxDS,name=MySqlDS jboss.jca:service=LocalTxPool,name=MySqlDS jboss.jca:service=CachedConnectionManager jboss.security:name=JaasSecurityManager jboss.jca:service=RARDeployer Depends On Me: ] <> MySqlDS jdbc:mysql://localhost:3306/mDrover org.gjt.mm.mysql.Driver myusername mypassword jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper 0 50 5000 15 ByContainer jboss.jca:service=CachedConnectionManager jboss.security:name=JaasSecurityManager java:/TransactionManager jboss.jca:service=RARDeployer
RE: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0
Here you go David... Regards Chris -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Thursday, 15 August 2002 10:47 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0 Can you send me the (suitably de-password-ized) working config file so I can put it with our examples in cvs? Thanks! david jencks On 2002.08.14 19:54:55 -0400 Chris Pinfold wrote: > Yes, you were spot on David. The SAP Adapter was deployed under a > different name .. doh!. The Jetty problem I was getting was > because I had a distributable tag in my web.xml - although this > didn't cause a problem in 3.0.0. > > Anyway, thanks for all your help .. it is all working now. > > Cheers > Chris > > > -Original Message- > From: David Jencks [mailto:[EMAIL PROTECTED]] > Sent: Saturday, 10 August 2002 2:36 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0 > > > Is the SAP adapter itself deploying properly? this makes it look like it > isn't: > > ObjectName: jboss.jca:service=XaTxDS,name=SAPConnectorFactory > state: CONFIGURED > I Depend On: jboss.jca:service=RARDeployment,name=SAP R3 Connector > > Depends On Me: jboss.jca:service=XaTxCM,name=SAPConnectorFactory > ] > > Look on the jmx viewer for jboss.jca:service=RARDeployment,name=SAP R3 > Connector > > Don't know about the Jetty problem. > > david jencks > > On 2002.08.09 01:36:54 -0400 Chris Pinfold wrote: > > Thanks David. I have created a new sapr3-service.xml file based on > > the firebird-service.xml example, but I am still having a few > > problems (see below). > > > > I have attached, the sapr3-service.xml file, my jboss.xml and > ejb-jar.xml > > > > If I deploy to JBoss 3.0.0: > > 1) Deployment completes successfully, i.e. > > > > 05:16:31,053 INFO [MainDeployer] Successfully completed deployment of > > package: file:/C:/j2ee/jboss-3.0.0/server/default/conf/jboss-service.xml > > > > 2) When I run a test from a JSP page, I get the following error: > > > > 05:18:32,577 ERROR [MSapBean] Error processing request > > javax.naming.NameNotFoundException: R3ConnectionFactory not bound > > at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) > > at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) > > at org.jnp.server.NamingServer.getObject(NamingServer.java:509) > > at org.jnp.server.NamingServer.lookup(NamingServer.java:282) > > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:445) > > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) > > at javax.naming.InitialContext.lookup(InitialContext.java:347) > > at >com.yambay.mflim.sapadapter.ejb.MSapBean.executeBapiFunction(MSapBean.java:284) > > at com.yambay.mflim.sapadapter.ejb.MSapBean.getOrderList(MSapBean.java:119) > > 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:324) > > at >org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:664) > > at >org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186) > > at >org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) > > at >org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:144) > > at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62) > > at >org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) > > at >org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129) > > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) > > at >org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313) > > at org.jboss.ejb.Container.invoke(Container.java:705) > > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) > > at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) > > at >org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102) > > at >org.jboss.proxy.TransactionIntercepto
RE: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0
Yes, you were spot on David. The SAP Adapter was deployed under a different name .. doh!. The Jetty problem I was getting was because I had a distributable tag in my web.xml - although this didn't cause a problem in 3.0.0. Anyway, thanks for all your help .. it is all working now. Cheers Chris -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Saturday, 10 August 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0 Is the SAP adapter itself deploying properly? this makes it look like it isn't: ObjectName: jboss.jca:service=XaTxDS,name=SAPConnectorFactory state: CONFIGURED I Depend On: jboss.jca:service=RARDeployment,name=SAP R3 Connector Depends On Me: jboss.jca:service=XaTxCM,name=SAPConnectorFactory ] Look on the jmx viewer for jboss.jca:service=RARDeployment,name=SAP R3 Connector Don't know about the Jetty problem. david jencks On 2002.08.09 01:36:54 -0400 Chris Pinfold wrote: > Thanks David. I have created a new sapr3-service.xml file based on > the firebird-service.xml example, but I am still having a few > problems (see below). > > I have attached, the sapr3-service.xml file, my jboss.xml and ejb-jar.xml > > If I deploy to JBoss 3.0.0: > 1) Deployment completes successfully, i.e. > > 05:16:31,053 INFO [MainDeployer] Successfully completed deployment of > package: file:/C:/j2ee/jboss-3.0.0/server/default/conf/jboss-service.xml > > 2) When I run a test from a JSP page, I get the following error: > > 05:18:32,577 ERROR [MSapBean] Error processing request > javax.naming.NameNotFoundException: R3ConnectionFactory not bound > at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) > at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) > at org.jnp.server.NamingServer.getObject(NamingServer.java:509) > at org.jnp.server.NamingServer.lookup(NamingServer.java:282) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:445) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) > at javax.naming.InitialContext.lookup(InitialContext.java:347) > at >com.yambay.mflim.sapadapter.ejb.MSapBean.executeBapiFunction(MSapBean.java:284) > at com.yambay.mflim.sapadapter.ejb.MSapBean.getOrderList(MSapBean.java:119) > 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:324) > at >org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:664) > at >org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:186) > at >org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:96) > at >org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:144) > at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62) > at >org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) > at >org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:129) > at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166) > at >org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContainer.java:313) > at org.jboss.ejb.Container.invoke(Container.java:705) > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) > at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) > at >org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:102) > at >org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:73) > at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) > at >org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:111) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) > at $Proxy28.getOrderList(Unknown Source) > at org.apache.jsp.bapi$jsp._jspService(bapi$jsp.java:157) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at >org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201) > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) > at or
RE: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0
SARDeployer.java:249) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:796) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564) 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:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221) at org.jboss.Main.boot(Main.java:142) at org.jboss.Main$1.run(Main.java:375) at java.lang.Thread.run(Thread.java:536) 3) I also get the following error if I execute my test JSP... 05:05:57,161 ERROR [MarshallingInterceptor] could not get Attribute: msap java.io.InvalidClassException: org.mortbay.j2ee.session.SerializableEJBObject; local class incompatible: stream classdesc serialVersionUID = 9075948 9670159644, local class serialVersionUID = 9076021037437592860 at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:454) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1511) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1425) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1616) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1264) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:322) at org.mortbay.j2ee.session.MarshallingInterceptor.demarshal(MarshallingInterceptor.java:84) at org.mortbay.j2ee.session.MarshallingInterceptor.getAttribute(MarshallingInterceptor.java:93) at org.mortbay.j2ee.session.StateInterceptor.getAttribute(StateInterceptor.java:43) at org.mortbay.j2ee.session.StateInterceptor.getAttribute(StateInterceptor.java:43) at org.mortbay.j2ee.session.TypeCheckingInterceptor.getAttribute(TypeCheckingInterceptor.java:90) at org.mortbay.j2ee.session.StateAdaptor.getAttribute(StateAdaptor.java:204) at org.apache.jsp.connect$jsp._jspService(connect$jsp.java:128) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:201) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:381) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:473) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:344) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:313) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:554) at org.mortbay.jetty.servlet.WebApplicationHandler.handle(WebApplicationHandler.java:199) at org.mortbay.http.HttpContext.handle(HttpContext.java:1572) at org.mortbay.http.HttpContext.handle(HttpContext.java:1522) at org.mortbay.http.HttpServer.service(HttpServer.java:795) at org.jboss.jetty.Jetty.service(Jetty.java:531) at org.mortbay.http.HttpConnection.service(HttpConnection.java:784) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:941) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:799) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:186) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:322) at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:713) at java.lang.Thread.run(Thread.java:536) Regards Chris -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED]] Sent: Friday, 9 August 2002 1:25 AM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] SAP R/3 JCA connector and JBoss 3.0.0 I suggest you modify the firebird-service.xml example. If you can't get it to work quickly post what you have and I'll try to help. I recommend using 3.0.1 at least: start with the example config that comes with your download to get a compatible format. david jencks On 2002.08.08 02:43:16 -0400 Chris Pinfold wrote: > I am currently trying to port our project to jboss-3.0.0alpha to > jboss-3.0.0 (final release) and I am having trouble > getting our SAP R/3 Resource Adapter to deploy correctly. > > I am using the sapr3-service.xml
RE: [JBoss-user] SAP DB and JBoss
There is one in the docs/examples/jca directory in the 3.0.1 release (it was not in the 3.0.0) Regards Chris -Original Message- From: Sandor Arpa Sent: Friday, 9 August 2002 2:37 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] SAP DB and JBoss Howdy, is anybody out there who has experience and/or any idea on running JBoss 3.0 with the opensource SAP DB? Any suggestions where to find an example sapdb-service.xml file? Any idea or contribution will be greatly appreciated!! Cheers, Sandor Sandor Arpa Software Engineer Yambay Technologies tel: +61(0)2 9955 5300 mob: +61(0)414 663 091 web: www.yambay.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
