This week's book giveaways are in the Scala and Android forums.
We're giving away four copies each of Machine Learning Systems: Designs that scale and Xamarin in Action: Creating native cross-platform mobile apps and have the authors on-line!
See this thread and this one for details.
Win a copy of Machine Learning Systems: Designs that scale this week in the Scala forum
or Xamarin in Action: Creating native cross-platform mobile apps in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Here's a fun one...  RSS feed

 
Ranch Hand
Posts: 238
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
{this may be a websphere question, but here it goes...}
I have a servlet that was running fine last week. Now, when I try to run it (running on a test server in WebSphere Application Developer Studio 4) I can compile the servlet, run a JSP form to pass the data to the servlet, and it creates an HTML file for display of the information it pulls from a database.
The fun part is that when I go back (using history.back() )to the jsp page and submit a new query, I get the following message:
[5/28/02 11:02:25:859 EDT] 22538893 SystemOut U The url cannot be null
If I recompile the servlet (or restart the server), it works once then does the same thing again...
Any thoughts?

[ May 28, 2002: Message edited by: Sam Smoot ]
 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If the query string has some association with particular session ID, then using a bookmarked url may cause issues.
 
Sam Smoot
Ranch Hand
Posts: 238
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The servlet calls a loader class that calls a connection class that connects to the database. I'm not sure, but I think the connection is not invoked at each request, but only on the first request so that subsequent calls do not get the information from the properties file.
Does this sound correct?
The ConnFactory.class connects to the database.
this is the code:


This is the dbConnect.properties file:
 
Sam Smoot
Ranch Hand
Posts: 238
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ok.. we figger'd it out... Our connection manager wasn't passing the connect string on the second pass. It thought it was already initialized.
Maby next time I'll know what I'm doing? :roll:
[ May 29, 2002: Message edited by: Sam Smoot ]
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!