Paul,
Thanks a lot for guiding me through this process. I have tested your Test
class in a project mode and it passes the test. I just added a main(is this
even the right way to test it:)) and created an instance of the Test class
and it ran smoothly, is there any way where I can send the message to a
different application rather than seeing it in jconsole? Thanks again for
the immense help.
public static void main(String args[])
{
JMSAppenderTest mytest = new JMSAppenderTest();
System.out.println("**constructor executed**");
}
Regards,
-Misty.
On 6/26/07, Paul Smith <[EMAIL PROTECTED]> wrote:
On 27/06/2007, at 10:45 AM, Misty Thornton wrote:
> Paul,
> I am using ActiveMQ 4.1.1. What if I use..
>
> Destination destination = session.createTopic("CUST01.TOPIC1");
>
> Do you think that might help? I will go ahead and test it but
> please feel
> free to give me any input you may have. My boss is insisting that
> he needs
> to see the messages stored somewhere..:).
If you configure the JMSAppender with the specified topic name ala my
test case example, it should work. I don't think you will see any
messages in the topic in JMX, because Topics messages are delivered
to any message listeners (consumers), or if none, thrown away. I'm
not sure if you can create a Durable topic subscription system via
this mechanism. If you're after an appender that is storing the
events for later analysis, I'm not sure JMSAppender is the way to go,
perhaps DBAppender or it's siblings?
Have you tried using the open source Hermes JMS utility to connect to
the ActiveMQ instance and create a 'browser' on the topic you have
created? That's the easiest way to test.
The key to this is the jndi.properties and how it relates to the
JMSAppender. You will need to modify the jndi.properties that are
used by the test case because the test case only sets up an embedded
ActiveMQ broker for testing. The 'java.naming.provider.url' will
need to match the ActiveMQ connector details of your remote ActiveMQ
instance, for example 'tcp://somehost.com:61616' (whatever your
ActiveMQ is using). Please bear in mind that the test case is based
on the older ActiveMQ 3.2, so I'm not 100% certain if this is the
same way you'd do it in AMQ 4.1.
I would suggest setting up a test project in an IDE that depends on
log4j 1.2.14, activemq 4.1 libraries (I think only the -core are
needed) and try using the test case code to verify that it passes,
because that would be a good first step.
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
