[jira] Reopened: (SM-1084) make configurable if CONTENT-TYPE is used as property from the normalized message or not
[ https://issues.apache.org/activemq/browse/SM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reopened SM-1084: --- Should be configurable on per endpoint basis. So tha's not the right solution make configurable if CONTENT-TYPE is used as property from the normalized message or not Key: SM-1084 URL: https://issues.apache.org/activemq/browse/SM-1084 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Affects Versions: 3.1.2 Reporter: Thomas Termin Assignee: Thomas Termin Fix For: 3.1.3, 3.2 Make it configurable if the http content type will be used from the property of the normalized message or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-1084) make configurable if CONTENT-TYPE is used as property from the normalized message or not
[ https://issues.apache.org/activemq/browse/SM-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-1084. --- Resolution: Fixed fixed for 3.2 Author: tterm Date: Thu Oct 4 09:02:44 2007 New Revision: 581955 URL: http://svn.apache.org/viewvc?rev=581955view=rev Log: SM-1084 make configurable if CONTENT-TYPE is used as property from the normalized message or not Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java fixed for 3.1.3 Author: tterm Date: Thu Oct 4 09:23:11 2007 New Revision: 581959 URL: http://svn.apache.org/viewvc?rev=581959view=rev Log: SM-1084 make configurable if CONTENT-TYPE is used as property from the normalized message or not Modified: incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/branches/servicemix-3.1/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java make configurable if CONTENT-TYPE is used as property from the normalized message or not Key: SM-1084 URL: https://issues.apache.org/activemq/browse/SM-1084 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Affects Versions: 3.1.2 Reporter: Thomas Termin Assignee: Thomas Termin Fix For: 3.1.3, 3.2 Make it configurable if the http content type will be used from the property of the normalized message or not -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.2
+1 Cheers, Thomas Freeman Fang wrote: Hi All, I have uploaded a version of ServiceMix 3.1.2 for you to review. See http://cwiki.apache.org/confluence/display/SM/ServiceMix+3.1.2 for all the links and release notes. [ ] +1 Release ServiceMix 3.1.2 [ ] ± 0 [ ] -1 Do not release ServiceMix 3.1.2 Cheers Freeman -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [jira] Commented: (SM-1044) Routing based on message property and set new property on the message in EIP content based router
Sorry for long response time. I will look into your patch as soon as possible. Cheers, Thomas Termin Vinod Chhabria (JIRA) wrote: [ https://issues.apache.org/activemq/browse/SM-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40120 ] Vinod Chhabria commented on SM-1044: We think this is a good enhancement to the existing predicate classes. Can you please approve so we can go ahead and add this to our servicemix installation. We do not want to apply any patch that will not be available in future releases. If you think this is too specific and not good enough to be added as a patch to the servicemix-eip distribution, then please provide us documentation as to how to include our custom predicate class to our service unit. We tried doing it but it is requiring all other eip classes to be included in the service unit. Please advise so we can resolve either way. Routing based on message property and set new property on the message in EIP content based router - Key: SM-1044 URL: https://issues.apache.org/activemq/browse/SM-1044 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Affects Versions: 3.1 Environment: Windows, JBoss-4.0.4-GA using Servicemix deployer Reporter: Srivatsan Sridharan Priority: Minor Attachments: SwitchPredicate.java, XPathPredicate.java SwitchPredicate.java (available in Servicemix trunk) routes based on the (boolean) value of the property set on the message exchange. It would be good to have it 1) route based on the value (not particularly boolean) of a property set on the message. 2) set additional property on the message when the evaluation of property value is true. SwitchPredicate.java attached herewith has the changes to address the above. XPathPredicate.java attached herewith has the changes to set additional property in the ContentBasedRouter. Please let me know if this is the right approach. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Resolved: (SM-1038) http provider endpoint sends wrong Host header
[ https://issues.apache.org/activemq/browse/SM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-1038. --- Resolution: Fixed Fix Version/s: 3.2 Fixed Many thanks to Torsten Mielke for the patch!!! Author: tterm Date: Wed Aug 22 08:09:59 2007 New Revision: 568645 URL: http://svn.apache.org/viewvc?rev=568645view=rev Log: SM-1038 http provider endpoint sends wrong Host header Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java http provider endpoint sends wrong Host header -- Key: SM-1038 URL: https://issues.apache.org/activemq/browse/SM-1038 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.1.1 Environment: JDK 5.0 Reporter: Torsten Mielke Fix For: 3.2 Attachments: http-marshaler.patch The current ServiceMix http:provider endpoint uses jetty-client-6.1.5 library, which contains a bug fixed in their trunk. More infomation on http://fisheye.codehaus.org/browse/jetty-contrib/jetty/trunk/contrib/client/src/main/java/org/mortbay/jetty/client/HttpConnection.java?r1=374r2=378. This causes wrong Host header in HTTP request. Actual Host header looks like this: Host: [EMAIL PROTECTED]//host.com:8080(1,0,0) Of course such header causes HTTP 400 response and endpoint cannot be used at all. To work around this bug deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java needs to get the attached patch applied. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1038) http provider endpoint sends wrong Host header
[ https://issues.apache.org/activemq/browse/SM-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39996 ] Thomas Termin commented on SM-1038: --- Patch should be undone if a new jetty release is available http provider endpoint sends wrong Host header -- Key: SM-1038 URL: https://issues.apache.org/activemq/browse/SM-1038 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.1.1 Environment: JDK 5.0 Reporter: Torsten Mielke Fix For: 3.2 Attachments: http-marshaler.patch The current ServiceMix http:provider endpoint uses jetty-client-6.1.5 library, which contains a bug fixed in their trunk. More infomation on http://fisheye.codehaus.org/browse/jetty-contrib/jetty/trunk/contrib/client/src/main/java/org/mortbay/jetty/client/HttpConnection.java?r1=374r2=378. This causes wrong Host header in HTTP request. Actual Host header looks like this: Host: [EMAIL PROTECTED]//host.com:8080(1,0,0) Of course such header causes HTTP 400 response and endpoint cannot be used at all. To work around this bug deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java needs to get the attached patch applied. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1035) Continuation problems when Max Idle Time ocurr
[
https://issues.apache.org/activemq/browse/SM-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39988
]
Thomas Termin commented on SM-1035:
---
You can adjust the behavoiur with a higher connectorMaxIdleTime and
consumerProcessorSuspendTime (The later should be higher) for long processing
requests. Why should it be wrong to retry a request?
Continuation problems when Max Idle Time ocurr
--
Key: SM-1035
URL: https://issues.apache.org/activemq/browse/SM-1035
Project: ServiceMix
Issue Type: Bug
Components: servicemix-http
Environment: Servicemix 3.1
Reporter: Jorge Rodríguez Pedrianes
Fix For: 3.1.2
Original Estimate: 2 minutes
Remaining Estimate: 2 minutes
HI!
I saw in Http binding component, that if my service work too time, the
http endpoint retry the current request. but this it's wrong. I think that in
ConsumerProcessor class it's better to do this:
{code:title=ConsumerProcessor java|borderStyle=solid}
...
public void process(HttpServletRequest request, HttpServletResponse
response) throws Exception {
// If the continuation is not a retry
if (!cont.isPending() cont.isNew()) {
...
}
{code}
Whith this we avoid put the request two times in the bus.
Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39957 ] Thomas Termin commented on SM-1002: --- Bruce, The problem seems to be in the ProviderProcessor: You can test this with the following scenario for example: httpclient - consumer - lwcontainer1 - provider - NETWORK - consumer - lwcontainer2(with sleep of maybe 10sec) The httpclient has to send more requests in a loop then you have max connections per host. What happens is all threads (higher then max connections per host) are on lock to get a connection. If the first answer comes back there are no more threads to bring the answer back. And then you have the hang/deadlock. The http connection is closed after the done is initiated for the exchange. If the answer is not processed the done state will never initiated and the connection will not be closed and all other threads wait forever. To solve this there should be something like if the threads are don't get a connection, they should go back to the pool and the request should be queued. If there is a connection available the next request from the queue can be processed. Any thoughts on this? Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39959 ] Thomas Termin commented on SM-1002: --- So if I understand you correctly then you will limit the number of connections with the number of threads. I will try this out. But you have to remove the opportunity for the user to change the values for max connections and max connections per host. Because If you don't do that the user can again configure a deadlock scenario, right? Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Termin reopened SM-854:
--
Assignee: Thomas Termin (was: Bruce Snyder)
Should be also fixed for 3.1.2
LogService uses hard-coded path to the log4j.xml file
--
Key: SM-854
URL: https://issues.apache.org/activemq/browse/SM-854
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1
Reporter: Bruce Snyder
Assignee: Thomas Termin
Fix For: 3.2
Attachments: SM-854.patch.txt
The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
able to locate this file and logging will not work properly. Below is the
output from a started in the {{bin}} directory:
{panel}
$ ./servicemix
servicemix: JAVA_HOME not set; results may vary
java version 1.5.0_07
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
JBI Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please
see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - JBIContainer - ServiceMix JBI Container
(ServiceMix) started
INFO - JDBCAdapterFactory - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
ERROR - LogTask- java.io.FileNotFoundException:
conf/log4j.xml (No such file or directory)
{panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-854) LogService uses hard-coded path to the log4j.xml file
[
https://issues.apache.org/activemq/browse/SM-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Termin resolved SM-854.
--
Resolution: Fixed
Fix Version/s: 3.1.2
backport to 3.1.2
Applied the patch from Bruce.
Author: tterm
Date: Thu Jul 26 04:09:05 2007
New Revision: 559781
URL: http://svn.apache.org/viewvc?view=revrev=559781
Log:
SM-854 LogService uses hard-coded path to the log4j.xml file
Modified:
incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogService.java
incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/logging/LogTask.java
LogService uses hard-coded path to the log4j.xml file
--
Key: SM-854
URL: https://issues.apache.org/activemq/browse/SM-854
Project: ServiceMix
Issue Type: Bug
Components: servicemix-core
Affects Versions: 3.1
Reporter: Bruce Snyder
Assignee: Thomas Termin
Fix For: 3.1.2, 3.2
Attachments: SM-854.patch.txt
The path the log4j.xml file is hard-coded to {{conf/log4j.xml}}. If
ServiceMix is started from inside the {{bin}} directory, ServiceMix won't be
able to locate this file and logging will not work properly. Below is the
output from a started in the {{bin}} directory:
{panel}
$ ./servicemix
servicemix: JAVA_HOME not set; results may vary
java version 1.5.0_07
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT
Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at:
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
JBI Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please
see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component:
#SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - JBIContainer - ServiceMix JBI Container
(ServiceMix) started
INFO - JDBCAdapterFactory - Database driver recognized:
[apache_derby_embedded_jdbc_driver]
ERROR - LogTask- java.io.FileNotFoundException:
conf/log4j.xml (No such file or directory)
{panel}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: Checkstyle and PMD
Bruce Snyder wrote: 1) Is there a reason why the maven-checkstyle-plugin is enabled in many subproject level POMs instead of just in the build module POM? It seems like this should be enabled in one location instead of being spread throughout 14 POMs across the code base. Even the PMD ruleset is only enabled in build module POM. I guess it is because not all components are refactored. See for example https://issues.apache.org/activemq/browse/SM-933 On some day there should be all components refactored and the checkstyle will be enabled in only one POM. 2) It is a *major* pain to have a build fail simply because the code is not formatted according to the Checkstyle and PMD conventions being used in ServiceMix. So I've taken a stab at creating a code formatter profile for Eclipse and some quick docs located here: This prevents a user to checkin stuff which is not in the correct style. There were a hint from Guillaume some day. http://cwiki.apache.org/confluence/display/SM/Building#Building-CodeConventions If you're using Eclipse, please try it out and improve it if necessary. Cheers Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: SecuredBroker and responses
Sounds like a good idea for me. Piotr Bzdyl wrote: Hi, I am trying to use SecuredBroker but I have one problem with its current implementation. If the user is not authorized to send the exchange do the endpoint, then the SecurityException is thrown and the exchange is not sent back to the calling component. This is the cause that the caller won't get any response. Shouldn't it return the exchange to the caller with status set to ERROR and the security exception set as an error on the message exchange? Thanks and regards, Piotr -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 GeschÀftsfÌhrer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39658 ] Thomas Termin commented on SM-1002: --- Maybe you could add an example which I could try. Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-1002) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost
[ https://issues.apache.org/activemq/browse/SM-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39656 ] Thomas Termin commented on SM-1002: --- Can you give a bit more information. For example describe the involved components. Could you provide a threaddump for it? (kill -3) Service mix hangs when the # concurrent requests exceeds the maxConnectionsPerHost -- Key: SM-1002 URL: https://issues.apache.org/activemq/browse/SM-1002 Project: ServiceMix Issue Type: Bug Components: servicemix-core Environment: Unix, Java 1.5 Reporter: Ruwan Linton When I am doing a performance test I have sent more than 40 concurrent requests from a single host to servicemix, and the maxConnectionsPerHost was 40. It is acceptable the failing to respond when it exceeds 40 (maxConnectionsPerHost) concurrent requests. But afterward, SM hangs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Split container and components release cycles ?
I think it is a good idea! But it might be hard to test eventually. Cheers, Thomas Guillaume Nodet wrote: I'd like to start a discussion on splitting the container and components release cycles. What do people think about that ? Should we keep the container and all the components in a single release like we have done so far, or should we split these releases and release the components separately from the container ?
[jira] Commented: (SM-978) Provider side of the new HTTP endpoints
[ https://issues.apache.org/activemq/browse/SM-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39550 ] Thomas Termin commented on SM-978: -- How far is this? What is still to do? Provider side of the new HTTP endpoints --- Key: SM-978 URL: https://issues.apache.org/activemq/browse/SM-978 Project: ServiceMix Issue Type: Task Components: servicemix-http Reporter: Guillaume Nodet Attachments: provider.patch Unfinished patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Concurrent connection in servicemix
Hello, Could you provide a little bit more info. Does this appear with http prvoider BC ? Thomas Ruwan Linton wrote: Hi, I am trying to do a performance test on servicemix. When I send 1 requests from 20 threads concurrently servicemix is working fine, no errors. But when the thread count is increased to 40, SM seems to be hanging and I didn't get any reply to my requests. Is there a mechanism to tune SM for handling simultaneous connections? If so can some one please point me how to do that. Thanks in advance, Ruwan 1 -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Resolved: (SM-959) ssl truststore is not set for unmanaged
[ https://issues.apache.org/activemq/browse/SM-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-959. -- Resolution: Fixed Fixed. Author: tterm Date: Thu May 31 05:46:32 2007 New Revision: 543125 URL: http://svn.apache.org/viewvc?view=revrev=543125 Log: SM-959 ssl truststore is not set for unmanaged Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JettyContextManager.java ssl truststore is not set for unmanaged --- Key: SM-959 URL: https://issues.apache.org/activemq/browse/SM-959 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.1 Reporter: Thomas Termin Assignee: Thomas Termin Fix For: 3.2 The truststore is not set for an unmanaged ssl connection as reported by David Potter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-959) ssl truststore is not set for unmanaged
ssl truststore is not set for unmanaged --- Key: SM-959 URL: https://issues.apache.org/activemq/browse/SM-959 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.1 Reporter: Thomas Termin Assignee: Thomas Termin Fix For: 3.2 The truststore is not set for an unmanaged ssl connection as reported by David Potter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ServiceMix 3.1.1 (2nd try)
+1 Guillaume Nodet wrote: I have uploaded a version of ServiceMix 3.1.1 in the standard repo for you to review. See http://incubator.apache.org/servicemix/servicemix-311.html for the future download page and release notes (these are also included in the distribution). The distribution have been uploaded to http://people.apache.org/~gnodet/servicemix-3.1.1-incubating/org/apache/servicemix/apache-servicemix/3.1.1-incubating/ I send this mail both to the dev list and [EMAIL PROTECTED], as a first vote has been conducted on the ServiceMix dev list and some issues have been fixed since that, so hopefully this one will be fine. [ ] +1 Release ServiceMix 3.1.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.1.1 The rat log is available at http://people.apache.org/~gnodet/rat-servicemix-3.1.1-incubating.txthttp://people.apache.org/%7Egnodet/rat-servicemix-3.1.1-incubating.txt Here's my +1 -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [VOTE] Release ServiceMix 3.1.1
+1 Guillaume Nodet wrote: I have uploaded a version of ServiceMix 3.1.1 in the standard repo for you to review. See http://incubator.apache.org/servicemix/servicemix-311.html for all the links and release notes. [ ] +1 Release ServiceMix 3.1.1 [ ] +/- 0 [ ] -1 Do not release ServiceMix 3.1.1 I will upload a rat report asap. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: [Fwd: WARNING - 2 days to deadline for May reports]
Like Guillaume said: Sounds good. Thanks Gert! Cheers, Thomas Gert Vanthienen wrote: L.S., I have written a summary about what's been going on with ServiceMix in the last few months on the wiki page that was mentioned in the original mail. I hope that is OK... Can someone take a look to ensure that I've added the correct information in the report? Regards, Gert Gert Vanthienen wrote: Guillaume, What exactly is it that needs to be done? Can I help out with it? Gert Guillaume Nodet wrote: Anybody want to take a look at this ? Subject: WARNING - 2 days to deadline for May reports From: William A. Rowe, Jr. [EMAIL PROTECTED] Date: Mon, 07 May 2007 22:02:00 -0500 To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Well this sort of sucks - with everyone so busy at ApacheCon EU, we've neglected to remind you of the deadline on the 9th (posted months ago) for http://wiki.apache.org/incubator/May2007 Abdera Lokahi NMaven RCF ServiceMix stdcxx Tika TSIK Tuscany Woden WSRP4J XAP Yoko must report. PLEASE rush to get this done, so we have time to review the reports and get them to the board. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: jms:endpoint role=consumer versus jms:consumer
Gert, I guess the latter. Look at SM-537. This is also available for http but not yet finished. Cheers, Thomas Gert Vanthienen wrote: L.S., While I was trying to get automatic reconnect to a JMS broker (WebSphere MQ which is restarted at least once per week) up and running with jms:endpoint role=consumer/, I noticed the possibility of using jms:consumer / to specify JMS message receiving into the ESB. The jms:consumer / uses Spring's DefaultMessageListenerContainer class, which provides the auto-reconnect behavior I was looking for. My question: why isn't this syntax specified in any of the docs or used in any of the archetypes? Is the jms:consumer / deprecated or is the documentation incomplete? Regards, Gert -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Updated: (SM-934) change checkstyle line length to 140
[ https://issues.apache.org/activemq/browse/SM-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin updated SM-934: - Fix Version/s: 3.2 change checkstyle line length to 140 Key: SM-934 URL: https://issues.apache.org/activemq/browse/SM-934 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial Fix For: 3.2 change line length in smx-checkstyle.xml to 140 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-876) jmx.xml should use the jmx.url property
[ https://issues.apache.org/activemq/browse/SM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin updated SM-876: - Component/s: servicemix-core Affects Version/s: 3.1.1 Fix Version/s: 3.1.1 jmx.xml should use the jmx.url property --- Key: SM-876 URL: https://issues.apache.org/activemq/browse/SM-876 Project: ServiceMix Issue Type: Improvement Components: servicemix-core Affects Versions: 3.1.1 Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial Fix For: 3.1.1 Attachments: patch.jmx.xml Just a small patch. ;-) The jmx.xml should specify the jmx.url from servicemix.properties. Furthermore the hostname should be configurable. (Very nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-904) The jmx url is wrong if there are spaces at the end of the properties
[ https://issues.apache.org/activemq/browse/SM-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin updated SM-904: - Affects Version/s: 3.1.1 Fix Version/s: 3.1.1 The jmx url is wrong if there are spaces at the end of the properties - Key: SM-904 URL: https://issues.apache.org/activemq/browse/SM-904 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1.1 Reporter: Thomas Termin Assigned To: Thomas Termin Fix For: 3.1.1 The jmx.url string is wrong if the properties in servicemix.properties have spaces at the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Resolved: (SM-795) HTTP headers attached as properties may cause requests to fail
Will do a backport for this. Thomas Termin (JIRA) wrote: [ https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-795. -- Resolution: Fixed Fix Version/s: 3.2 Fixed! But it is configurable over HttpConfiguration(what means you can change the behaviour via JMX as well as conf/component.properties) Author: tterm Date: Fri Apr 27 06:00:19 2007 New Revision: 533084 URL: http://svn.apache.org/viewvc?view=revrev=533084 Log: SM-795 HTTP headers attached as properties may cause requests to fail Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java HTTP headers attached as properties may cause requests to fail -- Key: SM-795 URL: https://issues.apache.org/activemq/browse/SM-795 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: W2KS, JDK1.5 Reporter: Maxim Y. Tebenev Assigned To: Thomas Termin Fix For: 3.2 Attachments: SM-795.patch When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP headers as message properties. When forwarding the message to another provider endpoint the properties goes as HTTP headers in request. For example, the following request to the second provider endpoint will have following headers: POST /DeliveryService/DeliveryService HTTP/1.1 Date: Wed, 27 Dec 2006 13:24:46 GMT Server: Apache-Coyote/1.1 Transfer-Encoding: chunked Content-Type: text/xml Content-Length: 359 SOAPAction: User-Agent: Jakarta Commons-HttpClient/3.0 Host: localhost:8082 Server, Date and Transfer-Encoding headers are illegal in client request and cause Apache Tomcat server to fail with 500 error. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39053 ] Thomas Termin commented on SM-932: -- Fixed for servicemix-http! Thanks a lot to Gert Vanthienen! Author: tterm Date: Fri Apr 27 05:23:20 2007 New Revision: 533074 URL: http://svn.apache.org/viewvc?view=revrev=533074 Log: SM-932 Enable PMD/CheckStyle for binding components Added: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/AbstractProcessor.java Removed: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/processors/Constants.java Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/BasicAuthCredentials.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpBootstrap.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpBridgeServlet.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpComponent.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfiguration.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpConfigurationMBean.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpManagedServlet.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpProcessor.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/HttpWsdl1Deployer.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ManagedContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/ProxyParameters.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/SslParameters.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/DefaultHttpProviderMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpConsumerEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpProviderMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpSoapConsumerEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/HttpSoapConsumerMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/endpoints/SerializedMarshaler.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JCLLogger.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JaasJettyPrincipal.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JaasUserRealm.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/JettyContextManager.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src/main/java/org/apache/servicemix/http/jetty/ServiceMixSslSocketConnector.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-http/src
Re: [ANNOUNCE] Welcome Gert Vanthienen as our newest committer
Guillaume Nodet wrote: Gert has accepted the PPMC invitation to become a committer on ServiceMix. Congratulations and welcome aboard Gert ! Congratulations Gert! Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-932) Enable PMD/CheckStyle for binding components
[ https://issues.apache.org/activemq/browse/SM-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39046 ] Thomas Termin commented on SM-932: -- Gert, the http patch doesn't work. There is a class missing: AbstractProcessor. I guess you forgot to add this class to svn before you do the svn diff. Enable PMD/CheckStyle for binding components Key: SM-932 URL: https://issues.apache.org/activemq/browse/SM-932 Project: ServiceMix Issue Type: Task Components: servicemix-file, servicemix-ftp, servicemix-http, servicemix-jms, servicemix-truezip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-932-file.patch, SM-932-ftp.patch, SM-932-http.patch, SM-932-jms.patch, SM-932-truezip.patch, SM-932-xmpp.patch PMD/CheckStyle should be enabled for binding components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-606) Ability to customize http requests when acting as a client
[ https://issues.apache.org/activemq/browse/SM-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39043 ] Thomas Termin commented on SM-606: -- What is still to do here? There were some things done on this issue, right! Ability to customize http requests when acting as a client -- Key: SM-606 URL: https://issues.apache.org/activemq/browse/SM-606 Project: ServiceMix Issue Type: New Feature Components: servicemix-http Affects Versions: 3.0 Reporter: Guillaume Nodet We should be able to deactivate retries, configure timeouts, aso... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-795) HTTP headers attached as properties may cause requests to fail
[ https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reassigned SM-795: Assignee: Thomas Termin HTTP headers attached as properties may cause requests to fail -- Key: SM-795 URL: https://issues.apache.org/activemq/browse/SM-795 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: W2KS, JDK1.5 Reporter: Maxim Y. Tebenev Assigned To: Thomas Termin Attachments: SM-795.patch When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP headers as message properties. When forwarding the message to another provider endpoint the properties goes as HTTP headers in request. For example, the following request to the second provider endpoint will have following headers: POST /DeliveryService/DeliveryService HTTP/1.1 Date: Wed, 27 Dec 2006 13:24:46 GMT Server: Apache-Coyote/1.1 Transfer-Encoding: chunked Content-Type: text/xml Content-Length: 359 SOAPAction: User-Agent: Jakarta Commons-HttpClient/3.0 Host: localhost:8082 Server, Date and Transfer-Encoding headers are illegal in client request and cause Apache Tomcat server to fail with 500 error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-795) HTTP headers attached as properties may cause requests to fail
[ https://issues.apache.org/activemq/browse/SM-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-795 started by Thomas Termin. HTTP headers attached as properties may cause requests to fail -- Key: SM-795 URL: https://issues.apache.org/activemq/browse/SM-795 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: W2KS, JDK1.5 Reporter: Maxim Y. Tebenev Assigned To: Thomas Termin Attachments: SM-795.patch When SMX receives HTTP response from provider HTTP endpoint it attaches HTTP headers as message properties. When forwarding the message to another provider endpoint the properties goes as HTTP headers in request. For example, the following request to the second provider endpoint will have following headers: POST /DeliveryService/DeliveryService HTTP/1.1 Date: Wed, 27 Dec 2006 13:24:46 GMT Server: Apache-Coyote/1.1 Transfer-Encoding: chunked Content-Type: text/xml Content-Length: 359 SOAPAction: User-Agent: Jakarta Commons-HttpClient/3.0 Host: localhost:8082 Server, Date and Transfer-Encoding headers are illegal in client request and cause Apache Tomcat server to fail with 500 error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: antlib.xml in servicemix-core
Guillaume Nodet wrote: What about these files which is already included in the distribution ? http://svn.apache.org/repos/asf/incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/ant/ Isn't it the same thing ? Yeah this is the same thing. Thx. ;-) On 4/11/07, Thomas TERMIN [EMAIL PROTECTED] wrote: What do you think to package an antlib.xml file in servicemix-core so that the user can easily declare all jbi tasks like: typedef resource=org/apache/servicemix/jbi/management/task/antlib.xml uri=http://servicemix.apache.org/ant/1.0/ Otherwise the user has to declare a taskdef for each task. Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Created: (SM-934) change checkstyle line length to 140
change checkstyle line length to 140 Key: SM-934 URL: https://issues.apache.org/activemq/browse/SM-934 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial change line length in smx-checkstyle.xml to 140 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Checkstyle / PMD and recent commits
Gert,
I checked in the change of the line length to 140.
Thomas
Gert Vanthienen wrote:
Guillaume,
Just a few questions/remarks about the CheckStyle rules:
- a lot of the code seems to be written with a line length of 132 in
mind, why change it to 120?
- the rules don't allow using this way of creating setters
public void setMBeanServer(MBeanServer mbeanServer) {
this.mbeanServer = mbeanServer;
}
Regards,
Gert Vanthienen
Guillaume Nodet wrote:
Hi everybody !
I have recently checked in lots of changes. These are mostly
code conventions fixes. Let me explain.
I've started to add checkstyle and pmd checks at build time.
For those who do not know these tools, checkstyle
(http://checkstyle.sourceforge.net/) enforces
code conventions (braces, spaces, etc ...), while PMD
(http://pmd.sourceforge.net/) checks for possible bugs.
These tools are configured in the new parent module
which all other modules should inherit directly or indirectly
when they pass these checks (the buid fails if these checks
do not pass).
Currently, only the serviceengines module inherit from parent
so any help to migrate the other modules is welcome :-)
The goal is to have all modules (core, common, deployables mainly)
inherit from parent.
Btw, thanks to the CXF team which did that a few months ago,
and where I borrowed the configuration and all ...
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Resolved: (SM-934) change checkstyle line length to 140
[ https://issues.apache.org/activemq/browse/SM-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-934. -- Resolution: Fixed Author: tterm Date: Thu Apr 12 09:56:07 2007 New Revision: 528028 URL: http://svn.apache.org/viewvc?view=revrev=528028 Log: SM-934 change checkstyle line length to 140 Modified: incubator/servicemix/trunk/build/src/main/resources/smx-checkstyle.xml change checkstyle line length to 140 Key: SM-934 URL: https://issues.apache.org/activemq/browse/SM-934 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial change line length in smx-checkstyle.xml to 140 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-931) PMD/CheckStyle errors for servicemix-eip
[ https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38988 ] Thomas Termin commented on SM-931: -- Gert, I'm currently working on this but you were faster. :-) PMD/CheckStyle errors for servicemix-eip Key: SM-931 URL: https://issues.apache.org/activemq/browse/SM-931 Project: ServiceMix Issue Type: Bug Components: servicemix-eip Reporter: Gert Vanthienen Priority: Minor Attachments: SM-931.patch Build fails with PMD/CheckStyle enabled for servicemix-eip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SM-864) Configure jetty in the main configuration so that we can easily deploy web applications
[ https://issues.apache.org/activemq/browse/SM-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reassigned SM-864: Assignee: Thomas Termin Configure jetty in the main configuration so that we can easily deploy web applications --- Key: SM-864 URL: https://issues.apache.org/activemq/browse/SM-864 Project: ServiceMix Issue Type: New Feature Components: servicemix-assembly Reporter: Guillaume Nodet Assigned To: Thomas Termin Attachments: jetty.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-864) Configure jetty in the main configuration so that we can easily deploy web applications
[ https://issues.apache.org/activemq/browse/SM-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-864 started by Thomas Termin. Configure jetty in the main configuration so that we can easily deploy web applications --- Key: SM-864 URL: https://issues.apache.org/activemq/browse/SM-864 Project: ServiceMix Issue Type: New Feature Components: servicemix-assembly Reporter: Guillaume Nodet Assigned To: Thomas Termin Attachments: jetty.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-933) Enable PMD/CheckStyle for servicemix-core
Enable PMD/CheckStyle for servicemix-core - Key: SM-933 URL: https://issues.apache.org/activemq/browse/SM-933 Project: ServiceMix Issue Type: Task Components: servicemix-core Reporter: Thomas Termin Priority: Minor PMD/Checkstyle should be enabled for servicemix-core -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
antlib.xml in servicemix-core
What do you think to package an antlib.xml file in servicemix-core so that the user can easily declare all jbi tasks like: typedef resource=org/apache/servicemix/jbi/management/task/antlib.xml uri=http://servicemix.apache.org/ant/1.0/ Otherwise the user has to declare a taskdef for each task. Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Created: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter -- Key: SM-929 URL: https://issues.apache.org/activemq/browse/SM-929 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor Fix For: 3.2 This switch predicate can be used to easily switch on/off an exchange flow. This might be interessting for environments where you have different things installed. With an property file or an exchange property can you switch the behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
[ https://issues.apache.org/activemq/browse/SM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-929 started by Thomas Termin. eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter -- Key: SM-929 URL: https://issues.apache.org/activemq/browse/SM-929 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor Fix For: 3.2 This switch predicate can be used to easily switch on/off an exchange flow. This might be interessting for environments where you have different things installed. With an property file or an exchange property can you switch the behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-929) eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter
[ https://issues.apache.org/activemq/browse/SM-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-929. -- Resolution: Fixed Author: tterm Date: Tue Apr 10 09:58:29 2007 New Revision: 527197 URL: http://svn.apache.org/viewvc?view=revrev=527197 Log: SM-929 eip message filter switch predicate where you can easily turn on/off the exchange flow in a message filter depending on a property Added: incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/main/java/org/apache/servicemix/eip/support/SwitchPredicate.java eip message filter switch predicate where you can easily turn on/off the exchange flow depending on a property in a message filter -- Key: SM-929 URL: https://issues.apache.org/activemq/browse/SM-929 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor Fix For: 3.2 This switch predicate can be used to easily switch on/off an exchange flow. This might be interessting for environments where you have different things installed. With an property file or an exchange property can you switch the behaviour. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Access to JNDI Resources by java code
What you mean is that: getContext().getNamingContext() should work and is also the better way if it is inside of a component. I read the mail to fast I guess. What also works inside the same vm is just: new InitialContext() Cheers, Thomas Guillaume Nodet wrote: I don't really see why one has to specify these properties, at least when inside ServiceMix standalone, or when using the InitialContext retreived from the ComponentContext. Any idea ? On 4/4/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Andrea Zoppello wrote: Hi to all I'm asking if there's a way to access Jndi resources (defined in jndi.xml ) in the java code of a component/endpoint??? That should work. private String jndiInitialContextFactory = org.apache.xbean.spring.jndi.SpringInitialContextFactory; private String jndiProviderUrl = classpath:jndi.xml; Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, this.jndiInitialContextFactory); env.put(Context.PROVIDER_URL, jndiProviderUrl); Context ctx = new InitialContext(env); Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: Access to JNDI Resources by java code
I've corrected this. :-) Thomas TERMIN wrote: What you mean is that: getContext().getNamingContext() should work and is also the better way if it is inside of a component. I read the mail to fast I guess. What also works inside the same vm is just: new InitialContext() Cheers, Thomas Guillaume Nodet wrote: I don't really see why one has to specify these properties, at least when inside ServiceMix standalone, or when using the InitialContext retreived from the ComponentContext. Any idea ? On 4/4/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Andrea Zoppello wrote: Hi to all I'm asking if there's a way to access Jndi resources (defined in jndi.xml ) in the java code of a component/endpoint??? That should work. private String jndiInitialContextFactory = org.apache.xbean.spring.jndi.SpringInitialContextFactory; private String jndiProviderUrl = classpath:jndi.xml; Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, this.jndiInitialContextFactory); env.put(Context.PROVIDER_URL, jndiProviderUrl); Context ctx = new InitialContext(env); Cheers, Thomas -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
[jira] Commented: (SM-904) The jmx url is wrong if there are spaces at the end of the properties
[ https://issues.apache.org/activemq/browse/SM-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38947 ] Thomas Termin commented on SM-904: -- Backport to 3.1 branch Author: tterm Date: Tue Apr 3 05:01:41 2007 New Revision: 525144 URL: http://svn.apache.org/viewvc?view=revrev=525144 Log: SM-904 The jmx url is wrong if there are spaces at the end of the properties Modified: incubator/servicemix/branches/servicemix-3.1/core/servicemix-core/src/main/java/org/apache/servicemix/jbi/jmx/ConnectorServerFactoryBean.java The jmx url is wrong if there are spaces at the end of the properties - Key: SM-904 URL: https://issues.apache.org/activemq/browse/SM-904 Project: ServiceMix Issue Type: Bug Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin The jmx.url string is wrong if the properties in servicemix.properties have spaces at the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-904) The jmx url is wrong if there are spaces at the end of the properties
The jmx url is wrong if there are spaces at the end of the properties - Key: SM-904 URL: https://issues.apache.org/activemq/browse/SM-904 Project: ServiceMix Issue Type: Bug Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin The jmx.url string is wrong if the properties in servicemix.properties have spaces at the end. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-906) extend ComponentSupport with methods to propagate the correlation id
extend ComponentSupport with methods to propagate the correlation id Key: SM-906 URL: https://issues.apache.org/activemq/browse/SM-906 Project: ServiceMix Issue Type: Improvement Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor extends ComponentSupport that it has methods for creating exchanges with propagating the correlation id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-906) extend ComponentSupport with methods to propagate the correlation id
[ https://issues.apache.org/activemq/browse/SM-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-906. -- Resolution: Fixed Author: tterm Date: Thu Mar 29 07:43:43 2007 New Revision: 523729 URL: http://svn.apache.org/viewvc?view=revrev=523729 Log: SM-906 extend ComponentSupport with methods to propagate the correlation id Modified: incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/components/util/ComponentSupport.java extend ComponentSupport with methods to propagate the correlation id Key: SM-906 URL: https://issues.apache.org/activemq/browse/SM-906 Project: ServiceMix Issue Type: Improvement Components: servicemix-core Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Minor extends ComponentSupport that it has methods for creating exchanges with propagating the correlation id -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-905) message filter registers predicates as mbean as well as a new predicate for on/off filtering
message filter registers predicates as mbean as well as a new predicate for on/off filtering Key: SM-905 URL: https://issues.apache.org/activemq/browse/SM-905 Project: ServiceMix Issue Type: New Feature Components: servicemix-eip Reporter: Thomas Termin Priority: Minor Attachments: eip-message-filter.patch Predicat MBeans are registered exactly as the endpoint just with the extension Predicate Interessting is the message filter which do all with reflection and just register predicates if an MBean interface is implemented. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Switching trunk to full java 5 ?
Guillaume Nodet wrote: Most of our components uses java 5 now. The container itself works on JDK 1.4 with some minor modifications (see http://issues.apache.org/activemq/browse/SM-848) but i think it would be easier to officially switch to JDK 5 for everything Thoughts ? I fully agree with you. ;-)
[jira] Work started: (SM-876) jmx.xml should use the jmx.url property
[ https://issues.apache.org/activemq/browse/SM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SM-876 started by Thomas Termin. jmx.xml should use the jmx.url property --- Key: SM-876 URL: https://issues.apache.org/activemq/browse/SM-876 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial Attachments: patch.jmx.xml Just a small patch. ;-) The jmx.xml should specify the jmx.url from servicemix.properties. Furthermore the hostname should be configurable. (Very nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-876) jmx.xml should use the jmx.url property
[ https://issues.apache.org/activemq/browse/SM-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-876. -- Resolution: Fixed Date: Wed Mar 28 08:01:33 2007 New Revision: 523355 URL: http://svn.apache.org/viewvc?view=revrev=523355 Log: SM-876 jmx.xml should use the jmx.url property from servicemix.properties Modified: incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/jmx.xml incubator/servicemix/trunk/distributions/apache-servicemix/src/main/release/conf/servicemix.properties jmx.xml should use the jmx.url property --- Key: SM-876 URL: https://issues.apache.org/activemq/browse/SM-876 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Assigned To: Thomas Termin Priority: Trivial Attachments: patch.jmx.xml Just a small patch. ;-) The jmx.xml should specify the jmx.url from servicemix.properties. Furthermore the hostname should be configurable. (Very nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: correlation id with tracing
Guillaume, I extended component support so that we have the four methods with the MessageExchange parameter to get and set the correlation id. public InOnly createInOnlyExchange(MessageExchange beforeExchange) public InOptionalOut createInOptionalOutExchange(MessageExchange beforeExchange) public InOut createInOutExchange(MessageExchange beforeExchange) public RobustInOnly createRobustInOnlyExchange(MessageExchange beforeExchange) this are the corresponding methods to the four methods without parameters to create a new excahnge. Do you want to create corresponding methods to the other methods like public InOut createInOutExchange(QName service, QName interfaceName, QName operation) Cheers, Thomas Thomas TERMIN wrote: Is there a JIRA for that ? No not yet. I will create one. Do you want to implement this or should I do it? On 3/7/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: However, it might be possible to enhance the ComponentSupport or another class to support the correlation id automatically. This would make all lightweight components to support that. We could extend ComponentSupport with methods to create the new exchanges and this methods could put the correlation id automatically in the new excahnge. So if you would use ComponentSupport to create the exchange the correlationId will be propagated. The advantage is that you don't have to use this functions and it would be backward compatible. What do you think? On 1/23/07, Guillaume Nodet [EMAIL PROTECTED] wrote: I don't think so, as the container (or the ecxhange factory) has no way to know which jbi exchange is currently handled by the component. And you can not use a thread local, has the component may delegate the exhcange processing to another thread. That's the reason why it has been implemented in servicemix-common. Do you see something else ? On 1/23/07, Thomas TERMIN [EMAIL PROTECTED] wrote: A question again. If I have a lw component which opens a new message exchange the correlation id has to be propageted in the component itself. Would it be better or is it possible to do this automaticaly in the exchange factory? Cheers, Thomas Guillaume Nodet wrote: The way it works now is that all components using servicemix-common that create an exchange as part of the processing of a received exchange, will automatically put the correlationId in the new exchange properties. The correlationId is equal to correlationId of the input exchange, or the input exchange id if no correlation id is set. So if an endpoint A sends a JBI exchange to enpoint B, and endpoint B sends a jbi exchange to endpoint C while processing the exchange, both exchange will have the same correlationId. If we write a MessageExchange event listener, we should be able to retrieve all these informations. Note that the flow can be retrieved with the same logic used in the DotViewFlowListener instead. Just copy the DotViewFlowListener and change the drawing logic. What tool are will you use to draw the flow ? The output of the DotViewFlowListener is not very impressive, so any improvement would be welcome. On 1/10/07, Thomas TERMIN [EMAIL PROTECTED] wrote: How is this intended to work? I want to implement a tracing tool or whatever to see the flows between the components. Cheers Guillaume Nodet wrote: No one leverage the correlation ids, but i it could / should be done. What kind of informations are you looking for ? On 1/10/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello, How can I enable tracing in servicemix with the new correlation id mechanism. How do I have to use this? (I don't want to use the DotViewFlowListener) Cheers, Thomas -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: correlation id with tracing
I extended component support so that we have the four methods with the MessageExchange parameter to get and set the correlation id. public InOnly createInOnlyExchange(MessageExchange beforeExchange) public InOptionalOut createInOptionalOutExchange(MessageExchange beforeExchange) public InOut createInOutExchange(MessageExchange beforeExchange) public RobustInOnly createRobustInOnlyExchange(MessageExchange beforeExchange) this are the corresponding methods to the four methods without parameters to create a new excahnge. Cool, thx :-) Do you want to create corresponding methods to the other methods like public InOut createInOutExchange(QName service, QName interfaceName, QName operation) What about adding a helper method to progate / create the correlation id. create correlation id means (if correlation id == null) get the exchange id from the source exchange, right? public void propagateCorrelationId(MessageExchange source, MessageExchange dest); This method could be used by the four methods you've written, and could be called if the component use other methods. Hopefully your account will be created soon. I have sent a reminder, but I can't do much :-( Cheers, Thomas Thomas TERMIN wrote: Is there a JIRA for that ? No not yet. I will create one. Do you want to implement this or should I do it? On 3/7/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: However, it might be possible to enhance the ComponentSupport or another class to support the correlation id automatically. This would make all lightweight components to support that. We could extend ComponentSupport with methods to create the new exchanges and this methods could put the correlation id automatically in the new excahnge. So if you would use ComponentSupport to create the exchange the correlationId will be propagated. The advantage is that you don't have to use this functions and it would be backward compatible. What do you think? On 1/23/07, Guillaume Nodet [EMAIL PROTECTED] wrote: I don't think so, as the container (or the ecxhange factory) has no way to know which jbi exchange is currently handled by the component. And you can not use a thread local, has the component may delegate the exhcange processing to another thread. That's the reason why it has been implemented in servicemix-common. Do you see something else ? On 1/23/07, Thomas TERMIN [EMAIL PROTECTED] wrote: A question again. If I have a lw component which opens a new message exchange the correlation id has to be propageted in the component itself. Would it be better or is it possible to do this automaticaly in the exchange factory? Cheers, Thomas Guillaume Nodet wrote: The way it works now is that all components using servicemix-common that create an exchange as part of the processing of a received exchange, will automatically put the correlationId in the new exchange properties. The correlationId is equal to correlationId of the input exchange, or the input exchange id if no correlation id is set. So if an endpoint A sends a JBI exchange to enpoint B, and endpoint B sends a jbi exchange to endpoint C while processing the exchange, both exchange will have the same correlationId. If we write a MessageExchange event listener, we should be able to retrieve all these informations. Note that the flow can be retrieved with the same logic used in the DotViewFlowListener instead. Just copy the DotViewFlowListener and change the drawing logic. What tool are will you use to draw the flow ? The output of the DotViewFlowListener is not very impressive, so any improvement would be welcome. On 1/10/07, Thomas TERMIN [EMAIL PROTECTED] wrote: How is this intended to work? I want to implement a tracing tool or whatever to see the flows between the components. Cheers Guillaume Nodet wrote: No one leverage the correlation ids, but i it could / should be done. What kind of informations are you looking for ? On 1/10/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello, How can I enable tracing in servicemix with the new correlation id mechanism. How do I have to use this? (I don't want to use the DotViewFlowListener) Cheers, Thomas -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim
Re: eip filter extension
Guillaume Nodet wrote:
Yeah, it should work. Even if not embedded in servicemix,
though I would prefer to avoid hard dependencies on internal
classes. The other solution is to do it with reflection, as done
in AsyncBaseLifeCycle#findExecutorFactory
If you can try to hide this hideous cast in a common parent class,
that would be fine ;-)
So I did the complete stuff with reflection. It would be nice if you
would have a look at the code.
On 3/15/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume,
can I do this?
if (isComponentContextImpl(getContext().getMBeanNames()))
{
ComponentContextImpl contextImpl
=(ComponentContextImpl)getContext().getMBeanNames();
}
or is it to dirty? I would have all information then. ;-)
Guillaume Nodet wrote:
Well, i think it will be difficult without accessing
ServiceMix internals.
Or maybe tweaking with the mbean names factory
available on the component context ? I don't recall what it gives ...
On 3/14/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume Nodet wrote:
Yeah, sounds good.
Make sure you use the facilities available on
the ComponentContext to create the mbean names ...
Do you have special vision there? What I thought is to have it under
the
Type=Endpoint,SubType=Internal or External. But it seems not so easy.
If the mbean name for this interface could be related
to the endpoint name, that would make it easier to find.
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume Nodet wrote:
I mean, did you already implement the JMX part ?
Which interface are you exposing to JMX ?
Anyway, you should raise a JIRA ...
I didn't implemtet it up to now. But what I want to do is expose an
SwitchPredicateMBean interface where you can change some
properties.
What do you think. This could also be done for the XpathPredicate
and
so
on. I have implemented the SwitchPredicate and doing tests at the
moment.
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Yes of course should also be changeable via JMX.
Guillaume Nodet wrote:
Well, it sounds good.
What about the JMX stuff ?
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED]
wrote:
Guillaume Nodet wrote:
On 3/12/07, Thomas TERMIN [EMAIL PROTECTED]
wrote:
Peter my colleague asked if you need a switch-filter as an
EIP
component. It does nothing more then check a property
for
message
flow.
If this property is true it sends the message to the
destination
and
if
it is false the exchange will be discarde. This is
helpfull
if
you
have
different installations where some services are
installed or
not
installed in servicemix. What he want to do is that you
can
enable or
disbale the flow via JMX as well as an property in a
property
file at
runtime. (Hope the explanation was understandable)
Sounds good, but I wonder wha's the difference with the
http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter
.
We only need to implement a new predicate based on
properties,
which
could
be
reused by the router for example. I'm not sure if this is
what
you
meant
or not
(maybe you were talking about a system property ?)
As for the JMX stuff, it's a very good idea.
I'm still not sure if you were talking about a property on
the
JBI
exchange
or a system property. There's no predicate on message
properties
it
could be implemented easily (and should anyway). As I
said,
JMX
controlled
routers or filters would be very useful for manually
re-routing
flows,
etc
This filter is intended just as a on/off filter.
eip:filter
eip:property-predicate
propertyResource=file:conf/feature.properties
propertyName=on/
/eip:filter
So as you can see above there is a spring resourece defined
and a
property name. This property name will be read from the
resource
and
can
have the value true(on) or false(off). The property could
also
be an
exchange property. The configuration would be:
eip:filter
eip:property-predicate fromExchange=true
propertyName=on/
/eip:filter
We implemented this just as a SwitchPredicate which just
returns
true
or
false depending on the property.
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems
can't build servicemix
I can't build servicemix at the moment. [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.servicemix ArtifactId: servicemix-wsn2005 Version: 3.2-incubating-20070316.093011-18 Reason: Unable to locate resource in repository What can I do? Cheers, Thomas
Re: eip filter extension
Guillaume,
can I do this?
if (isComponentContextImpl(getContext().getMBeanNames()))
{
ComponentContextImpl contextImpl
=(ComponentContextImpl)getContext().getMBeanNames();
}
or is it to dirty? I would have all information then. ;-)
Guillaume Nodet wrote:
Well, i think it will be difficult without accessing
ServiceMix internals.
Or maybe tweaking with the mbean names factory
available on the component context ? I don't recall what it gives ...
On 3/14/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume Nodet wrote:
Yeah, sounds good.
Make sure you use the facilities available on
the ComponentContext to create the mbean names ...
Do you have special vision there? What I thought is to have it under the
Type=Endpoint,SubType=Internal or External. But it seems not so easy.
If the mbean name for this interface could be related
to the endpoint name, that would make it easier to find.
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume Nodet wrote:
I mean, did you already implement the JMX part ?
Which interface are you exposing to JMX ?
Anyway, you should raise a JIRA ...
I didn't implemtet it up to now. But what I want to do is expose an
SwitchPredicateMBean interface where you can change some properties.
What do you think. This could also be done for the XpathPredicate and
so
on. I have implemented the SwitchPredicate and doing tests at the
moment.
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Yes of course should also be changeable via JMX.
Guillaume Nodet wrote:
Well, it sounds good.
What about the JMX stuff ?
On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote:
Guillaume Nodet wrote:
On 3/12/07, Thomas TERMIN [EMAIL PROTECTED]
wrote:
Peter my colleague asked if you need a switch-filter as an
EIP
component. It does nothing more then check a property for
message
flow.
If this property is true it sends the message to the
destination
and
if
it is false the exchange will be discarde. This is helpfull
if
you
have
different installations where some services are
installed or
not
installed in servicemix. What he want to do is that you can
enable or
disbale the flow via JMX as well as an property in a
property
file at
runtime. (Hope the explanation was understandable)
Sounds good, but I wonder wha's the difference with the
http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter
.
We only need to implement a new predicate based on
properties,
which
could
be
reused by the router for example. I'm not sure if this is
what
you
meant
or not
(maybe you were talking about a system property ?)
As for the JMX stuff, it's a very good idea.
I'm still not sure if you were talking about a property on
the
JBI
exchange
or a system property. There's no predicate on message
properties
it
could be implemented easily (and should anyway). As I said,
JMX
controlled
routers or filters would be very useful for manually
re-routing
flows,
etc
This filter is intended just as a on/off filter.
eip:filter
eip:property-predicate
propertyResource=file:conf/feature.properties
propertyName=on/
/eip:filter
So as you can see above there is a spring resourece defined
and a
property name. This property name will be read from the resource
and
can
have the value true(on) or false(off). The property could also
be an
exchange property. The configuration would be:
eip:filter
eip:property-predicate fromExchange=true
propertyName=on/
/eip:filter
We implemented this just as a SwitchPredicate which just returns
true
or
false depending on the property.
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim
servicemix.properties
Which class is reading the servicemix.properties file? If you have some spaces after a property the jmx.url is then also with spaces and that doesn't work.
Re: RE : servicemix.properties
Guillaume Nodet wrote:
This property is used to configure the
org.apache.servicemix.jbi.jmx.ConnectorServerFactoryBean
so I gess this class could be improved to trim the url before
using it.
Thomas, you can fix it, once your account is activated.
Ok. That's what I mean. ;-)
On 3/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hello,
Spring framework reads this file to provide all
properties into servicemix.xml file
please see @servicemix.xml:
bean id=propertyConfigurer
class=
org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=location
value=classpath:servicemix.properties /
/bean
You can use all properties from servicemix.properties
in your servicemix.xml file. For example
${activemq.url} property.
i hope it is could help you.
Cordialement,
--- Thomas TERMIN [EMAIL PROTECTED] a
écrit :
Which class is reading the servicemix.properties
file? If you have some
spaces after a property the jmx.url is then also
with spaces and that
doesn't work.
___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos
questions
!
Profitez des connaissances, des opinions et des expériences des
internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
--
Thomas Termin
___
blue elephant systems GmbH
Wollgrasweg 49
D-70599 Stuttgart
Tel: (+49) 0711 - 45 10 17 676
Fax: (+49) 0711 - 45 10 17 573
WWW: http://www.blue-elephant-systems.com
Email : [EMAIL PROTECTED]
blue elephant systems GmbH
Firmensitz : Wollgrasweg 49, D-70599 Stuttgart
Registergericht : Amtsgericht Stuttgart, HRB 24106
Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: eip filter extension
Guillaume Nodet wrote: Yeah, sounds good. Make sure you use the facilities available on the ComponentContext to create the mbean names ... Do you have special vision there? What I thought is to have it under the Type=Endpoint,SubType=Internal or External. But it seems not so easy. If the mbean name for this interface could be related to the endpoint name, that would make it easier to find. On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: I mean, did you already implement the JMX part ? Which interface are you exposing to JMX ? Anyway, you should raise a JIRA ... I didn't implemtet it up to now. But what I want to do is expose an SwitchPredicateMBean interface where you can change some properties. What do you think. This could also be done for the XpathPredicate and so on. I have implemented the SwitchPredicate and doing tests at the moment. On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Yes of course should also be changeable via JMX. Guillaume Nodet wrote: Well, it sounds good. What about the JMX stuff ? On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: On 3/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Peter my colleague asked if you need a switch-filter as an EIP component. It does nothing more then check a property for message flow. If this property is true it sends the message to the destination and if it is false the exchange will be discarde. This is helpfull if you have different installations where some services are installed or not installed in servicemix. What he want to do is that you can enable or disbale the flow via JMX as well as an property in a property file at runtime. (Hope the explanation was understandable) Sounds good, but I wonder wha's the difference with the http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter . We only need to implement a new predicate based on properties, which could be reused by the router for example. I'm not sure if this is what you meant or not (maybe you were talking about a system property ?) As for the JMX stuff, it's a very good idea. I'm still not sure if you were talking about a property on the JBI exchange or a system property. There's no predicate on message properties it could be implemented easily (and should anyway). As I said, JMX controlled routers or filters would be very useful for manually re-routing flows, etc This filter is intended just as a on/off filter. eip:filter eip:property-predicate propertyResource=file:conf/feature.properties propertyName=on/ /eip:filter So as you can see above there is a spring resourece defined and a property name. This property name will be read from the resource and can have the value true(on) or false(off). The property could also be an exchange property. The configuration would be: eip:filter eip:property-predicate fromExchange=true propertyName=on/ /eip:filter We implemented this just as a SwitchPredicate which just returns true or false depending on the property. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: eip filter extension
Guillaume Nodet wrote: On 3/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Peter my colleague asked if you need a switch-filter as an EIP component. It does nothing more then check a property for message flow. If this property is true it sends the message to the destination and if it is false the exchange will be discarde. This is helpfull if you have different installations where some services are installed or not installed in servicemix. What he want to do is that you can enable or disbale the flow via JMX as well as an property in a property file at runtime. (Hope the explanation was understandable) Sounds good, but I wonder wha's the difference with the http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter . We only need to implement a new predicate based on properties, which could be reused by the router for example. I'm not sure if this is what you meant or not (maybe you were talking about a system property ?) As for the JMX stuff, it's a very good idea. I'm still not sure if you were talking about a property on the JBI exchange or a system property. There's no predicate on message properties it could be implemented easily (and should anyway). As I said, JMX controlled routers or filters would be very useful for manually re-routing flows, etc This filter is intended just as a on/off filter. eip:filter eip:property-predicate propertyResource=file:conf/feature.properties propertyName=on/ /eip:filter So as you can see above there is a spring resourece defined and a property name. This property name will be read from the resource and can have the value true(on) or false(off). The property could also be an exchange property. The configuration would be: eip:filter eip:property-predicate fromExchange=true propertyName=on/ /eip:filter We implemented this just as a SwitchPredicate which just returns true or false depending on the property.
Re: eip filter extension
Yes of course should also be changeable via JMX. Guillaume Nodet wrote: Well, it sounds good. What about the JMX stuff ? On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: On 3/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Peter my colleague asked if you need a switch-filter as an EIP component. It does nothing more then check a property for message flow. If this property is true it sends the message to the destination and if it is false the exchange will be discarde. This is helpfull if you have different installations where some services are installed or not installed in servicemix. What he want to do is that you can enable or disbale the flow via JMX as well as an property in a property file at runtime. (Hope the explanation was understandable) Sounds good, but I wonder wha's the difference with the http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter . We only need to implement a new predicate based on properties, which could be reused by the router for example. I'm not sure if this is what you meant or not (maybe you were talking about a system property ?) As for the JMX stuff, it's a very good idea. I'm still not sure if you were talking about a property on the JBI exchange or a system property. There's no predicate on message properties it could be implemented easily (and should anyway). As I said, JMX controlled routers or filters would be very useful for manually re-routing flows, etc This filter is intended just as a on/off filter. eip:filter eip:property-predicate propertyResource=file:conf/feature.properties propertyName=on/ /eip:filter So as you can see above there is a spring resourece defined and a property name. This property name will be read from the resource and can have the value true(on) or false(off). The property could also be an exchange property. The configuration would be: eip:filter eip:property-predicate fromExchange=true propertyName=on/ /eip:filter We implemented this just as a SwitchPredicate which just returns true or false depending on the property. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
Re: eip filter extension
Guillaume Nodet wrote: I mean, did you already implement the JMX part ? Which interface are you exposing to JMX ? Anyway, you should raise a JIRA ... I didn't implemtet it up to now. But what I want to do is expose an SwitchPredicateMBean interface where you can change some properties. What do you think. This could also be done for the XpathPredicate and so on. I have implemented the SwitchPredicate and doing tests at the moment. On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Yes of course should also be changeable via JMX. Guillaume Nodet wrote: Well, it sounds good. What about the JMX stuff ? On 3/13/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Guillaume Nodet wrote: On 3/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Peter my colleague asked if you need a switch-filter as an EIP component. It does nothing more then check a property for message flow. If this property is true it sends the message to the destination and if it is false the exchange will be discarde. This is helpfull if you have different installations where some services are installed or not installed in servicemix. What he want to do is that you can enable or disbale the flow via JMX as well as an property in a property file at runtime. (Hope the explanation was understandable) Sounds good, but I wonder wha's the difference with the http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter . We only need to implement a new predicate based on properties, which could be reused by the router for example. I'm not sure if this is what you meant or not (maybe you were talking about a system property ?) As for the JMX stuff, it's a very good idea. I'm still not sure if you were talking about a property on the JBI exchange or a system property. There's no predicate on message properties it could be implemented easily (and should anyway). As I said, JMX controlled routers or filters would be very useful for manually re-routing flows, etc This filter is intended just as a on/off filter. eip:filter eip:property-predicate propertyResource=file:conf/feature.properties propertyName=on/ /eip:filter So as you can see above there is a spring resourece defined and a property name. This property name will be read from the resource and can have the value true(on) or false(off). The property could also be an exchange property. The configuration would be: eip:filter eip:property-predicate fromExchange=true propertyName=on/ /eip:filter We implemented this just as a SwitchPredicate which just returns true or false depending on the property. -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
eip filter extension
---BeginMessage--- On 3/12/07, Thomas TERMIN [EMAIL PROTECTED] wrote: Hello Guillaume, did you see my small patch in JIRA? Yeah, thx. The next days I will provide the patch for ComponentSupport related to the correlationID. I couln't make it up to now. Cool :-) Peter my colleague asked if you need a switch-filter as an EIP component. It does nothing more then check a property for message flow. If this property is true it sends the message to the destination and if it is false the exchange will be discarde. This is helpfull if you have different installations where some services are installed or not installed in servicemix. What he want to do is that you can enable or disbale the flow via JMX as well as an property in a property file at runtime. (Hope the explanation was understandable) Sounds good, but I wonder wha's the difference with the http://incubator.apache.org/servicemix/servicemix-eip.html#servicemix-eip-MessageFilter . We only need to implement a new predicate based on properties, which could be reused by the router for example. I'm not sure if this is what you meant or not (maybe you were talking about a system property ?) As for the JMX stuff, it's a very good idea. I will also look in this embedded jetty stuff the next days. Thanks ... Btw, unless there is something confidential, such discussion should take place on the dev list ... If you could forward this mail there ... ;-) Cheers, Thomas Guillaume Nodet wrote: Thanks a lot ! On 3/9/07, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello Guillaume, I faxed this CLA to apache. Cheers, Thomas -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/ http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ ---End Message---
[jira] Created: (SM-876) jmx.xml should use the jmx.url property
jmx.xml should use the jmx.url property --- Key: SM-876 URL: https://issues.apache.org/activemq/browse/SM-876 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin Priority: Trivial Attachments: patch.jmx.xml Just a small patch. ;-) The jmx.xml should specify the jmx.url from servicemix.properties. Furthermore the hostname should be configurable. (Very nice for us) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] [PROPOSAL] Coding standards
Is there also an code formatting setup for idea available? Would be nice. Juergen Mayrbaeurl wrote: OK for me. Can anyone provide an Eclipse code formatting setup? Kind regards Juergen gnodet wrote: I propose the following coding standards (taken from the Geronimo web site) which are actually the most common in ServiceMix code base: http://cwiki.apache.org/SM/coding-standards.html Does anyone want to modify / add / change something ? -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/ -- Thomas Termin ___ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel: (+49) 0711 - 45 10 17 676 Fax: (+49) 0711 - 45 10 17 573 WWW: http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 Geschäftsführer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle
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 :-)
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
[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
Re: log4j
So I implemted it. It works fine until now. I still have to do some improvements on it but I guess I can provide it to you tomorrow. Cheers, Thomas Thomas TERMIN wrote: I found it. ;-) I'm implementing at the moment the new service. 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
[jira] Created: (SM-746) JettyContextManager does not set the truststore parameters for unmanaged ssl endpoints
JettyContextManager does not set the truststore parameters for unmanaged ssl endpoints -- Key: SM-746 URL: https://issues.apache.org/activemq/browse/SM-746 Project: ServiceMix Issue Type: Bug Components: servicemix-http Affects Versions: 3.0, 3.0-M2, 3.0-M1, 3.0.1, 3.1, incubation Reporter: Thomas Termin Priority: Minor Attachments: jettyContextManager-Patch The sslParamters for the truststore environment are ignored in the JettyContextManager. If you use an unmanaged ssl consumer endpoint the values for the truststore are not set. The result is that the jre truststore is always used which is problematical for selfsigned certificates! You could set the java system properties in servicemix but that is not really a solution! -- 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-714) component.properties in conf directory
component.properties in conf directory -- Key: SM-714 URL: https://issues.apache.org/activemq/browse/SM-714 Project: ServiceMix Issue Type: Improvement Components: servicemix-http Reporter: Thomas Termin Attachments: component.properties, patch.txt There should be support for an initial component.properties file in the servicemix/conf directory. I added support for that (see the patch). The file in the conf directory will be loaded if no property file is in the workspace directory (I implemented that just for the servicemix-http component). If you change properties via JMX the changes will be saved in the workspace directory. The file in the conf directory has then still the original values. I added also a component.properties file. -- 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
