Re: Release ServiceMix 3.1
But I hope we will have this logging tool in 3.1. Is it possible? I do my best to finish the work on it today. Cheers, Thomas Guillaume Nodet wrote: I think it's time to start the release process for 3.1. I have been working on the distribution a bit, but it needs more work to check that the samples all work well, etc ... So please test the release to ensure everything is working well, that all legal stuff is ok (need to check all jars included in the distribution), etc ... This is a hard work, so help is really welcome :-)
[jira] Commented: (SM-761) JRuby support
[ https://issues.apache.org/activemq/browse/SM-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37905 ] Guillaume Nodet commented on SM-761: This was more related to the servicemix-script component which allows to deploy Groovy / JRuby scripts as endpoints. Btw, spring 2.0.2 has been released a few days ago. For the development process, I agree this is a bit tedious ;-) Any ideas for improving that is welcome. JRuby support - Key: SM-761 URL: https://issues.apache.org/activemq/browse/SM-761 Project: ServiceMix Issue Type: Improvement Components: servicemix-script Reporter: Guillaume Nodet JRuby support should work with spring 2.0.2 + jruby 0.9.1 See http://forum.springframework.org/showthread.php?t=28798 -- 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-801) can not deploy bridge-sa in apache-servicemix-3.1-incubating-SNAPSHOT + Geronimo 1.2 Beta
[ https://issues.apache.org/activemq/browse/SM-801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-801. Resolution: Fixed Assignee: Guillaume Nodet Thanks ! I have checked the modification in, but I put the same jar which is used everywhere in SMX build. Author: gnodet Date: Fri Jan 12 00:28:38 2007 New Revision: 495514 URL: http://svn.apache.org/viewvc?view=revrev=495514 Log: SM-801: Missing stax-api in geronimo plan Modified: incubator/servicemix/trunk/platforms/geronimo/servicemix/pom.xml can not deploy bridge-sa in apache-servicemix-3.1-incubating-SNAPSHOT + Geronimo 1.2 Beta - Key: SM-801 URL: https://issues.apache.org/activemq/browse/SM-801 Project: ServiceMix Issue Type: Bug Components: geronimo Environment: apache-servicemix-3.1-incubating-SNAPSHOT + Geronimo 1.2 Beta Reporter: xiaoxiong duan Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: pom.xml deploy bridge-sa in apache-servicemix-3.1-incubating-SNAPSHOT + Geronimo 1.2 Beta get the following exception: 16:36:22,180 INFO [FileSystemXmlApplicationContext] Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [EMAIL PROTECTED] 16:36:22,180 INFO [DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [org.apache.servicemix.jms.JmsEndpoint,connectionFactory]; root of BeanFactory hierarchy] 16:36:22,190 INFO [ServiceUnitLifeCycle] Starting service unit: bridge-http-su 16:36:22,210 INFO [ServiceAssembly] doFail called for JBI service assembly: bridge-sa 16:36:22,210 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=servicemix-assemblies/bridge-sa/0.0/car?jbiType=JBIServiceAssembly,name=bridge-sa java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamWriter at org.apache.servicemix.http.processors.ConsumerProcessor.init(ConsumerProcessor.java:79) at org.apache.servicemix.http.HttpEndpoint.createConsumerProcessor(HttpEndpoint.java:300) at org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:346) at org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:55) at org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:151) at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103) at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130) at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:105) at org.apache.servicemix.geronimo.ServiceMixGBean.register(ServiceMixGBean.java:201) at org.apache.servicemix.geronimo.ServiceMixGBean$$FastClassByCGLIB$$fcdcf76b.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:122) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:820) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.servicemix.geronimo.Container$$EnhancerByCGLIB$$d7d47bd7.register(generated) at org.apache.servicemix.geronimo.ServiceAssembly.doStart(ServiceAssembly.java:55) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:984) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:543) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:378) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at
[jira] Commented: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37907 ] Guillaume Nodet commented on SM-816: I'm not sure if the commons-logging / log4j jars should be included or removed from the SAR ? The JIRA title seems to say we should remove them, but the patch add those ... useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the
[jira] Commented: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37908 ] Guillaume Nodet commented on SM-816: Sorry, the patch is excludes/, i thought it was dependency/ useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- 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:
[jira] Resolved: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-816. Resolution: Fixed Assignee: Guillaume Nodet Patch committed, thx ! useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- 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
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[ https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37910 ] Guillaume Nodet commented on SM-811: Does Tibco really cares about the content of the SoapAction property, or does it work if you put an empty one for example ? I'd rather put an empty one, until we have full support for SoapActions (they should be retrieved from the WSDL) servicemix-jms does not set SoapAction property for SOAP jms messages - Key: SM-811 URL: https://issues.apache.org/activemq/browse/SM-811 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.0, 3.0.1, 3.1 Environment: Tested with Tibco EMS as jms server and Tibco Business works as system providing the service. The error should also occur with ActiveMQ. Reporter: Christian Schneider Priority: Critical Attachments: servicemix-jms-sm-811.patch, servicemix-jsr181-sm-811.patch When tibco is the client all works well but when tibco implements the service it rejects the soap/jms message as it wants the SoapAction jms property to be set. I have added a dummy SoapAction in StandardProviderProcessor: ... MessageProducer producer = session.createProducer(destination); TextMessage msg = session.createTextMessage(); NormalizedMessage nm = exchange.getMessage(in); fromNMS(nm, msg); String soapAction = default; msg.setStringProperty(SoapAction, soapAction); ... I was able to do a complete request/reply with tibco in this way. Of course the default SoapAction will only help if my service has only one method. From what I see in Tibco the SoapAction should at least contain the method name of the service being called. The servicemix-jms component should by default set this property to make it more compatible with other soap/jms compatible systems. -- 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] Reopened: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégoire A. reopened SM-816: Regression: [Regression] i really don't know what's happen with my patch but it seems forgot exclusion tag before commons-logging L:74 useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators:
[jira] Resolved: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-816. Resolution: Fixed My bad ;-) I should have applied the patch correctly and compiled. This is now fixed. useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: pom.diff Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators:
[jira] Updated: (SM-816) useless include log framwork into jboss deployer
[ https://issues.apache.org/activemq/browse/SM-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégoire A. updated SM-816: --- Attachment: pom.diff.2 useless include log framwork into jboss deployer Key: SM-816 URL: https://issues.apache.org/activemq/browse/SM-816 Project: ServiceMix Issue Type: Bug Affects Versions: incubation Environment: linux, jdk5, jboss 4-0-5 GA Reporter: Grégoire A. Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: pom.diff, pom.diff.2 Original Estimate: 15 minutes Remaining Estimate: 15 minutes Exception raise when commons-logging and log4j jar are included into sar jboss deployer 00:51:07,136 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:58s:2ms 00:51:22,446 ERROR [STDERR] log4j:ERROR A org.jboss.logging.util.OnlyOnceErrorHandler object is not assignable to a org.apache.log4j.spi.ErrorHandler variable. 00:51:22,447 ERROR [STDERR] log4j:ERROR The class org.apache.log4j.spi.ErrorHandler was loaded by 00:51:22,447 ERROR [STDERR] log4j:ERROR [EMAIL PROTECTED] url=file:/home/keo/EclipseWorkspace/workspace_3.2.SMX.TEST/jboss-4.0.5.GA/server/default/tmp/deploy/tmp61318servicemix-jboss-deployer-3.1-SNAPSHOT.sar ,addedOrder=40}] whereas object of type 00:51:22,447 ERROR [STDERR] log4j:ERROR org.jboss.logging.util.OnlyOnceErrorHandler was loaded by [EMAIL PROTECTED] 00:51:22,489 ERROR [STDERR] log4j:ERROR Could not create an Appender. Reported error follows. 00:51:22,489 ERROR [STDERR] java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:175) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:150) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:163) 00:51:22,490 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:425) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:394) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:829) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:712) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:618) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.LogManager.clinit(LogManager.java:122) 00:51:22,491 ERROR [STDERR] at org.apache.log4j.Logger.getLogger(Logger.java:104) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:283) 00:51:22,491 ERROR [STDERR] at org.apache.commons.logging.impl.Log4JLogger.init(Log4JLogger.java:108) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) 00:51:22,491 ERROR [STDERR] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) 00:51:22,491 ERROR [STDERR] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) 00:51:22,492 ERROR [STDERR] at java.lang.reflect.Constructor.newInstance(Constructor.java:494) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1040) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:838) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:601) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:333) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307) 00:51:22,492 ERROR [STDERR] at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:645) 00:51:22,492 ERROR [STDERR] at org.apache.servicemix.jbi.container.JBIContainer.clinit(JBIContainer.java:95) 00:51:22,492 ERROR [STDERR] at org.servicemix.jboss.deployment.JBIService.init(JBIService.java:45) -- 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:
[jira] Commented: (SM-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[ https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37913 ] Christian Schneider commented on SM-811: Tibco requires this field to be set. The message is rejected if there is no SoapAction. An empty SoapAction does not work either. Will it hurt to set the SoapAction? You can´t really always retrieve the SoapAction from the WSDL. In my case there is no WSDl as I go from Pojos to Soap. Perhaps the setting from the WSDL could override the setting derived from the JBI exchange. BTW. WSDLs from Tibco look different in some cases from those that xfire generates. servicemix-jms does not set SoapAction property for SOAP jms messages - Key: SM-811 URL: https://issues.apache.org/activemq/browse/SM-811 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.0, 3.0.1, 3.1 Environment: Tested with Tibco EMS as jms server and Tibco Business works as system providing the service. The error should also occur with ActiveMQ. Reporter: Christian Schneider Priority: Critical Attachments: servicemix-jms-sm-811.patch, servicemix-jsr181-sm-811.patch When tibco is the client all works well but when tibco implements the service it rejects the soap/jms message as it wants the SoapAction jms property to be set. I have added a dummy SoapAction in StandardProviderProcessor: ... MessageProducer producer = session.createProducer(destination); TextMessage msg = session.createTextMessage(); NormalizedMessage nm = exchange.getMessage(in); fromNMS(nm, msg); String soapAction = default; msg.setStringProperty(SoapAction, soapAction); ... I was able to do a complete request/reply with tibco in this way. Of course the default SoapAction will only help if my service has only one method. From what I see in Tibco the SoapAction should at least contain the method name of the service being called. The servicemix-jms component should by default set this property to make it more compatible with other soap/jms compatible systems. -- 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
Build broken
Just synchronised with HEAD and ran the build, but it is failing at ServiceMix :: Samples :: WSDL first :: SA [INFO] Determining component name for service unit wsdl-first-jsr181-su [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.servicemix.maven.plugin.jbi.JbiResolutionListener$Node.getChild ren()Ljava/util/List; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.servicemix.maven.plugin.jbi.JbiResolutionListener$Node.getChild ren()Ljava/util/List; at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:386) at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:213) at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.execute(GenerateServiceAssemblyDescriptorMojo.java:157) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMana ger.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi fecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecyc le(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLif ecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFa ilures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(De faultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecyc leExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Terry
Re: Build broken
Maybe retry with a clean before ? mvn -o clean rm -Rf ~/.m2/repo/org/apache/servicemix mvn -Dmaven.test.skip=true On Fri, 12 Jan 2007 11:02 + (GMT Standard Time), Terry Cox [EMAIL PROTECTED] wrote: Just synchronised with HEAD and ran the build, but it is failing at ServiceMix :: Samples :: WSDL first :: SA [INFO] Determining component name for service unit wsdl-first-jsr181-su [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org.apache.servicemix.maven.plugin.jbi.JbiResolutionListener$Node.getChild ren()Ljava/util/List; [INFO] [INFO] Trace java.lang.NoSuchMethodError: org.apache.servicemix.maven.plugin.jbi.JbiResolutionListener$Node.getChild ren()Ljava/util/List; at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.getComponentName(GenerateServiceAssemblyDescriptorMojo.java:386) at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.generateJbiDescriptor(GenerateServiceAssemblyDescriptorMojo.java:213) at org.apache.servicemix.maven.plugin.jbi.GenerateServiceAssemblyDescriptorMo jo.execute(GenerateServiceAssemblyDescriptorMojo.java:157) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMana ger.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLi fecycleExecutor.java:534) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecyc le(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLif ecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFa ilures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(De faultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecyc leExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm pl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Terry -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: log4j
Hello,
attached the patch for the new logging service. Please have a look at it
if it is ok this way (if it is please let me know I will raise a JIRA
issue then and will attach the patch). If there are any improvements on
it I will change that.
Cheers,
Thomas
Guillaume Nodet wrote:
Forwarding to the dev list ...
I think you may want to take a look at how the
JdbcAuditor, DotViewService or StatisticsService
are implemented. They all inherit the
o.a.s.jbi.management.BaseSystemService
abstract class. They come in different flavous wrt configuration however.
I would recommend to look at the StatisticsService, which can be configured
that way:
sm:container ...
sm:services
sm:statistics .. /
/sm:services
/sm:container
This way, the service is automatically registered in JMX and has its own
lifecycle (which is tied to the container), so that you can stop / start
the
service from jmx.
On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
What I want to do is to implement a MBean which configure the log4j
system periodicaly with a scheduler. But before I will look if there is
a log4j.xml or log4j.properties in the conf directory if there is
nothing in it then I assume that there is no log4j system and don't
reconfigure log4j (I will give you a better explanation later ;-) ).
The Problem what I have is to register a MBean in conf/servicemix.xml.
How do I have to do this? I tried this with the spring MBeanExporter but
it doesn't work for me.
Cheers,
Thomas
Btw, if you don't mind, i'd rather have such discussion on
servicemix-dev / servicemix-users ;-)
No problem at all! If you open the thread...
Cheers,
Thomas
Guillaume Nodet wrote:
Did you implement something useful ? Would you
consider giving it back to ServiceMix ?
On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote:
Sorry I did not mean a servicemix component. I use allways the word
component ;-) since I started working with servicemix. What you
said is
exactly what I meant. So I will have a look on it!
Thanks,
Thomas
Guillaume Nodet wrote:
I would rather use a ServiceMix service instead of
a component, as this is more related to management /
configuration than a component if I understand you
correctly. ... and use a timer to reload the log4j config.
But iirc, log4j already has this feature, we just need to
enable it.
On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote:
Hello Guillaume,
We would need a log4j Component where you can change the debug
level at
runtime. I would implement a MBean which initialise the log4j
system at
startup and also have a scheduler which looks if the
log4j.xml has
changed and then reinitialise the log4j system.
If I would provide you a patch would you accept this in
servicemix?
Cheers,
Thomas Termin
Index: core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogService.java
===
--- core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogService.java (Revision 0)
+++ core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogService.java (Revision 0)
@@ -0,0 +1,212 @@
+package org.apache.servicemix.jbi.logging;
+
+import org.apache.servicemix.jbi.management.BaseSystemService;
+import org.apache.servicemix.jbi.management.OperationInfoHelper;
+import org.apache.servicemix.jbi.management.AttributeInfoHelper;
+import org.apache.servicemix.jbi.container.JBIContainer;
+import org.apache.log4j.Logger;
+import org.springframework.beans.factory.InitializingBean;
+
+import javax.jbi.JBIException;
+import javax.management.MBeanOperationInfo;
+import javax.management.JMException;
+import javax.management.MBeanAttributeInfo;
+import java.util.Timer;
+import java.net.URL;
+import java.net.MalformedURLException;
+
+/**
+ *
+ *
+ * @org.apache.xbean.XBean element=logService
+ *
+ * TODO add methods to change one or more specific LogLevels at runtime
+ */
+public class LogService extends BaseSystemService implements InitializingBean, LogServiceMBean
+{
+ private boolean autoStart = true;
+ private boolean initialized = false;
+ private int refreshPeriod = 60; // 60sec
+ private URL configFileUrl = null;
+ private String configUrl = file:conf/log4j.xml;
+ private LogTask logTask = null;
+ // timer in daemon mode
+ private Timer timer = null;
+ private static Logger logger = Logger.getLogger(LogService.class);
+
+ public void afterPropertiesSet() throws Exception {
+if (this.container == null) {
+ throw new IllegalArgumentException(container should not be null);
+}
+init(getContainer());
+if (autoStart) {
+ start();
+}
+ }
+
+ public JBIContainer getContainer() {
+return container;
+ }
+
+ public void setContainer(JBIContainer container) {
+ this.container
Re: log4j
Yeah, good point. As was only worried to use a relative URL ... Let mw try it first. Could you raise a JIRA and attach the patch please ? On 1/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: Yeah, looks good. I will try it now. What about using a spring Resource instead of a String ? Yes would be nice of course but than I have to learn spring. ;-) I'm not that experienced with spring. I think it would enable using classpath: notation, which is very handy ... Hum, i guess it would not work with JMX ;-) It should. I guess we could simulate that by checking if the url begins with classpath: and use a getClass().getClassLoader().getResource() ? What do you think ? That should of course work. I did this because DOMConfigurator.configure use the url and because I could check the content type of the config file. So that we could later (if it is needed) extend this service for a normal log4j.properties file. If it is application/xml then use DOMConfigurator and if it is text use PropertyConfigurator. Cheers, Thomas On 1/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello, attached the patch for the new logging service. Please have a look at it if it is ok this way (if it is please let me know I will raise a JIRA issue then and will attach the patch). If there are any improvements on it I will change that. Cheers, Thomas Guillaume Nodet wrote: Forwarding to the dev list ... I think you may want to take a look at how the JdbcAuditor, DotViewService or StatisticsService are implemented. They all inherit the o.a.s.jbi.management.BaseSystemService abstract class. They come in different flavous wrt configuration however. I would recommend to look at the StatisticsService, which can be configured that way: sm:container ... sm:services sm:statistics .. / /sm:services /sm:container This way, the service is automatically registered in JMX and has its own lifecycle (which is tied to the container), so that you can stop / start the service from jmx. On 1/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote: What I want to do is to implement a MBean which configure the log4j system periodicaly with a scheduler. But before I will look if there is a log4j.xml or log4j.properties in the conf directory if there is nothing in it then I assume that there is no log4j system and don't reconfigure log4j (I will give you a better explanation later ;-) ). The Problem what I have is to register a MBean in conf/servicemix.xml. How do I have to do this? I tried this with the spring MBeanExporter but it doesn't work for me. Cheers, Thomas Btw, if you don't mind, i'd rather have such discussion on servicemix-dev / servicemix-users ;-) No problem at all! If you open the thread... Cheers, Thomas Guillaume Nodet wrote: Did you implement something useful ? Would you consider giving it back to ServiceMix ? On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote: Sorry I did not mean a servicemix component. I use allways the word component ;-) since I started working with servicemix. What you said is exactly what I meant. So I will have a look on it! Thanks, Thomas Guillaume Nodet wrote: I would rather use a ServiceMix service instead of a component, as this is more related to management / configuration than a component if I understand you correctly. ... and use a timer to reload the log4j config. But iirc, log4j already has this feature, we just need to enable it. On 10/20/06, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello Guillaume, We would need a log4j Component where you can change the debug level at runtime. I would implement a MBean which initialise the log4j system at startup and also have a scheduler which looks if the log4j.xml has changed and then reinitialise the log4j system. If I would provide you a patch would you accept this in servicemix? Cheers, Thomas Termin -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
Re: Singleton Service/Endpoint?
There is usually only one instance which process all the messages concurrently, so if you process them in a synchronized method, only one message will be processed at one time. This does not really ensure ordering however. On 1/12/07, Anthony [EMAIL PROTECTED] wrote: Hi guys, I wrote a service engine that works much the same way as servicemix-eip's split-aggregator but it contains some other functionality that's specific to our environment for e.g.: - aggregation is created (per custom generated session ID) when a start aggregation arrives aggregates when a stop aggregation message arrives - we persist our aggregations in various persistence stores (memory, jms, database) depending on the system involved - etc An example usage would be: 1. start aggregation message with session ID 1 arrives on input endpoint, aggregation is created 2. content for session ID 1 arrives on input endpoint, is added to previous aggregation 3. content for session ID 1 arrives on input endpoint, is added to previous aggregation 4. content for session ID 1 arrives on input endpoint, is added to previous aggregation 5. stop aggregation message for session ID 1 arrives on input endpoint, aggregation finishes and result is put on output endpoint I just pumped 2000 messages through to my input endpoint and it looks like multiple instances of this service engine/assembly is launched for the input messages (like some sort of thread pooling). The messages are then being processed not in the order that I sent them from my test class, causing exceptions. This happens because for example a content messages gets processed before its start aggregation message got processed thus throwing my SessionNotFound exception because the session has not been created yet... Do any of you know how I can make this service engine/unit to be a Singleton / only 1 thread run at a time, thus causing my messages to be processed in the order that they arrive on my input endpoint? Can you just configure this in one of the XML configuration files like you can in Spring? (I'm running this in FUSE version 1.2.1) Please help! Many thanks! Anthony -- View this message in context: http://www.nabble.com/Singleton-Service-Endpoint--tf2965466s12049.html#a8296840 Sent from the ServiceMix - Dev mailing list archive at Nabble.com. -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
[jira] Created: (SM-817) log4j service for changing log levels at runtime
log4j service for changing log levels at runtime - Key: SM-817 URL: https://issues.apache.org/activemq/browse/SM-817 Project: ServiceMix Issue Type: New Feature Components: servicemix-core Reporter: Thomas Termin Attachments: logging_service.patch This patch add a new MBean service to reconfigure the log4j system at runtime. The default is a scheduler which looks in a configurable time for changes in the log4j.xml file and reconfigures the system if something has changed and of course if the file is available. The service could be extended to read also a property file and reconfigure the system as well as to set one or more specific log levels via JMX console. I wouldn't need that...! -- 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-811) servicemix-jms does not set SoapAction property for SOAP jms messages
[ https://issues.apache.org/activemq/browse/SM-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37917 ] Guillaume Nodet commented on SM-811: Could you rework the patch to include the needed code in AbstractJmsProcessor#fromNMS I guess it will need an additional parameter for the exchange. Also, is the value of the soap action really important ? What if no operation is defined on the exchange ? And the current code will throw an NPE if the targetService / targetInterface attribute is used on the endpoint, because the exchange.getEndpoint() may return null. Thanks ! servicemix-jms does not set SoapAction property for SOAP jms messages - Key: SM-811 URL: https://issues.apache.org/activemq/browse/SM-811 Project: ServiceMix Issue Type: Bug Components: servicemix-jms Affects Versions: 3.0, 3.0.1, 3.1 Environment: Tested with Tibco EMS as jms server and Tibco Business works as system providing the service. The error should also occur with ActiveMQ. Reporter: Christian Schneider Priority: Critical Attachments: servicemix-jms-sm-811.patch, servicemix-jsr181-sm-811.patch When tibco is the client all works well but when tibco implements the service it rejects the soap/jms message as it wants the SoapAction jms property to be set. I have added a dummy SoapAction in StandardProviderProcessor: ... MessageProducer producer = session.createProducer(destination); TextMessage msg = session.createTextMessage(); NormalizedMessage nm = exchange.getMessage(in); fromNMS(nm, msg); String soapAction = default; msg.setStringProperty(SoapAction, soapAction); ... I was able to do a complete request/reply with tibco in this way. Of course the default SoapAction will only help if my service has only one method. From what I see in Tibco the SoapAction should at least contain the method name of the service being called. The servicemix-jms component should by default set this property to make it more compatible with other soap/jms compatible systems. -- 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
