Android Question Setting up RDC on SQL Server 2012 issue

D

damos911

Member
Licensed User
Longtime User
Having issues setting up RDC, setup file looks like this:

B4X: 
DriverClass=com.microsoft.sqlserver.jdbc.SQLServerDriver
JdbcUrl=jdbc:sqlserver://WIN-JN25GDPVVKR;databaseName=ePlanner

#SQL Server
#DriverClass=net.sourceforge.jtds.jdbc.Driver
#JdbcUrl=jdbc:jtds:sqlserver://<database server ip>/<database>

User=sa
Password=***********
ServerPort=17178

LOG FROM RDC

B4X: 
trace: 10]
2014-06-20 15:37:36.496:INFO::Started SelectChannelConnector@0.0.0.0:17178 START
ING
Jun 20, 2014 3:37:43 PM com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource ge
tPoolManager
INFO: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acqu
ireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCo
mmitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> fa
lse, checkoutTimeout -> 20000, connectionCustomizerClassName -> null, connection
TesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceN
ame -> sleme4921evfv461vekqfy|6bfd472, debugUnreturnedConnectionStackTraces -> f
alse, description -> null, driverClass -> com.microsoft.sqlserver.jdbc.SQLServer
Driver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false
, identityToken -> sleme4921evfv461vekqfy|6bfd472, idleConnectionTestPeriod -> 6
00, initialPoolSize -> 3, jdbcUrl -> jdbc:sqlserver://WIN-JN25GDPVVKR;databaseNa
me=ePlanner, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, maxIdleTime
-> 1800, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 15, maxStatements ->
150, maxStatementsPerConnection -> 0, minPoolSize -> 3, numHelperThreads -> 3, p
referredTestQuery -> null, properties -> {user=******, password=******}, propert
yCycle -> 0, statementCacheNumDeferredCloseThreads -> 0, testConnectionOnCheckin
-> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeout -> 0,
userOverrides -> {}, usesTraditionalReflectiveProxies -> false ]
java.sql.SQLException: An attempt by a client to checkout a Connection has timed
out.
        at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:118)
        at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:77)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConne
ction(C3P0PooledConnectionPool.java:687)
        at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(A
bstractPoolBackedDataSource.java:140)
        at anywheresoftware.b4a.remotedatabase.Servlet.doGet(Servlet.java:64)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:538
)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
:478)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
er.java:937)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
406)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle
r.java:871)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:117)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper
.java:110)
        at org.eclipse.jetty.server.Server.handle(Server.java:346)
        at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.
java:589)
        at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete
(HttpConnection.java:1048)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:601)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214)

        at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:41
1)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEn
dPoint.java:535)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEnd
Point.java:40)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool
.java:529)
        at java.lang.Thread.run(Thread.java:745)
Caused by: com.mchange.v2.resourcepool.TimeoutException: A client timed out whil
e waiting to acquire a resource from com.mchange.v2.resourcepool.BasicResourcePo
ol@164c7983 -- timeout at awaitAvailable()
        at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicRes
ourcePool.java:1416)
        at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(
BasicResourcePool.java:606)
        at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicR
esourcePool.java:526)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutAndMarkConn
ectionInUse(C3P0PooledConnectionPool.java:755)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConne
ction(C3P0PooledConnectionPool.java:682)
        ... 21 more
Jun 20, 2014 3:45:49 PM com.mchange.v2.resourcepool.BasicResourcePool$ScatteredA
cquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@281e
dacc -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to
acquire a needed new resource, we failed to succeed more than the maximum numbe
r of allowed acquisition attempts (30). Last acquisition attempt exception:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the ho
st WIN-JN25GDPVVKR, port 1433 has failed. Error: "Connection refused: connect. V
erify the connection properties. Make sure that an instance of SQL Server is run
ning on the host and accepting TCP/IP connections at the port. Make sure that TC
P connections to the port are not blocked by a firewall.".
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(S
QLServerException.java:190)
        at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExcepti
onToSQLServerException(SQLServerException.java:241)
        at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:22
43)
        at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLSer
verConnection.java:1309)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConne
ction.java:991)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerCon
nection.java:827)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.
java:1012)
        at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManag
erDataSource.java:146)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:195)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:184)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionRe
sourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:200)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResource
Pool.java:1086)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPe
ndingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1073)
        at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourc
ePool.java:44)
        at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.ru
n(BasicResourcePool.java:1810)
        at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(Thre
adPoolAsynchronousRunner.java:648)

Jun 20, 2014 3:45:49 PM com.mchange.v2.resourcepool.BasicResourcePool forceKillA
cquires
WARNING: Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicR
esourcePool@164c7983 is interrupting all Threads waiting on a resource to check
out. Will try again in response to new client requests.
Jun 20, 2014 3:45:50 PM com.mchange.v2.resourcepool.BasicResourcePool$ScatteredA
cquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@3f43
00e -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to
acquire a needed new resource, we failed to succeed more than the maximum number
of allowed acquisition attempts (30). Last acquisition attempt exception:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the ho
st WIN-JN25GDPVVKR, port 1433 has failed. Error: "Connection refused: connect. V
erify the connection properties. Make sure that an instance of SQL Server is run
ning on the host and accepting TCP/IP connections at the port. Make sure that TC
P connections to the port are not blocked by a firewall.".
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(S
QLServerException.java:190)
        at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExcepti
onToSQLServerException(SQLServerException.java:241)
        at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:22
43)
        at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLSer
verConnection.java:1309)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConne
ction.java:991)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerCon
nection.java:827)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.
java:1012)
        at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManag
erDataSource.java:146)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:195)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:184)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionRe
sourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:200)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResource
Pool.java:1086)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPe
ndingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1073)
        at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourc
ePool.java:44)
        at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.ru
n(BasicResourcePool.java:1810)
        at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(Thre
adPoolAsynchronousRunner.java:648)

Jun 20, 2014 3:45:50 PM com.mchange.v2.resourcepool.BasicResourcePool forceKillA
cquires
WARNING: Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicR
esourcePool@164c7983 is interrupting all Threads waiting on a resource to check
out. Will try again in response to new client requests.
Jun 20, 2014 3:45:50 PM com.mchange.v2.resourcepool.BasicResourcePool$ScatteredA
cquireTask run
WARNING: com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask@17fd
8d42 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to
acquire a needed new resource, we failed to succeed more than the maximum numbe
r of allowed acquisition attempts (30). Last acquisition attempt exception:
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the ho
st WIN-JN25GDPVVKR, port 1433 has failed. Error: "Connection refused: connect. V
erify the connection properties. Make sure that an instance of SQL Server is run
ning on the host and accepting TCP/IP connections at the port. Make sure that TC
P connections to the port are not blocked by a firewall.".
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(S
QLServerException.java:190)
        at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExcepti
onToSQLServerException(SQLServerException.java:241)
        at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:22
43)
        at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLSer
verConnection.java:1309)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConne
ction.java:991)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerCon
nection.java:827)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.
java:1012)
        at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManag
erDataSource.java:146)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:195)
        at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnecti
on(WrapperConnectionPoolDataSource.java:184)
        at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionRe
sourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:200)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResource
Pool.java:1086)
        at com.mchange.v2.resourcepool.BasicResourcePool.doAcquireAndDecrementPe
ndingAcquiresWithinLockOnSuccess(BasicResourcePool.java:1073)
        at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourc
ePool.java:44)
        at com.mchange.v2.resourcepool.BasicResourcePool$ScatteredAcquireTask.ru
n(BasicResourcePool.java:1810)
        at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(Thre
adPoolAsynchronousRunner.java:648)

Jun 20, 2014 3:45:50 PM com.mchange.v2.resourcepool.BasicResourcePool forceKillA
cquires
WARNING: Having failed to acquire a resource, com.mchange.v2.resourcepool.BasicR
esourcePool@164c7983 is interrupting all Threads waiting on a resource to check
out. Will try again in response to new client requests.




Any help would be appreciated :-D
 
Sort by date Sort by votes
D

damos911

Member
Licensed User
Longtime User
I did try the IP address but it is a public IP address not a local IP address, would that matter? Will try jtds driver now and post back to see if it worked.
 
Upvote 0
D

damos911

Member
Licensed User
Longtime User
Its on a VPS and I can RDP to the server so yes it's accessible, but I am running the RDC on the VPS itself. I have tried to put it 127.0.0.1, Machine name, machine name/sql DB name, external IP address, localhost... and still no joy *cries* lol
 
Upvote 0
alienhunter

alienhunter

Active Member
Licensed User
Longtime User
Erel said:
127.0.0.1 is the correct address if RDC is running on the same machine.
Click to expand...

I always put the port too 127.0.0.1 :5555 , it works in my case , got mysql postgres and ms sql running with rdc no problems at all with ms sql 2012, i have to go to work and i will post the connection in rdc ,
 
Upvote 0
alienhunter

alienhunter

Active Member
Licensed User
Longtime User
damos911 said:
Thanks, will try again tomorrow.
Click to expand...
B4X: 
#Lines starting with '#' are comments.
#Backslash character at the end of line means that the command continues in the next line.
#DriverClass=com.mysql.jdbc.Driver
#JdbcUrl=jdbc:mysql://localhost/test?characterEncoding=utf8

#SQL Server
DriverClass=net.sourceforge.jtds.jdbc.Driver
JdbcUrl=jdbc:jtds:sqlserver://10.0.22.29:1433/database1233


#DriverClass=org.sqlite.JDBC
#JdbcUrl=jdbc:sqlite:C:/temp/test1.db

User=user123
Password=1234
ServerPort=19000
#If Debug is true then this file will be reloaded on every query.
#This is useful if you need to modify the queries.
Debug=true
 
Upvote 0
D

damos911

Member
Licensed User
Longtime User
Tried all suggestions but the SQL server still refusing to accept connections. Is there something I have to do on the server?
 
Upvote 0
D

damos911

Member
Licensed User
Longtime User
B4X: 
C:\RDC\RDC-Server\RDC-Server\RemoteDatabaseConnector>"C:\Program Files\Java\jdk1
.7.0_60\bin\java" -Xmx256m -cp .;libs\*;jdbc_driver\* anywheresoftware.b4a.remot
edatabase.RemoteServer
B4A Remote Database Connecter (version 0.9)
loading: C:\RDC\RDC-Server\RDC-Server\RemoteDatabaseConnector\config.properties
2014-06-21 11:46:41.171:INFO::jetty-7.4.2.v20110526
2014-06-21 11:46:41.343:INFO::started o.e.j.s.ServletContextHandler{/,null}
Jun 21, 2014 11:46:41 AM com.mchange.v2.log.MLog <clinit>
INFO: MLog clients using java 1.4+ standard logging.
Jun 21, 2014 11:46:42 AM com.mchange.v2.c3p0.C3P0Registry banner
INFO: Initializing c3p0-0.9.2.1 [built 20-March-2013 11:16:28 +0000; debug? true
; trace: 10]
2014-06-21 11:46:42.421:INFO::Started SelectChannelConnector@0.0.0.0:1433 STARTI
NG
Jun 21, 2014 11:47:16 AM com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource g
etPoolManager
INFO: Initializing c3p0 pool... com.mchange.v2.c3p0.ComboPooledDataSource [ acqu
ireIncrement -> 3, acquireRetryAttempts -> 30, acquireRetryDelay -> 1000, autoCo
mmitOnClose -> false, automaticTestTable -> null, breakAfterAcquireFailure -> fa
lse, checkoutTimeout -> 20000, connectionCustomizerClassName -> null, connection
TesterClassName -> com.mchange.v2.c3p0.impl.DefaultConnectionTester, dataSourceN
ame -> sleme4921g2ms0pbfbrri|4823ec74, debugUnreturnedConnectionStackTraces -> f
alse, description -> null, driverClass -> com.microsoft.sqlserver.jdbc.SQLServer
Driver, factoryClassLocation -> null, forceIgnoreUnresolvedTransactions -> false
, identityToken -> sleme4921g2ms0pbfbrri|4823ec74, idleConnectionTestPeriod -> 6
00, initialPoolSize -> 3, jdbcUrl -> jdbc:sqlserver://127.0.0.1:1433;instance=;d
atabaseName=ePlanner, maxAdministrativeTaskTime -> 0, maxConnectionAge -> 0, max
IdleTime -> 1800, maxIdleTimeExcessConnections -> 0, maxPoolSize -> 15, maxState
ments -> 150, maxStatementsPerConnection -> 0, minPoolSize -> 3, numHelperThread
s -> 3, preferredTestQuery -> null, properties -> {user=******, password=******}
, propertyCycle -> 0, statementCacheNumDeferredCloseThreads -> 0, testConnection
OnCheckin -> false, testConnectionOnCheckout -> false, unreturnedConnectionTimeo
ut -> 0, userOverrides -> {}, usesTraditionalReflectiveProxies -> false ]
Jun 21, 2014 11:47:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: 4d119dc2-8ead-4956-8034-9939addc2592
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:3 ClientConnectionId: 9dce32cb-1aa7-4c93-8e73-a70cabaa2921
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:1 ClientConnectionId: 74c5b332-9b89-494a-b83e-b8f0385381bf
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:16 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: 82c3d8f8-3f6f-4b81-b2ef-4df6d71e63b1
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:3 ClientConnectionId: da6ea2e2-2cd8-4f62-831a-f44208252de0
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:1 ClientConnectionId: ce9747b1-c3d9-4937-ad43-c4763cd3b438
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: 61a5fe84-f54b-45d8-9eaf-489648c8aeb6
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:3 ClientConnectionId: 134996f3-5a8e-4d32-9cf3-3d2bb25727f3
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:1 ClientConnectionId: 3303928f-94e1-46e6-a9fe-2fe34ef9eb47
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: c8002271-4872-43de-b00f-fde1c9e07ea7
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:3 ClientConnectionId: c27732d7-fcc4-4157-b378-f047840041a9
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:17 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:1 ClientConnectionId: 11dbf53d-4eca-40ac-8cf6-0860d4f00053
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:18 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: efd1c73e-c69f-49b1-93e6-6d99481c9b01
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:18 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:3 ClientConnectionId: fda493d4-5cef-4c5b-bcc0-a06f43b72297
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:18 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:1 ClientConnectionId: 2e2c70cc-b82a-40d6-8e8d-e58be5edaf3c
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
Jun 21, 2014 11:47:19 AM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelog
in
WARNING: ConnectionID:2 ClientConnectionId: ddf3b928-0e39-44b6-a964-4c3aa242ec1d
Prelogin error: host 127.0.0.1 port 1433 Unexpected response type:72
This is the new error I am getting using 127.0.0.1:1443
 
Upvote 0
D

damos911

Member
Licensed User
Longtime User
Awesome!! That was the next thoughts I was having as we are using a VPS to run our application. So I got thinking how many connections could this RDC handle. I'm looking at 1,000s of android phones connecting. Would it handle this do you think. Maybe 10,000s phones if we can get our app out there?
We want to maximize the use of our VPS by running 3 different DB's, 1 for each application and 100,000s of phones accessing them? Would this be possible? Or new VPS for each app?
 
Upvote 0
alienhunter

alienhunter

Active Member
Licensed User
Longtime User
damos911 said:
Awesome!! That was the next thoughts I was having as we are using a VPS to run our application. So I got thinking how many connections could this RDC handle. I'm looking at 1,000s of android phones connecting. Would it handle this do you think. Maybe 10,000s phones if we can get our app out there?
We want to maximize the use of our VPS by running 3 different DB's, 1 for each application and 100,000s of phones accessing them? Would this be possible? Or new VPS for each app?
Click to expand...


? what app do you intend to write ?
 
Upvote 0
You must log in or register to reply here.

Similar Threads

D
  • Solved
Android Question jRDC2 MSSQL connection problem
Replies
1
Views
886
Daica
D
M
  • Question
Android Question jRDC2 error
Replies
3
Views
846
Gabino A. de la Gala
Gabino A. de la Gala
Marlou Fin
  • Question
Android Question jRDC2 MSSQL getting error fetching connection when connecting
Replies
6
Views
3K
Marlou Fin
Marlou Fin
C
  • Question
Android Question MSSQL-JDBC Minimalistic Example
2
Replies
27
Views
21K
MrKim
MrKim
O
  • Question
Android Question jRDC2 MS SQLSERVER
Replies
3
Views
2K
OliverA
OliverA
Top