Hi,
If security is your main concern, you should really consider 2.6:
Technologies like AppArmor are are giving a lot of confidence.
And you have intrusion detection included.
And IMHO you have no long term alternative to using current and maintained
software.
R.
Am Dienstag, 13. März 2007 12
Hi,
does your tomcat instance really use JRE 1.6 ?
You can easily check in the manager app.
Anyway I would suggest to always use
-source 1.4 -target 1.4
for older Classes, because you avoid all possible syntax problems.
Other combinations of source/target could be tested if you suspect a javac
. Any review, retransmission, dissemination or other use of, or
> taking of any action in reliance upon, this information by persons or
> entities other than the intended recipient is prohibited. If you received
> this in error, please contact the sender and delete this message.
>
>
&
lot for any advice
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Reinhard Moosauer
IT Beratung
---
Hi,
you can mimimize http traffic by correctly linking to
http://localhost:8080/mytestapp/?qa=1 (with the slash)
Please consider that "mytestapp" should be seen as a directory by the browser.
And your first url is wrong (strictly speaking), so Tomcat tries to fix it by
a redirect.
I see no r
Hi,
the outbound address is determined from the routing on OS level.
Fix your routes and the outgoing address is ok also.
If this is not possible, you can resort to NAT (network address translation).
This solution is used very widely.
regards,
R.
Am Dienstag, 13. Juni 2006 14:56 schrieb Panos
Hi,
please consider the following:
- Error 403 seems completely suitable from your words
- Browsers always store Login Info until the browser windows is closed
(No session here, this applies only to basic-auth!)
With form auth: you can alyways provide a logout-button
- If Standard-errorpage
Or even better:
change "class=.." to "type=.."
class means: this class can be instantiated
type means: This attribute has been set before and should not be instantiated
(List cannot anyway because its an interface)
Since Tomcat 5 the JSP compiler checks this to reduce runtime errors.
Am Donners
Hi,
please do not mix up the tomcat cluster and apache load balancing.
Sticky session means that tomcat2 is not used at all in your configuration.
Only tomcat1, which created the cookie.
When tomcat2 creates no session, the browser gets none and the lb-worker
cannot work also. Maybe your apps/c
Hi again,
this sounds like you should use apache for that.
Are you using a specific download manager on the client side?
Note you can always configure tomcat to serve content outside of webapps. Just
use context.xml-Configuration:
http://tomcat.apache.org/tomcat-5.5-doc/deployer-howto.html
-->"A
Hi,
Sun's JDK contains am small Java-App called 'jconsole'.
You can run it remotely after configuring your tomcat like this:
http://tomcat.apache.org/tomcat-5.5-doc/monitoring.html (Enabling JMX Remote)
Consider reading the JDK-docs also.
Real memory usage can be understood much better with this
Hi,
this sounds like "repackage" would be a huge job.
If yes, I would suggest: learn ant
If not: You have to reload the apps anyway. So what do you achieve?
just my 2 cents.
R.
Am Freitag, 24. März 2006 16:19 schrieb Fran Varin:
> Yes, that is the exact situation we are attempting to avoid in T
worker.worker2.cachesize=10
> worker.worker2.cache_timeout=600
> worker.worker2.socket_keepalive=1
> worker.worker2.reclycle_timeout=300
>
>
>
> virtual host for greenlight
>
> JkLogFile /var/log/apache2/mod_jk.log
> JkMount /servlets/* worker2
>
>
Hi,
please check your browser. I think you have cookies disabled for any reason.
(or cookies are disabled in your tomcat app)
yould check with ethereal or try using cookie-less mode with
response.encodeURL(hyperlink)
hope this helps
R.
Am Freitag, 17. März 2006 13:35 schrieb Vahid Hedayati:
>
ox without creating dirs and
setting permissions.
Reinhard
Am Dienstag, 14. März 2006 16:29 schrieb Peter Rossbach:
> Please open a bug report,
> then we can better discuss the issue.
>
> Peter
>
> Am 14.03.2006 um 16:21 schrieb Reinhard Moosauer:
> > Hi Peter,
> >
&
is that option (serialize sessions) in the
> manager or in the admin ? Or it is a value that need to be changed manually
> in server.xml or any props file ?
>
> Thanks
>
> Rodrigo Asensio
>
> -Original Message-
> From: Reinhard Moosauer [mailto:[EMAIL PROTECTED
> This feature is important do guaranty a clear state after change the
> binary. Feel free to open
> an enhancement bug report, and feel free to add a patch. The current
> behaviour is
> correct for production sites.
>
> Peter
>
> Am 14.03.2006 um 15:03 schrieb Reinhard Moosa
uency apps)
Formerly, the persisted session data survived the remove, so I could
re-install the app.
Please help!
Reinhard
Am Dienstag, 14. März 2006 13:53 schrieb Reinhard Moosauer:
> Hello List,
>
> recently I upgraded from tomcat 5.5.9 to 5.5.15
> Since then, all my sessions are lost
Hello List,
recently I upgraded from tomcat 5.5.9 to 5.5.15
Since then, all my sessions are lost after a remove/install via the manager.
The problem is the following:
I installed a war-file, which is copied to the webapps-folder during
manager-install. When I want to replace the war with a new v
Hi Poorna,
you must have access to the manager-application. Otherwise you could not
deploy/restart your webapp. Don't you?
If you have access to the manager-webapp, you can deploy a context.xml-file
along with your realm. Please see
http://yourserver:8080/manager/html/
->Install->XML config UR
Hi List,
it seemed clear to me, that this construct:
... (some inner logic)
should be equivalent to this one:
<%
for (Iterator it=t.getRecords(); it.hasNext(); ) {
String x = (String)it.next();
%>
... (some inner logic)
<% }
%>
But the forEach-version is not wor
21 matches
Mail list logo
