You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by bwtaylor <br...@yahoo.com> on 2009/06/20 04:52:37 UTC

camel:run JVM arguments

Is there an easy way to enable debugging or profiling while using the camel
maven plugin to do the camel:run goal? Or more generally, can I control the
jvm arguments that are passed to the java command?
-- 
View this message in context: http://www.nabble.com/camel%3Arun-JVM-arguments-tp24121531p24121531.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: camel:run JVM arguments

Posted by bwtaylor <br...@yahoo.com>.
Actually, the code is just fine. I'd just recommend documenting the features
a little better on your wiki. There actually are quite a few configuration
settings that'd be good to mention there. Basically, all the options of the 
http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html maven exec plugin 
are available, plus a few more that are camel specific. In particular, the 
http://camel.apache.org/debugger.html debug  and 
http://camel.apache.org/tracer.html trace  options that look useful.

For the benefit of anyone who stumbles upon this thread looking for
information, the 
https://svn.apache.org/repos/asf/camel/trunk/tooling/maven/camel-maven-plugin/src/main/java/org/apache/camel/maven/RunMojo.java
RunMojo.java source code  is pretty accessible. The main method invoked
defaults to 
https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/main/java/org/apache/camel/spring/Main.java
org.apache.camel.spring.Main , which extends 
https://svn.apache.org/repos/asf/camel/trunk/camel-core/src/main/java/org/apache/camel/impl/MainSupport.java
org.apache.camel.impl.MainSupport . So, you can always control everything by
launching from java via:
java org.apache.camel.spring.Main


willem.jiang wrote:
> 
> Thanks for sharing the information with the community.
> Please feel free to fill a JIRA[1] or submit a patch if you don't
> satisfy with current camel mvn plugin's implementation.
> 
> [1] https://issues.apache.org/activemq/browse/CAMEL
> 
> Willem
> 
> bwtaylor wrote:
>> I answered my own question. It looks like camel:run uses code similar to
>> the
>> maven exec plugin and so the answer is to use the shell environment
>> variable
>> MAVEN_OPTS to pass in JVM arguments. Interestingly, it appears that
>> camel:run is not forking a new JVM, but simply launching a new thread
>> within
>> the maven process.
>> 
>> Now if I can just figure out why TPTP is giving me "Could not find agent
>> library in absolute path" when I've got the right 64bit file on the path
>> to
>> match my 64 bit JVM. Baffling.
>> 
>> 
>> bwtaylor wrote:
>>> Is there an easy way to enable debugging or profiling while using the
>>> camel maven plugin to do the camel:run goal? Or more generally, can I
>>> control the jvm arguments that are passed to the java command?
>>>
>> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/camel%3Arun-JVM-arguments-tp24121531p24137987.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: camel:run JVM arguments

Posted by Willem Jiang <wi...@gmail.com>.
Thanks for sharing the information with the community.
Please feel free to fill a JIRA[1] or submit a patch if you don't
satisfy with current camel mvn plugin's implementation.

[1] https://issues.apache.org/activemq/browse/CAMEL

Willem

bwtaylor wrote:
> I answered my own question. It looks like camel:run uses code similar to the
> maven exec plugin and so the answer is to use the shell environment variable
> MAVEN_OPTS to pass in JVM arguments. Interestingly, it appears that
> camel:run is not forking a new JVM, but simply launching a new thread within
> the maven process.
> 
> Now if I can just figure out why TPTP is giving me "Could not find agent
> library in absolute path" when I've got the right 64bit file on the path to
> match my 64 bit JVM. Baffling.
> 
> 
> bwtaylor wrote:
>> Is there an easy way to enable debugging or profiling while using the
>> camel maven plugin to do the camel:run goal? Or more generally, can I
>> control the jvm arguments that are passed to the java command?
>>
> 


Re: camel:run JVM arguments

Posted by bwtaylor <br...@yahoo.com>.
I answered my own question. It looks like camel:run uses code similar to the
maven exec plugin and so the answer is to use the shell environment variable
MAVEN_OPTS to pass in JVM arguments. Interestingly, it appears that
camel:run is not forking a new JVM, but simply launching a new thread within
the maven process.

Now if I can just figure out why TPTP is giving me "Could not find agent
library in absolute path" when I've got the right 64bit file on the path to
match my 64 bit JVM. Baffling.


bwtaylor wrote:
> 
> Is there an easy way to enable debugging or profiling while using the
> camel maven plugin to do the camel:run goal? Or more generally, can I
> control the jvm arguments that are passed to the java command?
> 

-- 
View this message in context: http://www.nabble.com/camel%3Arun-JVM-arguments-tp24121531p24128096.html
Sent from the Camel - Users mailing list archive at Nabble.com.