Sgrìobh Rémy Maucherat na leanas 10/10/2024 aig 1:07f:
The crawler valve seems to be defined on the Engine, but more
importantly it seems you have no default host ?
So the request is not being mapped and it would return 404 (but the
valve would need some extra null checks).
Rémy
Ahhh of
gt; complaining that the Host used in the getClientIdentifier method within
> the CrawlerSessionManagerValve is null. Full stack trace is:
>
> 10-Oct-2024 10:47:35.297 SEVERE [http-nio-8080-exec-5]
> org.apache.coyote.http11.Http11Processor.service Error processing request
> j
the CrawlerSessionManagerValve is null. Full stack trace is:
10-Oct-2024 10:47:35.297 SEVERE [http-nio-8080-exec-5]
org.apache.coyote.http11.Http11Processor.service Error processing request
java.lang.NullPointerException: Cannot invoke
"org.apache.catalina.Host.getName()" because "host
Adam,
On 6/3/24 04:16, Adam Danischewski wrote:
Using Embedded Tomcat 10 in SpringBoot, trying to manually configure a new
HTTPS/SSL port. I've got the following SSL bundle set in my application
properties (fairly sure this part is working fine):
>
> [snip]
Note: I am new to Tomcat and most o
ski wrote:
>
> > Not sure why I'm getting:
> >
> > Caused by: java.lang.NullPointerException: Cannot invoke
> > "org.apache.tomcat.util.net.SSLHostConfig.getProtocols()" because
> > "this.sslHostConfig" is null
>
> You haven't con
On 03/06/2024 09:16, Adam Danischewski wrote:
Not sure why I'm getting:
Caused by: java.lang.NullPointerException: Cannot invoke
"org.apache.tomcat.util.net.SSLHostConfig.getProtocols()" because
"this.sslHostConfig" is null
You haven't configured a defa
;
shc.setHostName("localhost");
prot.addSslHostConfig(shc);
tomcat.getService().addConnector(connector);
return super.getTomcatWebServer(tomcat);
}
Not sure why I'm getting:
Caused by: java.lang.NullPointerException: Cannot invoke
"org.apache.tomcat.util
On 12/11/2023 23:01, Усманов Азат Анварович wrote:
Sorry for delayed response, Once I comment out the CredentialHandler in context
xml both in my app's context.xml and in global context.xml, and add realm to
server.xml. CredentialHandler returns null once again.
This is by design.
Sorry for delayed response, Once I comment out the CredentialHandler in context
xml both in my app's context.xml and in global context.xml, and add realm to
server.xml. CredentialHandler returns null once again.
От: Christopher Schultz
Отправлено: 5 ноября
Азат,
On 10/31/23 13:53, Усманов Азат Анварович wrote:
Hi everyone! CredentialHandler became not null, as soon as I
transferred Realm definition from server.xml to context.xml(after
checking the source code) .I've been able to see the new pbkdf2
version of the given clear text password
Hi everyone! CredentialHandler became not null, as soon as I transferred Realm
definition from server.xml to context.xml(after checking the source code) .I've
been able to see the new pbkdf2 version of the given clear text password even
with old 9.0.64 version. I was wondering i
I did recheck using 9.0.82, unfortunately nothing has changed CredentialHandler
is still null
От: Christopher Schultz
Отправлено: 30 октября 2023 г. 18:52
Кому: Tomcat Users List ; Усманов Азат Анварович
Тема: Re: Accessing Credential handler inside the web
System.out.println("context vs"+context.getMajorVersion()); //
prints 4
System.out.println("ATRIB"+context.getAttribute(Globals.CREDENTIAL_HANDLER));//always
prints ATRIB null
return (CredentialHandler)
context.getAttribute(Globals.CREDENTIAL_HAND
uot;+context.getMajorVersion()); //
prints 4
System.out.println("ATRIB"+context.getAttribute(Globals.CREDENTIAL_HANDLER));//always
prints ATRIB null
return (CredentialHandler)
context.getAttribute(Globals.CREDENTIAL_HANDLER);
}
UserRecord class
public boo
Message-
From: Poh Wei Xiang
Sent: Thursday, March 9, 2023 1:56 PM
To: Tomcat Users List
Cc: Ong Han Sheng
Subject: Re: Encountered java.sql.sqlexception "the url cannot be null"
starting from tomcat 9.0.71
Hi,
Glad to hear that this is going to be fixed.
Do you have a sample cont
, 2023 1:56 PM
To: Tomcat Users List
Cc: Ong Han Sheng
Subject: Re: Encountered java.sql.sqlexception "the url cannot be null"
starting from tomcat 9.0.71
Hi,
Glad to hear that this is going to be fixed.
Do you have a sample context format to work with connectionstring?
Sent from O
:
Mark
Sent from Outlook for Android<https://aka.ms/AAb9ysg>
From: Mark Thomas
Sent: Wednesday, 8 March 2023, 20:14
To: users@tomcat.apache.org
Subject: Re: Encountered java.sql.sqlexception "the url cannot be null"
starting from tomc
he.org
Subject: Re: Encountered java.sql.sqlexception "the url cannot be null"
starting from tomcat 9.0.71
On 08/03/2023 11:58, Mark Thomas wrote:
> Thanks,
>
> I am able to recreate that stack trace. I am looking into the root cause
> now.
Found it.
There was a c
Mark
Mark
On 08/03/2023 09:03, Poh Wei Xiang wrote:
Hi,
java.sql.SQLException: The url cannot be null
java.sql.DriverManager.getConnection(Unknown Source)
java.sql.DriverManager.getConnection(Unknown Source)
org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.g
Thanks,
I am able to recreate that stack trace. I am looking into the root cause
now.
Mark
On 08/03/2023 09:03, Poh Wei Xiang wrote:
Hi,
java.sql.SQLException: The url cannot be null
java.sql.DriverManager.getConnection(Unknown Source)
java.sql.DriverManager.getConnection
Hi,
java.sql.SQLException: The url cannot be null
java.sql.DriverManager.getConnection(Unknown Source)
java.sql.DriverManager.getConnection(Unknown Source)
org.apache.tomcat.dbcp.dbcp2.cpdsadapter.DriverAdapterCPDS.getPooledConnection(DriverAdapterCPDS.java:396
On 08/03/2023 03:50, Poh Wei Xiang wrote:
Hi,
I am encountering an issue validating my application database connectivity, it
throws java.sql.SQLException: The url cannot be null upon validation.
Full stack trace please.
Mark
The application is developed using Avaya’s Orchestration
Hi,
I am encountering an issue validating my application database connectivity, it
throws java.sql.SQLException: The url cannot be null upon validation.
The application is developed using Avaya’s Orchestration designer (Eclipse) and
database validation works until 9.0.70.
I hope someone
1.2.35) to host.
>> In the past, I did not need to provide a “secret”, but now it appears I do
>> since I get the following error in Catalina.out:
>>
>>
>> java.lang.IllegalArgumentException: The AJP Connector is configured with
>> secretRequired="true&q
a “secret”, but now it appears I do
since I get the following error in Catalina.out:
java.lang.IllegalArgumentException: The AJP Connector is configured with
secretRequired="true" but the secret attribute is either null or "". This
combination is not valid.
I have modified
I get the following error in Catalina.out:
java.lang.IllegalArgumentException: The AJP Connector is configured with
secretRequired="true" but the secret attribute is either null or "". This
combination is not valid.
I have modified the connector in my server.xml for Tomcat t
sion 9.0.59 to 9.0.60.
> Since the update, we are having issues with some views because NULL-Strings
> are no longer coerced to Empty-Strings.
> I know the current behaviour is compliant to the EL specification and the
> former behaviour was not.
> But this update has caused some trou
Tomcat Version: 9.0.60
Primefaces: 11.0.5
Hello,
recently we updated our environment from Tomcat Version 9.0.59 to 9.0.60.
Since the update, we are having issues with some views because NULL-Strings are
no longer coerced to Empty-Strings.
I know the current behaviour is compliant to the EL
> -Original Message-
> From: Christopher Schultz
> Sent: Wednesday, March 17, 2021 3:13 PM
> To: users@tomcat.apache.org
> Subject: Re: Wait... NULL address in java.net.BindException: Address already
> in use (Bind failed) ???
>
> Eric and Martin,
>
> -Original Message-
> From: Martin Grigorov
> Sent: Wednesday, March 17, 2021 2:35 PM
> To: Tomcat Users List
> Subject: Re: Wait... NULL address in java.net.BindException: Address already
> in use (Bind failed) ???
>
> On Wed, Mar 17, 2021, 20:27 Eric Robinso
Eric and Martin,
On 3/17/21 15:35, Martin Grigorov wrote:
On Wed, Mar 17, 2021, 20:27 Eric Robinson wrote:
From: Martin Grigorov
Sent: Wednesday, March 17, 2021 12:45 PM
To: Tomcat Users List
Subject: Re: Wait... NULL address in java.net.BindException: Address
already
in use (Bind failed
On Wed, Mar 17, 2021, 20:27 Eric Robinson wrote:
> > From: Martin Grigorov
> > Sent: Wednesday, March 17, 2021 12:45 PM
> > To: Tomcat Users List
> > Subject: Re: Wait... NULL address in java.net.BindException: Address
> already
> > in use (Bind failed) ???
&
> From: Martin Grigorov
> Sent: Wednesday, March 17, 2021 12:45 PM
> To: Tomcat Users List
> Subject: Re: Wait... NULL address in java.net.BindException: Address already
> in use (Bind failed) ???
>
> Hi,
>
> On Wed, Mar 17, 2021, 19:34 Eric Robinson
&
; I have confirmed with netstat and fuser that there is no other process
> listening on that port. Could the problem be that the host address is null
> for some reason? I don't recall seeing that before, and Google diving came
> up dry.
>
> -Eric
>
>
>
> Disclaimer
s no other process listening on
that port. Could the problem be that the host address is null for some reason?
I don't recall seeing that before, and Google diving came up dry.
-Eric
Disclaimer : This email and any files transmitted with it are confidential and
intended solely for intended
"true"
removeAbandoned="true"
username="x"
password="y"
/>
My apologies for the noise.
On 1/9/21 8:10 PM, Rob Sargent wrote:
After many loops through this, I'm pretty certain my datasource
factory is simply
urce
factory is simply never added to the context as per the SEVERE message.
Any other combinations of lookups generates a NamingException.
This verbose approach demonstrates that the key is in the map and it
is mapped to null.
InitialContext ic = new InitialContext();
Context sgsCon
ates that the key is in the map and it
is mapped to null.
InitialContext ic = new InitialContext();
Context sgsContext = (Context) ic.lookup("java:/comp/env");
Context jctx = (Context) sgsContext.lookup("jdbc");
dataSource = (PerUserPoolDataSource) jctx.lookup(
After many loops through this, I'm pretty certain my datasource factory
is simply never added to the context as per the SEVERE message.
Any other combinations of lookups generates a NamingException.
This verbose approach demonstrates that the key is in the map and it is
mapped to
Nice catch. Unfortunately that doesn't clear up the 'Cannot register
null bean' problem.
rjs
On 1/8/21 12:18 PM, Mark Thomas wrote:
On 08/01/2021 16:11, Rob Sargent wrote:
classname="org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource"
factory=
On 08/01/2021 16:11, Rob Sargent wrote:
> classname="org.apache.tomcat.dbcp.dbcp.datasources.PerUserPoolDataSource"
> factory="org.apache.commons.dbcp2.datasources.PerUserPoolDataSourceFactory"
You are mixing Commons DBCP 2 and Apache Tomcat's internal fork of DBCP
2. They use different packa
I'm getting the following error message during startup
SEVERE: Cannot register null bean for
[Tomcat:type=DataSource,host=localhost,context=/sgs,class=javax.sql.DataSource,name="jdbc/sgsdb"]
with sgs/META-INF/context.xml as
and sgs/WEB-INF/web.xml
ctive wisdom, as the EOL of Tomcat 7 is looming, we
>>>> are migrating our legacy app from Tomcat 7.0 to Tomcat 8.5.
>>>> We deploy exactly the same war in both versions. For some
>>>> reason Tomcat 8.5 adds null characters to the end of
>>>> JavaScrip
deploy
>>> exactly the same war in both versions. For some reason Tomcat 8.5
>>> adds null characters to the end of JavaScript files. For
>>> instance, jQuery file served by Tomcat 8.5 ends with “})( window
>>> ); �” where five last characters are bytes 00. Tom
omcat 7.0 to Tomcat 8.5. We deploy
>> exactly the same war in both versions. For some reason Tomcat 8.5
>> adds null characters to the end of JavaScript files. For
>> instance, jQuery file served by Tomcat 8.5 ends with “})( window
>> ); �” where five last characte
Hi,
On Tue, May 19, 2020 at 3:32 PM Tuukka Ilomäki
wrote:
> Dear collective wisdom,
> as the EOL of Tomcat 7 is looming, we are migrating our legacy app from
> Tomcat 7.0 to Tomcat 8.5. We deploy exactly the same war in both versions.
> For some reason Tomcat 8.5 adds null character
Dear collective wisdom,
as the EOL of Tomcat 7 is looming, we are migrating our legacy app from Tomcat
7.0 to Tomcat 8.5. We deploy exactly the same war in both versions. For some
reason Tomcat 8.5 adds null characters to the end of JavaScript files. For
instance, jQuery file served by Tomcat
On 31/03/2020 14:36, Manuel Dominguez Sarmiento wrote:
> Thanks, so we would be able to log this with AccessLogValve using the
> following patterns, right?
> %{org.apache.coyote.connectionID}r
> %{org.apache.coyote.streamID}r
Correct.
Mark
>
> *Manuel Dominguez Sarmiento*
>
> On 31/03/2020 10
Thanks, so we would be able to log this with AccessLogValve using the
following patterns, right?
%{org.apache.coyote.connectionID}r
%{org.apache.coyote.streamID}r
*Manuel Dominguez Sarmiento*
On 31/03/2020 10:28, Mark Thomas wrote:
On 29/03/2020 16:16, Mark Thomas wrote:
On 29/03/2020 15:58,
On 29/03/2020 16:16, Mark Thomas wrote:
> On 29/03/2020 15:58, Manuel Dominguez Sarmiento wrote:
>>
>>> Do the streams with errors all share the same connection ID? I suspect
>>> an error on one stream is triggering the closure of the connection and
>>> what you are seeing is the fallout of closing
On 29/03/2020 15:58, Manuel Dominguez Sarmiento wrote:
>
>> Do the streams with errors all share the same connection ID? I suspect
>> an error on one stream is triggering the closure of the connection and
>> what you are seeing is the fallout of closing the connection.
> That makes sense and is ki
Do the streams with errors all share the same connection ID? I suspect
an error on one stream is triggering the closure of the connection and
what you are seeing is the fallout of closing the connection.
That makes sense and is kind of what we're suspecting. How can we check
the connection/stre
one whole day in one single high-volume server).
> Some of the following request fields are NULL (or -1) in these examples:
> - remoteAddr
> - remotePort
> - serverPort
> - requestURI
> - User-Agent
>
> Some requests are missing some of the fields, some of the requests are
> m
ields are NULL (or -1) in these examples:
- remoteAddr
- remotePort
- serverPort
- requestURI
- User-Agent
Some requests are missing some of the fields, some of the requests are
missing others. What is particularly interesting is that the errors are
clustered around particular timestamps, pointi
the init parameters in the doGet()
> > method, but I keep getting a null value when I use
> > this.getServletConfig(). If I save the ServletConfig in an instance
> > variable from the init() method it works as expected. Shouldn't the
> > this.getServletConfig() return the co
On 14/02/2020 18:29, Richard Monson-Haefel wrote:
> Hi,
>
> I'm experimenting with using annotations. I created a Servlet with
> annotations and then attempt to get the init parameters in the doGet()
> method, but I keep getting a null value when I use
> this.getServletC
Hi,
I'm experimenting with using annotations. I created a Servlet with
annotations and then attempt to get the init parameters in the doGet()
method, but I keep getting a null value when I use
this.getServletConfig(). If I save the ServletConfig in an instance
variable from the init() meth
Hi Christopher, please see below:
1) The Tomcat valves operate on all webapps. We only need/require
this for one particular webapp without affecting the others.
Not true; see Konstantin's response.
Yes, I realized per-context valve configuration was possible after I
sent my original email.
doc/config/context.html#Defining_a_context
You are correct. I realized this after my original response. We actually
already use per-context AccessLogValves.
2. If I understand correctly, the null value from
request.getRemoteAddr() means that the client connection has already
been closed.
Tomcat cannot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Manuel,
On 2/5/20 1:29 PM, Manuel Dominguez Sarmiento wrote:
> Yes, there are two reasons:
>
> 1) The Tomcat valves operate on all webapps. We only need/require
> this for one particular webapp without affecting the others.
Not true; see Konstanti
n by placing it
into Context configuration for that specific web application (usually
that is the "/META-INF/context.xml" configuration file). [1]
[1]
http://tomcat.apache.org/tomcat-9.0-doc/config/context.html#Defining_a_context
2. If I understand correctly, the null value from
request.g
Yes, there are two reasons:
1) The Tomcat valves operate on all webapps. We only need/require this
for one particular webapp without affecting the others.
2) The code has been simplified for illustration purposes. Besides
X-Forwarded-For, we detect and work around many other custom external
mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Manuel,
On 2/5/20 12:12 PM, Manuel Dominguez Sarmiento wrote:
> Our filter is not doing anything fancy (and it has always worked
> correctly before we ran into this bug). In pseudo-code:
>
> public doFilter(request, response) {
>
> String ip = re
Our filter is not doing anything fancy (and it has always worked
correctly before we ran into this bug). In pseudo-code:
public doFilter(request, response) {
String ip = request.getRemoteAddr();
boolean isProxy = isProxy(ip);
if (isProxy) {
String unwrappedIP = unwrapXForwar
On 04/02/2020 22:27, Manuel Dominguez Sarmiento wrote:
> We are getting the NPEs in a top-of-the-chain servlet filter which
> decorates HttpServletRequest.getRemoteAddr() before actual servlet
> processing. Only on HTTP/2 and in a very small number of cases. Perhaps
> we should test 9.0.31 and see
We are getting the NPEs in a top-of-the-chain servlet filter which
decorates HttpServletRequest.getRemoteAddr() before actual servlet
processing. Only on HTTP/2 and in a very small number of cases. Perhaps
we should test 9.0.31 and see what happens. When is this new version due
for release?
*
On 04/02/2020 15:37, Manuel Dominguez Sarmiento wrote:
> Thanks Mark. I just wanted to clarify that the issue is not only present
> when the request arrives at AccessLogValve, but while the request is
> being serviced as well.
> We noticed this bug because we were getting random NullPointerExceptio
Thanks Mark. I just wanted to clarify that the issue is not only present
when the request arrives at AccessLogValve, but while the request is
being serviced as well.
We noticed this bug because we were getting random NullPointerExceptions
when trying to do anything with the result from
HttpServ
On 03/02/2020 19:24, Mark Thomas wrote:
> I haven't fixed this but I can reproduce it easily with the h2spec test
> suite. As I have a reproducible test case I'm hopeful I'll be able to
> find a fix fairly quickly.
I've just committed a fix. It is in:
- master for 10.0.0.0-M1 onwards
- 9.0.x fo
On 24/01/2020 12:26, Manuel Dominguez Sarmiento wrote:
> Hi Mark, thanks for your feedback. Please see below:
>> On 23/01/2020 13:40, Manuel Dominguez Sarmiento wrote:
>>> Hi, we started
>>> noticing that HttpServletRequest.getRemoteAddr() was
>>> someti
Hi Mark, thanks for your feedback. Please see below:
On 23/01/2020 13:40, Manuel Dominguez Sarmiento wrote:> Hi, we started
noticing that HttpServletRequest.getRemoteAddr() was
sometimes returning NULL (which is invalid according to the servlet
spec), about 20-50 times per day (we have h
On 23/01/2020 13:40, Manuel Dominguez Sarmiento wrote:> Hi, we started
noticing that HttpServletRequest.getRemoteAddr() was
> sometimes returning NULL (which is invalid according to the servlet
> spec), about 20-50 times per day (we have high-load servers which
> routinely handle over
Hi, we started noticing that HttpServletRequest.getRemoteAddr() was
sometimes returning NULL (which is invalid according to the servlet
spec), about 20-50 times per day (we have high-load servers which
routinely handle over 100 requests per second). This only happens on
secure HTTP/2 requests
List'
>Betreff: PooledConnection#connectUsingDriver,
>Thread.currentThread().getContextClassLoader() is null
>
>Context:
>Debian GNU/Linux 9 \n \l
>java version 1.8.0_162
>Tomcat 8.5.35
>
>From time to time we are facing the follwing exception (call stack):
>...
>Caused by
Note: I have moved this "issue" over to the tomcat-dev mailinglist ...
-Ursprüngliche Nachricht-
Von: Clemens Wyss DEV
Gesendet: Mittwoch, 24. Juli 2019 11:07
An: 'Tomcat Users List'
Betreff: PooledConnection#connectUsingDriver,
Thread.currentThread().getContextC
org.apache.tomcat.jdbc.pool.ClassLoaderUtil.loadClass(ClassLoaderUtil.java:56)
at
org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver(PooledConnection.java:280)
... 59 common frames omitted
Caused by: java.lang.ClassNotFoundException: Classloader is null
at
org.apache.tomcat.jdbc.pool.ClassLoaderUtil.loadClass
What is the current way of coercing empty string input fields to NULL With
9.0.12? This issue seems to come up with each new major version of EL/JSF.
All of the previous work arounds are no longer producing null values. Surely
I’m missing something obvious that has been published
t; >
> > After checking togglz’s code, I found that it calls
> “Thread.currentThread().getContextClassLoader()” every times calling
> togglz.
> >
> >
> > Then I print out context class loader when calling togglz, like
> this:
> >
> >
ing togglz, like this:
>
>
> And I find a strange thing. Only execute thread has context class
> loader, worker thread created by parallelStream got null for class loader.
>
>
>
> But when it start as an springboot application, all threads has cont
” every times calling
> togglz.
>
> Then I print out context class loader when calling togglz, like this:
> And I find a strange thing. Only *execute thread* has context class
> loader, *worker thread *created by parallelStream got *null* for class
> loader.
> But when it start as
01, Mark Thomas wrote:
>>>> On 13/06/17 15:27, Chris Cheshire wrote:
>>>
>>>
>>>
>>>>> I'm bewildered at why tomcat operates this way when it comes
>>>>> to Numbers
>>> and
>>>>> Strings. Why is it
gt;>
>>>> I'm bewildered at why tomcat operates this way when it comes
>>>> to Numbers
>> and
>>>> Strings. Why is it insistent on coercion when null and zero
>>>> are
>> absolutely
>>>> not the same value. If this is be
On Tue, Jun 13, 2017 at 6:06 PM, Mark Thomas wrote:
> On 13/06/17 22:01, Mark Thomas wrote:
> > On 13/06/17 15:27, Chris Cheshire wrote:
>
>
>
> >> I'm bewildered at why tomcat operates this way when it comes to Numbers
> and
> >> Strings. Why is it
On 13/06/17 22:01, Mark Thomas wrote:
> On 13/06/17 15:27, Chris Cheshire wrote:
>> I'm bewildered at why tomcat operates this way when it comes to Numbers and
>> Strings. Why is it insistent on coercion when null and zero are absolutely
>> not the same value. If thi
On 13/06/17 15:27, Chris Cheshire wrote:
> On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote:
>
>> On 31/05/17 23:31, Chris Cheshire wrote:
>>> I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
>>> attributes of type Long/Integer/Float, how
> -XX:MaxTenuringThreshold=15 -XX:+UseTLAB -XX:G1HeapRegionSize=32m
> -XX:-UseAdaptiveSizePolicy -XX:MaxMetaspaceSize=512m
> -XX:-UseSplitVerifier "
>
>
>
> -Original Message- From: Chris Cheshire
> [mailto:yahoono...@gmail.com] Sent: Tuesday, June 13, 2017 7:58 PM
> To:
5
-XX:+UseTLAB
-XX:G1HeapRegionSize=32m -XX:-UseAdaptiveSizePolicy -XX:MaxMetaspaceSize=512m
-XX:-UseSplitVerifier "
-Original Message-
From: Chris Cheshire [mailto:yahoono...@gmail.com]
Sent: Tuesday, June 13, 2017 7:58 PM
To: Tomcat Users List
Subject: Re: tomcat 7, null tag attributes
On Tue, Jun 6, 2017 at 2:29 PM, Mark Thomas wrote:
> On 31/05/17 23:31, Chris Cheshire wrote:
> > I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
> > attributes of type Long/Integer/Float, however it is *always* coerced to
> > zero.
> >
>
On 31/05/17 23:31, Chris Cheshire wrote:
> I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
> attributes of type Long/Integer/Float, however it is *always* coerced to
> zero.
>
> <%@attribute name="parentId" required="true" rte
/31/17 6:31 PM, Chris Cheshire wrote:
>>>> I am using tomcat 7 on CentOS 7 and I need to pass a null
>>>> value to tag attributes of type Long/Integer/Float, however
>>>> it is *always* coerced to zero.
>>>>
>>>> <%@attribute name=&q
at 7 on CentOS 7 and I need to pass a null value to
> > tag attributes of type Long/Integer/Float, however it is *always*
> > coerced to zero.
> >
> > <%@attribute name="parentId" required="true" rtexprvalue="true"
> > type="java.lang
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Chris,
On 5/31/17 6:31 PM, Chris Cheshire wrote:
> I am using tomcat 7 on CentOS 7 and I need to pass a null value to
> tag attributes of type Long/Integer/Float, however it is *always*
> coerced to zero.
>
> <%@attribute name=&
I am using tomcat 7 on CentOS 7 and I need to pass a null value to tag
attributes of type Long/Integer/Float, however it is *always* coerced to
zero.
<%@attribute name="parentId" required="true" rtexprvalue="true"
type="java.lang.Long" %>
Changing r
ried. However, on subsequent requests, I have quite often
>>> the remote user being null despite having the correct JSESSION
>>> cookie set from the login call.
>>>
>>> This is not happening always, but it is quite frequent.
>>> Interestingly, if a set an
>> Hello,
>>
>> I am using HttpServletRequest.login to authenticate users on an ajax
>> call.
>> This is working fine and the relevant realm is queried. However, on
>> subsequent requests, I have quite often the remote user being null
>> despite
>>
On 12/09/2016 00:45, Nicolas Clemeur wrote:
> Hello,
>
> I am using HttpServletRequest.login to authenticate users on an ajax call.
> This is working fine and the relevant realm is queried. However, on
> subsequent requests, I have quite often the remote user being null despi
Hello,
I am using HttpServletRequest.login to authenticate users on an ajax call.
This is working fine and the relevant realm is queried. However, on
subsequent requests, I have quite often the remote user being null despite
having the correct JSESSION cookie set from the login call.
This is not
Hello,
When using WsWebSocketContainer.connectToServer with ClientEndpointConfig I
get java.nio.BufferOverflowException in case the HTTP headers are more than
4k.
The used ByteBuffer is 4k:
https://github.com/apache/tomcat80/blob/trunk/java/org/apache/tomcat/websocket/WsWebSocketContainer.java#L6
Environment: Tomcat 8.0.33 on RHEL6
In our app we are capturing the SSL/TLS protocol being used by referencing
the org.apache.tomcat.util.net.secure_protocol_version request attribute.
When the connector is NIO this works beautifully, but trying this on NIO2
returns null.
-
Jason Schwanz
yer and our application started
>>> crashing
>>> > about every 1-2 hours. We're running the following versions of
>>> software:
>>> >
>>> > apache-tomcat-7.0.52
>>> > jdk1.6.0_113
>>> > SunOS vs-danaus 5.10 Generic_150400-
1 - 100 of 699 matches
Mail list logo
