I have a background thread that is using hornetq client to receive jms
topic message from a remote hornetq broker. This thread is started as
ServletContextListener when tomcat starts.
But the tomcat throws strange Exception:
llegal access: this web application instance has been stopped already.
C
Joao,
try channelSendOptions="6"
this will mean that
1. You wish to use ACK's (option 2)
2. You wish the ACK to be synchronous
If you don't have the 0x0002 option enabled, it wont use ACKs at all.
Filip
On Thu, Jul 3, 2014 at 4:44 PM, João Sávio wrote:
> If I set channelSendOptions="8" (def
If I set channelSendOptions="8" (default value = asynchronous), the % of
errors increase (as expected)
Regards
João
2014-07-03 19:43 GMT-03:00 João Sávio :
> I don't think so.
>
> Here it is: http://pastebin.com/qYCzmECb (server.xml - node1)
>
> Regards
> João
>
--
http://joaosavio.wordpre
I don't think so.
Here it is: http://pastebin.com/qYCzmECb (server.xml - node1)
Regards
João
did you post your server.xml cause I can't find it?
On Thu, Jul 3, 2014 at 4:25 PM, João Sávio wrote:
> Hello Filip
>
> I'm using channelSendOptions="4", which is supposed to be synchronous
>
> Regards
> João
>
Hello Filip
I'm using channelSendOptions="4", which is supposed to be synchronous
Regards
João
A race condition could happen if you set replication to happen async. But I
do have a memory of the configuration specifying synchronous replication,
which would guarantee that the replication changes have happened before the
request is complete.
On Thu, Jul 3, 2014 at 3:51 PM, Christopher Schu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 7/3/14, 2:19 PM, Mark Eggers wrote:
> João,
>
> This list has a convention of posting either inline or at the end
> of the message you're replying to.
>
> See here for mailing list notes:
>
> http://tomcat.apache.org/lists.html#tomcat-us
Ok, at least the stack trace is clear. The session has been invalidated
somehow.
We would need to figure out when and how this happens, is it possible that
you are doing a clean shutdown of a tomcat instance and that instance
expires all the sessions? If that is the case, kill the tomcat with 'kill
On 03/07/2014 21:51, Leo Donahue wrote:
> On Thu, Jul 3, 2014 at 1:05 AM, Mark Thomas wrote:
>
>> On 3 July 2014 04:11:32 GMT+01:00, Leo Donahue
>> wrote:
>>> I don't want to start a war, but just curious if the Tomcat developers
>>> see
>>> any use case for adding default methods to any of the
On Thu, Jul 3, 2014 at 1:05 AM, Mark Thomas wrote:
> On 3 July 2014 04:11:32 GMT+01:00, Leo Donahue
> wrote:
> >I don't want to start a war, but just curious if the Tomcat developers
> >see
> >any use case for adding default methods to any of the Interfaces in the
> >API?
>
> Which API?
>
> Mark
On Thu, Jul 3, 2014 at 4:22 AM, André Warnier wrote:
> Leo Donahue wrote:
>
>> On Wed, Jul 2, 2014 at 2:33 AM, André Warnier wrote:
>>
>> Blachon, Philippe wrote:
>>>
>>>
>>> Why would one run a virus scanner permanently on a Tomcat server ?
>>>
>>>
>> Does the OP work in the government? My fo
Hello Mark
In fact, I'm not explicit invalidating session on this two requests.
Regards
João
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Filip,
On 7/3/2014 12:11 PM, Filip Hanik wrote:
> 1. are your machines in time sync? If they are not, a session can
> get timed out. 2. 3. SEVERE: Manager [localhost#/myApp]: Unable to
> receive message through TCP channel 4.
> java.lang.IllegalStateE
Hello Filip
The nodes are in the same machine!
Regards
João
On 03/07/2014 16:03, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul,
On 7/2/14, 4:28 PM, Paul Taylor wrote:
On 02/07/2014 16:34, Christopher Schultz wrote:
The solution is that the web application, packaged in a WAR
file, needs to unpack the Lucene indexes ont
1. are your machines in time sync? If they are not, a session can get
timed out.
2.
3. SEVERE: Manager [localhost#/myApp]: Unable to receive message through
TCP channel
4. java.lang.IllegalStateException: setAttribute: Session [
DEC3612CF763194E7953DB3FD2C433E0] has already bee
Hi everyone
I ran my test (total of 1k requests, total of 100 threads) against two
nodes with default VM settings. I've just set heap size. I had about 15% of
errors.
cluster.log - node1 - http://pastebin.com/cpX900Qw
cluster.log - node2 - http://pastebin.com/qCSzMaU6
Running for a long time (to
you mention NIO and say maxThreads, that sounds like the
configuration, but the BIO receiver is on the cluster, and it a completely
different component that also has an applicable NIO configuration.
are you confusing the two?
I'm saying that you should use the NIO receiver on the cluster componen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
João,
This list has a convention of posting either inline or at the end of
the message you're replying to.
See here for mailing list notes:
http://tomcat.apache.org/lists.html#tomcat-users
On 7/3/2014 10:24 AM, João Sávio wrote:
> Hello
>
> Some p
On Thu, Jul 3, 2014 at 9:11 PM, Propes, Barry L
wrote:
> Good to hear.
>
> -Original Message-
> From: Vijendra Pachoriya [mailto:vijendra.pachor...@indegene.com]
> Sent: Thursday, July 03, 2014 8:22 AM
> To: Tomcat Users List
> Subject: RE: Error in DBCP Connection Pool with tomcat 6.x
>
Hello
Some points below:
** What is "on time"?*
In my application, a group of users should always hit the same node after
the first request. So, in first request each group of users will receive an
specific cookie, and LB will perform the load balancing based on this
cookie. In first request, a u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/3/2014 9:12 AM, João Sávio wrote:
> cluster.log -> http://pastebin.com/c98WhnmG
>
>
> 2014-07-03 13:04 GMT-03:00 João Sávio :
>
>> Hello!
>>
>> Using NIO (with channelSendOptions="4", i.e., synchronous), with
>> lightly load, my tests pass 100
On Thu, Jul 3, 2014 at 12:04 PM, João Sávio wrote:
> Hello!
>
> Using NIO (with channelSendOptions="4", i.e., synchronous), with lightly
> load, my tests pass 100%. But, on heavy load, not all sessions are
> replicated on time,
>
Define "on time".
> and I have about 20% of errors.
>
Can you e
cluster.log -> http://pastebin.com/c98WhnmG
2014-07-03 13:04 GMT-03:00 João Sávio :
> Hello!
>
> Using NIO (with channelSendOptions="4", i.e., synchronous), with lightly
> load, my tests pass 100%. But, on heavy load, not all sessions are
> replicated on time, and I have about 20% of errors. If
Hello!
Using NIO (with channelSendOptions="4", i.e., synchronous), with lightly
load, my tests pass 100%. But, on heavy load, not all sessions are
replicated on time, and I have about 20% of errors. If I increase
maxThreads to 400, I have about 15% of errors.
More information:
* I am not performi
Good to hear.
-Original Message-
From: Vijendra Pachoriya [mailto:vijendra.pachor...@indegene.com]
Sent: Thursday, July 03, 2014 8:22 AM
To: Tomcat Users List
Subject: RE: Error in DBCP Connection Pool with tomcat 6.x
Thanks everyone !!
Managed to solve the issue. It seems the wait time
These errors may happen when you have two libraries that both contain the
class javax.persistence.spi.PersistenceProvider
search the libraries (*.jar) in both tomcat and your WAR file, and see if
there are multiple instances of the above named class
On Thu, Jul 3, 2014 at 9:28 AM, Xavier Outhier
Hi,
we have an application that is running under Tomcat. We are trying to upgrade
to latest version 7.0.54 from 7.0.39.
As 7.0.54 lead to some errors, we tried to find out which version broke the
application. The result is that the issue appears with 7.0.52 and is not
present until 7.0.50.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 7/2/14, 3:33 AM, André Warnier wrote:
> Blachon, Philippe wrote:
>> Good morning,
>>
>> We have 4 identical servers with a scheduled task running every
>> night on each of them. This task Stop Tomcat -> Update some data
>> -> Start Tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Emmanual,
On 7/2/14, 5:26 PM, Emmanuel Bourg wrote:
> I'm also pleased to announce that Tomcat 8.0.9 is now available
> for Debian 7 (Wheezy) through the backport repository [1].
Nice job!
It's nice to see Debian working to shed that image of alwa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul,
On 7/2/14, 4:28 PM, Paul Taylor wrote:
> On 02/07/2014 16:34, Christopher Schultz wrote:
>>
>> The solution is that the web application, packaged in a WAR
>> file, needs to unpack the Lucene indexes onto the disk when it
>> starts up. You can
I'd be more inclined to continue down the path of the NIO connector, it has
been tested and used more. What are the errors you get when running with
NIO?
On Thu, Jul 3, 2014 at 8:51 AM, Konstantin Kolinko
wrote:
> 2014-07-03 18:46 GMT+04:00 João Sávio :
> > Unfortunately it's not working yet
>
2014-07-03 18:46 GMT+04:00 João Sávio :
> Unfortunately it's not working yet
>
> I increased the log level as you suggested. Log attached
>
> Thanks
>
Please read numbers 6. and 7. here:
http://tomcat.apache.org/lists.html#tomcat-users
The attachment was thrown away by the mail server.
-
Unfortunately it's not working yet
I increased the log level as you suggested. Log attached
Thanks
2014-07-03 11:10 GMT-03:00 João Sávio :
> Hello Mark
>
> Thanks for your answer. I put the new information and cluster works (maybe
> because I reboot my machine)
>
> Indeed, I'm trying BIO beca
Hello Mark
Thanks for your answer. I put the new information and cluster works (maybe
because I reboot my machine)
Indeed, I'm trying BIO because NIO is causing session replication issues on
load tests. Using NIO, I've already tried to increase maxThreads, and this
minimizes the problem, but don'
Thanks everyone !!
Managed to solve the issue. It seems the wait time out for db was less than
that of configured in tomcat.
Which was leading to close the connection before tomcat does it.
Regards,
Vijendra
-Original Message-
From: Phil Steitz [mailto:phil.ste...@gmail.com]
Sent: 0
2014-07-03 0:38 GMT+04:00 Gulliver Smith :
> Apache Tomcat/7.0.28, Debian
>
> I have two configuration descriptors in /etc/tomcat7/Catalina/localhost/
>
> One, solr.xml deploys correctly and fills catalina.out with lots of
> useful messages.
>
>
> The other fails silently to start (see below).
>
>
Leo Donahue wrote:
On Wed, Jul 2, 2014 at 2:33 AM, André Warnier wrote:
Blachon, Philippe wrote:
Good morning,
We have 4 identical servers with a scheduled task running every night on
each of them. This task Stop Tomcat -> Update some data -> Start Tomcat.
This worked fine for months.
We ha
Good morning,
Yes, it was "random occasions where Tomcat appears not to re-start ".
Finally we have excluded from McAfee scanning : Tomcat7.exe, Java.exe and .zip
files. As the launched application is Java opening a 3.5 Go .zip file surely
the server was too busy to launch Tomcat and scan all t
40 matches
Mail list logo
