首页 文章 精选 留言 我的

精选列表

搜索[issues],共3071篇文章
优秀的个人博客,低调大师

Lync Mobile iOS Client Authentication Issues

Troubleshooting Lync client connectivity can be difficult when there are multiple clients which exhibit slightly different behavior and there are some scenarios where not all clients can successfully sign in. If the case is that both Windows Phone 7 and Android client are able to successfully login but iOS clients cannot then the cause could be related to a specific configuration change applied to the Lync servers somewhere along the line. More specifically the behavior seen on the iOS clients is that they will hang during the sign-in process and the cancel button is unresponsive. Basically the iOS clients do not support the basic NTLM Authentication method while Windows Phone and Android clients do. To determine the available authentication options, the Lync mobile application will retrieve the MEX bindings from the Web Ticket Service and the iOS clients expects to seeWebTicketServiceWinNegotiatefrom the available authentication port names . const std::string MEX_ATTRIBUTE_VALUE_WIN_NEGOTIATE("WinNegotiate"); const std::string MEX_ATTRIBUTE_VALUE_WEBTICKET_BEARER_TOKEN("WebTicketBearer"); const std::string MEX_ATTRIBUTE_VALUE_FED_BEARER_TOKEN("FedBearer"); When Lync is misconfigured and the iOS clients can not sign-in then the Web Ticket service response will look like this: <wsdl:service name="WebTicketService"> <wsdl:port name="" binding="tns:WebTicketServiceWinNtlm"> <soap:address location="https://lync.schertz.local/WebTicket/WebTicketService.svc"/> </wsdl:port> But the iOS client would expect to see the following response from the Web Ticket service: <wsdl:service name="WebTicketService"> <wsdl:port name="" binding="tns:WebTicketServiceWinNegotiate"> <soap:address location="https://lync.schertz.local/WebTicket/WebTicketService.svc"/> </wsdl:port> Resolution Verify that theUseWindowsAuthoption is correctly set toNegotiatein the Lync Server’s Web Service configuration. From the Lync Server Management Shell issue theGet-CsWebServiceConfigurationcmdlet to view the current setting. Get-CsWebServiceConfiguration To change the setting use the following cmdlet to revert Lync back to the recommended authentication setting and then verify the new parameter value. Set-CsWebServiceConfiguration –UseWindowsAuth Negotiate Get-CsWebServiceConfiguration Thanks again toDave Howeat Microsoft for sharing details on these Lync mobility topics. 本文转自cantgis 51CTO博客,原文链接:http://blog.51cto.com/cantgis/1161989,如需转载请自行联系原作者

优秀的个人博客,低调大师

Connection pool,sqlnet,listener related issues/questions

Advise required on inbound paramters , prespawn servers and db resident connection Question: The application does not support persistent connection. currently we find time out errors. In order to fix the issue we seek your advise on the following: currently all of the following are default values SQLNET.INBOUND_CONNECT_TIMEOUT, --- can we make it 10 seconds ? or what value you suggest SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT INBOUND_CONNECT_TIMEOUT_listenernam -- planning to make 5 seconds; what are your suggestios. 2. ours is 11.2.0.1 ; whether prspawn server is still there in 11g R2. Will it be helpful for application supporting persistent connection or not 3. Regarding DRCP for those applications not supporting persistent connection , similarly do we have any answer for applications having persistent connections but at the same time avoiding logon storms. Answer: Well it sounds like you need to increase the processes parameters to allow the logon storms. Or setup a connection pool from the apache side to prevent the number of connections from hitting the server to increase. Otherwise from the server side any values you set other then increasing the processes value to handle the load will report errors to the client trying to connect. For example if you set the INBOUND_CONNECT_TIMEOUT then the client has to authenticate in that timeframe or it will error and report the 3136 error. But that defaults to 60 seconds to prevent any good connections from being booted just for being slow. Now if you hit the processes value it will start reporting the 12518 and should trigger a connection error so apache should stop trying to force the connections at that point. If it continues then it will get errors and there is not much you can do. From the Oracle side you cannot really control how the client connects. If they cause a storm you either configure to handle the load or accept the fact the system will generate errors and not service the storm. From the server side most of the parameters we have are to limit or control the amount of connections that are allowed to the server itself. If the client keeps trying to connect in a storm fashion there is not much you can do to prevent it on the DB you simply need to make it possible for those processes to connect. the only real option from the server is to bump up the processes parameter to make sure you can handle the full load and have them setup a connection pool on the apache side to limit the total number of connections to the database from the web server to prevent them from hitting the processes value. 本文转自maclean_007 51CTO博客,原文链接:http://blog.51cto.com/maclean/1277770

资源下载

更多资源
优质分享App

优质分享App

近一个月的开发和优化,本站点的第一个app全新上线。该app采用极致压缩,本体才4.36MB。系统里面做了大量数据访问、缓存优化。方便用户在手机上查看文章。后续会推出HarmonyOS的适配版本。

Mario

Mario

马里奥是站在游戏界顶峰的超人气多面角色。马里奥靠吃蘑菇成长,特征是大鼻子、头戴帽子、身穿背带裤,还留着胡子。与他的双胞胎兄弟路易基一起,长年担任任天堂的招牌角色。

Nacos

Nacos

Nacos /nɑ:kəʊs/ 是 Dynamic Naming and Configuration Service 的首字母简称,一个易于构建 AI Agent 应用的动态服务发现、配置管理和AI智能体管理平台。Nacos 致力于帮助您发现、配置和管理微服务及AI智能体应用。Nacos 提供了一组简单易用的特性集,帮助您快速实现动态服务发现、服务配置、服务元数据、流量管理。Nacos 帮助您更敏捷和容易地构建、交付和管理微服务平台。

Spring

Spring

Spring框架(Spring Framework)是由Rod Johnson于2002年提出的开源Java企业级应用框架,旨在通过使用JavaBean替代传统EJB实现方式降低企业级编程开发的复杂性。该框架基于简单性、可测试性和松耦合性设计理念,提供核心容器、应用上下文、数据访问集成等模块,支持整合Hibernate、Struts等第三方框架,其适用范围不仅限于服务器端开发,绝大多数Java应用均可从中受益。

用户登录
用户注册
修改密码
忘记密码