Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: ECLIPSE-262
Type: Bug Bug
Status: Resolved Resolved
Resolution: Cannot Reproduce
Priority: Major Major
Assignee: Unassigned
Reporter: Eric Johnson
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Fuse IDE

Route tracing doesn't display anything

Created: 14/Jun/11 06:26 PM   Updated: 16/Jun/11 04:56 AM
Component/s: JMX
Affects Version/s: None
Fix Version/s: 2.0

Environment: Windows XO, Eclipse 3.6.2


 Description  « Hide
I ran the demo in fon/samples/camel-activemq-web using mvn:run and connected the JMX browser as instructed.
All of the artifacts showed up in the different views. I turned on tracing for Route 1 and dragged a message onto route1.in and nothing showed up in the message view. I tried selecting all of the possible output endpoints and they also showed nothing in the message view.

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
James Strachan added a comment - 14/Jun/11 06:33 PM
Clicking on an endpoint currently just shows the messages on that endpoint; not the tracing.

To view trace messages you need to click on a Route in the tree. (As its the routes that are traced).


Eric Johnson added a comment - 14/Jun/11 06:38 PM
The route doesn't show any messages either.... In other words I can drag and drop messages onto activeMQ endpoints(which gives me feedback that it is successful) and nothing shows up anywhere. Not on the target endpoints and not on a traced route.

James Strachan added a comment - 14/Jun/11 07:16 PM
BTW check if you're dragging XML files onto the endpoints, make sure its got the xmlns definition in it...
<message xmlns="http://fabric.fusesource.org/schema/messages">
...

a recent change was to add that in (for easier diagnostic of what is a messages file and whats a general XML file etc.

Its working fine for me here.

  • I grab some messages from a queue, drop them into a source directory to get a few XML files (I can then edit those files to change the payload etc).
  • I enable tracing on the myCamel context (or route1).
  • drop one of the message.xml files onto myCamel/Endpoints/activemq/route1.In
  • I see the message show up on myCamel/Endpoints/activemq/route1.Out.Other
  • If I click on myCamel/Routes or myCamel/Routes/route1 I see in the Messages View 3 versions of the message I just dropped; if I select one of them it highlights where it was in the Route View

Wondering if you used a different permutation of dragging/dropping?

FWIW previously I"ve hit the odd issue over some combination of endpoint/queue/message at the drag or drop bit; though if the send fails you usually get a dialog popup?


James Strachan added a comment - 14/Jun/11 07:16 PM
Anything show up in the Error Log after you try drop the message onto an endpoint?

Eric Johnson added a comment - 14/Jun/11 07:24 PM
adding the message wrapper fixed the issue

What if the message isn't XML?


James Strachan added a comment - 14/Jun/11 08:15 PM
Great stuff, phew!

So the main purpose of this new namespace is to detect if the file being dropped is a 'message XML' (in which case the headers & body are used) otherwise the intention is to create a message XML with the file XML encoded as the body.

Should have that bit implemented this week hopefully...


James Strachan added a comment - 16/Jun/11 04:56 AM
I think this is no longer an issue; we can always reopen if it is...