RE: two users see the same session

[Bill Lunnon]

Nikhil,

I have seen this problem occur when using JSP and incorrectly defining
session variables or beans in the declaration part of the script.

e.g

<%!
BeanClass bean = new BeanClass();
%>

Make sure only initialise session variables or bean classes
in the context scope

ie
<%
BeanClass bean = new BeanClass();
%>

Would suggest visual inspection of all code and JSP pages to make sure this
is not occuring!

Hope this helps


Bill
-Original Message-
From: Nikhil G. Daddikar [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 November 2003 4:03 PM
To: [EMAIL PROTECTED]
Subject: two users see the same session


Hello Folks,

Sometimes our users get to see information stored in the session of
another user. We've verified this because they have sent us screen captures.

The question is how? We have one server, one tomcat (4.1.27), and we use
the default i.e. cookie based sessions.

If anyone of you can shed some light on this or tell me how to prevent
this, that will be great.

Thanks for your time.
Nikhil


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Form Double Submit Detection

[Bill Lunnon]

Tom,
Don't know if this is complimentary to your workflow,
try a javascript confirm (ie a client side pop-up, asking the user to click
"Ok" to continue). This will catch any double clicks on the client side.

Hope this helps

Bill

-Original Message-
From: Tom Parker [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 28 October 2003 10:18 AM
To: [EMAIL PROTECTED]
Subject: Form Double Submit Detection


I've designed my workflows so that they do not need to store anything in
the user's session. This allows the user to conduct more than one
instance of a particular task at the same time without data getting
mixed up. However this presents me with a problem if the user double
clicks the submit button and causes the server to do something twice.

The normal(?) way of detecting this would be to store a unique token in
the session and in the form, and compare them to ensure that the user
has not submitted this form twice. For this to work, you need to store
something in the session for each possible form submission. If the user
never submits the form, then the token will hang around for the life of
the session as we don't know that the user won't submit the form
someday.

Currently I'm thinking of allowing the user to store a finite number of
duplicate check tokens, or to make the tokens expire after an amount of
time. The former doesn't seem very attractive (load a record, view a
bunch of other records such that the first record's token is dropped,
save the first record - no token found), while the latter could lead to
rather a lot of tokens being stored.

Is there a solution to this problem that I'm missing?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JSP seems to be executing twice and we are getting duplicate records in our database

[Bill Lunnon]

Adrian,

If you do not want anothe rows created every time the page is submitted,
then you are going to have to implement something to stop this. TOMCAT will
not do this for you.

Without knowing the requirements for the form, stopping multiple rows being
generated could be as simple as:
- Assign a session to the user (clients browser).
- When the form is submitted, capture the sessionId in the database with the
record.
- If there is no row with the sessionId in the database, create a new record
with an insert. If there is a existing session, use an update to modify the
record.


Hope this helps

Bill

-Original Message-
From: Adrian Beech [mailto:[EMAIL PROTECTED]
Sent: Monday, 4 August 2003 8:45 PM
To: [EMAIL PROTECTED]
Subject: JSP seems to be executing twice and we are getting duplicate
records in our database


Hi folks,

We have a weird problem where a JSP seems to be executing twice and we are
getting duplicate records in our database.  The data is coming from a HTML
form and upon submit a subsequent JSP page is called that performs the SQL
insert, etc.  We are also getting duplicate log messages so our initial
conclusion is that it's a Tomcat related issue.

We have tested this with Tomcat 3.3.1, J2SE 1.3.1 and from the client side
using both IE 5.5 and 6.0 and it happens intermittently.

At this stage we have absolutely no idea of what is going on.  Alas I didn't
write the code so I'm not up to speed with its structure, flow or
functionality.

I've searched the list archive and there appears to be several references to
similar problems.  However I am unable to find any real answer to what might
be causing this problem.

Hoping someone out yonder can help.

AB



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Help required

[Bill Lunnon]

There is an exception thrown in "price_jsp.java:414"

I assume this is something that has been developed for the project.



-Original Message-
From: Veena K.S [mailto:[EMAIL PROTECTED]
Sent: Friday, 25 July 2003 4:37 PM
To: '[EMAIL PROTECTED]'
Subject: Help required


Hi all,
We have a website hosted on tomcat4.1.12 .We are facing the
following problem when the site is up for a long time and the pages does not
load end up with a blank page , but the log file has the entry as stack
trace given below
What could be the reason for this and what could be the possible solution to
rectify this problem?

Thanks in advance
regds,
Veena

2003-07-25 13:31:38 StandardWrapperValve[jsp]: Servlet.service() for servlet
jsp threw exception
org.apache.jasper.JasperException
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
48)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:260)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.
java:170)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172
)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:641)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:174)
at
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok
eNext(StandardPipeline.java:643)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:256)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:361)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:563)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:535)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:638)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:533)
at java.lang.Thread.run(Thread.java:479)
- Root Cause -
javax.servlet.ServletException
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp
l.java:497)
at org.apache.jsp.price_jsp._jspService(price_jsp.java:414)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:136)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:2
04)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:289)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:240)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
v

RE: Tomcat destoying beans

[Bill Lunnon]

Dominic,

You haven't set the session in the page declaration
<[EMAIL PROTECTED] session=true ...


Hope this helps

Bill

-Original Message-
From: Dominic Parry [mailto:[EMAIL PROTECTED]
Sent: Monday, 9 June 2003 7:00 PM
To: Tomcat Users List
Subject: Tomcat destoying beans


Hi

After I call a servlet that accesses two beans created in a jsp, the beans
seem to have been destroyed.

They are created like this:

<%@ page import="beans.*"%>



this page then response.sendRedirect("MyServlet");

code in MyServlet:

 session = req.getSession();
 UserAuth authBean = (beans.UserAuth) session.getAttribute("authBean");
 DataBean dataBean = (beans.DataBean) session.getAttribute("dataBean");

I am able to access these beans in the servlet, but once it has finished
execution, they seem to have been garbage collected!

What am I missing?!

Thanks

Dom


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: I need a good driver for SQL Server

[Bill Lunnon]

Try JSQLConnect at www.j-netdirect.com , I found it very useful with
SQLServer

Bill

-Original Message-
From: Victor Gonzalez [mailto:[EMAIL PROTECTED]
Sent: Friday, 14 March 2003 8:55 AM
To: 'Tomcat Users List'; [EMAIL PROTECTED]
Subject: I need a good driver for SQL Server
Importance: High


Hi all,

I need a good driver and how to realize the connection to SQL Server
2000
from Tomcat 4.1.18,

Tnks all,

Regards,

Victor Gonzalez
***


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Pls help me !! Urgent!

[Bill Lunnon]

Zafar,

You need to test for the null after you have retrived the parameter from the
query, via jdbc ResultSet.wasNull()

Code might look like

CallableStatement cs;
// setup the callable statement stuff prior to here
ResultSet rs = cs.executeQuery();

while (rs.next()) {
String param = rs.getString(pos);
if (rs.wasNull() == true) {
// set preferred param value
param = "0"; // or ""
}
}

Hope this helps

Bill
-Original Message-
From: zafar Ahsan [mailto:[EMAIL PROTECTED]
Sent: Monday, 10 March 2003 6:16 PM
To: [EMAIL PROTECTED]
Subject: Pls help me !! Urgent!


hello
Can any one pls let me know how to deals with null that result set returns
when quering from an oracle database. its display "null" when using
rset.getString() method and i want it to be either 0 or " "(nothing).Am
novice to java and tomcat and null being a special literal in java cosing me
problem to get up to my work.
I would be very thankful for yr kind help.
And if don't mind pls let me also know how to start tomcat server through
windows server2000 services.
Md. Zafar Ahsan


_
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Share Java resources between two (or more) servlets

[Bill Lunnon]

Andreas,

Firstly, the servlet with db connections should be created and added to the
ServletContext (hence not really a servlet). All other servlets can than
access this object via getServletContext.getAttribute() etc.
This servlet is defined as a servlet, loaded on initialisation. You must
release that the init() method of this servlet can be called multiple times,
especially if web.xml is changed. To avoid any dramas, make sure that the
init() is singleton (ie it only operates once). Same applies to the
destroy()

To be safe, make sure the get() and post() methods of the servlet do
something like redirect the response to another web page.

I know this approach works.

Hope this helps

Bill
-Original Message-
From: Andreas Byström [mailto:[EMAIL PROTECTED]
Sent: Friday, 7 March 2003 9:20 PM
To: Tomcat Users
Subject: Share Java resources between two (or more) servlets


Hi all!

I'm writing an application that uses (for now) 4 different servlets. I would
like all these servlets to share some java singelton object. Is this
possible? Do all servlets share the same jvm instance and thereby uses the
same singelton object?

I have one servlet that is set to load-on-startup, this servlet will create
the java object (db connections and other stuff) that I want all servlets to
share later on. This servlet is not used anymore, it hust listens for
shutdown and will not receive any requests. Is this how you should solve a
initialization problem or is there some other way?

When I run my application I start this servlet  (servlet1) as above. But
when I then invoke another servlet, servlet2, (that is not set to
load-on-startup) there is a strange behavior. Using my traces I can read
that it first invokes init on servlet1 again and then init on servlet2. If I
then sends a first reuquest to servlet3 it just does init on servlet3. If I
instead had sent the first request to 3 before the first request to servlet2
it is the same behavior but vice versa. when the request comes to servlet3
it does init on first 1 nd then 3. The request to servlet 2 now just incokes
init on servlet2. Have anyone a clue of you it can be like this?

// Andreas


Andreas Bystrom
Computer Engineer

e-horizon Streaming Technologies
Stadshusplatsen 2, 4th floor
Box 172
SE 14922 Nynashamn

mail  : [EMAIL PROTECTED]
web   : www.e-horizon.se
phone : +46 8 524 201 80
mobile: +46 708 85 23 35



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JSPs sometimes don't recompile

[Bill Lunnon]

Sounds like a browser cache problem,
to get around this, simply add some other parameters to the url
(e.g http://foo.com/some_servlet?param=value&dummy=fred)

hope this helps

Bill

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, 28 February 2003 6:44 AM
To: [EMAIL PROTECTED]
Subject: JSPs sometimes don't recompile



We are running Tomcat 3.2.4 and occasionly experience problems with JSPs
not recompiling after thay have been modified.  In the latest instance, a
single new JSP (not an "included" file) was placed out on the server. Upon
testing the change, it was determined that Tomcat was serving up the old
file.  A couple of things were tried. First, we simply touched the file in
an effort to force it to be recompiled. No luck.  Then we deleted the file
to see if we would get a 404.  The old file was still being served up by
Tomcat.  Looking in the work  directory, there was no trace of the
offending JSP.  No .java file, no .class file.  How can Tomcat still be
serving up the file when it is not even there?



This e-mail may contain data that is confidential, proprietary or
"non-public
personal information", as that term is defined in the Gramm-Leach-Bliley Act
(collectively, "Confidential Information"). The Confidential Information is
disclosed conditioned upon your agreement that you will treat it
confidentially and in accordance with applicable law, ensure that such data
isn't used or disclosed except for the limited purpose for which it's being
provided and will notify and cooperate with us regarding any requested or
unauthorized disclosure or use of any Confidential Information. By accepting
and reviewing the Confidential Information you agree to indemnify us against
any losses or expenses, including attorney's fees that we may incur as a
result of any unauthorized use or disclosure of this data due to your acts
or
omissions. If a party other than the intended recipient receives this
e-mail,
you are requested to instantly notify us of the erroneous delivery and
return
to us all data so delivered.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Form based security and "Remember Me"

[Bill Lunnon]

A thought (just started following the thread).

I can see a problem, in that the cookies may never get initialised because
of the use of the checkbox. If the checkbox hasn't been selected, you'll
always receive null from the form.

Would suggest using a radio button instead, where the parameter will always
return a value (null is definitely an error).

Hope this is relevant to the thread

Bill

-Original Message-
From: John Trollinger [mailto:[EMAIL PROTECTED]]
Sent: Friday, 21 February 2003 7:32 AM
To: 'Tomcat Users List'
Subject: RE: Form based security and "Remember Me"


But does this work with Form based authenticaiton and realms... How do
you let the realm know that the user remembered so the login can be
bypassed?

John

> -Original Message-
> From: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 20, 2003 3:23 PM
> To: Tomcat Users List
> Subject: RE: Form based security and "Remember Me"
>
>
>
> Howdy,
> I'm not doing this, and I'm one of those people who cleans
> their cache every time their browser is closed (12Ghosts auto
> wash is among the greatest tools I've ever seen for any
> computing purpose, ever), so Remember Me functionality
> doesn't typically work for me, but...
>
> >Is anyone doing this at all?  And if so how?
>
> Assuming remember me is a checkbox, e.g.
> Remember Me
>
> Then something like:
> String rememberUserString = request.getParameter("rememeberUser");
> if((rememebrUserString != null) &&
>(rememeberUserString.equalsIgnoreCase("true")) {
>  //  Create cookie
>  Cookie userInfoCookie = new Cookie(...);
>  response.addCookie(userInfoCookie);
> }
>
> Then other pages in the app attempt to retrieve the cookie (using
> request.getCookies() and iterating through the cookies.  You
> can retrieve the information in a fairly cross-browser,
> server-independent way.
>
> You can also set attributes in the session
> (HttpSession.setAttribute("myUserName", username) or
> whatever) or do it in many other ways.
>
> Yoav Shapira
> Millennium ChemInformatics
>
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged.  This e-mail is
> intended only for the individual(s) to whom it is addressed,
> and may not be saved, copied, printed, disclosed or used by
> anyone else.  If you are not the(an) intended recipient,
> please immediately delete this e-mail from your computer
> system and notify the sender.  Thank you.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: How to enable secured JSP to be cached by browser?

[Bill Lunnon]

Adam,

Even if you could do this (and it is not recommended!!!) the caching is not
going to solve the problem, each browser implements its own and different
caching policy.

The better way to do this is populate the form before the data is
re-displayed to the user (a two phase approach).
Scriplet may look like this

<%
somebean Bean = null;   // bean used to read/write the form data
String enteredParam = null;
boolean haveEntered = false; // set to true if the user has entered form
data
%>

<%
enteredParam = "":
if (haveEntered == true) {
enteredParam = somebean.getEnteredValue();
}
%>


Hope this helps

Bill
-Original Message-
From: Szwajkajzer Adam [mailto:[EMAIL PROTECTED]]
Sent: Friday, 14 February 2003 10:18 PM
To: [EMAIL PROTECTED]
Subject: How to enable secured JSP to be cached by browser?


Hi all.
I'm using Tomcat 4.1.18 (in boundle with JBoss 3.0.5).
My application is configured to use declarative security (FORM based).
Here my problems start.
Each HTTP respons for secured JSP page gets amend by Tomcat.
Additional header Pragma, Cache-Control and Expires entries are inserted
to prevent the page to be locally cached.
I've found on that list it is performed by AuthenticatorBase class and was
added
to prevent security vulnerability.

The problem is with form pages in following scenario:
User inserts data, submits form, server returns an application error.
User returns to form page but it is reread from server and of course it's
empty.
(User gets angry while retyping all form data;)

Since the application is only used in intranet it would be acceptable to
locally cache
secured JSP pages.
So, is it possible to switch off  no-cache/expires feature in Tomcat 4.1.18?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: strange response.getAttribute problem

[Bill Lunnon]

Try
request.getParameter()
also
you should test for null on the parameter (it will probably cause a
NullPointerException down the line)

HTH

Bill

-Original Message-
From: Erik Price [mailto:[EMAIL PROTECTED]]
Sent: Friday, 24 January 2003 9:16 AM
To: Tomcat Users List
Subject: strange response.getAttribute problem


In my index.jsp file, I have the following snippet of code:

" />

I'm trying to capture the value of the "dest" URL parameter.  I tried
setting it as an attribute in the response object that redirects to
index.jsp, and that didn't work.  But I thought for sure that if I
hardcoded it into the URL, it would work.  Strangely, if I call
index.jsp with the following URL:

domain.com:8080/webapp/index.jsp?dest=/test/path

Then the JSP renders as such:





any idea why the GET attribute's not getting pulled into the JSP?


Thanks,

Erik


--
To unsubscribe, e-mail:

For additional commands, e-mail:



--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Form Data & IE vs NS

[Bill Lunnon]

[Suggestion]
Don't rely on browsers to retain the previous data on a a posted form.
If you have detected an error, retrieve the data that was posted (via
request.getParamter()) and populate the form yourself.

Sample scriptlet could be

<%
String lastFoo = "";
//error detected, haveError set to true
if (haveError == true) {
lastFoo = request.getParameter("foo");
}
%>
mailto:[EMAIL PROTECTED]]
Sent: Friday, 24 January 2003 8:14 AM
To: Tomcat-User@Jakarta. Apache. Org (E-mail)
Subject: Form Data & IE vs NS


[problem]
Form data not retained using back operation in IE v6.0.2800.1160 after a
form is posted but a required field was missing. Versions of IE prior to
this would allow the retention of form data.

[info]
Netscape v7.0 retains the data after an unsuccessful post and the back
button is used to return.

[System]
Tomcat 4.0.4 (using built-in HTTP connector) on SuSE Linux 8.1
MySQL database 3.x
Servlet application using JDBC.

Any ideas as to why the above version of IE doesn't keep form data in cache
would be very appreciated.

Thanks,

Kevin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: Start tomcat before apache on RedHat7.3

[Bill Lunnon]

-Original Message-
From: news [mailto:[EMAIL PROTECTED]]On Behalf Of Arcadius A.
Sent: Wednesday, 15 January 2003 1:13 AM
To: [EMAIL PROTECTED]
Subject: Re: Start tomcat before apache on RedHat7.3



"Turner, John" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> Then the delay shouldn't need to be more than 5 or 10 seconds.
>

Ok John,
I'm not asking you to do the whole thing for me
but could you give me an example of a script that could do what you're
talking about?

This problem is realy strange I have TomCat 3.2 running on FreeBSD with
apache3.27 and mod_jk (automatic config)  when I reboot, tomcat and
apache start quite fine without the need of any special script  but I
cannot see why I'm having troubles on RedHat.

regards.


Have attached a copy of my /etc/rc.d/init.d/httpd file.
It starts TOMCAT (3.3.1) and apache(1.3.27)
and stops the other way.

Hope this helps

Bill

--
To unsubscribe, e-mail:

For additional commands, e-mail:




httpd
Description: Binary data
--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: session /application in servlets

[Bill Lunnon]

Paul,

Getting the error because "application" is a JSP default object for
javax.Servlet.ServletContext

If you want to put someting in the servlet context, use something like

this.getServletContext.setAttribute()

Not too sure about the correct method names,but you should get the idea

Bill

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: Monday, 25 November 2002 4:01 PM
To: Tomcat Users List
Subject: session /application in servlets


Hi,
Pertaining to recent posts, can someone please describe how
session or application are defined in a servlet please? In JSP syntax
there is no problem but in the method in the .java servlet below:

public class LoadMyServletAtStartup implements ServletContextListener {

  public void contextInitialized(ServletContextEvent sce) {

Hashtable style_index = new Hashtable();

style_index.put("element1", "ONE");
style_index.put("element2", "TWO");

application.setAttribute("style_index", style_index);

}

it is failing to compile:

unable to resolve symbol
application.setAttribute("style_index", style_index);
^
1 Error

many thanks for your help

Paul.





--
To unsubscribe, e-mail:   
For additional commands, e-mail: