It seems like I have to create the NetworkConnector first or it messes up the
ManagementContext.
But if I do create the NetworkConnector first, it *seems* like it creates a
ManagementContext on it's own and it uses the default port (1099). But I
already have another broker on the machine usin
On Friday 05 September 2008, Bryan Murphy said:
> Sounds like a nightmare to me. Maybe I don't understand what you're trying
> to accomplish, but I think something like Hadoop would be a better fit for
> this kind of problem.
sounds like a job that JINI was designed for.
>
> Bryan
>
> On Fri, Se
I've read that you need to create the NetworkConnector before anything else,
and it seems true that you need a NetworkConnector before the
ManagementContext will work.
What seems to be happening is that the NetworkConnector uses a
ManagementContext, but because it isn't one that I built for it
Now, it seems like the recommendation is for Master/Slave for reliable
delivery, but I don't think we can do that.
We've got field laptops which may or may not have connectivity with the central
office, but they want to be able to run the application and have it send
messages that get delivere
On Wednesday 01 October 2008, Thomas R. Corbin said:
> Now, it seems like the recommendation is for Master/Slave for reliable
> delivery, but I don't think we can do that.
>
> We've got field laptops which may or may not have connectivity with the
> central office, but th
On Wednesday 01 October 2008, Joe Fernandez said:
> Use care, if you've assigned the multicast uri to all the brokers' network
> and transport connectors. They'll all end up trying to connect to one
> another. I think what you may want to consider is more of a hub-n-spoke
> topology, where the hub
On Thursday 02 October 2008, Joe Fernandez said:
> Are your 'assignments' messages are being sent out as non persistent? If
> so, then that is more than likely your problem.
>
> http://activemq.apache.org/why-do-i-not-receive-messages-on-my-durable-topi
>c-subscription.html
They *should* be persi
but not the other. Does that make sense?
When I run an embedded broker in my client process and it connects to the
central office broker, I can see a network bridge on the client jconsole
connecting to the central office broker, but I don't see a NetworkBridge in the
jconsole for the central
I'm using 5.1.0 with durable topics and durable messages. I'm using the derby
persistence and have removed all the derby persistence stores just prior to
starting my processes.
I'm assuming I've got something configured poorly, I just don't know what.
When I run one server process with an emb
What does this tell me?
sam-dataService is the name of one broker and masterJms is the name of my
central office broker.
What does the inbound mean?
NC_sam-dataService_inboundmasterJms
On Friday 03 October 2008, Bruce Snyder said:
> On Fri, Oct 3, 2008 at 1:47 PM, Thomas R. Corbin
>
> <[EMAIL PROTECTED]> wrote:
> > On Friday 03 October 2008, you said:
> >> On Fri, Oct 3, 2008 at 1:08 PM, Thomas R. Corbin
> >>
> >> <[EMA
On Friday 03 October 2008, Bruce Snyder said:
> On Fri, Oct 3, 2008 at 2:59 PM, Thomas R. Corbin
> <[EMAIL PROTECTED]> wrote:
> ...
>
> > What is the URI you're using in the embedded broker to connect to the
> > remote broker?
> >
> > Just the Asyn
On Friday 03 October 2008, Thomas R. Corbin said:
> On Friday 03 October 2008, Bruce Snyder said:
> > On Fri, Oct 3, 2008 at 2:59 PM, Thomas R. Corbin
> > <[EMAIL PROTECTED]> wrote:
> > ...
> >
> > > What is the URI you're using in the embedd
13 matches
Mail list logo
