RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-22 Thread Iván Escobedo
Wade, I have new information, I tried to replicate this problem with both tomcats at 
my home, and I found two issues:

1.  Tomcat 5.0.27 only works in standalone mode.
2.  Both Tomcats work only if it access a User DNS; at my job, it works weather I 
use a System or User DNS.



-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 03:50 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:
 Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
 start it in service mode and now it works.  What the...?
 I really don't know what happened, i just now that now it works.
 
 Any insights?
 
 -Mensaje original-
 De: Robert Bateman [mailto:[EMAIL PROTECTED]
 Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
 Para: Tomcat Users List
 Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025
 
 Ivan,
 
 It may not be a jar issue.  One of the problems with running something as a 
 service in Windows is that the program must know it's a service and log into and 
 network drives or data bases itself.  Do you have your data source set to read a 
 file on a networked drive?
 
 Bob
 
 
 On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:
 
Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
be that the service doesnn't load some jars? Another thing you have to 
know is that the app is accesing a System DNS .

 
 
 
 -
 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]
 
 
 
I don't have any real idea other than maybe there was a file that tomcat probably was 
not able to create...one that may have been created by running it in standalone mode.

Maybe it wasn't able to create a certain temp file or what ever under it's own working 
directories and somehow that caused it to pass invalid info to the underlying odbc 
driver.

That's about the only thing I can think of.  Since you ran it as the your user and 
created a file it may have then been able to read it though it wasn't able to create 
it.

I would have to see all the code in tomcat and the code inside of the jdbc odbc bridge 
classes and trace down in it to be sure, but usually it is something like that when it 
comes to security and an app working after running it as another user with more 
privileges.

One thing is for sure...it wasn't magic...just allusive.  ;-)

Wade


-
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: Problem with jdbc:odbc in Tomcat 5.025

2004-07-22 Thread Wade Chandler
Iván Escobedo wrote:
Wade, I have new information, I tried to replicate this problem with both tomcats at 
my home, and I found two issues:
1.  Tomcat 5.0.27 only works in standalone mode.
2.  Both Tomcats work only if it access a User DNS; at my job, it works weather I use a 
System or User DNS.

-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 03:50 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:
Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
start it in service mode and now it works.  What the...?
I really don't know what happened, i just now that now it works.
Any insights?
-Mensaje original-
De: Robert Bateman [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025
Ivan,
It may not be a jar issue.  One of the problems with running something as a 
service in Windows is that the program must know it's a service and log into and network drives or data 
bases itself.  Do you have your data source set to read a file on a networked drive?
Bob
On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:

Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
be that the service doesnn't load some jars? Another thing you have to 
know is that the app is accesing a System DNS .


-
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]

I don't have any real idea other than maybe there was a file that tomcat probably 
was not able to create...one that may have been created by running it in standalone 
mode.
Maybe it wasn't able to create a certain temp file or what ever under it's own working 
directories and somehow that caused it to pass invalid info to the underlying odbc 
driver.
That's about the only thing I can think of.  Since you ran it as the your user and 
created a file it may have then been able to read it though it wasn't able to create 
it.
I would have to see all the code in tomcat and the code inside of the jdbc odbc bridge 
classes and trace down in it to be sure, but usually it is something like that when it 
comes to security and an app working after running it as another user with more 
privileges.
One thing is for sure...it wasn't magic...just allusive.  ;-)
Wade
-
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]

Do you mean TC 5.0.27 only works against a User DNS even in standalone 
mode?  Just clarifying.  Is anyone else reading this thread getting the 
same type of an error that might be able to help out by adding some more 
detail to this thread.  I think it definitely boils down to a security 
issue.

Did you use the TC installer for windows, or did you unzip the tomcat 
installation and setup the service manually?  I would track down which 
user is the owner of the running service.  Then I would give that user 
permissions to the tomcat server directories (recursively).  See if that 
helps anything.  Also be sure that user has at least read access to your 
entire JVM directory (recursively) and can write to any temp directories 
setup for that user.

One time I had to give a user access to certain areas of the registry 
for some odbc stuff I was working on.  This may be what is happening to 
you as well.  I was using ODBC, Access, and nameless ODBC entries.

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


RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-22 Thread Shapira, Yoav

Hi,
I doubt many people are reading this thread, because jdbc:odbc is generally cruisin' 
for a bruisin', something always breaks.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Wade Chandler [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 22, 2004 3:10 PM
To: Tomcat Users List
Subject: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:

 Wade, I have new information, I tried to replicate this problem with both
tomcats at my home, and I found two issues:

 1.  Tomcat 5.0.27 only works in standalone mode.
 2.  Both Tomcats work only if it access a User DNS; at my job, it works
weather I use a System or User DNS.



 -Mensaje original-
 De: Wade Chandler [mailto:[EMAIL PROTECTED]
 Enviado el: Miércoles, 21 de Julio de 2004 03:50 p.m.
 Para: Tomcat Users List
 Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

 Iván Escobedo wrote:

Ok, something happened after i started the Tomcat 5.0.27 in standalone,
'cause now i start it in service mode and now it works.  What the...?
I really don't know what happened, i just now that now it works.

Any insights?

-Mensaje original-
De: Robert Bateman [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Ivan,

It may not be a jar issue.  One of the problems with running
something as a service in Windows is that the program must know it's a
service and log into and network drives or data bases itself.  Do you have
your data source set to read a file on a networked drive?

Bob


On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:


Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it
be that the service doesnn't load some jars? Another thing you have to
know is that the app is accesing a System DNS .




-
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]




 I don't have any real idea other than maybe there was a file that tomcat
probably was not able to create...one that may have been created by running
it in standalone mode.

 Maybe it wasn't able to create a certain temp file or what ever under
it's own working directories and somehow that caused it to pass invalid
info to the underlying odbc driver.

 That's about the only thing I can think of.  Since you ran it as the your
user and created a file it may have then been able to read it though it
wasn't able to create it.

 I would have to see all the code in tomcat and the code inside of the
jdbc odbc bridge classes and trace down in it to be sure, but usually it is
something like that when it comes to security and an app working after
running it as another user with more privileges.

 One thing is for sure...it wasn't magic...just allusive.  ;-)

 Wade


 -
 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]



Do you mean TC 5.0.27 only works against a User DNS even in standalone
mode?  Just clarifying.  Is anyone else reading this thread getting the
same type of an error that might be able to help out by adding some more
detail to this thread.  I think it definitely boils down to a security
issue.

Did you use the TC installer for windows, or did you unzip the tomcat
installation and setup the service manually?  I would track down which
user is the owner of the running service.  Then I would give that user
permissions to the tomcat server directories (recursively).  See if that
helps anything.  Also be sure that user has at least read access to your
entire JVM directory (recursively) and can write to any temp directories
setup for that user.

One time I had to give a user access to certain areas of the registry
for some odbc stuff I was working on.  This may be what is happening to
you as well.  I was using ODBC, Access, and nameless ODBC entries.

Wade


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




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

RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-22 Thread Iván Escobedo
I used the installer version of TC 5.0.27 in my home, tonight i'm gonna make the test 
of the privileges and tomorrow i'll have an answer 

-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Jueves, 22 de Julio de 2004 01:10 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:

 Wade, I have new information, I tried to replicate this problem with both tomcats at 
 my home, and I found two issues:
 
 1.  Tomcat 5.0.27 only works in standalone mode.
 2.  Both Tomcats work only if it access a User DNS; at my job, it works weather I 
 use a System or User DNS.
 
 
 
 -Mensaje original-
 De: Wade Chandler [mailto:[EMAIL PROTECTED]
 Enviado el: Miércoles, 21 de Julio de 2004 03:50 p.m.
 Para: Tomcat Users List
 Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025
 
 Iván Escobedo wrote:
 
Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
start it in service mode and now it works.  What the...?
I really don't know what happened, i just now that now it works.

Any insights?

-Mensaje original-
De: Robert Bateman [mailto:[EMAIL PROTECTED]
Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Ivan,

It may not be a jar issue.  One of the problems with running something as a 
service in Windows is that the program must know it's a service and log into and 
network drives or data bases itself.  Do you have your data source set to read a 
file on a networked drive?

Bob


On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:


Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
be that the service doesnn't load some jars? Another thing you have 
to know is that the app is accesing a System DNS .




-
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]



 
 I don't have any real idea other than maybe there was a file that tomcat probably 
 was not able to create...one that may have been created by running it in standalone 
 mode.
 
 Maybe it wasn't able to create a certain temp file or what ever under it's own 
 working directories and somehow that caused it to pass invalid info to the 
 underlying odbc driver.
 
 That's about the only thing I can think of.  Since you ran it as the your user and 
 created a file it may have then been able to read it though it wasn't able to create 
 it.
 
 I would have to see all the code in tomcat and the code inside of the jdbc odbc 
 bridge classes and trace down in it to be sure, but usually it is something like 
 that when it comes to security and an app working after running it as another user 
 with more privileges.
 
 One thing is for sure...it wasn't magic...just allusive.  ;-)
 
 Wade
 
 
 -
 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]
 
 
 
Do you mean TC 5.0.27 only works against a User DNS even in standalone mode?  Just 
clarifying.  Is anyone else reading this thread getting the same type of an error that 
might be able to help out by adding some more detail to this thread.  I think it 
definitely boils down to a security issue.

Did you use the TC installer for windows, or did you unzip the tomcat installation and 
setup the service manually?  I would track down which user is the owner of the running 
service.  Then I would give that user permissions to the tomcat server directories 
(recursively).  See if that helps anything.  Also be sure that user has at least read 
access to your entire JVM directory (recursively) and can write to any temp 
directories setup for that user.

One time I had to give a user access to certain areas of the registry for some odbc 
stuff I was working on.  This may be what is happening to you as well.  I was using 
ODBC, Access, and nameless ODBC entries.

Wade


-
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: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Wade Chandler
:520)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Martes, 20 de Julio de 2004 03:15 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:

Hello guys I have a question, I have two tomcats. 4.1.30 and 5.0.27, both with the 
same application, they are both similar and connect to a MSAccess database thru Jdbc 
Odbc bridge, however, in 4.1.30 everything works, but in 5.0.27 i have this message 
when I try to connect to the database.
I have searched for the answer, but until now i don't know what's the problem, could 
you help me?
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found 
and no default driver specified
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)
at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.crstore.admin.AdminDbBean.getDescriptors(AdminDbBean.java:50)
at org.apache.jsp.jsp.Menu_jsp._jspService(Menu_jsp.java:118)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jsp.jsp.Default_jsp._jspService(Default_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at com.crstore.core.Shopper.doPost(Shopper.java:95)
at com.crstore.core.Shopper.doGet(Shopper.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157

RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Iván Escobedo
Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it be that the 
service doesnn't load some jars? Another thing you have to know is that the app is 
accesing a System DNS .

-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 06:13 a.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:

 Ok, thanks for replying,
 
 First, both tomcats are running on the same machine, but not at the same time, i 
 just wanted to prove to myself that something's changed in Tomcat 5.
 
 Second, Tomcat 4 is running as a standalone, and the other one as a service, and at 
 first I was using a user level DNS, but now i'm using a System DNS, and I have a new 
 error.
 
 Third, they are using the exact same configuration.
 
 This is the new error:
 
 java.sql.SQLException: General error
   at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6987)
   at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
   at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)
   at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
   at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
   at java.sql.DriverManager.getConnection(DriverManager.java:512)
   at java.sql.DriverManager.getConnection(DriverManager.java:171)
   at com.crstore.admin.AdminDbBean.getDescriptors(AdminDbBean.java:50)
   at org.apache.jsp.jsp.Menu_jsp._jspService(Menu_jsp.java:118)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
   at org.apache.jsp.jsp.Default_jsp._jspService(Default_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
   at 
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
   at 
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
   at com.crstore.core.Shopper.doPost(Shopper.java:95)
   at com.crstore.core.Shopper.doGet(Shopper.java:64)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
   at 
 org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at 
 org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
   at 
 org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
   at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
   at 
 org.apache.catalina.core.StandardHostValve.invoke

Re: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Robert Bateman
Ivan,

It may not be a jar issue.  One of the problems with running something as 
a service in Windows is that the program must know it's a service and log 
into and network drives or data bases itself.  Do you have your data source 
set to read a file on a networked drive?

Bob


On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:
 Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it be
 that the service doesnn't load some jars? Another thing you have to know is
 that the app is accesing a System DNS .



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



RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Iván Escobedo
Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
start it in service mode and now it works.  What the...?
I really don't know what happened, i just now that now it works.

Any insights?

-Mensaje original-
De: Robert Bateman [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Ivan,

It may not be a jar issue.  One of the problems with running something as a 
service in Windows is that the program must know it's a service and log into and 
network drives or data bases itself.  Do you have your data source set to read a file 
on a networked drive?

Bob


On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:
 Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
 be that the service doesnn't load some jars? Another thing you have to 
 know is that the app is accesing a System DNS .



-
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: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Wade Chandler
Iván Escobedo wrote:
Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
start it in service mode and now it works.  What the...?
I really don't know what happened, i just now that now it works.
Any insights?
-Mensaje original-
De: Robert Bateman [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Ivan,
It may not be a jar issue.  One of the problems with running something as a 
service in Windows is that the program must know it's a service and log into and network drives or data 
bases itself.  Do you have your data source set to read a file on a networked drive?
Bob
On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:
Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
be that the service doesnn't load some jars? Another thing you have to 
know is that the app is accesing a System DNS .


-
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]

I don't have any real idea other than maybe there was a file that tomcat 
probably was not able to create...one that may have been created by 
running it in standalone mode.

Maybe it wasn't able to create a certain temp file or what ever under 
it's own working directories and somehow that caused it to pass invalid 
info to the underlying odbc driver.

That's about the only thing I can think of.  Since you ran it as the 
your user and created a file it may have then been able to read it 
though it wasn't able to create it.

I would have to see all the code in tomcat and the code inside of the 
jdbc odbc bridge classes and trace down in it to be sure, but usually it 
is something like that when it comes to security and an app working 
after running it as another user with more privileges.

One thing is for sure...it wasn't magic...just allusive.  ;-)
Wade
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-21 Thread Iván Escobedo
Jajaja, ok Wade and Robert, thanks for your help

-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Miércoles, 21 de Julio de 2004 03:50 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:
 Ok, something happened after i started the Tomcat 5.0.27 in standalone, 'cause now i 
 start it in service mode and now it works.  What the...?
 I really don't know what happened, i just now that now it works.
 
 Any insights?
 
 -Mensaje original-
 De: Robert Bateman [mailto:[EMAIL PROTECTED]
 Enviado el: Miércoles, 21 de Julio de 2004 02:38 p.m.
 Para: Tomcat Users List
 Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025
 
 Ivan,
 
 It may not be a jar issue.  One of the problems with running something as a 
 service in Windows is that the program must know it's a service and log into and 
 network drives or data bases itself.  Do you have your data source set to read a 
 file on a networked drive?
 
 Bob
 
 
 On Wednesday 21 July 2004 04:30 pm, Iván Escobedo wrote:
 
Yes Wade, I started Tomcat 5.1 as a standalone and it works, could it 
be that the service doesnn't load some jars? Another thing you have to 
know is that the app is accesing a System DNS .

 
 
 
 -
 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]
 
 
 
I don't have any real idea other than maybe there was a file that tomcat probably was 
not able to create...one that may have been created by running it in standalone mode.

Maybe it wasn't able to create a certain temp file or what ever under it's own working 
directories and somehow that caused it to pass invalid info to the underlying odbc 
driver.

That's about the only thing I can think of.  Since you ran it as the your user and 
created a file it may have then been able to read it though it wasn't able to create 
it.

I would have to see all the code in tomcat and the code inside of the jdbc odbc bridge 
classes and trace down in it to be sure, but usually it is something like that when it 
comes to security and an app working after running it as another user with more 
privileges.

One thing is for sure...it wasn't magic...just allusive.  ;-)

Wade


-
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]



Problem with jdbc:odbc in Tomcat 5.025

2004-07-20 Thread Iván Escobedo
Hello guys I have a question, I have two tomcats. 4.1.30 and 5.0.27, both with the 
same application, they are both similar and connect to a MSAccess database thru Jdbc 
Odbc bridge, however, in 4.1.30 everything works, but in 5.0.27 i have this message 
when I try to connect to the database.

I have searched for the answer, but until now i don't know what's the problem, could 
you help me?


java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found and 
no default driver specified
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)
at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.crstore.admin.AdminDbBean.getDescriptors(AdminDbBean.java:50)
at org.apache.jsp.jsp.Menu_jsp._jspService(Menu_jsp.java:118)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jsp.jsp.Default_jsp._jspService(Default_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at com.crstore.core.Shopper.doPost(Shopper.java:95)
at com.crstore.core.Shopper.doGet(Shopper.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 

Re: Problem with jdbc:odbc in Tomcat 5.025

2004-07-20 Thread Wade Chandler
Iván Escobedo wrote:
Hello guys I have a question, I have two tomcats. 4.1.30 and 5.0.27, both with the 
same application, they are both similar and connect to a MSAccess database thru Jdbc 
Odbc bridge, however, in 4.1.30 everything works, but in 5.0.27 i have this message 
when I try to connect to the database.
I have searched for the answer, but until now i don't know what's the problem, could 
you help me?
java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found 
and no default driver specified
at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)
at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.crstore.admin.AdminDbBean.getDescriptors(AdminDbBean.java:50)
at org.apache.jsp.jsp.Menu_jsp._jspService(Menu_jsp.java:118)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
at 
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
at 
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
at org.apache.jsp.jsp.Default_jsp._jspService(Default_jsp.java:102)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
at com.crstore.core.Shopper.doPost(Shopper.java:95)
at com.crstore.core.Shopper.doGet(Shopper.java:64)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at 

RE: Problem with jdbc:odbc in Tomcat 5.025

2004-07-20 Thread Iván Escobedo
)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)

-Mensaje original-
De: Wade Chandler [mailto:[EMAIL PROTECTED] 
Enviado el: Martes, 20 de Julio de 2004 03:15 p.m.
Para: Tomcat Users List
Asunto: Re: Problem with jdbc:odbc in Tomcat 5.025

Iván Escobedo wrote:

 Hello guys I have a question, I have two tomcats. 4.1.30 and 5.0.27, both with the 
 same application, they are both similar and connect to a MSAccess database thru Jdbc 
 Odbc bridge, however, in 4.1.30 everything works, but in 5.0.27 i have this message 
 when I try to connect to the database.
 
 I have searched for the answer, but until now i don't know what's the problem, could 
 you help me?
 
 
 java.sql.SQLException: [Microsoft][ODBC Driver Manager] Data source name not found 
 and no default driver specified
   at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6958)
   at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7115)
   at sun.jdbc.odbc.JdbcOdbc.SQLDriverConnect(JdbcOdbc.java:3074)
   at sun.jdbc.odbc.JdbcOdbcConnection.initialize(JdbcOdbcConnection.java:323)
   at sun.jdbc.odbc.JdbcOdbcDriver.connect(JdbcOdbcDriver.java:174)
   at java.sql.DriverManager.getConnection(DriverManager.java:512)
   at java.sql.DriverManager.getConnection(DriverManager.java:171)
   at com.crstore.admin.AdminDbBean.getDescriptors(AdminDbBean.java:50)
   at org.apache.jsp.jsp.Menu_jsp._jspService(Menu_jsp.java:118)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590)
   at 
 org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:510)
   at 
 org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:966)
   at org.apache.jsp.jsp.Default_jsp._jspService(Default_jsp.java:102)
   at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
   at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
   at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
   at 
 org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:704)
   at 
 org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:474)
   at 
 org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:409)
   at 
 org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:312)
   at com.crstore.core.Shopper.doPost(Shopper.java:95)
   at com.crstore.core.Shopper.doGet(Shopper.java:64)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157