[jira] Updated: (AMQ-739) STOMP transport handles JMS type improperly
[ https://issues.apache.org/activemq/browse/AMQ-739?page=all ] james strachan updated AMQ-739: --- Version: 4.0.1 4.0 STOMP transport handles JMS type improperly --- Key: AMQ-739 URL: https://issues.apache.org/activemq/browse/AMQ-739 Project: ActiveMQ Type: Bug Components: Transport Versions: 4.0.1, 4.0 Environment: sending from STOMP to JMS Reporter: Nathan Mittler Assignee: Nathan Mittler Priority: Minor Fix For: 4.1 Original Estimate: 1 week Remaining: 1 week Sending a text message from a stomp client with a content-length results in a bytes message on JMS. Suggest doing the following ... 1) The stomp transport should always add the content-length header to out-going messages, regardless of content-type or whether or not a content-length was provided on the incoming message. 2) The stomp transport should handle in-coming messages with a content-type header, and should pass that through. 3) If a message comes in without a content-length or a content-type, it should just be assumed a TextMessage. This way we can use the terminating null character as the delimiter. -- 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-739) STOMP transport handles JMS type improperly
[ https://issues.apache.org/activemq/browse/AMQ-739?page=comments#action_36437 ] Nathan Mittler commented on AMQ-739: clients can use bytes and text messages so long as they follow AMQ's scheme for making the distinction: if content-length is specified, it's a bytes message, otherwise it's text. So I don't think any action needs to be taken on this issue other than updating AMQ's stomp page to make it clear how to make the distinction between bytes and text using the stomp protocol. STOMP transport handles JMS type improperly --- Key: AMQ-739 URL: https://issues.apache.org/activemq/browse/AMQ-739 Project: ActiveMQ Type: Bug Components: Transport Versions: 4.0.1, 4.0 Environment: sending from STOMP to JMS Reporter: Nathan Mittler Assignee: Nathan Mittler Priority: Minor Fix For: 4.1 Original Estimate: 1 week Remaining: 1 week Sending a text message from a stomp client with a content-length results in a bytes message on JMS. Suggest doing the following ... 1) The stomp transport should always add the content-length header to out-going messages, regardless of content-type or whether or not a content-length was provided on the incoming message. 2) The stomp transport should handle in-coming messages with a content-type header, and should pass that through. 3) If a message comes in without a content-length or a content-type, it should just be assumed a TextMessage. This way we can use the terminating null character as the delimiter. -- 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.1
+1 On 6/17/06, Hiram Chirino [EMAIL PROTECTED] wrote: Since the 4.0 release a bunch of small bug have been fixed and we felt it better to release early and often, so here are the release binarys for the 4.0.1 version of activemq: http://people.apache.org/~chirino/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.1-RC1/ The release notes will show up here as soon as the mirrors catch up... http://incubator.apache.org/activemq/activemq-401-release.html if you are impatient, here's the wiki page for the release notes: 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.1 [ ] -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
[jira] Assigned: (AMQ-663) JMX management info about subscriptions is incomplete
[ https://issues.apache.org/activemq/browse/AMQ-663?page=all ] james strachan reassigned AMQ-663: -- Assign To: james strachan JMX management info about subscriptions is incomplete - Key: AMQ-663 URL: https://issues.apache.org/activemq/browse/AMQ-663 Project: ActiveMQ Type: Improvement Versions: 4.0 RC2 Reporter: Bruce Mitchener Assignee: james strachan Fix For: 4.1 When I'm viewing my current subscriptions via jconsole, the info about them is incomplete and doesn't mention (at least) whether they are durable or retroactive. There are probably other properties missing? -- 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-764) Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0)
Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0) - Key: AMQ-764 URL: https://issues.apache.org/activemq/browse/AMQ-764 Project: ActiveMQ Type: Bug Components: JCA Container Versions: 4.0 RC3 Environment: REDHAT 3.0 JBoss 4.04-GA ActiveMQ-4.0-RC2 Reporter: shahzad bhatti Fix For: 4.0.2 Attachments: activemq_jboss.zip I am testing ActiveMQ 4.0 with JBoss 4.0 where I am using ActiveMQ's .rar file within JBoss. I have a test applicacation that consists of following components: -Message driven bean listens to queue within JBoss. It receives message and invokes stateless session bean, which invokes entity bean and the message is added to the databsae (mysql). After adding message, it replies back the response to the client. -JBoss stateless session bean -- uses entity bean to add message to the database -JBoss entity bean that uses CMP to add message to the database. -Publisher client - uses ActiveMQ APIs to publish message to the queue and listens for response I find that after about 2200 messages, I get OutOfMemory exception in ActiveMQ and my application hangs. I am also attaching source code minus jar files. You will also need mysql database. -- 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-RESULT] Release Apache ActiveMQ 4.0.1
I am wondered why activemq release named incubator-activemq4.x? why add a prefix incubator ? Is it not a production? -- I love Java! I love Sports! I love this Game ! QQ:33093778 MSN:[EMAIL PROTECTED] home:http://www.jsports.org blog:http://blog.csdn.net/jsports http://blog.matrix.org.cn/page/jsports --
AMQP
FYI: http://www.infoq.com/news/amq AMQP looks to be an attempt at wire protocol specification like openwire or stomp. Probably good for us to look at, though the licensing probably needs to bounce through [EMAIL PROTECTED] before we do much as it is not immediately clear if it is okay. I probably is, but I'd love to get Cliff's opinion. -Brian
Re: [VOTE-RESULT] Release Apache ActiveMQ 4.0.1
Its is prefixed with incubator because the project's *community* is being incubated as an _Apache community_. The software is indeed production level. I'd imagine that soonish that the community will be promoted to a top-level project and the incubator prefix will be done away with. But that is up to the project management and board to decided. --jason On Jun 20, 2006, at 7:17 PM, -=Kobye=- wrote: I am wondered why activemq release named incubator-activemq4.x? why add a prefix incubator ? Is it not a production? -- I love Java! I love Sports! I love this Game ! QQ:33093778 MSN:[EMAIL PROTECTED] home:http://www.jsports.org blog:http://blog.csdn.net/jsports http://blog.matrix.org.cn/page/jsports --
[jira] Commented: (AMQ-764) Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0)
[ https://issues.apache.org/activemq/browse/AMQ-764?page=comments#action_36447 ] james strachan commented on AMQ-764: Can you try using 4.0.1 please and see if you can reproduce? http://incubator.apache.org/activemq/activemq-401-release.html Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0) - Key: AMQ-764 URL: https://issues.apache.org/activemq/browse/AMQ-764 Project: ActiveMQ Type: Bug Components: JCA Container Versions: 4.0 RC3 Environment: REDHAT 3.0 JBoss 4.04-GA ActiveMQ-4.0-RC2 Reporter: shahzad bhatti Fix For: 4.0.2 Attachments: activemq_jboss.zip I am testing ActiveMQ 4.0 with JBoss 4.0 where I am using ActiveMQ's .rar file within JBoss. I have a test applicacation that consists of following components: -Message driven bean listens to queue within JBoss. It receives message and invokes stateless session bean, which invokes entity bean and the message is added to the databsae (mysql). After adding message, it replies back the response to the client. -JBoss stateless session bean -- uses entity bean to add message to the database -JBoss entity bean that uses CMP to add message to the database. -Publisher client - uses ActiveMQ APIs to publish message to the queue and listens for response I find that after about 2200 messages, I get OutOfMemory exception in ActiveMQ and my application hangs. I am also attaching source code minus jar files. You will also need mysql database. -- 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
ServiceMix-3.0-M2-incubating
I have uploaded binaries for the 3.0-M2-incubating release. The repos and site are available at http://people.apache.org/~gnodet/servicemix-3.0-M2-incubating Binary distribution can be directly accessed at http://people.apache.org/~gnodet/servicemix-3.0-M2-incubating/m2/org/apache/servicemix/apache-servicemix/3.0-M2-incubating/apache-servicemix-3.0-M2-incubating.tar.gz http://people.apache.org/~gnodet/servicemix-3.0-M2-incubating/m2/org/apache/servicemix/apache-servicemix/3.0-M2-incubating/apache-servicemix-3.0-M2-incubating.zip Please, take some time to download and test the main configuration, components and examples (I have changed quite a few things these last days, so ...), and post your feedback (and votes for PPMC members). Cheers, Guillaume Nodet
[jira] Resolved: (SM-463) Possible NPE when using jmx and passing null arguments
[ https://issues.apache.org/activemq/browse/SM-463?page=all ] Guillaume Nodet resolved SM-463: Fix Version: 3.0 Resolution: Fixed Assign To: Guillaume Nodet Author: gnodet Date: Tue Jun 20 14:08:33 2006 New Revision: 415805 URL: http://svn.apache.org/viewvc?rev=415805view=rev Log: SM-463: Possible NPE when using jmx and passing null arguments Modified: incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/BaseStandardMBean.java Possible NPE when using jmx and passing null arguments -- Key: SM-463 URL: https://issues.apache.org/activemq/browse/SM-463 Project: ServiceMix Type: Bug Components: servicemix-core Versions: 3.0-M2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.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] Resolved: (SM-464) Fix ant tasks to be fully jbi compliant
[ https://issues.apache.org/activemq/browse/SM-464?page=all ] Guillaume Nodet resolved SM-464: Fix Version: 3.0 Resolution: Fixed Assign To: Guillaume Nodet Author: gnodet Date: Tue Jun 20 14:11:42 2006 New Revision: 415807 URL: http://svn.apache.org/viewvc?rev=415807view=rev Log: SM-464: Fix ant tasks to be fully jbi compliant Modified: incubator/servicemix/trunk/apache-servicemix/src/main/release/ant/servicemix-ant-task.xml incubator/servicemix/trunk/apache-servicemix/src/main/release/ant/servicemix_ant_taskdef.properties incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/InstallComponentTask.java incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/JbiTask.java incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/ListBindingComponentsTask.java incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/ListServiceAssembliesTask.java incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/ListServiceEnginesTask.java incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/management/task/ListSharedLibrariesTask.java Fix ant tasks to be fully jbi compliant --- Key: SM-464 URL: https://issues.apache.org/activemq/browse/SM-464 Project: ServiceMix Type: Bug Components: servicemix-assembly, servicemix-core Versions: 3.0-M2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.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
ApacheCon EU
Who's going to ApacheCon EU? Is there going to be a hackathon? Regards, Alan
[jira] Updated: (SM-393) ServiceMix 3.0-M1 RC doesn't like spaces in the path on Windows
[ https://issues.apache.org/activemq/browse/SM-393?page=all ] Guillaume Nodet updated SM-393: --- Fix Version: 3.0 (was: 3.0-M2) ServiceMix 3.0-M1 RC doesn't like spaces in the path on Windows --- Key: SM-393 URL: https://issues.apache.org/activemq/browse/SM-393 Project: ServiceMix Type: Bug Components: servicemix-assembly Versions: 3.0-M1 Reporter: Dan Diephouse Assignee: Guillaume Nodet Fix For: 3.0 The servicemix 3.0 M1 RC doesn't seem to want to run on cygwin (and probably dos too) with spaces in the path. It does work fine if I move it out of a folder that has spaces into the root c: drive though. [EMAIL PROTECTED] /workspace/servicemix-3.0-M1/examples/basic $ ../../bin/servicemix.bat servicemix.xml Exception in thread main java.lang.NoClassDefFoundError: and [EMAIL PROTECTED] /cygdrive/c/servicemix-3.0-M1/examples/basic $ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System3 2/Wbem:/cygdrive/c/Program Files/ATI Technologies/ATI Control Panel:/cygdrive/c/Program Files/MySQL/MySQL Server 4.1/bin :%MAVEN_HOME%/bin:/cygdrive/c/Program Files/Microsoft SQL Server/90/Tools/binn/:/cygdrive/c/Program Files/Microsoft Comm and Shell/v1.0/:/cygdrive/c/Program Files/Microsoft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Program Files/Microsoft Visual Studio/Common/MSDev98/Bin:/cygdrive/c/Program Files/Microsoft Visual Studio/Common/Tools:/cygdrive/c/Program Fil es/Microsoft Visual Studio/VC98/bin:/cygdrive/c/Program Files/Java/jdk1.5.0_06/bin:/cygdrive/c/apache-ant-1.6.3/bin:/cyg drive/c/Program Files/Apache Software Foundation/Maven 1.1-beta-2/bin:/cygdrive/c/maven-2.0.2/bin [EMAIL PROTECTED] /workspace/servicemix-3.0-M1/examples/basic $ ../../bin/servicemix servicemix.xml ../../bin/servicemix: line 133: /cygdrive/c/Program: No such file or directory JVM vendor is SUN /cygdrive/c/Program Files/Java/jdk1.5.0_06/bin/java -server -Xms128M -Xmx512M -Dderby.system.home=/workspace/servicemix- 3.0-M1/var -Dderby.storage.fileSyncTransactionLog=true -classpath .\;c:\Documents and Settings\Dan\workspace\servicemix- 3.0-M1\conf;c:\Documents and Settings\Dan\workspace\servicemix-3.0-M1\lib\classworlds-1.0.1.jar -Dclassworlds.conf=c:\Do cuments and Settings\Dan\workspace\servicemix-3.0-M1\conf\servicemix.conf -Dservicemix.home=c:\Documents and Settings\Da n\workspace\servicemix-3.0-M1 -Dcygwin.user.home=C:\cygwin\home\Dan -Djava.endorsed.dirs=c:\Documents and Settings\Dan\w orkspace\servicemix-3.0-M1/lib/endorsed org.codehaus.classworlds.Launcher servicemix.xml ../../bin/servicemix: line 268: /cygdrive/c/Program: No such file or directory ../../bin/servicemix: line 268: exec: /cygdrive/c/Program: cannot execute: No such file or 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] Updated: (SM-408) Migrate common JAXP/StAX code to stax-utils
[ https://issues.apache.org/activemq/browse/SM-408?page=all ] Guillaume Nodet updated SM-408: --- Fix Version: 3.0 (was: 3.0-M2) Migrate common JAXP/StAX code to stax-utils --- Key: SM-408 URL: https://issues.apache.org/activemq/browse/SM-408 Project: ServiceMix Type: Task Reporter: Dan Diephouse Fix For: 3.0 The org.apache.servicemix.jbi.jaxp code is quite common (for instance some of the classes are from XFire). We should move the package to the stax-utils project to share common 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] Updated: (SM-394) Create XFire example
[ https://issues.apache.org/activemq/browse/SM-394?page=all ] Guillaume Nodet updated SM-394: --- Fix Version: 3.0 (was: 3.0-M2) Create XFire example Key: SM-394 URL: https://issues.apache.org/activemq/browse/SM-394 Project: ServiceMix Type: Task Components: servicemix-components Reporter: Dan Diephouse Priority: Minor Fix For: 3.0 We should have a more comprehensive xfire example which shows how to use things like ws-security and existing xfire services with servicemix. -- 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: (SM-438) DefaultServiceMixClient.stop() doesn't stop JBI Container
[ https://issues.apache.org/activemq/browse/SM-438?page=all ] Guillaume Nodet updated SM-438: --- Fix Version: 3.0 (was: 3.0-M2) DefaultServiceMixClient.stop() doesn't stop JBI Container - Key: SM-438 URL: https://issues.apache.org/activemq/browse/SM-438 Project: ServiceMix Type: Bug Components: servicemix-core Environment: jdk 1.5 winXP eclipse 3.1 Reporter: GODOT Philippe Assignee: Guillaume Nodet Fix For: 3.0 Method DefaultServiceMixClient.stop() doesn't stop JBI container. some ActiveMQ thread are blocked status. If you stop the JBI Agent, in the log you have: 09:57:45,201 DEBUG [AbstractConnection] Transport failed: java.net.SocketException: Connection reset [0.0.1:3633] (org.apache.activemq.broker.AbstractConnection.Transport:166) java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:48) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:55) at java.io.DataInputStream.readInt(DataInputStream.java:353) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:270) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:138) at java.lang.Thread.run(Thread.java:595) 09:57:45,201 INFO [DemandForwardingBridgeSupport] Network connection between vm://peer-chdsk-pgodot-3631-1148457416186-1-0#2 and tcp://localhost/127.0.0.1:3620 shutdown: Connection reset [0.0.1:3620] (org.apache.activemq.network.DemandForwardingBridge:264) java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:48) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.read(TcpBufferedInputStream.java:55) at java.io.DataInputStream.readInt(DataInputStream.java:353) at org.apache.activemq.openwire.OpenWireFormat.unmarshal(OpenWireFormat.java:270) at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:138) at java.lang.Thread.run(Thread.java:595) This exception wakeup the threads and everything stop. -- 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-452) Classpath issues with lwcontainer
[ https://issues.apache.org/activemq/browse/SM-452?page=all ] Guillaume Nodet resolved SM-452: Fix Version: 3.0-M2 Resolution: Fixed Assign To: Guillaume Nodet I have removed servicemix-components from the lwcontainer, so that one will need to : * deploy it in the SU (and put dependencies along) * put it in the lib/optional folder with the needed dependencies It seems there is still one problem with activemq-core which is in the container classloader, but may miss some dependencies (for example using org.apache.activemq.pool.*). I think i will improve xbean to support child first class loading delegation along with exclusions, and it should be better. Classpath issues with lwcontainer - Key: SM-452 URL: https://issues.apache.org/activemq/browse/SM-452 Project: ServiceMix Type: Bug Components: servicemix-lwcontainer Versions: 3.0 Environment: Java 5 Reporter: Doug Fischer Assignee: Guillaume Nodet Fix For: 3.0-M2 The problem is that the smack jars are loaded from the classloader which contains the jabber component, which is the lwconatiner classloader, and not from the SU classloader. It seems this is a design problem of the lwcontainer. I will remove the servicemix-components jar from the lwcontainer, thus you will have to deploy it inside your service unit, but the problem should be fixed. In the mean time, you should be able to copy/paste the jabber component, rename it, and bundle it inside your SU with the jar dependencies. -- 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-457) Classloader for XBean deployment should support child delegation and class exclusions
Classloader for XBean deployment should support child delegation and class exclusions - Key: SM-457 URL: https://issues.apache.org/activemq/browse/SM-457 Project: ServiceMix Type: New Feature Components: servicemix-common Versions: 3.0-M2 Reporter: Guillaume Nodet Fix For: 3.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] Commented: (SM-457) Classloader for XBean deployment should support child delegation and class exclusions
[ https://issues.apache.org/activemq/browse/SM-457?page=comments#action_36434 ] Guillaume Nodet commented on SM-457: Depends on http://issues.apache.org/jira/browse/XBEAN-19 Classloader for XBean deployment should support child delegation and class exclusions - Key: SM-457 URL: https://issues.apache.org/activemq/browse/SM-457 Project: ServiceMix Type: New Feature Components: servicemix-common Versions: 3.0-M2 Reporter: Guillaume Nodet Fix For: 3.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
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
+1 David Blevins wrote: +1 On Jun 19, 2006, at 8:33 AM, Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear
[jira] Created: (AMQ-762) Message Group based load balancing not well distributed across brokers
Message Group based load balancing not well distributed across brokers -- Key: AMQ-762 URL: https://issues.apache.org/activemq/browse/AMQ-762 Project: ActiveMQ Type: Bug Versions: 4.0 Environment: Active MQ 4.0, Lingo 1.1 Reporter: Sanjiv Jivan Attachments: lingocluster.zip I started 2 servers, each of which have an embedded broker. A shell based chield sends messages to 30 different message groups (using command register message group in the samepl app provided. Only 2 mesages are received by server1, 3 by server2 and 25 by server3. The load balancing distribution is highly unenen. As suggested, I also tried setting a low destination queue prefetch value (consumer.prefetch=1) but the result was the same. To run sample : 1. Unzip attached file and run maven.bat from the oot directory (Maven 1.0) 2. Open 3 DOS boxes in the dist\bin folder and run startoptimizerPooled.bat, startOptimizerPooled2.bat and startOptimizerPooled3.bat in each DOS box respectively. 3. Step 2 starts a network of 3 servers apps which have an embedded broker. The Spring configuration files for each of these servers is in the dist\conf directory. 4. Open another DOS box in dist\bin and start a test client by running startClientShell.bat 5. This command driver test client accepts commads in the form register message group close message group and exit NOTE: The command close message group is supposed to close/reset the message group by issueing a JMSXGroupSeq header as described here : http://www.activemq.org/site/message-groups.html 6. Try sending several messages to the server by issuing several commands like regeister A, register B, register C and so on.. You'll see the highly uneven distibution of messages. Only one or two messages are received my 2 servers while the third one receives a majority of the messages. Please let me know if you have trouble running the sample or replicating the issue. Thanks, Sanjiv -- 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-763) closing of Message Groups not working
closing of Message Groups not working - Key: AMQ-763 URL: https://issues.apache.org/activemq/browse/AMQ-763 Project: ActiveMQ Type: Bug Components: Broker Versions: 4.0 Environment: Active MQ 4.0, XP, Lingo 1.1 Reporter: Sanjiv Jivan I'm trying to close/reset a message group as described here : http://www.activemq.org/site/message-groups.html but this does not seem to be working. To reproduce, use the sample app provided in issue : http://issues.apache.org/activemq/browse/AMQ-762 and follow the instructions provided there. Issue the command close message group on a previously sent message group (via register message group). This is supposed to reset the message group affinity to the brokers but on issuing a register message group for the message group just closed you'll notice that the server affinity still exists and this call always goes to the server/broer that was previosly chosen. -- 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] Closed: (AMQ-760) many issue with network of brokers
[ https://issues.apache.org/activemq/browse/AMQ-760?page=all ] Sanjiv Jivan closed AMQ-760: Resolution: Duplicate Created separate and more specific issues AMQ-762 and AMQ-763 many issue with network of brokers -- Key: AMQ-760 URL: https://issues.apache.org/activemq/browse/AMQ-760 Project: ActiveMQ Type: Bug Components: Broker Versions: 4.0 Environment: XP, Active MQ 4.0, Lingo 1.1 Reporter: Sanjiv Jivan Attachments: lingocluster.zip I'm having a real rough time getting Active MQ 4.0 to work property when deployed as a network of brokers using Message Groups. The behaviour even without Message Groups seems highly unstable. I don't even know where to start but I'll give it a shot. Basically every time I try to carry out any manual test, like start two brokers, start client and send message, stop one server, start client etc.. I see a misbehaviour. I've seen things like a single message group being sent to two different servers, the client hanging, servers not responding ... etc Build the uploaded sample and give it play around with it and you'll see what I mean. 1. Open two DOS boxes and run two servers by calling startoptimizerPooled.bat from dist\bin. First, if brokerName is specified in the configuration, it fails when running on JDK 1.4 with a noclassdef error on a jmx class JMXServiceURL. When using JDK 1.5 and specifying a brokerName, the client hangs when a call is made to the server. 2. Start a client by calling startclient.bat foobar from dist\bin. Here foobar translated to the Message Group ID. Terminate the client midway, and restart it. Repeat and you'll see that the foobar message group is received by both servers. 3. Open a third dos box and start another client and send messages as described in step 2, and you'll notice strange behavior again. 4. When running a network of broker, after a broker is started and has received a message, when another broker is started, an exception is raised immediately. Try this by opening another DOS box and running startoptimizerPooled.bat. 5. Now try starting a broker on a different machine and repeat above test. Different errors like the ones described in issue https://issues.apache.org/activemq/browse/AMQ-696 start showing up. Too many things don't seem to be working but hopefully once these issues get sorted out, I'll be able to attain Lingo nirvana. -- 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: Request change to RTC Process
ROFLMAO :) See my comments on chimerical (excellent...excellent) Agree with your other statements. Hiram Chirino wrote: On 6/19/06, Matt Hogstrom [EMAIL PROTECTED] wrote: I'm not sure Ken's intent was to introduce a new concept as much as he was pointing out a side benefit. My understanding was that RTC was enforce to improve community collaboration and communication. Clearly its not working very well based on the comments in this thread. Seems to be going the opposite way. Clearly the opinion of some on the thread is they trust each other and communication has already been fine so this is just slowing them down? Is that the summary? I'd have to disagree that things have been fine although I'll concede that perhaps some changes to RTC may be warranted. I'm sitting in an airport right now so I don't have time to do this but it might be nice if someone can compile some statistics on what has actually transpired and then we can discuss why this isn't working and then make some recommendations as to how to move forward rather than the current dialogue which doesn't seem to be improving collaboration and communication but is actually driving polarization (which I think we're trying to avoid). Hiram Chirino wrote: On 6/17/06, Rodent of Unusual Size [EMAIL PROTECTED] wrote: RTC means tested quality, not assumed quality. If you can't find people to test the quality of something, it doesn't go in because the quality isn't assured. I'm not sure where 'quality' requirement is coming from. I don't think it's ever been discussed on the list. For example, I don't remember a discussion of should we focus on stabilizing and in effect slowing down the development of Geronimo. Or should it focus on implementing the J2EE features that it's missing as quickly as possible? I can see how IBM would prefer the 1st option since it would allow it's chimerical offerings to stay differentiated from Geronimo. But I don't think the rest of this community would agree. I'm having trouble understanding the above paragraph and Dain's comments in another e-mail. I proposed that we take 1.1.1 to stabilize it because there are a number of quality issues in Geronimo that make it undesireable in a production enviroment. NPEs abound and we have usability problems. Personally I think these need to be addressed to improve the adoption rate of Geronimo. I'm not aware of a lot of developers or administrators that accept a server that is 90% reliable (my made up number). If you disagree that fixing these are a waste of time then please speak up. I have other things to do then. I think that's great! and I hope a 1.1.2 rolls out soon too and that the 1.1 branch keeps stabilizing at a good pace. I'm also having difficulty understanding the chimerical comment. I can only assume that you mean that WAS CE is some mythical and unachievable goal? Here is where I'm drawing my inference from: http://dictionary.reference.com/wordoftheday/archive/2003/02/24.html Here is a quote from the above: 1. Merely imaginary; produced by or as if by a wildly fanciful imagination; fantastic; improbable or unrealistic. If WAS CE is mythical then I'm not sure what hope there is for Geronimo because it is the basis for WAS CE. If CE can't succeed then I'd say Geronimo poisoned the apple. Can you please clarify your comments Hiram because they aren't making sense to me. I'm sure you don't mean the above. lol.. that's why you can't trust spell checkers! replace chimerical with commercial! I was more referring to WAS compared to WASCE and it staying highly differentiated because RTC could stifle geronimo's innovation. Ok this is awesome :-0 I was wondering if you meant commercial but it was such a perfect fit at chimerical you had me guessing :) - Eliminates trust. I know say, David J has a lot of experience with say, connectors, and if he puts a patch in that area, I think I can read his summary and trust that he's implemented it sensibly. But now that doesn't count, I have to review it line by line? I think it should be up to me which patches I trust and which patches want to review in detail. Considering the problems concerning trust that are already extant, I think the first sentence as a conclusion is bogus. And once again you want to *assume* quality rather than *assure* it. That's how CTR works. RTC works to *assure* it. I trust a bunch of the folks that work here and while I could review patches, unless you are working with that code ALL the time, there could be unexpected side-effects that only folks working on it all the time could catch. So I would rather than assume I know what I'm doing, I'd delegate to folks who specialize in that area of Geronimo. By way of example, if its connector or Tx code I'd trust Jencks. Perhaps the problem is that Geronimo has not attracted enough people to have more than one person interested in a specific
Re: Request change to RTC Process
Ok, I understand the issue. To be honest I took a look at Hiram's RTC request. The time to take and apply the patches and test them was a bit onerous given the other things I was working on. I think Ken's switch from CTR to RTC was to promote communication as well as improve knowledge (I really do think his comment on quality was a side benefit and not the driving force) of other areas. I think Greg Stein had also indicated that perhaps a review (and not a token +1) was fair. I think that would be a place to perhaps move to and if Ken perceives were back in a ditch then he can tighten it back up. I agree that communication is much better since the RTC. Thanks to DBlevins for whacking me in his response to this. It seemed that this thread was going the wrong way but perhaps I mis read it. Cheers. Dain Sundstrom wrote: On Jun 19, 2006, at 4:28 PM, Matt Hogstrom wrote: Clearly the opinion of some on the thread is they trust each other and communication has already been fine so this is just slowing them down? Is that the summary? I'd have to disagree that things have been fine although I'll concede that perhaps some changes to RTC may be warranted. I think that the model of reviewing is working and I like it. What I don't like is the requirement to physically apply every patch and run a full build. I feel that a careful read of the patch is good enough for trunk and tends to spur collaboration and communication that was the original intent of switching to RTC. For micro releases, I taking a more conservative approach may be warranted, but I honestly don't see how applying a patch and building it is going to find more error. For example, the NPEs you pointed out are likely to only be found by testing user applications, and when we do find one a test case should be added to prevent regressions. -dain
Re: ApacheCon EU
I'll be arriving on Monday some time. Alan D. Cabrera wrote: Who's going to ApacheCon EU? Is there going to be a hackathon? Regards, Alan
[jira] Created: (SM-459) NPE upon missing in message
NPE upon missing in message --- Key: SM-459 URL: https://issues.apache.org/activemq/browse/SM-459 Project: ServiceMix Type: Bug Components: servicemix-http Versions: 3.0-M2 Environment: Windows 2000, JBoss-4.0.3SP1 Reporter: Andreas Held Priority: Trivial I created a component with an InOut exchange and forgot to add the in message. This yielded the following exception: java.lang.NullPointerException at org.apache.servicemix.soap.marshalers.JBIMarshaler.fromNMS(JBIMarshaler.java:76) A slightly more meaningful exception could be helpful. -- 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: [Fwd: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote]
+1 G1.1 +1 specs +1 daytrader On Jun 19, 2006, at 2:21 PM, Matt Hogstrom wrote: I originally sent this note about 3 hours ago. Not sure where the bottleneck is so I'm trying again. Apologies if there are duplicates. Original Message Subject: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote Date: Mon, 19 Jun 2006 11:33:31 -0400 From: Matt Hogstrom [EMAIL PROTECTED] To: dev@geronimo.apache.org, [EMAIL PROTECTED], user@geronimo.apache.org Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE- NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1- final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1- final-2_src.zip *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty- j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty- j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty- minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty- minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat- j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat- j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat- minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat- minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/ org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/ org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/ org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/ org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/ daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/ daytrader_src-1.1-final-2.zip *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader- ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear -sachin
[jira] Commented: (GERONIMODEVTOOLS-85) Plugin does not recognize started Geronimo 1.1 Final-2
[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-85?page=comments#action_12416894 ] Sachin Patel commented on GERONIMODEVTOOLS-85: -- Yes I think your assesment may be correct. I'm waiting for the jars to be 1.1 jars to be published so I can create a new distribution that updates that packaged jars. Plugin does not recognize started Geronimo 1.1 Final-2 -- Key: GERONIMODEVTOOLS-85 URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-85 Project: Geronimo-Devtools Type: Bug Components: eclipse-plugin Environment: Windows, Callisto RC4a. Reporter: Neal Sanche Priority: Critical I downloaded the Geronimo 1.1 final release which has the final directory structure layout, the 1.1-SNAPSHOT is now simply 1.1 everywhere in the geronimo-1.1/repository directory. I defined a new 'Server' using the wizard, and pointed it at my newly unzipped geronimo-1.1 tree. When I try to 'start' the server using the right-click menu, the plugin begins the start of the server as usual, this seems to work. Problem is that the plugin does not recognize that the server is actually started. I suspect that it may be using 1.1-SNAPSHOT somewhere to recognize when the server has started, or something similar, but that is only a hunch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Where did the 1.1 branch go?!?! - Summary and recommendation
On 6/19/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Tony, The 1.1 branch is close and not accepting updates. It is currently located at branches/1.1.0 and will me moved to tags/1.1.0 when the final approval vote goes through. branches/1.1.1 is ready for updates but we haven't agreed on the content yet. See.. I don't understand why we have 1.1.1 branch out yet. I would think all work targeted at 1.1.1 should be done in the 1.1 branch and WHEN the release manager feels it is time to do a release he copies it over tot he 1.1.1 branch and starts his release work. I think I'm in agreement with you that it should be branches/1.1 to be consistent. Let me send out a separate to hopefully drive consensus on this. toby cabot wrote: Hi, On Fri, Jun 16, 2006 at 12:40:03AM -0400, Matt Hogstrom wrote: Working copies of versions in branches would be branches/n.n. This would be the effective trunk for any version work. Does this mean that someone will be re-creating a branches/1.1 branch? There used to be one, and it looks as if there isn't one now. Otherwise I can do a new checkout of the 1.1.1 branch but if there's going to be a 1.1 branch I think I'd rather track it than a specific release branch. Thanks, Toby -- Regards, Hiram Blog: http://hiramchirino.com
[jira] Commented: (XBEAN-21) org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work
[ http://issues.apache.org/jira/browse/XBEAN-21?page=comments#action_12416899 ] Alan Cabrera commented on XBEAN-21: --- Can you provide some detail as to what this means? org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work --- Key: XBEAN-21 URL: http://issues.apache.org/jira/browse/XBEAN-21 Project: XBean Type: Bug Components: spring Versions: 2.4 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: ApacheCon EU
i'll be there on monday afternoon. On 6/20/06, Matt Hogstrom [EMAIL PROTECTED] wrote: I'll be arriving on Monday some time. Alan D. Cabrera wrote: Who's going to ApacheCon EU? Is there going to be a hackathon? Regards, Alan -- Davanum Srinivas : http://wso2.com/blogs/
Re: Web site update
Merging isn't working, I don't see anything being updated into trunk. How do I create a patch if my local working copy is fully in sync with the branch, not the trunk. Is there a way to copy/move the content of the branch and overwrite the trunk? Thanks Hernan David Blevins wrote: On Jun 19, 2006, at 12:11 PM, Hernan Cunico wrote: Hi All, I'm a bit lost with the two branches we have now to manage the web site. I have the .../site/branches/may2006 branch updated and ready to go live, it already includes that last two changes (updated events and added book to documentation). What would be the next step? replacing the content of .../site/ trunk and then commit to the live site from the updated trunk? how do I replace it the content in .../site/trunk with the may2006 branch? Typically, you'd merge over your changes. Could use the 'svn merge' command. Or you could create a patch file and apply it to trunk. I like to use the graphical diff tool in Visual SlickEdit, but that's not free. -David
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
-1 - There are some licensing and packaging issues. See in-line comments below. Regards, John David Blevins wrote: +1 On Jun 19, 2006, at 8:33 AM, Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip Source zip still has META-INF folder at top level. (the specs jar is ok) LICENSE.txt and NOTICE.txt don't have the licensing changes that were made recently. Maybe you zipped from the wrong place? *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip DayTrader Source file doesn't contain both the LICENSE.txt and NOTICE.txt files. See the specs src for an example of what it should contain. See http://www.apache.org/dev/release.html#what-must-every-release-contain and the section Is a NOTICE File Required For Pure ASF Code? in http://www.apache.org/dev/release.html#license *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear DayTrader ear only contains the LICENSE file. It needs a NOTICE file according to the rules mentioned above. Would be preferable if they had a .txt extension (with the appropriate svn properties) to be consistent with Geronimo.
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
+1 Cheers! Hernan Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear
[jira] Resolved: (SM-459) NPE upon missing in message
[ https://issues.apache.org/activemq/browse/SM-459?page=all ] Guillaume Nodet resolved SM-459: Fix Version: 3.0 Resolution: Fixed Assign To: Guillaume Nodet Author: gnodet Date: Tue Jun 20 04:22:49 2006 New Revision: 415613 URL: http://svn.apache.org/viewvc?rev=415613view=rev Log: Throw a meaningfull exception if no 'in' message is set on the incoming exchange Modified: incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java NPE upon missing in message --- Key: SM-459 URL: https://issues.apache.org/activemq/browse/SM-459 Project: ServiceMix Type: Bug Components: servicemix-http Versions: 3.0-M2 Environment: Windows 2000, JBoss-4.0.3SP1 Reporter: Andreas Held Assignee: Guillaume Nodet Priority: Trivial Fix For: 3.0 I created a component with an InOut exchange and forgot to add the in message. This yielded the following exception: java.lang.NullPointerException at org.apache.servicemix.soap.marshalers.JBIMarshaler.fromNMS(JBIMarshaler.java:76) A slightly more meaningful exception could be helpful. -- 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: (XBEAN-21) org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work
[ http://issues.apache.org/jira/browse/XBEAN-21?page=comments#action_12416901 ] Guillaume Nodet commented on XBEAN-21: -- It means that the current XmlWebApplicationContext is unusable because it does not find the xbean spring 1 or spring 2 implementation classes. I have a fix i put in servicemix, and i will attach a patch asap. See http://svn.apache.org/repos/asf/incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/xbean/XmlWebApplicationContext.java org\apache\xbean\spring\context\XmlWebApplicationContext.java does not work --- Key: XBEAN-21 URL: http://issues.apache.org/jira/browse/XBEAN-21 Project: XBean Type: Bug Components: spring Versions: 2.4 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 2.5 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
Thanks John. I can respin these. Since I don't have to rebuild the server I would like to put out the new files and continue the vote. Does this sound good to everyone ? John Sisson wrote: -1 - There are some licensing and packaging issues. See in-line comments below. Regards, John David Blevins wrote: +1 On Jun 19, 2006, at 8:33 AM, Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip Source zip still has META-INF folder at top level. (the specs jar is ok) LICENSE.txt and NOTICE.txt don't have the licensing changes that were made recently. Maybe you zipped from the wrong place? *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip DayTrader Source file doesn't contain both the LICENSE.txt and NOTICE.txt files. See the specs src for an example of what it should contain. See http://www.apache.org/dev/release.html#what-must-every-release-contain and the section Is a NOTICE File Required For Pure ASF Code? in http://www.apache.org/dev/release.html#license *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear DayTrader ear only contains the LICENSE file. It needs a NOTICE file according to the rules mentioned above. Would be preferable if they had a .txt extension (with the appropriate svn properties) to be consistent with Geronimo.
[jira] Resolved: (AMQ-663) JMX management info about subscriptions is incomplete
[ https://issues.apache.org/activemq/browse/AMQ-663?page=all ] james strachan resolved AMQ-663: Resolution: Fixed fixed in SVN HEAD JMX management info about subscriptions is incomplete - Key: AMQ-663 URL: https://issues.apache.org/activemq/browse/AMQ-663 Project: ActiveMQ Type: Improvement Versions: 4.0 RC2 Reporter: Bruce Mitchener Assignee: james strachan Fix For: 4.1 When I'm viewing my current subscriptions via jconsole, the info about them is incomplete and doesn't mention (at least) whether they are durable or retroactive. There are probably other properties missing? -- 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] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
sounds good to me,. On 6/20/06, Matt Hogstrom [EMAIL PROTECTED] wrote: Thanks John. I can respin these. Since I don't have to rebuild the server I would like to put out the new files and continue the vote. Does this sound good to everyone ? John Sisson wrote: -1 - There are some licensing and packaging issues. See in-line comments below. Regards, John David Blevins wrote: +1 On Jun 19, 2006, at 8:33 AM, Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip Source zip still has META-INF folder at top level. (the specs jar is ok) LICENSE.txt and NOTICE.txt don't have the licensing changes that were made recently. Maybe you zipped from the wrong place? *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip DayTrader Source file doesn't contain both the LICENSE.txt and NOTICE.txt files. See the specs src for an example of what it should contain. See http://www.apache.org/dev/release.html#what-must-every-release-contain and the section Is a NOTICE File Required For Pure ASF Code? in http://www.apache.org/dev/release.html#license *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear DayTrader ear only contains the LICENSE file. It needs a NOTICE file according to the rules mentioned above. Would be preferable if they had a .txt extension (with the appropriate svn properties) to be consistent with Geronimo. -- Davanum Srinivas : http://wso2.com/blogs/
[jira] Resolved: (AMQ-757) MapMessage to support nested Map objects to create a typesafe hierarchial message such as used on RV etc
[ https://issues.apache.org/activemq/browse/AMQ-757?page=all ] james strachan resolved AMQ-757: Resolution: Fixed Supports nested Map and List types (of arbitrary nesting depth) on Message properties or MapMessage. For more details see... http://activemq.org/site/structured-message-properties-and-mapmessages.html MapMessage to support nested Map objects to create a typesafe hierarchial message such as used on RV etc Key: AMQ-757 URL: https://issues.apache.org/activemq/browse/AMQ-757 Project: ActiveMQ Type: Improvement Versions: 4.0 Reporter: james strachan Assignee: james strachan Fix For: 4.1 -- 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
[VOTE-RESULT] Release Apache ActiveMQ 4.0.1
Hi Folks, After the customary 72 hour voting period, the 4.0.1 release was approved with the following +1's: +1 Hiram Chirino +1 Alan D. Cabrera +1 Adrian Co +1 Brian McCallister +1 Jonas Lim +1 Fritz Oconer +1 James Strachan +1 Robert Davies The release will become official once the incubator blesses it. -- Regards, Hiram Blog: http://hiramchirino.com
Re: Nested MapMessage
I've implemented support for nested MapMessage; so that they can contain entires containing arbitrarily deep Map and List objects. This patch also allows nested Map and List objects on JMS Message properties as well. More details of this new feature here... http://activemq.org/site/structured-message-properties-and-mapmessages.html On 6/16/06, James Strachan [EMAIL PROTECTED] wrote: On 6/16/06, jhakim [EMAIL PROTECTED] wrote: Clearly both setObject(name, map) and setObject(name, mapMsg) work. As you correctly point out, using a hierarchical naming scheme would allow the client to specify nesting and works with any MOM. However, I would argue that forcing clients to write code to create/parse a hierarchical naming scheme defeats the key goal of ease of use. For instance, suppose one wants to create a framework for marshaling arbitrary beans to JMS messages. A logical implmentation would be to use reflection to discover bean properties and create a corresponding MapMessage. Now, suppose that a bean contains other beans as properties. One elegant approach would to marshal each bean property to a nested MapMessage. This exact strategy is used by many systems on Wall Street and by open-source projects (messageforge.sourceforge.net). BTW - the underlying JMS provider can, beneath the covers, use hierarchical naming schemes and strip off properties from nested messages. As far as the client is concerned, this should just be an implementation detail and not the required way for clients to use the MOM. Agreed. Obviously if you have a nested array of beans you can obviously use ObjectMessage too - but I totally understand the motivation for having a typesafe hierarchial MapMessage that other languages can parse too. I've created an issue to track this feature request http://issues.apache.org/activemq/browse/AMQ-757 -- James --- http://radio.weblogs.com/0112098/ -- James --- http://radio.weblogs.com/0112098/
[announce] Apache Geronimo welcomes Joe Bohn as our newest committer
In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congrats Joe!! On 6/20/06, Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congratulations Joe!!! Very well deserved :) Welcome!!! Cheers! Hernan Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
On Jun 20, 2006, at 10:47 AM, Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC Congrats Joe! Keep up the great work! --kevan
[jira] Commented: (AMQ-764) Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0)
[ https://issues.apache.org/activemq/browse/AMQ-764?page=comments#action_36441 ] shahzad bhatti commented on AMQ-764: Another thing, I am running ActiveMQ with 800m heap size (which I increased from 512m after memory errors) and message size is 1K. Getting OutofMemoryException after sending 2200 messages (JBoss 4.0/ActiveMQ 4.0) - Key: AMQ-764 URL: https://issues.apache.org/activemq/browse/AMQ-764 Project: ActiveMQ Type: Bug Components: JCA Container Versions: 4.0 RC3 Environment: REDHAT 3.0 JBoss 4.04-GA ActiveMQ-4.0-RC2 Reporter: shahzad bhatti Fix For: 4.0.2 Attachments: activemq_jboss.zip I am testing ActiveMQ 4.0 with JBoss 4.0 where I am using ActiveMQ's .rar file within JBoss. I have a test applicacation that consists of following components: -Message driven bean listens to queue within JBoss. It receives message and invokes stateless session bean, which invokes entity bean and the message is added to the databsae (mysql). After adding message, it replies back the response to the client. -JBoss stateless session bean -- uses entity bean to add message to the database -JBoss entity bean that uses CMP to add message to the database. -Publisher client - uses ActiveMQ APIs to publish message to the queue and listens for response I find that after about 2200 messages, I get OutOfMemory exception in ActiveMQ and my application hangs. I am also attaching source code minus jar files. You will also need mysql database. -- 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: Wiki based FAQ
Sounds cool. Can you setup a demo?
-dain
On Jun 19, 2006, at 7:33 PM, Jason Dillon wrote:
+1
I think that this is a good idea. I setup a wiki-based Knowledge
Base at my previous company in Confluence and it really helped to
collect and spread knowledge.
For this to work in Confluence it should have its own space, like
GMOxKB. It also works really well when using the {excerpt} macro
to give the TOC more context, and the {scrollbar} macro to make it
easier to navigate through pages in the KB.
--jason
On Jun 16, 2006, at 3:19 PM, Dain Sundstrom wrote:
I put together a FAQ in the sandbox on the cwiki. I seeded it
with content from the main wiki on the Geronimo website and with
some content from a resent email I sent about accessing an MBean
server from a GBean.
This is just an idea, and I will have no hard feelings if we
decide to delete it (it only took 20 minutes to get going).
http://cwiki.apache.org/confluence/display/GMOxSBOX/FAQ
What do you think?
-dain
Re: [openejb-dev] Merge of OpenEJB branch dead_2_2
Can you please try to annotate trunk's all_changes.log file to track which revisions you are dealing with? thanks david jencks On Jun 19, 2006, at 1:46 AM, Dain Sundstrom wrote: I've discovered that I need a bunch of patched from geronimo's dead-1.2 branch to make openejb's dead_2_2 version work. The problem is these patches need openejb dead_2_2 or we will get compile errors. To ease this situation, I have created a private working directory for myself at https://svn.apache.org/repos/asf/ geronimo/branches/dain/openejb-2.2-merge. I will try to keep the changes as simple as possible, svn merge commands mostly. I'll do my best to document the svn commands to recreate the changes. -dain On Jun 16, 2006, at 8:55 PM, Dain Sundstrom wrote: I've spent the better part of a day researching the changes in 2.0- dead_2_2 verses the changes in 2.0-trunk, and I have come to the conclusion it will be easier to simply dead_2_2 to run in Geronimo trunk than it will be to apply the dead_2_2 changes to the OpenEJB trunk. Here is more info on what I found in much more detail: 2664-HEAD - Packaging for release an branch cutting 2595-2664 - A few new features such like xbean serialization, MEJB rewrite, jndi changes (mount gbeans into jnid) and configuration manager patches branch_1_1-2585 - Main work in 1.1. This is 99% changes caused by API changes in Geronimo configid-branch_1_1 - Minor work to prove configid changes would work 1_0 - configid - configid was cut directly from 1.0 but a few changes made it in for 1.0.1. These were merged into the configid branch immediately before it was renamed to branch_1_1 (r2522). Based on this data, I'm going to make a copy of the dead_2_2 branch and attempt to update it to the new apis by hand. Once this is done, all of us will need to scan over the change log between configid and head to make sure all important fixes or features are present in the dead_2_2 branch. If you already know about important stuff in head that needs to be pulled over, let me know by responding to this email and I'll try to get it in (make sure to CC [EMAIL PROTECTED] and dev@geronimo.apache.org). Right now, I'm not sure this plan will work, but by Sunday I should know. -dain - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Way to go, Joe! -David On Jun 20, 2006, at 7:47 AM, Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Awesome ! Congrats Joe. Cheers Prasad On 6/20/06, anita kulshreshtha [EMAIL PROTECTED] wrote: CONGRATULATIONS! Joe Cheers Anita --- Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congratulations Joe! Aaron On 6/20/06, Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
M2 Build Instructions on wiki (M2 : Build Instruction)
Hi All, I would like to add Maven 2 build instructions to the wiki. Since the code base contains pom.xml files, people assume that it builds with M2. I am considering an index 'Apache Geronimo' or 'Apache Geronimo - Latest'. This space could deal with things happening on the trunk. As suggested by Jacek, I could use 'Apache Geronimo Build using Apache Maven 2' title for the new page. Comments/suggestions? Thanks Anita --- Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/19/06, anita kulshreshtha [EMAIL PROTECTED] wrote: I was looking for a suitable place to add the build instrucitons for M2. I could not find any section dealing with the trunk at http://cwiki.apache.org/geronimo/ Pick your favorite name and propose it. Send a note to dev and await comments. Upon having received some, go and create it. What about 'Apache Geronimo Build using Apache Maven 2' ? Anita Jacek -- Jacek Laskowski http://www.laskowski.net.pl __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[jira] Created: (AMQ-765) ActiveMQ RA serialization issue on Glassfish
ActiveMQ RA serialization issue on Glassfish Key: AMQ-765 URL: https://issues.apache.org/activemq/browse/AMQ-765 Project: ActiveMQ Type: Bug Components: Connector Versions: 4.0.1, 4.0 Environment: Glassfish Reporter: Chris Conrad I've been trying to work through an issue with a NullPointerException run using the JCA 1.5 resource adapter on Glassfish. In the course of debugging, Siva from the Glassfish team provided this information: Thanks for trying out GlassFish. Since I have only the trace snippet above, I tried to debug this problem by going through ActiveMQ RA's source available at https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ This is what I understand happens. Please correct me if there are errors. When ActiveMQConnectionFactory [https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ActiveMQConnectionFactory.java] is created at the createConnectionFactory method of https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ActiveMQManagedConnectionFactory.java, the ConnectionManager is initialized to a *transient* variable manager. Since ConnectionFactory instances can be serialized/deserialized while publishing to JNDI (as is the case in Project GlassFish), the connectionManager reference is lost and hence the NPE. The fix ideally should be in the ActiveMQRA's code. You could copy me [sivakumart AT sun DOT com] while you are discussing this with ActiveMQ, if you wish. If you still have any issues, please provide a copy of your domain.xml [connector connection pool, resource configuratin information] and the entire trace in server.log. -- 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-765) ActiveMQ RA serialization issue on Glassfish
[ https://issues.apache.org/activemq/browse/AMQ-765?page=comments#action_36442 ] Chris Conrad commented on AMQ-765: -- The mailing list discussion related to this issue can be found at: http://www.nabble.com/NullPointerException-with-RA-on-Glassfish-t1814940.html#a4959128 ActiveMQ RA serialization issue on Glassfish Key: AMQ-765 URL: https://issues.apache.org/activemq/browse/AMQ-765 Project: ActiveMQ Type: Bug Components: Connector Versions: 4.0.1, 4.0 Environment: Glassfish Reporter: Chris Conrad I've been trying to work through an issue with a NullPointerException run using the JCA 1.5 resource adapter on Glassfish. In the course of debugging, Siva from the Glassfish team provided this information: Thanks for trying out GlassFish. Since I have only the trace snippet above, I tried to debug this problem by going through ActiveMQ RA's source available at https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ This is what I understand happens. Please correct me if there are errors. When ActiveMQConnectionFactory [https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ActiveMQConnectionFactory.java] is created at the createConnectionFactory method of https://svn.apache.org/repos/asf/incubator/activemq/trunk/activemq-ra/src/main/java/org/apache/activemq/ra/ActiveMQManagedConnectionFactory.java, the ConnectionManager is initialized to a *transient* variable manager. Since ConnectionFactory instances can be serialized/deserialized while publishing to JNDI (as is the case in Project GlassFish), the connectionManager reference is lost and hence the NPE. The fix ideally should be in the ActiveMQRA's code. You could copy me [sivakumart AT sun DOT com] while you are discussing this with ActiveMQ, if you wish. If you still have any issues, please provide a copy of your domain.xml [connector connection pool, resource configuratin information] and the entire trace in server.log. -- 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: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congrats Joe! Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
[jira] Created: (AMQ-766) add jmdns.jar to lib/optional in the binary distro
add jmdns.jar to lib/optional in the binary distro -- Key: AMQ-766 URL: https://issues.apache.org/activemq/browse/AMQ-766 Project: ActiveMQ Type: Improvement Versions: 4.0.1 Reporter: james strachan Fix For: 4.1 its ASL 2.0 so I don't think we need a license file too but its worth double checking -- 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: M2 Build Instructions on wiki (M2 : Build Instruction)
I don't think we should keep creating so many spaces. The idea behind having multiple spaces was to allow easier management of the documentation as we deliver new releases of Geronimo. Documents not attached to specific Geronimo releases should all go into the same space, the challenge would be to give that space a name big enough to clearly send the message what is organized in there. Today that space is named Apache Geronimo SandBox, we definitively need to change it. D. Blevins, if gbuild and vmbuild are part of the Geronimo project, would you consider moving them into the Apache Geronimo SandBox? Again, we need to change that name soon, I couldn't come up with anything better at that time. Any proposal anyone? Cheers! Hernan anita kulshreshtha wrote: Hi All, I would like to add Maven 2 build instructions to the wiki. Since the code base contains pom.xml files, people assume that it builds with M2. I am considering an index 'Apache Geronimo' or 'Apache Geronimo - Latest'. This space could deal with things happening on the trunk. As suggested by Jacek, I could use 'Apache Geronimo Build using Apache Maven 2' title for the new page. Comments/suggestions? Thanks Anita --- Jacek Laskowski [EMAIL PROTECTED] wrote: On 6/19/06, anita kulshreshtha [EMAIL PROTECTED] wrote: I was looking for a suitable place to add the build instrucitons for M2. I could not find any section dealing with the trunk at http://cwiki.apache.org/geronimo/ Pick your favorite name and propose it. Send a note to dev and await comments. Upon having received some, go and create it. What about 'Apache Geronimo Build using Apache Maven 2' ? Anita Jacek -- Jacek Laskowski http://www.laskowski.net.pl __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[jira] Created: (GERONIMO-2139) Link to Geronimo documentation is out of date, point still to atlassian server.
Link to Geronimo documentation is out of date, point still to atlassian server. --- Key: GERONIMO-2139 URL: http://issues.apache.org/jira/browse/GERONIMO-2139 Project: Geronimo Type: Bug Security: public (Regular issues) Components: website Reporter: Glen Mazza Priority: Minor Hello, on this page: http://geronimo.apache.org/documentation.html The first two links under Online documentation are out of date--they are pointing to the atlassian sites that both state that they are obsolete. The first link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-users-guide.html but is instead pointing to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+V1+-+Documentation+Draft The second link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-developers-guide.html but is instead pointint to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+Development+Process Thanks, Glen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Wiki based FAQ
Sure, maybe have something to look at later this week.--jasonOn 6/20/06, Dain Sundstrom [EMAIL PROTECTED]
wrote:Sounds cool.Can you setup a demo?-dainOn Jun 19, 2006, at 7:33 PM, Jason Dillon wrote:
+1 I think that this is a good idea.I setup a wiki-based Knowledge Base at my previous company in Confluence and it really helped to collect and spread knowledge.
For this to work in Confluence it should have its own space, like GMOxKB.It also works really well when using the {excerpt}macro to give the TOC more context, and the {scrollbar} macro to make it
easier to navigate through pages in the KB. --jason On Jun 16, 2006, at 3:19 PM, Dain Sundstrom wrote: I put together a FAQ in the sandbox on the cwiki.I seeded it
with content from the main wiki on the Geronimo website and with some content from a resent email I sent about accessing an MBean server from a GBean. This is just an idea, and I will have no hard feelings if we
decide to delete it (it only took 20 minutes to get going). http://cwiki.apache.org/confluence/display/GMOxSBOX/FAQ
What do you think? -dain
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congratulation! -dain On Jun 20, 2006, at 7:47 AM, Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [openejb-dev] Merge of OpenEJB branch dead_2_2
Done. I noted which ones I merged into branches/dain/openejb-2.2-merge. If we ultimately merge changes from that branch to trunk, we should change the status. -dain On Jun 20, 2006, at 6:11 AM, David Jencks wrote: Can you please try to annotate trunk's all_changes.log file to track which revisions you are dealing with? thanks david jencks On Jun 19, 2006, at 1:46 AM, Dain Sundstrom wrote: I've discovered that I need a bunch of patched from geronimo's dead-1.2 branch to make openejb's dead_2_2 version work. The problem is these patches need openejb dead_2_2 or we will get compile errors. To ease this situation, I have created a private working directory for myself at https://svn.apache.org/repos/asf/ geronimo/branches/dain/openejb-2.2-merge. I will try to keep the changes as simple as possible, svn merge commands mostly. I'll do my best to document the svn commands to recreate the changes. -dain On Jun 16, 2006, at 8:55 PM, Dain Sundstrom wrote: I've spent the better part of a day researching the changes in 2.0-dead_2_2 verses the changes in 2.0-trunk, and I have come to the conclusion it will be easier to simply dead_2_2 to run in Geronimo trunk than it will be to apply the dead_2_2 changes to the OpenEJB trunk. Here is more info on what I found in much more detail: 2664-HEAD - Packaging for release an branch cutting 2595-2664 - A few new features such like xbean serialization, MEJB rewrite, jndi changes (mount gbeans into jnid) and configuration manager patches branch_1_1-2585 - Main work in 1.1. This is 99% changes caused by API changes in Geronimo configid-branch_1_1 - Minor work to prove configid changes would work 1_0 - configid - configid was cut directly from 1.0 but a few changes made it in for 1.0.1. These were merged into the configid branch immediately before it was renamed to branch_1_1 (r2522). Based on this data, I'm going to make a copy of the dead_2_2 branch and attempt to update it to the new apis by hand. Once this is done, all of us will need to scan over the change log between configid and head to make sure all important fixes or features are present in the dead_2_2 branch. If you already know about important stuff in head that needs to be pulled over, let me know by responding to this email and I'll try to get it in (make sure to CC [EMAIL PROTECTED] and dev@geronimo.apache.org). Right now, I'm not sure this plan will work, but by Sunday I should know. -dain - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Welcome :-)--jasonOn 6/20/06, Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community,the Geronimo PMC is proud to announce the committership of Joe Bohn.Joe has contributed in many areas, including the console and as ofrecent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy forproblems faced by other committers and willingness to work on fixingthese problems. We look forward to his continued involvement as a committer.Please join us in congratulating Joe.The Apache Geronimo PMC
[jira] Assigned: (GERONIMO-2139) Link to Geronimo documentation is out of date, point still to atlassian server.
[ http://issues.apache.org/jira/browse/GERONIMO-2139?page=all ] Hernan Cunico reassigned GERONIMO-2139: --- Assign To: Hernan Cunico Link to Geronimo documentation is out of date, point still to atlassian server. --- Key: GERONIMO-2139 URL: http://issues.apache.org/jira/browse/GERONIMO-2139 Project: Geronimo Type: Bug Security: public(Regular issues) Components: website Reporter: Glen Mazza Assignee: Hernan Cunico Priority: Minor Hello, on this page: http://geronimo.apache.org/documentation.html The first two links under Online documentation are out of date--they are pointing to the atlassian sites that both state that they are obsolete. The first link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-users-guide.html but is instead pointing to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+V1+-+Documentation+Draft The second link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-developers-guide.html but is instead pointint to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+Development+Process Thanks, Glen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2139) Link to Geronimo documentation is out of date, point still to atlassian server.
[ http://issues.apache.org/jira/browse/GERONIMO-2139?page=comments#action_12416968 ] Hernan Cunico commented on GERONIMO-2139: - Working on the web site update, merging branch now. Link to Geronimo documentation is out of date, point still to atlassian server. --- Key: GERONIMO-2139 URL: http://issues.apache.org/jira/browse/GERONIMO-2139 Project: Geronimo Type: Bug Security: public(Regular issues) Components: website Reporter: Glen Mazza Assignee: Hernan Cunico Priority: Minor Hello, on this page: http://geronimo.apache.org/documentation.html The first two links under Online documentation are out of date--they are pointing to the atlassian sites that both state that they are obsolete. The first link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-users-guide.html but is instead pointing to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+V1+-+Documentation+Draft The second link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-developers-guide.html but is instead pointint to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+Development+Process Thanks, Glen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-2139) Link to Geronimo documentation is out of date, point still to atlassian server.
[ http://issues.apache.org/jira/browse/GERONIMO-2139?page=all ] Hernan Cunico resolved GERONIMO-2139: - Resolution: Fixed I just updated the web site. These changes should be reflected on the live site momentarily. Link to Geronimo documentation is out of date, point still to atlassian server. --- Key: GERONIMO-2139 URL: http://issues.apache.org/jira/browse/GERONIMO-2139 Project: Geronimo Type: Bug Security: public(Regular issues) Components: website Reporter: Glen Mazza Assignee: Hernan Cunico Priority: Minor Hello, on this page: http://geronimo.apache.org/documentation.html The first two links under Online documentation are out of date--they are pointing to the atlassian sites that both state that they are obsolete. The first link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-users-guide.html but is instead pointing to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+V1+-+Documentation+Draft The second link should point to: http://cwiki.apache.org/GMOxDOC10/apache-geronimo-v10-developers-guide.html but is instead pointint to: http://opensource.atlassian.com/confluence/oss/display/GERONIMO/Apache+Geronimo+Development+Process Thanks, Glen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
On 6/20/06, Sachin Patel [EMAIL PROTECTED] wrote: Please join us in congratulating Joe. Congrats Joe! Don't think you're done - the game has just begun :-) Jacek -- Jacek Laskowski http://www.laskowski.net.pl
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congrats JOE! Keep up the good work. ;) --- Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congrats, and welcome aboard !Guillaume NodetOn 6/20/06, Sachin Patel [EMAIL PROTECTED] wrote: In recognition of his contributions to the Apache Geronimo community,the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as ofrecent, the work on our minimal distributions.His work shows initiative, concern to get user feedback, empathy forproblems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as acommitter.Please join us in congratulating Joe.The Apache Geronimo PMC
[jira] Created: (SM-461) Fix possible NPE in ExtendedXMLStreamReader
Fix possible NPE in ExtendedXMLStreamReader --- Key: SM-461 URL: https://issues.apache.org/activemq/browse/SM-461 Project: ServiceMix Type: Bug Versions: 3.0-M2 Reporter: Guillaume Nodet Fix For: 3.0-M2 ERROR - Jsr181Component- Error processing exchange null java.lang.NullPointerException at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.FragmentStreamReader.getNamespaceURI(FragmentStreamReader.java:125) at org.apache.servicemix.jbi.jaxp.StaxSource.getAttributes(StaxSource.java:137) at org.apache.servicemix.jbi.jaxp.StaxSource.parse(StaxSource.java:105) at org.apache.servicemix.jbi.jaxp.StaxSource.parse(StaxSource.java:220) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.getXMLStreamReader(Jsr181ExchangeProcessor.java:114) at org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:78) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:397) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:42) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:619) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:168) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:226) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) 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: (SM-461) Fix possible NPE in ExtendedXMLStreamReader
[ https://issues.apache.org/activemq/browse/SM-461?page=all ] Guillaume Nodet resolved SM-461: Fix Version: 3.0 (was: 3.0-M2) Resolution: Fixed Assign To: Guillaume Nodet Author: gnodet Date: Tue Jun 20 13:44:35 2006 New Revision: 415795 URL: http://svn.apache.org/viewvc?rev=415795view=rev Log: SM-461: Fix possible NPE in ExtendedXMLStreamReader Modified: incubator/servicemix/trunk/servicemix-core/src/main/java/org/apache/servicemix/jbi/jaxp/ExtendedXMLStreamReader.java Fix possible NPE in ExtendedXMLStreamReader --- Key: SM-461 URL: https://issues.apache.org/activemq/browse/SM-461 Project: ServiceMix Type: Bug Versions: 3.0-M2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.0 ERROR - Jsr181Component- Error processing exchange null java.lang.NullPointerException at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.ExtendedXMLStreamReader$SimpleNamespaceContext.getNamespaceURI(ExtendedXMLStreamReader.java:105) at org.apache.servicemix.jbi.jaxp.FragmentStreamReader.getNamespaceURI(FragmentStreamReader.java:125) at org.apache.servicemix.jbi.jaxp.StaxSource.getAttributes(StaxSource.java:137) at org.apache.servicemix.jbi.jaxp.StaxSource.parse(StaxSource.java:105) at org.apache.servicemix.jbi.jaxp.StaxSource.parse(StaxSource.java:220) at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484) at org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.getXMLStreamReader(Jsr181ExchangeProcessor.java:114) at org.apache.servicemix.jsr181.Jsr181ExchangeProcessor.process(Jsr181ExchangeProcessor.java:78) at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:397) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:42) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:619) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:168) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:226) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) 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: (SM-462) When the processor throws an exception, the BaseLifeCycle tries to rollback a transaction when there is no transaction active
When the processor throws an exception, the BaseLifeCycle tries to rollback a transaction when there is no transaction active - Key: SM-462 URL: https://issues.apache.org/activemq/browse/SM-462 Project: ServiceMix Type: Bug Components: servicemix-common Versions: 3.0-M2 Reporter: Guillaume Nodet Assigned to: Guillaume Nodet Fix For: 3.0 ERROR - Jsr181Component- Error setting exchange status to ERROR java.lang.IllegalStateException: No transaction associated with current thread at org.apache.geronimo.transaction.manager.TransactionManagerImpl.setRollbackOnly(TransactionManagerImpl.java:132) at org.apache.geronimo.transaction.context.TransactionContextManager.setRollbackOnly(TransactionContextManager.java:193) at org.apache.geronimo.transaction.context.GeronimoTransactionManager.setRollbackOnly(GeronimoTransactionManager.java:115) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:51) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:619) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:168) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:226) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) 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
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
+1 John Matt Hogstrom wrote: Thanks John. I can respin these. Since I don't have to rebuild the server I would like to put out the new files and continue the vote. Does this sound good to everyone ? John Sisson wrote: -1 - There are some licensing and packaging issues. See in-line comments below. Regards, John David Blevins wrote: +1 On Jun 19, 2006, at 8:33 AM, Matt Hogstrom wrote: Here are the latest binaries built from http://svn.apache.org/repos/asf/geronimo/branches/1.1.0, http://svn.apache.org/repos/asf/geronimo/specs/tags/1_1 and http://svn.apache.org/repos/asf/geronimo/daytrader/branches/1.1.0. I believe this will start a new vote for this binary. All issues that I'm aware of have been addressed that needed to be for this release. RELEASE-NOTES-1.1.txt were updated with issues that will be addressed in 1.1.1. *Previous Votes are invalidated...please re-vote* The console has been updated to reflect issues related to bad links. Consensus appears to favor defering the LICENSE issue in the console to 1.1.1 as the correct LICENSE and NOTICES files are included in the builds. DayTrader sources are included with updated README to instruct the user how to build and install DayTrader on Geronimo. Please cast your votes and remember that only PMC member votes are binding. However, I am confident that commiter votes will help to inform the PMC of the quality of this release candidate. Thanks to all that have been checking this out. John Sisson especially has been burning the midnight oil and finding the remaining issues that have helped to improve the quality of this release. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2_src.zip Source zip still has META-INF folder at top level. (the specs jar is ok) LICENSE.txt and NOTICE.txt don't have the licensing changes that were made recently. Maybe you zipped from the wrong place? *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.zip DayTrader Source file doesn't contain both the LICENSE.txt and NOTICE.txt files. See the specs src for an example of what it should contain. See http://www.apache.org/dev/release.html#what-must-every-release-contain and the section Is a NOTICE File Required For Pure ASF Code? in http://www.apache.org/dev/release.html#license *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.ear Note: to build Geronimo the above ear needs to be placed into your repo as $MAVEN_HOME/repository/geronimo/ears/daytrader-ear-1.1.ear DayTrader ear only contains the LICENSE file. It needs a NOTICE file according to the rules mentioned above. Would be preferable if they had a .txt extension (with the appropriate svn properties) to be consistent with Geronimo.
[jira] Resolved: (SM-462) When the processor throws an exception, the BaseLifeCycle tries to rollback a transaction when there is no transaction active
[ https://issues.apache.org/activemq/browse/SM-462?page=all ] Guillaume Nodet resolved SM-462: Resolution: Fixed Author: gnodet Date: Tue Jun 20 13:51:12 2006 New Revision: 415798 URL: http://svn.apache.org/viewvc?rev=415798view=rev Log: SM-462: When the processor throws an exception, BaseLifeCycle tries to rollback a transaction when there is no transaction active Modified: incubator/servicemix/trunk/servicemix-common/src/main/java/org/apache/servicemix/common/BaseLifeCycle.java When the processor throws an exception, the BaseLifeCycle tries to rollback a transaction when there is no transaction active - Key: SM-462 URL: https://issues.apache.org/activemq/browse/SM-462 Project: ServiceMix Type: Bug Components: servicemix-common Versions: 3.0-M2 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 3.0 ERROR - Jsr181Component- Error setting exchange status to ERROR java.lang.IllegalStateException: No transaction associated with current thread at org.apache.geronimo.transaction.manager.TransactionManagerImpl.setRollbackOnly(TransactionManagerImpl.java:132) at org.apache.geronimo.transaction.context.TransactionContextManager.setRollbackOnly(TransactionContextManager.java:193) at org.apache.geronimo.transaction.context.GeronimoTransactionManager.setRollbackOnly(GeronimoTransactionManager.java:115) at org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:51) at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:619) at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:168) at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176) at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:226) at org.apache.geronimo.connector.work.WorkerContext.run(WorkerContext.java:291) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) 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
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
The corrections applied due to license files are first in this list. Thanks to John for dogging this. The distributions and builds were not affected. Based on previous feedback the vote continues. Thanks for your feedback. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2.1_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2.1_src.zip John noted that the source zip had a META-INF. I've created a script to use in the future because with so many changes forgetting to use zip and typing jar is not acceptable. Also, note that the build itself has the LICENSE and NOTICES in two different places. The are located in modules/scripts/src/main/resources/ which put the right files in the distributions however they werenot correctly specified for source as the LICENSE and NOTICES are part of the source tree. After this release we need to address this issue so as to avoid manual problems like this. *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.1.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.1.zip Corrected LICENSE and NOTICES files. Use zip rather than jar to create zip. *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.1.ear Corrected LICENSE and NOTICE files in ear. John, whats the correct command to set the properties? Or, would you like to address these? No changes to the below files. *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Well deserved. Congratulations! John Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Congratulations Joe! Gianny Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC
Re: [VOTE] Geronimo 1.1, DayTrader 1.1 and Specs 1.1 Final-2 Vote
Matt Hogstrom wrote: The corrections applied due to license files are first in this list. Thanks to John for dogging this. The distributions and builds were not affected. Based on previous feedback the vote continues. Thanks for your feedback. *Geronimo 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2.1_src.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-1.1-final-2.1_src.zip John noted that the source zip had a META-INF. I've created a script to use in the future because with so many changes forgetting to use zip and typing jar is not acceptable. Also, note that the build itself has the LICENSE and NOTICES in two different places. The are located in modules/scripts/src/main/resources/ which put the right files in the distributions however they werenot correctly specified for source as the LICENSE and NOTICES are part of the source tree. After this release we need to address this issue so as to avoid manual problems like this. Thanks for creating the script, it will be helpful to others who may build releases in the future. *DayTrader 1.1 Version* *Source* http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.1.tar.gz http://people.apache.org/~hogstrom/1.1-final2/daytrader_src-1.1-final-2.1.zip Corrected LICENSE and NOTICES files. Use zip rather than jar to create zip. *Ear* http://people.apache.org/~hogstrom/1.1-final2/daytrader-ear-1.1-final-2.1.ear Corrected LICENSE and NOTICE files in ear. John, whats the correct command to set the properties? Or, would you like to address these? FYI.. The svn propset command is used to set the properties. If you need to set properties on a single existing file, look at the commands for the appropriate file extension that are used in https://svn.apache.org/repos/asf/geronimo/gbuild/trunk/svnpropset.sh I noticed there are a few files in daytrader without the correct properties (e.g. pom.xml and README.jboss). I can fix this up after the release is out if you like, but I will have to do it to the DT trunk and branches so there aren't problems merging changes. What are the plans for the m2standard branch in Daytrader? Thanks, John No changes to the below files. *Full J2EE Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-j2ee-1.1-final-2.zip *Minimal Jetty Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-jetty-minimal-1.1-final-2.zip *Full Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-j2ee-1.1-final-2.zip *Minimal Tomcat Version* http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/geronimo-tomcat-minimal-1.1-final-2.zip *Geronimo 1.1 Spec Jars* *Source* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs_src-1.1-final-2.zip *Binaries* http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.tar.gz http://people.apache.org/~hogstrom/1.1-final2/org.apache.geronimo.specs-1.1-final-2.zip
Re: M2 Build Instructions on wiki (M2 : Build Instruction)
I don't think we should keep creating so many spaces. The idea behind having multiple spaces was to allow easier management of the documentation as we deliver new releases of Geronimo. I do not think we should limit the number of spaces... If a sub-project warrants its own space, then lets give it one. Spaces are just like top-level directories in a 2-level file system. If it was more than 2-levels, then I would agree, but since it is not, then I think that adding new spaces where appropriate is the way to go. D. Blevins, if gbuild and vmbuild are part of the Geronimo project, would you consider moving them into the Apache Geronimo SandBox? IMO, GBuild/vmbuild should have a separate space. Again, we need to change that name soon, I couldn't come up with anything better at that time. Any proposal anyone? Just change it to Apache Geronimo, GMO. The root space. All other spaces are GMOxYYY --jason
Derby library does not have line number debug information
The Derby library we are using in Geronimo does not have line number debug information, which is useful in stack traces. This has been addressed in the upcoming Derby 10.1.3 release by providing a lib-debug distribution ( http://issues.apache.org/jira/browse/DERBY-178 ) . I'll raise a JIRA if people think it would be a good idea to use the debug version. Comments? Thanks, John
Re: Derby library does not have line number debug information
+1 to using the debug version of derby Paul On 6/20/06, John Sisson [EMAIL PROTECTED] wrote: The Derby library we are using in Geronimo does not have line number debug information, which is useful in stack traces. This has been addressed in the upcoming Derby 10.1.3 release by providing a lib-debug distribution ( http://issues.apache.org/jira/browse/DERBY-178 ) . I'll raise a JIRA if people think it would be a good idea to use the debug version. Comments? Thanks, John
Re: Derby library does not have line number debug information
+10 The lack of line numbers makes is virtually impossible to fix problems, and has really bitten me in the past. -dain On Jun 20, 2006, at 5:38 PM, John Sisson wrote: The Derby library we are using in Geronimo does not have line number debug information, which is useful in stack traces. This has been addressed in the upcoming Derby 10.1.3 release by providing a lib-debug distribution ( http://issues.apache.org/jira/ browse/DERBY-178 ) . I'll raise a JIRA if people think it would be a good idea to use the debug version. Comments? Thanks, John
Re: [announce] Apache Geronimo welcomes Joe Bohn as our newest committer
Thank you all for your most gracious welcome. I'm both honored and humbled to be working with such a talented group of developers. I'll do my best to try to keep up with all of you! :-) Joe Sachin Patel wrote: In recognition of his contributions to the Apache Geronimo community, the Geronimo PMC is proud to announce the committership of Joe Bohn. Joe has contributed in many areas, including the console and as of recent, the work on our minimal distributions. His work shows initiative, concern to get user feedback, empathy for problems faced by other committers and willingness to work on fixing these problems. We look forward to his continued involvement as a committer. Please join us in congratulating Joe. The Apache Geronimo PMC -- Joe Bohn joe.bohn at earthlink.net He is no fool who gives what he cannot keep, to gain what he cannot lose. -- Jim Elliot
