Troubleshooting
Problem
The Application Server Servant Region log shows the following message even though log4j2.enableJndiJdbc=true is set:
ERROR JNDI must be enabled by setting log4j2.enableJndiJdbc=true
Symptom
The servant log shows:
ERROR JNDI must be enabled by setting log4j2.enableJndiJdbc=true
ERROR No ConnectionSource provided: connectionSource
ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.db.jdbc.JdbcAppender for element JDBC org.apache.logging.log4j.core.config.ConfigurationException: Arguments given for element JDBC are invalid: field 'connectionSource' has invalid value 'null'
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectFields(PluginBuilder.java:210)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:121)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1120)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1045)
ERROR No ConnectionSource provided: connectionSource
ERROR Could not create plugin of type class org.apache.logging.log4j.core.appender.db.jdbc.JdbcAppender for element JDBC org.apache.logging.log4j.core.config.ConfigurationException: Arguments given for element JDBC are invalid: field 'connectionSource' has invalid value 'null'
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.injectFields(PluginBuilder.java:210)
at org.apache.logging.log4j.core.config.plugins.util.PluginBuilder.build(PluginBuilder.java:121)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createPluginObject(AbstractConfiguration.java:1120)
at org.apache.logging.log4j.core.config.AbstractConfiguration.createConfiguration(AbstractConfiguration.java:1045)
....
Cause
This issue can be caused by an invalid value in the "server name" field in the "Common and required data source properties" section in the Datasource configuration.
This message can be caused if the server name is either missing or does not match the name of the server being configured.
Diagnosing The Problem
In the admin console look in the Datasource configuration under the "Common and required data source properties" section.
Make sure that the "Server name" contains the correct name of the server.
Check the resources.xml file under <resources.jdbc:JDBCProvider..<
and look for
name="serverName" type="java.lang.String" value="WrongOrNoName" description="The TCP/IP address or host name for the DRDA server.
Resolving The Problem
Correct the Server name to reflect the name of the respective server and is not null (empty/blank) either.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"ARM Category":[{"code":"a8m50000000CdPoAAK","label":"WebSphere Application Server traditional-All Platforms-\u003EORB-Naming-\u003EJNDI Naming-\u003EOther JNDI problem"}],"ARM Case Number":"TS011900868","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Product Synonym
WebSphere Application Server for z/OS; WebSphere Application Server
Was this topic helpful?
Document Information
Modified date:
09 May 2023
UID
ibm16988961