Re: Expired message stuck inside the queue

[James Strachan]

Can you try switching your jars to 4.2-snapshot (from January 2007) in
development / system testing and seeing if you can make the bug
happen? I'd like to know if the issue is fixed in 4.2-snapshot.


On 1/19/07, bluedolphin <[EMAIL PROTECTED]> wrote:


Sorry, may i know what do u mean reproduce?


James.Strachan wrote:
>
> On 1/19/07, bluedolphin <[EMAIL PROTECTED]> wrote:
>>
>> we just allowed to use official release for our production use. Since 4.2
>> haven been officially released, we r not allowed to use it. Is there any
>> other solution?
>
> Can't you try reproduce it in development?
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>
>

--
View this message in context: 
http://www.nabble.com/Expired-message-stuck-inside-the-queue-tf3038899.html#a8446723
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: Expired message stuck inside the queue

[James Strachan]

On 1/19/07, bluedolphin <[EMAIL PROTECTED]> wrote:


we just allowed to use official release for our production use. Since 4.2
haven been officially released, we r not allowed to use it. Is there any
other solution?


Can't you try reproduce it in development?

--

James
---
http://radio.weblogs.com/0112098/

Re: Expired message stuck inside the queue

[James Strachan]

Does the same thing happen if you try the latest 4.2-snapshot (from January)?

On 1/19/07, bluedolphin <[EMAIL PROTECTED]> wrote:


4.1

James.Strachan wrote:
>
> Which version are you using?
>
> On 1/19/07, bluedolphin <[EMAIL PROTECTED]> wrote:
>>
>> I had sent an 10 sec expired message to a queue(i stopped the application
>> server tat reading the queue's message for 10 sec to create this
>> scenario),
>> then started the application server and i send another message to the
>> same
>> queue after 20 sec (in this case the previous message should be expired).
>> The 2nd message that I send to the queue cannot be consumed due to the
>> previous expired message stuck inside the queue. May i know how to solve
>> this? thanks.
>> --
>> View this message in context:
>> 
http://www.nabble.com/Expired-message-stuck-inside-the-queue-tf3038899.html#a8445948
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>
>

--
View this message in context: 
http://www.nabble.com/Expired-message-stuck-inside-the-queue-tf3038899.html#a8446196
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: Error while Sending Map message

[James Strachan]

On 1/15/07, garima015 <[EMAIL PROTECTED]> wrote:


Can i also send exception object ?? as Object Message


You can send any Serializable object in an ObjectMessage
--

James
---
http://radio.weblogs.com/0112098/

Re: [VOTE] Release ActiveMQ-CPP 1.1

[James Strachan]

+1

On 1/14/07, Rob Davies <[EMAIL PROTECTED]> wrote:

+1

On 14 Jan 2007, at 16:07, Nathan Mittler wrote:

> Hi everyone,
> Several bug fixes as well as a few new features have been
> incorporated into
> ActiveMQ-CPP - worthy of a 1.1 release, before we go for full openwire
> support in 2.0.
>
> The source bundle for the release candidate can be found here:
> http://people.apache.org/~nmittler/incubator-activemq-cpp-1.1-src.zip
> 
>
> And here's the wiki page for the release:
> http://www.activemq.org/site/activemq-cpp-11-release.html
> 
>
> Please cast your votes:
>
> [ ] +1 Release the source as Apache ActiveMQ  CPP 1.1
> [ ] -1 Veto the release (provide specific comments)
>
> Regards,
> Nate





--

James
---
http://radio.weblogs.com/0112098/

[jira] Resolved: (AMQ-1114) ActiveMQ Queue management- How to kill a queue?

[james strachan (JIRA)]

 [ 
https://issues.apache.org/activemq/browse/AMQ-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

james strachan resolved AMQ-1114.
-

   Resolution: Fixed
Fix Version/s: 4.1.0

See the methods on the Queue MBean such as purge() to delete all messages on a 
queue

http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/apache/activemq/broker/jmx/QueueViewMBean.html#purge()

> ActiveMQ Queue management- How to kill a queue?
> ---
>
> Key: AMQ-1114
> URL: https://issues.apache.org/activemq/browse/AMQ-1114
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker, JCA Container
>Affects Versions: 4.0.1
> Environment: Windows XP, Jdk 1.5, ActiveMQ4.0.1
>Reporter: Vairavan Chandrasekhar
> Fix For: 4.1.0
>
>
> ActiveMQ: Through 'jconsole' we can view all the java components which ever 
> is active. So by this way, we can see the particular queue and also we can 
> able to find how many customers are listening.
> But I want to manage the queue, like I want to kill a particular queue.  Can 
> anybody help me how to proceed with?
> It's pleasure to explain more if you are not clear.
> Thanks in advance
> Shekar

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Broker Fails

[James Strachan]

On 1/2/07, garima015 <[EMAIL PROTECTED]> wrote:


I am not using network of brokers.I have a scenario in which if my running
broker fails or get shutdown what is going to  happen with the messages.


If they are sent using persistent message delivery they will be on
disk / in the database and redelivered on restart.


Also
if broker shutdown where my application will send the message in order to
restore them once the borker will start again. Also how the restarted borker
will resume with the undelivered messages
can somebody please help me in suggesting any solution. It is very urgent


If you are using auto-reconnection then the jms client will handle
brokers being restarted or will failover to a new broker instance etc.

http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html
--

James
---
http://radio.weblogs.com/0112098/

Re: Performance Issue

[James Strachan]

On 12/19/06, garima015 <[EMAIL PROTECTED]> wrote:


Thanks for the reply,but it is solved.


How did you solve it?

--

James
---
http://radio.weblogs.com/0112098/

[jira] Resolved: (AMQ-1093) Client deadlock during failover

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1093?page=all ]

james strachan resolved AMQ-1093.
-

Fix Version/s: 4.2.0
   Resolution: Fixed

I've just committed a patch to trunk for this which I think resolves the issue. 

There's no test case to easily verify its resolved though (its a tad hard to 
recreate) so I wonder could you try and see if this is now fixed - if not let 
us know and we can reopen this issue

> Client deadlock during failover
> ---
>
> Key: AMQ-1093
> URL: https://issues.apache.org/activemq/browse/AMQ-1093
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Transport
>Affects Versions: 4.1.0
> Environment: Linux 2.6, java 1.5.0
>Reporter: Danielius Jurna
>Priority: Critical
> Fix For: 4.2.0
>
>
> In 4.1.0 there's deadlock on connection failover. There is the scenario: 
> 1. Client consumes message using message listener 
> 2. Conection is lost 
> 3. Client sends message to another queue from messagle listener and waits 
> until connection is restored. 
> 4. Reconnect task blocks on reconnecting. 
>  
> This bug is new to 4.1.0. The problem is in ActiveMQMessageConsumre.dispatch 
> . There is new lock on unconsumedMessages.getMutex() . So the reconnect task 
> cannot invoke ActiveMQMessageConsumre.clearMessagesInProgress(), because lock 
> is acquired by message listener, which waits untill message is sent (untill 
> connection is resumed). Here is stack traces: 
>  
> "ActiveMQ Session Task" daemon prio=1 tid=0x002b27774260 nid=0x4778 in 
> Object.wait() [0x40ef3000..0x40ef4db0] 
> at java.lang.Object.wait(Native Method) 
> - waiting on <0x002b0020a7c8> (a 
> edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) 
> at java.lang.Object.wait(Object.java:474) 
> at 
> edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar.await(CondVar.java:75)
>  
> - locked <0x002b0020a7c8> (a 
> edu.emory.mathcs.backport.java.util.concurrent.locks.CondVar) 
> at 
> edu.emory.mathcs.backport.java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:318)
>  
> at 
> org.apache.activemq.transport.FutureResponse.getResult(FutureResponse.java:42)
>  
> at 
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:75)
>  
> at 
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1171)
>  
> at 
> org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1548) 
> at 
> org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
>  
> at 
> org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:75) 
> - locked <0x002b173fa480> (a 
> org.apache.activemq.ActiveMQMessageProducer) 
> at 
> org.apache.activemq.pool.PooledProducer.send(PooledProducer.java:60) 
> at 
> org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:537) 
> at 
> org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:513) 
> at 
> org.springframework.jms.core.JmsTemplate$2.doInJms(JmsTemplate.java:479) 
> at 
> org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:430) 
> at 
> org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:477) 
> at 
> lt.elitnet.dbp.das.impl.storage.HI2StorageImpl.storeHI2Message(HI2StorageImpl.java:57)
>  
> at 
> lt.elitnet.dbp.das.impl.hi2.HI2PersistanceBase.saveIRIContent(HI2PersistanceBase.java:77)
>  
> at sun.reflect.GeneratedMethodAccessor185.invoke(Unknown Source) 
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>  
> at java.lang.reflect.Method.invoke(Method.java:585) 
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
>  
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:203)
>  
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:162)
>  
> at 
> org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107)
>  
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
>  
> at 
> org.springframework.orm.hibern

Re: steps to publish to a topic for BrokerFilter-based classes?

[James Strachan]

Yeah - you might want to look at the Virtual Destination stuff which
does this kind of thing - forwarding a message to arbitrary
destinations based on selectors/filters - you could maybe reuse some
of that code. But it seems like you've figured it out anyway :)

On 12/7/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:

Hi,
   It's really not so difficult, after all.  If you have a class that
extends BrokerFilter, then you can use the next.send(ConnectionContext
ctxt, Message msg) method to send a Message that has been generated.

  ActiveMQTopic responseTopic =
 new ActiveMQTopic(responseTopicString);
  ActiveMQTextMessage responseMsg =
 new ActiveMQTextMessage();
  responseMsg.setText( "this is the message text" );
  responseMsg.setDestination( responseTopic );
  responseMsg.setMessageId( new MessageId(
java.util.UUID.randomUUID().toString() ) );

  next.send(ctxt, responseMsg); /* this sends the message! */

   Thanks for all your great work on ActiveMQ!

   Patrick



On 12/6/06, Fritz Oconer <[EMAIL PROTECTED]> wrote:
> Hi Patrick,
>
> What I could suggest is to use JmsTemplate to send messages and possibly
> Spring based configurations. See unit test SpringTest.java and
> SpringProducer.java located in
> 
"${activemq.source.home}\activemq-core\src\test\java\org\apache\activemq\spring\
> " for reference.
>
> Regards,
> Fritz
>
> - Original Message -
> From: "J. Patrick Bedell" <[EMAIL PROTECTED]>
> To: 
> Sent: Thursday, December 07, 2006 7:04 AM
> Subject: steps to publish to a topic for BrokerFilter-based classes?
>
>
> > Hello,
> >   I'm working on a Broker interceptor class that extends BrokerFilter.
> >   After processing an incoming message, I would like to publish to a
> > topic that is determined from the content of the message.
> >   My question is: is there a quicker way to publish to a topic from a
> > Broker than the standard method a client uses to publish (getting
> > connection, TopicSession, TopicPublisher, and then using the
> > TopicPublisher to publish)?
> >   Thanks!
> >

--
   J. Patrick Bedell
   [EMAIL PROTECTED]
   http://infoeng.sourceforge.net
   http://rothbardix.blogspot.com




--

James
---
http://radio.weblogs.com/0112098/

[jira] Created: (AMQ-1091) add a source distro to the maven2 build

[james strachan (JIRA)]

add a source distro to the maven2 build
---

 Key: AMQ-1091
 URL: https://issues.apache.org/activemq/browse/AMQ-1091
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: james strachan
 Fix For: 4.2.0




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-761) ActiveMQConnectionFactory.setBrokerURL does not set all connection properties corrrectly

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-761?page=all ]

james strachan resolved AMQ-761.


Fix Version/s: 4.1.0
   Resolution: Fixed

> ActiveMQConnectionFactory.setBrokerURL does not set all connection properties 
> corrrectly
> 
>
> Key: AMQ-761
> URL: https://issues.apache.org/activemq/browse/AMQ-761
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 3.2.2
> Environment: Windows XP, Java 1.4.1
>Reporter: Jim Beattie
> Fix For: 4.1.0
>
> Attachments: UrlSetterTest.java
>
>
> If I set the brokerUrl of ActiveMQConnectionFactory using setBrokerURL(), the 
> connection factory does not reparse all of the properties from the URL.  As a 
> result, when a new connection is created, some of the properties from the URL 
> specified during the construction of the connection factory (typically the 
> defaults) are used instead.  Attached is a unit test to demonstrate the 
> problem.
> As a minimum, the following block of code is required in setBrokerURL().  But 
> this doesn't really fix it because properties settings from the URL used by 
> the constructor may not be reset by this code.  A structural change may be in 
> order (e.g. just-in-time parsing of the properties).
>if( brokerURL.indexOf("?")>= 0 ) {
> String options = brokerURL.substring(brokerURL.indexOf("?")+1);
> Map properties = URIHelper.parseQuery(options);
> if (!properties.isEmpty()) {
> BeanUtils.populate(this, properties);
> }   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[VOTE][RESULT] Release Apache ActiveMQ 4.1.0 (RC 2)

[James Strachan]

So if my mental arithmetic is correct the results are

3 binding +1s
6 +1s from the PPMC

so this vote passes. Thanks to all those who took the time to review
the distros.


On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Hey folks,

I was able to finally get around to doing a binary release candidate
from the 4.1 branch.

it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-410-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.1.0
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1


--
Regards,
Hiram

Blog: http://hiramchirino.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--

James
---
http://radio.weblogs.com/0112098/

[jira] Resolved: (AMQ-756) Hangs on creating topic on Windows XP 2002 SP2

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-756?page=all ]

james strachan resolved AMQ-756.


Fix Version/s: 4.1.0
   Resolution: Cannot Reproduce

AFAIK this is now resolved. Let us know and we can reopen if required

> Hangs on creating topic on Windows XP 2002 SP2
> --
>
> Key: AMQ-756
> URL: https://issues.apache.org/activemq/browse/AMQ-756
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0 M4
> Environment: Windows 2002 XP SP2
>Reporter: shantharam
> Fix For: 4.1.0
>
>
> On windows server when trying to create a Topic Session code just hangs, here 
> is the Thread Dump, same code works fine Unix and Linux environment
> "StackTrace Remote Thread" prio=5 tid=0x0444a1a0 nid=0x15ac runnable 
> [0..55dfb9c]
>  
> "tcp://dubxww11hr/10.251.116.216:29258" prio=5 tid=0x04454868 nid=0xcf4 
> runnable [550f000..550fd8c]
> at java.net.SocketInputStream.socketRead0(Native Method)
> at java.net.SocketInputStream.read(SocketInputStream.java:129)
> at 
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:48)
> at 
> org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:55)
> at java.io.DataInputStream.readInt(DataInputStream.java:443)
> at 
> org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:180)
> at 
> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:135)
> at java.lang.Thread.run(Thread.java:534)
>  
> "Thread-0" daemon prio=5 tid=0x03733c30 nid=0x508 in Object.wait() 
> [42df000..42dfd8c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x12cb01c8> (a java.util.TaskQueue)
> at java.util.TimerThread.mainLoop(Timer.java:429)
> - locked <0x12cb01c8> (a java.util.TaskQueue)
> at java.util.TimerThread.run(Timer.java:382)
>  
> "Signal Dispatcher" daemon prio=10 tid=0x008ad9f0 nid=0xf8c runnable [0..0]
>  
> "Finalizer" daemon prio=9 tid=0x008aafa0 nid=0x1328 in Object.wait() 
> [2faf000..2fafd8c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x12d6cac0> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111)
> - locked <0x12d6cac0> (a java.lang.ref.ReferenceQueue$Lock)
> at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127)
> at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
>  
> "Reference Handler" daemon prio=10 tid=0x008a9c20 nid=0x760 in Object.wait() 
> [2eaf000..2eafd8c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x12d6cb28> (a java.lang.ref.Reference$Lock)
> at java.lang.Object.wait(Object.java:429)
> at 
> java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115)
> - locked <0x12d6cb28> (a java.lang.ref.Reference$Lock)
>  
> "main" prio=5 tid=0x00037c50 nid=0x1650 in Object.wait() [7e000..7fc3c]
> at java.lang.Object.wait(Native Method)
> - waiting on <0x101deeb0> (a 
> edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch)
> at java.lang.Object.wait(Object.java:429)
> at 
> edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:173)
> - locked <0x101deeb0> (a 
> edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch)
> at 
> org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:61)
> at 
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> - locked <0x101efb00> (a java.lang.Object)
> at 
> org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:62)
> at 
> org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:67)
> at 
> org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1068)
> at 
> org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1132)
> at 
> org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:251)
> at 
> org.apache.activemq.ActiveMQConnecti

[jira] Resolved: (AMQ-728) Active MQ is creating great number of Oracle processes

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-728?page=all ]

james strachan resolved AMQ-728.


Fix Version/s: 4.2.0
   Resolution: Fixed

I think this is now resolved - if it isn't please let us know and we can reopen

> Active MQ is creating great number of Oracle processes
> --
>
> Key: AMQ-728
> URL: https://issues.apache.org/activemq/browse/AMQ-728
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Message Store
>Affects Versions: 3.2.1
> Environment: Sun Solaris 8, Oracle 9i2, Java 1.4.2_08
>Reporter: Hans Huber
> Fix For: 4.2.0
>
> Attachments: OracleAfter.png, OracleBefore.png
>
>
> We migrated from derby to Oracle as message persistence layer. We discoverd 
> now, that ActiveMQ is creating a lot of Oracle resource intensive processes. 
> Please see attached diagrams:
> OracleBefore.png = Orace processes with derby as persistence layer
> OraceAfter.png = Oracle processes with Oracele as persistence layer
> Any help is much appreciated. If you need any additional information, pls 
> don't hesitate to contact me
> Best regards, Hans Huber

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-992) MySQL doesn't honor lock in JDBC Master Slave configuration?

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-992?page=all ]

james strachan resolved AMQ-992.


Fix Version/s: 4.1.1
   4.2.0
   Resolution: Fixed

> MySQL doesn't honor lock in JDBC Master Slave configuration?
> 
>
> Key: AMQ-992
> URL: https://issues.apache.org/activemq/browse/AMQ-992
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1.0
> Environment: RHEL 4
> MySQL 4.x, 5.x
> mysql-ab_jdbc_driver
>Reporter: Steven Lotito
> Fix For: 4.1.1, 4.2.0
>
> Attachments: mysql_obtain_lock.txt
>
>
> I have been attempting to get the new 4.1 JDBC Master Slave configuration 
> working with MySQL.
> The log from the first broker to start up states:
> 2006-10-18 09:35:08,558 [main   ] INFO  DefaultDatabaseLocker 
>  - Attempting to acquire the exclusive lock to become the Master broker
> 2006-10-18 09:35:08,559 [main   ] INFO  DefaultDatabaseLocker 
>  - Becoming the master on dataSource: [EMAIL PROTECTED]
> The 2nd broker to start up has an identical message and both brokers listen 
> for connections.
> The 2nd broker should be waiting for the lock and NOT accepting connections, 
> if I understand http://www.activemq.org/site/jdbc-master-slave.html 
> correctly...
> Oracle exhibits the expected behavior:
> When running the exact same configuration (except using an Oracle 
> datasource), the first broker has the same log message as above,  while the 
> 2nd broker halts at the "Attempting to acquire the exclusive lock to become 
> the Master broker" message until I fail the master.  Then it becomes the 
> master.
> Is this a known issue?  I was able to replicate it using both MySql 4 and 5 
> (trying both the MySQL Connector/J 3.1 and MySQL Connector/J 5.0 drivers)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1050) browse -QTopic=* does not seem to return anything...

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1050?page=all ]

james strachan resolved AMQ-1050.
-

Resolution: Fixed

> browse -QTopic=* does not seem to return anything...
> 
>
> Key: AMQ-1050
> URL: https://issues.apache.org/activemq/browse/AMQ-1050
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.x
>    Reporter: james strachan
> Assigned To: Adrian Co
> Fix For: 4.1.1, 4.2.0
>
>
> I think there's something funny going on in the regex stuff. I tried from the 
> SimpleConsole typing
>   query -QTopic=*
> and I get nothing. 
>   query 
> returns tons of stuff though.
> I wonder if it might be simpler to have specific arguments for topic and 
> queues? 
> query -topic=*
> queyr -queue=*
> to avoid the complex regex of ObjectName etc?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: NEED HELP on how i can "Provide an ay for retrieving the amount of messages per priority that is waiting to be sent to subscribers"

[James Strachan]

You could write a broker interceptor to keep a track of this kind of
thing; or use selectors.

http://incubator.apache.org/activemq/interceptors.html

On 12/4/06, samahome <[EMAIL PROTECTED]> wrote:


Which classes in ActiveMQ source i can look at for Providing  an way for
retrieving the amount of messages per priority that is waiting to be sent to
subscribers ?

I would like to get this functionality programatically (other than the use
of JMX).

Help /Insights on this greatly appreciated.

Thanks,
Sreenivas
--
View this message in context: 
http://www.nabble.com/NEED-HELP--on-how-i-can-%22Provide-an-ay-for-retrieving-the-amount-of-messages-per-priority-that-is-waiting-to-be-sent-to-subscribers%22-tf2749797.html#a7671885
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

[jira] Updated: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ]

james strachan updated AMQ-1054:


Fix Version/s: 4.1.1

updated fix versions

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Fix For: 4.2.0, 4.1.1
>
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1072) "TimeToLive" doesn't work on MessageListener

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1072?page=all ]

james strachan resolved AMQ-1072.
-

Fix Version/s: 4.1.0
   Resolution: Fixed

This has been fixed in 4.1

> "TimeToLive" doesn't work on MessageListener
> 
>
> Key: AMQ-1072
> URL: https://issues.apache.org/activemq/browse/AMQ-1072
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 4.0.1
>Reporter: Joseph Leung
> Fix For: 4.1.0
>
>
> When a queue message is consumed using MessageListener throught the 
> setMessageListener method,
> it could recieve the messages even if they are expired. (While using 
> consumer.receive() will discard them).
> Reproduce Steps:
> 1. deliver a number of message to a queue with a short expire time.
> 2. wait until the message should be expired.
> 3. use MessageConsumer.receive() method to receive the messages,
>  -- You should not receive any messages, and through the monitor console, 
> you should see some
>  messages are left and not discarded.
> 4. stop the receive() method.
> 5. add a MessageListener to the same queue, the messages which found left is 
> received by the
>  onMessage() method.
> ps. if step3 is skipped, likely you would receive all the expired message.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37589 ] 

james strachan commented on AMQ-1054:
-

Have backported the test case and fix to 4.1 branch too if we release a new bug 
fix release of 4.1 before 4.2

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Fix For: 4.2.0
>
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ]

james strachan resolved AMQ-1054.
-

Fix Version/s: 4.2.0
   Resolution: Fixed

Aha! So the reason the test case was working that I checked into trunk and 4.0 
branch was due to the fact that the test was using the VM transport - which 
tends to avoid mashalling to and from a socket, so not causing the bug.

Have patched the test case both in trunk and in the 4.0 branch. The one in the 
4.0 branch now does indeed fail with the ClassCastException. The one in trunk 
passes with flying colours. So this issue is now resolved and will go out as 
part of the 4.2 release.

If we cut a 4.1.x bug fix release this fix can be back ported for that too



> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Fix For: 4.2.0
>
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1074) support JDBC master slave on MySQL

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1074?page=all ]

james strachan resolved AMQ-1074.
-

Resolution: Fixed

I think this is now working - if folks find an issue with it we can reopen this 
issue

> support JDBC master slave on MySQL
> --
>
> Key: AMQ-1074
> URL: https://issues.apache.org/activemq/browse/AMQ-1074
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: james strachan
> Fix For: 4.2.0
>
>
> We need to make a few changes to support MySQL's SQL dialect for JDBC Master 
> Slave...
> http://incubator.apache.org/activemq/jdbc-master-slave.html
> For details see this thread...
> http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37584 ] 

james strachan commented on AMQ-1054:
-

Hi Shoaib

Thanks for the link. FWIW the patch Mary gives is similar to the one you 
suggested and the one I've applied to trunk to fix this issue. So fingers 
crossed its fixed.


> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1075) support for FileMessage interface to support in-band and out-of-band file transfer

[james strachan (JIRA)]

support for FileMessage interface to support in-band and out-of-band file 
transfer
--

 Key: AMQ-1075
 URL: https://issues.apache.org/activemq/browse/AMQ-1075
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker
Reporter: james strachan
 Fix For: 4.2.0


Some new API like this...

public class ActiveMQSession  {

// send a local file or stream over JMS
public FileMessage createLocalFileMessage(InputStream inputStream) {...}
public FileMessage createLocalFileMessage(File file) {..,}
public FileMessage createLocalFileMessage(URL url) {..,}


// send a remote URL over JMS
public FileMessage createRemoteFileMessage(URL url) {...}
}

with FileMessage like this...

public interface FileMessage extends Message {

  // access the remote resource
  // or for local resources, force creation of temporary file
  // so this resource can be parsed multiple times etc
  URL getURL();

  InputStream getInputStream();
}


For further discussion see
http://www.nabble.com/support-for-FileMessage--tf2641673.html#a7373916




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1074) support JDBC master slave on MySQL

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1074?page=comments#action_37583 ] 

james strachan commented on AMQ-1074:
-

Patch applied to trunk - which seems to work for me with MySQL Connector/J 
5.0.4.

> support JDBC master slave on MySQL
> --
>
> Key: AMQ-1074
> URL: https://issues.apache.org/activemq/browse/AMQ-1074
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: james strachan
> Fix For: 4.2.0
>
>
> We need to make a few changes to support MySQL's SQL dialect for JDBC Master 
> Slave...
> http://incubator.apache.org/activemq/jdbc-master-slave.html
> For details see this thread...
> http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: (AMQ 992) DefaultDatabaseLocker and mysql

[James Strachan]

On 11/21/06, slotito <[EMAIL PROTECTED]> wrote:


Hi,

I am trying to get MySQL to work in the Master/Slave JDBC configuration -
the default sql does not lock the table properly.

I added a MysqlJDBCAdapter that extends
org.apache.activemq.store.jdbc.adapter.DefaultJDBCAdapter so I could
override the lockCreateStatement.

I then edited the resources so that the mysql-ab_jdbc_driver would use the
MysqlJDBCAdapter instead of the DefaultJDBCAdapter.

The new locking statement is: LOCK TABLE ACTIVEMQ_LOCK WRITE  (which works
in MySQL 5.x at least)

Unfortunately, once I run it with the new code, it gets stuck in the
following block (from org.apache.activemq.store.jdbc.DefaultDatabaseLocker)

PreparedStatement statement =
connection.prepareStatement(statements.getLockCreateStatement());
while (true) {
try {
log.info("Attempting to acquire the exclusive lock to become
the Master broker");
boolean answer = statement.execute();
if (answer) {
break;
}
}
catch (Exception e) {
if (stopping) {
throw new Exception("Cannot start broker as being asked
to shut down. Interupted attempt to acquire lock: " + e, e);
}
log.error("Failed to acquire lock: " + e, e);
}
log.debug("Sleeping for " + sleepTime + " milli(s) before trying
again to get the lock...");
Thread.sleep(sleepTime);
}

Unlike the original SQL ("SELECT* FROM ACTIVEMQ_LOCK FOR UPDATE"), the lock
table command for Mysql doesn't return a ResultSet.  This means that
"answer" above will always be false, even though the table is successfully
locked, and it basically goes into an infinite loop "Attempting to
acquire...".

(see
http://java.sun.com/j2se/1.4.2/docs/api/java/sql/Statement.html#execute(java.lang.String))

I see three ways to get this working, but I might be missing something.
I've never contributed anything to this project so I'd like to get some
advice from you guys.

1) I'm pretty sure it is possible to allow multiple queries in a statement
through the use of a connection string parameter (?allowMultiQueries=true)
in the mysql driver - i.e. it would allow "LOCK TABLE ACTIVEMQ_LOCK WRITE;
SELECT * FROM ACTIVEMQ_LOCK" which would return a ResultSet and set "answer"
to true.  This would just be a documentation effort, basically making sure
anyone using the Master/Slave JDBC configuration with MySQL knows to set
that connection parameter.

2) I could create a MysqlDatabaseLocker and the necessary resource/config
changes, then override that method and remove the "answer" part.  This seems
like overkill since none of the other databases seem to require their own at
this point.

3) I could remove the boolean answer from the DefaultDatabaseLocker.  Is it
currently necessary?  If there's anything kind of database access error, it
will just throw a SQLException anyway.  Other connections will wait for the
lock to become available before they return from the statement.execute(),
right?

Any thoughts on this?


Thanks for this great contribution Steve!

Firstly - I've raised a JIRA to track this issue...
http://issues.apache.org/activemq/browse/AMQ-1074

I agree with 3), I think we should ignore the check for a result set
on the SQL statement. I've made this change in trunk now which should
help. I've also committed your patch to trunk - providing a
MySqlJDBCAdapter which uses the SQL you so kindly submitted for the
exclusive lock. I tried it on my machine with MySQL Connector/J 5.0.4
and it seemed to work great.

I wonder could you see if it works for you? If so we can close the issue.

--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37581 ] 

james strachan commented on AMQ-1054:
-

Shoaib - I wonder could you try using ActiveMQ trunk (or tomorrows nightly 
snapshot build of 4.2-SNAPSHOT) to see if I've fixed the bug for you on your 
environment? I think I've nailed the ClassCastException you're seeing - am just 
not yet sure of the magic incantations to reproduce it so I can know for sure 
its fixed

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37580 ] 

james strachan commented on AMQ-1054:
-

Hi Guy

Just to be sure - are you saying the bug doesn't happen for you on OSX/Unix? 
i.e. its a windows only bug?

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1074) support JDBC master slave on MySQL

[james strachan (JIRA)]

support JDBC master slave on MySQL
--

 Key: AMQ-1074
 URL: https://issues.apache.org/activemq/browse/AMQ-1074
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: james strachan
 Fix For: 4.2.0


We need to make a few changes to support MySQL's SQL dialect for JDBC Master 
Slave...

http://incubator.apache.org/activemq/jdbc-master-slave.html

For details see this thread...
http://www.nabble.com/%28AMQ-992%29-DefaultDatabaseLocker-and-mysql-tf2682498.html#a7482369

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37576 ] 

james strachan commented on AMQ-1054:
-

Just to make absolutely sure, I've added the test case into the 4.0 branch too

https://svn.apache.org/repos/asf/incubator/activemq/branches/activemq-4.0/activemq-test-atomikos/

and the test case works fine. I wonder if these tests fail on a specific 
platform only? I wonder could someone try running these test cases on Windows 
(am an OS X / unix person myself)

BTW I tried Java 1.4.2 with the 4.0 branch (which is basically 4.0.2)



> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1054?page=all ]

james strachan updated AMQ-1054:


Attachment: pom.xml

This pom.xml replaces the one in activemq-test-atomikos to run against 4.0.2 of 
ActiveMQ

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37574 ] 

james strachan commented on AMQ-1054:
-

FWIW I've tried the same test case against 4.0.2 as well and it works fine. I'm 
attaching the pom.xml file you can use in the activemq-test-atomikos directory 
to run the test case against 4.0.2 of ActiveMQ.

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
> Attachments: pom.xml
>
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Latest official release

[James Strachan]

On 11/28/06, nabble615 <[EMAIL PROTECTED]> wrote:


Hi, may I know whether the latest official activemq release is 4.0.2?


Currently yes. The 4.1 release is still in voting; its looking good so
hopefully should pass in the next day or so


 May I
know when is the released date of it as well? Thanks


It was released a few weeks ago
http://www.nabble.com/-ANN--Apache-ActiveMQ-4.0.2-released%21-tf2627759.html

--

James
---
http://radio.weblogs.com/0112098/

Re: communicating with Topic subscribers from custom interceptor class

[James Strachan]

On 11/27/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:

Hello,
   Thanks for your great work on ActiveMQ!


Thanks! :)



   I'm writing a custom interceptor that extends BrokerFilter in order
to process messages that are published to particular Topics.  My
question is, how can my interceptor make a direct connection with the
JMS client that published the message?


What kind of thing are you trying to do?



Does the subscriber have to
manually set an identifier in order to be accessible, or are the
identifiers automatically generated?


Subscribers are visible in JMX or the BrokerService via their unique
generated consumerId's.



   Additionally, is there a way to access the list of subscribers to a
particular topic and send messages to individual subscribers from a
custom interceptor class?


Not easily. What are you trying to do - maybe there's an easier way.

--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-1054) XA recover fails for 4.0.1

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1054?page=comments#action_37566 ] 

james strachan commented on AMQ-1054:
-

h3. Guy

I've added your test case to subversion...

https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-test-atomikos/

Unfortunately it works perfectly against trunk. I'm guessing the test case only 
fails if you have XA transactions to recover?


h3. Shoaib 

Thanks for the great diagnosis! Yeah that line of code does look suspicious. 
I've patched the code in trunk to avoid the ClassCastException - though I'm not 
too sure how to reproduce the bug yet. I wonder could you try trunk and see if 
it now works for you?

> XA recover fails for 4.0.1
> --
>
> Key: AMQ-1054
> URL: https://issues.apache.org/activemq/browse/AMQ-1054
> Project: ActiveMQ
>  Issue Type: Bug
> Environment: Java, JDK 1.4, Windows, Atomikos TransactionsEssentials 
> for the JTA/XA part
>Reporter: Guy Pardon
>
> XAResource.recover seems to fail for 4.x of ActiveMQ:
> ERROR IN RECOVERY [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 
> 08:43:35,152 
> [Lorg.apache.activemq.command.DataStructure; [thread: 
> SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: 
> org.apache.activemq.TransactionContext.recover(TransactionContext.java:508) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.recover(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.datasource.xa.XATransactionalResource.endRecovery(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,152 
> at: com.atomikos.icatch.imp.TransactionServiceImp.recover(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: 
> com.atomikos.datasource.xa.XATransactionalResource.setRecoveryService(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.icatch.system.Configuration.addResource(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.checkSetup(Unknown Source) 
> [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createQueueConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> at: com.atomikos.jms.QueueConnectionFactoryBean.createConnection(Unknown 
> Source) [thread: SimpleAsyncTaskExecutor-3] on: 06-11-16 08:43:35,153 
> Also see http://www.atomikos-support.com/forums/viewtopic.php?t=351 (where I 
> borrowed this stack trace from). We have seen similar things in other 
> applications that tried to use ActiveMQ. I think this is a class cast error 
> in ActiveMQ...
> With 3.1 there is no problem. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1068) DestinationMap seems to use up lots of RAM if using deep hierarchies

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1068?page=comments#action_37564 ] 

james strachan commented on AMQ-1068:
-

The fix was done in r478324 on trunk if folks wanna backport

> DestinationMap seems to use up lots of RAM if using deep hierarchies
> 
>
> Key: AMQ-1068
> URL: https://issues.apache.org/activemq/browse/AMQ-1068
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1.0, 4.0.2
>    Reporter: james strachan
>     Assigned To: james strachan
> Fix For: 4.2.0
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1073) support selectors in virtual destinations to allow a message to be dispatched to multiple phyiscal queues if it matches the selector

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1073?page=all ]

james strachan resolved AMQ-1073.
-

Resolution: Fixed

For documentation see http://activemq.org/site/virtual-destinations.html

> support selectors in virtual destinations to allow a message to be dispatched 
> to multiple phyiscal queues if it matches the selector
> 
>
> Key: AMQ-1073
> URL: https://issues.apache.org/activemq/browse/AMQ-1073
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>    Reporter: james strachan
>     Assigned To: james strachan
> Fix For: 4.2.0
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Message Expiry

[James Strachan]

On 11/25/06, Sergey <[EMAIL PROTECTED]> wrote:


Hallo,

I've got the same problem. Expiration dosn't seem to work. I'm using 4.0.2.


Have you tried trunk or 4.1?

--

James
---
http://radio.weblogs.com/0112098/

pluggable MessageTransformer available in trunk

[James Strachan]

Which allows you to transform messages as they go onto the message bus
or as a JMS client takes them off the bus.

They are described more fully here...

http://activemq.org/site/message-transformation.html

The idea is so that you can use ObjectMessage in your code; but then
if you wish to avoid Java serialization at deployment time you could
configure your connection factory so that the actual messages which
make it onto the bus are of type TextMessage and use XML via XStream
(via the XStreamMessageTransformer) or via JAXB2 to contain the data
etc.

Feedback greatly appreciated
--

James
---
http://radio.weblogs.com/0112098/

[jira] Created: (AMQ-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus

[james strachan (JIRA)]

allow a MessageTransformer to be registered with a producer or consumer to help 
transform a message going onto the bus or coming off the bus


 Key: AMQ-1053
 URL: https://issues.apache.org/activemq/browse/AMQ-1053
 Project: ActiveMQ
  Issue Type: New Feature
Reporter: james strachan
 Assigned To: james strachan


For example a user may wish to use ObjectMessage in their code - but in 
deployment use a TextMessage with XStream or JAXB as the marshalling.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (AMQ-1053) allow a MessageTransformer to be registered with a producer or consumer to help transform a message going onto the bus or coming off the bus

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1053?page=all ]

james strachan updated AMQ-1053:


Fix Version/s: 4.2.0

> allow a MessageTransformer to be registered with a producer or consumer to 
> help transform a message going onto the bus or coming off the bus
> 
>
> Key: AMQ-1053
> URL: https://issues.apache.org/activemq/browse/AMQ-1053
> Project: ActiveMQ
>  Issue Type: New Feature
>    Reporter: james strachan
>     Assigned To: james strachan
> Fix For: 4.2.0
>
>
> For example a user may wish to use ObjectMessage in their code - but in 
> deployment use a TextMessage with XStream or JAXB as the marshalling.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1051) be able to interact with the broker via messaging

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1051?page=comments#action_37455 ] 

james strachan commented on AMQ-1051:
-

Code checked in - could use some documentation.

Currently if you can send a message to the Topic *ActiveMQ.Agent* it will be 
interpreted as an activemq-console command. So the following kinds of commands 
are available

* help
* list
* query
* browse

etc.

I've tested it with XMPP so you can chat via Jabber to the broker! :)

http://incubator.apache.org/activemq/xmpp.html

The best way to get started is to run the web console

http://incubator.apache.org/activemq/web-console.html

> be able to interact with the broker via messaging
> -
>
> Key: AMQ-1051
> URL: https://issues.apache.org/activemq/browse/AMQ-1051
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker
>Reporter: james strachan
>
> Send a text message over JMS, XMPP, Stomp, Ajax or REST to communicate with 
> the broker, query queues/topics etc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1051) be able to interact with the broker via messaging

[james strachan (JIRA)]

be able to interact with the broker via messaging
-

 Key: AMQ-1051
 URL: https://issues.apache.org/activemq/browse/AMQ-1051
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker
Reporter: james strachan


Send a text message over JMS, XMPP, Stomp, Ajax or REST to communicate with the 
broker, query queues/topics etc.




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1050) browse -QTopic=* does not seem to return anything...

[james strachan (JIRA)]

browse -QTopic=* does not seem to return anything...


 Key: AMQ-1050
 URL: https://issues.apache.org/activemq/browse/AMQ-1050
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.x
Reporter: james strachan
 Assigned To: Adrian Co
 Fix For: 4.2.0


I think there's something funny going on in the regex stuff. I tried from the 
SimpleConsole typing

  query -QTopic=*

and I get nothing. 

  query 

returns tons of stuff though.

I wonder if it might be simpler to have specific arguments for topic and 
queues? 

query -topic=*
queyr -queue=*

to avoid the complex regex of ObjectName etc?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Switching to ActiveMQ 4.2 to Java 5???

[James Strachan]

It'd be good to use annotations for the xbean stuff

On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

On 11/15/06, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> Sounds good.
> Do you plan to refactor some code to use generics, or other
> Java 5 features ?

At a minimum we should switch to the Java 1.5 concurrent package.
Switch generics has an upside that it will make our code more type
safe but a downside that merging patches from 4.2.x <-> 4.1.x will be
more difficult.

How about annotations?? any places where you think those would make more sense?

>
> On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> > Hi folks,
> >
> > How do you guys feel about switching the minimum run time requirement
> > for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> > has a much better set of concurrent implementation.
> >
> > We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
> >  Also I have a feeling that once we switch to Java 5, someone will
> > figure out how to use retrotranslator to make our Java 5 binaries also
> > run on Java 1.4.  But I doubt anybody will make any efforts to look
> > into that until we actually jump to Java 5.
> >
> > So what do you say?  Shall we switch ??
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
>
>
> --
> Cheers,
> Guillaume Nodet
>


--
Regards,
Hiram

Blog: http://hiramchirino.com




--

James
---
http://radio.weblogs.com/0112098/

chatting with the Broker over Jabber / XMPP

[James Strachan]

I've added a  to the broker's activemq.xml which allows
you to communicate with a broker over a JMS topic (ActiveMQ.Agent) to
send management commands using a simple text based system.

Its currently reusing the commands in the activemq-console module.
(Incidentally I added a SimpleConsole so you can boot up a simple
interactive shell in your IDE easily and communicate with a remote
broker to try out the commands). So you can type commands like 'help',
'list', 'browse' etc.

This allows folks to send messages on this topic and if the JMSReplyTo
is specified, a message is returned with the results.

I've patched the xmpp transport so that you can now use a jabber
client to talk to the broker :). Just join the room ActiveMQ.Agent and
chat away!

To get XMPP to work nicely I create a temporary queue and subscription
to that queue which can then be used for any inbound messages. It
might be nice to do this for Stomp too - though I guess a stomp client
could create a temporary topic & subscribe to it itself.

Though it would be kinda nice to not have to do that.

e.g. in Stomp we could do...

SEND
destination:/topic/ActiveMQ.Agent

help
^@

and immediately get the list of commands.

--

James
---
http://radio.weblogs.com/0112098/

Re: Switching to ActiveMQ 4.2 to Java 5???

[James Strachan]

Agreed. Its very easy to use the 1.5 bytecode on 1.4 without any work
by just installing the retrotranslator JIT :)


On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

On 11/15/06, James Strachan <[EMAIL PROTECTED]> wrote:
> +1.
>
> We should switch to Java 5 for compilation and for the default release
> (since the concurrent stuff is  faster & more bug free on Java 5) but
> maybe provide a retrotranslator version of the jars for those who
> can't move JVM.
>
> i.e. build on Java 5 only - but allow deployments on 1.4
>

I agree.. but I don't want to condition the switch to 1.5 on getting
the retrotranslator stuff working first.  If we get the
retrotranslator stuff working.. well that should just be the gravy.

> On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> > Hi folks,
> >
> > How do you guys feel about switching the minimum run time requirement
> > for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
> > has a much better set of concurrent implementation.
> >
> > We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
> >  Also I have a feeling that once we switch to Java 5, someone will
> > figure out how to use retrotranslator to make our Java 5 binaries also
> > run on Java 1.4.  But I doubt anybody will make any efforts to look
> > into that until we actually jump to Java 5.
> >
> > So what do you say?  Shall we switch ??
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
>
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>


--
Regards,
Hiram

Blog: http://hiramchirino.com




--

James
---
http://radio.weblogs.com/0112098/

Re: Switching to ActiveMQ 4.2 to Java 5???

[James Strachan]

+1.

We should switch to Java 5 for compilation and for the default release
(since the concurrent stuff is  faster & more bug free on Java 5) but
maybe provide a retrotranslator version of the jars for those who
can't move JVM.

i.e. build on Java 5 only - but allow deployments on 1.4

On 11/15/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Hi folks,

How do you guys feel about switching the minimum run time requirement
for ActiveMQ 4.2 to be Java 5??  I'm itching to do this since Java 5
has a much better set of concurrent implementation.

We can keep the 4.1.x branch alive as the Java 1.4 compatible version.
 Also I have a feeling that once we switch to Java 5, someone will
figure out how to use retrotranslator to make our Java 5 binaries also
run on Java 1.4.  But I doubt anybody will make any efforts to look
into that until we actually jump to Java 5.

So what do you say?  Shall we switch ??

--
Regards,
Hiram

Blog: http://hiramchirino.com




--

James
---
http://radio.weblogs.com/0112098/

Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)

[James Strachan]

+1

Looks good to me.

On 11/14/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Hey folks,

I was able to finally get around to doing a binary release candidate
from the 4.1 branch.

it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2/m2-incubating-repository/org/apache/activemq/apache-activemq/4.1.0-incubator/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.1.0-RC2

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-410-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.1.0
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1


--
Regards,
Hiram

Blog: http://hiramchirino.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--

James
---
http://radio.weblogs.com/0112098/

[VOTE RESULT] Release Apache ActiveMQ 4.0.2 (RC 6)

[James Strachan]

With 3 binding +1s and 7 +1s from the PPMC I think we've finally got
the 4.0.2 release approved!  :)


On 11/8/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:

+1 from me.

-- dims

On 11/8/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
> Hiram,
>
> I pulled the versions from your personal site and looked at the
> tar.gz files.  The server started fine and from a user perspective it
> looks great.
>
> The LICENSE information seems to be correct.  The only nit is that
> the NOTICE file does not have a .txt on the end like the other files.
>
> I'd vote +1.
>
> Looks good.
>
> Matt
>
> On Nov 8, 2006, at 2:34 PM, Hiram Chirino wrote:
>
> > Unless I'm lossing email... I think we still need a few more votes
> > from incubator pmc members to make this release official.  Anybody
> > around that can help check this release??
> >
> > On 10/29/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> >> Some last minute NOTICE issues were still present in the 5th release
> >> candidate of the
> >> 4.0.2 build.  We have also received confirmation from Apache legal
> >> discuss that it's ok to include work covered by the "Creative Commons
> >> Attribution" license.  I have cut and RC 6 of the 4.0.2 build with
> >> the
> >> fixes and it's available here:
> >>
> >> http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6/
> >> maven1/incubator-activemq/distributions/
> >>
> >> Maven 1 and Maven 2 repos for this release can be found at:
> >> http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6
> >>
> >> Here's the wiki page for the release notes:
> >> http://incubator.apache.org/activemq/activemq-402-release.html
> >>
> >> Please vote to approve this release binary
> >>
> >> [ ] +1 Release the binary as Apache ActiveMQ  4.0.2
> >> [ ] -1 Veto the release (provide specific comments)
> >>
> >> This vote is being cross posted to the general incubator mailing list
> >> also to expedite the voting process.
> >>
> >> Here's my +1
> >>
> >> --
> >> Regards,
> >> Hiram
> >>
> >> Blog: http://hiramchirino.com
> >>
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> Matt Hogstrom
> [EMAIL PROTECTED]
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--

James
---
http://radio.weblogs.com/0112098/

Re: newbie request for help - custom server implementation in ActiveMQ?

[James Strachan]

On 11/9/06, J. Patrick Bedell <[EMAIL PROTECTED]> wrote:

Hello,
   I am interested in using ActiveMQ to develop a market for
information currency (http://infoeng.sourceforge.net).  I'm a real
ActiveMQ/Spring newbie, so I'm not very clear on how to create a POJO
to serve as a filter for certain messages sent to the server.


I don't really understand the question I'm afraid.
--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-1017) Build of current trunk with Maven2 fails

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37392 ] 

james strachan commented on AMQ-1017:
-

I guess we need someone else with a windows machine to trash their local repo 
and try again - it could be a windows-only-with-no-local-repo issue

> Build of current trunk with Maven2 fails
> 
>
> Key: AMQ-1017
> URL: https://issues.apache.org/activemq/browse/AMQ-1017
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1
> Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06
>Reporter: Bernhard Wellhöfer
>Priority: Critical
> Attachments: mvn.log, mvn.log, mvn.log
>
>
> A build of a fresh checkout from 
> https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. 
> See the attached log of the build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1017) Build of current trunk with Maven2 fails

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37391 ] 

james strachan commented on AMQ-1017:
-

I've tried trashing the local repo too - and it still works fine for me. I'm 
kinda mystified why its failing for you.

> Build of current trunk with Maven2 fails
> 
>
> Key: AMQ-1017
> URL: https://issues.apache.org/activemq/browse/AMQ-1017
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1
> Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06
>Reporter: Bernhard Wellhöfer
>Priority: Critical
> Attachments: mvn.log, mvn.log, mvn.log
>
>
> A build of a fresh checkout from 
> https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. 
> See the attached log of the build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Creating a 4.1 Branch

[James Strachan]

+1.

4.1 is long overdue (as is getting the 4.0.2 release out of the door too :)

On 11/8/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Well folks,

I think it's about time we get serious about doing a 4.1 release.  In
that effort I'm going to create a 4.1 branch in SVN unless anybody has
an objection.  Please let me know!

--
Regards,
Hiram

Blog: http://hiramchirino.com




--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-1036) web-console broken (queue browsing).

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1036?page=comments#action_37369 ] 

james strachan commented on AMQ-1036:
-

Which version are you using? Its working for me on the 4.1-SNAPSHOT

> web-console broken (queue browsing).
> 
>
> Key: AMQ-1036
> URL: https://issues.apache.org/activemq/browse/AMQ-1036
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: incubation
>Reporter: Dave Syer
>
> I managed to build and launch the web-console from svn, but the queue 
> browsing page is broken - queue.jsp uses properties of Queue e.g. ${row.size} 
> that do not exist.  When I hacked queue.jsp to remove references to those 
> properties I got another error on trying to purge a queue:
> RequestURI=/activemq-web-console/purgeDestination.action
> Caused by:
> java.lang.IllegalArgumentException: Target bean must not be null
>   at org.springframework.util.Assert.notNull(Assert.java:113)
>   at 
> org.springframework.validation.BeanPropertyBindingResult.(BeanPropertyBindingResult.java:58)
>   at 
> org.springframework.validation.DataBinder.initBeanPropertyAccess(DataBinder.java:167)
>   at 
> org.springframework.validation.DataBinder.getInternalBindingResult(DataBinder.java:186)
>   at 
> org.springframework.validation.DataBinder.getPropertyAccessor(DataBinder.java:196)
>   at 
> org.springframework.validation.DataBinder.applyPropertyValues(DataBinder.java:515)
>   at org.springframework.validation.DataBinder.doBind(DataBinder.java:417)
>   at 
> org.springframework.web.bind.WebDataBinder.doBind(WebDataBinder.java:146)
>   at 
> org.springframework.web.bind.ServletRequestDataBinder.bind(ServletRequestDataBinder.java:108)
>   at 
> org.apache.activemq.web.handler.BindingBeanNameUrlHandlerMapping.getHandlerInternal(BindingBeanNameUrlHandlerMapping.java:43)
> ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1034) bad acknowledgement messages when rolling back on a large queue

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1034?page=all ]

james strachan resolved AMQ-1034.
-

Fix Version/s: 4.0.3
   4.1
   Resolution: Fixed

hiram fixed this in trunk revision 472345.

I've just back ported it to 4.0.x in revision: 472423

> bad acknowledgement messages when rolling back on a large queue
> ---
>
> Key: AMQ-1034
> URL: https://issues.apache.org/activemq/browse/AMQ-1034
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0.2, 4.1
>    Reporter: james strachan
> Assigned To: james strachan
> Fix For: 4.0.3, 4.1
>
>
> See the test case RollbacksWhileConsumingLargeQueueTest for details of how to 
> reproduce

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1034) bad acknowledgement messages when rolling back on a large queue

[james strachan (JIRA)]

bad acknowledgement messages when rolling back on a large queue
---

 Key: AMQ-1034
 URL: https://issues.apache.org/activemq/browse/AMQ-1034
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.2, 4.1
Reporter: james strachan
 Assigned To: james strachan


See the test case RollbacksWhileConsumingLargeQueueTest for details of how to 
reproduce

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-1017) Build of current trunk with Maven2 fails

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-1017?page=comments#action_37357 ] 

james strachan commented on AMQ-1017:
-

The build works perfectly for me on OS X and Linux. I guess it must be some 
windows issue.

I wonder does trashing your ~/.m2/repository help? Am wondering if you've got 
some old version of some jar in your local repo? You definitely have the latest 
from trunk right?


> Build of current trunk with Maven2 fails
> 
>
> Key: AMQ-1017
> URL: https://issues.apache.org/activemq/browse/AMQ-1017
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 4.1
> Environment: Windows XP, Maven 2.0.4, Java 1.5.0_06
>Reporter: Bernhard Wellhöfer
>Priority: Critical
> Attachments: mvn.log
>
>
> A build of a fresh checkout from 
> https://svn.apache.org/repos/asf/incubator/activemq/trunk with Maven2 fails. 
> See the attached log of the build.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Release schedule

[James Strachan]

On 11/6/06, Vadim Pesochinsky <[EMAIL PROTECTED]> wrote:


Hi!

Any updates on when 4.1 will be ready?


The code's been ready a while now (rather like 4.0.2)- we just need to
wait for the 4.0.2 release to get out, then we can call a vote for 4.1

--

James
---
http://radio.weblogs.com/0112098/

Re: [VOTE] Release Apache ActiveMQ 4.0.2 (RC 6)

[James Strachan]

+1

On 10/30/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Some last minute NOTICE issues were still present in the 5th release
candidate of the
4.0.2 build.  We have also received confirmation from Apache legal
discuss that it's ok to include work covered by the "Creative Commons
Attribution" license.  I have cut and RC 6 of the 4.0.2 build with the
fixes and it's available here:

http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6/maven1/incubator-activemq/distributions/

Maven 1 and Maven 2 repos for this release can be found at:
http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC6

Here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-402-release.html

Please vote to approve this release binary

[ ] +1 Release the binary as Apache ActiveMQ  4.0.2
[ ] -1 Veto the release (provide specific comments)

This vote is being cross posted to the general incubator mailing list
also to expedite the voting process.

Here's my +1

--
Regards,
Hiram

Blog: http://hiramchirino.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--

James
---
http://radio.weblogs.com/0112098/

XMPP support (Jabber) available in the main trunk

[James Strachan]

Just a heads up, I've added XMPP support back into ActiveMQ (we had
some experimental support a long time go that's been sitting in the
sandbox for a while).

This allows any Jabber application (or GoogleTalk) to communicate with
the ActiveMQ broker. Currently all names in XMPP map to Topics; am
sure we can figure out a way to support queues as well later on.

There's some documentation and a demo walk through available here...

http://activemq.org/site/xmpp.html

The nice thing about the XMPP support is you can use your Jabber
client as a quick way to test out your installation & watch things
happening in development etc.

--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-40) jabber support as client & server

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-40?page=comments#action_37289 ] 

james strachan commented on AMQ-40:
---

FWIW in 4.1 its now via xmpp://host:port

For more details see
http://activemq.org/site/xmpp.html

> jabber support as client & server
> -
>
> Key: AMQ-40
> URL: https://issues.apache.org/activemq/browse/AMQ-40
> Project: ActiveMQ
>  Issue Type: New Feature
>Reporter: james strachan
>Priority: Minor
> Fix For: 3.1
>
>
> we now support a new transport
> jabber://localhost:61606
> which allows a Jabber client to connect to ActiveMQ and talk Jabber (XMPP) to 
> the ActiveMQ broker. This allows any Jabber client in any language to talk 
> natively to ActiveMQ.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-506) Jabber transport missing

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-506?page=all ]

james strachan resolved AMQ-506.


Fix Version/s: 4.1
   (was: 4.2)
   Resolution: Fixed

Now back as activemq-xmpp

> Jabber transport missing
> 
>
> Key: AMQ-506
> URL: https://issues.apache.org/activemq/browse/AMQ-506
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Transport
>Affects Versions: 4.0 M4
>Reporter: Guillaume Nodet
> Fix For: 4.1
>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-1007?page=all ]

james strachan resolved AMQ-1007.
-

Resolution: Fixed

The activemq-xmpp module provides the functionality, for documentation see

http://activemq.org/site/xmpp.html

> XMPP support (Jabber support) so existing Jabber clients can be used to 
> interact with and monitor ActiveMQ messages
> ---
>
> Key: AMQ-1007
> URL: https://issues.apache.org/activemq/browse/AMQ-1007
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Transport
>    Reporter: james strachan
>     Assigned To: james strachan
> Fix For: 4.1
>
>
> This is particularly useful for demos or testing things out in development.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Created: (AMQ-1007) XMPP support (Jabber support) so existing Jabber clients can be used to interact with and monitor ActiveMQ messages

[james strachan (JIRA)]

XMPP support (Jabber support) so existing Jabber clients can be used to 
interact with and monitor ActiveMQ messages
---

 Key: AMQ-1007
 URL: https://issues.apache.org/activemq/browse/AMQ-1007
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Transport
Reporter: james strachan
 Assigned To: james strachan
 Fix For: 4.1


This is particularly useful for demos or testing things out in development.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: ActiveMQ can now support AMQP clients.

[James Strachan]

Great work Hiram!

On 10/21/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Hey Folks,

Just wanted to give you an update on the progress that ActiveMQ is making in
supporting AMQP clients.  I have taken most of the java code from the qpid
project and done some major refactoring to it so that it's more inline with
the ActiveMQ architecture.  It now uses the ActiveMQ transport, wireformat,
broker service, connector, and configuration patterns.  So now it is
possible to have your ActiveMQ broker support both standard ActiveMQ clients
and AMQP clients like the qpid implemented java and C++ clients.

The stuff that still missing is that the AMQP messages are in separate
messaging domain from the ActiveMQ messages.  The next set of work that's
still pending is :
 - Need to add Unit tests!
 - integrating the messaging domains
 - implementing the AMQP persistence using ActiveMQ's message stores
 - porting the sasl implementation in qpid (big refactor needed to make it
IOC configured).
 - and once we are happy with all the integration and everything is pretty
stable, JMXify it!

Please note that the AMQP spec is still moving so the latest qpid's clients
may no long be compatible with this work, (I've been testing against qpid
sources about 3 weeks old.)  Hopefully qpid will do a milestone release soon
and then I'll port the protocol changes that I've missed when they do that.

If anybody wants to pitch in and help, here's where our amqp/qpid
integration module is located in svn:
http://svn.apache.org/viewvc/incubator/activemq/sandbox/qpid

--
Regards,
Hiram

Blog: http://hiramchirino.com





--

James
---
http://radio.weblogs.com/0112098/

Re: NMS Provider for Tibco EMS?

[James Strachan]

On 10/20/06, Dave68 <[EMAIL PROTECTED]> wrote:


Hi James and Hiram, thanks for the quick response!

The Tibco EMS server does come with c# APIs and example client code when you
download their evaluation server.  Take a look at
http://cf.tibco.com/eval/RegEval.cfm

I really want to use NMS instead so that in future the application can also
support other servers such as ActiveMQ, Sun, JBoss, etc.


Awesome! Sounds like a great idea!

--

James
---
http://radio.weblogs.com/0112098/

Re: NMS Provider for Tibco EMS?

[James Strachan]

On 10/20/06, Dave68 <[EMAIL PROTECTED]> wrote:


Hi, am I correct in thinking that the current NMS source supports the Apache
ActiveMQ server only?  I would like to write a client that can talk to a
Tibco EMS server.  Do I have to implement a provider in order to do this, or
is there one already available?  If so how do I go about it?  Would the
provider reside on the server or the client?  Unfortunately bridging from
Apache to Tibco is not an option.  Can a client support multiple providers
at one time?


So we've got a provider so far for ActiveMQ via OpenWire and a
provider for MSMQ. So am sure we can write a provider for TibCo too -
we just need to figure out how to actually talk to EMS from .Net. Is
there a C# client we could use?

--

James
---
http://radio.weblogs.com/0112098/

Re: Separate client/server packages...

[James Strachan]

On 10/4/06, Komandur <[EMAIL PROTECTED]> wrote:

Is there a  way to generate a light weight clientside package (without any
broker specifics) when a version is released ?


You could try patching the maven build to make a new smaller client
jar if you like?


--

James
---
http://radio.weblogs.com/0112098/

Re: how to use failover url protocol in STOMP C client

[James Strachan]

BTW Stomp based failover should also re-submit any in-progress
operations - e.g. to resume any SUBSCRIBE's. If you are supporting
transactions, you should replay any non-complete transactions too.

On 10/2/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:

Just checked again .. and yep it's there.

Follow the use of the "reliable" variable.  when set to true, it acts
very similar to how failover acts.  When a failure occurs it keeps
trying to reconnect to the broker.  And that's basically the hard part
of faiover, the only other thing that failover does is on failure it
chooses a different host to connect to from a list.


On 10/2/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote:
> I looked into the ruby code; it looks to me plain STOMP message
> implementation. I don't see any specific implementation to failover
> protocol.
>
> Any idea?
>
> Vik
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
> Chirino
> Sent: Monday, October 02, 2006 11:55 AM
> To: activemq-dev@geronimo.apache.org
> Subject: Re: how to use failover url protocol in STOMP C client
>
> Seems that the ruby code was moved recently so it could be
> independently released.. here's where it lives now:
>
> http://svn.codehaus.org/stomp/ruby/trunk/
>
>
> On 10/2/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]>
> wrote:
> > Hiram,
> >
> > I can't access the Ruby code on STOMP's website. When I click on
> source
> > link on the "Stomp Client for Ruby page" it gives me a "Not Found
> > error".
> >
> > Please let me know, I was getting ready to work on failover for STOMP
> C
> > client and wanted to see how it is implemented in Ruby client.
> >
> > Thanks!
> >
> >
> >
> > Vik
> >
> > -Original Message-
> > From: Dhawan, Vikram (LNG-DAY) [mailto:[EMAIL PROTECTED]
> > Sent: Monday, September 25, 2006 10:18 AM
> > To: activemq-dev@geronimo.apache.org
> > Subject: RE: how to use failover url protocol in STOMP C client
> >
> > Hi Hiram,
> >
> > I will do that. BTW I had another question and haven't got any
> response
> > yet... this is about message selector in STOMP C clients. Because of
> > some reason I can't get it work. Can you provide me some sample? As
> far
> > as my understanding I am setting the selector at the SUBSCRIBE command
> > and it should work.
> >
> > Thanks!
> >
> > Vik
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hiram
> > Chirino
> > Sent: Friday, September 22, 2006 7:37 PM
> > To: activemq-dev@geronimo.apache.org
> > Subject: Re: how to use failover url protocol in STOMP C client
> >
> > Hi Vikram,
> >
> > Not implemented in the stomp C client yet.  If you want to take a
> > cracked at implementing it yourself, you might want to peek at how it
> > was implemented in the stomp ruby client.
> >
> > On 9/22/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]>
> > wrote:
> > > Hi,
> > >
> > >
> > >
> > > I want to know can I use same failover protocol URL syntax in STOMP
> C
> > > clients.  And will it work the way failover is described in the AMQ
> > > documentation.
> > >
> > >
> > >
> > > Thanks!
> > >
> > >
> > >
> > > Vik
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Regards,
> > Hiram
> >
> > Blog: http://hiramchirino.com
> >
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>


--
Regards,
Hiram

Blog: http://hiramchirino.com




--

James
---
http://radio.weblogs.com/0112098/

[jira] Resolved: (AMQ-950) createConnector="false" has no effect on Tiger

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-950?page=all ]

james strachan resolved AMQ-950.


Resolution: Fixed

Patch applied - many thanks Renaud.

BTW could you double check my version of your patch works - I only create a 
connector if result != null and createConnector is true.



> createConnector="false" has no effect on Tiger
> --
>
> Key: AMQ-950
> URL: https://issues.apache.org/activemq/browse/AMQ-950
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1
> Environment: JDK 1.5.0_08
>Reporter: Renaud Bruyeron
>Priority: Minor
> Fix For: 4.1
>
>
> On Tiger, activemq always creates a rmi connector on port 1099 no matter what 
> I do with -Djavax.management... and 
> In particular, setting createConnector="false" should prevent AMQ from 
> setting up its own connector, but it does not.
> The problem is in the findMBeanServer() method:
> if (result == null && createMBeanServer) {
> result = createMBeanServer();
> }
> else {
> createConnector(result);
> }
> result is not null on Tiger with useJmx="true", and createConnector is not 
> protected by if(createConnector) like it is on the non-Tiger flow.
> The fix (I think) is simply to do this:
> if (result == null && createMBeanServer) {
> result = createMBeanServer();
> }
> else {
> if(createConnector){
>   createConnector(result);
> }
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Problem on setting destination queue at startup

[James Strachan]

On 9/27/06, Christopher_Ong <[EMAIL PROTECTED]> wrote:


06-Jul-2006 00:00


Thats pretty old, try a newer one build in September

--

James
---
http://radio.weblogs.com/0112098/

Re: Problem on setting destination queue at startup

[James Strachan]

On 9/27/06, Christopher_Ong <[EMAIL PROTECTED]> wrote:


I am using apache-incubator-activemq-4.1-SNAPSHOT and not 4.02, and the error
is what I posted earlier.


Are you sure you are using the right one from here?

http://people.apache.org/maven-snapshot-repository/org/apache/activemq/apache-activemq/4.1-incubator-SNAPSHOT/

which date are you using?

--

James
---
http://radio.weblogs.com/0112098/

Re: STOMP C prefetchSize question

[James Strachan]

On 9/26/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote:

Hi,



On STOMP webpage where it says ActiveMQ extensions to STOMP. It says
activemq.prefetchSize expects a int type value. But from my earlier
question we can only set string value to a header property using STOMP C
client. Will prefetchSize still work if I set it as a string form
number? Some thing like as follows



apr_hash_set(frame.headers, "activemq.prefetchSize",
APR_HASH_KEY_STRING, "1");


Yes.  All Stomp headers are Strings on the wire - the documentation
just means use an integer String representation.
--

James
---
http://radio.weblogs.com/0112098/

Re: Problem on setting destination queue at startup

[James Strachan]

I suspect you are not using 4.1. The website does say its a 4.1
feature but a few folks keep hitting this so I've just added a more
obvious info box to make this a bit more explicit...

http://activemq.org/site/configure-startup-destinations.html

On 9/27/06, Christopher_Ong <[EMAIL PROTECTED]> wrote:


Hello everyone, after I put the below xml codes inside my activemq.xml, it
shown the error that I attached. Please guide me on how to solve the
problem. Thanks.


  



  
http://activemq.org/config/1.0";>

  
  
  
  
  


http://www.nabble.com/file/189/error.txt error.txt
--
View this message in context: 
http://www.nabble.com/Problem-on-setting-destination-queue-at-startup-tf2342201.html#a6519094
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

[jira] Assigned: (AMQ-917) Discovery Network Connector needs to clean up internal ...

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-917?page=all ]

james strachan reassigned AMQ-917:
--

Assignee: james strachan

> Discovery Network Connector needs to clean up internal ...
> --
>
> Key: AMQ-917
> URL: https://issues.apache.org/activemq/browse/AMQ-917
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Connector
>Reporter: Sridhar Komandur
>     Assigned To: james strachan
> Attachments: patchfile.txt
>
>
> Consider the following scenario: All the brokers are using a directory 
> service based discovery agent (for example, DNS). Broker A comes up and tries 
> to connect to broker B, which is not functional yet. The Discovery Network 
> Connector at A adds service B to its tracking state "bridges" (list of 
> connected services) before activating the connection. However, if there is a 
> failure, the data structure is not cleaned up. When the DNS Discovery Agent 
> module rescans (DNS)  and passes on uri for B into DNC, it simply ignores it 
> (as its tracking state hasn't been cleaned up upon prior failure).
> The attached patch should take care of this issue (in the observed code path) 
> - test log below:
> 2006-09-11 15:36:11,810 [main   ] INFO  
> network.DemandForwardingBridge1 - Starting a network connection between 
> vm://localhost#0 and tcp://null:0 has been established.
> 2006-09-11 15:36:48,158 [main   ] DEBUG 
> network.DemandForwardingBridge1 -  stopping localhost bridge to null is 
> disposed already ? false
> 2006-09-11 15:36:48,158 [main   ] INFO  
> ransport.vm.VMTransportFactory1 - Shutting down VM connectors for broker: 
> localhost
> 2006-09-11 15:36:48,159 [main   ] INFO  
> ransport.vm.VMTransportFactory1 - Shutting down VM connectors for broker: 
> localhost
> 2006-09-11 15:36:48,162 [main   ] INFO  
> vemq.broker.TransportConnector1 - Connector vm://localhost Stopped
> 2006-09-11 15:36:48,162 [main   ] DEBUG 
> network.DemandForwardingBridge1 - localhost bridge to null stopped
> 2006-09-11 15:37:11,246 [main   ] WARN  
> ivemq.network.NetworkConnector1 - Could not start network bridge between: 
> vm://localhost?network=true and: tcp://komandur-2.desktop.amazon.com:61617 
> due to: java.net.ConnectException: Connection refused
> java.net.ConnectException: Connection refused

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (AMQ-932) Quickly broken client connections lead to memory leaks

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-932?page=all ]

james strachan resolved AMQ-932.


Fix Version/s: 4.1
   Resolution: Fixed

Patch applied John with thanks - could you double check I've applied it 
correctly please?

> Quickly broken client connections lead to memory leaks
> --
>
> Key: AMQ-932
> URL: https://issues.apache.org/activemq/browse/AMQ-932
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.0.2
>Reporter: John Heitmann
> Fix For: 4.1
>
> Attachments: 73.diff
>
>
> Connections to the openwire port that are pathologically broken (for example 
> any http request) or that die in some other way extremely quickly will lead 
> to memory losses of aout 64Kb each time. This happens because many services 
> are stop()ed directly in the middle of start(), and then never stopped for 
> real, or stopped again but on an object tree with an inconsistent state. This 
> is usually also accompanied by the JMX message:
> WARN  ManagedTransportConnection - Failed to unregister mbean: 
> org.apache.activemq:BrokerName=localhost,Type=Connection,ConnectorName=default,Connection=25
> But that is a cosmetic symptom and not critical (and this has otherwise 
> nothing to do with JMX).
> My patch is a band-aid that is functional but I'm not very happy with it. The 
> patch changes some service logic so that if stop is called in the middle of 
> start, the stop is instead queued and called at the end of start. There will 
> still be multiple stops, and you'll still see the cosmetic JMX error from the 
> second ineffectual stop, but the first stop cleans up correctly so there are 
> no leaks.
> I think there's probably a better solution, but it was tough to see what. I'd 
> appreciate better ideas. Possibly something involving moving the dangerous 
> operations (wire format negotiation etc) out of start?
> I am working on a unit test, but I can't promise I will have something to 
> submit. I'm having to play JVM games to detect the problem in a unit test and 
> that might not fly for general purpose use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (AMQ-826) LDAP based authorization support

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_37009 ] 

james strachan commented on AMQ-826:


Any progress on this yet?

> LDAP based authorization support
> 
>
> Key: AMQ-826
> URL: https://issues.apache.org/activemq/browse/AMQ-826
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: james strachan
> Assigned To: Nikola Goran Cutura
> Attachments: LdapAuth.zip
>
>
> Patch kindly added by ngcutura - discussion thread...
> http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Invalid property 'destinations' of bean class

[James Strachan]

activemq > foo.txt


On 9/25/06, Tommy615 <[EMAIL PROTECTED]> wrote:


Sorry, may i know how to 'piping the output to a file'? I just know how to
pause the batch file so tat it won't auto close.

THanks

James.Strachan wrote:
>
> On 9/25/06, Tommy615 <[EMAIL PROTECTED]> wrote:
>>
>> I attached a image showing the error.
>
> It doesn't really help much.  Could you provide the full XML file you
> are using along with the full stack trace? e.g. try piping the output
> to a file.
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>
>

--
View this message in context: 
http://www.nabble.com/Invalid-property-%27destinations%27-of-bean-class-tf2328853.html#a6482472
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: Authentication (Jconsole)

[James Strachan]

On 9/25/06, James Strachan <[EMAIL PROTECTED]> wrote:

Maybe JRE_HOME has a spacein it?


What is the value of JRE_HOME - does it have a space?

--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-930) Session 'consumers' hashtable susceptible to invalid operation exception

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-930?page=comments#action_36991 ] 

james strachan commented on AMQ-930:


I don't quite understand the reason for this patch - I wonder if you could help 
explain it?

Session.DispatchAsyncMessages() is only ever called in a separate thread pool 
via a call to ThreadPool.QueueUserWorkItem(new 
WaitCallback(session.DispatchAsyncMessages) in the MessageConsumer.

The idea is that only 1 thread at once calls this method for all consumers 
created by the session. (In NMS, just like in JMS, messages are only dispatched 
from one session at once to however many consumers it has - rather than 
dispatching to multiple consumers in parallel).

Am wondering if a better fix is just to ensure that the collection 
("consumer.Values") is completely thread safe to avoid the concurrent 
modification errors you are seeing. I'm working on a patch right now - will 
commit it shortly - am wondering if this is a better approach?




> Session 'consumers' hashtable susceptible to invalid operation exception
> 
>
> Key: AMQ-930
> URL: https://issues.apache.org/activemq/browse/AMQ-930
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: NMS (C# client)
>Affects Versions: incubation
> Environment: Windows XP, NMS API running against a AMQ 4.0.2 provider
>Reporter: Bryan Schmidt
>
> In a multithreaded environment that reuses the Session object, the following 
> exception is thrown:
> Invalid operation exception with the text: "Collection was modified; 
> enumeration operation may not execute."
> The exception is thrown when iterating through Session's consumers.Values 
> collection.  It appears that the lock is being ignored.  Spinning up a new 
> thread fixes the problem:
> --- Session.cs, DispatchAsyncMessages method ---
> public void DispatchAsyncMessages(object state)
> {
> // lets iterate through each consumer created by this session
> // ensuring that they have all pending messages dispatched
> lock (this)
> {
> // lets ensure that only 1 thread dispatches messages in a 
> consumer at once
> foreach (MessageConsumer consumer in consumers.Values)
> {
> ThreadPool.QueueUserWorkItem(new 
> WaitCallback(consumer.DispatchAsyncMessages));
> }
> }
> }

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [stomp-dev] Pluggable Stomp Message Mapping (was: [stomp-dev] PHP Stomp Client)

[James Strachan]

Sounds great, go for it Dejan!

On 9/20/06, Dejan Bosanac <[EMAIL PROTECTED]> wrote:

This sounds to me like the best approach to this problem. It
simplifies implementation of the configuration mechanism and at the
same time gives just enough flexibility. I don't think that there will
be many (if any) clients that will want to change mapping for
connections that are already established.

If others agree with this approach, I can try to find some time these
days to do some work in this direction.

Thanks,
Dejan

On 9/19/06, Hiram Chirino <[EMAIL PROTECTED]> wrote:
> I think that the client should only be allowed to change the default
> mapping if he optionally specifies a 'protocol-mapping' header when he
> connects.  Something like
>
> CONNECT
> login:
> passcode:
> protocol-mapping: foo
>
> Where foo is mapped to a implementation of ProtocolMapper/Converter.
> Then the client will be expected to send messages in that mapping
> format and all messages sent to it will also conform to that format.
>
> On 9/19/06, Dejan Bosanac <[EMAIL PROTECTED]> wrote:
> > And one copy for this list as I assume that we will continue discussion 
here :)
> >
> > On 9/19/06, Dejan Bosanac <[EMAIL PROTECTED]> wrote:
> > > I think that in order to make this framework usable, it has to be
> > > simple. It could be a simple interface such as
> > >
> > > public interface ProtocolTransformer {
> > >  public StompFrame convertMessage(ActiveMQMessage message)
> > > throws IOException, JMSException;
> > >
> > >  public  ActiveMQMessage convertMessage(StompFrame command)
> > > throws IOException, JMSException;
> > > }
> > >
> > > this two methods would be called at appropriate places (probably at
> > > the begging) of the methods in the ProtocolConverter class. In this
> > > way we would allow developers to change message type and/or set
> > > appropriate headers, which seems to me would be more than enough.
> > >
> > > The one thing that I'm not sure of is how the ProtocolConverter will
> > > decide which transformers it should call. For incoming Stomp messages
> > > someone mentioned a solution which seems fine: to put an extra header
> > > in the stomp message (such as amq-msg-type or activemq-transformation
> > > or whatever) which would have a full class name of the transformer to
> > > be applied. Then the ProtocolConverter would try to load this
> > > transformer and if it succeed it would apply the transformation.
> > >
> > > But this solution is not working for messages that are sent from the
> > > broker to the stomp clients. We need some mechanism which will say,
> > > apply this transformation to the ByteMessages so we need a mechanism
> > > that will be able to register all transformers to the
> > > ProtocolConverter and then every transformer would be responsible to
> > > detect whether it should or not change the message.
> > >
> > > For configuring purposes we could use Service Provider JAR
> > > functionality 
(http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html#Service%20Provider)
> > > since it is the only way I can think of that not requires external
> > > configuration.
> > >
> > > Two questions that we need to address:
> > >
> > > 1. do we want to enable more than one transformation to be applied?
> > > 2. how this framework will affect overall performances?
> > >
> > > What do you think?
> > >
> > > Regards,
> > > Dejan
> > >
> > > On 9/19/06, Brian McCallister <[EMAIL PROTECTED]> wrote:
> > > > (Replying at top as it is a long message :-)
> > > >
> > > > The mapping be configured by naming a "converter" of some kind in the
> > > > activemq.xml
> > > >
> > > > This is a bit tricksier than it might be because the activemq.xml is
> > > > just a specialized spring config which reads a lot of stuff from a
> > > > URL syntax, and adding Java classnames in a URL is the ick.
> > > >
> > > > I've started poking around and my current plan is to pull the AMQ
> > > > message creating and Stomp message creation bits out of the protocol
> > > > converter and use an implementation of some mapping interface to do
> > > > the conversion.
> > > >
> > > > Exactly what the interface needs to look like I am not sure yet. In
> > > > order to handle largish messages, it should probably deal with
> > > > DataInput (AMQ's stream/buffer+channel hiding thing) instances, but
> > > > we'll have had to already parse the type to get this far, so it may
> > > > be a case of doing some parsing of the headers, and passing the data
> > > > input in to be munged, or it may fall out that something else is more
> > > > useful.
> > > >
> > > > For encoding AMQ to stomp, we are faced with something similar -- we
> > > > pass in the JMS message, which might be a stream message with a large
> > > > body, we probably want to be able to "chunk" it out, that means
> > > > either making a stomp frame abstraction which can read from a stream
> > > > and is returned by the converter, or having the converter actually
> > > > "send" the messa

Re: How to create permanent Queue

[James Strachan]

Until the 4.1 release goes out you can download a snapshot here...

http://people.apache.org/maven-snapshot-repository/org/apache/activemq/apache-activemq/4.1-incubator-SNAPSHOT/

On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:


The one that I am using is ActiveMQ 4.0.1 Release (latest one since the 4.0.2
having broken link).

Thanks


James.Strachan wrote:
>
> Note you need 4.1 to be able to use the  element.
>
> On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:
>>
>> I had put
>> 
>>   
>>   
>> 
>>
>> James.Strachan wrote:
>> >  as reference to the example given at the link that u gave to me. But
>> > there is an error showing that 'Bean property 'destinations' is not
>> > writable or has an invalid setter method: Does the parameter type of
>> the
>> > setter match the return type of the getter?'
>> >
>> > Here's the link again - details here on how to force the list of
>> > startup destinations...
>> >
>> http://incubator.apache.org/activemq/configure-startup-destinations.html
>> >
>> > On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Maybe I shouldn't use the word 'temporary'. I created the queue and
>> send
>> >> message to it. (let say 10 msg) and the queue size wil be 10. If
>> doens't
>> >> has
>> >> any consumer to consume the msg and I shutdown the broker then the
>> next
>> >> time
>> >> I on the broker again, the queue that having 10 unconsumed msg wil be
>> >> shown
>> >> up at the Jconsole. Let say for another senario is that I created the
>> >> queue
>> >> and send 10 msg to it and it's msg has been consumed and queue size
>> >> become 0
>> >> then I shutdown the broker, but when the next time i on the broker
>> again,
>> >> the queue that i created b4 no longer exist (due to the queue size is
>> 0
>> >> and
>> >> there isn't has any unconsumed msg resided in it). Is there a way to
>> make
>> >> the queue alive even though it's queue size is 0 after I shutdown the
>> >> broker
>> >> and restart it again?
>> >>
>> >> Thanks
>> >>
>> >>
>> >> Tommy615 wrote:
>> >> >
>> >> > I use Jconsole to monitor the activemq broker. I manage to create
>> the
>> >> > (temporary) queue after the broker started and I could monitor by
>> using
>> >> > the Jconsole. But once I shutdown the activemq broker and I open the
>> >> > broker next time then the queue that I created before will be gone.
>> May
>> >> I
>> >> > know how to make the queue still there even though I shutdown it
>> >> earlier
>> >> > and on it during the next time? Thanks
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/How-to-create-permanent-Queue-tf2315492.html#a6440732
>> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> >
>> > James
>> > ---
>> > http://radio.weblogs.com/0112098/
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-create-permanent-Queue-tf2315492.html#a6441093
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>
>

--
View this message in context: 
http://www.nabble.com/How-to-create-permanent-Queue-tf2315492.html#a6442070
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: How to create permanent Queue

[James Strachan]

Note you need 4.1 to be able to use the  element.

On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:


I had put

  
  


James.Strachan wrote:
>  as reference to the example given at the link that u gave to me. But
> there is an error showing that 'Bean property 'destinations' is not
> writable or has an invalid setter method: Does the parameter type of the
> setter match the return type of the getter?'
>
> Here's the link again - details here on how to force the list of
> startup destinations...
> http://incubator.apache.org/activemq/configure-startup-destinations.html
>
> On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:
>>
>> Maybe I shouldn't use the word 'temporary'. I created the queue and send
>> message to it. (let say 10 msg) and the queue size wil be 10. If doens't
>> has
>> any consumer to consume the msg and I shutdown the broker then the next
>> time
>> I on the broker again, the queue that having 10 unconsumed msg wil be
>> shown
>> up at the Jconsole. Let say for another senario is that I created the
>> queue
>> and send 10 msg to it and it's msg has been consumed and queue size
>> become 0
>> then I shutdown the broker, but when the next time i on the broker again,
>> the queue that i created b4 no longer exist (due to the queue size is 0
>> and
>> there isn't has any unconsumed msg resided in it). Is there a way to make
>> the queue alive even though it's queue size is 0 after I shutdown the
>> broker
>> and restart it again?
>>
>> Thanks
>>
>>
>> Tommy615 wrote:
>> >
>> > I use Jconsole to monitor the activemq broker. I manage to create the
>> > (temporary) queue after the broker started and I could monitor by using
>> > the Jconsole. But once I shutdown the activemq broker and I open the
>> > broker next time then the queue that I created before will be gone. May
>> I
>> > know how to make the queue still there even though I shutdown it
>> earlier
>> > and on it during the next time? Thanks
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-create-permanent-Queue-tf2315492.html#a6440732
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>
>
>
> --
>
> James
> ---
> http://radio.weblogs.com/0112098/
>
>

--
View this message in context: 
http://www.nabble.com/How-to-create-permanent-Queue-tf2315492.html#a6441093
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: How to create permanent Queue

[James Strachan]

On 9/22/06, Tommy615 <[EMAIL PROTECTED]> wrote:


I use Jconsole to monitor the activemq broker. I manage to create the
(temporary) queue


FWIW temporary queues are only created via the createTemporaryQueue()
method on a JMS client


 after the broker started and I could monitor by using the
Jconsole. But once I shutdown the activemq broker and I open the broker next
time then the queue that I created before will be gone.


It just doesn't appear by default as destinations are lazily created -
any messages sent to the queue will be persisted.

More details here...

http://incubator.apache.org/activemq/configure-startup-destinations.html
http://incubator.apache.org/activemq/how-do-i-create-new-destinations.html


--

James
---
http://radio.weblogs.com/0112098/

Re: implement autoresume file sending in activemq?

[James Strachan]

If you are using auto-reconnection, then I don't think you should need
to do anything particular to re-resume things on a reconnection. So
just use the failover: transport to connect to the broker and use JMS
streams

http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html
http://incubator.apache.org/activemq/jms-streams.html

On 9/15/06, tianqio <[EMAIL PROTECTED]> wrote:


what can I do to implement this ? I  think  I  can maintain the connection
and destination in client, and get the outputstream if resume is acted.But I
do not have a try,I do not know how dose the server handle stream msg ,so
I can't predict the actually behavior of the server. any suggestion?
especially whether there exists some API that I can judge a new msg or a
resume msg from the  server?
--
View this message in context: 
http://www.nabble.com/implement-autoresume-file-sending-in-activemq--tf2275804.html#a6320181
Sent from the ActiveMQ - Dev forum at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: [activemq-dev] Support for message priority (AMQ-122)

[James Strachan]

On 9/14/06, samahome <[EMAIL PROTECTED]> wrote:

Is this feature going to be in activeMQ 4.2 version or was this feature
existed in any of the previous releases (3.2 or any) of activeMQ ?

How about specifying producer priorities and consumer priorities ? Does this
exist in 4.0.1 release? From the documentation, my understanding is
confused.


We support consumer priorities. We use this for example to weight
local consumers above remote brokers.

See
http://www.activemq.org/site/consumer-priority.html
http://www.activemq.org/site/destination-options.html
--

James
---
http://radio.weblogs.com/0112098/

Re: multiple consumer threads in same program in STOMP issue

[James Strachan]

It could be the stomp c client doesn't do multi threaded consumption
too well. You might wanna take a peek at how the consumption code
works

On 9/14/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote:

Hi,



I am running into a strange issue, I created a consumer program using
STOMP C which actually creates two separate consumer threads and both
threads are reading from the same queue in the AMQ server using their
own selectors on a header property.



I was expecting that each thread will keep on consuming messages those
who satisfy the selector conditions. But what happening here is at a
time only one consumer thread is able to get its messages, another one
just hangs. If I call disconnect in the thread which is working then
only the hanged thread starts getting its messages.



I will appreciate any explanation.



Thanks!



Vik








--

James
---
http://radio.weblogs.com/0112098/

Re: is there a character limit in message selector

[James Strachan]

Not on the Java side no - there could be in a stomp client's
implementation maybe but that should be pretty easy to fix

On 9/15/06, vik Dhawan <[EMAIL PROTECTED]> wrote:


Hi,

I want to know if there is a AMQ specific character limit in message
selector. I am using STOMP C and message selector is working when I am
checking a message header value for null/not null. But in another situation
I am checking for a string in one of the message header property, the size
of the string I am looking for is around 100bytes. So first question came to
my mind was is there any size limit there?

Thanks!.
--
View this message in context: 
http://www.nabble.com/is-there-a-character-limit-in-message-selector-tf2275075.html#a6317949
Sent from the ActiveMQ - Dev forum at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: how to apply message filters in STOMP

[James Strachan]

On 9/8/06, Dhawan, Vikram (LNG-DAY) <[EMAIL PROTECTED]> wrote:

Hi,

In a STOMP client what is the way to apply a message filter. In my
Consumer code I want to accept only those messages who has a particular
header value in one of the message header field.


See the stomp documentation...

http://incubator.apache.org/activemq/stomp.html

which details all the various Stomp headers you can use. In this case
add a 'selector' header (using the same syntax as JMS's SQL 92 syntax)
on the SUBSCRIBE command

--

James
---
http://radio.weblogs.com/0112098/

Re: Writing an architecture overview doc

[James Strachan]

On 8/29/06, Sepand M <[EMAIL PROTECTED]> wrote:

Hi,

I'm thinking of writing an overview of the ActiveMQ communication and
security systems. Before I start, does one already exist? Do you think
it would be useful?


Sounds awesome! Feel free to write it on the wiki if you like? So far
all the security related information is linked from this page
http://incubator.apache.org/activemq/security.html
--

James
---
http://radio.weblogs.com/0112098/

Re: Marshalling failure with pending messages.

[James Strachan]

I'd consider using a newer version of both the broker and the C++
client such as 4.0.1

On 8/28/06, Naveen Rawat <[EMAIL PROTECTED]> wrote:



Hi all


I am working with the binary version of ActiveMQ 4.0 broker and trying out
the openwire cpp apis for asynchronous messaging.
[https://svn.apache.org/repos/asf/incubator/activemq/tags/activemq-4.0/openw
ire-cpp]


I had been testing the persistency between a producer and a listener against
large number of offline messages. After sending  some messages (I tried
around 84) to an offline listener, brining back of listener also brings the
following ERROR (My listener first reads all the pending messages from the
listening queue). However for lesser number of messges it works fine. Also
when both listener and producer are on, the working is perfect.


ERROR: Received a broker exception: Unmarshal failed; unknown data
structure type 46, at

/home/nrawat/openwire2/src/main/cpp/activemq/protocol/openwire/OpenWireMa
rshaller.cpp line 710
Exiting read loop due to exception: Unmarshal failed; unknown data
structure type 46, at

/home/nrawat/openwire2/src/main/cpp/activemq/protocol/openwire/OpenWireMa
rshaller.cpp line 710





THANKS IN ADVANCE

Hearty Regards,
Navin




--

James
---
http://radio.weblogs.com/0112098/

Re: Where to put new Callback and CallbackHandler classes

[James Strachan]

Sounds fine to me.


On 8/26/06, Sepand M <[EMAIL PROTECTED]> wrote:

Hi again,

After looking at things closer, I think that all callback handlers,
etc (including existing ones) should be moved to the jaas module and
all of the authentication brokers should stay where they are in core.

The callbacks should move since they are no necessary for core and
moving them fixes the circular dependancy problem.

The brokers should remain since they are needed for the authorization
broker to function (and i don't think authorization should be moved
into jaas). This also allows the bean stuff to continue working.

Any objections?

On 8/25/06, Sepand M <[EMAIL PROTECTED]> wrote:
> Ok. So, to confirm, I shouldm ove all Jaas* classes to the jaas module?
>
> On 8/25/06, James Strachan <[EMAIL PROTECTED]> wrote:
> > On 8/25/06, Sepand M <[EMAIL PROTECTED]> wrote:
> > > Well there's already a JaasAuthenticationBroker in core, shouldn't the
> > > JaasCertificateAuthenticationBroker (that's the full name) be in the
> > > same package?
> >
> > Sure
> >
> > > Also, would I still be able to use it easily (just by specifying it in
> > > the config xml) if I move it to the jaas module?
> >
> > Yes.; though we might have to hack the xbean-plugin configuration in
> > the activemq-core module to also search other modules to keep them all
> > in the same namespace as right now the xbean plugin isn't too great at
> > creating a single schema & document reference for multiple modules in
> > a single namespace.
> >
> > FWIW I'd like activemq-core, activemq-ra, activemq-jaas and maybe
> > activemq-optional all to be in the same namespace & schema &
> > reference.
> >
> > e.g. right now the activemq-ra stuff is in a different namespace; when
> > its only a couple of elements; we really should unify them all
> > together.
> > --
> >
> > James
> > ---
> > http://radio.weblogs.com/0112098/
> >
>




--

James
---
http://radio.weblogs.com/0112098/

Re: Patch submission process and turn around time

[James Strachan]

On 8/25/06, Sepand M <[EMAIL PROTECTED]> wrote:

Hi,

I'm almost done coding for the SSL transport support project (refer to
the "Creating a secure connection system and using JMSXUserID support"
thread).


Great


I was just wondering how I would submit the patch for approval, how
long approval would take, when the code might make it into a release,
etc.


Here's details
http://incubator.apache.org/activemq/contributing.html



I ask this because my company needs to use this code fairly soon and I
need to figure out if we should wait for your release (if you accept
my code) or try to get my stuff in independant of activemq.


We can't give any particular dates for releases - you might want to
use a local build until the release goes out
--

James
---
http://radio.weblogs.com/0112098/

[jira] Commented: (AMQ-826) LDAP based authorization support

[james strachan (JIRA)]

[ 
https://issues.apache.org/activemq/browse/AMQ-826?page=comments#action_36849 ] 

james strachan commented on AMQ-826:


Great - thanks for the heads up. Good luck :)

> LDAP based authorization support
> 
>
> Key: AMQ-826
> URL: https://issues.apache.org/activemq/browse/AMQ-826
> Project: ActiveMQ
>  Issue Type: Improvement
>    Reporter: james strachan
> Assigned To: Nikola Goran Cutura
> Attachments: LdapAuth.zip
>
>
> Patch kindly added by ngcutura - discussion thread...
> http://www.nabble.com/LDAP-Authorization-tf1851705.html#a5344494

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: JAAS problems

[James Strachan]

On 8/24/06, Sepand M <[EMAIL PROTECTED]> wrote:

Hello all,

The problem has been solved.
In case anyone is wondering, I did not realize that activemq used the
jar files within the lib directory. I thought it was using the
snapshot jar (which it wasn't).
Copying the snapshot jar to the lib folder solved everything.


Ah cool thanks for letting us know


My new question is this:
How do I control which jaas jars are loaded by the activemq script?


The activemq script loads whatever's in the lib directory. If you want
something more clever you could always write your own bootstrap of the
broker as its just plain Java

--

James
---
http://radio.weblogs.com/0112098/

Re: How to create a temporary Queue

[James Strachan]

I don't really follow the point of quoting these links - one link is
about a completely different JMS provider, SwiftMQ and the other is
about passing destinations in arbitrary JMS headers as opposed to the
JMSReplyTo property - on a very old version of ActiveMQ..

If you think you can reproduce a bug with ActiveMQ please raise a JIRA
and preferably a test case...

http://incubator.apache.org/activemq/support.html

On 8/23/06, Naveen Rawat <[EMAIL PROTECTED]> wrote:


Hi James,


> It sounds like your server is sending a response to a client which has
> already disconnected.


It seems the issue about the respond-back consumer not able to see the
temporary queue/topic even when its creator sender is in connection has been
faced in the past. The issue has been discussed here (I hav managed to get 2
of those) -

"The initial receiver (reply back server) is hanging on to the message."
http://www.nabble.com/Locked-messages-tf2115092.html#a5907342

"The message sent to a temp topic  is never delivered to consumer."
http://www.nabble.com/Flow-control-tf1539523.html#a4208304


What is discussed in the links is exactly my scenario. My receiver also goes
into sleep mode (to be restarted again) after receiving the first message.
As suggested in the above discussion links, the working becomes fine if
regular topics/queues are used which is exactly happening with me. This
issue remained unresolved in both the above links.

I think this issue has the cardinality to be taken seriously.
What do you say James.


Thanks in Advance


With warm regards,
Navin


--
View this message in context: 
http://www.nabble.com/How-to-create-a-temporary-Queue-tf2145190.html#a5944413
Sent from the ActiveMQ - Dev forum at Nabble.com.





--

James
---
http://radio.weblogs.com/0112098/

Re: How to create a temporary Queue

[James Strachan]

On 8/23/06, ahamad <[EMAIL PROTECTED]> wrote:

On 8/23/06, ahamad <[EMAIL PROTECTED]> wrote:
>
> Hi James,
>
> >We're not keeping it there :).
>
> >The Destination objects are like URL classes; they can be attached to
> >messages or held in client's RAM - the broker can't really go around
> >every JVM and make sure they don't happen to have a reference to a non
> >existent destination lying around
>
>
> >The broker resources have been removed when the client disconnected.
>
> But James, when I use top command this is not showing released resources.

>What resources are  you talking about that you can see via top?

I am talking about the memory which is taken by the broker, this memory does
not decrease whenever the clients are disconnected.


Top is not a good way to decude memory usage of Java. Try using
jconsole and forcing GCs or a profiler
--

James
---
http://radio.weblogs.com/0112098/

[jira] Resolved: (AMQ-893) on solaris you cannot easily kill a slave broker when using JDBC Master Slave

[james strachan (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-893?page=all ]

james strachan resolved AMQ-893.


Resolution: Fixed

Have just added a short circuit for the loop trying to acquire the exclusive 
lock so that we fail fast if we are stopping

> on solaris you cannot easily kill a slave broker when using JDBC Master Slave
> -
>
> Key: AMQ-893
> URL: https://issues.apache.org/activemq/browse/AMQ-893
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 4.1
> Environment: Solaris, T20000
>    Reporter: james strachan
> Assigned To: james strachan
> Fix For: 4.1
>
>
> Seems to hang in a tight loop

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira