[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 fix for 3.2 Author: tterm Date: Thu Oct 4 05:39:05 2007 New Revision: 581878 URL: http://svn.apache.org/viewvc?rev=581878&view=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/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.
[jira] Commented: (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:comment-tabpanel#action_40260 ] Thomas Termin commented on SM-1084: --- fixed for 3.1.3 Author: tterm Date: Thu Oct 4 04:46:09 2007 New Revision: 581863 URL: http://svn.apache.org/viewvc?rev=581863&view=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/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.
[jira] Updated: (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 updated SM-1084: -- Component/s: servicemix-http Description: Make it configurable if the http content type will be used from the property of the normalized message or not Affects Version/s: 3.1.2 Fix Version/s: 3.2 3.1.3 Assignee: Thomas Termin Summary: make configurable if CONTENT-TYPE is used as property from the normalized message or not (was: make configurable if CONTENT_TP) > 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] Created: (SM-1084) make configurable if CONTENT_TP
make configurable if CONTENT_TP --- Key: SM-1084 URL: https://issues.apache.org/activemq/browse/SM-1084 Project: ServiceMix Issue Type: Improvement Reporter: Thomas Termin -- 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_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] 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] Updated: (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 updated SM-959: - Fix Version/s: 3.1.2 backport for 3.1 Author: tterm Date: Mon Jul 23 10:38:42 2007 New Revision: 558809 URL: http://svn.apache.org/viewvc?view=rev&rev=558809 Log: ssl truststore is not set for unmanaged Modified: incubator/servicemix/branches/servicemix-3.1/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.1.2, 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] 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.
[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.
[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=rev&rev=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] Work started: (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 ] Work on SM-959 started by Thomas Termin. > 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.
[jira] Updated: (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 updated SM-906: - Fix Version/s: 3.2 > 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 > Fix For: 3.2 > > > 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] 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.
[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-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] Commented: (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:comment-tabpanel#action_39097 ] Thomas Termin commented on SM-795: -- Backport to 3.1 branch Author: tterm Date: Wed May 2 10:07:28 2007 New Revision: 534549 URL: http://svn.apache.org/viewvc?view=rev&rev=534549 Log: SM-795 HTTP headers attached as properties may cause requests to fail 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/processors/ConsumerProcessor.java incubator/servicemix/branches/servicemix-3.1/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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 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=rev&rev=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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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] Assigned: (SM-933) Enable PMD/CheckStyle for servicemix-core
[ https://issues.apache.org/activemq/browse/SM-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reassigned SM-933: Assignee: Thomas Termin > 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 > Assigned To: 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.
[jira] Resolved: (SM-931) PMD/CheckStyle errors for servicemix-eip
[ https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin resolved SM-931. -- Resolution: Fixed Fix Version/s: 3.2 Author: tterm Date: Wed Apr 11 05:36:32 2007 New Revision: 527473 URL: http://svn.apache.org/viewvc?view=rev&rev=527473 Log: SM-931 PMD/CheckStyle errors for servicemix-eip Modified: incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/main/java/org/apache/servicemix/eip/support/SwitchPredicate.java > 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 > Assigned To: Thomas Termin >Priority: Minor > Fix For: 3.2 > > 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] 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] 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] Assigned: (SM-931) PMD/CheckStyle errors for servicemix-eip
[ https://issues.apache.org/activemq/browse/SM-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Termin reassigned SM-931: Assignee: Thomas Termin > 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 > Assigned To: Thomas Termin >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] 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] Commented: (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:comment-tabpanel#action_38948 ] Thomas Termin commented on SM-876: -- Backport to 3.1 branch Author: tterm Date: Tue Apr 3 04:36:04 2007 New Revision: 525140 URL: http://svn.apache.org/viewvc?view=rev&rev=525140 Log: SM-876 jmx.xml should use the jmx.url property from servicemix.properties Modified: incubator/servicemix/branches/servicemix-3.1/distributions/apache-servicemix/src/main/release/conf/jmx.xml incubator/servicemix/branches/servicemix-3.1/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.
[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=rev&rev=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] 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=rev&rev=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-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-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 resolved SM-904.
--
Resolution: Fixed
fixed with serviceUrl = serviceUrl.replaceAll(" ", "");
Author: tterm
Date: Thu Mar 29 01:28:39 2007
New Revision: 523618
URL: http://svn.apache.org/viewvc?view=rev&rev=523618
Log:
SM-904 The jmx.url string is wrong if the properties in servicemix.properties
have spaces at the end
Modified:
incubator/servicemix/trunk/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-817) log4j service for changing log levels at runtime
log4j service for changing log levels at runtime - Key: SM-817 URL: https://issues.apache.org/activemq/browse/SM-817 Project: ServiceMix Issue Type: New Feature Components: servicemix-core Reporter: Thomas Termin Attachments: logging_service.patch This patch add a new MBean service to reconfigure the log4j system at runtime. The default is a scheduler which looks in a configurable time for changes in the log4j.xml file and reconfigures the system if something has changed and of course if the file is available. The service could be extended to read also a property file and reconfigure the system as well as to set one or more specific log levels via JMX console. I wouldn't need that...! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] 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
