Hi, Thank you for your answer. I am very puzzled now. The version of servicemix and the version of ode is very important? And i tried many different ways to configure the servicemix and ode with mysql, it always doesn't work.
And before we use mysql, could we import the sql schema first? And this point is not resolved in user guide. Are the INTERNAL and EXTERNAL mode the same? Why did i configure servicemix according to the userguide, it threw exception? And there is also the same problem in the page http://www.nabble.com/Probleme-deployin-ODE-in-servicemix-td16480993.html#a16488059 my servicemix is apache-servicemix-3.2.2, my ode is ode-jbi-1.2.zip it threw these exceptions: Caught: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jndi ' defined in class path resource [jndi.xml]: Cannot resolve reference to bean 'jndiEntries' while se tting bean property 'entries'; nested exception is org.springframework.beans.factory.BeanCreationExc eption: Error creating bean with name 'jndiEntries': Cannot resolve reference to bean 'transactionMa nager' while setting bean property 'sourceMap' with key [TypedStringValue: value [javax.transaction. TransactionManager], target type [null]]; nested exception is org.springframework.beans.factory.Bean CreationException: Error creating bean with name 'transactionManager': FactoryBean threw exception o n object creation; nested exception is java.lang.NoSuchMethodError: org.apache.geronimo.transaction. manager.GeronimoTransactionManager.<init>(ILorg/apache/geronimo/transaction/manager/XidFactory;Lorg/ apache/geronimo/transaction/manager/TransactionLog;Ljava/util/Collection;)V if i use servicemix3.1.2 and ode1.1 it also threw exceptions: java.sql.SQLException at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:61) at org.apache.ode.scheduler.simple.JdbcDelegate.getConnection(JdbcDelegate.java:254) at org.apache.ode.scheduler.simple.JdbcDelegate.guessDialect(JdbcDelegate.java:289) at org.apache.ode.scheduler.simple.JdbcDelegate.<init>(JdbcDelegate.java:78) at org.apache.ode.jbi.OdeLifeCycle.initBpelServer(OdeLifeCycle.java:207) at org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:115) at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.init(ComponentMBeanImpl.java:201) at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.doStart(ComponentMBeanImpl.java:28 7) at org.apache.servicemix.jbi.framework.ComponentMBeanImpl.start(ComponentMBeanImpl.java:216) at org.apache.servicemix.jbi.framework.InstallationService.install(InstallationService.java: 331) at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentSer vice.java:277) at org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeployment Service.java:646) at org.apache.servicemix.jbi.framework.AutoDeploymentService.access$200(AutoDeploymentServic e.java:62) at org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.jav a:606) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: javax.resource.ResourceException: The pooling strategy does not match the MatchManagedCon nections implementation. Please investigate and reconfigure this pool at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnect ion(SinglePoolConnectionInterceptor.java:105) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnect ion(AbstractSinglePoolConnectionInterceptor.java:78) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(Tran sactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(Transa ctionCachingInterceptor.java:95) at org.apache.geronimo.connector.outbound.ConnectionHandleInterceptor.getConnection(Connecti onHandleInterceptor.java:43) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java :39) at org.apache.geronimo.connector.outbound.ConnectionTrackingInterceptor.getConnection(Connec tionTrackingInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.allocateConnection(Abstr actConnectionManager.java:61) at org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:56) ... 15 more INFO - Runtime - Starting OpenJPA 0.9.7-incubating INFO - JDBC - OpenJPA will now connect to the database to attempt to dete rmine what type of database dictionary to use. To prevent this connection in the future, set your o penjpa.jdbc.DBDictionary configuration property to the appropriate value for your database (see the documentation for available values). ERROR - ComponentMBeanImpl - Could not start component Matthieu Riou-5 wrote: > > On Thu, Sep 25, 2008 at 2:05 AM, yebo <[EMAIL PROTECTED]> wrote: > >> >> Another question: >> I configure the ode-jbi.property "ode-jbi.db.mode=INTERNAL" it works, but >> i >> configure it "ode-jbi.db.mode=EXTERNAL", it doesn't work, why? >> > > In the external mode we lookup a datasource that must be configured in the > container. In the internal mode we create our own pool and connect > directly > to the database ourselves. So if your problem in external mode is probably > related to your datasource configuration in ServiceMix. > > For performance, the two first things (both documented in the user guide) > you should do are: > > * Deactivate the events generation, those can really create a lot of > data. > * See if you can run some of your processes in memory. This is > significantly faster. > > Cheers, > Matthieu > > >> >> >> >> yebo wrote: >> > >> > I configre the ode-jbi.property "ode-jbi.db.mode=INTERNAL" instead of >> > "ode-jbi.db.mode=EXTERNAL" >> > what is the difference between them? >> > and when i use loadrunner to test it, the performce is also not very >> good. >> > How should i configure it to impove the performace? >> > Is there any doc in detail? What i see it the ode-site some are not >> very >> > particular. >> > >> > Thank you very much. >> > >> > >> > >> > Matthieu Riou-5 wrote: >> >> >> >> On Mon, Sep 22, 2008 at 6:50 PM, yebo <[EMAIL PROTECTED]> wrote: >> >> >> >>> >> >>> There is another problem is that after i test the servicemix with ode >> >>> according to loadrunner with 10 vusers, i must delete all the >> directory >> >>> of >> >>> servicemix and use a clean new servicemix and then my application >> could >> >>> run >> >>> correctly, if i just delete the directory >> >>> apache-servicemix-3.2.2\data\smx\components\OdeBpelEngine the >> servicemix >> >>> could restart nomally, but my application could not run correctly, >> why? >> >>> >> >> >> >> You should upgrade by building the latest 1.X branch, you should get >> >> better >> >> results. Also I definitely not advise doing load testing on Derby, >> it's >> >> far >> >> too pessimistic. Use MySQL or Postgres. >> >> >> >> Matthieu >> >> >> >> >> >>> >> >>> Thank you very much. >> >>> >> >>> this is my application >> >>> >> >>> >> http://www.nabble.com/file/p19619923/CreateConference-sa-1.0-SNAPSHOT.zip >> >>> CreateConference-sa-1.0-SNAPSHOT.zip >> >>> http://www.nabble.com/file/p19619923/webservicegenerate.war >> >>> webservicegenerate.war >> >>> -- >> >>> View this message in context: >> >>> >> http://www.nabble.com/Problem-error-when-start-servicemix-with-ODE-tp19602756p19619923.html >> >>> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >>> >> >>> >> >> >> >> >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Problem-error-when-start-servicemix-with-ODE-tp19602756p19665706.html >> Sent from the Apache Ode User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Problem-error-when-start-servicemix-with-ODE-tp19602756p19670696.html Sent from the Apache Ode User mailing list archive at Nabble.com.
