Database problem when upgrading to 6.0.4

Questions and Answers on installation, deployment, management, locking, tranasactions of Servoy Application Server

Database problem when upgrading to 6.0.4

Postby msedita » Fri Jan 20, 2012 6:36 am

I'm having a problem upgrading from 6.0.1 to 6.0.4 at multiple locations. When the server starts up, it throws this error for every active database server:

Code: Select all
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
       at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
       at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
       at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
       at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)


followed by something like this:

Code: Select all
com.servoy.j2db.persistence.RepositoryException: Server repository_server not found
       at com.servoy.j2db.dataprocessing.Zu.Za(Zu.java:820)
       at com.servoy.j2db.dataprocessing.Zu.performQuery(Zu.java:1317)
       at com.servoy.j2db.server.dataprocessing.Zc.checkIfAdministratorsAreAvailable(Zc.java:175)
       at com.servoy.j2db.server.main.ApplicationServer.hasAdministatorAccess(ApplicationServer.java:631)
       at com.servoy.j2db.server.servlets.ConfigServlet.service(ConfigServlet.java:1067)
       at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
       at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
       at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
       at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
       at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
       at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
       at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
       at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)
       at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
       at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
       at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
       at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
       at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
       at java.lang.Thread.run(Unknown Source)


If I access the admin database server page, I see "Error not on-line see log for details" each server. If I click on the server and save save settings, it comes on-line. However, if I stop and restart the Servoy application server, it once again doesn't connect to the database servers, until I manually click save settings for each one. I'm using Sybase 11. This happens under Windows Server 2008 and Windows 7. Java 1.6.0_23 and 1.6.0_29.
Can somebody point me in the right direction? I need to update to be able to use the pdf_output plugin that broke in 6.0.1.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby msedita » Mon Jan 23, 2012 5:28 pm

Anybody? I have users with pitchforks and torches outside my office demanding that I make the pdf output plugin work with Servoy 6.
.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby lvostinar » Mon Jan 23, 2012 5:52 pm

Server repository_server not found


Do you have a running repository server? (with repository tables created)
Laurian Vostinar
Servoy
lvostinar
 
Posts: 1064
Joined: Tue Feb 19, 2008 10:53 am

Re: Database problem when upgrading to 6.0.4

Postby msedita » Mon Jan 23, 2012 6:23 pm

Yes, the database server starts all the databases, including servoy_repository.db, without showing errors in the sybase log.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby lvostinar » Mon Jan 23, 2012 6:28 pm

msedita wrote:Yes, the database server starts all the databases, including servoy_repository.db, without showing errors in the sybase log.


And servoy.properties file correctly points to servoy_repository.db ? (name,url,password are correct)
Laurian Vostinar
Servoy
lvostinar
 
Posts: 1064
Joined: Tue Feb 19, 2008 10:53 am

Re: Database problem when upgrading to 6.0.4

Postby msedita » Mon Jan 23, 2012 7:44 pm

It is the same servoy.properties file and drivers that work fine with 6.0.1. Same everything, in fact, except whatever files were changed by 6.0.4 update. What has changed between 6.0.1 and 6.0.4 that might cause this problem?
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby rgansevles » Mon Jan 23, 2012 10:46 pm

Michael,

Just before this stack trace:

msedita wrote:I'm having a problem upgrading from 6.0.1 to 6.0.4 at multiple locations. When the server starts up, it throws this error for every active database server:

Code: Select all
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
       at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
       at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
       at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
       at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)


There should be another stack trace in the log file which will give a better clue to see what is going on.



Rob
Rob Gansevles
Servoy
User avatar
rgansevles
 
Posts: 1927
Joined: Wed Nov 15, 2006 6:17 pm
Location: Amersfoort, NL

Re: Database problem when upgrading to 6.0.4

Postby msedita » Tue Jan 24, 2012 12:23 am

Thanks. This is the entire servoy_log.txt:
Code: Select all
2012-01-23 17:12:15,361 ERROR [pool-1-thread-1] com.servoy.j2db.server.Za.Zo - java.sql.SQLException: Accessing a closed ResultSet object
2012-01-23 17:12:15,364 ERROR [pool-1-thread-1] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
   at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
   at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
   at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
   at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2012-01-23 17:12:15,398 ERROR [pool-1-thread-1] com.servoy.j2db.server.Za.Zo - java.sql.SQLException: Accessing a closed ResultSet object
2012-01-23 17:12:15,399 ERROR [pool-1-thread-1] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
   at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
   at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
   at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
   at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2012-01-23 17:12:15,412 ERROR [pool-1-thread-1] com.servoy.j2db.server.Za.Zo - java.sql.SQLException: Accessing a closed ResultSet object
2012-01-23 17:12:15,412 ERROR [pool-1-thread-1] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
   at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
   at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
   at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
   at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2012-01-23 17:12:15,424 ERROR [pool-1-thread-1] com.servoy.j2db.server.Za.Zo - java.sql.SQLException: Accessing a closed ResultSet object
2012-01-23 17:12:15,425 ERROR [pool-1-thread-1] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
   at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
   at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
   at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
   at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)
2012-01-23 17:12:15,445 ERROR [pool-1-thread-1] com.servoy.j2db.server.Za.Zo - java.sql.SQLException: Accessing a closed ResultSet object
2012-01-23 17:12:15,445 ERROR [pool-1-thread-1] com.servoy.j2db.util.Debug - Throwable
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Accessing a closed ResultSet object Accessing a closed ResultSet object
   at com.servoy.j2db.server.Za.Zo.Zd(Zo.java:1108)
   at com.servoy.j2db.server.Za.Zo.Zc(Zo.java:1490)
   at com.servoy.j2db.server.Za.Zo.getTable(Zo.java:1181)
   at com.servoy.j2db.server.main.Zr.run(Zr.java:7)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)


This is what the current stack/systeminfo from the admin page shows (if it's any help):
Code: Select all
Current time: Mon Jan 23 17:17:38 EST 2012

Server Information
Servoy version 6.0.4 -build 1227
Port used by RMI Registry: 1099
Repository version 40

Current time: Mon Jan 23 17:17:38 EST 2012

Uptime:  5 minutes 28 seconds

JDK Information
java.vm.name=Java HotSpot(TM) Client VM
java.version=1.6.0_29
java.vm.info=mixed mode
java.vm.vendor=Sun Microsystems Inc.

Operating System Information
os.name=Windows 7
os.version=6.1
os.arch=x86

System Information
Heap Space Memory: allocated=94004K, used=44415K, max=1267072K
Non-Heap Space Memory: allocated=48704K, used=48424K, max=163840K

Thread: http-8080-1, state: RUNNABLE, total cpu time: 202.8013ms, total user time: 171.6011ms
  sun.management.ThreadImpl.getThreadInfo1(Native Method)
  sun.management.ThreadImpl.getThreadInfo(Unknown Source)
  sun.management.ThreadImpl.getThreadInfo(Unknown Source)
  com.servoy.j2db.server.servlets.ConfigServlet.Zs(ConfigServlet.java:1436)
  com.servoy.j2db.server.servlets.ConfigServlet.service(ConfigServlet.java:539)
  javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
  org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
  org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
  org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:567)
  org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
  org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:849)
  org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:454)
  java.lang.Thread.run(Unknown Source)

Thread: DestroyJavaVM, state: RUNNABLE, total cpu time: 6489.6416ms, total user time: 5538.0355ms

Thread: http-443-Acceptor-0, state: RUNNABLE, total cpu time: 0.0ms, total user time: 0.0ms
  java.net.PlainSocketImpl.socketAccept(Native Method)
  java.net.PlainSocketImpl.accept(Unknown Source)
  java.net.ServerSocket.implAccept(Unknown Source)
  com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source)
  org.apache.tomcat.util.net.jsse.JSSESocketFactory.acceptSocket(JSSESocketFactory.java:151)
  org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:317)
  java.lang.Thread.run(Unknown Source)

Thread: http-8080-Acceptor-0, state: RUNNABLE, total cpu time: 0.0ms, total user time: 0.0ms
  java.net.PlainSocketImpl.socketAccept(Native Method)
  java.net.PlainSocketImpl.accept(Unknown Source)
  java.net.ServerSocket.implAccept(Unknown Source)
  java.net.ServerSocket.accept(Unknown Source)
  org.apache.tomcat.util.net.DefaultServerSocketFactory.acceptSocket(DefaultServerSocketFactory.java:61)
  org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:317)
  java.lang.Thread.run(Unknown Source)

Thread: ContainerBackgroundProcessor[StandardEngine[Catalina]], state: TIMED_WAITING, total cpu time: 78.0005ms, total user time: 15.6001ms
  java.lang.Thread.sleep(Native Method)
  org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1579)
  java.lang.Thread.run(Unknown Source)

Thread: ModificationWatcher Task, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Thread.sleep(Native Method)
  org.apache.wicket.util.time.Duration.sleep(Duration.java:445)
  org.apache.wicket.util.thread.Task$1.run(Task.java:130)
  java.lang.Thread.run(Unknown Source)

Thread: pool-1-thread-2, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  sun.misc.Unsafe.park(Native Method)
  java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
  java.util.concurrent.DelayQueue.take(Unknown Source)
  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  java.lang.Thread.run(Unknown Source)

Thread: GC Daemon, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  sun.misc.GC$Daemon.run(Unknown Source)

Thread: RMI Reaper, state: WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  java.lang.ref.ReferenceQueue.remove(Unknown Source)
  java.lang.ref.ReferenceQueue.remove(Unknown Source)
  sun.rmi.transport.ObjectTable$Reaper.run(Unknown Source)
  java.lang.Thread.run(Unknown Source)

Thread: pool-1-thread-1, state: WAITING, total cpu time: 421.2027ms, total user time: 280.8018ms
  sun.misc.Unsafe.park(Native Method)
  java.util.concurrent.locks.LockSupport.park(Unknown Source)
  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
  java.util.concurrent.LinkedBlockingQueue.take(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  java.lang.Thread.run(Unknown Source)

Thread: RMI TCP Accept-1099, state: WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  sun.misc.Unsafe.park(Native Method)
  java.util.concurrent.locks.LockSupport.park(Unknown Source)
  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
  java.util.concurrent.ArrayBlockingQueue.take(Unknown Source)
  com.servoy.j2db.rmi.ServerTwoWaySocketFactory$TwoWayServerSocket.accept(ServerTwoWaySocketFactory.java:579)
  sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(Unknown Source)
  sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(Unknown Source)
  java.lang.Thread.run(Unknown Source)

Thread: 2 way Server Acceptor, state: RUNNABLE, total cpu time: 0.0ms, total user time: 0.0ms
  java.net.PlainSocketImpl.socketAccept(Native Method)
  java.net.PlainSocketImpl.accept(Unknown Source)
  java.net.ServerSocket.implAccept(Unknown Source)
  com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(Unknown Source)
  com.servoy.j2db.rmi.ServerTwoWaySocketFactory$TwoWayServerSocket.run(ServerTwoWaySocketFactory.java:597)
  java.lang.Thread.run(Unknown Source)

Thread: pool-2-thread-1, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  sun.misc.Unsafe.park(Native Method)
  java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
  java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
  java.util.concurrent.DelayQueue.take(Unknown Source)
  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
  java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
  java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
  java.lang.Thread.run(Unknown Source)

Thread: PingScanner, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  com.servoy.j2db.dataprocessing.Zn.run(Zn.java:21)
  java.lang.Thread.run(Unknown Source)

Thread: MessageScheduler, state: TIMED_WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  com.servoy.j2db.dataprocessing.Zp.run(Zp.java:46)
  java.lang.Thread.run(Unknown Source)

Thread: MessagePreHandler, state: WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  java.lang.Object.wait(Object.java:485)
  com.servoy.j2db.dataprocessing.ClientMessagePreQueueHandler.run(ClientMessagePreQueueHandler.java:7)
  java.lang.Thread.run(Unknown Source)

Thread: Attach Listener, state: RUNNABLE, total cpu time: 0.0ms, total user time: 0.0ms

Thread: Signal Dispatcher, state: RUNNABLE, total cpu time: 0.0ms, total user time: 0.0ms

Thread: Finalizer, state: WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  java.lang.ref.ReferenceQueue.remove(Unknown Source)
  java.lang.ref.ReferenceQueue.remove(Unknown Source)
  java.lang.ref.Finalizer$FinalizerThread.run(Unknown Source)

Thread: Reference Handler, state: WAITING, total cpu time: 0.0ms, total user time: 0.0ms
  java.lang.Object.wait(Native Method)
  java.lang.Object.wait(Object.java:485)
  java.lang.ref.Reference$ReferenceHandler.run(Unknown Source)


And this is the sybase log:
Code: Select all
I. 01/23 17:11:41. 1: -ec
I. 01/23 17:11:41. 2: tls(tls_type=rsa;identity=sybase_db/sybase.cmhcihost.id;identity_password=newman1234)
I. 01/23 17:11:41. 3: -es
I. 01/23 17:11:41. 4: -ti
I. 01/23 17:11:41. 5: 0
I. 01/23 17:11:41. 6: -x
I. 01/23 17:11:41. 7: tcpip{dobroad=no;port=2638;tds=no}
I. 01/23 17:11:41. 8: -z
I. 01/23 17:11:41. 9: -qs
I. 01/23 17:11:41. 10: -qw
I. 01/23 17:11:41. 11: -o
I. 01/23 17:11:41. 12: sybase_db/sybase_log.txt
I. 01/23 17:11:41. 13: database/servoy_repository.db
I. 01/23 17:11:41. 14: database/user_data.db
I. 01/23 17:11:41. 15: database/example.db
I. 01/23 17:11:41. 16: database/log_data.db
I. 01/23 17:11:41. 17: database/udm.db
I. 01/23 17:11:41. 18: database/pdf_forms.db
I. 01/23 17:11:41. 19: database/bug_db.db
I. 01/23 17:11:41. 20: database/cmhci.db
I. 01/23 17:11:41. 21: -ek ****
I. 01/23 17:11:41.

I. 01/23 17:11:41. SQL Anywhere Network Server Version 11.0.1.2044

I. 01/23 17:11:41. Workgroup edition
I. 01/23 17:11:41.

I. 01/23 17:11:41. Copyright © 2001-2009, iAnywhere Solutions, Inc.
I. 01/23 17:11:41. Portions copyright © 1988-2009, Sybase, Inc. All rights reserved.
I. 01/23 17:11:41. Use of this software is governed by the Sybase License Agreement. Refer to http://www.sybase.com/softwarelicenses
I. 01/23 17:11:41.

I. 01/23 17:11:41. 2 logical processor(s) on 1 physical processor(s) detected.
I. 01/23 17:11:41. This edition is restricted to use a maximum of 2 physical processors (0 = unlimited).
I. 01/23 17:11:41. Per-processor licensing model. The server is licensed to use 1 physical processor(s).
I. 01/23 17:11:41. This server is licensed to:
I. 01/23 17:11:41.     servoy
I. 01/23 17:11:41.     servoy
I. 01/23 17:11:41. Running Windows 7 Build 7601 Service Pack 1 on X86_64
I. 01/23 17:11:41. Server built for X86 processor architecture
I. 01/23 17:11:42. 1048576K of memory used for caching
I. 01/23 17:11:42. Minimum cache size: 2048K, maximum cache size: 3569160K
I. 01/23 17:11:42. Using a maximum page size of 8192 bytes
I. 01/23 17:11:42. TCP using Winsock version 2.2
I. 01/23 17:11:42. IPv6 support enabled
I. 01/23 17:11:42. Starting database "log_data" (C:\Servoy6\application_server\database\log_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "example" (C:\Servoy6\application_server\database\example.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "user_data" (C:\Servoy6\application_server\database\user_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "servoy_repository" (C:\Servoy6\application_server\database\servoy_repository.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "cmhci" (C:\Servoy6\application_server\database\cmhci.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "pdf_forms" (C:\Servoy6\application_server\database\pdf_forms.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "udm" (C:\Servoy6\application_server\database\udm.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Starting database "bug_db" (C:\Servoy6\application_server\database\bug_db.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Transaction log: pdf_forms.log
I. 01/23 17:11:42. Starting checkpoint of "pdf_forms" (pdf_forms.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Finished checkpoint of "pdf_forms" (pdf_forms.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:42. Database "pdf_forms" (pdf_forms.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Transaction log: example.log
I. 01/23 17:11:43. Transaction log: bug_db.log
I. 01/23 17:11:43. Transaction log: log_data.log
I. 01/23 17:11:43. Transaction log: servoy_repository.log
I. 01/23 17:11:43. Starting checkpoint of "bug_db" (bug_db.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Starting checkpoint of "example" (example.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Finished checkpoint of "bug_db" (bug_db.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Finished checkpoint of "example" (example.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Database "bug_db" (bug_db.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Performance warning: Database "bug_db" has a page size of 4096 that does not match maximum of 8192 set for server, causing inefficient use of cache
I. 01/23 17:11:43. Database "example" (example.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Performance warning: Database "example" has a page size of 4096 that does not match maximum of 8192 set for server, causing inefficient use of cache
I. 01/23 17:11:43. Starting checkpoint of "log_data" (log_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Finished checkpoint of "log_data" (log_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Starting checkpoint of "servoy_repository" (servoy_repository.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Finished checkpoint of "servoy_repository" (servoy_repository.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:43. Database "servoy_repository" (servoy_repository.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Transaction log: user_data.log
I. 01/23 17:11:44. Transaction log: udm.log
I. 01/23 17:11:44. Transaction log: cmhci.log
I. 01/23 17:11:44. Database "log_data" (log_data.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Starting checkpoint of "udm" (udm.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Starting checkpoint of "cmhci" (cmhci.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Finished checkpoint of "udm" (udm.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Finished checkpoint of "cmhci" (cmhci.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Database "udm" (udm.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Database "cmhci" (cmhci.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:44. Starting checkpoint of "user_data" (user_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:45. Finished checkpoint of "user_data" (user_data.db) at Mon Jan 23 2012 17:11
I. 01/23 17:11:45. Database "user_data" (user_data.db) started at Mon Jan 23 2012 17:11
I. 01/23 17:11:45. Database server started at Mon Jan 23 2012 17:11
I. 01/23 17:11:45. Trying to start SharedMemory link ...
I. 01/23 17:11:45.     SharedMemory link started successfully
I. 01/23 17:11:45. Trying to start TCPIP link ...
I. 01/23 17:11:45. TDS connections disabled
I. 01/23 17:11:46. Starting TCP listener on IP address (::1):2638
I. 01/23 17:11:47. Starting TCP listener on IP address 127.0.0.1:2638
I. 01/23 17:11:48. Starting TCP listener on IP address (::):2638
I. 01/23 17:11:49. Starting TCP listener on IP address 0.0.0.0:2638
I. 01/23 17:11:49. Starting UDP listener on IP address 127.0.0.1:2638
I. 01/23 17:11:49. This is a class A network address
I. 01/23 17:11:49. Starting UDP listener on IP address 192.168.0.15:2638
I. 01/23 17:11:49. This is a class C network address
I. 01/23 17:11:49. Not performing a broadcast
I. 01/23 17:11:49. Starting UDP listener on IP address 192.168.0.15:2638
I. 01/23 17:11:49. This is a class C network address
I. 01/23 17:11:49. Starting UDP listener on IP address 127.0.0.1:2638
I. 01/23 17:11:49. This is a class A network address
I. 01/23 17:11:49.     TCPIP link started successfully
I. 01/23 17:11:49. Now accepting requests
I. 01/23 17:12:11. TCP/IP: Received connection request from 127.0.0.1:53674.
I. 01/23 17:12:11. Connection from 127.0.0.1:53674 assigned connection ID 1
I. 01/23 17:12:11. Connection ID 1: "DBA" connected to database "servoy_repository" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:11. Connection ID 1: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x3094;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:11. Connection ID 1: Server character set conversion is enabled, but not required
    using character set "windows-1252"
I. 01/23 17:12:11. Connection ID 1: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53677.
I. 01/23 17:12:14. Connection from 127.0.0.1:53677 assigned connection ID 2
I. 01/23 17:12:14. Connection ID 2: "DBA" connected to database "pdf_forms" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 2: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 2: Server character set conversion will occur
    database character set is "UTF-8"
    using client character set "windows-1252"
I. 01/23 17:12:14. Connection ID 2: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. Connection ID 2: Character set changed to "none"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53678.
I. 01/23 17:12:14. Connection from 127.0.0.1:53678 assigned connection ID 3
I. 01/23 17:12:14. Connection ID 3: "dba" connected to database "cmhci" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 3: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 3: Server character set conversion is enabled, but not required
    using character set "windows-1252"
I. 01/23 17:12:14. Connection ID 3: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53679.
I. 01/23 17:12:14. Connection from 127.0.0.1:53679 assigned connection ID 4
I. 01/23 17:12:14. Connection ID 4: "DBA" connected to database "example" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 4: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 4: Server character set conversion will occur
    database character set is "UTF-8"
    using client character set "windows-1252"
I. 01/23 17:12:14. Connection ID 4: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. Connection ID 4: Character set changed to "none"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53680.
I. 01/23 17:12:14. Connection from 127.0.0.1:53680 assigned connection ID 5
I. 01/23 17:12:14. Connection ID 5: "DBA" connected to database "log_data" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 5: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 5: Server character set conversion will occur
    database character set is "UTF-8"
    using client character set "windows-1252"
I. 01/23 17:12:14. Connection ID 5: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. Connection ID 5: Character set changed to "none"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53681.
I. 01/23 17:12:14. Connection from 127.0.0.1:53681 assigned connection ID 6
I. 01/23 17:12:14. Connection ID 6: "dba" connected to database "servoy_repository" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 6: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 6: Server character set conversion is enabled, but not required
    using character set "windows-1252"
I. 01/23 17:12:14. Connection ID 6: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. TCP/IP: Received connection request from 127.0.0.1:53682.
I. 01/23 17:12:14. Connection from 127.0.0.1:53682 assigned connection ID 7
I. 01/23 17:12:14. Connection ID 7: "DBA" connected to database "udm" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:14. Connection ID 7: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x6ac;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:14. Connection ID 7: Server character set conversion will occur
    database character set is "UTF-8"
    using client character set "windows-1252"
I. 01/23 17:12:14. Connection ID 7: NCHAR character set changed to "UTF-8"
I. 01/23 17:12:14. Connection ID 7: Character set changed to "none"
I. 01/23 17:12:16. TCP/IP: Received connection request from 127.0.0.1:53683.
I. 01/23 17:12:16. Connection from 127.0.0.1:53683 assigned connection ID 8
I. 01/23 17:12:16. Connection ID 8: "DBA" connected to database "servoy_repository" from SQL Anywhere 11.0.1 (2331) client over TCPIP
I. 01/23 17:12:16. Connection ID 8: AppInfo is IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x260c;THREAD=0x3094;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
I. 01/23 17:12:16. Connection ID 8: Server character set conversion is enabled, but not required
    using character set "windows-1252"
I. 01/23 17:12:16. Connection ID 8: NCHAR character set changed to "UTF-8"


So sybase thinks it's connected to servoy. I can't tell anything beyond that. And again, if I click save in the admin-database page, it connects, until servoy is restarted.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby rgansevles » Tue Jan 24, 2012 1:10 am

That is very strange.

The code catches an exception, logs it and throws the exception you are showing.
The first exception is the one that we need.
Also nothing showing on the log section of the admin page?

Rob
Rob Gansevles
Servoy
User avatar
rgansevles
 
Posts: 1927
Joined: Wed Nov 15, 2006 6:17 pm
Location: Amersfoort, NL

Re: Database problem when upgrading to 6.0.4

Postby msedita » Tue Jan 24, 2012 1:26 am

The log section of the admin page show the same thing as the text log. FYI - I'm using the jodbc driver for Sybase, not the jconn or jtds. It's the same driver I've been using for years but I'm wondering if anything changed that would cause an incompatibility. I'm assuming that others who use sybase have done this upgrade, so it must be particular to my installations. Maybe no one else is using that driver. That's about all I got.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby Robert Huber » Tue Jan 24, 2012 4:48 pm

Hi Michael

We use SQL Anywhere 12 and the entry in the Driver field is: com.sybase.jdbc3.jdbc.SybDriver. The file is called jconn3.jar and is in the SQLA installed database folder, something like /Library/SQLAnywhere12/System/java/jconn3.jar if it is installed in /Library/SQLAnywhere12 like we have done.
Hope that helps.

msedita wrote:The log section of the admin page show the same thing as the text log. FYI - I'm using the jodbc driver for Sybase, not the jconn or jtds. It's the same driver I've been using for years but I'm wondering if anything changed that would cause an incompatibility. I'm assuming that others who use sybase have done this upgrade, so it must be particular to my installations. Maybe no one else is using that driver. That's about all I got.


Regards, Robert
Robert Huber
7r gmbh, Switzerland
SAN Developer
www.seven-r.ch
User avatar
Robert Huber
 
Posts: 1239
Joined: Tue Aug 23, 2005 6:52 pm
Location: Schaffhausen, Switzerland

Re: Database problem when upgrading to 6.0.4

Postby msedita » Tue Jan 24, 2012 5:05 pm

Thanks Rob and Robert. The problem is definitely with the driver we are using (ianywhere JDBC driver http://www.sybase.com/detail?id=1037304#1). When I switch back to jconnect, no problems. Unfortunately, we can't use jconnect in a production environment because it doesn't support encrypted-only connections. So this seems like something changed in 6.0.4, some different way of communicating with the db server, that doesn't seem to work with jdbc driver.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby msedita » Thu Jan 26, 2012 2:45 am

So I still haven't resolved this problem. I enabled a detail log with a switch on the database url, this show it connecting successfully as far as Sybase is converned:

Code: Select all
Tue Jan 24 2012 12:02:58
12:02:58 Attempting to connect using:
UID=dba;PWD=********;DBN=CMHCi;ENG=servoy_repository;CON=SQL_DBC_604b5a00;ENC='tls(tls_type=rsa;trusted_certificates=sybase.cmhcihost.crt)';LOG=cmhci_connect.txt;LINKS='tcpip(host=localhost;port=2638;dobroad=no)';PBUF=2m
12:02:58 Attempting to connect to a running server...
12:02:58 Attempting TCPIP connection (address 127.0.0.1:2638 found in sasrv.ini cache)
12:02:58 Looking for server with name servoy_repository
12:02:58 Trying to find server at address localhost
12:02:58 Found server, verifying server name
12:02:58 Found database server at address 127.0.0.1:2638
12:02:58 Found database server servoy_repository on TCPIP link
12:02:58 Connected using client address 127.0.0.1:56719
12:02:58 Connected to server over TCPIP at address 127.0.0.1:2638
12:02:58 Connected to SQL Anywhere Server version 11.0.1.2044
12:02:58 Application information:
12:02:58 IP=192.168.0.15;HOST=MS-DELLE6500;OSUSER=mike;OS='Windows 7 Build 7601 Service Pack 1';EXE='C:\Program Files (x86)\Java\jre6\bin\java.exe';PID=0x1ad8;THREAD=0x2fa0;VERSION=11.0.1.2331;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300
12:02:58 Connected to the server, attempting to connect to a running database...
12:02:58 [    2] Connected to database successfully
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby msedita » Wed Feb 01, 2012 11:34 pm

OK - I tried to upgrade a fully functional 6.0.1 installation to 6.0.5 and it breaks. I also tried a fresh install of 6.0.5, and just added the sql anywhere driver and server definitions to the properties file. Doesn't work either, same errors. So I'm not sure where to go with this. Changing a bunch of production servers over to postgres isn't practical. I can't use the sql anywhere driver that ships with Servoy because it isn't secure. I can't keep running without the pdf_output plugin that was broke in version 6. I've tried different different versions of the sql drivers, spent hours researching the " Accessing a closed ResultSet object" error and I got nothing. So throw me a bone here Servoy - I need a way out of this problem that didn't occur until I installed a minor update in order to fix a problem cause by a prior update.
Michael Sedita
MS Health Software Corp.
Developers of software solutions for behavioral healthcare and social service providers.
www.mshealth.com
User avatar
msedita
 
Posts: 224
Joined: Thu Dec 13, 2007 8:01 pm

Re: Database problem when upgrading to 6.0.4

Postby ROCLASI » Thu Feb 02, 2012 1:28 am

Hi Michael,

I suggest you file a support case with Servoy.
Robert Ivens
SAN Developer / Servoy Valued Professional / Servoy Certified Developer

ROCLASI Software Solutions / JBS Group, Partner
Mastodon: @roclasi
--
ServoyForge - Building Open Source Software.
PostgreSQL - The world's most advanced open source database.
User avatar
ROCLASI
Servoy Expert
 
Posts: 5438
Joined: Thu Oct 02, 2003 9:49 am
Location: Netherlands/Belgium

Next

Return to Servoy Server

Who is online

Users browsing this forum: No registered users and 7 guests

cron