RE: Camel Tracer Component - problem with persistence

[Gnanaguru S]

Thanks Great to know !

Happy new year .

Regards
Guru

From: BAnanth [via Camel] [ml-node+s465427n5724733...@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,


jdbc:derby://localhost:1527/CAMEL_MESSAGETRACED

org.apache.derby.jdbc.ClientDriver
derbyclient.jar

false
false
FailingConnectionOnly


APP
APP

  



org.apache.derby.jdbc.ClientDriver

org.apache.derby.jdbc.ClientXADataSource
 
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



  

  
  



  


c. In camel-context, used the jta data source instead of the hibernate 
connection properties
java:jboss/datasources/derbyDS

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

[BAnanth]

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,
/
   
jdbc:derby://localhost:1527/CAMEL_MESSAGETRACED
   
org.apache.derby.jdbc.ClientDriver
derbyclient.jar

false
false
   
FailingConnectionOnly


APP
APP

  /

/
   
org.apache.derby.jdbc.ClientDriver
   
org.apache.derby.jdbc.ClientXADataSource
 /
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

/

  

  
  



  
/

c.  In camel-context, used the jta data source instead of the hibernate
connection properties
/java:jboss/datasources/derbyDS/ 

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

[BAnanth]

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

[BAnanth]

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+s465427n572444...@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]> 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

[Pontus Ullgren]

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  wrote:
> 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

[BAnanth]

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

[Christian Müller]

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  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+s465427n572430...@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]> 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

[BAnanth]

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+s465427n572430...@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]> 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

[Christian Müller]

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  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

[BAnanth]

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

[Gnanaguru S]

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.