This gets turned into a gbean attribute called ServerUrl on the
ResourceAdapterWrapper gbean so it should be possible to override it
that way in config.xml.
thanks
david jencks
On Apr 9, 2007, at 7:48 PM, Anita Kulshreshtha wrote:
Kevan,
The plan for activemq-ra config is using 61616:
Thanks David! I could not find a ServerUrl attribute in
ResourceAdapterWrapper gbean. Do we need to add one? If yes, how?
Thanks
Anita
--- David Jencks [EMAIL PROTECTED] wrote:
This gets turned into a gbean attribute called ServerUrl on the
ResourceAdapterWrapper gbean so it should be
All the config-properties specified in ra.xml for the resource
adapter class and the outbound ManagedConnectionFactory and IIRC the
admin objects are turned into dynamic attributes for the wrapper
gbeans so they can be set through the gbean mechanism, exposed to
management, overridden in
Thanks David! I had overlooked getAttribute and setAttribute methods
in ResourceAdapterWrapperGBean. I used ActiveMQ RA and it worked like
charm!
Thanks
Anita
--- David Jencks [EMAIL PROTECTED] wrote:
All the config-properties specified in ra.xml for the resource
adapter class and the
Kevan,
The plan for activemq-ra config is using 61616:
resourceadapter
resourceadapter-instance
resourceadapter-nameActiveMQ RA/resourceadapter-name
config-property-setting
name=ServerUrltcp://${PlanServerHostname}:${PlanActiveMQPort}/config-property-setting
--- Kevan Miller [EMAIL PROTECTED] wrote:
So, we're establishing this
internal connection to ActiveMQ without specifying a port number (and
activemq is defaulting).
This seems more likely... (rev 521546)
Or, we're using the wrong port number.
Server reports the correct port
On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
I get following exception while starting an instance of g using
port
61626 instead of 61616. Where is 61616 coming from?
Hi Anita,
61616 is the ActiveMQ's default port. So, we're establishing this
internal connection to ActiveMQ
--- Kevan Miller [EMAIL PROTECTED] wrote:
On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
I get following exception while starting an instance of g using
port
61626 instead of 61616. Where is 61616 coming from?
Hi Anita,
61616 is the ActiveMQ's default port. So,