Re: IRC sessions on ServiceMix 4.0 design (was Re: ServiceMix 4.0)

[Adrian Co]

It's fine. I'll try to join in when I can or just read the logs. :)

Nodet Guillaume wrote:

Ok, sounds like we have enough people.
So we just need to find a data and an hour.
What about Friday 3 pm GMT,  11 am EST, 8 am PST
Adrian, I'm not sure how to find a time that would suits you...
Other propositions are welcome...

Cheers,
Guillaume Nodet

On Aug 24, 2007, at 11:04 AM, Nodet Guillaume wrote:


Any other people interested ?

Cheers,
Guillaume Nodet

On Aug 23, 2007, at 3:37 PM, Kit Plummer wrote:


I'd be up for a few chat sessions!

On 8/23/07, Nodet Guillaume [EMAIL PROTECTED] wrote:


Btw, if there is sufficient interest, we could organize irc meetings
to discuss these topics and post the log to the dev list for archiving
and later discussion.

Cheers,
Guillaume Nodet

On Aug 22, 2007, at 4:59 PM, Nodet Guillaume wrote:


As I explained in the other thread, I've been working on a new API
for ServiceMix 4.0.
Hopefully this will serve as an input for JBI 2.0.
This API is available at  https://svn.apache.org/repos/asf/
incubator/servicemix/branches/servicemix-4.0/api

So here a few key changes:
  * clean integration with OSGi
  * the NormalizedMessage can contain not only XML
  * no more components
  * no more JBI packaging (just use OSGi bundles)
  * move the Channel to the Endpoint
  * use push delivery instead of pulling exchanges
  * introduce a single interface for identifying the Target of an
Exchange

As we remove components, everything goes down to the endpoint which
become a key feature.

The endpoint must implement the Endpoint interface.  In OSGi, the
NMR would listen to endpoints
registered in the OSGi registry and call the registry to register /
unregister the endpoints.
As part of the endpoint registration, the NMR would inject a
Channel into them, thus actually activating the
endpoint.  I guess I could write a sequence diagram for that
(anybody knows a good tool for uml ?).
In a non OSGI environment, the Endpoint will be registered in the
Registry by calling the register method
somehow.

The Endpoint receives Exchange to be processed on the process method.
I think we should keep the JBI 1.0 semantics and the endpoint use
the same process as for JBI 1.0, which is
send the exchange back using the Channel (with the response /
fault / error / done).  This will put the threading,
transactions and security burden on the container itself.  Which
means it is easier to write JBI apps :-)

Exchanges can be created using the Channel#createExchange method.
The only change I'd like to
integrate in the messaging API is to allow for non xml payloads and
maybe untyped attachments.  The body
could be converted automatically to a given type if supported (I
think Camel does it nicely, so I'm thinking of
shamelessly copying the converter layer).  I have added a few
helper methods on the exchanges and
messages (copy, copyFrom, ensureReReadable, display) to ease
message management.

For the deployment part, there is no packaging anymore.  One would
deploy an OSGi bundle that would
register the needed endpoints in the OSGi registry.  For certain
types of endpoints, we may need an external
activation process (such as creating a server socket for listening
to HTTP requests) that may need to be shared
across endpoints of a given type.  In such a case, you would deploy
a component that listens to new
endpoints implementing HttpEndpoint for example.  When a new
endpoint is registered, the listener would
activate a server socket that could be shared across all http
endpoints.   In a different way, if we have  a BPEL
engine, the bpel component  would listen for new bundles and look
for a specific file containing deployment
information. The component would register new endpoints in the OSGi
registry as needed (we could do that
for jaxws pojos using cxf for example).
So I said there is no more components, because this feature is not
in the api anymore, but we will certainly need
these components for some use cases.   For simple endpoints, you
would not need any component at all.
Another benefit is that you can easily deploy a whole application
inside a single OSGi bundle.  Using spring-osgi,
the bundle would just consist in a spring configuration file
containing the endpoints declaration and expose them
as OSGi services.

Of course, we need to write a JBI 1.0 compatibility layer, and we
could have an intermediate layer where SAs and
JBI components could be OSGi bundles directly, thus leveraging the
OSGi classloading mechanism.

The thing I'm not completely sure about if the Target interface
which aims to identify the target of an exchange.
I'm thinking that some metadata are associated with endpoints (like
service name, interface name, wsdl
location, etc..).   These metadatas could be used to retrieve
targets using the Registry.  We could plug in different
mechanisms to query the metadata (simple lookup per id, policy
based, etc...).  And the result itself could be
not only a single Endpoint, but could include some 

Re: IRC sessions on ServiceMix 4.0 design (was Re: ServiceMix 4.0)

[Adrian Co]

I'm interested too.

Brian O'Neill wrote:

Yes. I'm in.

-brian

On 8/24/07, Gordon Dickens [EMAIL PROTECTED] wrote:
  

I too would like to listen in.

Regards,
Gordon

Daryl Richter wrote:


On Aug 24, 2007, at 5:04 AM, Nodet Guillaume wrote:


  

Any other people interested ?




I wouldn't mind listening in.  We are in the very early stages of a
ServiceMix implementation, though, so I don't have a lot of
opinions... yet.  :)



  

Cheers,
Guillaume Nodet





--
Daryl
http://itsallsemantics.com

We want great men who, when fortune frowns, will not be discouraged.
 -- Colonel Henry Knox, 1776








  




  

Re: ServiceMix 4.0

[Adrian Co]

Not sure if this is the right forum to bring this up, but I was 
wondering if this is a good opportunity to migrate some of servicemix's 
infra to newer version.


i.e.

1. Use slf4j as the logging framework. (http://www.slf4j.org/) - btw, 
I'm not sure if its a better option, but I did hear some good stuff 
about it.

2. Upgrade to junit 4.x (Port the existing test cases maybe?)

and maybe others.

Just my 2 cents. :)

Daryl Richter wrote:


On Aug 23, 2007, at 4:21 PM, Bruce Snyder wrote:


On 8/23/07, Kit Plummer [EMAIL PROTECTED] wrote:


I've used MagicDraw on OS X.  It's pretty terrible...but does work for
sequence diagrams.  I'm not sure if they have a free version or not.
Doesn't OmniGraffle do some UML stuff too?


Yeah I've used MagicDraw in the past. Unfortunately the free version
doesn't generate sequence diagrams and that's the key for me. I want
the ability to have the tool generate UML from the source and that's
hard to find in a free tool.


Yes, I agree.  JUDE can generate UML from source, though it doesn't 
support Java 1.5 annotations.  It does make nice sequence diagrams and 
is a nice tool to work with, in general.




Bruce
--
perl -e 'print 
unpack(u30,D0G)[EMAIL PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT*

);'

Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/


--
Daryl
http://itsallsemantics.com

Re: configuring sevicemix-jms to IBM MQ

[Adrian Co]

Can you include the full stack trace?

unni_varun wrote:
I'm getting Null Pointer Exception in JMS SU. 
  

Re: svn commit: r552774 - in /incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms: ./ src/test/java/org/apache/servicemix/jms/ src/test/resources/org/apache/servicemix/jms/

[Adrian Co]

Yeah I thought of refactoring it, to make it easier to configure the smx 
container, because it was creating some directories outside the target dir.


Though I can't figure out why this error occurred. I don't see this in 
my build. :(


Bruce Snyder wrote:

On 7/3/07, Guillaume Nodet [EMAIL PROTECTED] wrote:

Hey, I've just svn up and I have the following problem when bulding:

[INFO] Surefire report directory:
c:\java\servicemix\clean\deployables\bindingcomponents\servicemix-jms\target\surefire-reports 


org.apache.maven.surefire.booter.SurefireExecutionException: Unable to
create test class 'org.apache.servicemix.jms.'; nested exception is
java.lang.ClassNotFou
ndException: org.apache.servicemix.jms.; nested exception is
org.apache.maven.surefire.testset.TestSetFailedException: Unable to
create test class 'org.apache.s
ervicemix.jms.'; nested exception is java.lang.ClassNotFoundException:
org.apache.servicemix.jms.
org.apache.maven.surefire.testset.TestSetFailedException: Unable to
create test class 'org.apache.servicemix.jms.'; nested exception is
java.lang.ClassNotFoundE
xception: org.apache.servicemix.jms.
java.lang.ClassNotFoundException: org.apache.servicemix.jms.
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at 
org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:103) 

at 
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:87) 

at 
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) 


at org.apache.maven.surefire.Surefire.run(Surefire.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:585)
at 
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:290) 

at 
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818) 



Does this work for you ?


FWIW, I just moved the src/main/java/org/apache/servicemix/jms
directory aside, updated and rebuilt and I got past this error. But
then I ran into a test failure due to a method signature being changed
on the 
org.springframework.jmx.support.ConnectorServerFactoryBean.setObjectName() 


method and had to fix that (I'll commit this one in a bit).

Adrian, it is extremely ironic that you have refactored the
JmsConsumerEndpointTest and JmsProviderEndpointTest to extend
AbstractJmsTestCase. I did the same exact thing last week but hadn't
yet committed my work. Very odd that we were working on some of the
same changes to the same tests ;-).

Bruce

[jira] Assigned: (SM-987) Binding Component archetype - can't build

[Adrian Co (JIRA)]

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

Adrian Co reassigned SM-987:


Assignee: Adrian Co

Should we remove the checkstyle for the archetype or maybe for this specific 
error only?

 Binding Component archetype - can't build
 -

 Key: SM-987
 URL: https://issues.apache.org/activemq/browse/SM-987
 Project: ServiceMix
  Issue Type: Bug
Affects Versions: 3.2
 Environment: linux, normal pc
Reporter: Eduardo Burgos
Assignee: Adrian Co

 revision: 551635
 cd trunk
 svn up
 at revision 551635
 when I try to build everything it has this error:
 [INFO] Building ServiceMix :: Archetypes :: BindingComponent
 [INFO]task-segment: [clean, install]
 [INFO] 
 
 .
 .
 .
 [INFO] Starting audit...
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyEndpointType.java:17:
  Missing package declaration.
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyComponent.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyBootstrap.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyConsumerEndpoint.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyProviderEndpoint.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/test/java/MySpringComponentTest.java:19:1:
  Got an exception - expecting EOF, found 'import'
 Audit done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-987) Binding Component archetype - can't build

[Adrian Co (JIRA)]

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

Adrian Co resolved SM-987.
--

   Resolution: Fixed
Fix Version/s: 3.2

Fix added: http://svn.apache.org/viewvc?view=revrev=551839

 Binding Component archetype - can't build
 -

 Key: SM-987
 URL: https://issues.apache.org/activemq/browse/SM-987
 Project: ServiceMix
  Issue Type: Bug
Affects Versions: 3.2
 Environment: linux, normal pc
Reporter: Eduardo Burgos
Assignee: Adrian Co
 Fix For: 3.2


 revision: 551635
 cd trunk
 svn up
 at revision 551635
 when I try to build everything it has this error:
 [INFO] Building ServiceMix :: Archetypes :: BindingComponent
 [INFO]task-segment: [clean, install]
 [INFO] 
 
 .
 .
 .
 [INFO] Starting audit...
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyEndpointType.java:17:
  Missing package declaration.
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyComponent.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyBootstrap.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyConsumerEndpoint.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/main/java/MyProviderEndpoint.java:19:1:
  Got an exception - expecting EOF, found 'import'
 /src/servicemix/trunk/archetypes/servicemix-binding-component/src/main/resources/archetype-resources/src/test/java/MySpringComponentTest.java:19:1:
  Got an exception - expecting EOF, found 'import'
 Audit done.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-969) JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage

[Adrian Co (JIRA)]

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

Adrian Co resolved SM-969.
--

   Resolution: Fixed
Fix Version/s: 3.2

http://svn.apache.org/viewvc?view=revrev=550764

Patch applied. Much thanks! 

 JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage
 ---

 Key: SM-969
 URL: https://issues.apache.org/activemq/browse/SM-969
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-soap
Reporter: Piotr Bzdyl
Assignee: Adrian Co
 Fix For: 3.2

 Attachments: JBIMarshaler.java.diff


 JBIMarshaler doesn't copy Subject from NormalizedMessage to SoapMessage so 
 the information about the subject is lost. It does so in opposite way (from 
 SoapMessage to NormalizedMessage).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (XBEAN-87) Broken pom for the 3.0 release

[Adrian Co (JIRA)]

Broken pom for the 3.0 release
--

 Key: XBEAN-87
 URL: https://issues.apache.org/jira/browse/XBEAN-87
 Project: XBean
  Issue Type: Bug
  Components: kernel
Affects Versions: 3.0
Reporter: Adrian Co


I'm not sure if this is a bug, since 3.0 has not been officially released yet. 
But the pom deployed here: 
http://repo1.maven.org/maven2/org/apache/xbean/xbean/3.0/xbean-3.0.pom says 
that the pom version is 3.0, but the proeprties specifies 3.0-SNAPSHOT as the 
version.

This is related to: https://issues.apache.org/activemq/browse/AMQ-1259


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (SM-840) JMS connections not close in servicemix-wsn2005

[Adrian Co (JIRA)]

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

Adrian Co reassigned SM-840:


Assignee: Adrian Co

 JMS connections not close in servicemix-wsn2005
 ---

 Key: SM-840
 URL: https://issues.apache.org/activemq/browse/SM-840
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-wsn2005
Affects Versions: 3.1
 Environment: winxp
Reporter: Adrian Co
 Assigned To: Adrian Co

 There doesn't seem to be any code in the smx-wsn2005 component that closes 
 the JMS connection it uses.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SM-840) JMS connections not close in servicemix-wsn2005

[Adrian Co (JIRA)]

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

Adrian Co resolved SM-840.
--

   Resolution: Fixed
Fix Version/s: 3.2

Fix added to rev. 507843

 JMS connections not close in servicemix-wsn2005
 ---

 Key: SM-840
 URL: https://issues.apache.org/activemq/browse/SM-840
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-wsn2005
Affects Versions: 3.1
 Environment: winxp
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 3.2


 There doesn't seem to be any code in the smx-wsn2005 component that closes 
 the JMS connection it uses.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SM-840) JMS connections not close in servicemix-wsn2005

[Adrian Co (JIRA)]

JMS connections not close in servicemix-wsn2005
---

 Key: SM-840
 URL: https://issues.apache.org/activemq/browse/SM-840
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-wsn2005
Affects Versions: 3.1
 Environment: winxp
Reporter: Adrian Co


There doesn't seem to be any code in the smx-wsn2005 component that closes the 
JMS connection it uses.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (AMQ-1046) Consolidate the ActiveMQ admin scripts to a single command line script

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1046.


Resolution: Fixed

Fix added to r495172

Admin commands can be success using:
activemq-admin bstat
activemq-admin stop
activemq-admin list
activemq-admin query ...
activemq-admin purge
etc..

 Consolidate the ActiveMQ admin scripts to a single command line script
 --

 Key: AMQ-1046
 URL: https://issues.apache.org/activemq/browse/AMQ-1046
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Hiram Chirino
 Assigned To: Adrian Co
 Fix For: 4.2.0


 Right now we have serveral command line scripts in the ActiveMQ bin directory 
 of the binary distribution.  They are used for admin purposes.  They are less 
 than ideal because some of them have very generic names and might clash with 
 existing commands if the activemq bin directory is added to the PATH of a 
 unix system.
 I think it would be more idea if we consolidated all the command so that are 
 executed using just 1 script.  Something like:
 $ activemq-admin list
 $ activemq-admin stat
 $ activemq-admin browse
 etc. etc. etc.  This way only 2 executable scripts are added to the path:
  (1) activemq - the binary that starts up ActiveMQ
  (2) activemq-admin - the binary used to manage the ActiveMQ instance.

-- 
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-1096) activemq-console only has limited classpath/extensions directory functionality

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1096.


Resolution: Fixed

Fix added to r495172

Added a activemq.classpath system property to extend the classpath of activemq

By default it contains activemq.home/conf.

It can be extended by specifying additional paths via the ACTIVEMQ_CLASSPATH 
environment variable separated by semi-colons.

 activemq-console only has limited classpath/extensions directory functionality
 --

 Key: AMQ-1096
 URL: https://issues.apache.org/activemq/browse/AMQ-1096
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1.0
Reporter: John Heitmann
 Assigned To: Adrian Co
Priority: Minor
 Attachments: logpatch.diff


 Reproduction:
 1) Untar the binary distribution.
 2) Run bin/activemq and note what logging looks like (you should see output 
 to the console)
 3) Stop the broker.
 4) mv conf/log4j.properties foo/log4j.properties
 5) export CLASSPATH=/path/to/foo/
 6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
 7) Run './activemq --extdir /path/to/foo
 Now note there is no log output even though there are 3 different attempts to 
 set the proper directory. This is a regression from 4.0 to 4.1.
 There are 2 root problems in Main.java. First, 'classpaths' doesn't actually 
 pull from the classpath. The only thing that ever gets added to classpaths is 
 the hard coded 'conf' directory. Second, directories specified with --extdir 
 have jars and zips added, but not the directories themselves.
 The attached patch totally removes the vestigial classpaths, and fixes extdir 
 to pull in directories. This means that step 7 now works, but steps 5 and 6 
 are still useless. I like having only one way to specify classpath, but I 
 could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to 
 work.

-- 
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] Assigned: (AMQ-1096) activemq-console only has limited classpath/extensions directory functionality

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-1096:
--

Assignee: Adrian Co

 activemq-console only has limited classpath/extensions directory functionality
 --

 Key: AMQ-1096
 URL: https://issues.apache.org/activemq/browse/AMQ-1096
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1.0
Reporter: John Heitmann
 Assigned To: Adrian Co
Priority: Minor
 Attachments: logpatch.diff


 Reproduction:
 1) Untar the binary distribution.
 2) Run bin/activemq and note what logging looks like (you should see output 
 to the console)
 3) Stop the broker.
 4) mv conf/log4j.properties foo/log4j.properties
 5) export CLASSPATH=/path/to/foo/
 6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
 7) Run './activemq --extdir /path/to/foo
 Now note there is no log output even though there are 3 different attempts to 
 set the proper directory. This is a regression from 4.0 to 4.1.
 There are 2 root problems in Main.java. First, 'classpaths' doesn't actually 
 pull from the classpath. The only thing that ever gets added to classpaths is 
 the hard coded 'conf' directory. Second, directories specified with --extdir 
 have jars and zips added, but not the directories themselves.
 The attached patch totally removes the vestigial classpaths, and fixes extdir 
 to pull in directories. This means that step 7 now works, but steps 5 and 6 
 are still useless. I like having only one way to specify classpath, but I 
 could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to 
 work.

-- 
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] Assigned: (AMQ-1071) Activemq connection factory silently ignores the erroneous arguments in broker url

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-1071:
--

Assignee: Adrian Co

 Activemq connection factory silently ignores the erroneous arguments in 
 broker url
 --

 Key: AMQ-1071
 URL: https://issues.apache.org/activemq/browse/AMQ-1071
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
 Environment: Linux
Reporter: Dileepan K
 Assigned To: Adrian Co
Priority: Minor

 When an erroneous argument is passed to the broker url with failover, 
 activemq connection factory ignores the error. However if failover is 
 removed, it does throw exception. 
 Here is the example
 1. 
 failover:(tcp://localhost:62012)?jms.prefetchPolicy.all=10amp;wireFormat.maxInactivityDuration=0amp;jms.optimizeAcknowledge=false
 2. 
 tcp://localhost:62012?jms.prefetchPolicy.all=10amp;wireFormat.maxInactivityDuration=0amp;jms.optimizeAcknowledge=false
 Only the # 2 throws exception as jms.prefetchPolicy.all is an invalid 
 argument here

-- 
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-1106) PooledBrokerFactoryBean incorrectly compares broker config resources

[Adrian Co (JIRA)]

PooledBrokerFactoryBean incorrectly compares broker config resources


 Key: AMQ-1106
 URL: https://issues.apache.org/activemq/browse/AMQ-1106
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1.2, 4.2.0
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.1.2, 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] Updated: (AMQ-1097) Using a selector provides invalid output

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-1097:
---

Affects Version/s: 4.0.3
   4.1.1
   4.1.2

 Using a selector provides invalid output
 

 Key: AMQ-1097
 URL: https://issues.apache.org/activemq/browse/AMQ-1097
 Project: ActiveMQ
  Issue Type: Bug
  Components: Selector
Affects Versions: 4.2.0, 4.0.3, 4.1.1, 4.1.2
 Environment: Windows XP Professional, jdk 1.5
Reporter: Marlon Santos
 Assigned To: Adrian Co
 Fix For: 4.2.0


 When consuming messages with a selector, the consumer consumes invalid 
 messages. (Both queue and topic).  

-- 
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-1097) Using a selector provides invalid output

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1097.


Resolution: Fixed

Fix added to r487187

 Using a selector provides invalid output
 

 Key: AMQ-1097
 URL: https://issues.apache.org/activemq/browse/AMQ-1097
 Project: ActiveMQ
  Issue Type: Bug
  Components: Selector
Affects Versions: 4.2.0, 4.0.3, 4.1.1, 4.1.2
 Environment: Windows XP Professional, jdk 1.5
Reporter: Marlon Santos
 Assigned To: Adrian Co
 Fix For: 4.2.0


 When consuming messages with a selector, the consumer consumes invalid 
 messages. (Both queue and topic).  

-- 
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] Assigned: (AMQ-1097) Using a selector provides invalid output

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-1097:
--

Assignee: Adrian Co

 Using a selector provides invalid output
 

 Key: AMQ-1097
 URL: https://issues.apache.org/activemq/browse/AMQ-1097
 Project: ActiveMQ
  Issue Type: Bug
  Components: Selector
Affects Versions: 4.2.0
 Environment: Windows XP Professional, jdk 1.5
Reporter: Marlon Santos
 Assigned To: Adrian Co
 Fix For: 4.2.0


 When consuming messages with a selector, the consumer consumes invalid 
 messages. (Both queue and topic).  

-- 
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-1097) Using a selector provides invalid output

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1097:


This is when using the destination url configuration. e.g. 
(TEST.FOO?consumer.selector=test=1)

 Using a selector provides invalid output
 

 Key: AMQ-1097
 URL: https://issues.apache.org/activemq/browse/AMQ-1097
 Project: ActiveMQ
  Issue Type: Bug
  Components: Selector
Affects Versions: 4.2.0
 Environment: Windows XP Professional, jdk 1.5
Reporter: Marlon Santos
 Assigned To: Adrian Co
 Fix For: 4.2.0


 When consuming messages with a selector, the consumer consumes invalid 
 messages. (Both queue and topic).  

-- 
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] Reopened: (AMQ-908) Authorization plugin should have configurable principal classes

[Adrian Co (JIRA)]

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

Adrian Co reopened AMQ-908:
---

  Assignee: Jonas Lim
 
I think its much better if we perform parseACL in the afterPropertiesSet method 
(assuming it implements the InitializingBean), rather than relying on 
alphabetical properties.

Thoughts?

 Authorization plugin should have configurable principal classes
 ---

 Key: AMQ-908
 URL: https://issues.apache.org/activemq/browse/AMQ-908
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Broker
Affects Versions: 4.0.1
Reporter: Aaron Mulder
 Assigned To: Jonas Lim
 Fix For: 4.2.0

 Attachments: authorizationPlugin.patch, authorizationPlugin.patch, 
 AuthorizationPlugin.patch, AuthorizationPlugin.patch


 Currently, if you configure the authorization plugin, it assumes that all 
 principals listed should be of type 
 {{org.apache.activemq.jaas.GroupPrincipal}}.  This is OK if you're using 
 ActiveMQ LoginModules, but since there's a fairly small supply of those, it 
 would be great if you could use arbitrary login modules and tell the 
 authorization plugin which principal classes to use.  For example, 
 {{groupClass=weblogic.security.principal.WLSGroupImpl}} or something like 
 that.  A good first step would be to let you change the group class.  A good 
 second step would be to let you specify user and group classes and then 
 somehow indicate which names are which (e.g. 
 {{admin=administrators,user:aaron,user:bob}} or whatever).  Someday maybe 
 it will be nice to support any arbitrary combination of principal classes but 
 that seems far away.
 When instantiating the principal classes, I imagine we should use a 
 constructor with a single String argument if available, or else a default 
 constructor plus a setName method, or else I guess bail.

-- 
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] Assigned: (AMQ-594) SimpleNetworkTest hangs

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-594:
-

Assignee: Rob Davies  (was: Adrian Co)

Assigning to Rob for technical review. :)

 SimpleNetworkTest hangs
 ---

 Key: AMQ-594
 URL: https://issues.apache.org/activemq/browse/AMQ-594
 Project: ActiveMQ
  Issue Type: Bug
  Components: Test Cases
Affects Versions: 4.0 RC2
Reporter: Darwin Flores
 Assigned To: Rob Davies
 Fix For: 4.2.0

 Attachments: DemandForwardingBridgePatch.patch


 The SimpleNetworkTest appears to be hanging in Linux platform

-- 
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-594) SimpleNetworkTest hangs

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-594:
--

Attachment: DemandForwardingBridgePatch.patch

Seems that the test is hanging because the remote broker is trying to send a 
ShutdownInfo to the local broker after the fact that the local broker has been 
stopped. I've attached a patch that would not use failover when the forwarding 
bridge is sending a shutdown info. I'm not sure though if this is a good 
approach.

 SimpleNetworkTest hangs
 ---

 Key: AMQ-594
 URL: https://issues.apache.org/activemq/browse/AMQ-594
 Project: ActiveMQ
  Issue Type: Bug
  Components: Test Cases
Affects Versions: 4.0 RC2
Reporter: Darwin Flores
 Assigned To: Adrian Co
 Fix For: 4.2.0

 Attachments: DemandForwardingBridgePatch.patch


 The SimpleNetworkTest appears to be hanging in Linux platform

-- 
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-1065) Provide startup option to flush journal to store then exit the broker

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1065:


Personally, I prefer this as a utility separate from the broker. I'll try to 
look into incorporating this into the console.

 Provide startup option to flush journal to store then exit the broker
 -

 Key: AMQ-1065
 URL: https://issues.apache.org/activemq/browse/AMQ-1065
 Project: ActiveMQ
  Issue Type: Wish
  Components: Broker
Affects Versions: 4.2.0
Reporter: [EMAIL PROTECTED]
 Fix For: 4.2.0


 This is a wish for a command line argument that will flush the journal to 
 the database and quit.
 This makes it possible to:
 1.  Do some kinds of message administration / emergency fixing in SQL.
 2. Upgrade even if there are incompatible changes by first flushing the 
 journal and then applying the appropriate SQL change script to the database.
 3.  Switch the kind of journaling, switch to no journaling, etc.
 Jason

-- 
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-1060) Unable to connect to AMQ 4.x queue with MDB

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1060:


Kindly attach the broker and client logs with debug turned on and whatever 
configuration you used for the broker and client. I don't have Websphere, but 
maybe someone will see something. :)

 Unable to connect to AMQ 4.x queue with MDB
 ---

 Key: AMQ-1060
 URL: https://issues.apache.org/activemq/browse/AMQ-1060
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0.1, 4.0.2
 Environment: OS Windows 2003 Server, AMQ 4.0.2, Websphere 5.1.11
Reporter: Stephen Murray
 Fix For: 3.2.2


 Can you please raise a JIRA for a bug introduced in Version 4.x of ActiveMQ ? 
 I'm unable to connect to an ActiveMQ queue with an MDB when the ActiveMQ 
 queue I'm connecting to has a queue depth. 
 This works in ActiveMQ 3.2.2, but doesn't in 4.0.1 or 4.0.2. 
 Environment : 
 AMQ 4.0.1 or 4.0.2 deployed standalone on a Windows 2003 server. 
 Basic (Hello World) MDB deployed within IBM Websphere 5.1 (Patch 11). 
 Intructions to recreate : 
 Start AMQ, load a message onto the MDBs Queue, start Websphere and MDB won't 
 connect to the ActiveMQ queue. 
 If there is any further information you require to assist in the resolution 
 of this problem, please let us know. We can provide details of the code or 
 the WAS/AMQ config. 
 Whilst stating this doesn't work for a Hello World MDB, this is for 
 simplicity and ease of testing this issue, in reality we are using the MDB 
 and AMQ as part of a full blown integration solution at 2 major Utility 
 companies and seriously need some assistance with this. Testing onsite of the 
 solution at each of these companies has revealed this issue, this is 
 therefore preventing the move of the solution into production. 
 We cannot revert to the use of the version 3.2.2 of AMQ as there are some 
 memory limitations with this version (that have been addressed in 4.x) that 
 mean that it will not cope with the volumes of messages that are required to 
 be handled. 
 Thanks,
 Stephen Murray

-- 
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: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)

[Adrian Co]

+1 :)

Hiram Chirino wrote:

Howdy ActiveMQ Mentors...

This is just a gentle reminder that this vote is still open and
looking for at least 1 more incubator PMC binding vote to make it
official.  Please take a moment and review the release.

Thanks!

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

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

[Adrian Co]

+1 about time. :)

Hiram Chirino 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 ??

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

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1036.


Resolution: Fixed

Fix applied to 4.1 branch at rev 475831

 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
 Assigned To: Adrian Co
 Fix For: 4.1.1, 4.2.0


 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] Commented: (AMQ-1050) browse -QTopic=* does not seem to return anything...

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1050:


I've added a fix for this issue in rev 475901.

BTW, if we are going to move to Java 1.5, are we still going to use mx4j or the 
jmx implementation of java 1.5?

JMX supposedly has this query mechanism to perform better object name querying 
and I want to use that instead of the regex thing. Last time I checked though, 
mx4j doesn't seem to support it, so I want to check if Java 1.5 has or the 
recent mx4j version has it. I'll keep this JIRA open to remind.

 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

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

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-1050:
---

Fix Version/s: 4.1.1

I might as well commit add this in the 4.1 branch also. :)

 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, 4.1.1


 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

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

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1050:


Fix added to 4.1 branch via r475929

 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, 4.1.1


 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

[jira] Resolved: (AMQ-1048) Some tools from Command line not works properly

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1048.


Resolution: Fixed

I've added a fix for this in the 4.1 (r475929) and 4.2 (r475901) branch.

The fix is only for the format parameter -QXXX=YYY. The --objname parameter 
seems to be working fine. I'd try adding quotes to the param when using in 
WinXP (I'm not sure about linux though). i.e. query -QTopic=XXX --objname 
Type=Topic,Destination=XXX.

 Some tools from Command line not works properly
 ---

 Key: AMQ-1048
 URL: https://issues.apache.org/activemq/browse/AMQ-1048
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.1
 Environment: Tested in Windows XP Professional and Linux Debian Sarge
Reporter: Lucas GPL
 Assigned To: Adrian Co
Priority: Critical
   Original Estimate: 2 days
  Remaining Estimate: 2 days

 Some command line not works properly, just return de prompt 
 Example: 
 query -QQueue=* 
 query --objname Type=Connect,BrokerName=localhost -xQNetworkConnector=* 
 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] Updated: (AMQ-1048) Some tools from Command line not works properly

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-1048:
---

Fix Version/s: 4.1.1
   4.2.0

 Some tools from Command line not works properly
 ---

 Key: AMQ-1048
 URL: https://issues.apache.org/activemq/browse/AMQ-1048
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.1
 Environment: Tested in Windows XP Professional and Linux Debian Sarge
Reporter: Lucas GPL
 Assigned To: Adrian Co
Priority: Critical
 Fix For: 4.2.0, 4.1.1

   Original Estimate: 2 days
  Remaining Estimate: 2 days

 Some command line not works properly, just return de prompt 
 Example: 
 query -QQueue=* 
 query --objname Type=Connect,BrokerName=localhost -xQNetworkConnector=* 
 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: Lets vote: activemq-cpp-1.0 release

[Adrian Co]

+1 :)

Timothy Bish wrote:

I think it's about time we start this ball rolling, so let's take a vote on
whether to call the source archive located here:
http://people.apache.org/~tabish the official 1.0 release of activemq-cpp

 What do you think, is it time to put this one to bed?

-
Timothy A. Bish


  

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

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1017:


I just did a fresh checkout of 
https://svn.apache.org/repos/asf/incubator/activemq/trunk with rev 473001.

Running in WinXP, did a mvn install -Dmaven.test.skip=true with a clean repo 
and it built successfully for me. :-/

 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-472933.log, 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

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1017:


Also using maven-2.0.4 and java version 1.5.0_07

 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-472933.log, 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-1028) AMQ Stops dispatching messages after a period of time without errors/warnings

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1028:


Could you provide more details of the setup?

Are you using a cluster of brokers or a standalone broker?

Are you using the default persistence adapter?

Are you sending persistent messages or non-persistent messages?

Do you have durable subscribers or non-durable subscribers?

Are your subscribers connected all the time and is consuming messages every 
time?

If you can provide a small test case to replicate this issue, it will make it 
easier to fix. :)

 AMQ Stops dispatching messages after a period of time without errors/warnings
 -

 Key: AMQ-1028
 URL: https://issues.apache.org/activemq/browse/AMQ-1028
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0.2
 Environment: Os: Ubuntu Linux i386 - Java: J2RE SE 1.5.0_08-b03
Reporter: Bas van Beek
Priority: Critical

 The ActiveMQ stand alone server seems to stop dispatching messages to topics 
 after a period of time. 
 New clients can connect... new subscriptions to topics can be made... no 
 errors are shown... messages are just not sent... including to and from the 
 new clients...
 No errors or warnings can be found in the ActiveMQ.log (even in debug mode)
 JConsole doesn't show the new messages coming in (EnqueueCount doesn't change)
 Stomp Protocol is used exclusively

-- 
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] Assigned: (AMQ-1024) Exclusive Consumer Losing a Message

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-1024:
--

Assignee: Adrian Co

 Exclusive Consumer Losing a Message
 ---

 Key: AMQ-1024
 URL: https://issues.apache.org/activemq/browse/AMQ-1024
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.1
 Environment: Windows XP
Reporter: M H
 Assigned To: Adrian Co

 In my test, I have two consumers, one is set to be an exclusive consumer.  
 The exclusive consumer is started last.  If a producer sends 10 messages, one 
 message goes to the non-exclusive consumer while the other 9 messages go to 
 the exclusive consumer.  I would think all the messages should go to the 
 exclusive consumer even though it is started after the non-exclusive 
 consumer.  Both consumers were started before the producer sent any messages.

-- 
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-1024) Exclusive Consumer Losing a Message

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1024.


Fix Version/s: 4.1
   Resolution: Fixed

Hi,

I've fixed this in trunk rev 473219.

Maybe you can try the latest version in trunk. :)

 Exclusive Consumer Losing a Message
 ---

 Key: AMQ-1024
 URL: https://issues.apache.org/activemq/browse/AMQ-1024
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.1
 Environment: Windows XP
Reporter: M H
 Assigned To: Adrian Co
 Fix For: 4.1


 In my test, I have two consumers, one is set to be an exclusive consumer.  
 The exclusive consumer is started last.  If a producer sends 10 messages, one 
 message goes to the non-exclusive consumer while the other 9 messages go to 
 the exclusive consumer.  I would think all the messages should go to the 
 exclusive consumer even though it is started after the non-exclusive 
 consumer.  Both consumers were started before the producer sent any messages.

-- 
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-1033) Intermittent ArrayIndexOutOfBoundsException during send and receive

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-1033:
---

Attachment: openwireformat.patch

Added a possible fix to the issue.

 Intermittent ArrayIndexOutOfBoundsException during send and receive
 ---

 Key: AMQ-1033
 URL: https://issues.apache.org/activemq/browse/AMQ-1033
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1
 Environment: winxp
Reporter: Adrian Co
 Assigned To: Rob Davies
 Fix For: 4.1

 Attachments: openwireformat.patch


Send and receive with multiple jms clients with a single broker.
  [java] WARNING: Async exception with no exception listener: 
 java.lang.ArrayIndexOutOfBoundsException
  [java] java.lang.ArrayIndexOutOfBoundsException
  [java] at java.lang.System.arraycopy(Native Method)
  [java] at 
 org.apache.activemq.util.DataByteArrayOutputStream.ensureEnoughBuffer(DataByteArrayOutputSt
 ream.java:249)
  [java] at 
 org.apache.activemq.util.DataByteArrayOutputStream.writeBoolean(DataByteArrayOutputStream.j
 ava:141)
  [java] at 
 org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.looseMarshalByteSequence(BaseDataS
 treamMarshaller.java:588)
  [java] at 
 org.apache.activemq.openwire.v2.MessageMarshaller.looseMarshal(MessageMarshaller.java:262)
  [java] at 
 org.apache.activemq.openwire.v2.ActiveMQMessageMarshaller.looseMarshal(ActiveMQMessageMarsh
 aller.java:111)
  [java] at 
 org.apache.activemq.openwire.v2.ActiveMQTextMessageMarshaller.looseMarshal(ActiveMQTextMess
 ageMarshaller.java:111)
  [java] at 
 org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:167)
  [java] at 
 org.apache.activemq.store.journal.JournalPersistenceAdapter.writeCommand(JournalPersistence
 Adapter.java:596)
  [java] at 
 org.apache.activemq.store.journal.JournalMessageStore.addMessage(JournalMessageStore.java:9
 5)
  [java] at 
 org.apache.activemq.store.journal.JournalTopicMessageStore.addMessage(JournalTopicMessageSt
 ore.java:77)
  [java] at 
 org.apache.activemq.broker.region.Topic.send(Topic.java:246)
  [java] at 
 org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:292)
  [java] at 
 org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:380)
  [java] at 
 org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
  [java] at 
 org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
  [java] at 
 org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:
 98)
  [java] at 
 org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:136)
  [java] at 
 org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:480)
  [java] at 
 org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
  [java] at 
 org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284)
  [java] at 
 org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177)
  [java] at 
 org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
  [java] at 
 org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
  [java] at 
 org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
  [java] at 
 org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
  [java] at 
 org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
  [java] at java.lang.Thread.run(Thread.java:595)

-- 
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-1033) Intermittent ArrayIndexOutOfBoundsException during send and receive

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1033.


Resolution: Fixed

Seems to be fixed by commit: r472421

 Intermittent ArrayIndexOutOfBoundsException during send and receive
 ---

 Key: AMQ-1033
 URL: https://issues.apache.org/activemq/browse/AMQ-1033
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1
 Environment: winxp
Reporter: Adrian Co
 Assigned To: Rob Davies
 Fix For: 4.1

 Attachments: openwireformat.patch


Send and receive with multiple jms clients with a single broker.
  [java] WARNING: Async exception with no exception listener: 
 java.lang.ArrayIndexOutOfBoundsException
  [java] java.lang.ArrayIndexOutOfBoundsException
  [java] at java.lang.System.arraycopy(Native Method)
  [java] at 
 org.apache.activemq.util.DataByteArrayOutputStream.ensureEnoughBuffer(DataByteArrayOutputSt
 ream.java:249)
  [java] at 
 org.apache.activemq.util.DataByteArrayOutputStream.writeBoolean(DataByteArrayOutputStream.j
 ava:141)
  [java] at 
 org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.looseMarshalByteSequence(BaseDataS
 treamMarshaller.java:588)
  [java] at 
 org.apache.activemq.openwire.v2.MessageMarshaller.looseMarshal(MessageMarshaller.java:262)
  [java] at 
 org.apache.activemq.openwire.v2.ActiveMQMessageMarshaller.looseMarshal(ActiveMQMessageMarsh
 aller.java:111)
  [java] at 
 org.apache.activemq.openwire.v2.ActiveMQTextMessageMarshaller.looseMarshal(ActiveMQTextMess
 ageMarshaller.java:111)
  [java] at 
 org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:167)
  [java] at 
 org.apache.activemq.store.journal.JournalPersistenceAdapter.writeCommand(JournalPersistence
 Adapter.java:596)
  [java] at 
 org.apache.activemq.store.journal.JournalMessageStore.addMessage(JournalMessageStore.java:9
 5)
  [java] at 
 org.apache.activemq.store.journal.JournalTopicMessageStore.addMessage(JournalTopicMessageSt
 ore.java:77)
  [java] at 
 org.apache.activemq.broker.region.Topic.send(Topic.java:246)
  [java] at 
 org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:292)
  [java] at 
 org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:380)
  [java] at 
 org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
  [java] at 
 org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
  [java] at 
 org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:
 98)
  [java] at 
 org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:136)
  [java] at 
 org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:480)
  [java] at 
 org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
  [java] at 
 org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284)
  [java] at 
 org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177)
  [java] at 
 org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
  [java] at 
 org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)
  [java] at 
 org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
  [java] at 
 org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
  [java] at 
 org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
  [java] at java.lang.Thread.run(Thread.java:595)

-- 
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

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-1017:


I just built the trunk and its working fine for me (WinXP). Though, I did see 
this once, but was unable to reproduce it. Are you able to consistently 
reproduce this? Maybe you can try mvn install -U

 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

[jira] Created: (AMQ-1033) Intermittent ArrayIndexOutOfBoundsException during send and receive

[Adrian Co (JIRA)]

Intermittent ArrayIndexOutOfBoundsException during send and receive
---

 Key: AMQ-1033
 URL: https://issues.apache.org/activemq/browse/AMQ-1033
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1
 Environment: winxp
Reporter: Adrian Co
 Assigned To: Rob Davies
 Fix For: 4.1


   Send and receive with multiple jms clients with a single broker.

 [java] WARNING: Async exception with no exception listener: 
java.lang.ArrayIndexOutOfBoundsException
 [java] java.lang.ArrayIndexOutOfBoundsException
 [java] at java.lang.System.arraycopy(Native Method)
 [java] at 
org.apache.activemq.util.DataByteArrayOutputStream.ensureEnoughBuffer(DataByteArrayOutputSt
ream.java:249)
 [java] at 
org.apache.activemq.util.DataByteArrayOutputStream.writeBoolean(DataByteArrayOutputStream.j
ava:141)
 [java] at 
org.apache.activemq.openwire.v2.BaseDataStreamMarshaller.looseMarshalByteSequence(BaseDataS
treamMarshaller.java:588)
 [java] at 
org.apache.activemq.openwire.v2.MessageMarshaller.looseMarshal(MessageMarshaller.java:262)
 [java] at 
org.apache.activemq.openwire.v2.ActiveMQMessageMarshaller.looseMarshal(ActiveMQMessageMarsh
aller.java:111)
 [java] at 
org.apache.activemq.openwire.v2.ActiveMQTextMessageMarshaller.looseMarshal(ActiveMQTextMess
ageMarshaller.java:111)
 [java] at 
org.apache.activemq.openwire.OpenWireFormat.marshal(OpenWireFormat.java:167)
 [java] at 
org.apache.activemq.store.journal.JournalPersistenceAdapter.writeCommand(JournalPersistence
Adapter.java:596)
 [java] at 
org.apache.activemq.store.journal.JournalMessageStore.addMessage(JournalMessageStore.java:9
5)
 [java] at 
org.apache.activemq.store.journal.JournalTopicMessageStore.addMessage(JournalTopicMessageSt
ore.java:77)
 [java] at org.apache.activemq.broker.region.Topic.send(Topic.java:246)
 [java] at 
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:292)
 [java] at 
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:380)
 [java] at 
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.java:193)
 [java] at 
org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:126)
 [java] at 
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeDestinationBroker.java:
98)
 [java] at 
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilter.java:136)
 [java] at 
org.apache.activemq.broker.TransportConnection.processMessage(TransportConnection.java:480)

 [java] at 
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.java:604)
 [java] at 
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:284)
 [java] at 
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:177)
 [java] at 
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
 [java] at 
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:133)

 [java] at 
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
 [java] at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
 [java] at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
 [java] at java.lang.Thread.run(Thread.java:595)

-- 
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-1019) Duplicate bean names (i.e. transportConnector/networkConnector names) in xml config causes exception in xbean.

[Adrian Co (JIRA)]

Duplicate bean names (i.e. transportConnector/networkConnector names) in xml 
config causes exception in xbean.
--

 Key: AMQ-1019
 URL: https://issues.apache.org/activemq/browse/AMQ-1019
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.1
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.1


Due to upgrade to xbean-2.7 and spring-2.0, beans with the same name/id will 
cause an exception in xbean/spring.

-- 
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-1015) ActiveMQ web-demo and web-console cannot be run

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-1015.


Resolution: Fixed

Backported to 4.0.x branch. rev 469583

 ActiveMQ web-demo and web-console cannot be run
 ---

 Key: AMQ-1015
 URL: https://issues.apache.org/activemq/browse/AMQ-1015
 Project: ActiveMQ
  Issue Type: Bug
  Components: JMS client
Affects Versions: 4.1, 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.0.3, 4.1


 Let's update the maven plugin from maven-jetty-plugin to maven-jetty6-plugin 
 for the 4.1.x branch and the 4.0.x branch. The web-console is throwing this 
 exception after:
 java.lang.NoSuchMethodError: 
 org.mortbay.jetty.webapp.WebAppClassLoader.getUrlClassPath()Ljava/lang/String;
 at 
 org.mortbay.jetty.plugin.Jetty6MavenConfiguration.configureClassLoader(Jetty6MavenConfiguration.jav
 a:62)
 at 
 org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453)
 at 
 org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
 at 
 org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
 at 
 org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
 at 
 org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
 at 
 org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
 at 
 org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
 at 
 org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
 at org.mortbay.jetty.Server.doStart(Server.java:210)
 at 
 org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:38)
 at 
 org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:115)
 at 
 org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:318)
 at 
 org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:268)
 at 
 org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:172)
 at 
 org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:167)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.
 java:488)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleEx
 ecutor.java:306)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.ja
 va:273)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
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] Reopened: (AMQ-801) activemq-jaas is not in the release distro

[Adrian Co (JIRA)]

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

Adrian Co reopened AMQ-801:
---

  Assignee: Adrian Co
 
The activemq-jaas is not being bundled with the distro

 activemq-jaas is not in the release distro
 --

 Key: AMQ-801
 URL: https://issues.apache.org/activemq/browse/AMQ-801
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.1, 4.0.1, 4.0.2
Reporter: james strachan
 Assigned To: Adrian Co
 Fix For: 4.1


 it should be in the activemq.jar and in the lib directory...

-- 
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-801) activemq-jaas is not in the release distro

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-801.
---

Resolution: Fixed

Fix to assembly committed. rev 469670

 activemq-jaas is not in the release distro
 --

 Key: AMQ-801
 URL: https://issues.apache.org/activemq/browse/AMQ-801
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.1, 4.0.1, 4.0.2
Reporter: james strachan
 Assigned To: Adrian Co
 Fix For: 4.1


 it should be in the activemq.jar and in the lib directory...

-- 
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-1003) ConnectionDotFile

[Adrian Co (JIRA)]

ConnectionDotFile
-

 Key: AMQ-1003
 URL: https://issues.apache.org/activemq/browse/AMQ-1003
 Project: ActiveMQ
  Issue Type: Bug
Reporter: Adrian Co




-- 
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-1003) ConnectionDotFilePlugin cannot support broker with a non-localhost broker name

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-1003:
---

  Summary: ConnectionDotFilePlugin cannot support broker with a 
non-localhost broker name  (was: ConnectionDotFile)
Affects Version/s: 4.1
  Description: The ConnectionDotFilePlugin creates a BrokerViewMBean, 
but uses the localhost as its broker name. This prevents a broker with a 
different name from using it. (throws instancenotfound exception)
 Priority: Minor  (was: Major)

 ConnectionDotFilePlugin cannot support broker with a non-localhost broker name
 --

 Key: AMQ-1003
 URL: https://issues.apache.org/activemq/browse/AMQ-1003
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.1
Reporter: Adrian Co
Priority: Minor

 The ConnectionDotFilePlugin creates a BrokerViewMBean, but uses the localhost 
 as its broker name. This prevents a broker with a different name from using 
 it. (throws instancenotfound exception)

-- 
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: [VOTE] Release Apache ActiveMQ 4.0.2 (RC 5)

[Adrian Co]

+1

Hiram Chirino wrote:

Some copyright header/licence/notice issues were found in the 4th release
candidate of the
4.0.2 build.  I have cut and RC 5 of the 4.0.2 build with the fixes 
and it's

available here:

http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC5/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-RC5

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

[jira] Resolved: (AMQ-942) ActiveMQStreamMessage should support large text format in writeString.

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-942.
---

Fix Version/s: 4.1
   Resolution: Fixed

rev: r452793
Added support for writing and reading of large strings in 
ActiveMQStreamMessage. Also, refactored ActiveMQStreamMessage to also use the 
MarshallingSupport utility.

NOTE: Refactoring the ActiveMQStreamMessage to use the MarshallingSupport 
utility will make it incompatible with previous versions as the wireformat has 
been changed. It is advisable to clear existing messages and use clients with 
the same version.

 ActiveMQStreamMessage should support large text format in writeString.
 --

 Key: AMQ-942
 URL: https://issues.apache.org/activemq/browse/AMQ-942
 Project: ActiveMQ
  Issue Type: Bug
  Components: JMS client
Affects Versions: 4.1, 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
Priority: Critical
 Fix For: 4.1


 I was wondering if ActiveMQStreamMessage should support large text messages 
 also, since MapMessage is also able to support this.

-- 
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

Changes in ActiveMQStreamMessage wireformat

[Adrian Co]

Hi,

I refactored the ActiveMQStreamMessage to also use the 
MarshallingSupport utility to write its data. This cause some changes in 
the wireformat of ActiveMQStreamMessage. So there would be wireformat 
incompatibility from r452793 and up with previous revisions. It is 
advisable to clear your message database to prevent any wireformat 
problems. :) Hope this is not too much of an inconvenience.


Regards,
Adrian Co

[jira] Created: (AMQ-948) Bug in 4.0 branch where the AMQ classpath is incorrectly determined.

[Adrian Co (JIRA)]

Bug in 4.0 branch where the AMQ classpath is incorrectly determined.


 Key: AMQ-948
 URL: https://issues.apache.org/activemq/browse/AMQ-948
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.0.3




-- 
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-949) Bug in 4.0 branch where a JMX connector is not created when the AMQ broker piggys back on an existing mbean server

[Adrian Co (JIRA)]

Bug in 4.0 branch where a JMX connector is not created when the AMQ broker 
piggys back on an existing mbean server
--

 Key: AMQ-949
 URL: https://issues.apache.org/activemq/browse/AMQ-949
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.0.3




-- 
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-948) Bug in 4.0 branch where the AMQ classpath is incorrectly determined.

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-948:
---

Backported fix from 4.1 branch
rev 451583

 Bug in 4.0 branch where the AMQ classpath is incorrectly determined.
 

 Key: AMQ-948
 URL: https://issues.apache.org/activemq/browse/AMQ-948
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.0.3




-- 
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-949) Bug in 4.0 branch where a JMX connector is not created when the AMQ broker piggys back on an existing mbean server

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-949.
---

Resolution: Fixed

Backported fix from 4.1 branch.
rev 451584

 Bug in 4.0 branch where a JMX connector is not created when the AMQ broker 
 piggys back on an existing mbean server
 --

 Key: AMQ-949
 URL: https://issues.apache.org/activemq/browse/AMQ-949
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.0.2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 4.0.3




-- 
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-935) Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-935.
---

Resolution: Fixed

Added test case for JmsLogAppender.
rev 451170

 Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1
 ---

 Key: AMQ-935
 URL: https://issues.apache.org/activemq/browse/AMQ-935
 Project: ActiveMQ
  Issue Type: New Feature
Affects Versions: 4.1
Reporter: Bruce Snyder
 Assigned To: Adrian Co
 Attachments: JmsLogAppenderSupport.diff.txt


 Porting the following classes from ACTIVEMQ_3_2_4: 
 {code}
 modules/core/src/test/org/activemq/util/test-log4j.properties
 modules/core/src/java/org/activemq/util/JmsLogAppender.java
 modules/core/src/java/org/activemq/util/JmsLogAppenderSupport.java
 modules/core/src/java/org/activemq/util/JndiJmsLogAppender.java
 modules/core/src/test/org/activemq/util/JmsLogAppenderTest.java
 {code}
 to ActiveMQ 4.1: 
 {code}
 activemq-optional/src/test/java/org/apache/activemq/util
 activemq-optional/src/test/java/org/apache/activemq/util/JmsLogAppenderTest.java
 activemq-optional/src/test/resources/test-log4j.properties
 activemq-optional/src/main/java/org/apache/activemq/util
 activemq-optional/src/main/java/org/apache/activemq/util/JndiJmsLogAppender.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppenderSupport.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppender.java
 {code}

-- 
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-942) ActiveMQStreamMessage should support large text format in writeString.

[Adrian Co (JIRA)]

ActiveMQStreamMessage should support large text format in writeString.
--

 Key: AMQ-942
 URL: https://issues.apache.org/activemq/browse/AMQ-942
 Project: ActiveMQ
  Issue Type: Bug
  Components: JMS client
Affects Versions: 4.0.2, 4.1
Reporter: Adrian Co
 Assigned To: Hiram Chirino
Priority: Critical


I was wondering if ActiveMQStreamMessage should support large text messages 
also, since MapMessage is also able to support this.

-- 
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] Assigned: (AMQ-935) Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-935:
-

Assignee: Adrian Co  (was: Hiram Chirino)

 Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1
 ---

 Key: AMQ-935
 URL: https://issues.apache.org/activemq/browse/AMQ-935
 Project: ActiveMQ
  Issue Type: New Feature
Affects Versions: 4.1
Reporter: Bruce Snyder
 Assigned To: Adrian Co
 Attachments: JmsLogAppenderSupport.diff.txt


 Porting the following classes from ACTIVEMQ_3_2_4: 
 {code}
 modules/core/src/test/org/activemq/util/test-log4j.properties
 modules/core/src/java/org/activemq/util/JmsLogAppender.java
 modules/core/src/java/org/activemq/util/JmsLogAppenderSupport.java
 modules/core/src/java/org/activemq/util/JndiJmsLogAppender.java
 modules/core/src/test/org/activemq/util/JmsLogAppenderTest.java
 {code}
 to ActiveMQ 4.1: 
 {code}
 activemq-optional/src/test/java/org/apache/activemq/util
 activemq-optional/src/test/java/org/apache/activemq/util/JmsLogAppenderTest.java
 activemq-optional/src/test/resources/test-log4j.properties
 activemq-optional/src/main/java/org/apache/activemq/util
 activemq-optional/src/main/java/org/apache/activemq/util/JndiJmsLogAppender.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppenderSupport.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppender.java
 {code}

-- 
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-935) Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-935:
---

Patch applied. Just need to update the test case to properly test the 
functionality.

 Port the JmsLogAppender API from ActiveMQ 3.2.4 to ActiveMQ 4.1
 ---

 Key: AMQ-935
 URL: https://issues.apache.org/activemq/browse/AMQ-935
 Project: ActiveMQ
  Issue Type: New Feature
Affects Versions: 4.1
Reporter: Bruce Snyder
 Assigned To: Adrian Co
 Attachments: JmsLogAppenderSupport.diff.txt


 Porting the following classes from ACTIVEMQ_3_2_4: 
 {code}
 modules/core/src/test/org/activemq/util/test-log4j.properties
 modules/core/src/java/org/activemq/util/JmsLogAppender.java
 modules/core/src/java/org/activemq/util/JmsLogAppenderSupport.java
 modules/core/src/java/org/activemq/util/JndiJmsLogAppender.java
 modules/core/src/test/org/activemq/util/JmsLogAppenderTest.java
 {code}
 to ActiveMQ 4.1: 
 {code}
 activemq-optional/src/test/java/org/apache/activemq/util
 activemq-optional/src/test/java/org/apache/activemq/util/JmsLogAppenderTest.java
 activemq-optional/src/test/resources/test-log4j.properties
 activemq-optional/src/main/java/org/apache/activemq/util
 activemq-optional/src/main/java/org/apache/activemq/util/JndiJmsLogAppender.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppenderSupport.java
 activemq-optional/src/main/java/org/apache/activemq/util/JmsLogAppender.java
 {code}

-- 
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: (SM-482) Missing jars in the BPE component

[Adrian Co (JIRA)]

[ 
https://issues.apache.org/activemq/browse/SM-482?page=comments#action_36982 ] 

Adrian Co commented on SM-482:
--

This is the exception I am getting:

jvm 1| org.apache.ode.bpe.deployment.bpel.DeploymentException: Native 
Exception: SAXException. Native Mess
age: com/sun/msv/datatype/DatabindableDatatype
jvm 1|  at 
org.apache.ode.bpe.deployment.bpel.BPELParser.parseBPEL(BPELParser.java:107)
jvm 1|  at 
org.apache.ode.bpe.deployment.bpel.BPELDeploy.deployJar(BPELDeploy.java:177)
jvm 1|  at 
org.apache.ode.bpe.bped.unmanaged.BPELDeployerSLImpl.loadDefinition(BPELDeployerSLImpl.java
:78)
jvm 1|  at 
org.apache.servicemix.bpe.BPEDeployer.deploy(BPEDeployer.java:86)
jvm 1|  at 
org.apache.servicemix.common.BaseServiceUnitManager.doDeploy(BaseServiceUnitManager.java:88
)
jvm 1|  at 
org.apache.servicemix.common.BaseServiceUnitManager.init(BaseServiceUnitManager.java:107)
jvm 1|  at 
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.init(ServiceUnitLifeCycle.java:85)

jvm 1|  at 
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle
.java:121)
jvm 1|  at 
org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCyc
le.java:328)
jvm 1|  at 
org.apache.servicemix.jbi.framework.DeploymentService.start(DeploymentService.java:97)
jvm 1|  at 
org.apache.servicemix.jbi.container.JBIContainer.start(JBIContainer.java:595)
jvm 1|  at 
org.apache.servicemix.jbi.container.SpringJBIContainer.afterPropertiesSet(SpringJBIContaine
r.java:79)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMeth
ods(AbstractAutowireCapableBeanFactory.java:957)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:924)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Abs
tractAutowireCapableBeanFactory.java:415)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFacto
ry.java:242)
jvm 1|  at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(Default
SingletonBeanRegistry.java:141)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.j
ava:239)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.j
ava:155)
jvm 1|  at 
org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingleto
ns(DefaultListableBeanFactory.java:303)
jvm 1|  at 
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationC
ontext.java:348)
jvm 1|  at 
org.apache.xbean.server.spring.configuration.SpringConfiguration.init(SpringConfiguration
.java:63)
jvm 1|  at 
org.apache.xbean.server.spring.configuration.SpringConfigurationServiceFactory.createServic
e(SpringConfigurationServiceFactory.java:106)
jvm 1|  at 
org.apache.xbean.kernel.standard.ServiceManager.start(ServiceManager.java:420)
jvm 1|  at 
org.apache.xbean.kernel.standard.ServiceManager.initialize(ServiceManager.java:200)
jvm 1|  at 
org.apache.xbean.kernel.standard.RegistryFutureTask$RegisterCallable.call(RegistryFutureTas
k.java:110)
jvm 1|  at 
edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
jvm 1|  at 
org.apache.xbean.kernel.standard.ServiceManagerRegistry.registerService(ServiceManagerRegis
try.java:409)
jvm 1|  at 
org.apache.xbean.kernel.standard.StandardKernel.registerService(StandardKernel.java:220)
jvm 1|  at 
org.apache.xbean.server.deployer.FileDeployer.createServiceForFile(FileDeployer.java:350)
jvm 1|  at 
org.apache.xbean.server.deployer.FileDeployer.processDirectory(FileDeployer.java:275)
jvm 1|  at 
org.apache.xbean.server.deployer.FileDeployer.processDirectory(FileDeployer.java:294)
jvm 1|  at 
org.apache.xbean.server.deployer.FileDeployer.processDirectory(FileDeployer.java:286)
jvm 1|  at 
org.apache.xbean.server.deployer.FileDeployer.afterPropertiesSet(FileDeployer.java:86)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMeth
ods(AbstractAutowireCapableBeanFactory.java:957)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:924)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(Abs
tractAutowireCapableBeanFactory.java:415)
jvm 1|  at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFacto

[jira] Resolved: (AMQ-925) unix src download labled with 'Source for Windows'

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-925.
---

Resolution: Fixed

 unix src download labled with 'Source for Windows'
 --

 Key: AMQ-925
 URL: https://issues.apache.org/activemq/browse/AMQ-925
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Bill Dudney
 Assigned To: Adrian Co
Priority: Trivial

 http://incubator.apache.org/activemq/activemq-401-release.html
 right hand column
 Binary for Window
 Source code for Windows
 Binary for Unix   
 Source code for Windows
 final row should say Source code for Unix

-- 
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] Assigned: (AMQ-925) unix src download labled with 'Source for Windows'

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-925:
-

Assignee: Adrian Co

 unix src download labled with 'Source for Windows'
 --

 Key: AMQ-925
 URL: https://issues.apache.org/activemq/browse/AMQ-925
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Bill Dudney
 Assigned To: Adrian Co
Priority: Trivial

 http://incubator.apache.org/activemq/activemq-401-release.html
 right hand column
 Binary for Window
 Source code for Windows
 Binary for Unix   
 Source code for Windows
 final row should say Source code for Unix

-- 
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-925) unix src download labled with 'Source for Windows'

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-925:
---

Applied changes. Thanks for the heads up Bill. :)

WIll just wait until the changes has been verified before resolving this issue.

 unix src download labled with 'Source for Windows'
 --

 Key: AMQ-925
 URL: https://issues.apache.org/activemq/browse/AMQ-925
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: Bill Dudney
 Assigned To: Adrian Co
Priority: Trivial

 http://incubator.apache.org/activemq/activemq-401-release.html
 right hand column
 Binary for Window
 Source code for Windows
 Binary for Unix   
 Source code for Windows
 final row should say Source code for Unix

-- 
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-915) Failover transport does not replay all the transaction operations on failover.

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-915:
---

Fix was applied to revision: 443271 in the trunk. Thanks for the heads up 
Hiram. Sorry for the confusion.


 Failover transport does not replay all the transaction operations on failover.
 --

 Key: AMQ-915
 URL: https://issues.apache.org/activemq/browse/AMQ-915
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Adrian Co
 Fix For: 4.1


 If transactions are being used on a connection that is using failover.. these 
 is a small chance that the transaction will fail or the connection will fail 
 due to a partial tx being run when the client reconnects.
 I will change the failover transport to buffer up all the tx operations that 
 are run against the broker and on failure, replay those operations.

-- 
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-915) Failover transport does not replay all the transaction operations on failover.

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-915.
---

Resolution: Fixed

 Failover transport does not replay all the transaction operations on failover.
 --

 Key: AMQ-915
 URL: https://issues.apache.org/activemq/browse/AMQ-915
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Adrian Co
 Fix For: 4.1


 If transactions are being used on a connection that is using failover.. these 
 is a small chance that the transaction will fail or the connection will fail 
 due to a partial tx being run when the client reconnects.
 I will change the failover transport to buffer up all the tx operations that 
 are run against the broker and on failure, replay those operations.

-- 
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-915) Failover transport does not replay all the transaction operations on failover.

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-915:
--

Fix Version/s: 4.0.3

Update the fix version to include 4.1 and 4.0.3

 Failover transport does not replay all the transaction operations on failover.
 --

 Key: AMQ-915
 URL: https://issues.apache.org/activemq/browse/AMQ-915
 Project: ActiveMQ
  Issue Type: Bug
Affects Versions: 4.0
Reporter: Hiram Chirino
 Assigned To: Adrian Co
 Fix For: 4.1, 4.0.3


 If transactions are being used on a connection that is using failover.. these 
 is a small chance that the transaction will fail or the connection will fail 
 due to a partial tx being run when the client reconnects.
 I will change the failover transport to buffer up all the tx operations that 
 are run against the broker and on failure, replay those operations.

-- 
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 3.0

[Adrian Co]

That will be great! :)

+1

Guillaume Nodet wrote:

I'd like to cut branch and start the
release process for ServiceMix 3.0
tomorrow.
Any objections ?

Re: [jira] Commented: (AMQ-899) mvn test fails with com.thoughtworks.qdox.parser.ParseException: syntax error @[90,25] in file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConne

[Adrian Co]

By all means, submit your patch by attaching it to the JIRA issue. We 
always welcome patches. :)

https://issues.apache.org/activemq/browse/AMQ-899

Sepand M wrote:

God speed!!
Will you be done any time soon?
I have a patch ready and I'm dying to submit it.

On 8/29/06, Adrian Co (JIRA) [EMAIL PROTECTED] wrote:
[ 
https://issues.apache.org/activemq/browse/AMQ-899?page=comments#action_36876 
]


Adrian Co commented on AMQ-899:
---

I've encountered this issue and the problem could be qdox-1.6 used by 
the maven-xbean-plugin. Workaround that I can think of for now, is to 
use qdox-1.5 (but I have to hack the pom of xbean, not good.) or to 
maybe try downgrading to a lower version of xbean 2.5 maybe? (haven't 
tried this yet though. :) )


 mvn test fails with com.thoughtworks.qdox.parser.ParseException: 
syntax error @[90,25] in 
file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConnector.java 

 
- 



 Key: AMQ-899
 URL: https://issues.apache.org/activemq/browse/AMQ-899
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.x
 Environment: Linux (RHEL3) and Windows XP
Reporter: Maxim Fateev

 svn co https://svn.apache.org/repos/asf/incubator/activemq/trunk
 
 Atrunk/README.txt
  U   trunk
 Checked out revision 437779.
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head ls
 trunk/
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head cd trunk/activemq-core
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head/trunk/activemq-core 
mvn test

 [INFO] Scanning for projects...
 [INFO] 
 


 [INFO] Building ActiveMQ :: Core
 [INFO]task-segment: [test]
 [INFO] 
 

 [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: 
checking for updates from apache-snapshots
 [INFO] snapshot 
org.apache.maven.plugins:maven-resources-plugin:2.3-SNAPSHOT: 
checking for updates from apache-snapshots

 ...
 ...
 ...
 Downloading: 
http://people.apache.org/maven-snapshot-repository/org/apache/activemq/maven-gram-plugin/4.1-incubator-SNAPSHOT/maven-gram-plugin-4.1-incubator-20060803.174437-6.jar 


 6K downloaded
 [WARNING] While downloading javacc:javacc:3.2
   This artifact has been relocated to net.java.dev.javacc:javacc:3.2.
 [INFO] [javacc:javacc {execution: default}]
 Java Compiler Compiler Version 3.2 (Parser Generator)
 (type javacc with no arguments for help)
 Reading from file 
/workplace/fateev/activemq-head/trunk/activemq-core/src/main/grammar/SelectorParser.jj 
. . .
 Note: UNICODE_INPUT option is specified. Please make sure you 
create the parser/lexer usig a Reader with the correct character 
encoding.

 File TokenMgrError.java does not exist.  Will create one.
 File ParseException.java does not exist.  Will create one.
 File Token.java does not exist.  Will create one.
 File SimpleCharStream.java does not exist.  Will create one.
 Parser generated successfully.
 Downloading: 
http://people.apache.org/maven-snapshot-repository/qdox/qdox/1.6/qdox-1.6.pom 

 [WARNING] Unable to get resource from repository apache-snapshots 
(http://people.apache.org/maven-snapshot-repository)

 Downloading: http://repository.codehaus.org/qdox/qdox/1.6/qdox-1.6.pom
 [WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)
 Downloading: 
http://dse.amazon.com:8081/proximity/repository/qdox/qdox/1.6/qdox-1.6.pom 


 4K downloaded
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: 
checking for updates from apache-snapshots
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: 
checking for updates from codehaus-snapshots
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: 
checking for updates from apache.snapshots
 Downloading: 
http://people.apache.org/maven-snapshot-repository/org/apache/xbean/xbean-spring/2.6-SNAPSHOT/xbean-spring-2.6-20060826.135020-8.pom 


 3K downloaded
 Downloading: 
http://people.apache.org/maven-snapshot-repository/org/apache/xbean/xbean-spring/2.6-SNAPSHOT/xbean-spring-2.6-20060826.135020-8.jar 


 143K downloaded
 Downloading: 
http://people.apache.org/maven-snapshot-repository/qdox/qdox/1.6/qdox-1.6.jar 

 [WARNING] Unable to get resource from repository apache-snapshots 
(http://people.apache.org/maven-snapshot-repository)

 Downloading: http://repository.codehaus.org/qdox/qdox/1.6/qdox-1.6.jar
 [WARNING] Unable to get resource from repository codehaus 
(http://repository.codehaus.org)
 Downloading: 
http://dse.amazon.com:8081/proximity/repository/qdox/qdox/1.6/qdox-1.6.jar 


 89K downloaded
 [INFO] [xbean:mapping {execution: default}]
 [INFO

[jira] Commented: (AMQ-899) mvn test fails with com.thoughtworks.qdox.parser.ParseException: syntax error @[90,25] in file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConnector

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-899:
---

I've encountered this issue and the problem could be qdox-1.6 used by the 
maven-xbean-plugin. Workaround that I can think of for now, is to use qdox-1.5 
(but I have to hack the pom of xbean, not good.) or to maybe try downgrading to 
a lower version of xbean 2.5 maybe? (haven't tried this yet though. :) )

 mvn test fails with com.thoughtworks.qdox.parser.ParseException: syntax 
 error @[90,25] in 
 file:.../activemq-core/src/main/java/org/apache/activemq/network/jms/JmsConnector.java
 -

 Key: AMQ-899
 URL: https://issues.apache.org/activemq/browse/AMQ-899
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 4.x
 Environment: Linux (RHEL3) and Windows XP
Reporter: Maxim Fateev

 svn co https://svn.apache.org/repos/asf/incubator/activemq/trunk
 
 Atrunk/README.txt
  U   trunk
 Checked out revision 437779.
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head ls
 trunk/
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head cd trunk/activemq-core
 [EMAIL PROTECTED]:/workplace/fateev/activemq-head/trunk/activemq-core mvn 
 test
 [INFO] Scanning for projects...
 [INFO] 
 
 [INFO] Building ActiveMQ :: Core
 [INFO]task-segment: [test]
 [INFO] 
 
 [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for 
 updates from apache-snapshots
 [INFO] snapshot org.apache.maven.plugins:maven-resources-plugin:2.3-SNAPSHOT: 
 checking for updates from apache-snapshots
 ...
 ...
 ...
 Downloading: 
 http://people.apache.org/maven-snapshot-repository/org/apache/activemq/maven-gram-plugin/4.1-incubator-SNAPSHOT/maven-gram-plugin-4.1-incubator-20060803.174437-6.jar
 6K downloaded
 [WARNING] While downloading javacc:javacc:3.2
   This artifact has been relocated to net.java.dev.javacc:javacc:3.2.
 [INFO] [javacc:javacc {execution: default}]
 Java Compiler Compiler Version 3.2 (Parser Generator)
 (type javacc with no arguments for help)
 Reading from file 
 /workplace/fateev/activemq-head/trunk/activemq-core/src/main/grammar/SelectorParser.jj
  . . .
 Note: UNICODE_INPUT option is specified. Please make sure you create the 
 parser/lexer usig a Reader with the correct character encoding.
 File TokenMgrError.java does not exist.  Will create one.
 File ParseException.java does not exist.  Will create one.
 File Token.java does not exist.  Will create one.
 File SimpleCharStream.java does not exist.  Will create one.
 Parser generated successfully.
 Downloading: 
 http://people.apache.org/maven-snapshot-repository/qdox/qdox/1.6/qdox-1.6.pom
 [WARNING] Unable to get resource from repository apache-snapshots 
 (http://people.apache.org/maven-snapshot-repository)
 Downloading: http://repository.codehaus.org/qdox/qdox/1.6/qdox-1.6.pom
 [WARNING] Unable to get resource from repository codehaus 
 (http://repository.codehaus.org)
 Downloading: 
 http://dse.amazon.com:8081/proximity/repository/qdox/qdox/1.6/qdox-1.6.pom
 4K downloaded
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: checking for 
 updates from apache-snapshots
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: checking for 
 updates from codehaus-snapshots
 [INFO] snapshot org.apache.xbean:xbean-spring:2.6-SNAPSHOT: checking for 
 updates from apache.snapshots
 Downloading: 
 http://people.apache.org/maven-snapshot-repository/org/apache/xbean/xbean-spring/2.6-SNAPSHOT/xbean-spring-2.6-20060826.135020-8.pom
 3K downloaded
 Downloading: 
 http://people.apache.org/maven-snapshot-repository/org/apache/xbean/xbean-spring/2.6-SNAPSHOT/xbean-spring-2.6-20060826.135020-8.jar
 143K downloaded
 Downloading: 
 http://people.apache.org/maven-snapshot-repository/qdox/qdox/1.6/qdox-1.6.jar
 [WARNING] Unable to get resource from repository apache-snapshots 
 (http://people.apache.org/maven-snapshot-repository)
 Downloading: http://repository.codehaus.org/qdox/qdox/1.6/qdox-1.6.jar
 [WARNING] Unable to get resource from repository codehaus 
 (http://repository.codehaus.org)
 Downloading: 
 http://dse.amazon.com:8081/proximity/repository/qdox/qdox/1.6/qdox-1.6.jar
 89K downloaded
 [INFO] [xbean:mapping {execution: default}]
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] com.thoughtworks.qdox.parser.ParseException: syntax error @[90,25] in 
 file:/workplace/fateev/activemq-head/trunk/activemq-core/src/main

[jira] Assigned: (SM-482) Missing jars in the BPE component

[Adrian Co (JIRA)]

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

Adrian Co reassigned SM-482:


Assignee: Adrian Co  (was: Guillaume Nodet)

 Missing jars in the BPE component
 -

 Key: SM-482
 URL: https://issues.apache.org/activemq/browse/SM-482
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-bpe
Affects Versions: 3.0-M2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 3.0-M3


 Some missing jars in the BPE component:
 - http://repo.mergere.com/maven2/msv/msv/20050913/msv-20050913.jar
 - 
 http://repo.mergere.com/maven2/msv/relaxngDatatype/20050913/relaxngDatatype-20050913.jar
 - http://repo.mergere.com/maven2/msv/xsdlib/20050913/xsdlib-20050913.jar
 and maybe others.

-- 
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: (SM-542) NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.

[Adrian Co (JIRA)]

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

Adrian Co resolved SM-542.
--

Resolution: Fixed

Fix added to BPE Deployer and use the latest bpe jar.

 NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.
 

 Key: SM-542
 URL: https://issues.apache.org/activemq/browse/SM-542
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-bpe
Affects Versions: 3.0-M2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 3.0-M3


 NPE occurs in the ODE-BPE class when undeploying, redeploying, and then 
 running the loan broker demo.

-- 
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: (SM-542) NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.

[Adrian Co (JIRA)]

NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.


 Key: SM-542
 URL: https://issues.apache.org/activemq/browse/SM-542
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-bpe
Affects Versions: 3.0-M2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 3.0-M3


NPE occurs in the ODE-BPE class when undeploying, redeploying, and then running 
the loan broker demo.

-- 
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: (SM-543) NPE occurs in onMessage of JmsServiceComponent

[Adrian Co (JIRA)]

NPE occurs in onMessage of JmsServiceComponent
--

 Key: SM-543
 URL: https://issues.apache.org/activemq/browse/SM-543
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-components
Affects Versions: 3.0-M2
Reporter: Adrian Co
 Assigned To: Adrian Co


NPE occurs in JmsServiceComponent when it receives messages, but the component 
has not been actually started, hence the work manager has not been initalized.

-- 
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: (SM-542) NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.

[Adrian Co (JIRA)]

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

Adrian Co resolved SM-542.
--

Resolution: Fixed

fixed.

 NPE occurs in ODE-BPE when undeploying and redeploying the loan broker demo.
 

 Key: SM-542
 URL: https://issues.apache.org/activemq/browse/SM-542
 Project: ServiceMix
  Issue Type: Bug
  Components: servicemix-bpe
Affects Versions: 3.0-M2
Reporter: Adrian Co
 Assigned To: Adrian Co
 Fix For: 3.0-M3


 NPE occurs in the ODE-BPE class when undeploying, redeploying, and then 
 running the loan broker demo.

-- 
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: Graduate to a TLP?

[Adrian Co]

+1 to graduate.
+1 to TLP.

:)

Regards
Adrian Co

Brian McCallister wrote:
I'd like to start the ball rolling to have ActiveMQ graduate to a top 
level project at Apache.


The original intent was to become a sub-project of Geronimo, but I 
think that this would be a disservice to ActiveMQ, which is quite 
capable of standing on it's own, and therefore, should be a project in 
itsef rather than expanding the G umbrella.


Looking over the incubator checklist, everything seems to have been 
completed, we have been making releases (a good sign that a project 
has it together) and I do believe it is time :-)


Thoughts?

-Brian

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

[Adrian Co]

+1 to release.

Regards,
Adrian Co

Hiram Chirino wrote:

Some LICENSE file issues were found in the first release candidate of the
4.0.2 build.  I have cut and RC 2 of the 4.0.2 build with the fixes 
and it's

available here:


http://people.apache.org/~chirino/incubator-activemq-4.0.2-RC2/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-RC2

Here's the wiki page for the release notes (they should soon get 
mirrored to

the activemq static website) :
http://goopen.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0.2+Release

Please vote to approve this release binary

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

If this vote passes, then we will then ask the Incubator PMC for their
blessing to ship this release officially.

Here's my +1

[jira] Resolved: (AMQ-733) Minor renaming of kaha module

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-733.
---

Resolution: Fixed

Renamed KahaPersistentAdaptor to KahaPersistenceAdapter

 Minor renaming of kaha module
 -

 Key: AMQ-733
 URL: https://issues.apache.org/activemq/browse/AMQ-733
 Project: ActiveMQ
  Issue Type: Wish
  Components: Message Store
Affects Versions: 4.0
Reporter: Adrian Co
 Assigned To: Adrian Co
Priority: Trivial
 Fix For: 4.1


 I was wondering if we can rename KahaPersistentAdaptor to 
 KahaPersistenceAdapter just to be consistent with the rest of the persistence 
 adapters.
 Also, should the package kahadaptor be kahaadapter or just plain kaha? :) 
 Assign the jira to me if you're ok with the changes, I don't mind doing the 
 renaming. Thanks! :)

-- 
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-522) get ProxyConnectorTest to work

[Adrian Co (JIRA)]

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

Adrian Co resolved AMQ-522.
---

Fix Version/s: 4.1
   Resolution: Fixed

Tested that this is passing in windows and linux. Although it takes 379 secs to 
complete in linux, while it only takes 9 secs in windows.

 get ProxyConnectorTest to work
 --

 Key: AMQ-522
 URL: https://issues.apache.org/activemq/browse/AMQ-522
 Project: ActiveMQ
  Issue Type: Test
  Components: Test Cases
Affects Versions: 4.0
 Environment: Linux, jdk 1.5
Reporter: Fritz Oconer
 Assigned To: Adrian Co
 Fix For: 4.1


 Running this test case hangs in iago.simulalabs.com. The test log file is 
 empty.

-- 
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: [VOTE] Release Apache ActiveMQ 4.0.2

[Adrian Co]

+1

Regards,
Adrian

Jonas Lim wrote:

+1


Regards,
Jonas
- Original Message - From: Hiram Chirino 
[EMAIL PROTECTED]

To: activemq-dev@geronimo.apache.org
Sent: Wednesday, July 26, 2006 1:26 PM
Subject: [VOTE] Release Apache ActiveMQ 4.0.2


Since it was brought up, and folks concurred that it's about time to 
put out

a bug fix release for ActiveMQ, I've put together a binary release of
ActiveMQ 4.0.2:

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

http://people.apache.org/%7Echirino/incubator-activemq-4.0.1-RC1/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-RC1
http://people.apache.org/%7Echirino/incubator-activemq-4.0.1-RC1/
Here's the wiki page for the release notes (they should soon get 
mirrored to

the activemq static website) :
http://goopen.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0.2+Release
http://goopen.org/confluence/display/ACTIVEMQ/ActiveMQ+4.0.1+Release
Please vote to approve this release binary

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

If this vote passes, then we will then ask the Incubator PMC for their
blessing to ship this release officially.

Here's my +1

--
Regards,
Hiram

Blog: http://hiramchirino.com

Re: Server 2003 Test Results

[Adrian Co]

Could be the space. I'm not sure though. :)

Brian McCallister wrote:

Yum, most of the errors seem to be of the form:

Caused by: java.lang.RuntimeException: java.net.URISyntaxException: 
Illegal character in path at index 18: file:/C:/Documents and 
Settings/administrator/Desktop/incubator-activemq-4.0.1/activemq-core/target/test-classes/org/apache/activemq/openwire/DataFileGeneratorTestSupport.class 



Anyone know what file uri's are supposed to look like on Windows?

-Brian

On Jul 20, 2006, at 2:46 PM, Rodriguez, Adrian wrote:


Here are the results from our test run.  Is there anything else we can
do to help?

thanx =)

adrian /

activemq_test.txt

[jira] Commented: (AMQ-828) add some XML configuration way to force the creation of certain destinations on startup

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-828:
---

ah. missed that one. thanks for the heads up.

 add some XML configuration way to force the creation of certain destinations 
 on startup
 ---

 Key: AMQ-828
 URL: https://issues.apache.org/activemq/browse/AMQ-828
 Project: ActiveMQ
  Issue Type: Improvement
Reporter: james strachan
 Assigned To: james strachan
 Fix For: 4.1


 e.g. have some kind of XML like
 destinations
 queues
   queuefoo.bar/queue
   queuefoo.xyz/queue
 /queues
 topics
   topica.b.c/topic
 /topics
 /destinations

-- 
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] Assigned: (AMQ-820) m2 assembly not working

[Adrian Co (JIRA)]

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

Adrian Co reassigned AMQ-820:
-

Assign To: Fritz Oconer  (was: Adrian Co)

 m2 assembly not working
 ---

  Key: AMQ-820
  URL: https://issues.apache.org/activemq/browse/AMQ-820
  Project: ActiveMQ
 Type: Bug

 Reporter: james strachan
 Assignee: Fritz Oconer
  Fix For: 4.1



 It seems to not include the run.jar and has incorrect versions of things 
 inside (e.g. should be using spring-2.0-rc1).
 Can we get the assembly module such that the can go into the bin directory 
 and run 'activemq' or java -jar run.jar and for things to work properly

-- 
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-820) m2 assembly not working

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-820:
---

Just added a fix to the Main class. Fritz is working on the spring-2.0-rc1 
problem.

 m2 assembly not working
 ---

  Key: AMQ-820
  URL: https://issues.apache.org/activemq/browse/AMQ-820
  Project: ActiveMQ
 Type: Bug

 Reporter: james strachan
 Assignee: Fritz Oconer
  Fix For: 4.1



 It seems to not include the run.jar and has incorrect versions of things 
 inside (e.g. should be using spring-2.0-rc1).
 Can we get the assembly module such that the can go into the bin directory 
 and run 'activemq' or java -jar run.jar and for things to work properly

-- 
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] Work stopped: (AMQ-820) m2 assembly not working

[Adrian Co (JIRA)]

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

Work on AMQ-820 stopped by Adrian Co

 m2 assembly not working
 ---

  Key: AMQ-820
  URL: https://issues.apache.org/activemq/browse/AMQ-820
  Project: ActiveMQ
 Type: Bug

 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 It seems to not include the run.jar and has incorrect versions of things 
 inside (e.g. should be using spring-2.0-rc1).
 Can we get the assembly module such that the can go into the bin directory 
 and run 'activemq' or java -jar run.jar and for things to work properly

-- 
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] Work started: (AMQ-820) m2 assembly not working

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-820?page=all ]
 
Work on AMQ-820 started by Adrian Co

 m2 assembly not working
 ---

  Key: AMQ-820
  URL: https://issues.apache.org/activemq/browse/AMQ-820
  Project: ActiveMQ
 Type: Bug

 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 It seems to not include the run.jar and has incorrect versions of things 
 inside (e.g. should be using spring-2.0-rc1).
 Can we get the assembly module such that the can go into the bin directory 
 and run 'activemq' or java -jar run.jar and for things to work properly

-- 
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-744) add a vmstat agent to the maven activemq performance plugin so we can track the CPU, IO, RAM use on the machine we are running the test on

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-744?page=all ]
 
Adrian Co resolved AMQ-744:
---

Resolution: Fixed

Added summary for blocks received, blocks sent, context switch, user time, 
system time, idle time, wait time.

 add a vmstat agent to the maven activemq performance plugin so we can track 
 the CPU, IO, RAM use on the machine we are running the test on
 

  Key: AMQ-744
  URL: https://issues.apache.org/activemq/browse/AMQ-744
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 When running a performance test it would be good to spawn off a process to 
 run 'vmstat' which works on linux and solaris (the flags may differ etc) 
 which outputs the amout of CPU use in system/user code and how much is idle 
 together with RAM  IO numbers.
 I'd be good to include in each snapshot whatever vmstat numbes we can find so 
 we can see how the box was doing as the test was running.
 e.g.
 sample index=5 ... 
 machine cpuSystem=50 cpuUser=25 cpuIdle=25 ram=44 io=1000/
 /sample
 Note that we may wanna make a few different machine monitoring agents using 
 different tools - so lets make it pluggable - let 'em write whatever XML they 
 can - though we should be able to get linux and solaris done (linux only 
 would be fine for now)
 To call vmstat we'll need to do a System.exec() then parse the results 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] Commented: (AMQ-744) add a vmstat agent to the maven activemq performance plugin so we can track the CPU, IO, RAM use on the machine we are running the test on

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-744:
---

Ive added the vmstat plugin and this is the result it writes:

cpudata index='0' r='1' b='0' w='0' swpd='48952' free='6220' inact='33244' 
active='372324' si='0' so='0' bi='0' bo='0' in='106' cs='42882' us='82' sy='18' 
id='0' /
cpudata index='1' r='0' b='0' w='0' swpd='48960' free='6216' inact='32988' 
active='372328' si='0' so='8' bi='0' bo='8' in='105' cs='36723' us='83' sy='17' 
id='0' /
cpudata index='2' r='1' b='0' w='0' swpd='48960' free='6200' inact='32988' 
active='372328' si='0' so='0' bi='0' bo='0' in='114' cs='36160' us='78' sy='22' 
id='0' /
cpudata index='3' r='0' b='0' w='0' swpd='48968' free='6216' inact='32732' 
active='372328' si='0' so='8' bi='0' bo='8' in='104' cs='42996' us='80' sy='20' 
id='0' /

This is generally straight from the vmstat command line. This is using vmstat 
2.0.11.

Let me know which data is of interest and i can filter it out.

Also, what data should be included in the summary.

 add a vmstat agent to the maven activemq performance plugin so we can track 
 the CPU, IO, RAM use on the machine we are running the test on
 

  Key: AMQ-744
  URL: https://issues.apache.org/activemq/browse/AMQ-744
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 When running a performance test it would be good to spawn off a process to 
 run 'vmstat' which works on linux and solaris (the flags may differ etc) 
 which outputs the amout of CPU use in system/user code and how much is idle 
 together with RAM  IO numbers.
 I'd be good to include in each snapshot whatever vmstat numbes we can find so 
 we can see how the box was doing as the test was running.
 e.g.
 sample index=5 ... 
 machine cpuSystem=50 cpuUser=25 cpuIdle=25 ram=44 io=1000/
 /sample
 Note that we may wanna make a few different machine monitoring agents using 
 different tools - so lets make it pluggable - let 'em write whatever XML they 
 can - though we should be able to get linux and solaris done (linux only 
 would be fine for now)
 To call vmstat we'll need to do a System.exec() then parse the results 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] Commented: (AMQ-745) in message selector does not match messages

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-745:
---

Hi,

I tried to reproduce the issue, but the in selector seems to work using the 
browse command. Im using the default out-of-the-box configuration. 
My test scenario includes:

1. start the default broker
2. run the producer example
3. run browse --amqurl tcp://localhost:61616 TEST.FOO
4. Get a sample message ID
5. run browse --amqurl tcp://localhost:61616 --msgsel 
JMSMessageID='ID:Javacoola-1841-1150366504906-0:0:1:1:8' TEST.FOO
one message is returned
6. run browse --amqurl tcp://localhost:61616 --msgsel JMSMessageID IN 
('ID:Javacoola-1841-1150366504906-0:0:1:1:8') TEST.FOO
one message is returned
7. run browse --amqurl tcp://localhost:61616 --msgsel JMSMessageID in 
('ID:Javacoola-1841-1150366504906-0:0:1:1:8') TEST.FOO
one message is returned

Could you provide more details on your test method?

Maybe the message has been consumed/expired in between run?

Did you run the browse --amqurl tcp://zuul:61616 --msgsel 
JMSMessageID='ID:zuul-45732-1149587838616-3:24:1:1:1' queue:inbound command 
after using IN to check if the message was still there?

Thanks!

Regards,
Adrian Co

 in message selector does not match messages
 ---

  Key: AMQ-745
  URL: https://issues.apache.org/activemq/browse/AMQ-745
  Project: ActiveMQ
 Type: Bug

   Components: Selector
 Versions: 4.0
  Environment: Java 5.0 on Linux
 Reporter: Jeff Martin
 Assignee: Adrian Co



 Using in as part of a message selector does not return any messages.
 Example:
 This returns one message
 browse --amqurl tcp://zuul:61616 --msgsel 
 JMSMessageID='ID:zuul-45732-1149587838616-3:24:1:1:1' queue:inbound
 This returns no messages
 browse --amqurl tcp://zuul:61616 --msgsel JMSMessageID in 
 ('ID:zuul-45732-1149587838616-3:24:1:1:1') queue:inbound

-- 
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] Work stopped: (AMQ-737) for consumers especially but for producers too, it'd be good to do a brief summary on the command line of the throughput

[Adrian Co (JIRA)]

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

Work on AMQ-737 stopped by Adrian Co

 for consumers especially but for producers too, it'd be good to do a brief 
 summary on the command line of the throughput
 

  Key: AMQ-737
  URL: https://issues.apache.org/activemq/browse/AMQ-737
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Versions: 4.0
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 e.g. after running
 mvn activemq-perf:consumer
 it'd be nice to output a little summary something like
 Average throughtput: 1234.45 message/second.
 For average calulation it might be nice to ignore the first couple or the 
 highest  lowest values or something.
 Also for multiple consumers inside the JVM it might be nice to show something 
 like...
 Average throughput : 5000 msg/sec. Average per consumer: 1000 msg/sec, Min 
 consumer: 200 msg/sec, Max consumer: 1400 msg/sec
 so its easy at a glance to get a feel for the results if you are running the 
 tests from a command line

-- 
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-737) for consumers especially but for producers too, it'd be good to do a brief summary on the command line of the throughput

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-737:
---

Added a verbose and xml based report generator. The xml based generator would 
also display a verbose summary at the end. Need to update the MOJOs and run 
some more system testing.

 for consumers especially but for producers too, it'd be good to do a brief 
 summary on the command line of the throughput
 

  Key: AMQ-737
  URL: https://issues.apache.org/activemq/browse/AMQ-737
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Versions: 4.0
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 e.g. after running
 mvn activemq-perf:consumer
 it'd be nice to output a little summary something like
 Average throughtput: 1234.45 message/second.
 For average calulation it might be nice to ignore the first couple or the 
 highest  lowest values or something.
 Also for multiple consumers inside the JVM it might be nice to show something 
 like...
 Average throughput : 5000 msg/sec. Average per consumer: 1000 msg/sec, Min 
 consumer: 200 msg/sec, Max consumer: 1400 msg/sec
 so its easy at a glance to get a feel for the results if you are running the 
 tests from a command line

-- 
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] Work started: (AMQ-702) `bstat --help` should display something useful

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-702?page=all ]
 
Work on AMQ-702 started by Adrian Co

 `bstat --help` should display something useful
 --

  Key: AMQ-702
  URL: https://issues.apache.org/activemq/browse/AMQ-702
  Project: ActiveMQ
 Type: Improvement

 Versions: 4.0 RC3
 Reporter: Jason Dillon
 Assignee: Adrian Co
  Fix For: 4.1, 4.0.1



 `bstat --help` should display something useful.  Right now using a 
 non-standard connectorPort for the managementContext I get this:
 {noformat}
 [EMAIL PROTECTED]:...bator-activemq-4.0-RC3/bin./bstat --help
 ACTIVEMQ_HOME: 
 /Users/jason/ws/paybytouch/ea/activemq/node1/incubator-activemq-4.0-RC3
 ERROR: java.lang.RuntimeException: Failed to execute query task. Reason: 
 java.io.IOException: Failed to retrieve RMIServer stub: 
 javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 ERROR: java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer 
 stub: javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 {noformat}
 `bstat localhost --help` works, showing that this is really calling `query`.  
 Anyways, not very helpful when the JMX URL is changed from the default.

-- 
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-702) `bstat --help` should display something useful

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-702?page=all ]
 
Adrian Co resolved AMQ-702:
---

Resolution: Fixed

Done. Added fix to 4.0.1 and trunk. Sorry, it took a awhile. ;)

 `bstat --help` should display something useful
 --

  Key: AMQ-702
  URL: https://issues.apache.org/activemq/browse/AMQ-702
  Project: ActiveMQ
 Type: Improvement

 Versions: 4.0 RC3
 Reporter: Jason Dillon
 Assignee: Adrian Co
  Fix For: 4.1, 4.0.1



 `bstat --help` should display something useful.  Right now using a 
 non-standard connectorPort for the managementContext I get this:
 {noformat}
 [EMAIL PROTECTED]:...bator-activemq-4.0-RC3/bin./bstat --help
 ACTIVEMQ_HOME: 
 /Users/jason/ws/paybytouch/ea/activemq/node1/incubator-activemq-4.0-RC3
 ERROR: java.lang.RuntimeException: Failed to execute query task. Reason: 
 java.io.IOException: Failed to retrieve RMIServer stub: 
 javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 ERROR: java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer 
 stub: javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 {noformat}
 `bstat localhost --help` works, showing that this is really calling `query`.  
 Anyways, not very helpful when the JMX URL is changed from the default.

-- 
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-702) `bstat --help` should display something useful

[Adrian Co (JIRA)]

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

Adrian Co updated AMQ-702:
--

Attachment: AMQ702.patch

Patch for trunk version attached.

 `bstat --help` should display something useful
 --

  Key: AMQ-702
  URL: https://issues.apache.org/activemq/browse/AMQ-702
  Project: ActiveMQ
 Type: Improvement

 Versions: 4.0 RC3
 Reporter: Jason Dillon
 Assignee: Adrian Co
  Fix For: 4.1, 4.0.1
  Attachments: AMQ702.patch


 `bstat --help` should display something useful.  Right now using a 
 non-standard connectorPort for the managementContext I get this:
 {noformat}
 [EMAIL PROTECTED]:...bator-activemq-4.0-RC3/bin./bstat --help
 ACTIVEMQ_HOME: 
 /Users/jason/ws/paybytouch/ea/activemq/node1/incubator-activemq-4.0-RC3
 ERROR: java.lang.RuntimeException: Failed to execute query task. Reason: 
 java.io.IOException: Failed to retrieve RMIServer stub: 
 javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 ERROR: java.lang.Exception: java.io.IOException: Failed to retrieve RMIServer 
 stub: javax.naming.ServiceUnavailableException [Root exception is 
 java.rmi.ConnectException: Connection refused to host: localhost; nested 
 exception is: 
 java.net.ConnectException: Connection refused]
 {noformat}
 `bstat localhost --help` works, showing that this is really calling `query`.  
 Anyways, not very helpful when the JMX URL is changed from the default.

-- 
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-737) for consumers especially but for producers too, it'd be good to do a brief summary on the command line of the throughput

[Adrian Co (JIRA)]

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

Adrian Co commented on AMQ-737:
---

See the manual for usage.

 for consumers especially but for producers too, it'd be good to do a brief 
 summary on the command line of the throughput
 

  Key: AMQ-737
  URL: https://issues.apache.org/activemq/browse/AMQ-737
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Versions: 4.0
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 e.g. after running
 mvn activemq-perf:consumer
 it'd be nice to output a little summary something like
 Average throughtput: 1234.45 message/second.
 For average calulation it might be nice to ignore the first couple or the 
 highest  lowest values or something.
 Also for multiple consumers inside the JVM it might be nice to show something 
 like...
 Average throughput : 5000 msg/sec. Average per consumer: 1000 msg/sec, Min 
 consumer: 200 msg/sec, Max consumer: 1400 msg/sec
 so its easy at a glance to get a feel for the results if you are running the 
 tests from a command line

-- 
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-737) for consumers especially but for producers too, it'd be good to do a brief summary on the command line of the throughput

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-737?page=all ]
 
Adrian Co resolved AMQ-737:
---

Resolution: Fixed

Done.

 for consumers especially but for producers too, it'd be good to do a brief 
 summary on the command line of the throughput
 

  Key: AMQ-737
  URL: https://issues.apache.org/activemq/browse/AMQ-737
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Versions: 4.0
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 e.g. after running
 mvn activemq-perf:consumer
 it'd be nice to output a little summary something like
 Average throughtput: 1234.45 message/second.
 For average calulation it might be nice to ignore the first couple or the 
 highest  lowest values or something.
 Also for multiple consumers inside the JVM it might be nice to show something 
 like...
 Average throughput : 5000 msg/sec. Average per consumer: 1000 msg/sec, Min 
 consumer: 200 msg/sec, Max consumer: 1400 msg/sec
 so its easy at a glance to get a feel for the results if you are running the 
 tests from a command line

-- 
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] Work started: (AMQ-737) for consumers especially but for producers too, it'd be good to do a brief summary on the command line of the throughput

[Adrian Co (JIRA)]

 [ https://issues.apache.org/activemq/browse/AMQ-737?page=all ]
 
Work on AMQ-737 started by Adrian Co

 for consumers especially but for producers too, it'd be good to do a brief 
 summary on the command line of the throughput
 

  Key: AMQ-737
  URL: https://issues.apache.org/activemq/browse/AMQ-737
  Project: ActiveMQ
 Type: Improvement

   Components: Performance Test
 Versions: 4.0
 Reporter: james strachan
 Assignee: Adrian Co
  Fix For: 4.1



 e.g. after running
 mvn activemq-perf:consumer
 it'd be nice to output a little summary something like
 Average throughtput: 1234.45 message/second.
 For average calulation it might be nice to ignore the first couple or the 
 highest  lowest values or something.
 Also for multiple consumers inside the JVM it might be nice to show something 
 like...
 Average throughput : 5000 msg/sec. Average per consumer: 1000 msg/sec, Min 
 consumer: 200 msg/sec, Max consumer: 1400 msg/sec
 so its easy at a glance to get a feel for the results if you are running the 
 tests from a command line

-- 
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-733) Minor renaming of kaha module

[Adrian Co (JIRA)]

Minor renaming of kaha module
-

 Key: AMQ-733
 URL: https://issues.apache.org/activemq/browse/AMQ-733
 Project: ActiveMQ
Type: Wish

  Components: Message Store  
Versions: 4.0.1
Reporter: Adrian Co
 Assigned to: Rob Davies 
Priority: Trivial


I was wondering if we can rename KahaPersistentAdaptor to 
KahaPersistenceAdapter just to be consistent with the rest of the persistence 
adapters.
Also, should the package kahadaptor be kahaadapter or just plain kaha? :) 
Assign the jira to me if you're ok with the changes, I don't mind doing the 
renaming. Thanks! :)

-- 
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: [VOTE] Release 4.0 of ActiveMQ

[Adrian Co]

+1

Regards,
Adrian Co

Hiram Chirino wrote:


Sorry to have to call this vote again.  While the vote was up at the
incubator, some last minute issues were found.  The readme file did
not properly refer to ActiveMQ as Apache ActiveMQ.

I also took this opportunity to include the fix for 2 major bugs that
would have waited for the 4.1 release:

* https://issues.apache.org/activemq/browse/AMQ-718
* http://issues.apache.org/activemq/browse/AMQ-726

The new binaries are up at:

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



The release notes will show up here as soon as the mirrors catch up...
http://incubator.apache.org/activemq/activemq-40-release.html

if you are impatient, here's the wiki page for the release notes:
http://incubator.apache.org/activemq/activemq-40-release.html

Please vote to approve this release binary

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

If this vote passes, then we will then ask the Incubator PMC for their
blessing to ship this release officially.

Here's my +1