In Coldfusion 11 on Datasource Verification, getting the error Timed out trying to establish connection
After an ABNORMAL shutdown of Coldfusion server and Oracle Database server, I started both Database & Coldfusion servers. Then I tried to verify Datasource from Coldfusion Admin, I am getting the below error for few hours.
Connection verification failed for data source:
java.sql.SQLException: Timed out trying to establish connection. The
root cause was that: java.sql.SQLException: Timed out trying to
establish connection.
So I created another datasource with different datasource name for the same database. But it worked properly.
After a few hours both datasouces worked.
Datasource connection Details below:
CF Data Source Name:
xxxxxxx
JDBC URL:
jdbc:macromedia:oracle://ip_address:port_no;SERVICENAME=;sendStringParametersAsUnicode=false;MaxPooledStatements=700;AlternateServers=(ip_address:port_no);ConnectionRetryCount=5;ConnectionRetryDelay=5
Driver Class:
macromedia.jdbc.MacromediaDriver
Why I am getting the timeout error after abnormal shutdown? How to fix this issue permanently? Do we need to clean up something like the cache in Coldfusion server?
oracle coldfusion odbc datasource coldfusion-11
edited Nov 14 '18 at 16:07
Shawn
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
add a comment |
After an ABNORMAL shutdown of Coldfusion server and Oracle Database server, I started both Database & Coldfusion servers. Then I tried to verify Datasource from Coldfusion Admin, I am getting the below error for few hours.
Connection verification failed for data source:
java.sql.SQLException: Timed out trying to establish connection. The
root cause was that: java.sql.SQLException: Timed out trying to
establish connection.
So I created another datasource with different datasource name for the same database. But it worked properly.
After a few hours both datasouces worked.
Datasource connection Details below:
CF Data Source Name:
xxxxxxx
JDBC URL:
jdbc:macromedia:oracle://ip_address:port_no;SERVICENAME=;sendStringParametersAsUnicode=false;MaxPooledStatements=700;AlternateServers=(ip_address:port_no);ConnectionRetryCount=5;ConnectionRetryDelay=5
Driver Class:
macromedia.jdbc.MacromediaDriver
Why I am getting the timeout error after abnormal shutdown? How to fix this issue permanently? Do we need to clean up something like the cache in Coldfusion server?
oracle coldfusion odbc datasource coldfusion-11
edited Nov 14 '18 at 16:07
Shawn
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
1
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55
add a comment |
After an ABNORMAL shutdown of Coldfusion server and Oracle Database server, I started both Database & Coldfusion servers. Then I tried to verify Datasource from Coldfusion Admin, I am getting the below error for few hours.
Connection verification failed for data source:
java.sql.SQLException: Timed out trying to establish connection. The
root cause was that: java.sql.SQLException: Timed out trying to
establish connection.
So I created another datasource with different datasource name for the same database. But it worked properly.
After a few hours both datasouces worked.
Datasource connection Details below:
CF Data Source Name:
xxxxxxx
JDBC URL:
jdbc:macromedia:oracle://ip_address:port_no;SERVICENAME=;sendStringParametersAsUnicode=false;MaxPooledStatements=700;AlternateServers=(ip_address:port_no);ConnectionRetryCount=5;ConnectionRetryDelay=5
Driver Class:
macromedia.jdbc.MacromediaDriver
Why I am getting the timeout error after abnormal shutdown? How to fix this issue permanently? Do we need to clean up something like the cache in Coldfusion server?
oracle coldfusion odbc datasource coldfusion-11
edited Nov 14 '18 at 16:07
Shawn
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
After an ABNORMAL shutdown of Coldfusion server and Oracle Database server, I started both Database & Coldfusion servers. Then I tried to verify Datasource from Coldfusion Admin, I am getting the below error for few hours.
Connection verification failed for data source:
java.sql.SQLException: Timed out trying to establish connection. The
root cause was that: java.sql.SQLException: Timed out trying to
establish connection.
So I created another datasource with different datasource name for the same database. But it worked properly.
After a few hours both datasouces worked.
Datasource connection Details below:
CF Data Source Name:
xxxxxxx
JDBC URL:
jdbc:macromedia:oracle://ip_address:port_no;SERVICENAME=;sendStringParametersAsUnicode=false;MaxPooledStatements=700;AlternateServers=(ip_address:port_no);ConnectionRetryCount=5;ConnectionRetryDelay=5
Driver Class:
macromedia.jdbc.MacromediaDriver
Why I am getting the timeout error after abnormal shutdown? How to fix this issue permanently? Do we need to clean up something like the cache in Coldfusion server?
oracle coldfusion odbc datasource coldfusion-11
oracle coldfusion odbc datasource coldfusion-11
edited Nov 14 '18 at 16:07
Shawn
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
edited Nov 14 '18 at 16:07
Shawn
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
edited Nov 14 '18 at 16:07
Shawn
3,53511324
edited Nov 14 '18 at 16:07
Shawn
3,53511324
edited Nov 14 '18 at 16:07
Shawn
3,53511324
3,53511324
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
asked Nov 14 '18 at 5:41
Rojin TerranceRojin Terrance
243
243
1
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55
add a comment |
1
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55
1
1
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293828%2fin-coldfusion-11-on-datasource-verification-getting-the-error-timed-out-trying%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53293828%2fin-coldfusion-11-on-datasource-verification-getting-the-error-timed-out-trying%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
How large is the database? Maybe it wasn't fully back on line when you tried to verify the original datasource. An abnormal shutdown can cause a database to run through various integrity checks when it restarts.
– Shawn
Nov 14 '18 at 16:09
The database is too large. Some table contains more than 100000 records. I tried Verifying datasource for 2-3 hours. But the same database connection from another JAVA Application works perfectly.
– Rojin Terrance
Nov 19 '18 at 9:14
100K records isn't a whole lot, unless they are very wide tables with heavy datatypes. If it's taking 2-3 hours just to verify the datasource, then you have another issue somewhere. There may be some corruption, especially after an abnormal shutdown. I would suggest a hard integrity check of that database (and a backup). What version of Oracle?
– Shawn
Nov 19 '18 at 15:55