You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by BAnanth <bh...@wipro.com> on 2012/12/18 06:06:29 UTC
Camel Tracer Component - problem with persistence
Hello,
We are using the Tracer component in out project for monitoring and
resending the messages to specific end points.
The project is a WAR file that we are deploying in Jboss 7.1.1.Final server.
We are using Derby as the DB for persisting the trace messages.
*a. We have followed the same approach as shown in the camel tracer example.
(The tracer example is an OSGI bundle whereas ours is a WAR file). Upon
deploying
in Jboss we get the following error, (Note: we tested this in the tomcat-cfx
example that is a WAR
file)*----------------------------------------------------------------
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,012 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_fr.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,028 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_hu.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,044 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_it.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,044 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_ja_JP.jar in "/E:/prj/Softwares/jboss-as-7
.1.1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,044 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_ko_KR.jar in "/E:/prj/Softwares/jboss-as-7
.1.1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,044 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_pl.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_pt_BR.jar in "/E:/prj/Softwares/jboss-as-7
.1.1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,059 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_ru.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,075 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_zh_CN.jar in "/E:/prj/Softwares/jboss-as-7
.1.1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,090 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry derbyLocale_zh_TW.jar in "/E:/prj/Softwares/jboss-as-7
.1.1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/derbyclient-10.9.1.0.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,106 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry jaxb-api.jar in "/E:/prj/Softwares/jboss-as-7.1.1.Fina
l/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/jaxb-impl-2.2.5.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,106 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry activation.jar in "/E:/prj/Softwares/jboss-as-7.1.1.Fi
nal/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/jaxb-impl-2.2.5.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,106 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry jsr173_1.0_api.jar in "/E:/prj/Softwares/jboss-as-7.1.
1.Final/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/jaxb-impl-2.2.5.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,122 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7)
Class Path entry jaxb1-impl.jar in "/E:/prj/Softwares/jboss-as-7.1.1.Fi
nal/bin/content/camel-example-cxf-tomcat.war/WEB-INF/lib/jaxb-impl-2.2.5.jar"
does not point to a valid jar for a Class-Path reference.
10:23:31,137 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5)
JBAS015893: Encountered invalid class name 'org.springframework.context.A
pplicationContext,org.springframework.beans.BeansException' for service type
'org.apache.cxf.bus.factory'
10:23:31,137 INFO [org.jboss.as.jpa] (MSC service thread 1-5) JBAS011401:
Read persistence.xml for tracer
10:23:31,278 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006:
Not installing optional component org.apache.cxf.transport.http.Servlet3Cont
inuationProvider$Servlet3Continuation due to exception:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
JBAS011054: Could not find d
efault constructor for class
org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation
at
org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)
at
org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.1.Final.jar:7.1.1
.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_04]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_04]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
/10:23:31,512 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service
thread 1-6) JBAS010403: Deploying JDBC-compliant driver class
org.apache.derby
.jdbc.AutoloadedDriver (version 10.9)
10:23:31,512 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service
thread 1-6) JBAS010403: Deploying JDBC-compliant driver class
org.apache.derby
.jdbc.ClientDriver (version 10.9)/10:23:31,512 INFO [org.jboss.as.jpa] (MSC
service thread 1-3) JBAS011402: Starting Persistence Unit Service
'camel-example-cxf-tomcat.war#tracer'
10:23:31,512 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread
1-3) HHH000204: Processing PersistenceUnitInfo [
name: tracer
...]
10:23:31,590 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-3) HHH000402: Using Hib
ernate built-in connection pool (not for production use!)
10:23:31,590 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-3) HHH000115: Hibernate
connection pool size: 20
10:23:31,590 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-3) HHH000006: Autocommi
t mode: true
10:23:31,590 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-3) HHH000401: using dri
ver [org.apache.derby.jdbc.ClientDriver] at URL
[jdbc:derby://localhost:1527/prj_MESSAGETRACED]
10:23:31,590 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-3) HHH000046: Connectio
n properties: {autocommit=true, release_mode=auto}
10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-3) HHH000342: Could not obtain connection to query
meta
data : No suitable driver found for
jdbc:derby://localhost:1527/prj_MESSAGETRACED
10:23:31,605 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-3)
HHH000400: Using dialect: org.apache.camel.example.cxf.FixedDerbyDialect
10:23:31,605 WARN [org.hibernate.dialect.DerbyDialect] (MSC service thread
1-3) HHH000430: The DerbyDialect dialect has been deprecated; use one of t
he version-specific dialects instead
10:23:31,605 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder]
(MSC service thread 1-3) HHH000422: Disabling contextual LOB creation as con
nection was null
10:23:31,621 INFO
[org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC
service thread 1-3) HHH000268: Transaction strategy: o
rg.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
10:23:31,621 INFO
[org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service
thread 1-3) HHH000397: Using ASTQueryTranslatorFactory
10:23:31,636 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-3) HHH000227: Running hbm2ddl schema export
/10:23:31,652 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-3) HHH000231: Schema export unsuccessful: java.sql.SQLException: No
suitable driver found for jdbc:derby://localhost:1527/prj_MESSAGETRACED
at java.sql.DriverManager.getConnection(DriverManager.java:604)
[rt.jar:1.7.0_04]
at java.sql.DriverManager.getConnection(DriverManager.java:190)
[rt.jar:1.7.0_04]
at
/org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnection(DriverManagerConnectionProviderImpl.java:
173) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51)
[hibernat
e-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:52)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:305)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:294)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:452)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Fi
nal]
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Fi
nal]
at
org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
[hibernate-entitymanager-4.0.1.Fin
al.jar:4.0.1.Final]
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
[jboss-as-jpa-
7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
[jboss-as-jpa-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_04]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_04]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
10:23:31,714 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-3) HHH000230: Schema export complete
10:23:31,714 WARN [org.hibernate.internal.SessionFactoryImpl] (MSC service
thread 1-3) HHH000008: JTASessionContext being used with JDBCTransactionFa
ctory; auto-flush will not operate correctly with getCurrentSession()
10:23:31,730 INFO
[org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/camel-example-cxf-tomcat]]
(MSC service thread 1-2) Initializi
ng Spring root WebApplicationContext
10:23:31,746 INFO [org.springframework.web.context.ContextLoader] (MSC
service thread 1-2) Root WebApplicationContext: initialization started
10:23:31,761 INFO
[org.springframework.web.context.support.XmlWebApplicationContext] (MSC
service thread 1-2) Refreshing Root WebApplicationContext:
startup date [Tue Dec 18 10:23:31 IST 2012]; root of context hierarchy
10:23:31,792 INFO
[org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (MSC service
thread 1-2) Loading XML bean definitions from class pa
th resource [camel-config.xml]
10:23:31,902 INFO
[org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (MSC service
thread 1-2) Loading XML bean definitions from class pa
th resource [META-INF/cxf/cxf.xml]
10:23:32,837 INFO
[org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC
service thread 1-2) Overriding bean definition for bean
'traced': replacing [Generic bean: class
[org.apache.camel.spring.CamelEndpointFactoryBean]; scope=; abstract=false;
lazyInit=false; autowireMode=0;
dependencyCheck=0; autowireCandidate=true; primary=false;
factoryBeanName=null; factoryMethodName=null; initMethodName=null;
destroyMethodName=null] w
ith [Generic bean: class [org.apache.camel.spring.CamelEndpointFactoryBean];
scope=; abstract=false; lazyInit=false; autowireMode=0; dependencyCheck=0
; autowireCandidate=true; primary=false; factoryBeanName=null;
factoryMethodName=null; initMethodName=null; destroyMethodName=null]
10:23:33,134 INFO
[org.springframework.web.context.support.XmlWebApplicationContext] (MSC
service thread 1-2) Bean 'cxf' of type [class org.apache.cx
f.bus.spring.SpringBus] is not eligible for getting processed by all
BeanPostProcessors (for example: not eligible for auto-proxying)
10:23:33,149 INFO
[org.springframework.beans.factory.support.DefaultListableBeanFactory] (MSC
service thread 1-2) Pre-instantiating singletons in org
.springframework.beans.factory.support.DefaultListableBeanFactory@1cea54a:
defining beans [cxf,org.apache.cxf.bus.spring.BusWiringBeanFactoryPostProce
ssor,org.apache.cxf.bus.spring.Jsr250BeanPostProcessor,org.apache.cxf.bus.spring.BusExtensionPostProcessor,myRoutes,traced,template,consumerTemplate,c
amel-1:beanPostProcessor,camel-1,camelTracer,transactionTemplate,jpaTemplate,entityManagerFactory];
root of factory hierarchy
10:23:33,649 INFO [org.apache.camel.impl.converter.DefaultTypeConverter]
(MSC service thread 1-2) Loaded 182 type converters
10:23:33,649 INFO
[org.apache.camel.core.xml.AbstractCamelContextFactoryBean] (MSC service
thread 1-2) Using custom Tracer: Tracer
10:23:33,664 INFO
[org.springframework.orm.jpa.LocalEntityManagerFactoryBean] (MSC service
thread 1-2) Building JPA EntityManagerFactory for persiste
nce unit 'tracer'
10:23:34,132 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-2) HHH000402: Using Hib
ernate built-in connection pool (not for production use!)
10:23:34,132 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-2) HHH000115: Hibernate
connection pool size: 20
10:23:34,132 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-2) HHH000006: Autocommi
t mode: true
10:23:34,148 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-2) HHH000401: using dri
ver [org.apache.derby.jdbc.ClientDriver] at URL
[jdbc:derby://localhost:1527/prj_MESSAGETRACED]
10:23:34,148 INFO
[org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl]
(MSC service thread 1-2) HHH000046: Connectio
n properties: {autocommit=true, release_mode=auto}
10:23:34,163 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-2) HHH000342: Could not obtain connection to query
meta
data : No suitable driver found for
jdbc:derby://localhost:1527/prj_MESSAGETRACED
10:23:34,163 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-2)
HHH000400: Using dialect: org.apache.camel.example.cxf.FixedDerbyDialect
10:23:34,163 WARN [org.hibernate.dialect.DerbyDialect] (MSC service thread
1-2) HHH000430: The DerbyDialect dialect has been deprecated; use one of t
he version-specific dialects instead
10:23:34,163 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder]
(MSC service thread 1-2) HHH000422: Disabling contextual LOB creation as con
nection was null
10:23:34,163 INFO
[org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC
service thread 1-2) HHH000268: Transaction strategy: o
rg.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
10:23:34,163 INFO
[org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service
thread 1-2) HHH000397: Using ASTQueryTranslatorFactory
10:23:34,241 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-2) HHH000227: Running hbm2ddl schema export
10:23:34,241 ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-2) HHH000231: Schema export unsuccessful: java.sql.SQLException: No
suitable driver found for jdbc:derby://localhost:1527/prj_MESSAGETRACED
at java.sql.DriverManager.getConnection(DriverManager.java:604)
[rt.jar:1.7.0_04]
at java.sql.DriverManager.getConnection(DriverManager.java:190)
[rt.jar:1.7.0_04]
at
org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnection(DriverManagerConnectionProviderImpl.java:
173) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.prepare(SuppliedConnectionProviderConnectionHelper.java:51)
[hibernat
e-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.DatabaseExporter.<init>(DatabaseExporter.java:52)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.execute(SchemaExport.java:368)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:305)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.tool.hbm2ddl.SchemaExport.create(SchemaExport.java:294)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:452)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737)
[hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Fi
nal]
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)
[hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Fi
nal]
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:56)
[hibernate-entitymanager-4.0.1.Final.jar:4.
0.1.Final]
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:63)
[hibernate-jpa-2.0-api-1.0.1.Final.jar:1.0.1.Final]
at
org.springframework.orm.jpa.LocalEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalEntityManagerFactoryBean.java:92)
[spring-o
rm-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:310)
[spring-orm-3.0.
7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1479
) [spring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1419)
[
spring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:518)
[spr
ing-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
[sprin
g-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
[spring-beans-3.0.7.RELEASE.jar:3.0
.7.RELEASE]
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
[spring-beans-3.
0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
[spring-beans-3.0.7.RELEASE.jar:3.0.7
.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
[spring-beans-3.0.7.RELEASE.jar:3.0.7.R
ELEASE]
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
[spring-beans-
3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
[spring
-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:13
27) [spring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
[sp
ring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
[spr
ing-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
[sprin
g-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:270)
[spring-beans-
3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:120)
[spring
-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:13
27) [spring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1085)
[sp
ring-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:516)
[spr
ing-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:455)
[sprin
g-beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
[spring-beans-3.0.7.RELEASE.jar:3.0
.7.RELEASE]
at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
[spring-beans-3.
0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
[spring-beans-3.0.7.RELEASE.jar:3.0.7
.RELEASE]
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
[spring-beans-3.0.7.RELEASE.jar:3.0.7.R
ELEASE]
at
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
[spring-
beans-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
[spring
-context-3.0.7.RELEASE.jar:3.0.7.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
[spring-context-3.0.7.RELEASE.j
ar:3.0.7.RELEASE]
at
org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:282)
[spring-web-3.0.7.RELEASE.jar:3.0.7.RELEA
SE]
at
org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:204)
[spring-web-3.0.7.RELEASE.jar:3.0.7.RELEASE
]
at
org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
[spring-web-3.0.7.RELEASE.jar:3.0.7
.RELEASE]
at
org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392)
[jbossweb-7.0.13.Final.jar:]
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3850)
[jbossweb-7.0.13.Final.jar:]
at
org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90)
[jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
[rt.jar:1.7.0_04]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
[rt.jar:1.7.0_04]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_04]
10:23:34,460 INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service
thread 1-2) HHH000230: Schema export complete
10:23:34,475 INFO [org.apache.camel.spring.SpringCamelContext] (MSC service
thread 1-2) Apache Camel 2.10.0 (CamelContext: camel-1) is starting
10:23:34,475 INFO [org.apache.camel.spring.SpringCamelContext] (MSC service
thread 1-2) Tracing is enabled on CamelContext: camel-1
10:23:34,491 INFO [org.apache.camel.management.ManagementStrategyFactory]
(MSC service thread 1-2) JMX enabled.
10:23:34,491 INFO
[org.apache.camel.management.DefaultManagementLifecycleStrategy] (MSC
service thread 1-2) StatisticsLevel at All so enabling load p
erformance statistics
10:23:34,569 INFO [org.apache.camel.component.jpa.JpaComponent] (MSC
service thread 1-2) Using EntityManagerFactory found in registry with id
[entity
ManagerFactory]
org.springframework.orm.jpa.LocalEntityManagerFactoryBean@b3820d
10:23:34,569 INFO [org.apache.camel.component.jpa.JpaComponent] (MSC
service thread 1-2) Using TransactionManager found in registry with id
[transact
ionTemplate] org.springframework.orm.jpa.JpaTransactionManager@11f4eec
10:23:34,584 INFO [org.apache.camel.spring.SpringCamelContext] (MSC service
thread 1-2) Total 0 routes, of which 0 is started.
10:23:34,584 INFO [org.apache.camel.spring.SpringCamelContext] (MSC service
thread 1-2) Apache Camel 2.10.0 (CamelContext: camel-1) started in 0.109
seconds
10:23:34,584 INFO [org.springframework.web.context.ContextLoader] (MSC
service thread 1-2) Root WebApplicationContext: initialization completed in
28
38 ms
10:23:34,787 INFO [org.jboss.web] (MSC service thread 1-2) JBAS018210:
Registering web context: /camel-example-cxf-tomcat
10:23:35,427 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1)
JBAS018559: Deployed "camel-example-cxf-tomcat.war"
----------------------------------------------------------------------------------------------------------------------------------------------------
The configurations are as follows,
*i.camel-config*<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:camel="http://camel.apache.org/schema/spring"
xmlns:cxf="http://camel.apache.org/schema/cxf"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd">
<import resource="classpath:META-INF/cxf/cxf.xml"/>
<bean id="myRoutes" class="org.apache.camel.example.cxf.CamelRoute"/>
<camelContext xmlns="http://camel.apache.org/schema/spring">
<endpoint id="traced"
uri="jpa://org.apache.camel.processor.interceptor.jpa.JpaTraceEventMessage?persistenceUnit=tracer"/>
</camelContext>
<bean id="camelTracer"
class="org.apache.camel.processor.interceptor.Tracer">
<property name="useJpa" value="true"/>
<property name="destination" ref="traced"/>
<property name="logLevel" value="OFF"/>
</bean>
<bean id="transactionTemplate"
class="org.springframework.transaction.support.TransactionTemplate">
<property name="transactionManager">
<bean class="org.springframework.orm.jpa.JpaTransactionManager">
<property name="entityManagerFactory" ref="entityManagerFactory"/>
</bean>
</property>
</bean>
<bean id="jpaTemplate" class="org.springframework.orm.jpa.JpaTemplate">
<property name="entityManagerFactory" ref="entityManagerFactory"/>
</bean>
<bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalEntityManagerFactoryBean">
<property name="persistenceUnitName" value="tracer"/>
</bean>
</beans>
*ii. persistence.xml*
<?xml version="1.0" encoding="UTF-8"?>
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1.0">
<persistence-unit name="tracer" transaction-type="RESOURCE_LOCAL">
<class>org.apache.camel.processor.interceptor.jpa.JpaTraceEventMessage</class>
<properties>
<property name="hibernate.dialect"
value="org.apache.camel.example.cxf.FixedDerbyDialect"/>
<property name="hibernate.connection.driver_class"
value="org.apache.derby.jdbc.ClientDriver"/>
<property name="hibernate.connection.url"
value="jdbc:derby://localhost:1527/prj_MESSAGETRACED"/>
<property name="hibernate.hbm2ddl.auto" value="create"/>
<property name="hibernate.show_sql" value="true"/>
<property name="hibernate.format_sql" value="true"/>
</properties>
</persistence-unit>
</persistence>
*b. In one of the hibernate forums it was mentioned that Spring 3 would be
compatible with Hibernate 3. We deployed Hibernate 3 jas as a module in
Jboss - forcing
our application to use Hibernate 3.6.6 Final. Even with that we are getting
the same exception.
c. We also tried defining a derby-ds.xml (placing the same in Web-INF). Now
the exception we are getting is somewhat different. Refer the same
below.*17:36:30,965 INFO [org.jboss.as.connector.deployers.jdbc] (MSC
service thread 1-8) JBAS010403: Deploying JDBC-compliant driver class
org.apache.derby
.jdbc.AutoloadedDriver (version 10.9)
17:36:30,981 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service
thread 1-8) JBAS010403: Deploying JDBC-compliant driver class
org.apache.derby
.jdbc.ClientDriver (version 10.9)
17:36:31,261 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC
service thread 1-8) Add Service
id=com.company.prj.usecase.enricher.EnrichmentEndpointImpl
address=http://localhost:8080/camel-prj-usecase/EnrichmentEndpointService
implementor=com.company.prj.usecase.enricher.EnrichmentEndpointImpl
invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
serviceName={http://enricher.usecase.prj.company.com}EnrichmentEndpointService
portName={http://enricher.usecase.prj.company.com}EnrichmentService
wsdlLocation=null
mtomEnabled=false
17:36:31,308 INFO
[org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service
thread 1-8) Creating Service {http://enricher.usecase.is
ova.company.com}EnrichmentEndpointService from class
com.company.prj.usecase.enricher.EnrichmentEndpoint
17:36:31,417 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread
1-8) Setting the server's publish address to be http://localhost:8080/came
l-prj-usecase/EnrichmentEndpointService
17:36:31,511 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher]
(MSC service thread 1-8) WSDL published to: file:/E:/prj/Softwares/jboss-a
s-7.1.1.Final/standalone/data/wsdl/camel-prj-usecase.war/EnrichmentEndpointService.wsdl
17:36:31,527 INFO [org.jboss.as.webservices] (MSC service thread 1-2)
JBAS015539: Starting service jboss.ws.port-component-link
17:36:31,527 INFO [org.jboss.as.webservices] (MSC service thread 1-2)
JBAS015539: Starting service
jboss.ws.endpoint."camel-prj-usecase.war"."com.w
ipro.prj.usecase.enricher.EnrichmentEndpointImpl"
17:36:31,542 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry]
(MSC service thread 1-2) register: jboss.ws:context=camel-prj-usecase,en
dpoint=com.company.prj.usecase.enricher.EnrichmentEndpointImpl
17:36:31,761 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1)
JBAS015870: Deploy of deployment "camel-prj-usecase.war" was rolled back wi
th failure message {"JBAS014771: Services with missing/unavailable
dependencies" =>
["jboss.persistenceunit.\"camel-prj-usecase.war#tracer\"jboss.na
ming.context.java.jboss.datasources.derbyDSMissing[jboss.persistenceunit.\"camel-prj-usecase.war#tracer\"jboss.naming.context.java.jboss.datasources
.derbyDS]"]}
17:36:31,761 INFO [org.jboss.as.webservices] (MSC service thread 1-6)
JBAS015540: Stopping service
jboss.ws.endpoint."camel-prj-usecase.war"."com.w
ipro.prj.usecase.enricher.EnrichmentEndpointImpl"
17:36:31,776 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry]
(MSC service thread 1-6) remove: jboss.ws:context=camel-prj-usecase,endp
oint=com.company.prj.usecase.enricher.EnrichmentEndpointImpl
17:36:31,792 INFO [org.jboss.as.webservices] (MSC service thread 1-7)
JBAS015540: Stopping service jboss.ws.port-component-link
17:36:37,377 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5)
JBAS015877: Stopped deployment camel-prj-usecase.war in 5622ms
17:36:37,377 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1)
JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.jboss.datasources.derbyDS (missing)
dependents: [service jboss.persistenceunit."camel-prj-usecase.war#tracer
"]
17:36:37,392 ERROR [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and
was rolled ba
ck. Steps that failed:" => {"Operation step-2" => {"JBAS014771: Services
with missing/unavailable dependencies" =>
["jboss.persistenceunit.\"camel-iso
va-usecase.war#tracer\"jboss.naming.context.java.jboss.datasources.derbyDSMissing[jboss.persistenceunit.\"camel-prj-usecase.war#tracer\"jboss.naming
.context.java.jboss.datasources.derbyDS]"]}}}
Thanks and Regards,
Bhavani
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
Hi,
I tried using the camel-jboss component also. Still no luck!
Any pointers would be helpful.
Regards,
Bhavani
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724601.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
Hi Guru
I have added persistence to the exiting cameml-cxf-tomcat example(this is a
WAR file). I have added the necessary dependencies in pom.xml also. The
derby jars are avaiable in web-inf/lib. Still the error is persisting.
Any pointers would be most helpful.
Thanks and Regards,
Bhavani
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724280.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by Christian Müller <ch...@gmail.com>.
Is it possible to share the WAR file?
I cannot imagine why the JBoss do not find the derby database driver if
it's present...
In the passed we had problems running Camel in JBoss which is the reason
why we created the camel-jboss component [1]. But this should not be
required with the newer Camel versions.
[1] http://camel.apache.org/camel-jboss.html
Best,
Christian
On Wed, Dec 19, 2012 at 6:54 AM, BAnanth <bh...@wipro.com> wrote:
> Hi Christian,
>
> That is exactly the issue. The derby jars are available in the Web-Inf/lib
> directory but somehow not getting recognized.
>
> In the camel-cxf-tomacat example, we had tried adding tracer. It gave the
> same exception.
>
> Any pointers would be helpful.
>
> Thank and Regards,
> Bhavani
>
>
>
>
> From: Christian Mueller [via Camel] [mailto:
> ml-node+s465427n5724304h8@n5.nabble.com]
> Sent: Wednesday, December 19, 2012 12:36 AM
> To: Bhavani Ananth (WT01 - BAS)
> Subject: Re: Camel Tracer Component - problem with persistence
>
> For me, it looks like something is wrong with your WAR. I assume the derby
> database driver is not found:
>
> 10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
> (MSC service thread 1-3) HHH000342: Could not obtain connection to query
> metadata : No suitable driver found for
> jdbc:derby://localhost:1527/prj_MESSAGETRACED
>
> Best,
> Christian
>
> On Tue, Dec 18, 2012 at 6:06 AM, BAnanth <[hidden
> email]</user/SendEmail.jtp?type=node&node=5724304&i=0>> wrote:
>
> > 10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
> > (MSC service thread 1-3) HHH000342: Could not obtain connection to query
> > meta
> > data : No suitable driver found for
> > jdbc:derby://localhost:1527/prj_MESSAGETRACED
> >
>
>
>
> --
>
> ________________________________
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724304.html
> To unsubscribe from Camel Tracer Component - problem with persistence,
> click here<
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5724262&code=YmhhdmFuaS5hbmFudGhAd2lwcm8uY29tfDU3MjQyNjJ8MTk0MzU5ODk5NQ==
> >.
> NAML<
> http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
>
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you are
> not the intended recipient, you should not disseminate, distribute or copy
> this e-mail. Please notify the sender immediately and destroy all copies of
> this message and any attachments.
>
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>
> www.wipro.com
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724343.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
RE: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
Hi Christian,
That is exactly the issue. The derby jars are available in the Web-Inf/lib directory but somehow not getting recognized.
In the camel-cxf-tomacat example, we had tried adding tracer. It gave the same exception.
Any pointers would be helpful.
Thank and Regards,
Bhavani
From: Christian Mueller [via Camel] [mailto:ml-node+s465427n5724304h8@n5.nabble.com]
Sent: Wednesday, December 19, 2012 12:36 AM
To: Bhavani Ananth (WT01 - BAS)
Subject: Re: Camel Tracer Component - problem with persistence
For me, it looks like something is wrong with your WAR. I assume the derby
database driver is not found:
10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-3) HHH000342: Could not obtain connection to query
metadata : No suitable driver found for
jdbc:derby://localhost:1527/prj_MESSAGETRACED
Best,
Christian
On Tue, Dec 18, 2012 at 6:06 AM, BAnanth <[hidden email]</user/SendEmail.jtp?type=node&node=5724304&i=0>> wrote:
> 10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
> (MSC service thread 1-3) HHH000342: Could not obtain connection to query
> meta
> data : No suitable driver found for
> jdbc:derby://localhost:1527/prj_MESSAGETRACED
>
--
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724304.html
To unsubscribe from Camel Tracer Component - problem with persistence, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5724262&code=YmhhdmFuaS5hbmFudGhAd2lwcm8uY29tfDU3MjQyNjJ8MTk0MzU5ODk5NQ==>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724343.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by Christian Müller <ch...@gmail.com>.
For me, it looks like something is wrong with your WAR. I assume the derby
database driver is not found:
10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
(MSC service thread 1-3) HHH000342: Could not obtain connection to query
metadata : No suitable driver found for
jdbc:derby://localhost:1527/prj_MESSAGETRACED
Best,
Christian
On Tue, Dec 18, 2012 at 6:06 AM, BAnanth <bh...@wipro.com> wrote:
> 10:23:31,605 WARN [org.hibernate.engine.jdbc.internal.JdbcServicesImpl]
> (MSC service thread 1-3) HHH000342: Could not obtain connection to query
> meta
> data : No suitable driver found for
> jdbc:derby://localhost:1527/prj_MESSAGETRACED
>
--
RE: Camel Tracer Component - problem with persistence
Posted by Gnanaguru S <gn...@wipro.com>.
Thanks Great to know !
Happy new year .
Regards
Guru
________________________________
From: BAnanth [via Camel] [ml-node+s465427n5724733h79@n5.nabble.com]
Sent: 31 December 2012 14:08:43
To: Gnanaguru Sattanathan (WT01 - BAS)
Subject: Re: Camel Tracer Component - problem with persistence
Hi,
For now , have made the tracer work in the WAR by making the following changes in Jboss,
a. Changed standalone.xml. The following lines were added,
<datasource jndi-name="java:jboss/datasources/derbyDS" pool-name="derbyDS" enabled="true" use-java-context="true">
<connection-url>jdbc:derby://localhost:1527/CAMEL_MESSAGETRACED</connection-url>
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<driver>derbyclient.jar</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>APP</user-name>
<password>APP</password>
</security>
</datasource>
<driver name="derbyclient.jar" module="org.apache.derby">
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<xa-datasource-class>org.apache.derby.jdbc.ClientXADataSource</xa-datasource-class>
</driver>
b. Derby was installed as a module in jboss so that it got loaded during startup.
i. Created a derby folder in jboss7.1.Final/modules/org/apache
ii. Created a main folder under derby
iii. Added derbyclient.jar in jboss7.1.Final/modules/org/apache/derby/main
iv. Added the module.xml with the following entry in jboss7.1.Final/modules/org/apache/derby/main folder
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.apache.derby">
<resources>
<resource-root path="derbyclient.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
</dependencies>
</module>
c. In camel-context, used the jta data source instead of the hibernate connection properties
<jta-data-source>java:jboss/datasources/derbyDS</jta-data-source>
Please do let me know if there is a better approach.
Thanks and Regards,
Bhavani
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724733.html
To unsubscribe from Camel Tracer Component - problem with persistence, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5724262&code=Z25hbmFndXJ1LnNhdHRhbmF0aGFuQHdpcHJvLmNvbXw1NzI0MjYyfDMwNzMwMjI2Mw==>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724735.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
Hi,
For now , have made the tracer work in the WAR by making the following
changes in Jboss,
a. Changed standalone.xml. The following lines were added,
/<datasource jndi-name="java:jboss/datasources/derbyDS" pool-name="derbyDS"
enabled="true" use-java-context="true">
<connection-url>jdbc:derby://localhost:1527/CAMEL_MESSAGETRACED</connection-url>
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<driver>derbyclient.jar</driver>
<pool>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>APP</user-name>
<password>APP</password>
</security>
</datasource>/
/<driver name="derbyclient.jar" module="org.apache.derby">
<driver-class>org.apache.derby.jdbc.ClientDriver</driver-class>
<xa-datasource-class>org.apache.derby.jdbc.ClientXADataSource</xa-datasource-class>
</driver>/
b. Derby was installed as a module in jboss so that it got loaded during
startup.
i. Created a derby folder in jboss7.1.Final/modules/org/apache
ii. Created a main folder under derby
iii. Added derbyclient.jar in jboss7.1.Final/modules/org/apache/derby/main
iv. Added the module.xml with the following entry in
jboss7.1.Final/modules/org/apache/derby/main folder
/<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.apache.derby">
<resources>
<resource-root path="derbyclient.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.transaction.api"/>
<module name="javax.servlet.api" optional="true"/>
</dependencies>
</module>/
c. In camel-context, used the jta data source instead of the hibernate
connection properties
/<jta-data-source>java:jboss/datasources/derbyDS</jta-data-source>/
Please do let me know if there is a better approach.
Thanks and Regards,
Bhavani
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724733.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by Gnanaguru S <gn...@wipro.com>.
Hello Bhavani,
I also face the same issue with this.
I used Camel-example-tracer. I replaced the in-memory hsql database
configuration with derby standalone in persistence.xml.
I suspect, the issue could be because of how you converted the osgi project
into the WAR/Web-App as you specified.
Please update this thread once if you find a solution.
Regards
Guru
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724263.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
Thanks Potus.
I will give it a try. I presume you are referring to camel-jboss component when you mention about jboss resolver.
I am using jboss 7.1.final.
Happy holidays to you too!.
Regards,
bhavani
________________________________________
From: pontus.ullgren [via Camel] [ml-node+s465427n5724449h3@n5.nabble.com]
Sent: Thursday, December 20, 2012 7:30 PM
To: Bhavani Ananth (WT01 - BAS)
Subject: Re: Camel Tracer Component - problem with persistence
My experience is that I have still had problems getting later versions
(2.9.x) working on JBoss 5.1.0.GA and JBoss 6.
So I still use the JBoss resolver to get things working.
But then again I've not put that much effort into finding the reason I
simply added the resolver and it started working.
Just my $0.02.
Happy holidays
// Pontus
On Thu, Dec 20, 2012 at 12:30 PM, BAnanth <[hidden email]</user/SendEmail.jtp?type=node&node=5724449&i=0>> wrote:
> camel-example-cxf-tomcat_-_tracer.zip
> <http://camel.465427.n5.nabble.com/file/n5724443/camel-example-cxf-tomcat_-_tracer.zip>
>
> Hi Christian,
>
> I am not able to upload the WAR file(size of the file is huge).
>
> I am however sending the entire source content as a Zip. This has to be put
> and extracted in the camel/examples folder and built. (Trust this is fine)
>
> We have tried o replicate the problem in camel-example-cxf-tomcat example.
>
>
> Thanks!.
>
> Regards,
> Bhavani
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724443.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
________________________________
If you reply to this email, your message will be added to the discussion below:
http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724449.html
To unsubscribe from Camel Tracer Component - problem with persistence, click here<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5724262&code=YmhhdmFuaS5hbmFudGhAd2lwcm8uY29tfDU3MjQyNjJ8MTk0MzU5ODk5NQ==>.
NAML<http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724482.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by Pontus Ullgren <ul...@gmail.com>.
My experience is that I have still had problems getting later versions
(2.9.x) working on JBoss 5.1.0.GA and JBoss 6.
So I still use the JBoss resolver to get things working.
But then again I've not put that much effort into finding the reason I
simply added the resolver and it started working.
Just my $0.02.
Happy holidays
// Pontus
On Thu, Dec 20, 2012 at 12:30 PM, BAnanth <bh...@wipro.com> wrote:
> camel-example-cxf-tomcat_-_tracer.zip
> <http://camel.465427.n5.nabble.com/file/n5724443/camel-example-cxf-tomcat_-_tracer.zip>
>
> Hi Christian,
>
> I am not able to upload the WAR file(size of the file is huge).
>
> I am however sending the entire source content as a Zip. This has to be put
> and extracted in the camel/examples folder and built. (Trust this is fine)
>
> We have tried o replicate the problem in camel-example-cxf-tomcat example.
>
>
> Thanks!.
>
> Regards,
> Bhavani
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724443.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Tracer Component - problem with persistence
Posted by BAnanth <bh...@wipro.com>.
camel-example-cxf-tomcat_-_tracer.zip
<http://camel.465427.n5.nabble.com/file/n5724443/camel-example-cxf-tomcat_-_tracer.zip>
Hi Christian,
I am not able to upload the WAR file(size of the file is huge).
I am however sending the entire source content as a Zip. This has to be put
and extracted in the camel/examples folder and built. (Trust this is fine)
We have tried o replicate the problem in camel-example-cxf-tomcat example.
Thanks!.
Regards,
Bhavani
--
View this message in context: http://camel.465427.n5.nabble.com/Camel-Tracer-Component-problem-with-persistence-tp5724262p5724443.html
Sent from the Camel - Users mailing list archive at Nabble.com.