Unable to use JDBC built-in connector within VS COde
Severity
P2 - High (Major functionality broken)
Describe the Bug with repro steps
Expected behaviour
- I can use the JDBC connector to connect to an database (eg: Oracle)
Actual behaviour
- Error message is "Failed to create connection: JDBC client library is missing. Please add pre-requisites JDBC Connector client library assemblies to the workflow application."
Steps:
- I have placed the "ojdbc8.jar" in the "...\lib\builtinOperationSdks\JAR" folder
- The following error message shows when I try to configure the connection
It's not clear if I need to install a JRE or JDK on my local machine for this to work.
It's also not clear which version of Java I should use if required, and also how I configure which version of Java is used when the Logic App is deployed (FUNCTIONS_EXTENSION_VERSION is set to ~4 and AzureFunctionsJobHost__extensionBundle__version is set to [1.*, 2.0.0))
Apologies if I've missed some documentation on this, I cannot find it anywhere :(
What type of Logic App Is this happening in?
Standard (VSCode)
Are you experiencing a regression?
I can upload the ojdbc8.jar in the Portal/Kudo and it works, so it appears to be a VS Code/documentation guidance issue
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
I'm unable to save the connection, so it's just a basic HTTP Request workflow atm
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"contentVersion": "1.0.0.0",
"actions": {},
"outputs": {},
"triggers": {
"When_an_HTTP_request_is_received": {
"type": "Request",
"kind": "Http"
}
}
},
"kind": "Stateful"
}
Screenshots or Videos
No response
Environment
- VS Code: 1.106.1
- Azure Logic App (Standard) extension: 5.185.10
Additional context
No response
@ccastrotrejo - hey 👋 - i see this got linked to another issue that was closed due to inactivity - is it possible to get someone to look at this?
That was my issue and it appears nobody ever looked at it. I think mine was possibly due to being in the azure government cloud for my workflow. However, you do need to have a JDK installed for this to work on your machine, you also need to make sure you enable multiple workers. In your local.settings.json you need: "AzureWebJobsFeatureFlags": "EnableMultiLanguageWorker".
hey @mnmilner - thanks for sharing your findings - did you find any MS docs on this or was the JDK install/settings all discovered via trial and error?
Were you able to work this out as well?
It's also not clear which version of Java I should use if required, and also how I configure which version of Java is used when the Logic App is deployed (FUNCTIONS_EXTENSION_VERSION is set to ~4 and AzureFunctionsJobHost__extensionBundle__version is set to [1.*, 2.0.0))
It was all trial and error. There is no documentation on that connector other than the standard information and some youtube videos that all assume you are in the portal. Because for this particular project I was working in the government cloud, I assumed that was part of my issue. I ended up installing JDK 21 or 22 (whatever is the most recent LTS version) and made sure to set environment variables like JAVA_HOME and added the bin directory to my path.