You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Steve Ingraham <si...@okcca.net> on 2008/01/09 19:50:35 UTC

problem with data input

I hope I am able to explain this problem adequately.  If I have gaps in
my explanation let me know and I will attempt to clarify further.  I
know enough about Tomcat to be dangerous, as they say.  I hope you guys
might be able to help me so here goes.
 
We have a MySQL database that we input case information into using a web
based application written in Java and running in Apache Tomcat 5.1.5.15.
On Monday one of our users was attempting to input some data into a
specific section of the database but the data was not stored.  This is,
so far, only happening in this one specific area of data entry that
inputs data into a specific table in the database.  We receive well over
100 new court filings that occur every day.  We have multiple users
inputting data into the new cases and existing cases every day
throughout the day.  So most of the data input is operating normally.
It is just input into this one area that I am seeing problems.  It could
be there are other areas with problems but we just haven't seen them
yet.  Whatever the case may be though, at present it is this one area
where I am seeing the problem.
 
I have been able to log into the database using MySQL Query Browser
1.1.6 and insert the data into the appropriate field for that record in
the table.  When I input that data I can then log into the web
application, navigate to that case and see the entry showing up as I
just entered it.  However, if I try to alter that data from the web
application nothing happens.
 
I had attempted to send this to the thread earlier with attached copies
of two logs for Monday and for Tuesday.  I never was able to see my post
on the thread so I am resending in the belief that my attachments may
have been cause for the forum to block my post.  If I need to post logs
please let me know what is the best way to send my logs.
 
Can someone assist me with finding out what may be causing this problem
and give some idea of how to resolve it?
 
Thanks,
Steve
 

RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Wednesday, January 09, 2008 3:37 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > > > running in Apache Tomcat 5.1.5.15.
> > > 
> > > No such level; what are you really running?  Also, what OS
> > > and what JVM?
> > 
> > I am not sure then what version of Tomcat.  How can I find this 
> > information?
> 
> You just did, in your message below.  Note that 5.5.15 != 5.1.5.15.
>  
> > Using CATALINA_BASE:   /home/movedfromusr/apache-tomcat-5.5.15
> > Using CATALINA_HOME:   /home/movedfromusr/apache-tomcat-5.5.15
> > Using CATALINA_TMPDIR: /home/movedfromusr/apache-tomcat-5.5.15/temp
> > Using JRE_HOME:       /usr/java/jdk1.5.0_04
> 
> > What is JVM?
> 
> Java Virtual Machine.  You have level 1.5.0_04 installed.
> 
> > How can I check to see if they are making it to the database server?
> 
> Usually by turning on traces on the db server or using 
> something like Wireshark to watch the network traffic between 
> your Tomcat and db server boxes.
> 
Ok, the MySQL database resides on the same server as Java and Tomcat.  I
ran netstat -an about two hours ago and saw this:

[root@dellapp01 bin]# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address               Foreign Address
State
tcp        0      0 0.0.0.0:8000                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:32768               0.0.0.0:*
LISTEN
tcp        0      0 127.0.0.1:32769             0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:6051                0.0.0.0:*
LISTEN
tcp        0      0 127.0.0.1:8005              0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:8009                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:32777               0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:3306                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:111                 0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:8080                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:6000                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:10000               0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:22                  0.0.0.0:*
LISTEN
tcp        0      0 127.0.0.1:631               0.0.0.0:*
LISTEN
tcp        0      0 127.0.0.1:25                0.0.0.0:*
LISTEN
tcp        0      0 0.0.0.0:1311                0.0.0.0:*
LISTEN
tcp        0      0 172.16.255.100:57557        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:58997        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59004        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59025        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59026        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59030        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59036        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59041        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59046        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59055        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59060        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59064        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59067        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59069        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59071        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59072        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59074        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59077        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59078        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59081        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59082        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59083        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59084        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59085        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59087        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59088        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59089        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59091        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59092        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59093        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59094        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59099        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59100        172.16.255.100:3306
TIME_WAIT
tcp        0      0 172.16.255.100:59102        172.16.255.100:3306
TIME_WAIT
tcp        0      0 127.0.0.1:34709             127.0.0.1:34708
TIME_WAIT
tcp        0      0 127.0.0.1:631               127.0.0.1:32785
ESTABLISHED
tcp        0      0 127.0.0.1:34701             127.0.0.1:8080
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59024
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59051
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59040
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59068
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59079
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59075
TIME_WAIT
tcp        0      0 172.16.255.100:3306         172.16.255.100:59101
TIME_WAIT
tcp        0      0 127.0.0.1:32785             127.0.0.1:631
ESTABLISHED
udp        0      0 0.0.0.0:32768               0.0.0.0:*
udp        0      0 0.0.0.0:10000               0.0.0.0:*
udp        0      0 0.0.0.0:6051                0.0.0.0:*
udp        0      0 0.0.0.0:810                 0.0.0.0:*
udp        0      0 0.0.0.0:41524               0.0.0.0:*
udp        0      0 0.0.0.0:111                 0.0.0.0:*
udp        0      0 0.0.0.0:631                 0.0.0.0:*
udp        0      0 172.16.255.100:123          0.0.0.0:*
udp        0      0 127.0.0.1:123               0.0.0.0:*
udp        0      0 0.0.0.0:123                 0.0.0.0:*
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ACC ]     STREAM     LISTENING     17896
/tmp/.ICE-unix/5397
unix  2      [ ACC ]     STREAM     LISTENING     17764
/tmp/ssh-OQef5397/agent.5397
unix  2      [ ACC ]     STREAM     LISTENING     17488
/tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     6259
/tmp/.font-unix/fs7100
unix  2      [ ACC ]     STREAM     LISTENING     6055   /tmp/mysql.sock
unix  2      [ ACC ]     STREAM     LISTENING     17945
/tmp/.fam_socket
unix  2      [ ACC ]     STREAM     LISTENING     17478
/tmp/.gdm_socket
unix  2      [ ACC ]     STREAM     LISTENING     6167   /dev/gpmctl
unix  13     [ ]         DGRAM                    3426   /dev/log
unix  2      [ ACC ]     STREAM     LISTENING     17780
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  2      [ ACC ]     STREAM     LISTENING     17788
/tmp/orbit-root/linc-1515-0-60dc8e69cc56b
unix  2      [ ACC ]     STREAM     LISTENING     17906
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  2      [ ACC ]     STREAM     LISTENING     17927
/tmp/orbit-root/linc-156c-0-21d75a075187c
unix  2      [ ACC ]     STREAM     LISTENING     17985
/tmp/orbit-root/linc-1578-0-2d41b8534526a
unix  2      [ ACC ]     STREAM     LISTENING     18013
/tmp/orbit-root/linc-157c-0-53f3b92d94a76
unix  2      [ ACC ]     STREAM     LISTENING     18032
/tmp/orbit-root/linc-157e-0-53f3b92da2aba
unix  2      [ ACC ]     STREAM     LISTENING     18052
/tmp/orbit-root/linc-157a-0-53f3b92dabffb
unix  2      [ ACC ]     STREAM     LISTENING     18078
/tmp/orbit-root/linc-1582-0-53f3b92dc64f4
unix  2      [ ACC ]     STREAM     LISTENING     18109
/tmp/orbit-root/linc-1580-0-53f3b92de08dd
unix  2      [ ACC ]     STREAM     LISTENING     18121
/tmp/orbit-root/linc-1584-0-53f3b92de2bc2
unix  2      [ ACC ]     STREAM     LISTENING     18283
/tmp/orbit-root/linc-15b1-0-5999656c44450
unix  2      [ ACC ]     STREAM     LISTENING     130297
/tmp/orbit-root/linc-1bea-0-247de6a5a34d4
unix  2      [ ACC ]     STREAM     LISTENING     9818
/etc/delloma.d/oma/omintf1064
unix  2      [ ACC ]     STREAM     LISTENING     7058
/etc/delloma.d/oma/omsad
unix  2      [ ]         DGRAM                    234873
unix  3      [ ]         STREAM     CONNECTED     130310
/tmp/orbit-root/linc-157a-0-53f3b92dabffb
unix  3      [ ]         STREAM     CONNECTED     130309
unix  3      [ ]         STREAM     CONNECTED     130308
/tmp/orbit-root/linc-1bea-0-247de6a5a34d4
unix  3      [ ]         STREAM     CONNECTED     130307
unix  3      [ ]         STREAM     CONNECTED     130304
/tmp/orbit-root/linc-1bea-0-247de6a5a34d4
unix  3      [ ]         STREAM     CONNECTED     130303
unix  3      [ ]         STREAM     CONNECTED     130302
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     130301
unix  3      [ ]         STREAM     CONNECTED     130300
/tmp/orbit-root/linc-1bea-0-247de6a5a34d4
unix  3      [ ]         STREAM     CONNECTED     130299
unix  3      [ ]         STREAM     CONNECTED     130296
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     130295
unix  3      [ ]         STREAM     CONNECTED     130289
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     130288
unix  3      [ ]         STREAM     CONNECTED     18299
/tmp/orbit-root/linc-157e-0-53f3b92da2aba
unix  3      [ ]         STREAM     CONNECTED     18298
unix  3      [ ]         STREAM     CONNECTED     18297
/tmp/orbit-root/linc-15b1-0-5999656c44450
unix  3      [ ]         STREAM     CONNECTED     18296
unix  3      [ ]         STREAM     CONNECTED     18291
/tmp/orbit-root/linc-15b1-0-5999656c44450
unix  3      [ ]         STREAM     CONNECTED     18290
unix  3      [ ]         STREAM     CONNECTED     18289
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     18288
unix  3      [ ]         STREAM     CONNECTED     18286
/tmp/orbit-root/linc-15b1-0-5999656c44450
unix  3      [ ]         STREAM     CONNECTED     18285
unix  3      [ ]         STREAM     CONNECTED     18282
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18281
unix  3      [ ]         STREAM     CONNECTED     18275
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18274
unix  3      [ ]         STREAM     CONNECTED     18221
unix  3      [ ]         STREAM     CONNECTED     18220
unix  3      [ ]         STREAM     CONNECTED     18192  /tmp/.famNVCKwT
unix  3      [ ]         STREAM     CONNECTED     18191
unix  3      [ ]         STREAM     CONNECTED     18182  /tmp/.famryEbUy
unix  3      [ ]         STREAM     CONNECTED     18181
unix  3      [ ]         STREAM     CONNECTED     18149
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18148
unix  3      [ ]         STREAM     CONNECTED     18143  /tmp/.famD0ggke
unix  3      [ ]         STREAM     CONNECTED     18142
unix  3      [ ]         STREAM     CONNECTED     18135
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18134
unix  3      [ ]         STREAM     CONNECTED     18130
/tmp/orbit-root/linc-1584-0-53f3b92de2bc2
unix  3      [ ]         STREAM     CONNECTED     18129
unix  3      [ ]         STREAM     CONNECTED     18128
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     18127
unix  3      [ ]         STREAM     CONNECTED     18126
/tmp/orbit-root/linc-1580-0-53f3b92de08dd
unix  3      [ ]         STREAM     CONNECTED     18125
unix  3      [ ]         STREAM     CONNECTED     18124
/tmp/orbit-root/linc-1584-0-53f3b92de2bc2
unix  3      [ ]         STREAM     CONNECTED     18123
unix  3      [ ]         STREAM     CONNECTED     18120
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18119
unix  3      [ ]         STREAM     CONNECTED     18118
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     18117
unix  3      [ ]         STREAM     CONNECTED     18116
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18115
unix  3      [ ]         STREAM     CONNECTED     18113
/tmp/orbit-root/linc-1580-0-53f3b92de08dd
unix  3      [ ]         STREAM     CONNECTED     18112
unix  3      [ ]         STREAM     CONNECTED     18106
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18105
unix  3      [ ]         STREAM     CONNECTED     18102
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18101
unix  3      [ ]         STREAM     CONNECTED     18103
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18100
unix  3      [ ]         STREAM     CONNECTED     18089
/tmp/.X11-unix/X0
unix  11     [ ]         STREAM     CONNECTED     18088
unix  3      [ ]         STREAM     CONNECTED     18081
/tmp/orbit-root/linc-1582-0-53f3b92dc64f4
unix  3      [ ]         STREAM     CONNECTED     18080
unix  3      [ ]         STREAM     CONNECTED     18077
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18076
unix  3      [ ]         STREAM     CONNECTED     18075
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18074
unix  3      [ ]         STREAM     CONNECTED     18073
/tmp/orbit-root/linc-157a-0-53f3b92dabffb
unix  3      [ ]         STREAM     CONNECTED     18069
unix  3      [ ]         STREAM     CONNECTED     18066
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     18065
unix  3      [ ]         STREAM     CONNECTED     18064
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18063
unix  3      [ ]         STREAM     CONNECTED     18055
/tmp/orbit-root/linc-157a-0-53f3b92dabffb
unix  3      [ ]         STREAM     CONNECTED     18054
unix  3      [ ]         STREAM     CONNECTED     18051
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18050
unix  3      [ ]         STREAM     CONNECTED     18049
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18048
unix  3      [ ]         STREAM     CONNECTED     18042
/tmp/orbit-root/linc-157e-0-53f3b92da2aba
unix  3      [ ]         STREAM     CONNECTED     18041
unix  3      [ ]         STREAM     CONNECTED     18040
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18039
unix  3      [ ]         STREAM     CONNECTED     18038
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     18037
unix  3      [ ]         STREAM     CONNECTED     18035
/tmp/orbit-root/linc-157e-0-53f3b92da2aba
unix  3      [ ]         STREAM     CONNECTED     18034
unix  3      [ ]         STREAM     CONNECTED     18031
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18030
unix  3      [ ]         STREAM     CONNECTED     18029
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18028
unix  3      [ ]         STREAM     CONNECTED     18022
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18021
unix  3      [ ]         STREAM     CONNECTED     18016
/tmp/orbit-root/linc-157c-0-53f3b92d94a76
unix  3      [ ]         STREAM     CONNECTED     18015
unix  3      [ ]         STREAM     CONNECTED     18012
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     18011
unix  3      [ ]         STREAM     CONNECTED     18010
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     18009
unix  3      [ ]         STREAM     CONNECTED     18003
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     18002
unix  3      [ ]         STREAM     CONNECTED     17992
/tmp/.ICE-unix/5397
unix  3      [ ]         STREAM     CONNECTED     17991
unix  3      [ ]         STREAM     CONNECTED     17990
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     17989
unix  3      [ ]         STREAM     CONNECTED     17988
/tmp/orbit-root/linc-1578-0-2d41b8534526a
unix  3      [ ]         STREAM     CONNECTED     17987
unix  3      [ ]         STREAM     CONNECTED     17984
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     17983
unix  3      [ ]         STREAM     CONNECTED     17977
/tmp/orbit-root/linc-156c-0-21d75a075187c
unix  3      [ ]         STREAM     CONNECTED     17976
unix  3      [ ]         STREAM     CONNECTED     17973
/tmp/orbit-root/linc-156c-0-21d75a075187c
unix  3      [ ]         STREAM     CONNECTED     17972
unix  3      [ ]         STREAM     CONNECTED     17971
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     17970
unix  3      [ ]         STREAM     CONNECTED     17951  /tmp/.famFxQ7fU
unix  3      [ ]         STREAM     CONNECTED     17950
unix  3      [ ]         STREAM     CONNECTED     17930
/tmp/orbit-root/linc-156c-0-21d75a075187c
unix  3      [ ]         STREAM     CONNECTED     17929
unix  3      [ ]         STREAM     CONNECTED     17926
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     17925
unix  3      [ ]         STREAM     CONNECTED     17919
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     17918
unix  3      [ ]         STREAM     CONNECTED     17913
/tmp/orbit-root/linc-1515-0-60dc8e69cc56b
unix  3      [ ]         STREAM     CONNECTED     17912
unix  3      [ ]         STREAM     CONNECTED     17911
/tmp/orbit-root/linc-156a-0-1372b3833fb27
unix  3      [ ]         STREAM     CONNECTED     17910
unix  3      [ ]         STREAM     CONNECTED     17880
/tmp/orbit-root/linc-1515-0-60dc8e69cc56b
unix  3      [ ]         STREAM     CONNECTED     17879
unix  3      [ ]         STREAM     CONNECTED     17878
/tmp/orbit-root/linc-1567-0-28cf4f3dbe6f2
unix  3      [ ]         STREAM     CONNECTED     17787
unix  2      [ ]         DGRAM                    17779
unix  3      [ ]         STREAM     CONNECTED     17774
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     17773
unix  3      [ ]         STREAM     CONNECTED     17579
/tmp/.font-unix/fs7100
unix  3      [ ]         STREAM     CONNECTED     17578
unix  4      [ ]         STREAM     CONNECTED     17581
/tmp/.X11-unix/X0
unix  3      [ ]         STREAM     CONNECTED     17491
unix  2      [ ]         DGRAM                    15771
unix  2      [ ]         DGRAM                    14188
unix  2      [ ]         DGRAM                    6270
unix  2      [ ]         DGRAM                    6153
unix  2      [ ]         DGRAM                    6128
unix  2      [ ]         DGRAM                    6114
unix  2      [ ]         DGRAM                    5919
unix  2      [ ]         DGRAM                    5891
unix  2      [ ]         DGRAM                    3490
unix  2      [ ]         DGRAM                    3434
[root@dellapp01 bin]#

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> > > running in Apache Tomcat 5.1.5.15.
> > 
> > No such level; what are you really running?  Also, what OS 
> > and what JVM?
> 
> I am not sure then what version of Tomcat.  How can I find this
> information?

You just did, in your message below.  Note that 5.5.15 != 5.1.5.15.
 
> Using CATALINA_BASE:   /home/movedfromusr/apache-tomcat-5.5.15
> Using CATALINA_HOME:   /home/movedfromusr/apache-tomcat-5.5.15
> Using CATALINA_TMPDIR: /home/movedfromusr/apache-tomcat-5.5.15/temp
> Using JRE_HOME:       /usr/java/jdk1.5.0_04

> What is JVM?

Java Virtual Machine.  You have level 1.5.0_04 installed.

> How can I check to see if they are making it to the database server?

Usually by turning on traces on the db server or using something like
Wireshark to watch the network traffic between your Tomcat and db server
boxes.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Thursday, January 10, 2008 12:18 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > If you have the time to walk me through this could you
> > direct me on where and how I turn on debugging for the
> > webapp and/or the database?
> 
> Sorry, all that depends on the actual webapp and the DB 
> you're using. Might be time to hire a consultant...
> 

When you refer to "webapp" are you talking about Tomcat or Java or
something else?  The database is a MySQL database.  MySQL, Java, Tomcat
are all running on the same server.

If there is a consultant that could look at this I would welcome the
opportunity to talk with them.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> If you have the time to walk me through this could you 
> direct me on where and how I turn on debugging for the
> webapp and/or the database?

Sorry, all that depends on the actual webapp and the DB you're using.
Might be time to hire a consultant...

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Thursday, January 10, 2008 11:00 AM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > I have checked the WEB-INF/lib for other duplicated .jar
> > files.  I have not seen any.
> 
> Good.
> 
> > What is the next step for troubleshooting the problem?
> 
> You'll need to trace what's going on in the webapp and the 
> database when attempts are made to update the area in 
> question.  Your DB most likely has some form of debugging 
> capability that you can enable, hopefully with some filtering 
> capability that will avoid generating tons of irrelevant 
> traces.  Also, if there's any debugging or logging built into 
> the webapp of interest, turn that on.  If all else fails, put 
> logging (or print) statements in the webapp to see what's 
> really going on when this particular kind of data is being 
> entered.  The webapp could be generating ill-formed SQL, 
> sending it to the DB, and eating any exceptions generated; 
> many other failure modes are also possible, but you'll need 
> information from within the webapp and DB to find out what.
> 
Ok, I understand about getting more information on this.  However, I
lack the knowledge to go about doing so without some assistance.  This
is a system that I have inherited and that I just marginally understand.
I can work through the steps necessary to do what you are talking about
but I do not know what those steps are, where to go to do them or how to
go about doing them without some guidance.  If you have the time to walk
me through this could you direct me on where and how I turn on debugging
for the webapp and/or the database?

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> I have checked the WEB-INF/lib for other duplicated .jar 
> files.  I have not seen any.

Good.

> What is the next step for troubleshooting the problem?

You'll need to trace what's going on in the webapp and the database when
attempts are made to update the area in question.  Your DB most likely
has some form of debugging capability that you can enable, hopefully
with some filtering capability that will avoid generating tons of
irrelevant traces.  Also, if there's any debugging or logging built into
the webapp of interest, turn that on.  If all else fails, put logging
(or print) statements in the webapp to see what's really going on when
this particular kind of data is being entered.  The webapp could be
generating ill-formed SQL, sending it to the DB, and eating any
exceptions generated; many other failure modes are also possible, but
you'll need information from within the webapp and DB to find out what.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Sent: Wednesday, January 09, 2008 7:30 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
> Sent: Wed 1/9/2008 5:02 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
>  
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > So I can look in
> > /usr/local/tomcat/common/lib and any duplicates of those in 
> > /usr/local/tomcat/webapps/occa/WEB-INF/lib I will remove.
> > 
> > Am I thinking about this correctly?
> 
> Yes.  Just remember this is getting rid of the noise so we 
> can better find the cause of the real problem, since I doubt 
> this is it.
> 
> Thought I would log on from home and check the mail list.  I 
> will look at this first thing when I get in.  Once I clear 
> those up what should be the next thing to do?
> 

Charles,
I have checked the WEB-INF/lib for other duplicated .jar files.  I have
not seen any.  What is the next step for troubleshooting the problem?

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.


-----Original Message-----
From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
Sent: Wed 1/9/2008 5:02 PM
To: Tomcat Users List
Subject: RE: problem with data input
 
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> So I can look in
> /usr/local/tomcat/common/lib and any duplicates of those in
> /usr/local/tomcat/webapps/occa/WEB-INF/lib I will remove.  
> 
> Am I thinking about this correctly? 

Yes.  Just remember this is getting rid of the noise so we can better
find the cause of the real problem, since I doubt this is it.

Thought I would log on from home and check the mail list.  I will look at this first thing when I get in.  Once I clear those up what should be the next thing to do?


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> So I can look in
> /usr/local/tomcat/common/lib and any duplicates of those in
> /usr/local/tomcat/webapps/occa/WEB-INF/lib I will remove.  
> 
> Am I thinking about this correctly? 

Yes.  Just remember this is getting rid of the noise so we can better
find the cause of the real problem, since I doubt this is it.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Wednesday, January 09, 2008 4:21 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > So If there is a jar not loaded where should it be?
> 
> No one said there was a jar not being loaded - just that you 
> have at least one jar in WEB-INF/lib that should be removed.  
> Tomcat usually figures out that it should ignore such 
> duplications, but in the interests of getting things as clean 
> as possible so the real problem can be uncovered, get rid of 
> it.

Ok, I understand now.  I have removed "servlet-api-2.3.jar" from
/usr/local/tomcat/webapps/occa/WEB-INF/lib/.



>  If you find any others in WEB-INF/lib that appear to be 
> duplicates of ones in Tomcat's common/lib or server/lib 
> directories, the extra ones in WEB-INF/lib should be 
> discarded as well (ask first if you're not comfortable doing 
> so on your own).
> 
There are a tub load of "jar" files in that directory.  So I can look in
/usr/local/tomcat/common/lib and any duplicates of those in
/usr/local/tomcat/webapps/occa/WEB-INF/lib I will remove.  However, I do
not want to remove anything without knowing which ones first so I will
ask: Am I thinking about this correctly? 

I appreciate your time and efforts assisting me.  I am at the end of my
shift so I will not be able to reply until tomorrow to any other posts
on this but would appreciate the opportunity to continue with this
tomorrow.  I will look for any new posts first thing.

Thanks,
Steve

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> So If there is a jar not loaded where should it be?

No one said there was a jar not being loaded - just that you have at
least one jar in WEB-INF/lib that should be removed.  Tomcat usually
figures out that it should ignore such duplications, but in the
interests of getting things as clean as possible so the real problem can
be uncovered, get rid of it.  If you find any others in WEB-INF/lib that
appear to be duplicates of ones in Tomcat's common/lib or server/lib
directories, the extra ones in WEB-INF/lib should be discarded as well
(ask first if you're not comfortable doing so on your own).

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Wednesday, January 09, 2008 3:33 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: RE: problem with data input
> > 
> > validateJarFile(/usr/local/tomcat/webapps/occa/WEB-INF/lib/
> > servlet-api-2.3.jar) - jar not loaded.
> 
> No servlet-api jar should be part of a webapp.  The servlet 
> API classes are provided by Tomcat (and every other app 
> server on the market).  Take it out of WEB-INF/lib; also 
> remove any other jars from WEB-INF/lib that are versions of 
> ones Tomcat provides.
> 
> > Jan 7, 2008 7:48:09 AM org.keel.clients.KeelClientUtil getLogger
> > WARNING: Unable to locate client.properties file - using default 
> > settings
> 
> Who provides org.keel.clients?  You may need to be talking to them.
>
All of the Tomcat, Java, org.keel., etc. was developed in house by a guy
who is no longer here.  He created everything that is currently in
place.  I do not have access to him in order to address these issues so
that leaves me trying to explore this without really knowing what the
heck I am doing.  I know enough about this stuff to tell you things that
are probably not necessarily so (i.e. the version of Tomcat we are
running).  So basically you are talking to a novice in terms of all of
this.  Prior to Monday things were working without any glitches.  I do
not know what might have occurred Monday to change things but something
happened.  I do not have enough knowledge to know what I am seeing let
alone where to see it.

Ughhh.  So If there is a jar not loaded where should it be?  How do I
see it and/or go fix what may be broken in order to have it load
properly?   Why would it have not loaded on Monday when it appears it
was properly functioning prior to Monday?  Perhaps I am delving into
things I can only make worse with my inexperience.

I really do not know where to start. 

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: RE: problem with data input
> 
> validateJarFile(/usr/local/tomcat/webapps/occa/WEB-INF/lib/
> servlet-api-2.3.jar) - jar not loaded.

No servlet-api jar should be part of a webapp.  The servlet API classes
are provided by Tomcat (and every other app server on the market).  Take
it out of WEB-INF/lib; also remove any other jars from WEB-INF/lib that
are versions of ones Tomcat provides.

> Jan 7, 2008 7:48:09 AM org.keel.clients.KeelClientUtil getLogger
> WARNING: Unable to locate client.properties file - using default
> settings

Who provides org.keel.clients?  You may need to be talking to them.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
Ok, I am not having much luck resolving my problem.  I am including some
information from the logs I have below.

Here is some of the content for a log from 01-07-2008:

Jan 7, 2008 7:46:51 AM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
Jan 7, 2008 7:46:52 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Jan 7, 2008 7:46:55 AM org.apache.coyote.http11.Http11BaseProtocol
destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080
Jan 7, 2008 7:46:55 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: Failed shutdown of Apache Portable Runtime
Jan 7, 2008 7:47:24 AM org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the java.library.path:
/usr/java/jdk1.5.0_04/jre/lib/i386/server:/usr/java/jdk1.5.0_04/jre/lib/
i386:/usr/java/jdk1.5.0_04/jre/../lib/i386:/opt/CA/SharedComponents/lib
Jan 7, 2008 7:47:25 AM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Jan 7, 2008 7:47:25 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 2759 ms
Jan 7, 2008 7:47:25 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Jan 7, 2008 7:47:25 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
Jan 7, 2008 7:47:25 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Jan 7, 2008 7:47:27 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive occa.war
Jan 7, 2008 7:47:28 AM org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/usr/local/tomcat/webapps/occa/WEB-INF/lib/servlet-api-2
.3.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending
class: javax/servlet/Servlet.class
Jan 7, 2008 7:47:39 AM org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Jan 7, 2008 7:47:39 AM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Jan 7, 2008 7:47:39 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/56  config=null
Jan 7, 2008 7:47:39 AM org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
Jan 7, 2008 7:47:39 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 14136 ms
Jan 7, 2008 7:48:09 AM org.keel.clients.KeelClientUtil getLogger
WARNING: Unable to locate client.properties file - using default
settings
Jan 7, 2008 7:48:09 AM org.keel.clients.DefaultClientConnector logInfo
INFO: Struts Client Connector starting.
Jan 7, 2008 7:48:09 AM org.keel.clients.DefaultClientConnector logInfo
INFO: Configuring Client 1
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 7:48:18 AM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.

This last part goes on all day with this showing up around 12:17 pm:
Jan 7, 2008 12:17:47 PM org.keel.clients.DefaultClientConnector logError
SEVERE: Stack for error from oscn.seq.promptUpdateCaseMaster, Key:
'InvalidStatenoatissuedate Message: Submitted date without At Issue
date.
org.keel.services.model.ModelException: Application Error
	at
org.keel.services.model.defaultmodel.DefaultModelResponse.addError(Defau
ltModelResponse.java:322)
	at
org.keel.services.model.defaultmodel.DefaultModelResponse.addErrors(Defa
ultModelResponse.java:403)
	at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.avalon.fortress.impl.factory.PassThroughInvocationHandler.inv
oke(PassThroughInvocationHandler.java:68)
	at $Proxy4.addErrors(Unknown Source)
	at
us.ok.state.occa.casemgmt.keel.model.updates.PromptCaseMaster.execute(Pr
omptCaseMaster.java:119)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.avalon.fortress.impl.factory.PassThroughInvocationHandler.inv
oke(PassThroughInvocationHandler.java:68)
	at $Proxy7.execute(Unknown Source)
	at
org.keel.services.model.defaultmodel.DefaultModelRequest.execute(Default
ModelRequest.java:218)
	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.avalon.fortress.impl.factory.PassThroughInvocationHandler.inv
oke(PassThroughInvocationHandler.java:68)
	at $Proxy1.execute(Unknown Source)
	at org.keel.models.util.Sequence.runModel(Sequence.java:395)
	at org.keel.models.util.Sequence.runSequence(Sequence.java:274)
	at org.keel.models.util.Sequence.execute(Sequence.java:140)
	at sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.avalon.fortress.impl.factory.PassThroughInvocationHandler.inv
oke(PassThroughInvocationHandler.java:68)
	at $Proxy2.execute(Unknown Source)
	at
org.keel.services.model.defaultmodel.DefaultModelRequest.execute(Default
ModelRequest.java:218)
	at sun.reflect.GeneratedMethodAccessor91.invoke(Unknown Source)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at
org.apache.avalon.fortress.impl.factory.PassThroughInvocationHandler.inv
oke(PassThroughInvocationHandler.java:68)
	at $Proxy1.execute(Unknown Source)
	at
org.keel.servers.direct.KeelDirectServer.execute(KeelDirectServer.java:2
30)
	at
org.keel.servers.direct.KeelDirectServer$MultiThreadedProcessor.run(Keel
DirectServer.java:271)


Jan 7, 2008 12:17:47 PM org.keel.clients.DefaultClientConnector logInfo
Jan 7, 2008 12:17:47 PM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.
Jan 7, 2008 12:17:48 PM org.keel.util.i18n.DynamicMessageSupport
getMessages
WARNING: [DynamicMessageSupport] Model name with prefixe 'oscn', and a
bundle was found under that key.


This last line above goes on throughout the 01-08-2008 log as well.

Any ideas that might help would be greatly appreciated.

Steve Ingraham
Director of Information Systems
Oklahoma Court of Criminal Appeals
mailto:singraham@okcca.net
405 522-5343 


> -----Original Message-----
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Sent: Wednesday, January 09, 2008 1:28 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> 
> > -----Original Message-----
> > From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com]
> > Sent: Wednesday, January 09, 2008 12:59 PM
> > To: Tomcat Users List
> > Subject: RE: problem with data input
> > 
> > 
> > > From: Steve Ingraham [mailto:singraham@okcca.net]
> > > Subject: problem with data input
> > > 
> > > running in Apache Tomcat 5.1.5.15.
> > 
> > No such level; what are you really running?  Also, what OS
> > and what JVM?
> > 
> > > However, if I try to alter that data from the web application 
> > > nothing happens.
> > 
> > Are the requests even making it to the database server?
> > 
> 
> I have some logs from Monday and Tuesday that may be helpful 
> but I am not sure how to get them on here for review.  When I 
> originally sent my request to the forum I attached them to my 
> email but that email never showed up on the forum.  So I am 
> assuming that email was blocked.  If these logs would be 
> useful for someone to review please let me know how I can 
> send them so you could look at them.
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
> 

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> -----Original Message-----
> From: Caldarale, Charles R [mailto:Chuck.Caldarale@unisys.com] 
> Sent: Wednesday, January 09, 2008 12:59 PM
> To: Tomcat Users List
> Subject: RE: problem with data input
> 
> 
> > From: Steve Ingraham [mailto:singraham@okcca.net]
> > Subject: problem with data input
> > 
> > running in Apache Tomcat 5.1.5.15.
> 
> No such level; what are you really running?  Also, what OS 
> and what JVM?
> 
> > However, if I try to alter that data from the web
> > application nothing happens.
> 
> Are the requests even making it to the database server?
> 

I have some logs from Monday and Tuesday that may be helpful but I am
not sure how to get them on here for review.  When I originally sent my
request to the forum I attached them to my email but that email never
showed up on the forum.  So I am assuming that email was blocked.  If
these logs would be useful for someone to review please let me know how
I can send them so you could look at them.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by Steve Ingraham <si...@okcca.net>.
> > 
> > running in Apache Tomcat 5.1.5.15.
> 
> No such level; what are you really running?  Also, what OS 
> and what JVM?
> 

I am not sure then what version of Tomcat.  How can I find this
information?

When I startup the service I get this return:
[root@dellapp01 bin]# sh startup.sh
Using CATALINA_BASE:   /home/movedfromusr/apache-tomcat-5.5.15
Using CATALINA_HOME:   /home/movedfromusr/apache-tomcat-5.5.15
Using CATALINA_TMPDIR: /home/movedfromusr/apache-tomcat-5.5.15/temp
Using JRE_HOME:       /usr/java/jdk1.5.0_04

OS is RedHat AS 3

What is JVM?  Like I said, I am not too knowledgeable about these things
so forgive my ignorance.


> > However, if I try to alter that data from the web
> > application nothing happens.
> 
> Are the requests even making it to the database server?
> 

How can I check to see if they are making it to the database server?
All of our users are still inputting data into the database using the
web application so I think that other information being entered is
making it to the database server.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: problem with data input

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Steve Ingraham [mailto:singraham@okcca.net] 
> Subject: problem with data input
> 
> running in Apache Tomcat 5.1.5.15.

No such level; what are you really running?  Also, what OS and what JVM?

> However, if I try to alter that data from the web
> application nothing happens.

Are the requests even making it to the database server?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org