Will there be any issue if I use activemq 4.x connector to connect ActiveMQ 5.x server ?
Hello, A geronimo 2.1.x user wants to use embed activemq 4.x connector/adapter to connect ActiveMQ 5.x broker. Can anyone give some hints about if there's any compatibility risk doing so ? -- Shawn
Re: Will there be any issue if I use activemq 4.x connector to connect ActiveMQ 5.x server ?
Thank you, Gary ! It's not that hard to upgrade the client, I'll update the client to match the broker version. In summary, If you update the broker, you also need to update the clients; or at least consider it! On Tue, Jul 31, 2012 at 6:07 PM, Gary Tully gary.tu...@gmail.com wrote: I wrote some detail on this a while back http://blog.garytully.com/2010/08/reminder-jms-is-client-server.html If you must mix versions, the bottom line is you will have to 'ask the computer' On 31 July 2012 08:22, Shawn Jiang genspr...@gmail.com wrote: Hello, A geronimo 2.1.x user wants to use embed activemq 4.x connector/adapter to connect ActiveMQ 5.x broker. Can anyone give some hints about if there's any compatibility risk doing so ? -- Shawn -- http://fusesource.com http://blog.garytully.com -- Shawn
Activemq does not support customized message listener ?
In EJB31 spec: 5.4.2 The Required Message Listener Interface. It said that
MDB should support customized message listener. Now I'm trying to enable
MDB custom listener in geronimo. But I find hard
coded javax.jms.MessageListener in ActiveMQ code, it make it impossible to
add the support for geronimo/openejb without updating code in activemq
side.Thoughts ?
1,
org.apache.activemq.ra.MessageEndpointProxy.MessageEndpointProxy(MessageEndpoint)
public MessageEndpointProxy(MessageEndpoint endpoint) {
if (!(endpoint instanceof MessageListener)) {
throw new IllegalArgumentException(MessageEndpoint is not a
MessageListener);
}
messageListener = endpoint;
proxyID = getID();
this.endpoint = endpoint;
}
2, org.apache.activemq.ra.ActiveMQEndpointWorker
public class ActiveMQEndpointWorker {
...
static {
try {
ON_MESSAGE_METHOD = MessageListener.class.getMethod(onMessage,
new Class[] {
Message.class
});
...
}
--
Shawn
Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn
Re: Failed to resolve artifact: xmlpull:xmlpull:jar:1.1.3.4d_b4_min
Thanks, I'll use the older version to build. On Tue, Oct 26, 2010 at 4:47 PM, Dejan Bosanac de...@nighttale.net wrote: Hi, this is fixed on the trunk, so instead of xmlpull we now use xpp3 version 1.1.4c. If you need to build the older version, you can use a bit older version 1.1.3.4a of xmlpull, just change xmlpull-version in pom.xml Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Oct 26, 2010 at 10:40 AM, Shawn Jiang genspr...@gmail.com wrote: I found that a xmlpull dependency is missing from central repo. Does anyone know how to report this kind of issues ? * [INFO] * * [ERROR] BUILD ERROR* * [INFO] * * [INFO] Failed to resolve artifact.* * * * Missing:* * --* * 1) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * Try downloading the file manually from the project website.* * * * Then, install it using the command: * * mvn install:install-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file* * * * Alternatively, if you host your own repository you can deploy the file there: * * mvn deploy:deploy-file -DgroupId=xmlpull -DartifactId=xmlpull -Dversion=1.1.3.4d_b4_min -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]* * * * Path to dependency: * * 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * 2) org.apache.activemq:activemq-web:jar:5.4.1* * 3) xmlpull:xmlpull:jar:1.1.3.4d_b4_min* * * * --* * 1 required artifact is missing.* * * * for artifact: * * org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2.1-SNAPSHOT* * * * from the specified remote repositories:* * central (http://repo1.maven.org/maven2),* * codehaus.snapshots (http://snapshots.repository.codehaus.org),* * apache.snapshots (http://repository.apache.org/snapshots),* -- Shawn -- Shawn
Re: [VOTE] Apache ActiveMQ 5.4.1
+1 Geronimo 22 branch TCK 100% passed with this staging release. On Mon, Sep 20, 2010 at 10:27 PM, Shawn Jiang genspr...@gmail.com wrote: TCK with Geronimo based on this staging activemq is still running. I will update the result here when it's completed. On Sat, Sep 18, 2010 at 9:56 PM, Hadrian Zbarcea hzbar...@gmail.comwrote: A maintenance release activemq-5.4.1 is out with approximately 49 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/ The binary distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/org/apache/activemq/activemq-all/5.4.1/ The source distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/org/apache/activemq/activemq-parent/5.4.1/ The repository tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.1/ The list of resolved issues is here: https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520styleName=Htmlversion=12332 Please review and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache ActiveMQ 5.4.1 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian -- Shawn -- Shawn
Re: [VOTE] Apache ActiveMQ 5.4.1
TCK with Geronimo based on this staging activemq is still running. I will update the result here when it's completed. On Sat, Sep 18, 2010 at 9:56 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: A maintenance release activemq-5.4.1 is out with approximately 49 issues resolved. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/ The binary distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/org/apache/activemq/activemq-all/5.4.1/ The source distribution is here: https://repository.apache.org/content/repositories/orgapacheactivemq-041/org/apache/activemq/activemq-parent/5.4.1/ The repository tag is here: https://svn.apache.org/repos/asf/activemq/tags/activemq-5.4.1/ The list of resolved issues is here: https://issues.apache.org/activemq/secure/ReleaseNote.jspa?projectId=10520styleName=Htmlversion=12332 Please review and vote to approve this release binary. Your vote counts! [ ] +1 Release the binary as Apache ActiveMQ 5.4.1 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian -- Shawn
[jira] Commented: (AMQ-2840) JMSX Properties not returned from message.propertyExists() and message.getPropertyNames()
[ https://issues.apache.org/activemq/browse/AMQ-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61304#action_61304 ] Shawn Jiang commented on AMQ-2840: -- Gary, #987193 bring the same TCK Failures.Could you revert them ? JMSX Properties not returned from message.propertyExists() and message.getPropertyNames() - Key: AMQ-2840 URL: https://issues.apache.org/activemq/browse/AMQ-2840 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.0 Reporter: Andriy Hnativ Assignee: Gary Tully Fix For: 5.4.1 Attachments: patch.txt Methods propertyExists() and getPropertyNames() defined in the class org.apache.activemq.command.ActiveMQMessage (activemq-core) return only custom properties. The JMSX properties (like JMSXDeliveryCount) are not being returned. This problem exists not only for a new version of ActiveMQ (5.4), but also for 5.3 (and probably for others as well). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2840) JMSX Properties not returned from message.propertyExists() and message.getPropertyNames()
[ https://issues.apache.org/activemq/browse/AMQ-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61291#action_61291 ] Shawn Jiang commented on AMQ-2840: -- I found that the version of trunk is 5.5-SNAPSHOT.Are you planing to release a 5.4.1 to fix this ? In my opinion, a 5.4.1 with fix should be released ASAP because the user's JMS code based on the wrong implementation will not be portable. JMSX Properties not returned from message.propertyExists() and message.getPropertyNames() - Key: AMQ-2840 URL: https://issues.apache.org/activemq/browse/AMQ-2840 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.0 Reporter: Andriy Hnativ Assignee: Gary Tully Fix For: 5.4.1 Attachments: patch.txt Methods propertyExists() and getPropertyNames() defined in the class org.apache.activemq.command.ActiveMQMessage (activemq-core) return only custom properties. The JMSX properties (like JMSXDeliveryCount) are not being returned. This problem exists not only for a new version of ActiveMQ (5.4), but also for 5.3 (and probably for others as well). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-2840) JMSX Properties not returned from message.propertyExists() and message.getPropertyNames()
[ https://issues.apache.org/activemq/browse/AMQ-2840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=61273#action_61273 ] Shawn Jiang commented on AMQ-2840: -- Hi, this patch broke the jms spec: --- /**Returns an Enumeration of all the property names. ** Note that *JMS standard header fields are not considered properties and are not returned in this enumeration*. **/ Enumeration getPropertyNames() throws JMSException So that this change is preventing the tck from passing.Could you please fix this ? JMSX Properties not returned from message.propertyExists() and message.getPropertyNames() - Key: AMQ-2840 URL: https://issues.apache.org/activemq/browse/AMQ-2840 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.4.0 Reporter: Andriy Hnativ Assignee: Gary Tully Fix For: 5.4.0 Attachments: patch.txt Methods propertyExists() and getPropertyNames() defined in the class org.apache.activemq.command.ActiveMQMessage (activemq-core) return only custom properties. The JMSX properties (like JMSXDeliveryCount) are not being returned. This problem exists not only for a new version of ActiveMQ (5.4), but also for 5.3 (and probably for others as well). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2094) Can't bind the connector to localhost or actuall IP correctly.
[
https://issues.apache.org/activemq/browse/AMQ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated AMQ-2094:
-
Attachment: AMQ-2094.patch
Please help review the patch, thanks.
Can't bind the connector to localhost or actuall IP correctly.
--
Key: AMQ-2094
URL: https://issues.apache.org/activemq/browse/AMQ-2094
Project: ActiveMQ
Issue Type: Bug
Components: Geronimo Integration
Affects Versions: 4.1.2, 5.2.0
Environment: Windows XP + SUN JDK 1.5
Reporter: Shawn Jiang
Attachments: AMQ-2094.patch
ActiveMQ server socket created with TcpTransportServer can't bind to
localhost or actuall IP correctly.
* expected result:
** localhost --- bind to 127.0.0.1
** actual IP bind to actual IP
* actual result:
** localhost --- bind to 0.0.0.0
** actual IP bind to 0.0.0.0
{code:title=org.apache.activemq.transport.tcp.TcpTransportServer}
InetAddress addr = InetAddress.getByName(host);
try {
if (host.trim().equals(localhost) || \
addr.equals(InetAddress.getLocalHost())) { //#1 start the socket with 0.0.0.0
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog); }
else {
//#2 start the socket with the ip spcified in addr.
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog, addr); }
{code}
Since if you config the real IP as a host setting, \
addr.equals(InetAddress.getLocalHost()) will allways be true so that the #1
will be used to start the socket with 0.0.0.0 by default. Which causes a
defect of geronimo: https://issues.apache.org/jira/browse/GERONIMO-4404
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2094) Can't bind the connector to localhost or actuall IP correctly.
[
https://issues.apache.org/activemq/browse/AMQ-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated AMQ-2094:
-
Patch Info: [Patch Available]
Can't bind the connector to localhost or actuall IP correctly.
--
Key: AMQ-2094
URL: https://issues.apache.org/activemq/browse/AMQ-2094
Project: ActiveMQ
Issue Type: Bug
Components: Geronimo Integration
Affects Versions: 4.1.2, 5.2.0
Environment: Windows XP + SUN JDK 1.5
Reporter: Shawn Jiang
Attachments: AMQ-2094.patch
ActiveMQ server socket created with TcpTransportServer can't bind to
localhost or actuall IP correctly.
* expected result:
** localhost --- bind to 127.0.0.1
** actual IP bind to actual IP
* actual result:
** localhost --- bind to 0.0.0.0
** actual IP bind to 0.0.0.0
{code:title=org.apache.activemq.transport.tcp.TcpTransportServer}
InetAddress addr = InetAddress.getByName(host);
try {
if (host.trim().equals(localhost) || \
addr.equals(InetAddress.getLocalHost())) { //#1 start the socket with 0.0.0.0
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog); }
else {
//#2 start the socket with the ip spcified in addr.
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog, addr); }
{code}
Since if you config the real IP as a host setting, \
addr.equals(InetAddress.getLocalHost()) will allways be true so that the #1
will be used to start the socket with 0.0.0.0 by default. Which causes a
defect of geronimo: https://issues.apache.org/jira/browse/GERONIMO-4404
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (AMQ-2094) Can't bind the connector to localhost or actuall IP correctly.
Can't bind the connector to localhost or actuall IP correctly.
--
Key: AMQ-2094
URL: https://issues.apache.org/activemq/browse/AMQ-2094
Project: ActiveMQ
Issue Type: Bug
Components: Geronimo Integration
Affects Versions: 5.2.0, 4.1.2
Environment: Windows XP + SUN JDK 1.5
Reporter: Shawn Jiang
ActiveMQ server socket created with TcpTransportServer can't bind to localhost
or actuall IP correctly.
* expected result:
** localhost --- bind to 127.0.0.1
** actual IP bind to actual IP
* actual result:
** localhost --- bind to 0.0.0.0
** actual IP bind to 0.0.0.0
{code:title=org.apache.activemq.transport.tcp.TcpTransportServer}
InetAddress addr = InetAddress.getByName(host);
try {
if (host.trim().equals(localhost) || \
addr.equals(InetAddress.getLocalHost())) { //#1 start the socket with 0.0.0.0
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog); }
else {
//#2 start the socket with the ip spcified in addr.
this.serverSocket = \
serverSocketFactory.createServerSocket(bind.getPort(), backlog, addr); }
{code}
Since if you config the real IP as a host setting, \
addr.equals(InetAddress.getLocalHost()) will allways be true so that the #1
will be used to start the socket with 0.0.0.0 by default. Which causes a
defect of geronimo: https://issues.apache.org/jira/browse/GERONIMO-4404
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
