[jira] Updated: (SM-702) Components instantiated multiple times
[ https://issues.apache.org/activemq/browse/SM-702?page=all ] Guillaume Nodet updated SM-702: --- Fix Version/s: 3.0.1 3.1 Components instantiated multiple times -- Key: SM-702 URL: https://issues.apache.org/activemq/browse/SM-702 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Environment: Win32 - ServiceMix 3.0-incubating Reporter: Andrew Chullikal Fix For: 3.0.1, 3.1 Attachments: src.zip I've been trying to write some of my own components, taking the file poller example as a starting basis. Being a newbie, I just ran the test code through my IDE's debugger and noticed that the components' constructors were being called twice. Also, another time consuming exercise was figuring that the endpoint had to be activated in my code, unlike the code present in the servicemix-component package. According to Sun's doc, the component is normaly meant to inform the engine that it has an active endpoint. What worries me here, is that there could be non-portability across containers. Perhaps the code in the PojoSupport init method could log a warning if the is no activated endpoint ? Finaly, there seems to be a discrepency between LifeCycleMBean.STARTED in the servicemix-jbi.jar and the javax.jbi.management.LifeCycleMbean.RUNNING token. Otherwise, keep up the good work ... -- 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-707) Subscription Manager and Flow MBeans do not get unregistered.
[ https://issues.apache.org/activemq/browse/SM-707?page=all ] Guillaume Nodet updated SM-707: --- Fix Version/s: 3.0.1 3.1 Subscription Manager and Flow MBeans do not get unregistered. - Key: SM-707 URL: https://issues.apache.org/activemq/browse/SM-707 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0 Reporter: Pawel Lipka Priority: Minor Fix For: 3.0.1, 3.1 Original Estimate: 1 hour Remaining Estimate: 1 hour These MBeans do not get unregistered upon container shutdown. -- 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-709) Upgrade to xbean 2.7 and Spring 2.0
Upgrade to xbean 2.7 and Spring 2.0 --- Key: SM-709 URL: https://issues.apache.org/activemq/browse/SM-709 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Reporter: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Created: (SM-710) Upgrade to jetty 6.0.1
Upgrade to jetty 6.0.1 -- Key: SM-710 URL: https://issues.apache.org/activemq/browse/SM-710 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Created: (SM-712) Upgrade to xfire 1.2.2
Upgrade to xfire 1.2.2 -- Key: SM-712 URL: https://issues.apache.org/activemq/browse/SM-712 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Commented: (SM-709) Upgrade to xbean 2.7 and Spring 2.0
[ https://issues.apache.org/activemq/browse/SM-709?page=comments#action_37204 ] Guillaume Nodet commented on SM-709: Need to upgrade to xbean 2.7 final when out Upgrade to xbean 2.7 and Spring 2.0 --- Key: SM-709 URL: https://issues.apache.org/activemq/browse/SM-709 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Commented: (SM-410) Component Uninstallation : ClassLoader not removed from JVM
[ https://issues.apache.org/activemq/browse/SM-410?page=comments#action_37205 ] Philippe Pinheiro commented on SM-410: -- I confirm that this problem still exist on the version 3.0 I also want to add that the number of classloader (org.apache.xbean.classloader.JarFileClassLoader) increases in the JVM after install / uninstall of the same component meaning that this issue is the cause of a memory leak. Component Uninstallation : ClassLoader not removed from JVM --- Key: SM-410 URL: https://issues.apache.org/activemq/browse/SM-410 Project: ServiceMix Issue Type: Bug Components: servicemix-components Affects Versions: 3.0-M1 Reporter: Philippe Pinheiro Attachments: servicemix.log After component uninstallation, the corresponding component classloader is not removed from the JVM and the jars in the wdir are locked. To reproduce this bug you just need to : - install the component : servicemix-jms by putting the jar on the install folder - install a service assembly containing a service unit with some endpoints : copy the zip in the deploy folder - uninstall the service assembly : delete the zip file - uninstall the component : delete the jar file Then you will see that some files are still locked on the wdir folder. Furthermore I use JSwat to remotely debug the JVM, with this tool you can see that the ParentFirstClassloader of the servicemix-jms component is still loaded. I also found that if a service assembly is not installed then this bug doesn't occur. -- 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-712) Upgrade to xfire 1.2.2
[ https://issues.apache.org/activemq/browse/SM-712?page=all ] Guillaume Nodet resolved SM-712. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Tue Oct 17 00:36:28 2006 New Revision: 464856 URL: http://svn.apache.org/viewvc?view=revrev=464856 Log: SM-712: Upgrade to xfire-1.2.2 Modified: incubator/servicemix/branches/servicemix-3.0/pom.xml Author: gnodet Date: Tue Oct 17 00:36:12 2006 New Revision: 464855 URL: http://svn.apache.org/viewvc?view=revrev=464855 Log: SM-712: Upgrade to xfire-1.2.2 Modified: incubator/servicemix/trunk/pom.xml Upgrade to xfire 1.2.2 -- Key: SM-712 URL: https://issues.apache.org/activemq/browse/SM-712 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Resolved: (SM-711) Upgrade to woodstox 3.0.2
[ https://issues.apache.org/activemq/browse/SM-711?page=all ] Guillaume Nodet resolved SM-711. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Tue Oct 17 00:34:25 2006 New Revision: 464854 URL: http://svn.apache.org/viewvc?view=revrev=464854 Log: SM-711: Upgrade to woodstox 3.0.2 Modified: incubator/servicemix/branches/servicemix-3.0/pom.xml Author: gnodet Date: Tue Oct 17 00:33:56 2006 New Revision: 464853 URL: http://svn.apache.org/viewvc?view=revrev=464853 Log: SM-711: Upgrade to woodstox 3.0.2 Modified: incubator/servicemix/trunk/pom.xml Upgrade to woodstox 3.0.2 - Key: SM-711 URL: https://issues.apache.org/activemq/browse/SM-711 Project: ServiceMix Issue Type: Improvement Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Commented: (SM-709) Upgrade to xbean 2.7 and Spring 2.0
[ https://issues.apache.org/activemq/browse/SM-709?page=comments#action_37210 ] Guillaume Nodet commented on SM-709: Author: gnodet Date: Tue Oct 17 00:28:20 2006 New Revision: 464850 URL: http://svn.apache.org/viewvc?view=revrev=464850 Log: SM-709: Upgrade to xbean-2.7 and spring-2.0 Modified: incubator/servicemix/trunk/pom.xml Author: gnodet Date: Tue Oct 17 00:27:46 2006 New Revision: 464849 URL: http://svn.apache.org/viewvc?view=revrev=464849 Log: SM-709: Upgrade to xbean-2.7 and spring-2.0 Modified: incubator/servicemix/branches/servicemix-3.0/pom.xml Upgrade to xbean 2.7 and Spring 2.0 --- Key: SM-709 URL: https://issues.apache.org/activemq/browse/SM-709 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Resolved: (SM-671) Use RI implementations for activation and javamail instead of geronimo ones
[ https://issues.apache.org/activemq/browse/SM-671?page=all ] Guillaume Nodet resolved SM-671. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Tue Oct 17 02:27:32 2006 New Revision: 464872 URL: http://svn.apache.org/viewvc?view=revrev=464872 Log: SM-671: Use RI implementation of mail and activation Modified: incubator/servicemix/trunk/apache-servicemix/pom.xml incubator/servicemix/trunk/apache-servicemix/src/main/assembly/bin.xml Author: gnodet Date: Tue Oct 17 02:27:59 2006 New Revision: 464873 URL: http://svn.apache.org/viewvc?view=revrev=464873 Log: SM-671: Use RI implementation of mail and activation Modified: incubator/servicemix/branches/servicemix-3.0/apache-servicemix/pom.xml incubator/servicemix/branches/servicemix-3.0/apache-servicemix/src/main/assembly/bin.xml Use RI implementations for activation and javamail instead of geronimo ones --- Key: SM-671 URL: https://issues.apache.org/activemq/browse/SM-671 Project: ServiceMix Issue Type: Task Components: servicemix-assembly Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.0.1, 3.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
[jira] Created: (SM-713) make some time values configurable
make some time values configurable -- Key: SM-713 URL: https://issues.apache.org/activemq/browse/SM-713 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Reporter: Thomas Termin Priority: Critical Attachments: patch The maxIdleTime for the jetty connector as well as the suspend time for the consumer processor are not configurable and both are under certain cirumstances to low (long requests). I added a patch where you can configure this values via JMX with the HttpConfigurationMBean. Hope this will help you. It works fine for us. The suspent time should be higher than the maxIdleTime. -- 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-713) make some time values configurable
[ https://issues.apache.org/activemq/browse/SM-713?page=all ] Guillaume Nodet resolved SM-713. Fix Version/s: 3.1 Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Tue Oct 17 02:55:56 2006 New Revision: 464883 URL: http://svn.apache.org/viewvc?view=revrev=464883 Log: SM-713: Make time-out values configurable Modified: incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JettyContextManager.java incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java make some time values configurable -- Key: SM-713 URL: https://issues.apache.org/activemq/browse/SM-713 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Reporter: Thomas Termin Assigned To: Guillaume Nodet Priority: Critical Fix For: 3.1 Attachments: patch The maxIdleTime for the jetty connector as well as the suspend time for the consumer processor are not configurable and both are under certain cirumstances to low (long requests). I added a patch where you can configure this values via JMX with the HttpConfigurationMBean. Hope this will help you. It works fine for us. The suspent time should be higher than the maxIdleTime. -- 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-695) Dynamic HTTP provider endpoint
[ https://issues.apache.org/activemq/browse/SM-695?page=all ] Guillaume Nodet updated SM-695: --- Patch Info: [Patch Available] Dynamic HTTP provider endpoint -- Key: SM-695 URL: https://issues.apache.org/activemq/browse/SM-695 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Affects Versions: 3.0 Reporter: James Lorenzen Priority: Minor Attachments: HttpProviderTest.java, JbiConstants.java, ProviderProcessor.java, ProviderProcessor.java It would be benficial to add functionaility to the HTTP BC to allow consumers to specify the provider locationURI through a NormalizedMessage property. Please see this thread for related information: http://www.nabble.com/http-endpoint-in-provider-mode%3A-dynamic-destination--tf1413771.html#a6721824 Our team plans on adding some code to the HTTP BC that first looks to see if the NormalizedMessage contains a specific property containing the value for the destination. Therefore a consumer could create a new NormalizedMessage and call setProperty to set the destination URI. If the HTTP BC detects this property he routes the request to this URI; otherwise it continues as normal and uses the locationURI specified in the xbean.xml file. We plan on making and testing this change in the next couple of days. After which we will reply back with the modifications. -- 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
