No. You can disable advisory support by setting it to false in your
broker confiiguration :
eg.
<broker brokerName="localhost" useJmx="true"
xmlns="http://activemq.org/config/1.0"; *advisorySupport="false"* >
....
Regards,
Jonas
pradeep wrote:
Thanks. Is it mandatory ?
Pradeep
jlim wrote:
These are advisory messages which allows you to watch the system by
creating jms messages.
http://www.activemq.org/site/what-are-those-topics-activemqadvisory.html
regards,
Jonas
pradeep wrote:
Thanks. I have noticed that without the authorizationEntry for
topic="ActiveMQ.Advisory.>" my program fails. Why do we need this.
Thanks
Pradeep
jlim wrote:
I'm not really sure when 4.2 will be released since 4.1 just got out.
Hopefully soon :-)
Jonas
pradeep wrote:
Thank you. I am seeing this problem only in 4.2 version.
Another question - When will 4.2 be released ?
Pradeep
jlim wrote:
It appears the jms client lost its connection to the broker.
You may want to try failover transport :
http://activemq.org/site/how-can-i-support-auto-reconnection.html
Regards,
Jonas
pradeep wrote:
jlim
Can you please tell me why the WARN message was displayed?
thanks a lot
pradeep
pradeep wrote:
Thank you. It worked with the Dec 3 build but I am seeing this
warning
message
11:20:12 [ActiveMQ Transport: tcp://localhost/127.0.0.1:61616] WARN
org.apache.activemq.ActiveMQConnection - Async exception with no
exception
listener: java.io.EOFException
java.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at
org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:267)
at
org.apache.activemq.transport.tcp.TcpTransport.readCommand(TcpTransport.java:156)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:136)
at java.lang.Thread.run(Unknown Source)
jlim wrote:
Can you try downloading again the latest 4.2 nighlty build (Dec 3)?
I
believe this feature was just added last Nov 27 to the svn trunk .
I
think you may have downloaded an older 4.2 build
Jonas
pradeep wrote:
I downloaded the activemq 4.2 nightly build but I am still seeing
the
same
problem. I don't see the TempDestincationAuthorization entry class
in
the
jar file.
jlim wrote:
Hi,
The Tempdestination authorization entry was just added on the
4.2
trunk
(revision 479639). I don't believe it made it to the 4.1 build.
You
can
checkout the latest from trunk or download a nightly build
http://people.apache.org/repo/m2-snapshot-repository/org/apache/activemq/apache-activemq/4.2-incubator-SNAPSHOT/
The ">" is a wildcard. You can use it as is to indicate all
queue/topic or you can append it to a destination name (ie.
USERS.>)
indicating all destinations that starts with "USERS."
Regard,
Jonas
pradeep wrote:
I am using the Tempdestination authorization entry as mentioned
in
http://activemq.org/site/security.html.
I am getting this error when starting embeded activemq server
Failed to load type: tempDestinationAuthorizationEntry. Reason:
java.lang.ClassNotFoundException:
tempDestinationAuthorizationEntry;
nested
exception is java.lang.ClassNotFoundException:
tempDestinationAuthorizationEntry
I am using activeMQ 4.1
Also what does ">" right angle bracker indicate in the below tag
?
<authorizationEntry queue=">" read="admins" write="admins"
admin="admins"
/>
