SMAT@Azure Platforms

Unable to get managed connection for java:jboss……

SMAT317 — Fri, 17 Oct 2014 03:33:33 GMT

VMs are not able to connect to SQL Azure Server. Ping to the SQL server is also not resolving to any IP. I also observe that the VMs are not able to connect to services running on other VM within the same cloud service.

Error:
ERROR:

ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/saoDataSource
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:527) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) [spring-beans-3.1.2.RELEASE.jar:3.1.2.RELEASE]
        at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:733) [spring-context-3.1.2.RELEASE.jar:3.1.2.RELEASE]
..
..
..
..
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host tiuexjq7la.database.windows.net, port 1433 has failed. Error: "null. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:190)
        at com.microsoft.sqlserver.jdbc.SQLServerException.ConvertConnectExceptionToSQLServerException(SQLServerException.java:241)
        at com.microsoft.sqlserver.jdbc.SocketFinder.findSocket(IOBuffer.java:2243)
        at com.microsoft.sqlserver.jdbc.TDSChannel.open(IOBuffer.java:491)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1309)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:1012)
        at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:254)

Troubleshooting:
Unable to ping the server at XXXXXX.database.windows.net. Able to ping from local server but unable to connect from this particular VM which has the issue.

UDL connecting fine from the other client but fails from the VM on azure.

ipconfig /registerdns -- Same issue

The pointer came from the fact that we were unable to browse to websites from this particular Virtual Machine.

Internet options, everything looked fine. Proxy and other connection related settings were in place.

nslookup was erroring:

C:\Users\xxxxxxx>nslookup
DNS request timed out.
timeout was 2 seconds.
Default Server: UnKnown
Address: xx.xxx.xx.xxx

> xxxxxxx.com
Server: UnKnown
Address: xx.xxx.xx.xxx

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
> xxxxxxx.com
C:\Users\saoadmin>

It was a custom DNS server.
On further probing, the custom DNS server wasn't configured properly and also it was not in use.

So we deleted the DNS server and rebooted the VMs in question.

After reboot, nslookup was working fine.

SQL Connectivity came back up and were able to browse to websites.

So in conclusion, when you see the above error as mentioned in the stack, there is nothing to check from SQL Server side or from the port 1433 perspective.

Reviewed By: Lalitesh Kumar

Unable to listen on a certain port while setting up a mirror DB

smat — Mon, 24 Aug 2009 03:24:00 GMT

In one of the scenarios, my mirror server wasn't able to connect using port 5022 but when I explicitly opened this port, it would start working as expected but I don't need to open any ports maunally while setting up a mirror.

Looked at the detour log from networking point of view and i could see that there are no requests for opening the port

20090808002116916 988 50.60: traceapi: 030 bind(70c,576150,10)
20090808002116916 988 50.60: traceapi: 030   Binding to port:1433
20090808002116916 988 50.60: traceapi: 030   bind(,,) -> 0
20090808002116916 988 50.60: traceapi: 030   Bind returned:0
20090808002116916 988 50.60: traceapi: 042 bind(778,9ef23d0,10)
20090808002116916 988 50.60: traceapi: 042   Binding to port:1434
20090808002116916 988 50.60: traceapi: 042   bind(,,) -> 0
20090808002116916 988 50.60: traceapi: 042   Bind returned:0

Also in SQL error log, it wouldn't show up to be listening on that specific port.

So sql server isn't sending the request to create and bind to port 5022. I added the port number to String value (REG_SZ) 5022 here HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2\MSSQLServer\SuperSocketNetLib\Tcp\IPAll and this worked which is equal to opening the port manually.

SQL Server service broker should take care of this part.

Ran

select is_broker_enabled, service_broker_guid from sys.databases where database_id =2

Result -- 0 which is disabled.

GUID : AA0539D0-3614-4A14-AC76-EF4AFEE5AD00 -- So Service broked is not enabled on TempDB database.

Ran:

DROP ENDPOINT endpoint_mirroring
ALTER DATABASE tempdb SET NEW_BROKER

Now while looking at netstat, I saw that 5022 is on a time_wait state. So removed the port number from the registry which was earlier added and now all is well.

Analyzing 32bit dumps taken on a 64bit machine using 64bit debugger

smat — Wed, 12 Aug 2009 21:36:00 GMT

Hi,

I came across this interesting situation while trying to analyze some dumps of a x86 bit application on a x64 machine where the dumps were taken using x64 version of the debugger.

Before going ahead, let me tell you that if this situation arises then the best bet would be take the dumps using x86 version of the debugger. However if you do come across these kind of dumps which are taken using x64 version of the debuggers then below is what you need to do.

Assuming that you have installed Debugging tool for windows under \Debuggers

When you do a kb in the dump you will see something like below with not much stack inforamtion.

0:000> kb

RetAddr : Args to Child : Call Site

00000000`78b840e5 : 00000023`7d61c888 00000000`00000023 00000000`00000202 00000000`0014e0e0 : wow64cpu!CpupSyscallStub+0x9 [d:\srvrtm\base\wow64\cpu\amd64\cpu\amd64\simulate.asm @ 983]

00000000`6b006a5a : 00000000`fffdf000 00000000`00080001 00000000`00000000 00000000`00000000 : wow64cpu!Thunk0ArgReloadState+0x1a [d:\srvrtm\base\wow64\cpu\amd64\cpu\amd64\simulate.asm @ 845]

00000000`6b005e0d : 00000000`00000000 00000000`0006f1b0 00000000`0006fab0 00000000`00000000 : wow64!RunCpuSimulation+0xa [d:\nt\base\wow64\wow64\wow64.c @ 1358]

00000000`77ed8030 : 00000000`000832f0 00000000`00000000 00000000`0006fab0 00000000`00000003 : wow64!Wow64LdrpInitialize+0x2ed [d:\nt\base\wow64\wow64\wow64.c @ 288]

00000000`77ed582f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitializeProcess+0x1538 [d:\nt\base\ntdll\ldrinit.c @ 3043]

00000000`77ef30a5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!_LdrpInitialize+0x18f [d:\nt\base\ntdll\ldrinit.c @ 1138]

00000000`77d59620 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!KiUserApcDispatch+0x15 [d:\nt\base\ntos\rtl\amd64\trampoln.asm @ 194]

00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d59620

00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000020`78746341 : 0x0

00000000`00000000 : 00000000`00000000 00000000`00000000 00000020`78746341 00005370`00000001 : 0x0

00000000`00000000 : 00000000`00000000 00000020`78746341 00005370`00000001 00000000`00000124 : 0x0

00000000`00000000 : 00000020`78746341 00005370`00000001 00000000`00000124 00000000`00000020 : 0x0

00000020`78746341 : 00005370`00000001 00000000`00000124 00000000`00000020 00000001`00000014 : 0x0

00005370`00000001 : 00000000`00000124 00000000`00000020 00000001`00000014 00000034`0000000a : 0x20`78746341

After opening the dump, load wow64exts which is located at Debuggers\winxp. e.g.

0:000> .load wow64exts

0:000> !wow64exts.k

Walking 64bit Stack...

Child-SP RetAddr Call Site

00000000`0006edf8 00000000`78b840e5 wow64cpu!CpupSyscallStub+0x9 [d:\srvrtm\base\wow64\cpu\amd64\cpu\amd64\simulate.asm @ 983]

00000000`0006ee00 00000000`6b006a5a wow64cpu!Thunk0ArgReloadState+0x1a [d:\srvrtm\base\wow64\cpu\amd64\cpu\amd64\simulate.asm @ 845]

00000000`0006ee70 00000000`6b005e0d wow64!RunCpuSimulation+0xa [d:\nt\base\wow64\wow64\wow64.c @ 1358]

00000000`0006eea0 00000000`77ed8030 wow64!Wow64LdrpInitialize+0x2ed [d:\nt\base\wow64\wow64\wow64.c @ 288]

00000000`0006f6d0 00000000`77ed582f ntdll!LdrpInitializeProcess+0x1538 [d:\nt\base\ntdll\ldrinit.c @ 3043]

00000000`0006f9d0 00000000`77ef30a5 ntdll!_LdrpInitialize+0x18f [d:\nt\base\ntdll\ldrinit.c @ 1138]

00000000`0006fab0 00000000`77d59620 ntdll!KiUserApcDispatch+0x15 [d:\nt\base\ntos\rtl\amd64\trampoln.asm @ 194]

00000000`0006ffa8 00000000`00000000 0x77d59620

00000000`0006ffb0 00000000`00000000 0x0

00000000`0006ffb8 00000000`00000000 0x0

00000000`0006ffc0 00000000`00000000 0x0

00000000`0006ffc8 00000000`00000000 0x0

00000000`0006ffd0 00000000`00000000 0x0

00000000`0006ffd8 00000000`00000000 0x0

00000000`0006ffe0 00000000`00000000 0x0

00000000`0006ffe8 00000000`00000000 0x0

00000000`0006fff0 00000000`00000000 0x0

00000000`0006fff8 00000000`00000000 0x0

00000000`00070000 00000020`78746341 0x0

00000000`00070008 00005370`00000001 0x20`78746341

Walking 32bit Stack...

*** WARNING: symbols timestamp is wrong 0x45d6cc72 0x45d709ff for ntdll.dll

ChildEBP RetAddr

0014fc0c 7d4d8c82 ntdll_7d600000!NtWaitForSingleObject+0x15 [d:\nt\base\ntdll\wow6432\obj\i386\usrstubs.asm @ 133]

0014fc7c 7d4d8bf1 kernel32!WaitForSingleObjectEx+0xac [d:\nt\base\win32\client\synch.c @ 1246]

0014fc90 5a36467a kernel32!WaitForSingleObject+0x12 [d:\nt\base\win32\client\synch.c @ 1147]

0014fca0 5a366e63 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10 [d:\srvrtm\inetsrv\iis\iisrearc\iisplus\ulatq\wpcontext.cxx @ 885]

0014fca8 5a3af42d w3dt!UlAtqStartListen+0x2d [d:\srvrtm\inetsrv\iis\iisrearc\iisplus\ulatq\ulatq.cxx @ 241]

0014fcb8 5a3bc335 w3core!W3_SERVER::StartListen+0xbd [d:\nt\inetsrv\iis\iisrearc\iisplus\ulw3\w3server.cxx @ 1388]

0014ff0c 0100187c w3core!UlW3Start+0x26e [d:\nt\inetsrv\iis\iisrearc\iisplus\ulw3\ulw3.cxx @ 242]

0014ff44 01001a27 w3wp!wmain+0x22a [d:\nt\inetsrv\iis\iisrearc\iisplus\w3wp\w3wp.cxx @ 269]

0014ffc0 7d4e7d2a w3wp!wmainCRTStartup+0x12f [d:\nt\base\crts\crtw32\dllstuff\crtexe.c @ 498]

0014fff0 00000000 kernel32!BaseProcessStart+0x28 [d:\nt\base\win32\client\support.c @ 838]

Now call the sw command which is a part of wow64exts extension.

Sw -- Switch between 32-bit and 64-bit mode .

!wow64exts.sw

Now below is what you see which makes sense and will let you debug further.

0:000:x86> kb

ChildEBP RetAddr Args to Child

0014fc0c 7d4d8c82 000001d0 00000000 00000000 ntdll_7d600000!NtWaitForSingleObject+0x15 [d:\nt\base\ntdll\wow6432\obj\i386\usrstubs.asm @ 133]

0014fc7c 7d4d8bf1 000001d0 ffffffff 00000000 kernel32!WaitForSingleObjectEx+0xac [d:\nt\base\win32\client\synch.c @ 1246]

0014fc90 5a36467a 000001d0 ffffffff 00000000 kernel32!WaitForSingleObject+0x12 [d:\nt\base\win32\client\synch.c @ 1147]

0014fca0 5a366e63 003d50c0 5a3af42d 00000000 w3dt!WP_CONTEXT::RunMainThreadLoop+0x10 [d:\srvrtm\inetsrv\iis\iisrearc\iisplus\ulatq\wpcontext.cxx @ 885]

0014fca8 5a3af42d 00000000 64711dcf 00000000 w3dt!UlAtqStartListen+0x2d [d:\srvrtm\inetsrv\iis\iisrearc\iisplus\ulatq\ulatq.cxx @ 241]

0014fcb8 5a3bc335 01001418 010013e4 010012d0 w3core!W3_SERVER::StartListen+0xbd [d:\nt\inetsrv\iis\iisrearc\iisplus\ulw3\w3server.cxx @ 1388]

0014ff0c 0100187c 00000005 003d3920 00000000 w3core!UlW3Start+0x26e [d:\nt\inetsrv\iis\iisrearc\iisplus\ulw3\ulw3.cxx @ 242]

0014ff44 01001a27 00000005 003d3920 003d4590 w3wp!wmain+0x22a [d:\nt\inetsrv\iis\iisrearc\iisplus\w3wp\w3wp.cxx @ 269]

0014ffc0 7d4e7d2a 00000000 00000000 fffdf000 w3wp!wmainCRTStartup+0x12f [d:\nt\base\crts\crtw32\dllstuff\crtexe.c @ 498]

0014fff0 00000000 010018f8 00000000 000000c8 kernel32!BaseProcessStart+0x28 [d:\nt\base\win32\client\support.c @ 838]

If it happens to be duplicate of any existing posts, treat it as purely coincidental.