Auf Thema antworten

Hat leider keine Besserung ergeben. Hatte ich auch vorher schonmal versucht, diesmal nur mit der Änderung, dass ich die derbyclient.jar nochmal in die Tomcat-lib eingefügt habe zusätzlich.

[CODE]

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

0    INFO  [main]            com.cron.InitializeServlet     - ### Servlet Initialized successfully

0 [main] INFO com.cron.InitializeServlet  - ### Servlet Initialized successfully

1    INFO  [main]            com.cron.InitializeServlet     - ### Initializing Scheduler

1 [main] INFO com.cron.InitializeServlet  - ### Initializing Scheduler

169  INFO  [main] org.quartz.core.SchedulerSignalerImpl     - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

169 [main] INFO org.quartz.core.SchedulerSignalerImpl  - Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl

169  INFO  [main]       org.quartz.core.QuartzScheduler     - Quartz Scheduler v.1.8.5 created.

169 [main] INFO org.quartz.core.QuartzScheduler  - Quartz Scheduler v.1.8.5 created.

172  INFO  [main] org.quartz.impl.jdbcjobstore.JobStoreTX     - Using thread monitor-based data access locking (synchronization).

172 [main] INFO org.quartz.impl.jdbcjobstore.JobStoreTX  - Using thread monitor-based data access locking (synchronization).

175  DEBUG [main] org.quartz.impl.jdbcjobstore.SimpleSemaphore     - Lock 'TRIGGER_ACCESS' is desired by: main

175 [main] DEBUG org.quartz.impl.jdbcjobstore.SimpleSemaphore  - Lock 'TRIGGER_ACCESS' is desired by: main

175  DEBUG [main] org.quartz.impl.jdbcjobstore.SimpleSemaphore     - Lock 'TRIGGER_ACCESS' is being obtained: main

175 [main] DEBUG org.quartz.impl.jdbcjobstore.SimpleSemaphore  - Lock 'TRIGGER_ACCESS' is being obtained: main

175  DEBUG [main] org.quartz.impl.jdbcjobstore.SimpleSemaphore     - Lock 'TRIGGER_ACCESS' given to: main

175 [main] DEBUG org.quartz.impl.jdbcjobstore.SimpleSemaphore  - Lock 'TRIGGER_ACCESS' given to: main

1306 INFO  [main]       org.quartz.core.QuartzScheduler     - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 shutting down.

1306 [main] INFO org.quartz.core.QuartzScheduler  - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 shutting down.

1307 INFO  [main]       org.quartz.core.QuartzScheduler     - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 paused.

1307 [main] INFO org.quartz.core.QuartzScheduler  - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 paused.

1307 INFO  [main]       org.quartz.core.QuartzScheduler     - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 shutdown complete.

1307 [main] INFO org.quartz.core.QuartzScheduler  - Scheduler MonitoringScheduler_$_JavaKaffee-PC1310645568894 shutdown complete.

org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'myDS': org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.) [See nested exception: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.)]]

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:612)

    at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:56)

    at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1274)

    at org.quartz.impl.StdSchedulerFactory.getScheduler(StdSchedulerFactory.java:1465)

    at com.cron.AlarmSchedule.<init>(AlarmSchedule.java:17)

    at com.cron.InitializeServlet.init(InitializeServlet.java:27)

    at javax.servlet.GenericServlet.init(GenericServlet.java:212)

    at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)

    at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)

    at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)

    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

    at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)

    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)

    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)

    at org.apache.catalina.core.StandardService.start(StandardService.java:525)

    at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)

    at org.apache.catalina.startup.Catalina.start(Catalina.java:595)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Caused by: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'myDS': org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.) [See nested exception: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.)]

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:695)

    at org.quartz.impl.jdbcjobstore.JobStoreTX.getNonManagedTXConnection(JobStoreTX.java:69)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3765)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3730)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.cleanVolatileTriggerAndJobs(JobStoreSupport.java:752)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:610)

    ... 23 more

Caused by: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.)

    at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)

    at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)

    at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)

    at org.quartz.utils.PoolingConnectionProvider.getConnection(PoolingConnectionProvider.java:194)

    at org.quartz.utils.DBConnectionManager.getConnection(DBConnectionManager.java:109)

    at org.quartz.impl.jdbcjobstore.JobStoreSupport.getConnection(JobStoreSupport.java:692)

    ... 28 more

Caused by: java.sql.SQLNonTransientConnectionException: java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.

    at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)

    at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)

    at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)

    at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)

    at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)

    at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1556)

    at org.apache.commons.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1545)

    ... 33 more

Caused by: org.apache.derby.client.am.DisconnectException: java.net.ConnectException: Fehler beim Herstellen der Verbindung zum Server 127.0.0.1 am Port 1527. Nachricht: Connection refused: connect.

    at org.apache.derby.client.net.NetAgent.<init>(Unknown Source)

    at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source)

    at org.apache.derby.client.am.Connection.<init>(Unknown Source)

    at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)

    at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)

    at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown Source)

    ... 38 more

Caused by: java.net.ConnectException: Connection refused: connect

    at java.net.PlainSocketImpl.socketConnect(Native Method)

    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)

    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)

    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)

    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

    at java.net.Socket.connect(Socket.java:529)

    at java.net.Socket.connect(Socket.java:478)

    at java.net.Socket.<init>(Socket.java:375)

    at java.net.Socket.<init>(Socket.java:189)

    at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:206)

    at org.apache.derby.client.net.OpenSocketAction.run(Unknown Source)

    at java.security.AccessController.doPrivileged(Native Method)

    ... 44 more

1312 INFO  [main]            com.cron.InitializeServlet     - ### Scheduler successfully initialized

1312 [main] INFO com.cron.InitializeServlet  - ### Scheduler successfully initialized

[/CODE]

Also ich habe die DB eigentlich "ordentlich aufgesetzt". Hab mir ein Tool runtergeladen, welches mir das Verzeichnis und die DB in meinem Projektordner erstellt hat, dann das Script aus Quartz durchgezogen für Derby. Die Tabellen sind vorhanden.


Edit: BTW, ich hatte vorher eine HSQLDB, die eigentlich genau dieselben Fehler (oder sehr vergleichbare) geschossen hat. Deswegen bin ich auf Derby umgeschwenkt. Eine davon soll es wohl werden, da man die halt embedded laufen lassen kann und nicht extra ne MySQL DB zur Verfügung stellen muss bzw. man könnte eine nutzen die da ist, allerdings soll diese selbst von der Anwendung überwacht werden und daher wäre das suboptimal.


Edit2: Ich bin übrigens Azubi im (noch) 1. Lehrjahr, bin daher noch nicht ganz soweit (ist meine erste größere Anwendung) und bin z.B. nun das erste mal mit Properties in Berührung gekommen. Mit Datenbanken hatte ich sonst bisher nicht so meine Probleme, eine kleine GUI-Inventarisierung mit MySQL-Anbindung habe ich eigentlich ohne großartige Probleme erstellt. Wenn also noch weitere Angaben benötigt werden sollten, bitte mitteilen :)



Oben