Using connectbox server running cf2023 for development and also manually running a notification process once each day. After a more or less 48 hour inactivity I returned to the app and it timed out connecting to the local database. The database was still available as I could connect to it using SqlYog. I restarted the server, no help. I restarted my laptop, no help. I ran the administrator and was unable to confirm the connections. I was unable to create a new database connection. I then ran a forget command and confirmed prompts to delete the server. I started a new server, installed all packages, ran the administrator, could not establish connections. Not sure what changed that suddenly has prevented me from connecting to the database after several months of operating with no problem. Does anyone have any suggestions?
I doesnāt sound like the issue is with CommandBox, or even ColdFusion. I would double check if the local server is running on the expected port and if the datasource config is correct. If the server is running inside of Docker, that may be something to review as well.
Hi Brad, Thank you very much for replying. I take your point that it probably isnāt CommandBox or ColdFusion but Iām not sure where to go. I have been very careful to check the information I am entering into the administrator for the data connection and am using my SqlYog tool, which is able to connect to the database as normal, to confirm the setup details. The only thing I canāt see is the password; I changed the password when all else failed, and put the password in my password manager. I then confirmed password correct by having to change it in SqlYog and using the password as in password manager. Then I edited the data connections with the new password but to no avail. Previously I redid the connections using the same info as originally entered - which previously worked -so I donāt think itās a setup entry error. I did a Windows 11 update on 1/11 to 24H2, I wonder if that changed something.
When you try to connect to the DB from ColdFusion, what do you see? An error? Is there a message? A stack trace? Can you take a screen shot? At this point youāve given us basically nothing to go on.
Sorry for delay. When able Iāve been fiddling with the Windows Defender firewall to no avail. I found the Coldfusion logs and am thinking this could be the problem: [ERROR] runwar.context: java.lang.UnsupportedClassVersionError: org/apache/derby/jdbc/ClientDriver has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Running Windows 11 w/ latest updates
I had a notice that a Java upgrade was available so upgraded from version 8.0 (52) to 9.0 (53), rebooted and reran, same error. I checked the java version in the Command Prompt and it said I was running version 8.0.
Not sure how to resolve this issue which I think must be addressed even if it isnāt the source of my data connection problem. Is the Java part of the commandbox package or is it run from my %Java_Home%? I am including the entire log section that was written when I last started the server.
[INFO ] runwar.server: Stopped server
[INFO ] runwar.server: ******************************************************************************
[INFO ] runwar.server: Starting Runwar
[INFO ] runwar.server: - Runwar Version: 5.0.0
[INFO ] runwar.server: - Java Version: 25.441-b07 (Oracle Corporation)
[INFO ] runwar.server: - Java Home: C:\Program Files (x86)\Java\jre1.8.0_441
[INFO ] runwar.server: ******************************************************************************
[INFO ] runwar.server: Listeners:
[INFO ] runwar.server: - Binding HTTP on 127.0.0.1:51096
[INFO ] runwar.server: ******************************************************************************
[INFO ] runwar.server: Configuring Servlet
[INFO ] runwar.server: Found WEB-INF: āC:\Users\ffs53.CommandBox\server\F7B6DEADAC27EBB8F87F3CFDB748320A-FFS_2024_Dev\adobe-2023.0.12.330713\WEB-INFā
[INFO ] runwar.server: ******************************************************************************
[INFO ] runwar.server: Creating deployment [default]
[INFO ] runwar.server: Web Root: C:\Users\ffs53\OneDrive\FFS_2024_Dev
[INFO ] runwar.context: Jan 22, 2025 19:14:29 PM Information [main] - Starting loggingā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:29 PM Information [main] - Starting licenseā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:30 PM Information [main] - Developer Edition enabled
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Starting cryptoā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Installed JSafe JCE provider: Version 6.21 Crypto-J 6.2.1, EMC Corporation. JsafeJCE Security Provider (implements RSA, DSA, ECDSA, Diffie-Hellman, ECDH, AES, DES, Triple DES, DESX, RC2, RC4, RC5, PBE, MD2, MD5, RIPEMD160, SHA1, SHA224, SHA256, SHA384, SHA512, HMAC-MD5, HMAC-RIPEMD160, HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-SHA384, HMAC-SHA512, HMACDRBG, HASHDRBG, CTRDRBG, FIPS186PRNG, SHA1PRNG, MD5PRNG; RFC 3394, RFC 5649 AES Key Wrap; X.509 CertificateFactory; PKCS12, PKCS15 KeyStore; X.509V1, PKIX, PKIX-SuiteB, PKIX-SuiteBTLS CertPathValidators; X.509V1, PKIX, PKIX-SuiteB, PKIX-SuiteBTLS CertPathBuilders; LDAP, Collection CertStores)
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Starting securityā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Starting schedulerā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Starting WatchServiceā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:36 PM Information [main] - Starting runtimeā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:42 PM Information [main] - Starting clientā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:42 PM Information [main] - The metrics service is disabled for the J2EE edition
[INFO ] runwar.context: Jan 22, 2025 19:14:42 PM Information [main] - Starting archiveā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:42 PM Information [main] - Starting CloudConfigā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:42 PM Information [main] - Starting GraphQLConfigā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Starting VendorCredentialā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Starting restā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Starting registryā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package adminapi startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package administrator startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package ccs startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package redissessionstorage startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package debugger startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package zip startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package image startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package caching startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package cfmongodb startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package mail startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:43 PM Information [main] - Package spreadsheet startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package axis startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package chart startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package feed startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package print startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package search startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package document startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package presentation startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package eventgateways startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Event Gateway Disabled.
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package dotnet startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - pmtagent package will not be deployed as it is not installed.
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package htmltopdf startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package awslambda startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:45 PM Information [main] - Package com startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package saml startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package awss3 startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package awss3legacy startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package azureblob startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package pdf startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [main] - Package websocket startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:46 PM Information [Thread-25] - PDFg service manager http://127.0.0.1:8995/PDFgServlet/ registered.
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package orm startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Error [pool-35-thread-1] - Address already in use: bind
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package ormsearch startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package ajax startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package derby startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package oracle startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package mysql startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package db2 startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package sybase startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package postgresql startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package sqlserver startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package odbc startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Starting sqlā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package scheduler startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package ftp startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package awssqs startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package awssns startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package azureservicebus startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package awsdynamodb startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package gcpfirestore startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package gcppubsub startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:47 PM Information [main] - Package gcpstorage startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - Package report startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - Package exchange startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - Package sharepoint startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - Package graphqlclient startedā¦
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - ColdFusion started
[INFO ] runwar.context: Jan 22, 2025 19:14:48 PM Information [main] - ColdFusion: application services are now available
[INFO ] runwar.context: Jan 22, 2025 19:14:49 WARN [main] - Unable to determine dialect of the StAX implementation at jar:file:/C:/Users/ffs53/.CommandBox/server/F7B6DEADAC27EBB8F87F3CFDB748320A-FFS_2024_Dev/adobe-2023.0.12.330713/WEB-INF/cfusion/lib/bundleaxis/wstx-asl-3.2.9.jar!/
[INFO ] runwar.context: Jan 22, 2025 19:14:49 PM Warning [main] - Unable to determine dialect of the StAX implementation at jar:file:/C:/Users/ffs53/.CommandBox/server/F7B6DEADAC27EBB8F87F3CFDB748320A-FFS_2024_Dev/adobe-2023.0.12.330713/WEB-INF/cfusion/lib/bundleaxis/wstx-asl-3.2.9.jar!/
[INFO ] runwar.server: ******************************************************************************
[INFO ] runwar.server: Starting āstopā listener thread - Host: 127.0.0.1 - Socket: 51261
[INFO ] dorkbox.systemTray.SystemTray: Successfully loaded
[WARN ] dorkbox.systemTray.SystemTray: Please disable tooltips, as they are not consistent across all platforms and tray types.
[INFO ] runwar.server: Server is up - stop-port:51261 PID:19448 version 5.0.0
[INFO ] runwar.server: Waiting up to 240 seconds for stop port 127.0.0.1:51261ā¦
[INFO ] runwar.server: Opening browser to url: http://127.0.0.1:51096
[ERROR] runwar.context: Exception in thread āThread-35ā
[ERROR] runwar.context: java.lang.UnsupportedClassVersionError: org/apache/derby/jdbc/ClientDriver has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0
[ERROR] runwar.context: at java.lang.ClassLoader.defineClass1(Native Method)
[ERROR] runwar.context: at java.lang.ClassLoader.defineClass(Unknown Source)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2338)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClassParallel(BundleWiringImpl.java:2156)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2090)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1556)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
[ERROR] runwar.context: at java.lang.ClassLoader.loadClass(Unknown Source)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.getClassByDelegation(BundleWiringImpl.java:1358)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.searchImports(BundleWiringImpl.java:1612)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1528)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
[ERROR] runwar.context: at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1976)
[ERROR] runwar.context: at java.lang.ClassLoader.loadClass(Unknown Source)
[ERROR] runwar.context: at coldfusion.derby.ApacheDerbyServiceimpl.isApacheDerbyDriver(ApacheDerbyServiceimpl.java:10)
[ERROR] runwar.context: at coldfusion.server.j2ee.sql.pool.JDBCPool.createPhysicalConnection(JDBCPool.java:612)
[ERROR] runwar.context: at coldfusion.server.j2ee.sql.pool.ConnectionRunner$RunnableConnection.run(ConnectionRunner.java:67)
[ERROR] runwar.context: at java.lang.Thread.run(Unknown Source)
[ERROR] runwar.context: A non-SQL error occurred while requesting a connection from 1055140_FFS_MSQ_R1.
[ERROR] runwar.context: Timed out trying to establish connection
[INFO ] runwar.context: Jan 22, 2025 19:14:56 PM Error [XNIO-1 task-1] - Error Executing Database Query.Timed out trying to establish connection The specific sequence of files included or processed is: C:\Users\ffs53\OneDrive\FFS_2024_Dev\index.cfm, line: 257
I see in the log information above that the java is running from my c: drive.
It would appear youāre using Java 25
[INFO ] runwar.server: - Java Version: 25.441-b07 (Oracle Corporation)
By default, servers will start on whatever version of Java the CLI is using. (which you can see in the output of the info
command). If youād like to start a server on a different version of Java, then tell CommandBox what youād like it to use.
I tried to download a newer version of Java but the version 1.80 is the version they offer and recommend and I wasnāt able find a version 1.90. I did instruct commandbox to load openjdk9 using the options listed in the help info you sent (thank you). Set server.defaults.jvm.javaVersion = openjdk9. However it responded that openjdk9 didnāt exist. Loading openjdk8 allowed it to load and have the āunable to connect to databaseā error. One think I note is that my java installation is 32-bit but connectbox is installing 64-bit Coldfusion. That seems wrong. I donāt understand why the jdbc driver is compiled by a more advanced version of java than Java will allow me to install. I renamed my Java directory to Javaw and connectbox couldnāt run, saying that it required Java 1.80 to run, so I confirmed it is using the Java installed on my machine to run.
Itās nearly impossible to follow what youāve done, and in what order, lol.
Who is ātheyā. I canāt imagine anyone recommend Java 8 in this day and age. Itās way out of date. The āJRE includedā versions of CommandBox on our Ortus download page bundle Java 11, but Iāve tested it up to Java 21.
Yeah, I wouldnāt use Java 9. Java 11 was the next LTS version. Versions 9 and 10 were sort of āstepping stoneā versions that donāt receive long term support.
To be clear, there are two separate Java processes at play when you start a server.
- The CLI process where you run the
server start
command - THe actual server process for the server that starts
These two processes donāt necessarily use the same version of Java. And configuring each one to use a specific version varies. I sent you instructions on how to run the actual server process (second bullet) on a specific version of Java, but not how to run the CLI itself (first bullet) on a given version of Java.
I would hope youāre not using 32-bit Java. UNless you PC is from 1998 that shouldnāt be necessary and will just cause issues. Please ensure you have a 64-bit version of Java.
There is no āversionā of ColdFusion for 32-bit or 64-bit. Only the JVM cares about that. Compiled bytecode will run on any JVM regardless of the ābitnessā of the CPU architecture.
To be clear, the error you provided above has nothing to do with the CPU architecture, it has to do with the actual version of java. I am a little confused about what actual version of Java you are running the server on. The output from Runwar showed
Java Version: 25.441-b07 (Oracle Corporation)
which doesnāt seem like a full version number. And the error from the JDBC driver was
UnsupportedClassVersionError: org/apache/derby/jdbc/ClientDriver has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0
which indicates you are trying to run a class file compiled for Java 9 on Java 8. So thereās some missing pieces or crossed wires here.
I donāt know what your java directory is or if itās in use by the CLI without more information. CommandBox does not require Java 8 at all unless you have some super old version of CommandBox installed! Please ensure you have CommandBox 6.1.0 installed. If CommandBox is telling you it requires Java 8, then please screenshot what youāre seeing so I can understand.
I donāt really follow this sentence. What is āitā? The CLI? The Server? What Java is on your machine? Is it set in an environment variable? Configured in the registry? In a jre
folder relative to box.exe
? All of things things factor into whether it gest used on Windows.
Iām running CommandBox 6.0.0+00787. I have installed 64-bit Java on my local machine and will now try to upgrade my commandbox. Thank you.
i have upgraded CommandBox to version 6.1.0+00813 and ConnectBox Server loads Java version 25?
C:\Users\ffs53\OneDrive\FFS_2024_Dev>box start cfengine=adobe@2023
ā | Starting Server
| ā | Installing package [java:openjdk8:lockVersion]
| ā | Setting site [FFS_2024_Dev] Profile to [development]
| ā | Loading CFConfig into server
[INFO ] Runwar: ******************************************************************************
[INFO ] Runwar: Starting Runwar
[INFO ] Runwar: - Runwar Version: 5.0.8
[INFO ] Runwar: - Java Version: 25.442-b06 (Temurin)
[INFO ] Runwar: - Java Home: C:\Users\ffs53.CommandBox\serverJREs\openjdk8_jre_x64_windows_hotspot_jdk8u442-b06
Despite this I still receive the jdbc class 53 vs 52 issue and am still unable to connect to database.
[ERROR] runwar.context: java.lang.UnsupportedClassVersionError: org/apache/derby/jdbc/ClientDriver has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0
Iām using the Mysql driver, which previously worked. I tried the Mysql Datadirect driver but no difference. Not sure of next step. I feel Iāve confirmed the setup details by creating new data connection in Sqlyog. I donāt see any errors in CommandBox.log.
Yeah, I donāt actually think thatās Java 25. I have no idea why itās showing up that way, but it clearly appears to be Java 8 from everything else.
Well yes, as previously discussed, that error means you canāt use a jar compiled for java 9+ on Java 8, so Iām not sure why you would still be starting on Java 8 on purpose when weāve determined that isnāt going to work. Again, my suggestion is you use at least Java 11.
Back in business, thank you. I eliminated the failure of the odbc to compile by no longer loading the odbc driver, which I donāt use. I had taken to loading all features when starting up a cf server, but I fell back to loading just those that are required. I did this before all updates were completed to try to move along. The Java on my machine that the CLI is using has been updated to 64-bit. I instructed commandbox to load openjdk11 and I believe commandbox popped up a message with link for me to update the jdk again, which I did without error.
Following these updates I was again able to connect to my mariaDB database and otherwise have all the functionality that I expected.
Thank you very much for your assistance and guidance during the process, I would likely still be floundering.
-Rick