Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Dwarka Damodaran

Greenhorn
+ Follow
since Nov 10, 2011
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Dwarka Damodaran

Hay Patrick,

your code for resultId does not seem to be doing a .next() and that might also be a problem.

Regards,
Dwarka
8 years ago
Hello Peter,

Ya as you said i had not deployed anything onto the tomcat and it was a fresh install. So i created a simple dynamic web project with an index.html and tried accessing it but it still failed with a HTTP Status 404 error. As you had mentioned about the tomcat deploy directory i did check the Server Overview page and found that under Server Locations composite "Use Workspace metadata" was checked. I changed it to "Use Tomcat Installation" and everything worked fine. But why was it not working when "Use Workspace metadata" was checked (Atleast the project that i deployed should have been accessible).

I will anyways try to find out why this happened and keep this post updated.

Thank you very much for your help !!!

Thanks and Regards,
Dwarka
If you are using one of the matured Databases, then you should have the option of database triggers. You can configure a trigger for the expected table and let the trigger communicate the change to your java program. In this way you are using the inherent feature supported by the database (Which is obviously performance effective) and also reducing the load on the application or the web server.

For how to use java in Oracle triggers see the following link

http://www.cs.umbc.edu/portal/help/oracle8/java.815/a64686/04_call2.htm

Hope this helps.

Thanks and Regards,
Dwarka

I ran delete from table



When talking about ID's getting automatically generated for a table, it has nothing to do with the delete command. It just keeps incrementing from the previous inserted value. The requirement that you are expecting can be easily be achieved either by using a database sequence or by writing your own sequence generator (This is pointless unless you hava a very unique requirement in ID generation). When using Database sequence, you wll have to just reset the sequence to the required value every time you encounter a delete operation.

Hope this helps.

Thanks and Regards,
Dwarka
Hay Himanshu,

I am using apache-tomcat server and I have already set classpath and Jdk path by environment variable



If you have already set the classpath then why are you still refering it during compilation. Its better to remove it from environment variable or to remove it from your compilation command. (Here i am talking about the servlet-api.jar)

In general during these situations the best way to setup an environment is to use a .bat, .cmd or a .sh file and set everything in that rather than messing up with the environment variable. In that way you have better control over the current command prompt.

Hope this helps you.

Thanks and Regards,
Dwarka
8 years ago
Hello All,

I ran into an issue as the subject says with apache-tomcat-6.0.33 zip archive installation.

When i run the tomcat server from command prompt it starts up perfectly correct i.e. i am able to access the admin console shipped with tomcat @ http://localhost:8080/. On the other hand i configured the same installation of tomcat with Eclipse Helios Service Release 1 and started the server and was able to see following log

Nov 10, 2011 2:28:04 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre7\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:/Program Files/Java/jre7/bin/client;C:/Program Files/Java/jre7/bin;C:/Program Files/Java/jre7/lib/i386;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\DISKEE~1\DISKEE~1\;C:\WINDOWS\Support\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files\QuickTime\QTSystem\;C:\develop\environment;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\DISKEE~1\DISKEE~1\;C:\WINDOWS\Support\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Autodesk Shared\;C:\Program Files\QuickTime\QTSystem\;.
Nov 10, 2011 2:28:04 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 10, 2011 2:28:04 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 323 ms
Nov 10, 2011 2:28:04 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Nov 10, 2011 2:28:04 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.33
Nov 10, 2011 2:28:04 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Nov 10, 2011 2:28:04 PM org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
Nov 10, 2011 2:28:04 PM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/16 config=null
Nov 10, 2011 2:28:04 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 176 ms

meaning the server started @localhost:8080, but i was not able to access the admin console as before with the command line. There were no error in the trace or any abnormal activity on the log. i looked into the TCPView and the port 8080 had the established status. The following are my environment details,

OS - Windows XP Professional (Service pack 3)
Eclipse: Helios Service Release 1 (Build 20100917-0705)
Tomcat: 6.0.33
Java: jdk1.6.0_14

Thanks and Regards,
Dwarka