I had used Quartz in my Java web-application but when Quartz will execute after its execution, Tomcat is being off. - eclipse

I wrote a code in Quartz that will update database on a daily basis exactly once a day.
I am using Eclipse in my web-application so had started the Tomcat through Eclipse.
But after updating the database from Quartz it is forcing the Tomcat to be terminated in Eclipse. So my application is not working after the Quartz portion is running (due to Tomcat termination). The messages I got in Eclipse 4 Quartz is displayed below:
Job name:Event Update1
Group name:mysql
Trigger name:cronTrigger4Event1
Firing Time:Mon Jan 24 14:30:00 IST 2011
dateFormat.format(calendar.getTime()) : 2011-01-24
Inserting values in Mysql database table!
1 row affected
Jan 24, 2011 2:30:00 PM org.apache.coyote.http11.Http11BaseProtocol pause
INFO: Pausing Coyote HTTP/1.1 on http-8080
[INFO] 24 Jan 2011 14:30:05.506 Thread-34 [org.quartz.core.QuartzScheduler]
Scheduler QuartzScheduler_$_NON_CLUSTERED shutting down.
[INFO] 24 Jan 2011 14:30:05.506 Thread-34 [org.quartz.core.QuartzScheduler]
Scheduler QuartzScheduler_$_NON_CLUSTERED paused.
[INFO] 24 Jan 2011 14:30:05.506 Thread-34 [org.quartz.core.QuartzScheduler]
Scheduler QuartzScheduler_$_NON_CLUSTERED shutdown complete.
Any help is appreciated.

i think your problem in tomcat and eclipse not in quartz itself so you have two solutions
1- get the tomcat out of eclipse and deploy you application manually, don't forget to give you application server more memory.
2- get you schedule jobs out of you application and use the Linux system cron jobs.

Related

Why does list classes in local OrientDB console hang?

I am trying to run list classes from the console:
orientdb {db=mydb}> list classes
CLASSES
But it hangs here indefinitely and then when I interrupt it:
Jul 07, 2020 10:02:27 AM com.orientechnologies.common.log.OLogManager log
WARNING: Received signal: SIGINT
Jul 07, 2020 10:02:27 AM com.orientechnologies.common.log.OLogManager log
INFO: Orient Engine is shutting down...
Jul 07, 2020 10:02:27 AM com.orientechnologies.common.log.OLogManager log
INFO: - shutdown storage: wdb2...
It works fine if I ssh to the server and run the console there but if I run the console locally then it doesn't work.
Selecting the classes from the schema metadata works in both cases:
orientdb {db=mydb}>select expand(classes) from metadata:schema
The only thing that I can think of is perhaps I am missing something on the classpath as I am running the orientdb-tools JAR myself.
Any ideas?

Installing CDT into Eclipse with P2 director gives "The target server failed to respond"

I download the 2020-03 Eclipse Platform Runtime Binary (v4.15 from eclipse-platform-4.15-linux-gtk-x86_64.tar.gz), then invoke the p2 director to install CDT package, but I'm always getting multiple caught exceptions of http://download.eclipse.org not responding (http/https switch doesn't have effect on this).
./eclipse -application org.eclipse.equinox.p2.director -profile SDKProfile -noSplash -roaming -repository http://download.eclipse.org/releases/2020-03,http://download.eclipse.org/releases/2020-03/202003181000/,http://download.eclipse.org/eclipse/updates/4.15/,http://download.eclipse.org/releases/latest,http://download.eclipse.org/tools/cdt/releases/9.11 -installIU org.eclipse.cdt.feature.group/9.11.0.202003091030
I tried it with Oracle JRE 8 and with Oracle JDK 14, I tried it on Debian and RHEL machines, tried different network connection (3 different IPS locations), removed all other plugins I install to nail it down to the CDT plugin. I do not know why or what is causing it, and searching for this problems shows to people that ISP fixed or some similar solution. While mine is consistent for about a year. I always eventually finishes, but it will will print out multiple messages:
Installing org.eclipse.cdt.feature.group 9.11.0.202003091030.
Apr 22, 2020 1:44:29 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://download.eclipse.org:80: The target server failed to respond
Apr 22, 2020 1:44:29 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://download.eclipse.org:80
Apr 22, 2020 1:44:36 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://download.eclipse.org:80: The target server failed to respond
Apr 22, 2020 1:44:36 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {}->http://download.eclipse.org:80
Operation completed in 44091 ms.
Using the HTTPS repositories has similar output:
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://download.eclipse.org:443: The target server failed to respond
Apr 22, 2020 4:02:50 P.M. org.apache.http.impl.execchain.RetryExec execute
INFO: Retrying request to {s}->https://download.eclipse.org:443
Operation completed in 46934 ms.
It's not critical as it eventually completes and the end result works, but I would like to understand it better what is happening, what has effect on this behaviour. When I shrink the list of repositories to these two, it will still install, but the messages will be present:
http://download.eclipse.org/releases/2020-03,http://download.eclipse.org/tools/cdt/releases/9.11
Is there maybe a resource/documentation which probably I missed and is explaining more in the detail what is happening and why?

Azure pipeline Docker `all pipe instances are busy`

When running a build pipeline with maven and docker-maven-plugin sometimes(more than 50% of the time) it throws following error and pipeline fails.
Jun 18, 2019 1:57:12 AM org.apache.http.impl.execchain.RetryExec execute
INFO: I/O exception (java.io.FileNotFoundException) caught when processing request to {}->npipe://127.0.0.1:1: \\.\pipe\docker_engine (All pipe instances are busy)
Jun 18, 2019 1:57:12 AM org.apache.http.impl.execchain.RetryExec execute
I can see in the log that multiple retry attempts, but all fails. Is there any way that I can overcome this?
I just solved this problem:
I added the right version of docker-maven-plugin 1.4.10
dockerfile-maven-plugin

JBoss Fuse Server not starting, giving below error

I am getting below error in Fuse log :
`Sep 14, 2017 5:21:57 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Sep 14, 2017 5:21:58 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Sep 14, 2017 5:21:59 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Sep 14, 2017 5:22:00 AM org.apache.karaf.main.SimpleFileLock lock
INFO: locking
Usually this happens because there is already another Fuse instance running, with the same current directory. If you started Fuse in a way that doesn't create a console, it's not difficult to forget that you did so, and try to start it again. Fuse is designed to work this way -- it's not an error to try to start multiple instances with the same working directory: this is often done for redundancy. But it can be hard to spot if you've done it by accident. Use "jps" or something to see if another JVM is running.
There are other potential causes of this problem that can be explored, but it's worth ruling out the simple explanations first.

Apache tomcat server startup increase over 30000 ms in eclipse Kepler

when i run my JSP page on apache tomcat 7 in my eclipse, server output shows up in 30000ms or more some times it never starts up, at first output got in lessthan 700ms,
Any help or suggession on this problem...
sample output...
NFO: Starting Servlet Engine: Apache Tomcat/7.0.12
Mar 18, 2014 10:42:39 PM org.apache.catalina.util.SessionIdGenerator createSecureRandom
INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [156] milliseconds.
Mar 18, 2014 10:42:58 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Mar 18, 2014 10:42:58 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Mar 18, 2014 10:42:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 30553 ms
Consider the following 2 suggestions:
1)As I commented above check if more then one application is running on the same server.This could be the primary reason.May be 3 or 4 applications might be running once you start your tomcat service.
2)May be some library that you are using for your application is creating some problem,for example the library might be initializing some file storage or may be something else.For this you will have to debug and check your stacktraces.