Problem with rds on exadata

Hi,
I have a problem with rds on exadata. After upgrading to uek kernel and patching to cell 11.2.3.3.0, I get following error:
Aug 18 16:17:36 exadb01 kernel: RDS/tcp: send to 192.168.10.5 returned -32, disconnecting and reconnecting
Aug 18 16:17:36 exadb01 kernel: RDS/tcp: send to 192.168.10.5 returned -32, disconnecting and reconnecting
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,4> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,0> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,0> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,4> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,0> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,0> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,4> dropped
Aug 18 16:17:36 exadb01 kernel: RDS/IB: connection <192.168.10.9,192.168.10.5,0> dropped
Aug 18 16:17:36 exadb01 kernel: BUG: scheduling while atomic: kworker/u:0/5/0x10000200
Aug 18 16:17:36 exadb01 kernel: Modules linked in: rds_rdma rds_tcp rds hidp rfkill lockd sunrpc ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr video sbs sbshc hed acpi_memhotplug acpi_ipmi ipmi_msghandler lp snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device serio_raw snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer drm snd parport_pc parport soundcore snd_page_alloc e1000 pata_acpi i2c_piix4 pcspkr i2c_core ata_generic dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_piix sd_mod crc_t10dif be2iscsi iscsi_boot_sysfs bnx2i cnic uio ipv6 cxgb3i libcxgbi cxgb3 mdio sg sr_mod cdrom iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi mpt2sas scsi_transport_sas raid_class ahci libahci ext3 jbd mbcache [last unloaded: rds]
Aug 18 16:17:36 exadb01 kernel: Pid: 5, comm: kworker/u:0 Not tainted 2.6.39-400.128.17.el5uek #1
Aug 18 16:17:36 exadb01 kernel: Call Trace:
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8105dc16>] __schedule_bug+0x66/0x70
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81504a15>] __schedule+0x645/0x6d0
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8148cb58>] ? tcp_write_xmit+0x238/0x2e0
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa02afee8>] ? e1000_tx_map+0x2b8/0x450 [e1000]
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8150704e>] ? common_interrupt+0xe/0x13
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8106a1ca>] __cond_resched+0x2a/0x40
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81504b2f>] _cond_resched+0x2f/0x40
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8147e505>] do_tcp_setsockopt+0x215/0x700
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8143b410>] ? dev_hard_start_xmit+0x200/0x530
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81506b3e>] ? _raw_spin_lock+0xe/0x20
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81457524>] ? sch_direct_xmit+0x84/0x1d0
Aug 18 16:17:36 exadb01 kernel: [<ffffffff812595d9>] ? put_dec+0x59/0x60
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81259918>] ? number+0x338/0x370
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81475496>] ? ip_finish_output+0x146/0x320
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81041009>] ? default_spin_lock_flags+0x9/0x10
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81506b84>] ? _raw_spin_lock_irqsave+0x34/0x50
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8106fdc8>] ? console_unlock+0xd8/0x110
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8147ea4a>] tcp_setsockopt+0x2a/0x40
Aug 18 16:17:36 exadb01 kernel: [<ffffffff814276f4>] sock_common_setsockopt+0x14/0x20
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa01e949e>] rds_tcp_cork+0x4e/0x60 [rds_tcp]
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa01e94ce>] rds_tcp_xmit_prepare+0x1e/0x20 [rds_tcp]
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa0616ec4>] rds_send_xmit+0x94/0x730 [rds]
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa06146b3>] ? rds_message_alloc+0x23/0x90 [rds]
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81041009>] ? default_spin_lock_flags+0x9/0x10
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa061762c>] rds_send_hb+0xcc/0x120 [rds]
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81041009>] ? default_spin_lock_flags+0x9/0x10
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa0613179>] rds_conn_probe_lanes+0x69/0x80 [rds]
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa06132c8>] rds_conn_drop+0x138/0x1f0 [rds]
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81428180>] ? lock_sock_nested+0x60/0x60
Aug 18 16:17:36 exadb01 kernel: [<ffffffffa01e87ac>] rds_tcp_state_change+0x7c/0x90 [rds_tcp]
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8147c131>] tcp_done+0x51/0x80
Aug 18 16:17:36 exadb01 kernel: [<ffffffff8148404e>] tcp_reset+0x3e/0x70
Aug 18 16:17:36 exadb01 kernel: [<ffffffff81484258>] tcp_validate_incoming+0x1d8/0x220
Aug 18 16:17:36 exadb01 kernel: [<ffffffff814906ac>] ? tcp_v4_inbound_md5_hash+0x6c/0x1b0
Aug 18 16:17:36 exadb01 kernel: [<ffffffff814890a7>] tcp_rcv_state_process+0x47/0x570
Can you help me?
Thank you,
Regards,

Hello 976232,
This type of issue would definitely be Oracle Support territory, so I'd be definitely checking in with them. A few clarifying questions you can expect to be asked:
- What is the impact on your system because of this error message
- How often does it happen
- Can you trigger it on demand?
Marc

Similar Messages

Problems with CF Builder + RDS + Windows XP.

I have been using CF Builder since the first beta, however I am missing out on most of the functionality because I can't get it to connect to RDS. I always get a 405 method not allowed.
Where I've seen this discussed (namely on Ray Camden's site) the suggestion was to change security in IIS. Of course IIS & security on XP is much more limited than on Windows Server. I have tried everything I can and can't get it to work.
Any thoughts?
-Bill

Hi Bill, yes, I can offer such help. In fact, I've long thought about offering a low-cost, fixed-fee option to solve any single problem.
Your request here, and another earlier today, have prompted me to go ahead and set that up. It's now enabled as a new engagement type at my http://www.carehart.org/consulting/ page (where I also discuss how I offer this as remote consulting, via Adobe Connect, which I usually perform in providing CF server troubleshooting.)
I help people solve problems with CFBuilder all the time (here and in other mailing lists), and I speak and write about using it extensively.
Still, some problems are just difficult to solve in email (plus there's no guarantee of one getting a reply from anyone, including myself, here). So I'd long considered offering a service to fill that gap. The two notes today prompted me to proceed with it.
You'll see it on the page as a "CFBuilder fixed-fee/single problem" option, for a flat $US75. That's for help in getting any one thing to work in CFBuilder, such as getting debugging to work, getting RDS to work, getting code insight to work, getting the ctrl+hover hyperlinking to work, solving slow performance problems, and so on.
Now, if someone gets their hackles up at the thought that they should have to pay for getting a problem solved with CFB, well, of course, you don't have to pay. That's why these forums are here. But as Bill says below, sometimes people are just willing to pay to solve a problem, and again some problems are just hard to do without being able to see what's going on and more easily explain how things need to be configured.
If paid support is not a solution for some readers, that's understandable. (I addressed this a little more in a lighthearted mention of the new option in my reply to the other forum thread here earlier today: http://forums.adobe.com/message/3056104#3056104).
My hope would be that, with my experience solving problems, we should be able to solve most of them quickly, which is good for both of us. I'm willing to take that risk and keep it a fixed fee (compared to my normal hourly rate of $US175 for CF server troubleshooting).
Of course, the fixed fee means there's no prorating of it if solved quickly. Think of it like a plumber, who has a fixed price for a service call, even if just to plug a single leak. You're not paying for the time to plug the leak (nor even to drive over), but for the value of stopping the leak, the plumber's knowledge of how and where to solve the problem, and his setting up a business to be there when you need him.
Conversely, though, there are sure to be some problems where I just can't solve them, even after a couple of hours (they may even be bugs in CFBuilder). In that case, to protect both of us, I offer the option to refund your money after those 2 hours (unless you feel there was still value in other aspects or information shared during the call).
Hope that's helpful, to Bill and to others. Feel free to mention it to others who may appreciate this when struggle at length with some CFBuilder problem.
/charlie

Problems with Win 7 64 bits printer configuration on RDS Web Access

hey All,
I have a scenario with RDS 2012 with Session host in 2008 R2 SP1, and on clients with windows XP SP3 and win 7 SP1 32 bits, printer configuration looks ok but in windows 7 64 bits it looks like a truncated configuration , i have been tested every solution
that was reported before, like changing GPO, install Drivers in the clients and in the server, changed display resolution (to print in video) and nothing works, is any issue or incompatibility reported in this cases ?
Thanks in advance
Breno Andrade

Hi,
Thanks for posting in Windows Server Forum.
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios.
If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.
Thanks for your Support & understanding.
Regards.
Dharmesh Solanki

There is a problem with the security certificate of the proxy server. Error code 18 and 38.

Hi All,
After several hours and a short night of sleep I'm out of ideas and hopefully someone here can help me trying to solve this one. First of all the situation:
Exchange 2013 on a remote location with a CA-certificate.
Outlook 2010 and 2013 on different locations, locally installed and on RDS.
When I open Outlook on my laptop all is fine, no errors, good sync, no problem. But when I open Outlook on our Remote Desktop Servers with Outlook 2013 I'm getting errors like "There is a problem with the security certificate of the proxy server. The
name on the security certificate is invalid or does not match the name of the site. Outlook is unable to connect to this server. (Error code 18)". Opening Outlook 2010 the message is the same, but the error code now is 38.
After this Outlook opens and is working, there's one more error though. After a while an security warning pops up with the message: "Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the
site's security certificate. * The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority. * The security certificate is valid. * The name on the security
certificate is invalid or does not match the name of the site."
Strangest thing is, it is the certificate of my RDS! It isn't my valid en officially bought certificate from my mailserver. What's going on? I'm out of options, what I've tried so far (in random order):
- restarting mailserver and AD;
- restarting switches;
- restarting routers;
- restarting RDS, AD and all other servers;
- bypassed proxyserver for RDS;
- created a new profile;
- checked recently installed updates;
- checked certificate on mailserver;
- checked RDS on a different location, working fine.
Nothing helped, what can I do next? Please advice.
Regards.

Found a thread that solves half my problem (https://social.technet.microsoft.com/Forums/office/en-US/70d18244-889a-4d95-ac3f-e234672a82b2/there-is-a-problem-with-the-proxy-servers-security-certificate-error-when-starting-outlook?forum=exchangesvrclients).
The first message can be suppressed by adding this to the Exchange config:
set-outlookprovider -Identity EXCH -CertprincipalName msstd:webmail.domain.tld
set-outlookprovider -Identity EXPR -CertprincipalName msstd:webmail.domain.tld
Giving the command get-outlookprovider, gives me empty information regarding the certprinipalname. Filled
this and after recreating the profile or deleting the ost-file I still have the second alert with the local certificate of my RDS.
Not completely where I want to be, any help regarding the second alert is greatly appreciated!

Problem with App-V 5 in Xenapp 6.5 Feature Pack 2 /PVS Server 7.1 Environment

Hi I hope someone can help me. We are pretty desperate right now.
At e customer of mine we are Using App-V 5 SP2 RDS Client together with a Xenapp 6.5 Feature Pack 2 /PVS Server 7.1 Environment.
The Golden Image for PVS gets built with SCCM 2007. We “Install” the App-V Packages local with Powershell with e Install Wrapper.
The Wrapper uses for Example the following command to “install” the Package during the Task Sequence.
Add-AppVClientPackage -Path "C:\_SMSTaskSequence\Packages\I010012B\x86-GE\001\Biella-Dominalprint(V)-2.0.appv" -DynamicDeploymentConfiguration "C:\_SMSTaskSequence\Packages\I010012B\x86-GE\001\Biella-Dominalprint(V)-2.0_DeploymentConfig.xml"
| Publish-AppvClientPackage -Global | Mount-AppvClientPackage -Verbose >C:\Windows\Logs\Install\Biella-Dominalprint(V)-2.0_001.LOG
The Package was Sequenced with SP1 Sequencer.
The Package contains e SystemX86 folder
C:\ProgramData\App-V\5D8F5879-923B-4401-BE13-F6E120F6569C\83FF2A00-5D2A-4A3B-82FD-3238D786BEE3\Root\VFS\SystemX86
In This Folder are a few Files. One of them is the tdbg5.ocx
The Package works without a Problem after the Installation of the Server has finished.
But when the Citrix Department does there Magic with PVS and they provision the VHD to another Server the Package is no longer Working. When we start the App we get an Error that it is Missing the tdbg5.ocx
But when I Use ACDC 2.0 to start the App or modify the Shortcut with the command /appvve: 5D8F5879-923B-4401-BE13-F6E120F6569C_83FF2A00-5D2A-4A3B-82FD-3238D786BEE3 it is working. Also when I remove the Package with Powershell from the provisioned Server
and reinstall it again it is working Again.
We have this Problem with two other Apps and both of them have files in the Root\VFS\SystemX86 Folder.
We also have e Virtualized Java Package. We have a Shortcut like this:
C:\ProgramData\App-V\1A971C0F-1C0F-430F-A2E2-2DF8487E6FF0\80A50994-7B30-4FC3-9DA4-1CE8B979B337\Root\VFS\ProgramFilesX86\Java\jre1.6.0.38\bin\javaws.exe
http://whatever.ch/zpv/webstart/zpv-prod.jnlp
If I start that link on the provisioned Sever Java Launches but it’s not downloading the App to the Cache. But also here it works perfect after the installation with SCCM, and it also works when I remove the package on the provisioned Sever and “install”
it again with Powershell. But here the /appvve workaround doesn’t work.
I know that we should ask that in the Citrix forums, the Citrix department of the Customer is opening a Case with Citrix and one with MS Support. But we are I a big hurry because the customer needs to start testing the Apps, because they need to start
the pilot Test very soon. So I hoped that someone in the community can help me out with this.
Thank you for your answers
Pascal

Another alternative, if you dont want to use the Shared Content Store, is to have your PackageInstallationRoot pointing to a non-provisioned disk (non-PVS). In our environment we had the same exact issue. Each of our Citrix servers have
a D drive thats non-provisioned that we use for Logs. Once I pointed the PackageInstallationRoot over to this location everything started working.   The key here is to have a script run at server startup that deletes the PackageInstallationRoot
since the provisioned non-persistent disk will reboot to a fresh image each time.   This way you wont end up with stale content out there as applications are updated and/or removed.
There are other things that also have to happen for this to work in these types of environments (related to roaming profile exclusions) that I can provide to you if you need them.
Let me know if you want/need more details.

Problem with RD gateway manager

Hi,
Have some problems with manager. It used to work, but suddenly I can't connect to local server.
Get this error:
"The RD Gateway Managment snap-in console cannot connect to the server. To connect to this server, you must be a memeber of the local administrators group on the server."
The user account that i'm using is a member of the local administrator group.
Any ideas?
The RDS server is a Win2012 server. The AD server is a win 2008 R2 server.
Thanks
\Kent

Hi Kent,
Thanks for your comment.
For this you need to create RD Rap and RD CAP policies. When you create the RD RAP, add the user groups that you defined in the RD CAP. Also, create a new RD Gateway-managed computer group that contains both the NetBIOS names and the fully qualified domain
names (FQDNs) of the RD Session Host servers or the RD Session Host server farm that hosts the RemoteApp programs.
Please check below article for information.
1. Remote Desktop Gateway Manager
2.How To Work with RD Gateway in Windows Server 2012
Hope it helps!
Thanks.
Dharmesh Solanki

RD Gateway 2012 R2 (DMZ) - Problem with authentification (NULL SID)

Hello,
I have a problem with a RD Gateway 2012 R2, that domain users can't log on over the RD Gateway to the RD Sessionhost. I get an error message in the eventlog on the RD Gateway.
Protokollname: Security
Quelle: Microsoft-Windows-Security-Auditing
Datum: 09.12.2014 16:45:24
Ereignis-ID: 4625
Aufgabenkategorie:Anmelden
Ebene: Informationen
Schlüsselwörter:Überwachung gescheitert
Benutzer: Nicht zutreffend
Computer: DMZ2.bptest.local
Beschreibung:
Fehler beim Anmelden eines Kontos.
Antragsteller:
Sicherheits-ID: NULL SID
Kontoname: -
Kontodomäne: -
Anmelde-ID: 0x0
Anmeldetyp: 3
Konto, für das die Anmeldung fehlgeschlagen ist:
Sicherheits-ID: NULL SID
Kontoname: [email protected]
Kontodomäne:
Fehlerinformationen:
Fehlerursache: Bei der Anmeldung ist ein Fehler aufgetreten.
Status: 0xC000005E
Unterstatus:: 0x0
Prozessinformationen:
Aufrufprozess-ID: 0x0
Aufrufprozessname: -
Netzwerkinformationen:
Arbeitsstationsname: SCHULUNG
Quellnetzwerkadresse: -
Quellport: -
Detaillierte Authentifizierungsinformationen:
Anmeldeprozess: NtLmSsp
Authentifizierungspaket: NTLM
Übertragene Dienste: -
Paketname (nur NTLM): -
Schlüssellänge: 0
Dieses Ereignis wird beim Erstellen einer Anmeldesitzung generiert. Es wird auf dem Computer generiert, auf den zugegriffen wurde.
Die Antragstellerfelder geben das Konto auf dem lokalen System an, von dem die Anmeldung angefordert wurde. Dies ist meistens ein Dienst wie der Serverdienst oder ein lokaler Prozess wie "Winlogon.exe" oder "Services.exe".
Das Anmeldetypfeld gibt den jeweiligen Anmeldetyp an. Die häufigsten Typen sind 2 (interaktiv) und 3 (Netzwerk).
Die Felder für die Prozessinformationen geben den Prozess und das Konto an, für die die Anmeldung angefordert wurde.
Die Netzwerkfelder geben die Quelle einer Remoteanmeldeanforderung an. Der Arbeitsstationsname ist nicht immer verfügbar und kann in manchen Fällen leer bleiben.
Die Felder für die Authentifizierungsinformationen enthalten detaillierte Informationen zu dieser speziellen Anmeldeanforderung.
- Die übertragenen Dienste geben an, welche Zwischendienste an der Anmeldeanforderung beteiligt waren.
- Der Paketname gibt das in den NTLM-Protokollen verwendete Unterprotokoll an.
- Die Schlüssellänge gibt die Länge des generierten Sitzungsschlüssels an. Wenn kein Sitzungsschlüssel angefordert wurde, ist dieser Wert 0.
The domain administrator can log on successfully over the RD Gateway. When i log on a domain user on the RD Gateway server console first and then log on over the RD Gateway, the authentication works fine.
The RD Gateway 2012 R2 has been installed as well as the instructions (http://technet.microsoft.com/en-us/library/cc754191.aspx). I have tried a lots of things, but without a result.
e.g.
register NPS in the AD
all ports in the Firewall between LAN and DMZ are opened
set the "Network security: LAN Manager authentication level" to "Send NTLMv2 response only"
re-install of the RD Gateway 2012 R2
Environment:
All machines have Windows Server 2012 R2 or Windows 8/8.1 with the latest updates. All servers are virtualized with Hyper-V.
Domaincontroller (LAN)
RD Sessionhost (LAN)
RD Gateway (DMZ)
Clients (DMZ/WAN)
Hardware-Firewall (3-zone)
Does anyone have an idea, what might be the problem?
Best regards,
BpDk

Hi,
From your description seems there is user permission issue and that’s the reason you can’t logon to the remote desktop. For this you can I would like to check whether you have done the following steps for troubleshooting.
Need to create RD CAP and RD RAP policies and also add the user under RD CAP properties for proper access. RD CAPs allow you to specify who can connect to an RD Gateway server. You can specify a user group that exists on the local RD Gateway server or in Active
Directory Domain Services. You can also specify other conditions that users must meet to access an RD Gateway server. You can list specific conditions in each RD CAP. For example, you might require a group of users to use a smart card to connect through RD
Gateway.
When there is no AD DS in the perimeter network, ideally the servers in the perimeter network should be in a workgroup, but the RD Gateway server has to be domain-joined because it has to authenticate and authorize corporate domain users and resources.
Please check below article for more troubleshooting and provide access & authenticate user.
RD Gateway deployment in a perimeter network & Firewall rules
http://blogs.msdn.com/b/rds/archive/2009/07/31/rd-gateway-deployment-in-a-perimeter-network-firewall-rules.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Terminal Server Licensing Problems with GPO Security Group License Server

Hello,
I have two fresh installs of W2K12R2.
One is RD Session Host and the other one is the License Server. Everything is fine until I active the GPO Security Group License Server. After that the License Server gives no licenses
to die clients (we have User und Device CALs). TS Licensing Diagnostic’s shows no errors, the number of available licenses is displayed correctly, even the state of GPO Security Group License Server is correctly shown as "active" and die
Membership in the Group "RDS-Endpointserver" is "Yes". Eventlog shows no Errors. Log in on the session host is even possible, maybe because the RDS-Service is in evaluation time.
If the GPO Security Group License Server is disabled again, the server starts to serve licenses as expected.
I don’t know what I can do anymore, never had problems with exact the same setup under W2K8, but with W2K12 is the second time I notice this issue.
Thanks for your ideas,
Andreas

Hi Andreas,
Thank you for posting in Windows Server Forum.
Sorry to inform but there is no official document for server 2012 related to this event, you can go through below article for reference.
You cannot use a security group to add computer accounts to the Terminal Server Computers group. You must add each computer account explicitly. To verify whether an RD Session Host server is allowed to request RDS CALs from the Remote Desktop license server,
you can use the IsSecureAccessAllowed method of Win32_TSLicenseServer class. For more details about this method, click here.
1. License Diagnosis tool returns error "License server <computer name> cannot issue RDS CALs to the Remote Desktop Session Host Server because the 'License server security group' Group
Policy setting is enabled."
2.Control the Issuance of RDS CALs
Note: You should only enable this policy setting when the license server is a member of a domain. You can only add computer accounts for RD Session Host servers to the RDS Endpoint Servers group when the license server is a member of a domain.
Hope it helps!
Thanks,
Dharmesh

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with threads and camera.

Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while((!performing.isShown()) && (backgroundCamera.isShown())){
                    Thread.yield();
                notifyAll();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    this.wait();
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?

Hi,
I've finally managed to work this fine.
The code:
       Object o = new Object();
       display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while(!performing.isShown()){
                    Thread.yield();
               synchronized(o) {
                  o.notify();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    synchronized(o) {
                       o.wait(1);
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();

Problem with threads hanging

We have a problem where our application stops responding after a few days of usage. Things will for fine for a day or two, and then pretty quickly threads will start getting hung up, usually in places where they are allocating memory
We are running WebLogic 8.1 SP2 on Sun JDK 1.4.2_04 on Solaris 8 using the alternate threading model and the -server hotspot vm. We are running pretty much the same code that we had no problems with under WebLogic 6.1 SP4 and Sun JDK 1.3.1.
A thread dump usually shows that some or all of our execute threads are in the state "waiting for monitor entry" even though they are not currently waiting on any java locks. Here is a sample thread from the thread dump (we have ~120 threads so I don't want to post the full dump).
=============================================================================================
"ExecuteThread: '8' for queue: 'itgCrmWarExecutionQueue'" daemon prio=5 tid=0x005941d0 nid=0x2c waiting for monitor entry [c807f000..c807fc28]
at java.lang.String.substring(String.java:1446)
at java.lang.String.substring(String.java:1411)
at weblogic.servlet.internal.ServletRequestImpl.getRelativeUri(ServletRequestImpl.java:1872)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3492)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
=============================================================================================
String.java line 1446 for this jdk allocates a new String object, and all the other threads in this state also are creating new objects or arrays, etc.
We've done a pstack on this process when it's in this state, and the threads that are in the "waiting for monitor entry" that look like they're allocating memory are all waiting on the same lwp_mutex_lock with some allocation method that's calling into the native TwoGenerationCollectorPolicy.mem_allocate_work (see pstack output below for the same thread as in the thread dump above)
=============================================================================================
----------------- lwp# 44 / thread# 44 --------------------
ff31f364 lwp_mutex_lock (e3d70)
fee92384 __1cNObjectMonitorGenter26MpnGThread__v_ (5000, 525c, 5000, 50dc, 4800, 4af0) + 2d8
fee324d4 __1cSObjectSynchronizerKfast_enter6FnGHandle_pnJBasicLock_pnGThread__v_ (c807f65c, c807f7d4, 5941d0, 0, 35d654, fee328ec) + 68
fee32954 __1cQinstanceRefKlassZacquire_pending_list_lock6FpnJBasicLock__v_ (c807f7d4, ff170000, d4680000, 4491d4, fee1bc2c,
0) + 78
fee3167c __1cPVM_GC_OperationNdoit_prologue6M_i_ (c807f7bc, 4400, ff170000, 2d2b8, 4a6268, c807fa18) + 38
fee2e0b0 __1cIVMThreadHexecute6FpnMVM_Operation__v_ (c807f7bc, 963a8, 0, 0, 1, 0) + 90
fed2c2a4 __1cbCTwoGenerationCollectorPolicyRmem_allocate_work6MIii_pnIHeapWord__ (962c0, ff1c29ec, ff1c297c, ff131a26, 4800, 4998) + 160
fed22940 __1cNinstanceKlassRallocate_instance6MpnGThread__pnPinstanceOopDesc__ (ee009020, 5941d0, 15ca581, 3647f0, 4a6268, c807f8c8) + 180
fed34928 __1cLOptoRuntimeFnew_C6FpnMklassOopDesc_pnKJavaThread__v_ (ee009018, 5941d0, 0, 0, 0, 0) + 28
fa435a58 ???????? (ee009018, e86de, 15ca4de, 50dc, 5941d0, c807f9c8)
fb36f9a4 ???????? (0, d412ccd8, ee046c28, ff170000, 0, 0)
fad8b278 ???????? (ee046c28, d6000c90, ee046530, 8, db8e8450, c807f9e8)
fad62abc ???????? (d412ccd8, ee046530, d6000c90, ee3bfa38, 8, c807fa18)
fa4b3c38 ???????? (c807fb9c, 0, f2134700, fa415e50, 8, c807faa8)
fa40010c ???????? (c807fc28, c807fe90, a, ee9e1e20, 4, c807fb40)
fed5d48c __1cJJavaCallsLcall_helper6FpnJJavaValue_pnMmethodHandle_pnRJavaCallArguments_pnGThread__v_ (c807fe88, c807fcf0, c807fda8, 5941d0, 5941d0, c807fd00) + 27c
fee4b784 __1cJJavaCallsMcall_virtual6FpnJJavaValue_nLKlassHandle_nMsymbolHandle_4pnRJavaCallArguments_pnGThread__v_ (ff170000, 594778, c807fd9c, c807fd98, c807fda8, 5941d0) + 164
fee5e8dc __1cJJavaCallsMcall_virtual6FpnJJavaValue_nGHandle_nLKlassHandle_nMsymbolHandle_5pnGThread__v_ (c807fe88, c807fe84, c807fe7c, c807fe74, c807fe6c, 5941d0) + 6c
fee6fc74 __1cMthread_entry6FpnKJavaThread_pnGThread__v_ (5941d0, 5941d0, 838588, 594778, 306d10, fee69254) + 128
fee6927c __1cKJavaThreadDrun6M_v_ (5941d0, 2c, 40, 0, 40, 0) + 284
fee6575c _start   (5941d0, fa1a1600, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Also when it's having this problem, the "VM Thread" is always using a lot of processor time. We did a couple of pstacks today while it was having this problem, and this thread was stuck in the ONMethodSweeper.sweep for over 15 minutes when we finally killed the server.
From the thread dump:
"VM Thread" prio=5 tid=0x000e2d20 nid=0x2 runnable
From the first pstack:
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed40c04 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (42a2f4, fa5fa46d, ffffffff, fc4ffcb8, 42a2f4, 42a324) + 124
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (42a2f0, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (fa5f7f88, fa608940, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Second pstack
=============================================================================================
----------------- lwp# 2 / thread# 2 --------------------
fed41180 __1cXvirtual_call_RelocationIparse_ic6FrpnICodeBlob_rpC5rppnHoopDesc_pi_nNRelocIterator__ (0, ff1b9664, ffffffff, fc4ffcb8, a6f2cc, fc4ffbd0) + 6a0
fed46318 __1cKCompiledIC2t5B6MpnKRelocation__v_ (a6f2c8, fc4ffd24, fc4ffd4c, e802, 0, 6) + 38
fed90c38 __1cHnmethodVcleanup_inline_caches6M_v_ (faded4c8, fadf2c80, 1, 0, fa400000, 6) + 1ac
fede18b4 __1cONMethodSweeperFsweep6F_v_ (2cf38, 0, ffffffff, ff1cf1fc, ff1c66e8, fede1d44) + 1b0
fede1e6c __1cUSafepointSynchronizeFbegin6F_v_ (2cf38, ff1ba138, 5000, 50dc, 5000, 525c) + 248
feef1fd4 __1cIVMThreadEloop6M_v_ (4400, 4000, 4324, 4000, 42b0, 3800) + 3d4
feef1ae4 __1cIVMThreadDrun6M_v_ (e2d20, 2, 40, 0, 40, 0) + 8c
fee6575c _start   (e2d20, ff270200, 0, 0, 0, 0) + 134
ff3758c0 lwpstart (0, 0, 0, 0, 0, 0)
=============================================================================================
Has anyone ever seen anything like this? I'm trying to figure out if this is caused by something we're doing, or something relating to our environment and jvm options. Any ideas?

Thanks for the reply - I'm testing our app with the +UseConcMarkSweepGC now in our test environment to make sure it doesn't cause any problems there. Unfortunately the only place we've had this problem is on the production server, so it's extra difficult debugging this.
We're using the following memory options:
-ms512m -mx512m -XX:NewSize=128m -XX:PermSize=192m -XX:MaxNewSize=128m -XX:MaxPermSize=192m -XX:SurvivorRatio=8and the following debugging options, as we've also been seeing OutOfMemoryErrors ( see http://forum.java.sun.com/thread.jsp?forum=37&thread=522354&tstart=45&trange=15 )
-verbosegc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGCBTW, which c++filt version and options are you using? Our Solaris boxes only seem to have the GNU version installed. I was trying to run that on some of the other stack traces and wasn't getting anywhere, and didn't know if because it was GNU version wouldn't work on something compiled with the Sun compiler.
Thanks!
--Andy

Problem with threads and ProgressMonitor

Dear Friends:
I have a little problem with a thread and a ProgressMonitor. I have a long time process that runs in a thread (the thread is in an separate class). The thread has a ProgressMonitor that works fine and shows the tasks progress.
But I need deactivate the main class(the main class is the user interface) until the thread ends.
I use something like this:
LongTask myTask=new LongTask();
myTask.start();
myTask.join();
Now, the main class waits for the task to end, but the progress monitor don`t works fine: it shows only the dialog but not the progress bar.
What's wrong?

Is the dialog a modal dialog? This can block other UI updates.
In general, you should make sure that it isn't modal, and that your workThread has a fairly low priority so that the UI can do its updating

Problem with threads and/or memory

I'm developing an application where there are 3 threads. One of them sends a request to the other, and if the 2nd can't answer it, it sends it to the 3rd (similar to CPU -> CACHE -> MEMORY). When i run the program with 1000-10.000 requests, no problem occurs. When i run it with 300.000-1.000.000 requests, it sometimes hangs. Is this a problem with the garbage collector, or should it be related to the threads mecanism.
(note: eache thread is in execution using a finite state machine)

i had been running the program inside Netbeans.
Running the jar using the command line outside
Netbeans i have no more problems... Does Netbeans use
it's own JVM?Depends how you set it up, but look under the options. There are settings for the compiler and jvm that it uses.

Problem with rds on exadata

Similar Messages

Maybe you are looking for