[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.
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.
[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
+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_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-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.
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.
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
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---
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-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
