-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lance,
On 8/27/18 19:21, Christopher Schultz wrote:
> Lance,
>
> On 8/24/18 11:52, Campbell, Lance wrote:
>> Tomcat 9 Use Case 1: I want to store the last N number of URLs
>> sent to Tomcat 9 application. Then if Tomcat shuts down I want
>> to w
I'm storing large files. Postgres has a limit for blobs and uses a
different api for larger stuff. Cut off is 1gb
On Mon, Aug 27, 2018, 7:19 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Alex,
>
> On 8/24/18 16:08, Alex O'Re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lance,
On 8/24/18 11:52, Campbell, Lance wrote:
> Tomcat 9 Use Case 1: I want to store the last N number of URLs
> sent to Tomcat 9 application. Then if Tomcat shuts down I want to
> write out these last N number of URLs to the log file.
>
> Stra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alex,
On 8/24/18 16:08, Alex O'Ree wrote:
> I have a use case where i need to downcast a pooled database
> connection down to the native class that is in use for the driver.
> Unfortunately I don't see any APIs that I can use to do this. Is
> there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tim,
On 8/27/18 10:19, Tim K wrote:
> I'm experimenting with Tomcat 9.0.8 enabling Cluster support.
> I've uncommented the line for it within the server.xml. I have 4
> separate servers on different hosts, all with the same config,
> except unique
I figured it out. Classpath issue. I had the postgres driver in my web app
and in tomcat's lib folder. Removing from the web app fixed it.
On Mon, Aug 27, 2018 at 9:47 AM Alex O'Ree wrote:
> Unfortunately, it's not working. I've tried unwrap for both
> org.postgresql.jdbc.PgConnection (concrete
I'm experimenting with Tomcat 9.0.8 enabling Cluster support. I've
uncommented the line for it within the server.xml. I have 4 separate
servers on different hosts, all with the same config, except unique
jvmRoute values. Upon startup, it appears that server1 and server4 pair up
and server2 and s
Hi, actually the issue got resolved. The system in question wasn't tomcat
but jboss (hence the offtopic) and in particular undertow. Undertow seems
to have completely different session expiration handling than tomcat, they
actually prolong expiration timestamp every time an attribute is accessed...
Unfortunately, it's not working. I've tried unwrap for both
org.postgresql.jdbc.PgConnection (concrete class) and
org.psotgresql.PGConnection (interface) and both of them fail to unwrap.
Any other suggestions?
On Sun, Aug 26, 2018 at 10:04 AM Alex O'Ree wrote:
> Perfect, thanks
>
> On Fri, Aug 2
Hi.
.. hmm, where to begin ? ...
Maybe first :
In your case, it looks like you may be more familiar with the configuration of Apache
httpd, than with the configuration of mod_jk and of tomcat.
So just as a possible tip : there is an alternative, at the Apache httpd level,
to mod_jk.
See here :
I have an apache 2.4 on Debian Jessie and I host several sites as virtual hosts.
On of these sites is running on jsp so I hav installed tomcat 8 and I
use mod_jk.
My virtual host configuration file for apache is:
AllowOverride None
Require all denied
Dear Lance
I don't know the motivation for your usecase. But note that the access log is
written after handling the complete request (therefore its able to log the
number of bytes send) and, because it's typical buffered, with a delay, too.
This means, that a request is listed there only in the
Dear Leon,
I suggest to use the Tomcat Manager Application to investigate the session data:
* Use the Session Display (/manager/html/sessions?path=/foo) to take a look on
the different Timers (Creation Time, Last Accessed Time, Used Time, Inactive
Timemm,TTL) or even the session data
* Use the
13 matches
Mail list logo
