Re: Switching to ActiveMQ 4.2 to Java 5???
Hiram Chirino wrote: On 11/15/06, Endre Stølsvik [EMAIL PROTECTED] wrote: 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. Rather big move for a minor version - why not call it ActiveMQ 5 instead (It'll even align!). lol.. good point. But I'd hate to have big increases without big functionality changes especially if the clients are still compatible with the 4.x stuff. It is a rather big _requirement_ change, though? (And you'll probably introduce some internal changes, and you'll remove a large pile of code (the down-port of concurrent), and .. so on.. going from Java 1.4 to 1.5.) IMHO, the story ActiveMQ 5 only works on java 1.5 (5), while ActiveMQ 4 is the older version that works on java 1.4 (and java 1.5) would be rather simple to tell, as opposed to exchanging those two versions with 4.2 and 4.1. Particularly since I'll bet that you'll have a rather long maintenance story going with the java 1.4 branch afterwards - so this won't be a small nice little dot-change, as such. Don't be too afraid of changing major-versions - other companies routinely go much further than one-uping: from 1.4 to 5.0 (:-)), and 2.6 to 7 (Solaris), and 3.11 to 95, 4.0 to 2000, 2000 to 'XP' (!), 4 to 6 (Netscape) and so on!! ;-) Tomcat peculiarly went from 5.0 to 5.5 on its java 1.4-1.5 dependency change (which I believe they somewhat regret - that story is rather difficult to get across without eh, say again?!s). Then keep ActiveMQ 4.x on 1.4. Regards, Endre.
Re: Switching to ActiveMQ 4.2 to Java 5???
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. Rather big move for a minor version - why not call it ActiveMQ 5 instead (It'll even align!). Then keep ActiveMQ 4.x on 1.4. Regards, Endre.
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
[I intially sent with wrong From: - sorry if double-posting] Guillaume Nodet wrote: I think the problem comes from the fact that the xsds are not generated in their default locations (target/xbean). Changing the configuration to: schematarget/xbean/activemq.xsd/schema should work. At that point they'll magically jump into some good place in the jar, being acessible in the classpath, and the spring.schemas will contain the right info? What about the actual, physical URL I mentioned? Shouldn't the xsd also actually be accessible from some nice-looking URL somewhere @ apache.com? And finally, I wonder why spring's own spring.schema fila have /actual/ URLs as reference? Spring's spring.schema file have lines like this: http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd See, given that spring's namespace-definitions look like this: http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd; While ActiveMQ's look like this: http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; One would deduce that the URL which is matched in the spring.schemas are the _latter_, not the _former_ of these URLS. PS: Just to do a fast check, I ripped the network cable out of my machine, and tried to start my application with current snapshot (where ActiveMQ is configured as suggested on http://incubator.apache.org/activemq/spring-support.html). This was the result (with full stop as result): This is fine: - 563 [main] DEBUG org.springframework.beans.factory.xml.ResourceEntityResolver - Attempting to resolve XML Schema [http://www.springframework.org/schema/aop/spring-aop-2.0.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver] This isn't: -- 578 [main] DEBUG org.springframework.beans.factory.xml.ResourceEntityResolver - Attempting to resolve XML Schema [http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd] using [org.springframework.beans.factory.xml.PluggableSchemaResolver] 766 [main] WARN org.springframework.beans.factory.xml.XmlBeanDefinitionReader - Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not xsd:schema. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) [snip - any element using amq wouldn't parse after this, obviously..] I then inserted it again, restart, and it went fine. Kind regards, Endre
Re: [VOTE] Release Apache ActiveMQ 4.1.0 (RC 2)
Hiram Chirino 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 useless -1: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/temp/META-INF$ cat spring.schemas http\://activemq.org/config/1.0=file:/Users/chirino/sandbox/activemq-4.1/activemq-core/target/activemq.xsd Two things: a) where is the xsd supposed to lay? (The _proper_ URL? Not this one mentioned on this page: http://incubator.apache.org/activemq/spring-support.html http://activemq.org/config/1.0 http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd; b) The idea behind spring.schemas is, AFAIK, that the spring-magic should kick in, and instead of going online to fetch the xsd, it will find it in the classpath. Given that the file:/Users/chirino/blahblah most definately isn't present on my machine, this will, AFAIK, result in every startup of ActiveMQ with spring-xbeans integration online access (which probably explains why all elements of the namespace-loading goes lightning, except from the activeMQ one, which stalls for some seconds). In comparison, here's the spring.schemas for spring-2.0.jar actually bundled with this ActiveMQ 4.1.0 RC2: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/META-INF$ cat spring.schemas http\://www.springframework.org/schema/beans/spring-beans-2.0.xsd=org/springframework/beans/factory/xml/spring-beans-2.0.xsd http\://www.springframework.org/schema/util/spring-util-2.0.xsd=org/springframework/beans/factory/xml/spring-util-2.0.xsd Note two things: the http-URL mentioned actually return the file, but in addition, the resource specified is a classpath-resource, which exists: [EMAIL PROTECTED]:~/temp/apache-activemq-4.1.0-incubator/lib/optional/temp/org/springframework/beans/factory/xml$ ls -la spring-* -rw-r--r-- 1 endre endre 23940 2006-09-13 23:57 spring-beans-2.0.dtd -rw-r--r-- 1 endre endre 39944 2006-09-13 23:57 spring-beans-2.0.xsd -rw-r--r-- 1 endre endre 21767 2006-08-19 19:00 spring-beans.dtd -rw-r--r-- 1 endre endre 1999 2006-09-09 23:53 spring-tool-2.0.xsd -rw-r--r-- 1 endre endre 5132 2006-09-09 23:53 spring-util-2.0.xsd This is bug AMQ-1016: https://issues.apache.org/activemq/browse/AMQ-1016 I think this should be fixed before 4.1.0 is released. Kind regards, Endre.
Re: Thread pool strategy
On Wed, 14 Jul 2004, Geir Magnusson Jr wrote: | | On Jul 13, 2004, at 5:39 PM, toby cabot wrote: | | On Tue, Jul 13, 2004 at 03:33:35PM -0400, Geir Magnusson Jr wrote: | Is it really now as in if you don't have to wait for a thread, do | it | - otherwise return w/ a status indicating now wasn't possible or now | as in wait until there's a thread, do it, and then return to me? | | three choices: | |doWork() - block until it's done |startWork() - block until it starts and then return |scheduleWork() - return now and do the work whenever. | | http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/work/ | WorkManager.html | | Thx. needs one more : | | doWorkNow() startHardWork() doWorkSmarter() doSmartWork() scheduleWorkLater() weekendNow() Endre.sleep()
