title: The Message-Driven EJB unable to connect JMS Destination stating Error creating the db_connection
body: <p>we have Oracle OSB 11g which is connecting to Oracle 12C DB in remote location or a different LAN.</p>
  
  <p>THE WebLogic EJBs connecting to Oracle AQs via JMS/JDBC and currently we are having issues with them.</p>
  
  <p>the WLS logs says:</p>
  
  <pre><code>####&lt;Sep 21, 2018 9:15:51.083 AM GMT+00:00&gt; &lt;Warning&gt; &lt;EJB&gt; &lt;10.170.128.102&gt; 
  &lt;osb02_m1&gt; &lt;[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default 
  (self-tuning)'&gt; &lt;&lt;anonymous&gt;&gt; &lt;&gt; 
  &lt;e10b4740d6c6fa2e:-5f6b2f84:165f9d83f34:-8000-0000000000000f87&gt; 
  &lt;1537521351083&gt; &lt;BEA-010096&gt; &lt;The Message-Driven EJB: 
  RequestEJB3103778799539238415X86e7f92.165e6e1ae31.X725d is unable to connect 
  to the JMS destination or bind to JCA resource adapter: queue/ProvRequestAQ. 
  Connection failed after 2,609 attempts. The MDB will attempt to 
  reconnect/rebind every 10 seconds. This log message will repeat every 600 
  seconds until the condition clears.&gt;
  
  ####&lt;Sep 21, 2018 9:15:51.083 AM GMT+00:00&gt; &lt;Warning&gt; &lt;EJB&gt; &lt;10.170.128.102&gt; 
  &lt;osb02_m1&gt; &lt;[ACTIVE] ExecuteThread: '18' for queue: 'weblogic.kernel.Default 
  (self-tuning)'&gt; &lt;&lt;anonymous&gt;&gt; &lt;&gt; 
  &lt;e10b4740d6c6fa2e:-5f6b2f84:165f9d83f34:-8000-0000000000000f87&gt; 
  &lt;1537521351083&gt; &lt;BEA-010061&gt; &lt;The Message-Driven EJB: 
  RequestEJB3103778799539238415X86e7f92.165e6e1ae31.X725d is unable to connect 
  to the JMS destination: queue/ProvRequestAQ. The Error was:
  oracle.jms.AQjmsException: Error creating the db_connection
  Nested exception: java.lang.UnsupportedOperationException: Remote JDBC 
  disabled
  Nested exception: java.lang.UnsupportedOperationException: Remote JDBC 
  disabled&gt;
  </code></pre>
  
  <p>I searched in internet and found the solution that I have to add the below parameter and add to setDomainEnv.sh and restart the WebLogic admins and managed servers, but still this issue is not resolved. I also checked that the DB User used to connect the DB has enqueue/dequeue privileges over the Oracle queues.</p>
  
  <p>Parameter was </p>
  
  <pre><code>WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled=true"
  </code></pre>