Quote:
Not sure, sometimes it seems to work and sometimes not.
|
Let me describe a sample action by the client using internet banking/metro/swiping/post office/mobile apps/...:
1. login => (Eg: access index.jsp)
2. create a session id at client coockies and always validate the cookie timeout periods.
3. Intermediately assume that client is donating 100.00 INR to prime minister to get a refund for last 10 months using that current session id.
4. Developer of that page invoking a page which is dependent on NRF.jar file which is not set at CLASSPATH environment variable.
Due to this 500 error reported at client side.
5. Developer handled to remove/reset the cookie at client and server side asking the client to re-login again.
I feel that the same condition applicable to your working/non-working exceptions at tomcat.
Hence I have informed to include related CLASSPATH and all tomcat environment variables at start_tomcat.sh (set all, and then call startup.sh if tomcat not at execution mode inside current host including that port number not in use by any other apps)
Following comment not related to this query.
However I am sharing some automated script at localhost whenever I login at 127.0.0.1:
a) Start bash.exe to check battery percentage and if it is greater than 98% open notepad.exe and provide alert to switch off battery
b) start putty.exe at 127.0.0.1 if not opened yet.
c) start firefox.exe if not opened yet.
d) clean /tmp and $TEMP directories and all cookies(I always used to clog after closing firefox manually)
d) exit from this automated script
e) execute above automated script using startup.cpp C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Windows\STARTM~1\Programs\Startup\startup.exe
Hence I have informed perform automated script to invoke startup.sh after setting all requirements for tomcat/any servers.
you can understand => ALL requirements...using lsof /-d /-f /ps/.../sudo required commands using automation at any OS.