Hi all,
I have a problem with the new release of the tomcat-connector (1.2.39) for
64 Bit Windows (isapi_redirect.dll), binary download.
The older versions worked like a charm under Windows Server 2008 R2 64 Bit
and Windows 7 64 Bit, even in a loadbalancing configuration. But after
switching to
A bit guessing here :
You have :
worker.ajp13w.host=localhost
and
jk_open_socket::jk_connect.c (735): connect to 0.0.0.0:8009 failed
(errno=49)
is localhost == 0.0.0.0 ?
From the point of view of mod_jk/isapi, should it not be 127.0.0.1 ?
Your answer points to the right
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:a...@ice-sa.com]
Gesendet: Donnerstag, 3. April 2014 15:36
An: Tomcat Users List
Betreff: Re: AW: tomcat-connectors-1.2.39-windows-x86_64-iis does not
work
Alten, Jessica-Aileen wrote:
A bit guessing here :
You have
Hi all,
I'm stunned about the enormous response to my question and I'm so sorry about
the long delay of my answer now - but there is a world outside with household
chores at the weekend. I'll try to answer the questions from the oldest to the
youngest:
Ok, another check in a command window
Sorry, I don't know how Windows internally resolves localhost. What I
wanted to say is, that the hosts file has not been modified on that
system - by default it does not contain any entries. This seems to have
changed since some Windows versions, as e.g. Windows Vista contains
127.0.0.1
I'll try to check my settings with the C# program.
Ipv6 loopback is available:
127.0.0.1
::1
See http://support.microsoft.com/kb/929852
However, I believe the disabled ipv6 might put us on the right track.
Regards,
Jessica
smime.p7s
Description: S/MIME cryptographic signature
It may be interesting to see what happens if you add a line like this
in the server's
hosts file :
127.0.0.1 localhost localtomcat
and then try to use each of these names in your isapi configuration for
the worker.host.
I tried the formerly commented out lines in the hosts file after a
Hi all,
the new tomcat-connectors-1.2.40-windows-x86_64-iis works with the localhost
setting in workers.properties! Great! Many thanks to the developers! :-)
Regards,
Jessica
smime.p7s
Description: S/MIME cryptographic signature
The official position of the ASF is that we provide code, not
binaries.
Sorry, I can't follow this argument - there are lots of binaries in the
download area, even for Tomcat and the Httpd flagship.
We'd love to provide Windows binaries for mod_jk, but they are a real
pain in the neck to
The Apache Tomcat Project is proud to announce the release of version
1.2.41 of the Apache Tomcat Connectors.
This version fixes one security issue (CVE-2014-8111) and a number of
bugs found in previous releases.
[...]
Downloads:
http://tomcat.apache.org/download-connectors.cgi
Is there
@Jessica: which CPU architecture are you using: x86 (32 Bit), x64 (64
Bits) or even Itanium 64? Which OS version do you have? If you are
willing to test, I can provide an example binary from which we might
learn, how well it works and whether that type of build is suitable for
others as well.
Currently, we have multiple Tomcat nodes running on a single or on
different physical machines with each having its own object pool
(consider we have a pool of java String object but not connection
pool) i.e., an object pool per node. The requirement is to share this
pool of objects across
> We have used HTTP Analayzer for file upload via Internet Explorer-8.
> Following are the scenario observed. [...]
I've just came back from vacation and didn't followed the whole thread - but I
think it is simply an IE 8 problem, see
Like Andreas I would vote for Weld (http://weld.cdi-spec.org/) - it is the
Reference Implementation of CDI for the Java EE platform. It is easy to
install (read
http://balusc.omnifaces.org/2013/10/how-to-install-cdi-in-tomcat.html) and has
an outstanding documentation
Dear all,
I have a problem with the Tomcat 9.0.22 configuration for TLSv1.3 using
jdk8u222-b10_openj9-0.15.1 on Windows Server 2016. In principle TLSv1.3
works, but I want to specify the allowed cipher suites as well.
The relevant parts of server.xml are:
...
> > I have a problem with the Tomcat 9.0.22 configuration for TLSv1.3 using
> > jdk8u222-b10_openj9-0.15.1 on Windows Server 2016. In principle
> > TLSv1.3 works, but I want to specify the allowed cipher suites as well.
> >
> > The relevant parts of server.xml are:
> > > SSLEngine="on" />
> >
16 matches
Mail list logo
