Mark,
Since we do not know how to "switch connectors", or install OpenSSL, and do
not have JDK on the server (only JRE 1.6.0_17), then I suppose the best bet
is to wait until Tomcat is fixed ("coming soon").
Steve Johnson (619) 237-8315 P Please consider the environment before
printing this e-ma
2010/1/19 Michael Hahn :
>>isapi_redirect.dll (failing):
>>(..)
>> log_file=C:\tomcat\isapi_redirect.log
The above is different in the working file,
log_file=C:\tomcat\logs\isapi_redirect.log
> 2010-01-18 23:16:33 W3SVC1804915670 10.10.10.227 GET
/servlets-examples/servlet/HelloWorldExample -
It should be a mod_jk configuration issue.
After compared your two configurations, I found two main differences:
- extension_uri=/jakarta/isapi_redirect.dll
+ extentions_uri=/jakarta/isapi_redirect.dll
extension_uri vs extensions_uri, right vs wrong
- log_level=info
+ log_level=ALL
The mod_
2010/1/18 iainmac :
>
> Hi,
>
> I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me
> this length error.
>
> I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18.
>
> I know I can rewrite the code, and over time I probably will, but is there a
> way of configuring Tomcat
Hi,
AHH!!
I was only looking through the Eclipse GUI settings, and hadn't noticed that
under Servers-->Tomcat v5.5 in the Eclipse Project Explorer, there were
catalina.policy, etc. files, including tomcat-users.xml :(...
So, I added my role and user definitions to that tomcat-users.xml, and it
The question, simply put, is we have no idea why we were able to get the
connector to work on one server (and only one server) and every other server
we've tried has failed with 404 errors and no isapi_redirect.log files being
generated. Even making the configuration identical to the working server
On Mon, 2010-01-18 at 10:14 -0500, Christopher Schultz wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Rick,
>
> On 1/17/2010 11:16 AM, Rick Bragg wrote:
> > OK, I did
> > #apt-get install --reinstall tomcat6
> > And the log files are back!
> >
> > I'm definitely a newbe at this.
Doesnt eclipse use use a $CATALINA_BASE to run tomcat? I think the tomcat
instance on eclipse is not the same as the one on $CATALINA_HOME. Look at
the server project files under eclipse they will have their own
configuration files.
On Mon, Jan 18, 2010 at 10:43 PM, wrote:
> Hi,
>
> I have a web
Hi,
I have a web application that works when run directly under Tomcat. This web
app has the following in web.xml:
testweb
accessible by authenticated users of the tomcat
role
/*
GET
POST
Nice letter, but what's the actual question?
On 01/18/2010 10:52 PM, Michael Hahn wrote:
Hello, we've been tasked with fowarding some requests to our IIS6 sharepoint
Regards
--
^TM
-
To unsubscribe, e-mail: users-unsubscr..
Hello, we've been tasked with fowarding some requests to our IIS6 sharepoint
server to tomcat 5.5 for use with SSO for other Tomcat based authentication.
The SSO piece of the puzzle is working fine. However, the request forwarding
we are having major problems with.
We first installed Tomcat 5.5 an
*** NOTICE *
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law. If the
reader of this
*** NOTICE *
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law. If the
reader of this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Iain,
On 1/18/2010 10:28 AM, iainmac wrote:
> I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me
> this length error.
Unlikely. See below.
> I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18.
This is going to be th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jeffrey,
On 1/18/2010 10:59 AM, Jeffrey Janner wrote:
> Thanks Chris. Some useful info I can start looking at.
> Yes, it looked like a normal shutdown to me also, all connectors stopped, etc.
> The only issue was that I think I should have seen a 3rd
On 01/18/2010 10:18 AM, Mark Thomas wrote:
On 18/01/2010 11:03, Steve G. Johnson wrote:
We recently installed Tomcat 5.5.23 in Windows server to support the Infor
WebUI (webtop) application.
We installed a cerificate and are using SSl on port 8443. This all works
fine.
The local IT Security
On 18/01/2010 11:37, Jens Neu wrote:
> Steve,
>
> it is not a vulnerability of Tomcat, nevertheless it can be fixed by it.
> You definitely _should_ fix it, since data integrity can not be assured on
> your https connections any more.
>
> I have little to no Windows experienc; but my understand
On 18/01/2010 11:03, Steve G. Johnson wrote:
>
> We recently installed Tomcat 5.5.23 in Windows server to support the Infor
> WebUI (webtop) application.
> We installed a cerificate and are using SSl on port 8443. This all works
> fine.
>
> The local IT Security team ran an HP "Web Inspect" and i
Steve,
it is not a vulnerability of Tomcat, nevertheless it can be fixed by it.
You definitely _should_ fix it, since data integrity can not be assured on
your https connections any more.
I have little to no Windows experienc; but my understanding is, that while
running Tomcat on Windows Serve
Hi
I am using comet connections for some time now in a server push manner:
Whenever the server needs to inform the client about some event, it sends a
packet to the client and waits for a reply in the same connection.
As soon, as a READ event is triggered, that reply is read and the next
message c
We recently installed Tomcat 5.5.23 in Windows server to support the Infor
WebUI (webtop) application.
We installed a cerificate and are using SSl on port 8443. This all works
fine.
The local IT Security team ran an HP "Web Inspect" and it showed a High
vulnerability for SSLv3/TLS known as CVE-20
*** NOTICE *
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential, and exempt from disclosure under applicable law. If the
reader of this
On 17/01/2010 16:08, Peter Crowther wrote:
> 2010/1/17 Hassan Schroeder :
>> You're welcome to your opinion, but personally I think the whole
>> splatter-files-all-over-the-system repackaging approach is horribly
>> flawed for apps like Tomcat
> [...]
>
> Tomcat has a very strong view on where its
On Mon, 2010-01-18 at 09:02 -0600, Caldarale, Charles R wrote:
> > From: Rick Bragg [mailto:li...@gmnet.net]
> > Subject: Re: Cyclos Webapp Trouble (404)
> >
> > Yes the above works perfect. I can log into MySQL in exactly that way.
> > I also double checked the password.
>
> Just for grins, do
Hi,
I am moving from Tomcat 5 to 6, and jsp's that worked fine in 5 now give me
this length error.
I also have moved from java j2sdk1.4.1_02 to jdk1.6.0_18.
I know I can rewrite the code, and over time I probably will, but is there a
way of configuring Tomcat 6 to enable me to compile these j
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 1/18/2010 10:02 AM, Caldarale, Charles R wrote:
>> From: Rick Bragg [mailto:li...@gmnet.net]
>> Subject: Re: Cyclos Webapp Trouble (404)
>>
>> Yes the above works perfect. I can log into MySQL in exactly that way.
>> I also double checked t
On Mon, 2010-01-18 at 09:02 -0600, Caldarale, Charles R wrote:
> > From: Rick Bragg [mailto:li...@gmnet.net]
> > Subject: Re: Cyclos Webapp Trouble (404)
> >
> > Yes the above works perfect. I can log into MySQL in exactly that way.
> > I also double checked the password.
>
> Just for grins, do
Thanks, I read that but its not clear at all. I added
java.util.logging.ConsoleHandler.useParentHandler = true
but has not made a difference.
Apache Tomcat 6.0.20 on XP.
I have it working by now by deleting the loggers other than:
handlers = 1catalina.org.apache.juli.FileHandler,
java.util.l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick,
On 1/17/2010 11:16 AM, Rick Bragg wrote:
> OK, I did
> #apt-get install --reinstall tomcat6
> And the log files are back!
>
> I'm definitely a newbe at this. The re-install kept my startup scripts
> (and config files) all in tact. So this i
18.01.2010 15:57, Rick Bragg:
> On Mon, 2010-01-18 at 09:43 -0500, David Smith wrote:
>> MySQL leave the tcp port disabled for security reasons. I've never
>> understood the decision, but it happens. You can test w/ the mysql command:
>>
>> mysql -P 3306 -h localhost -u cyclos -p
> Yes the abo
> From: Rick Bragg [mailto:li...@gmnet.net]
> Subject: Re: Cyclos Webapp Trouble (404)
>
> Yes the above works perfect. I can log into MySQL in exactly that way.
> I also double checked the password.
Just for grins, do a netstat -ano and verify that the MySQL pid really is
listening on 127.0.0.
On Mon, 2010-01-18 at 09:43 -0500, David Smith wrote:
> Rick Bragg wrote:
> > On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote:
> >
> >>> From: Rick Bragg [mailto:li...@gmnet.net]
> >>> Subject: RE: Cyclos Webapp Trouble (404)
> >>>
> >>> Yes I notices that as well, I forgot to post
Rick Bragg wrote:
> On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote:
>
>>> From: Rick Bragg [mailto:li...@gmnet.net]
>>> Subject: RE: Cyclos Webapp Trouble (404)
>>>
>>> Yes I notices that as well, I forgot to post my cyclos.properies Here
>>> is the "mysql" section...
>>>
>>> hibe
> From: Rick Bragg [mailto:li...@gmnet.net]
> Subject: RE: Cyclos Webapp Trouble (404)
>
> Error connecting to database at
> jdbc:mysql://127.0.0.1:3306/cyclos
You've still got some inconsistencies in your posts. You've stated that you're
installing Tomcat+cyclos on a brand new machine, yet you
On Mon, 2010-01-18 at 08:23 -0600, Caldarale, Charles R wrote:
> > From: Rick Bragg [mailto:li...@gmnet.net]
> > Subject: RE: Cyclos Webapp Trouble (404)
> >
> > Yes I notices that as well, I forgot to post my cyclos.properies Here
> > is the "mysql" section...
> >
> > hibernate.connection.url =
> From: Rick Bragg [mailto:li...@gmnet.net]
> Subject: RE: Cyclos Webapp Trouble (404)
>
> Yes I notices that as well, I forgot to post my cyclos.properies Here
> is the "mysql" section...
>
> hibernate.connection.url = jdbc:mysql://127.0.0.1:3306/cyclos
The above doesn't jibe with the error mes
On Mon, 2010-01-18 at 07:42 -0600, Caldarale, Charles R wrote:
> > From: Rick Bragg [mailto:li...@gmnet.net]
> > Subject: RE: Cyclos Webapp Trouble (404)
> >
> > Error connecting to database at jdbc:mysql://localhost/cyclos3
>
> Besides verifying that MySQL is actually running as David suggested,
Rick Bragg wrote:
> On Mon, 2010-01-18 at 07:39 -0500, David Smith wrote:
>
>>> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
>>> Communications link failure
>>>
>> To me this looks like it's outside of tomcat. Check that mysql is up,
>> listening on tcp port 3306
On Mon, 2010-01-18 at 07:39 -0500, David Smith wrote:
> >
> > Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> > Communications link failure
> To me this looks like it's outside of tomcat. Check that mysql is up,
> listening on tcp port 3306 (the standard mysql port) and ther
2010/1/18 iainmac :
>
> Hi,
>
> I am upgrading from Tomcat 5 to 6.
>
> When developing I run Tomcat from the command line so I can see the debug as
> it happens, but with Tomcat 6 I can see the debug that I have coded but when
> there is a Tomcat exception, it doesn't appear in the command line win
> From: iainmac [mailto:iain_macau...@hotmail.com]
> Subject: Stack Trace debug to screen
>
> I am upgrading from Tomcat 5 to 6.
Platform?
JVM version?
Precise Tomcat versions?
Changes to the default logging.properties?
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE P
> From: Rick Bragg [mailto:li...@gmnet.net]
> Subject: RE: Cyclos Webapp Trouble (404)
>
> Error connecting to database at jdbc:mysql://localhost/cyclos3
Besides verifying that MySQL is actually running as David suggested, note that
there's a mismatch in the cyclos installation instructions comp
Hi,
I am upgrading from Tomcat 5 to 6.
When developing I run Tomcat from the command line so I can see the debug as
it happens, but with Tomcat 6 I can see the debug that I have coded but when
there is a Tomcat exception, it doesn't appear in the command line window
any more although it is in th
>
> Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException:
> Communications link failure
To me this looks like it's outside of tomcat. Check that mysql is up,
listening on tcp port 3306 (the standard mysql port) and there aren't
any firewalls causing problems between tomcat and mysql
Rick Bragg wrote:
...
I think maybe my JDBC permissions are not quite right, or there is something
with the driver, but I'm not sure...
A very quick way to see if the security manager has anything to do with
this, is to turn it off temporarily.
Undr Ubuntu, if it is like Debian, there is prob
45 matches
Mail list logo
