Re: Spring AMQP Apache Camel Component Released

It appears the NPEs are due to a response not being made, either because a) a timeout occurred, b) delivery to the wrong queue or c) a null was actually sent as the endpoint's response. I have a patch now committed to master to resolve the NPE, however it just handles the null in a more sensical w

Re: Spring AMQP Apache Camel Component Released

This issue does appear to be fairly widespread and is documented as Issue #31 in GitHub. If you could, could you verify that VitorCardoso's work-around works? It's posted at https://github.com/Bluelock/camel-spring-amqp/issues/31#issueco

Re: Spring AMQP Apache Camel Component Released

Is thus using the Java DSL or a Spring config? -- View this message in context: http://camel.465427.n5.nabble.com/Spring-AMQP-Apache-Camel-Component-Released-tp5027785p5747358.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring AMQP Apache Camel Component Released

Thanks for following up. I'm hoping to have this and one other bug fixed & committed prior to February. I appreciate you submitting the route and the steps to reproduce! -- View this message in context: http://camel.465427.n5.nabble.com/Spring-AMQP-Apache-Camel-Component-Released-tp5027785p5745

Re: Spring AMQP Apache Camel Component Released

Odd... I'll take a look. Would you be able to send along your entire URI string? -- View this message in context: http://camel.465427.n5.nabble.com/Spring-AMQP-Apache-Camel-Component-Released-tp5027785p5744408.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring AMQP Apache Camel Component Released

The component is in active production use with several companies right now. One caveat is that acknowledgeMode is by default set to NONE - I think you would want it set to AUTO in most environments. Other than that, I believe it's good to go. -- View this message in context: http://camel.465427

Re: Component Design - SMSLib

My advice would be to read over the source for the file endpoint first - it's fairly bare-bones and makes it easy to comprehend how things work (for example, how endpoints receive parameters and then pass those along to consumers and producers). From there it's helpful to go through the mock endpoi

Re: Basic JMS to bean In/Out Router Question

What do you want to have happen on timeout? For example, are you wanting a TimeToLive on the message, after which it goes to a dead letter queue? The route you describe isn't a reply, it's a routing slip. See if that fits your concept: http://camel.apache.org/routing-slip.html mattmadhavan wrote

Re: Garbage collection Execuation ...

If you're seeing objects repeatedly get tenured into old gen, that often is a symptom of object references never being freed up. In that case it's not a garbage collection issue but more of a memory leak in your code. Collections that grow indefinitely or repeatedly creating prototype beans can oft

Re: Garbage collection Execuation ...

You can't force garbage collection to happen. You can /request/ that the JVM invoke it's configured garbage collector when it's next possible to do so, but a System garbage collection call is just a prompt and not a forced invocation. Since JMX is enabled on your map, your best bet would be to use

Re: Spring AMQP Apache Camel Component Released

"Vendor" meaning different implementations of the AMQP spec, both the client libraries as well as the broker. For example, right now the Spring AMQP project only supports RabbitMQ and lists the RabbitMQ client libraries as a dependency. Spring doesn't necessarily implement their own AMQP client lib

Re: Spring AMQP Apache Camel Component Released

Indeed, that is definitely on my list. Right now I've kept things relatively simple as the component enters more exhaustive pre-production testing, but after we've validated the component that's on my hit list of things to do. Prior to the completion of testing I have on the docket to: - Allow spe

Spring AMQP Apache Camel Component Released

For those who might be interested, I've posted a Camel component based on Spring AMQP for those who wish to use more AMQP semantics instead of a JMS->AMQP interface via Qpid. Source is now available at https://github.com/Bluelock/camel-spring-amqp While the Qpid component is great for those who mi

Re: Writing own Camel Components

he License 2 (RabbitMQ appears to be okay as a binary exclusion) but more on the feedback spurred by this post. I'll refactor the project (i.e. package names) to draw a greater distinction between this project and an ASF sponsored project, then re-push the project to GitHub. deckerego wrote:

Re: Writing own Camel Components

This seems like a great point to highlight and flush out... thanks for weighing in on this Jim. Your read on the license mirrors my own. I too understood that the exclusions referred to packaging within Apache /projects/ and not necessarily software that is not part of a project but licensed under

Re: Writing own Camel Components

I did not assume that adding the license made it so, but I mistakenly thought the dependency exclusion applied to Apache projects and not necessarily code released under the Apache License. I'll delete the repo. On Nov 9, 2011 5:25 PM, "Ashwin Karpe [via Camel]" < ml-node+s465427n4979330...@n5.nabb

Re: Writing own Camel Components

Gotcha. Reading the link that Hadrian supplied it seems that this applies to Apache projects but not necessarily for projects under the Apache License - is that correct? If the project continued to be provided under the Apache License 2 but hosted entirely within GitHub would that be acceptable? Or

Re: Writing own Camel Components

The client libraries appear to be dual-licensed under MPL 1.1 and GPL v2. Since the component never calls the RabbitMQ client libraries directly (and doesn't even mark them as an immediate dependency) does that still constitute a conflict? spring-amqp does pull in the client libraries, but camel-sp

Re: Writing own Camel Components

Got the approval, posted the component to https://github.com/deckerego/camel-spring-amqp This code is fresh from a conversion from RabbitMQ's client libraries to the Spring AMQP project, so there are no doubt some oddities lurking under the surface. Unit tests pass but I haven't tried i

Re: Writing own Camel Components

ee where it leads me. Michael Prieß wrote: > > Hello Deckerego, > > it would be nice if you can upload your component very soon on github. > > How long did you need to check if you can release your code under > Apache Licence and upload your code on Github. That I can fork you ;

Re: Writing own Camel Components

Believe it or not, I started writing a RabbitMQ component on Friday as well ;) Small world. In defense of Michael, I can totally understand why one would want to build a component based on the RabbitMQ client libraries. I've been trying to work with the Qpid libraries talking to a RabbitMQ broker

Re: Setting Cookie Header in Restlet Request

to be. Thanks! deckerego wrote: > > I think I see what you mean. In my head I'm trying to think of the > benefits of using CXFRS or Restlet instead of straight HTTP... but in > truth I'm not coming up with many. I'm ultimately just going to take the > resulting

Re: Setting Cookie Header in Restlet Request

I think I see what you mean. In my head I'm trying to think of the benefits of using CXFRS or Restlet instead of straight HTTP... but in truth I'm not coming up with many. I'm ultimately just going to take the resulting XML and unmarshal it via JAXB, then throw non-HTTP 200 response codes as an ex

Setting Cookie Header in Restlet Request

I'm attempting to send a REST message to an endpoint via the Restlet component. The service requires you to send the session ID that was set as a cookie for all subsequent requests - so I first authenticate, receive an ID in the Set-Cookie header on the HTTP response, then need to send the same ID

Re: Problem with JMS Component with PooledConnectionFactory

I've experienced the same thing. Sometimes (and this isn't predictable) JMS production ceases entirely and messages just back up. This isn't related to load either - this can happen with near-zero load as well. Issue does not happen with the JMS template or Camel's vanilla ActiveMQ Component. m