[
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
[
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
[
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
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
[
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
[
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
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
[
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
[
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
: 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
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
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
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
[
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
[
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
[
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
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
[
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
[
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
[
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
[
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
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
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
[
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
: 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
: 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
[
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
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
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
---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
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
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
: 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
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
: 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
35 matches
Mail list logo