You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/10/04 18:03:44 UTC
[jira] Created: (GERONIMO-4337) Upgrade to activeMQ 5.x
Upgrade to activeMQ 5.x
-----------------------
Key: GERONIMO-4337
URL: https://issues.apache.org/jira/browse/GERONIMO-4337
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 2.2
Reporter: David Jencks
Fix For: 2.2
Upgrade activemq support to 5.x. A few steps along the way:
- create an activemq5 work area under plugins
- move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
- keep only the broker gbean
- use an activemq configuration file in var/activemq, referenced by the broker gbean
- update dependencies to latest activemq
- figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
- investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "John Charles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639736#action_12639736 ]
John Charles commented on GERONIMO-4337:
----------------------------------------
David,
I signed the icla and posted it from Australia.
I followed your instructions and downloaded everything including all the activemq5 plugin modules. I firstly built geronimo from scratch. That worked fine. I then duplicated the local playpen in preparation for ActiveMQ5.* inclusion.
I modified the following files under plugins on the local installation to ensure they validated and performed a car:verify-no-dependency-change just to make sure things were structurally ok.
- plugins\activemq5\pom.xml
- plugins\activemq5\activemq5-broker
- plugins\activemq5\activemq5-console-jetty
- plugins\activemq5\activemq5-console-tomcat
- plugins\activemq5\activemq5-ra
- plugins\activemq5\geronimo-activemq5
- plugins\activemq5\geronimo-activemq5-management
- plugins\activemq5\geronimo-activemq5-ra
I also bumped up the activemq-core, activemq-ra references to 5.1.0 and the activeio-core to 3.1.0 as reflected in the ActiveMQ5.1 project. I can forward changes made to the pom files.
In addition to this I setup placeholder 2.2-SNAPSHOT version entries in my local .m2\repository :
- .m2\repository\org\apache\geronimo\configs\activemq5-broker
- .m2\repository\org\apache\geronimo\configs\activemq5-ra
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5-management
- .m2\repository\org\apache\geronimo\modules\geronimo-activemq5-ra
- .m2\repository\org\apache\geronimo\plugins\activemq5
- .m2\repository\org\apache\geronimo\plugins\activemq5-console-jetty
- .m2\repository\org\apache\geronimo\plugins\activemq5-console-tomcat
- .m2\repository\org\apache\geronimo\plugins\activemq5-portlets
I changed all version references to reflect ActiveMQ5.1 references for activemq-core, activemq-ra and activeio-core namely 5.1.0, 5.1.0 and 3.1.0 respectively.
All good so far!! The next step involved systematically building (mvn install) on each of the activemq5 plugin entries in the initial list.
The activemq5-broker built successfully however when I ran mvn install on the activemq5-console-jetty entry I got the following problem:
[ERROR] The protocol for the JAR file's URL is not supported
java.lang.UnsupportedOperationException: Only local file jars are supported jar:file:/C:/Documents and Settings/admin/.m2/repository/org/apache/geronimo/configs/activemq-ra/2.2-SNAPSHOT/activemq-ra-2.2-SNAPSHOT.car!/rar/activemq-ra-4.1.2.jar
org.apache.geronimo.kernel.classloader.UrlResourceFinder.cacheUrl(UrlResourceFinder.java:231)
org.apache.geronimo.kernel.classloader.UrlResourceFinder.rebuildClassPath(UrlResourceFinder.java:188)
org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:142)
org.apache.geronimo.kernel.classloader.UrlResourceFinder.addUrls(UrlResourceFinder.java:127)
org.apache.geronimo.kernel.classloader.JarFileClassLoader$2.run(JarFileClassLoader.java:159)
It looks like there was some discussion about issue from Jaceb Laskowski back in June 13 in relation to changes made in GERONIMO-4093.
What was interesting was the activemq5-broker reported a similar problem but the build succeeded.
My goal at this stage is to incorporate a version of ActiveMQ5.* into Geronimo and then I can wade into the other areas requiring modification. I find it easier to wade into this step by step given the overwhelming verbosity of maven output.
Let me know if I am on track and any insights on the above problem would be appreciated. I have kept all build log files and can forward if required.
Cheers,
John Charles
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636838#action_12636838 ]
David Jencks commented on GERONIMO-4337:
----------------------------------------
by rev 701669 I have the activemq5 plugin building ok. It still uses amg4, I guess the next step would be to update the version and start removing gbeans that won't work with amq5.
The main build needs some more changes too, I will get to them later.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-4337.
----------------------------------
Resolution: Fixed
I think this is stable enough so we can use individual jira entries for any remaining problems.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "John Charles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640083#action_12640083 ]
John Charles commented on GERONIMO-4337:
----------------------------------------
David,
The icla was sent snail mail and will take up to a week.
I am no Maven expert so I was just exploring under the hood. However I am
studying how it hangs together because I would like to use it on other
projects. I have checked out the latest changes as per Donald Woods updates
with updated pom files under activemq5 and will rebuild and test. I nuked
the local cache activemq5* repository mods; they get built anyway.
I will rebuild and see how the ActiveMQ 5.1.0 references go.
John C.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "John Charles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640084#action_12640084 ]
John Charles commented on GERONIMO-4337:
----------------------------------------
David,
Thanks for the update. I have checked out the latest release and will
rebuild with our changes to see how it goes.
Cheers,
John C.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by Donald Woods <dw...@apache.org>.
BTW - activeio is still listed as a dependency in the
activemq-core-5.1.0 pom.xml file and the activeio pom still lists
backport-util-concurrent as a dependency....
-Donald
David Jencks (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639741#action_12639741 ]
>
> David Jencks commented on GERONIMO-4337:
> ----------------------------------------
>
> Hi John,
>
> I'll keep my eyes out for the icla to arrive.
>
> I thought that activemq 5 did not use activeio at all.
> I don't understand what you mean by creating placeholders in .m2/repository. Maven will create any directories it needs when it needs them.
> You should try to build from plugins/activemq5 and let maven figure out the order to build the modules in. Before updating the activemq versions I see:
>
> [INFO] Geronimo Plugins, ActiveMQ 5
> [INFO] Geronimo Plugins, ActiveMQ5 :: Management Interfaces
> [INFO] Geronimo Plugins, ActiveMQ5 :: Core
> [INFO] Geronimo Plugins, ActiveMQ5 :: Broker
> [INFO] Geronimo Plugins, ActiveMQ5 :: Resource Adapter Core
> [INFO] Geronimo Plugins, ActiveMQ5 :: Resource Adapter
> [INFO] Geronimo Plugins, ActiveMQ5 :: Portlets
> [INFO] Geronimo Plugins, ActiveMQ5 :: Console (Jetty)
> [INFO] Geronimo Plugins, ActiveMQ5 :: Console (Tomcat)
>
> The error you get appears to refer to org.apache.geronimo.configs:activemq-ra and activemq-ra-4.1.2 which seems to indicate that some pom versions have not been updated to the proper values for activemq 5 or geronimo activemq5. If it is not clear how to proceed please attach a patch from svn diff and I will investigate.
>
> I would be surprised if the ActiveMQ5 Core module compiled successfully.
>
>> Upgrade to activeMQ 5.x
>> -----------------------
>>
>> Key: GERONIMO-4337
>> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
>> Project: Geronimo
>> Issue Type: Improvement
>> Security Level: public(Regular issues)
>> Components: ActiveMQ
>> Affects Versions: 2.2
>> Reporter: David Jencks
>> Fix For: 2.2
>>
>>
>> Upgrade activemq support to 5.x. A few steps along the way:
>> - create an activemq5 work area under plugins
>> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
>> - keep only the broker gbean
>> - use an activemq configuration file in var/activemq, referenced by the broker gbean
>> - update dependencies to latest activemq
>> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
>> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
>
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639741#action_12639741 ]
David Jencks commented on GERONIMO-4337:
----------------------------------------
Hi John,
I'll keep my eyes out for the icla to arrive.
I thought that activemq 5 did not use activeio at all.
I don't understand what you mean by creating placeholders in .m2/repository. Maven will create any directories it needs when it needs them.
You should try to build from plugins/activemq5 and let maven figure out the order to build the modules in. Before updating the activemq versions I see:
[INFO] Geronimo Plugins, ActiveMQ 5
[INFO] Geronimo Plugins, ActiveMQ5 :: Management Interfaces
[INFO] Geronimo Plugins, ActiveMQ5 :: Core
[INFO] Geronimo Plugins, ActiveMQ5 :: Broker
[INFO] Geronimo Plugins, ActiveMQ5 :: Resource Adapter Core
[INFO] Geronimo Plugins, ActiveMQ5 :: Resource Adapter
[INFO] Geronimo Plugins, ActiveMQ5 :: Portlets
[INFO] Geronimo Plugins, ActiveMQ5 :: Console (Jetty)
[INFO] Geronimo Plugins, ActiveMQ5 :: Console (Tomcat)
The error you get appears to refer to org.apache.geronimo.configs:activemq-ra and activemq-ra-4.1.2 which seems to indicate that some pom versions have not been updated to the proper values for activemq 5 or geronimo activemq5. If it is not clear how to proceed please attach a patch from svn diff and I will investigate.
I would be surprised if the ActiveMQ5 Core module compiled successfully.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642597#action_12642597 ]
David Jencks commented on GERONIMO-4337:
----------------------------------------
Sorry for the delay.
I dont think your svn.diff patch does anything useful at this point. The versions for the activemq and activeio jars are already specified in the plugins/activemq5/pom.xml in the <dependenciesManagement> element, and at least for me building plugins/activemq5 fails on the geronimo-activemq5-core module due to incompatible changes between activemq 4 and 5. We can't change the rest of the build to use activem5 until it actually works. I think the next step would be to propose some changes to the gbean classes so they compile against activemq 5.1.0. Let me know if I've missed some of your patches.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-4337:
--------------------------------------
Assignee: David Jencks
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "John Charles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Charles updated GERONIMO-4337:
-----------------------------------
Attachment: plugins.svn.diff.zip
I got some time last week to look at the compilation issue. I have attached
pom file changes and changes to the activemq5-broker GBean class files to
get the activemq5-broker service running in Geronimo. I tested the
deployment of the activemq5-broker module in a geronimo-tomcat assembly and
it fired up ok. I also tested it against a simple jms client using the
SendRecieveQueue and it worked.
The activemq4-ra module compiles but complains about needing a GBeanInfo
reference for MDBTransferBeanOutQueue and SendReceiveQueue mentioned in the
plan. I ran out of time to explore this further but commenting these
adminobjects out isolated that they were causing the module to fail on
startup. Perhaps you can point me in the right direction here.
John C.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639840#action_12639840 ]
Donald Woods commented on GERONIMO-4337:
----------------------------------------
John, I just made a small update to the activemq5/pom.xml in Rev704910 to upgrade to the AMQ 5.1.0 artifacts and to keep the console modules from building. Feel free to start creating patches and attaching them to this JIRA and we'll get them applied ASAP, so you can keep making progress. Thanks!
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656644#action_12656644 ]
Jarek Gawor commented on GERONIMO-4337:
---------------------------------------
Btw, I've noticed that with the new activemq plugin a "activemq-data" directory is created under the current working directory instead somewhere underneath the <server instance>/var/ directory.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654652#action_12654652 ]
David Jencks commented on GERONIMO-4337:
----------------------------------------
Bruce Snyder got enthusiastic about this at apachecon and we got some basic code working to get the broker started.
rev 724558 introduces amq5 as the normal amq and gets the console working with reduced functionality. I don't think we'll be able to provide amq plan editing very soon.
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, plugins.svn.diff.zip, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4337) Upgrade to activeMQ 5.x
Posted by "John Charles (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Charles updated GERONIMO-4337:
-----------------------------------
Attachment: geronimo-plugins.xml
svn.diff
I have built the activemq5 plugin. I made some changes to various pom.xml files as reflected in the attachment.
The next step is to incorporate ActiveMQ5 references in the various geronimo assemblies. I assume this is done via a maven repository hosting the geronimo-plugins.xml file located at http://gerornimo.apache.org/plugins/geronimo-{version}. I attached my guess at the reference changes required using a new version number of 2.2.1-SNAPSHOT.
Let me know if I am on the right track. If so, I guess I would need to wait until the online assembly configuration file geronimo-plugins.xml is ready.
John Charles
> Upgrade to activeMQ 5.x
> -----------------------
>
> Key: GERONIMO-4337
> URL: https://issues.apache.org/jira/browse/GERONIMO-4337
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: ActiveMQ
> Affects Versions: 2.2
> Reporter: David Jencks
> Fix For: 2.2
>
> Attachments: geronimo-plugins.xml, svn.diff
>
>
> Upgrade activemq support to 5.x. A few steps along the way:
> - create an activemq5 work area under plugins
> - move the specification of amq version from the root pom dependency management to the activemq and activemq5 plugins.
> - keep only the broker gbean
> - use an activemq configuration file in var/activemq, referenced by the broker gbean
> - update dependencies to latest activemq
> - figure out how much of the current jms portlet functionality can be reasonably kept. From discussions with Hiram I think that trying to reconfigure the broker while its running is a very bad idea and we should just drop the parts of the console that try to do this.
> - investigate how to run the amq console in geronimo, preferably as portlets inside the g. admin console.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.