[jira] Updated: (CAMEL-577) ResolverUtil can't resolve class under osgi enviroment

[ https://issues.apache.org/activemq/browse/CAMEL-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-577: -- Affects Version/s: 1.3.0 Component/s: camel-core ResolverUtil can't resolve class under

[jira] Resolved: (CAMEL-579) Allow custom registry to be defined in Spring Configuration

[ https://issues.apache.org/activemq/browse/CAMEL-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-579. --- Resolution: Fixed Applied patch with thanks (great work William) Allow custom registry to be

[jira] Commented: (CAMEL-573) Remove cycle between builder and impl

[ https://issues.apache.org/activemq/browse/CAMEL-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43246#action_43246 ] Christian Schneider commented on CAMEL-573: --- I think NoRouteBuilder is now in

[jira] Commented: (CAMEL-573) Remove cycle between builder and impl

[ https://issues.apache.org/activemq/browse/CAMEL-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43247#action_43247 ] Claus Ibsen commented on CAMEL-573: --- Deleting

Re: Compile error in camel-scala

Jon, The build works OK for me as well. We use the maven-scala-plugin to build our sources, which doesn't require you to set up anything special on your local machine. Could you try to an svn up to make sure you have the latest sources and retry the build with a mvn clean install to make

[jira] Created: (CAMEL-580) Velocity - reloading of vm from classpath

Velocity - reloading of vm from classpath - Key: CAMEL-580 URL: https://issues.apache.org/activemq/browse/CAMEL-580 Project: Apache Camel Issue Type: Improvement Components: camel-velocity

[jira] Resolved: (CAMEL-545) Camel public XSD is old

[ https://issues.apache.org/activemq/browse/CAMEL-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-545. Resolution: Fixed The scripts are committed into the

[jira] Closed: (CAMEL-6) add a CamelEndpointListener so you can listen to new endpoints being created/closed

[ https://issues.apache.org/activemq/browse/CAMEL-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-6. add a CamelEndpointListener so you can listen to new endpoints being created/closed

[jira] Closed: (CAMEL-5) add a CamelRouteListener to listen for routes being added/removed/stopped

[ https://issues.apache.org/activemq/browse/CAMEL-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-5. add a CamelRouteListener to listen for routes being added/removed/stopped

[jira] Closed: (CAMEL-284) add a JMX wiki page for how to work with JMX with Camel

[ https://issues.apache.org/activemq/browse/CAMEL-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-284. -- add a JMX wiki page for how to work with JMX with Camel

[jira] Closed: (CAMEL-361) @Component seems to cause configure() being called before @EndpointInject is invoked

[ https://issues.apache.org/activemq/browse/CAMEL-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-361. -- @Component seems to cause configure() being called before @EndpointInject is invoked

[jira] Closed: (CAMEL-479) Http Component needs to be able to make Http calls including POST/PUT/INFO/DELETE/GET to support REST endpoints.

[ https://issues.apache.org/activemq/browse/CAMEL-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-479. -- Http Component needs to be able to make Http calls including POST/PUT/INFO/DELETE/GET to support

[jira] Updated: (CAMEL-465) implement the camel spring integration component

[ https://issues.apache.org/activemq/browse/CAMEL-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-465: --- Summary: implement the camel spring integration component (was: impentent the camel spring

[jira] Closed: (CAMEL-464) write the document for how to use to the spring intergration component

[ https://issues.apache.org/activemq/browse/CAMEL-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-464. -- write the document for how to use to the spring intergration component

[jira] Closed: (CAMEL-436) typos in camel-cxf fixed

[ https://issues.apache.org/activemq/browse/CAMEL-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-436. -- typos in camel-cxf fixed Key: CAMEL-436

[jira] Closed: (CAMEL-434) Location of Spring and Camel configs should be configurable in Camel Maven Plugin

[ https://issues.apache.org/activemq/browse/CAMEL-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-434. -- Location of Spring and Camel configs should be configurable in Camel Maven Plugin

[jira] Closed: (CAMEL-562) camel-example-jms-file can't work within the Camel 1.4.0 snapshot

[ https://issues.apache.org/activemq/browse/CAMEL-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-562. -- camel-example-jms-file can't work within the Camel 1.4.0 snapshot

[jira] Closed: (CAMEL-575) Allow custom LifecycleStrategy to be defined in Spring configuration

[ https://issues.apache.org/activemq/browse/CAMEL-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-575. -- Allow custom LifecycleStrategy to be defined in Spring configuration

[jira] Closed: (CAMEL-568) CamelInvoker should set ExchangePattern according to the ServiceModel when use MESSAGE and PAYLOAD dataFormat

[ https://issues.apache.org/activemq/browse/CAMEL-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-568. -- CamelInvoker should set ExchangePattern according to the ServiceModel when use MESSAGE and PAYLOAD

[jira] Closed: (CAMEL-563) cxf name conflict in the spring context

[ https://issues.apache.org/activemq/browse/CAMEL-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-563. -- cxf name conflict in the spring context -

[jira] Closed: (CAMEL-512) Add the spring configuration support of the Camel JMX

[ https://issues.apache.org/activemq/browse/CAMEL-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-512. -- Add the spring configuration support of the Camel JMX

[jira] Closed: (CAMEL-574) Multicast default excecutor do not create the enough thread for parallel processing

[ https://issues.apache.org/activemq/browse/CAMEL-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang closed CAMEL-574. -- Multicast default excecutor do not create the enough thread for parallel processing

[jira] Assigned: (CAMEL-570) FTPComponent - Add delete/move operation

[ https://issues.apache.org/activemq/browse/CAMEL-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-570: - Assignee: Claus Ibsen FTPComponent - Add delete/move operation

[jira] Commented: (CAMEL-545) Camel public XSD is old

[ https://issues.apache.org/activemq/browse/CAMEL-545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43253#action_43253 ] Jonathan Anstey commented on CAMEL-545: --- Oh nice, I didn't even know we had this script

[jira] Work started: (CAMEL-580) Velocity - reloading of vm from classpath

[ https://issues.apache.org/activemq/browse/CAMEL-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-580 started by Claus Ibsen. Velocity - reloading of vm from classpath - Key: CAMEL-580

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: patch.txt Please review the attached patch. JMX Instrumentation - PerformanceCounter

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: jconsole.PNG Here is how it will look like. JMX Instrumentation - PerformanceCounter

[jira] Resolved: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hadrian Zbarcea resolved CAMEL-578. --- Fix Version/s: 1.4.0 Resolution: Fixed Excellent. Thanks for the patch William!

[jira] Resolved: (CAMEL-580) Velocity - reloading of vm from classpath

[ https://issues.apache.org/activemq/browse/CAMEL-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-580. --- Resolution: Fixed Improved the wiki documentation for velocity and stringtemplate as well.

[jira] Commented: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43281#action_43281 ] Claus Ibsen commented on CAMEL-578: --- William. I would have used System.currentTimeMillis

[jira] Reopened: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-578: --- JMX Instrumentation - PerformanceCounter - last processed timestamp

SpringDataSetTest failure on/off on Bamboo

Hi Why does the SpringDataSetTest fails once in a while on the Bamboo? It's a bit annoying. SpringDataSetTest : Run (testRun) History java.lang.AssertionError: dataset:foo Failed due to caught exception: java.lang.AssertionError: Header: camelDataSetIndex does not match. Expected: 9 but

[jira] Resolved: (CAMEL-581) CamelTemplate should clear endpoint cache when stopping

[ https://issues.apache.org/activemq/browse/CAMEL-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-581. --- Resolution: Fixed CamelTemplate should clear endpoint cache when stopping

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: millisec_patch.txt new patch that uses System.currentTimeMillis() to get time and fixes

[jira] Work started: (CAMEL-570) FTPComponent - Add delete/move operation

[ https://issues.apache.org/activemq/browse/CAMEL-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-570 started by Claus Ibsen. FTPComponent - Add delete/move operation Key: CAMEL-570

[jira] Commented: (CAMEL-570) FTPComponent - Add delete/move operation

[ https://issues.apache.org/activemq/browse/CAMEL-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43284#action_43284 ] Claus Ibsen commented on CAMEL-570: --- Drew is working on this. See the user forum.

[jira] Assigned: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-578: - Assignee: Claus Ibsen JMX Instrumentation - PerformanceCounter - last processed timestamp

[jira] Commented: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43276#action_43276 ] Claus Ibsen commented on CAMEL-578: --- William. At first glance the nano second timing value

[jira] Commented: (AMQ-1746) ActiveMQ server does not release the connection on a reconnect

[ https://issues.apache.org/activemq/browse/AMQ-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43243#action_43243 ] Hari commented on AMQ-1746: --- I have been working on this for a while now. I tried a bunch of things.

[jira] Commented: (AMQ-1746) ActiveMQ server does not release the connection on a reconnect

[ https://issues.apache.org/activemq/browse/AMQ-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43244#action_43244 ] Hari commented on AMQ-1746: --- Then also i tried to set the setKeepAlive on the socket to true and also

How Producer Flow Control works in activeMQ 5.1

Dear sir: Non-persistent messages will eventually fill up the memory made available for queues, and persistent messages will run out of allocated storage space and both situations pose risks to the stability of the message server and the entire distributed system. In order to ensure

[jira] Commented: (AMQ-1767) Multiple creating and closing consumers causes messages duplicated delivered

[ https://issues.apache.org/activemq/browse/AMQ-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43254#action_43254 ] Kevin commented on AMQ-1767: An update: I changed the code so, that each consumer and producer

[jira] Created: (AMQ-1771) Failover transport should always signal resume of transport

Failover transport should always signal resume of transport --- Key: AMQ-1771 URL: https://issues.apache.org/activemq/browse/AMQ-1771 Project: ActiveMQ Issue Type: Bug

[jira] Created: (AMQ-1772) Call stop() if exception thrown in start()

Call stop() if exception thrown in start() -- Key: AMQ-1772 URL: https://issues.apache.org/activemq/browse/AMQ-1772 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects

[jira] Resolved: (AMQ-1772) Call stop() if exception thrown in start()

[ https://issues.apache.org/activemq/browse/AMQ-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1772. - Resolution: Fixed Fixed by SVN revision 663604 Call stop() if exception thrown in start()

[jira] Assigned: (AMQ-1769) ActiveMQ broker in JBoss hangs when receiving 25k messages

[ https://issues.apache.org/activemq/browse/AMQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1769: --- Assignee: Rob Davies ActiveMQ broker in JBoss hangs when receiving 25k messages

Re: How Producer Flow Control works in activeMQ 5.1

So producer flow control works as follows: The producer has a window that gets smaller each time he sends a message. The client will stop sending once that window closes. When the broker has capacity, hes sends commands back to the producer to expand his window. Regards, Hiram On Thu, Jun 5,

Re: Unexpected EOFException on broker with big Stomp messages

the EOFException means that your client closed the socket. Regards, Hiram On Tue, Jun 3, 2008 at 6:28 AM, Ivan Jovanovic [EMAIL PROTECTED] wrote: I have a problem with sending big messages over Stomp. I have my own PHP Stomp client, ActiveMQ 5.1 on Gentoo Linux, Java 1.6_05 The message I

[jira] Assigned: (AMQ-1770) BlobUploader gets nulled out when copyMessageOnSend is set to true

[ https://issues.apache.org/activemq/browse/AMQ-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1770: --- Assignee: Rob Davies BlobUploader gets nulled out when copyMessageOnSend is set to true

[jira] Resolved: (AMQ-1770) BlobUploader gets nulled out when copyMessageOnSend is set to true

[ https://issues.apache.org/activemq/browse/AMQ-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1770. - Fix Version/s: 5.2.0 Resolution: Fixed Fixed by SVN revision 663639 BlobUploader gets nulled

[jira] Created: (AMQ-1773) The default Dead Letter Strategy sends non-persistent messages that have expired to the dead letter by default

The default Dead Letter Strategy sends non-persistent messages that have expired to the dead letter by default -- Key: AMQ-1773 URL:

[jira] Assigned: (AMQ-1773) The default Dead Letter Strategy sends non-persistent messages that have expired to the dead letter by default

[ https://issues.apache.org/activemq/browse/AMQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1773: --- Assignee: Rob Davies The default Dead Letter Strategy sends non-persistent messages that have

[jira] Resolved: (AMQ-1773) The default Dead Letter Strategy sends non-persistent messages that have expired to the dead letter by default

[ https://issues.apache.org/activemq/browse/AMQ-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1773. - Resolution: Fixed Fixed by SVN revision 663642 The default Dead Letter Strategy sends

[jira] Created: (AMQ-1774) Null pointer exception when sending expired advisory messages from a Queue

Null pointer exception when sending expired advisory messages from a Queue -- Key: AMQ-1774 URL: https://issues.apache.org/activemq/browse/AMQ-1774 Project: ActiveMQ

[jira] Resolved: (AMQ-1774) Null pointer exception when sending expired advisory messages from a Queue

[ https://issues.apache.org/activemq/browse/AMQ-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1774. - Resolution: Fixed Fixed by SVN revision 663644 Null pointer exception when sending expired advisory

[jira] Resolved: (AMQ-1769) ActiveMQ broker in JBoss hangs when receiving 25k messages

[ https://issues.apache.org/activemq/browse/AMQ-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1769. - Fix Version/s: 5.2.0 Resolution: Fixed ActiveMQ broker in JBoss hangs when receiving 25k

[jira] Created: (AMQ-1775) Error which starting tomcat with ActiveMQ 5.1

Error which starting tomcat with ActiveMQ 5.1 - Key: AMQ-1775 URL: https://issues.apache.org/activemq/browse/AMQ-1775 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.1.0

Re: missing dependency on trunk ?

Anybodyelse having this issue ? Sridhar2008 wrote: Hi, I tried to build from truck, but it fails the following directory is empty ... http://people.apache.org/repo/m2-snapshot-repository/org/apache/camel/camel-swing/1.4-SNAPSHOT/ Am I missing anything here ? Thanks - Sridhar

Re: missing dependency on trunk ?

Yes, but I have not tried yet today. On 6/5/08, Sridhar2008 [EMAIL PROTECTED] wrote: Anybodyelse having this issue ? Sridhar2008 wrote: Hi, I tried to build from truck, but it fails the following directory is empty ...

[jira] Assigned: (AMQ-1771) Failover transport should always signal resume of transport

[ https://issues.apache.org/activemq/browse/AMQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1771: --- Assignee: Rob Davies Failover transport should always signal resume of transport

[jira] Resolved: (AMQ-1771) Failover transport should always signal resume of transport

[ https://issues.apache.org/activemq/browse/AMQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1771. - Resolution: Fixed Fixed by SVN revision 663680 Failover transport should always signal resume of

[jira] Assigned: (AMQ-1768) Allow configuration of ActiveMQConfiguration in ActiveMQComponent with Spring

[ https://issues.apache.org/activemq/browse/AMQ-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1768: --- Assignee: Rob Davies Allow configuration of ActiveMQConfiguration in ActiveMQComponent with

[jira] Resolved: (AMQ-1768) Allow configuration of ActiveMQConfiguration in ActiveMQComponent with Spring

[ https://issues.apache.org/activemq/browse/AMQ-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1768. - Resolution: Fixed Fixed by SVN revision 663689 Allow configuration of ActiveMQConfiguration in

[jira] Issue Comment Edited: (AMQ-1771) Failover transport should always signal resume of transport

[ https://issues.apache.org/activemq/browse/AMQ-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43267#action_43267 ] rajdavies edited comment on AMQ-1771 at 6/5/08 11:12 AM: -- Fixed by SVN

[jira] Assigned: (AMQ-1754) org.apache.activemq.ActiveMQSslConnectionFactory extended to incorporate client.ks/client.ts files to enable convenient use of JNDI via SSL.

[ https://issues.apache.org/activemq/browse/AMQ-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1754: --- Assignee: Rob Davies org.apache.activemq.ActiveMQSslConnectionFactory extended to incorporate

[jira] Assigned: (AMQ-1746) ActiveMQ server does not release the connection on a reconnect

[ https://issues.apache.org/activemq/browse/AMQ-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1746: --- Assignee: Rob Davies ActiveMQ server does not release the connection on a reconnect

[jira] Commented: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43269#action_43269 ] Claus Ibsen commented on CAMEL-578: --- William good work. I was wondering if you could take a

[jira] Commented: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43271#action_43271 ] William Tam commented on CAMEL-578: --- No idea why it displays usec other than making it look

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: jconsole_nanosecond.PNG jconsole screenshot that shows perf counters in nanoseconds.

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: nanosecnd-patch.txt A patch that displays performance counters in nanoseconds. JMX

Bridge Topic to Queue

I would like to know if the bridge provided by ActiveMQ will work with Topic as the source and Queue as the destination.Currently there are 2 seperate bridges - Topic to Topic Queue to Queue which I see in the documentation. If I need to post message to WSMQ, what are the steps that I need to

[jira] Commented: (AMQ-1765) Getting IOException with Kaha storage

[ https://issues.apache.org/activemq/browse/AMQ-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43274#action_43274 ] vik dhawan commented on AMQ-1765: - Hi Rob, i understand you are saying its resolved in the

Re: Output Folder eclipse-classes.. why?

I've always thought it was just so maven eclipse don't confuse each other... however, this site tells me the real reason: Eclipse produces .class files even for classes with compilation errors. Such partially compiled classes may end up packaged into maven artifacts as mvn considers them

[jira] Created: (AMQ-1776) missing dependency on trunk ?

missing dependency on trunk ? -- Key: AMQ-1776 URL: https://issues.apache.org/activemq/browse/AMQ-1776 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.1.0 Reporter: Sridhar Komandur

Re: Output Folder eclipse-classes.. why?

Hi Chirstian, I don't like the mvn eclipse:eclipse default setting for share the target/classes and target/test-classes with eclipse. If I run mvn clean install in the trunk , I need to refresh the whole workspace and kick off a new building process in eclipse again, since eclipse lost the

[jira] Updated: (CAMEL-578) JMX Instrumentation - PerformanceCounter - last processed timestamp

[ https://issues.apache.org/activemq/browse/CAMEL-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Tam updated CAMEL-578: -- Attachment: undo_nano_patch.txt Here is a patch to change back to usec precision. JMX

[jira] Commented: (CAMEL-527) Break dependency cycle between camel and camel.impl

[ https://issues.apache.org/activemq/browse/CAMEL-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=43278#action_43278 ] Claus Ibsen commented on CAMEL-527: --- Hadrian has moved it back. Break dependency cycle