It's all about the answers!

Ask a question

[closed] Logging into JTS, RTC, RQM using LDAP authentication takes about 10 mins


Enrique Gaona (13462224) | asked Jul 05 '17, 2:19 p.m.
closed Mar 07, 8:52 a.m. by Ralph Schoon (60.5k33643)
Hi,
When I login to JTS or RTC or RQM, it takes over 10 minutes just to login.  The CLM server is using LDAP authenticaiton.  Looking at the jts.log, I'm constantly seeing an LDAPUserRegistry and ServiceUnavailableException error in the jts.log.    Does anyone know what these errors are and how to resolve them?   Thanks.

Output from jts.log:
2017-06-26 11:48:48,031 [http-bio-9443-exec-10760 @@ 11:33 xxxxxx@xx.xxx.com <com.ibm.team.repository.manageUsers/Search@34df35c0-087a-4b85-8243-7f42497b073a> /jts/service/com.ibm.team.repository.service.internal.IExternalUserRegistryRestService/searchRegistry] ERROR ce.jts.internal.userregistry.ldap.LDAPUserRegistry  - [ff00c384.2] CRJAZ0745I Error retrieving users from the external user directory.
2017-06-26 13:45:50,596 [http-bio-9443-exec-10997 @@ 13:30 xxxxx@xx.xxx.com <com.ibm.team.repository.editUser@28246360-497f-44dc-8f5f-af7443753aa1> /jts/service/com.ibm.team.repository.service.internal.IAdminRestService/contributorByUUID] ERROR ce.jts.internal.userregistry.ldap.LDAPUserRegistry  - [9e5744f] CRJAZ0743I Error retrieving group for user.
javax.naming.ServiceUnavailableException: bluepages.ibm.com:389; socket closed; remaining name 'ou=bluepages,o=ibm.com'
        at com.sun.jndi.ldap.Connection.readReply(Connection.java:479)
        at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:652)
        at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:575)
        at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1998)
        at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1860)
        at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1785)
        at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:399)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:369)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:352)
        at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:279)
        at com.ibm.team.repository.jndi.internal.DirContextImpl.search(DirContextImpl.java:242)
        at com.ibm.team.repository.service.jts.internal.userregistry.ldap.LDAPUserRegistry.fetchUserDN(LDAPUserRegistry.java:634)
        at com.ibm.team.repository.service.jts.internal.userregistry.ldap.LDAPUserRegistry.fetchUserDN(LDAPUserRegistry.java:616)
        at com.ibm.team.repository.service.jts.internal.userregistry.ldap.LDAPUserRegistry.fetchGroupsForUser(LDAPUserRegistry.java:700)
        at com.ibm.team.repository.service.jts.internal.userregistry.ldap.LDAPUserRegistry.fetchGroupsForUser(LDAPUserRegistry.java:607)
        at com.ibm.team.repository.service.jts.internal.userregistry.ExternalUserRegistryInternalService.fetchGroupsForUser(ExternalUserRegistryInternalService.java:255)
        at sun.reflect.GeneratedMethodAccessor3523.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at com.sun.proxy.$Proxy580.fetchGroupsForUser(Unknown Source)
        at com.ibm.team.repository.service.jts.internal.userregistry.JtsExternalUserRegistryService.fetchGroupsForUser(JtsExternalUserRegistryService.java:101)
        at sun.reflect.GeneratedMethodAccessor3522.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at com.sun.proxy.$Proxy581.fetchGroupsForUser(Unknown Source)
        at com.ibm.team.repository.service.jts.internal.userregistry.ExternalUserRegistryServiceDelegator.fetchGroupsForUser(ExternalUserRegistryServiceDelegator.java:79)
        at sun.reflect.GeneratedMethodAccessor3521.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at com.sun.proxy.$Proxy600.fetchGroupsForUser(Unknown Source)
        at com.ibm.team.repository.service.internal.AdminRestService.addContributorRoles(AdminRestService.java:671)
        at com.ibm.team.repository.service.internal.AdminRestService.getContributorByUUID(AdminRestService.java:645)
        at sun.reflect.GeneratedMethodAccessor3977.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
        at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
        at com.sun.proxy.$Proxy801.getContributorByUUID(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor3976.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
        at java.lang.reflect.Method.invoke(Method.java:620)
at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doModelledRestService(AbstractTeamServerServlet.java:573)
        at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2524)
        at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2315)
        at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1794)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
        at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
        at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
        at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
        at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:613)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
        at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:358)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:809)
2017-06-26 13:45:50,596 [http-bio-9443-exec-11000 @@ 13:30 rcerkas@us.ibm.com <com.ibm.team.repository.editUser@b4c89a0b-b17e-41a6-89e9-1d0d0ce00284> /jts/service/com.ibm.team.repository.service.internal.IAdminRestService/contributorByUUID] ERROR ce.jts.internal.userregistry.ldap.LDAPUserRegistry  - [9e5744f.2] CRJAZ0743I Error retrieving group for user.
2017-06-26 15:58:00,468 [http-bio-9443-exec-11192 @@ 15:42 rcerkas@us.ibm.com <com.ibm.team.repository.editUser@4be0e120-c2bf-4464-8f50-dadd778dc898> /jts/service/com.ibm.team.repository.service.internal.IAdminRestService/contributorByUUID] ERROR ce.jts.internal.userregistry.ldap.LDAPUserRegistry  - [9e5744f.3] CRJAZ0743I Error retrieving group for user.
2017-06-29 11:47:21,297 [http-bio-9443-exec-13655 @@ 11:31 rcerkas@us.ibm.com <com.ibm.team.repository.editUser@75b15595-c6df-4068-87f4-8dfb5b1d487b> /jts/service/com.ibm.team.repository.service.internal.IAdminRestService/contributorByUUID] ERROR ce.jts.internal.userregistry.ldap.LDAPUserRegistry  - [9e5744f] CRJAZ0743I Error retrieving group for user.
javax.naming.ServiceUnavailableException: bluepages.ibm.com:389; socket closed; remaining name 'ou=bluepages,o=ibm.com'
        at com.sun.jndi.ldap.Connection.readReply(Connection.java:479)
        at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:652)
        at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:575)
        at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1998)
        at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1860)

The question has been closed for the following reason: "Problem is not reproducible or outdated" by rschoon Mar 07, 8:52 a.m.

Accepted answer


permanent link
Adam Rabčan (453) | answered Mar 08, 2:56 a.m.

Sorry for reviving this old thread but I would like to add it here for other users searching for this as this was the only post found with this issue. 

Thank you Enrique for your reply.

Our solution:
We have used jumbo frames in this problematic environment running in docker. We have downsized it back to 1500 MTU and now it works as it should.

Ralph Schoon selected this answer as the correct answer

Comments
1
Ralph Schoon commented Mar 08, 3:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Thanks Adam. I made your answer the official one and accepted it.


Please note that I believe that there could be a whole host of different issues that could cause this. Network infrastructure, configuration, ... There was a case some years back where certain users at a certain site always took minutes to log in. The root cause was that the CA (certificate authority) for the SSL cert was unreachable from that site and the check back needed to time out. I do not believe there is an one size fits all answer here. 

4 other answers



permanent link
Kevin Ramer (4.5k6171190) | answered Jul 05 '17, 2:42 p.m.

I don't see this behavior for my dozens of Jazz applications also authenticating to the same LDAP.   LDAP really ought to be configured to LDAPS ( port 636 ).  One cannot infer your choice of J2EE container from the above (i.e. Tomcat, WAS or WAS Liberty ) so I can't advise further except to verify that you use these settings for lookups

This is a summary of LDAP Realm configured in WebSphere ( Security / Global Security )

Type: Custom
Host: bluepages.ibm.com
Port: 636

SSL Enabled: checked

Base DN: o=ibm.com

Values used for "Advanced LDAP registry" settings under the LDAP configuration

User Filter: (&(preferredIdentity=%v)(objectclass=ePerson))
Group Filter: (&(cn=%v)(|(objectclass=groupOfNames)(objectclass=groupOfUniqueNames)))
User ID Map: :preferredIdentity
Group ID Map:
:cn
Group Member ID Map: ibm-allGroups:member;ibm-allGroups:uniqueMember



Things to try on your server:

nslookup bluepages.ibm.com

host bluepages.ibm.com

ping bluepages.ibm.com

traceroute bluepages.ibm.com

Most should return immediately; if there are delays in the data being returned, you might need to check the DNS server settings on your network stack.

You could also try some ldapsearch commands from the machine hosting your front-end. 



Comments
Enrique Gaona commented Jul 05 '17, 3:05 p.m.

Kevin,

Thanks for the suggestions.   I have other RTC/RQM servers and they don't exhibit the same issue and are all running on Tomcat and configured LDAP the same way.  The above commands, including ldapsearch, returns their data without any delay.

Here's a copy of the LDAP in my  jts/teamserver.properties file.
com.ibm.team.repository.ldap.membersOfGroup=uniquemember
com.ibm.team.repository.ldap.baseUserDN=ou\=bluepages,o\=ibm.com
com.ibm.team.repository.ldap.userAttributesMapping=userId\=preferredidentity,name\=cn,emailAddress\=mail
com.ibm.team.repository.user.registry.type=LDAP
com.ibm.team.repository.ldap.registryLocation=ldap\://bluepages.ibm.com
com.ibm.team.repository.ldap.baseGroupDN=ou\=memberlist,ou\=ibmgroups,o\=ibm.com
com.ibm.team.repository.ldap.findGroupsForUserQuery=uniquemember\={USER-DN}
com.ibm.team.repository.ldap.findUsersByUserIdQuery=preferredidentity\=?1


Donald Nong commented Jul 06 '17, 5:00 a.m.

I think you get confused. When authenticating, it is the application server, Tomcat in your case, to talk to the LDAP server. So the configuration in teamserver.properties is not being used at that time. For Tomcat, you should look into the server.xml file.


Enrique Gaona commented Jul 07 '17, 5:41 p.m.

You're right!   I compared the server.xml from another RTC server that does not have the long authentication issue and they're basically the same and posted the contents of the server.xml below.  That said, I added JAVA_OPTS="$JAVA_OPTS -Dcom.sun.jndi.ldap.read.timeout=5000" to the server.startup script, which sets the timeout operation for LDAP operations.


permanent link
Enrique Gaona (13462224) | answered Jul 07 '17, 5:26 p.m.

The server.xml is basically identical to the server.xml from other RTC servers not having this issue.  Here are the relevant contents of my server.xml:
<!-- Define a non-SSL HTTP/1.1 Connector on port 9080 -->
    <Connector URIEncoding="UTF-8" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="9080" redirectPort="9443" sslEnabledProtocols="${jazz.connector.sslEnabledProtocols}"/>

<!-- Define a SSL HTTP/1.1 Connector on port 9443 -->
 <Connector SSLEnabled="true" URIEncoding="UTF-8" acceptCount="100" algorithm="${jazz.connector.algorithm}" clientAuth="false" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" keystoreFile="ibm-team-ssl.keystore" keystorePass="ibm-team" maxHttpHeaderSize="8192" maxThreads="500" minSpareThreads="25" port="9443" scheme="https" secure="true" sslEnabledProtocols="${jazz.connector.sslEnabledProtocols}"/>

<!-- Define an AJP 1.3 Connector on port 9009 -->
    <Connector enableLookups="false" port="9009" protocol="AJP/1.3" redirectPort="9443" sslEnabledProtocols="${jazz.connector.sslEnabledProtocols}"/>

<Realm adCompat="true" className="org.apache.catalina.realm.JNDIRealm" connectionURL="ldap://bluepages.ibm.com:389" debug="9" digest="SHA-1" digestEncoding="UTF-8" roleBase="ou=memberlist,ou=ibmgroups,o=ibm.com" roleName="cn" roleSearch="(uniquemember={0})" roleSubtree="false" userBase="ou=bluepages,o=ibm.com" userSearch="(mail={0})" userSubtree="true"/>


Here's the output from Catalina.out.   I restarted the Tomcat server at 11:36am and by 1:48pm the ServiceUnavailableException shows up.
Jul 07, 2017 11:36:02 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 49427 ms
Jul 07, 2017 1:48:17 PM org.apache.catalina.realm.JNDIRealm authenticate
INFO: Exception performing authentication. Retrying...
javax.naming.ServiceUnavailableException: bluepages.ibm.com:389; socket closed; remaining name 'ou=bluepages,o=ibm.com'
        at com.sun.jndi.ldap.Connection.readReply(Connection.java:479)
        at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:651)
        at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:574)
        at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1999)
        at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1861)
        at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1786)
        at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:399)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:369)
        at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:352)
        at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:279)
        at org.apache.catalina.realm.JNDIRealm.getUserBySearch(JNDIRealm.java:1490)
        at org.apache.catalina.realm.JNDIRealm.getUser(JNDIRealm.java:1326)
        at org.apache.catalina.realm.JNDIRealm.getUser(JNDIRealm.java:1274)
        at org.apache.catalina.realm.JNDIRealm.authenticate(JNDIRealm.java:1215)
        at org.apache.catalina.realm.JNDIRealm.authenticate(JNDIRealm.java:1073)
        at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:294)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:452)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
        at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:312)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)
        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1074)
        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)
        at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:314)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:809)


permanent link
Kevin Ramer (4.5k6171190) | answered Jul 10 '17, 12:56 p.m.

Looking back to a now ancient (circa 2011) Tomcat Jazz configuration, this is the Realm snippet in use then:

         <Realm className="org.apache.catalina.realm.JNDIRealm"
           debug="9"
           protocol="ssl"
           connectionURL="ldaps://bluepages.ibm.com:636"
           userBase="ou=bluepages,o=ibm.com"
           userSearch="(emailaddress={0})"
           userSubtree="true"
           roleBase="ou=memberlist,ou=ibmgroups,o=ibm.com"
           roleSubtree="false"
           roleSearch="(uniquemember={0})"
           roleName="cn"
          />

There are security requirements that state LDAPS must be used in authentication step.  


Comments
Enrique Gaona commented Jul 12 '17, 4:57 p.m.

 Thanks, I'll try it with the 636 port.


permanent link
Adam Rabčan (453) | answered Mar 07, 7:59 a.m.

 Hello,

Have you been able to solve this issue please?
We are facing the same issues at our customers.
We have multiples environments, some with JAS some not.
One environment has the same configuration as others yet it takes like 1-2 minutes until the user get authenticated and logged in.


Comments
David Honey commented Mar 07, 8:05 a.m.
JAZZ DEVELOPER

Please submit a new question rather than try to answer/comment on a 4+ year old question. See the forum etiquette.


Ralph Schoon commented Mar 07, 9:33 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Thanks David. I have closed this old question. 


Adam, please open a new question with your log data. With the data given, no one will be able to  answer anything.

You can also consider to open a case with support. Support can get the logs they need and the data is as safe as possible.


2
Enrique Gaona commented Mar 07, 9:51 a.m.

I know this thread has been closed but I thought I'd respond to Adam's question.


Adam,
The workaround I came up with, I added a cron job that would login (RTC commandline) to RTC every 5 minutes.  Once I had this in place, the issue went away.



Ralph Schoon commented Mar 07, 10:17 a.m. | edited Mar 07, 10:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

The answer is fine, Enrique, thank you for that. In general there is a pattern that some users really go to town on searching related questions in the forum. Which I like in general, that should hopefully find hints you can follow. 


Unfortunately some of the users follow up with answers on very old questions asking for updates and this is where this usually breaks. You usually do not get an answer and it is unlikely that the question is even related.

Plus it is actually also a pattern that spammers spam on old questions, so I always review changed items that have a lot of hits.

I think you have a work around, but that is not satisfactory, especially for major customers. That is why I would not accept any of the answers 8)

Something is configured incorrectly or there is a network or certificate error. This needs to be fixed. Hence support.