You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2007/03/19 22:50:32 UTC
[jira] Created: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Weed out backport-util-concurrent usage for server/trunk
--------------------------------------------------------
Key: GERONIMO-2995
URL: https://issues.apache.org/jira/browse/GERONIMO-2995
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Affects Versions: 2.0
Reporter: Jason Dillon
Assigned To: Jason Dillon
Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482350 ]
Jason Dillon commented on GERONIMO-2995:
----------------------------------------
It _may_ be unrelated... I can't tell at the moment.
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482516 ]
Jason Dillon commented on GERONIMO-2995:
----------------------------------------
Ah, looks like AMQ isn't happy with backport 3.0, so we *have* to use 2.2.
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484177 ]
David Jencks commented on GERONIMO-2995:
----------------------------------------
Note that if you want to run amq in an app client you need to add the backport- jar dependency to your client jms plan, since we don't run the activemq-broker in the client. (of course you could, and if you did you could get the backport classes from it).
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0-M5
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 2.0-M4
>
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482348 ]
Jason Dillon commented on GERONIMO-2995:
----------------------------------------
There may be an issue with AMQ, TCK is puking up a bunch of things like:
{noformat}
Exception in thread "ActiveMQ Transport: tcp:///127.0.0.1:56746" java.lang.ClassCastException: org.apache.activemq.transport.InactivityMonitor$1
at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.compareTo(ScheduledThreadPoolExecutor.java:189)
at edu.emory.mathcs.backport.java.util.PriorityQueue.remove(PriorityQueue.java:507)
at edu.emory.mathcs.backport.java.util.concurrent.DelayQueue.remove(DelayQueue.java:379)
at edu.emory.mathcs.backport.java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.remove(ScheduledThreadPoolExecutor.java:707)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.remove(ThreadPoolExecutor.java:1582)
at org.apache.activemq.thread.Scheduler.cancel(Scheduler.java:55)
at org.apache.activemq.transport.InactivityMonitor.stopMonitorThreads(InactivityMonitor.java:176)
at org.apache.activemq.transport.InactivityMonitor.onException(InactivityMonitor.java:149)
at org.apache.activemq.transport.TransportSupport.onException(TransportSupport.java:97)
at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:150)
at java.lang.Thread.run(Thread.java:613)
{noformat}
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482346 ]
Jason Dillon commented on GERONIMO-2995:
----------------------------------------
This is *mostly* done... we still need to include backport for rmi-naming and client configs, mostly due to {{org.apache.geronimo.gjndi.GlobalContextGBean}} I believe, though I'm not sure where that comes from so I can't update it at the moment.
2 non-import/pom changes were needed due to minor incompatibilities:
ConcurrentHashMap(int initialCapacity, float loadFactor) does not exist, using ConcurrentHashMap(int initialCapacity) since we were using the default loadFactory of {{0.75f}} anyways.
TimeUnit.MINUTES does not exist... use TimeUnit.SECONDS and multiply timed value by 60 to get minutes.
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Closed: (GERONIMO-2995) Weed out backport-util-concurrent usage for server/trunk
Posted by Jason Dillon <ja...@planet57.com>.
No, I don't expect they will, nor do I think they should. 4.1.x
still runs on JDK 1.4. This dep will be dropped in AMQ 5.0. So G
2.0 will still need to keep this dep in the repo for JMS muck (which
I am okay with).
--jason
On Mar 30, 2007, at 1:02 PM, Donald Woods wrote:
> Do we have a commitment from ActiveMQ to remove its backport-util-
> concurrent usage in a 4.1 release for our 2.0 release?
>
> -Donald
>
> Jason Dillon (JIRA) wrote:
>> [ https://issues.apache.org/jira/browse/GERONIMO-2995?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>> Jason Dillon closed GERONIMO-2995.
>> ----------------------------------
>> Resolution: Fixed
>> Fix Version/s: 2.0-beta1
>> This is done, once AMQ removes dependency on this... then we can
>> get it out of the repository.
>>> Weed out backport-util-concurrent usage for server/trunk
>>> --------------------------------------------------------
>>>
>>> Key: GERONIMO-2995
>>> URL: https://issues.apache.org/jira/browse/
>>> GERONIMO-2995
>>> Project: Geronimo
>>> Issue Type: Improvement
>>> Security Level: public(Regular issues) Affects Versions: 2.0
>>> Reporter: Jason Dillon
>>> Assigned To: Jason Dillon
>>> Fix For: 2.0-beta1
>>>
>>>
>>> Now that server/trunk requires 1.5 to build and run, I think we
>>> should start to weed out our usage of the {{backport-util-
>>> concurrent}} library (and concurrent if there is still anything
>>> left of that in our src tree).
>>> I think we may still have to include {{backport-util-concurrent-
>>> \*.jar}} in the assembly until all of our dependencies have
>>> weeded it out too... or perhaps just have to live with that in
>>> the repository. But hopefully we can remove our usage of these
>>> classes and not need to include this puppy in {{lib/\*}} anymore.
>>> Looks like we are currently using {{edu.emory.mathcs.backport}}
>>> in 39 locations (based on imports) which are over 25 files.
>>> Even after weeding out *our* usage, if we still need to include
>>> this jar I recommend we update to the latest release 3.0.
Re: [jira] Closed: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by Donald Woods <dr...@yahoo.com>.
Do we have a commitment from ActiveMQ to remove its
backport-util-concurrent usage in a 4.1 release for our 2.0 release?
-Donald
Jason Dillon (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jason Dillon closed GERONIMO-2995.
> ----------------------------------
>
> Resolution: Fixed
> Fix Version/s: 2.0-beta1
>
> This is done, once AMQ removes dependency on this... then we can get it out of the repository.
>
>> Weed out backport-util-concurrent usage for server/trunk
>> --------------------------------------------------------
>>
>> Key: GERONIMO-2995
>> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
>> Project: Geronimo
>> Issue Type: Improvement
>> Security Level: public(Regular issues)
>> Affects Versions: 2.0
>> Reporter: Jason Dillon
>> Assigned To: Jason Dillon
>> Fix For: 2.0-beta1
>>
>>
>> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
>> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
>> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
>> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
>
[jira] Closed: (GERONIMO-2995) Weed out backport-util-concurrent
usage for server/trunk
Posted by "Jason Dillon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon closed GERONIMO-2995.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta1
This is done, once AMQ removes dependency on this... then we can get it out of the repository.
> Weed out backport-util-concurrent usage for server/trunk
> --------------------------------------------------------
>
> Key: GERONIMO-2995
> URL: https://issues.apache.org/jira/browse/GERONIMO-2995
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 2.0-beta1
>
>
> Now that server/trunk requires 1.5 to build and run, I think we should start to weed out our usage of the {{backport-util-concurrent}} library (and concurrent if there is still anything left of that in our src tree).
> I think we may still have to include {{backport-util-concurrent-\*.jar}} in the assembly until all of our dependencies have weeded it out too... or perhaps just have to live with that in the repository. But hopefully we can remove our usage of these classes and not need to include this puppy in {{lib/\*}} anymore.
> Looks like we are currently using {{edu.emory.mathcs.backport}} in 39 locations (based on imports) which are over 25 files.
> Even after weeding out *our* usage, if we still need to include this jar I recommend we update to the latest release 3.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.