Issue with webtop login

Hello,

I am using webtop 6.5 sp3 which is customized .On login with generic accounts like install owner and system owner it is smooth .But when trying to login with ldap accounts its giving an error :-

invokeMethod() failed while calling: onLogin

null

java.lang.StackOverflowError in the webtop as a pop up.

Also in the docbase logs i can find :-

09:29:18,968 ERROR [http-8001-112] com.documentum.web.common.Trace - invokeMethod() failed while calling: onLogin
null
java.lang.StackOverflowError
        at java.lang.Thread.checkAccess(Thread.java:1216)
        at java.lang.Thread.setPriority(Thread.java:964)
        at java.lang.Thread.init(Thread.java:334)
        at java.lang.Thread.<init>(Thread.java:356)
        at java.util.TimerThread.<init>(Timer.java:456)
        at java.util.Timer.<init>(Timer.java:71)
        at java.util.Timer.<init>(Timer.java:106)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:171)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory$1.run(NetwiseDocbrokerRpcClientFactory.java:167)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:164)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.connect(NetwiseDocbrokerRpcClientFactory.java:124)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.openSocket(NetwiseDocbrokerRpcClientFactory.java:72)
        at com.documentum.fc.client.impl.connection.docbroker.netwise.NetwiseDocbrokerRpcClientFactory.newDocbrokerRpcClient(NetwiseDocbrokerRpcClientFactory.java:36)
        at com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnection.<init>(DocbrokerConnection.java:25)
        at com.documentum.fc.client.impl.connection.docbroker.DocbrokerConnectionFactory.newDocbrokerConnection(DocbrokerConnectionFactory.java:27)
        at com.documentum.fc.client.impl.docbroker.MapBuilder.issueRequest(MapBuilder.java:27)
        at com.documentum.fc.client.impl.docbroker.ServerMapBuilder.getDataFromDocbroker(ServerMapBuilder.java:76)
        at com.documentum.fc.client.impl.docbroker.ServerMapBuilder.getMap(ServerMapBuilder.java:35)
        at com.documentum.fc.client.impl.docbroker.DocbrokerClient.getServerMap(DocbrokerClient.java:152)
        at com.documentum.fc.client.impl.connection.docbase.ServerChoiceManager.updateServerChoices(ServerChoiceManager.java:158)
        at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.updateServerChoices(DocbaseConnection.java:269)
        at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.open(DocbaseConnection.java:156)
        at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.reopen(DocbaseConnection.java:515)
        at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1027)

Please suggest what to do .

Have already put the memory parameters in tomcat :-

export JAVA_OPTS="-Dfile.encoding=UTF-8 -Xms128m -Xmx1024m -XX:PermSize=64m -XX:MaxPermSize=256m"

Not sure if it related to web or the docbase ? Any suggestions

Thanks

Find more posts tagged with

Comments

DCTM_Guru

If you want to rule out customization, try logging into Documentum Administrator. This will tell you whether your LDAP config is set up correctly.

Abraham001

It's the same issue with DA.The generic accounts are working fine . If the error was ldap related then there should be some ldap related messages in the logs . Instead it gives this error after 5 mins.

Abraham001

Thanks Johnny,I am thinking which logs shall i look at .This error seems to be very strange.

DCTM_Guru

I see you are running webtop 6.5. Is your Content Server still 6.5? If so, what LDAP product/version are you using? There might be a compatibility problem.

Abraham001

Thanks Johnny ,Our C.S version is also 6.5 .We are facing this issue after migrating/cloning our CS to a new host .

The only difference is previous content server was in HA mode and we have this new lone C.S not in HA mode.

DCTM_Guru

After you cloned the repository, you probably need to clean out the references to the other/secondary server. Webtop might be trying to contact the secondary CS. This may not be the root cause, but you should eliminate the possibility.

Abraham001

Hi Johnny,

I have already changed the references,so i can login easily with generic accounts .Also the dfc.properties points to the new host .

In the docbase logs i find these :-

#3 0x085289fb in dmExceptionHandlerProc ()

#4 <signal handler called>

#5 0xf76dd672 in CERT_CopyName () from /apps/application/product/6.5/bin/libnss3.so

#6 0xf76da4df in CERT_CopyGeneralName () from /apps/application/product/6.5/bin/libnss3.so

#7 0xf76da63b in CERT_CopyNameConstraint () from /apps/application/product/6.5/bin/libnss3.so

...

#33 0x0849ea4b in dmLDAPConfigInfo::BindToLDAPServerInternal(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()

#34 0x084a5d66 in dmLDAPConfigInfo::BindToLDAPServer(dmSession*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, dmBool) ()

#35 0x084a789b in dmLDAPAuthMgr::AuthenticateByBindType(dmSession*, dmLDAPConfigInfo*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()

#36 0x084a8a5a in dmLDAPAuthMgr::LDAPAuthenticate(dmSession*, dmID, dmUserCacheEntry const*, std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) ()

#37 0x084a9417 in authenticateAgainstDirectoryServer(dmSession*, dmID, dmUserCacheEntry const*, char const*) ()

#38 0x084ccc17 in dmAuthenticateUserInternal(dmSession&, dmUserCredentials&, char const*, long&, char*, unsigned int) ()

#39 0x084cd7d1 in dmAuthenticateUserByPassword(dmUserCredentials&, dmSession&) ()

#40 0x084d0b97 in dmAuthenticateUser(dmSession&, dmUserCredentials&, dmBool, dmBool, dmBool) ()

#41 0x084d14dc in dmAuthenticateUser(char*, dmID, dmObject*, dmSession*) ()

#42 0x08104acc in dmSession::Apply(long, dmID, dmObject*, long, dmBool) ()

#43 0x08068142 in DoApply(dmSessionContext*, long, dmID, char*, dmBool) ()

#44 0x0806e77e in ApplyForObjectInternal(dmID, long, dmID, char*, dmBool*, dmBool*, dmID*, char**, long*, long&) ()

#45 0x08089fc4 in ApplyForObject_string(char*, long, char*, char*, int*, int*, long*) ()

#46 0x08085a03 in iIXApplyForObject_string(void*) ()

#47 0x0869d590 in _nwvss_(unsigned int, dscp_t*, int, rpc_t*, int, int (*)(...), int (*)(...), int (*)(...), void*, _rpcctl*) ()

#48 0x08085afd in S_ApplyForObject_string(int, rpc_t*, _Svrpc, dscp_t*) ()

#49 0x0807e701 in driver_Proc(int, dscp_t*) ()

#50 0x080782e7 in dmNetwiseConnection::Dispatch(dmBool&) ()

#51 0x08090b1a in dmSessionThreadStart(dmExecutionContext*, void*) ()

#52 0x0850d64c in dmFork::Launch() ()

#53 0x08091778 in dmServerExecutionContextPool::ProcessRequests() ()

#54 0x08091f12 in rpc_main(char const*, dmServiceFailoverList&, dmSession*) ()

#55 0x0806d312 in dmRPCInit(char const*, char const*, long, char const*, dmServiceFailoverList&, dmObject&) ()

#56 0x08070e54 in dmRPCMain(int, char const**, dmBool, dmBool) ()

#57 0x080714ad in main ()

PID(931) failure during processing of request: ApplyForObject_string. SIGSEGV: segmentation violation: (11) at (ApplyForObject_string)

Current Session ID: 0100a657803bbd00

Last SQL statement executed by DB was:

select r_object_type, i_vstamp, i_antecedent_id, i_branch_cnt, i_direct_dsc, r_immutable_flag, r_has_events, i_cabinet_id, r_link_cnt, r_frzn_assembly_cnt, r_access_date, i_latest_flag from dm_sysobject_s where r_object_id = :ID; :ID = 0800a65780001100

#0 0xf774b430 in __kernel_vsyscall ()

#1 0xf75b04ab in waitpid () from /lib/libpthread.so.0

#2 0x08528723 in dmExceptionManager::WalkStack(dmException*, int, siginfo*, void*) ()

#3 0x085289fb in dmExceptionHandlerProc ()

#4 <signal handler called>

This message is constantly repeated in the logs.

Thanks

DCTM_Guru

These are low level OS calls that I am not familiar with.

Abraham001

Hello , I enabled the trace today and found the below :-

PID(17820) failure during processing of request: ApplyForObject_string. SIGSEGV: segmentation violation: (11) at (ApplyForObject_string)

Tue Sep 6 12:28:12 2016 011818: 17836[17836] AT 17836: Failed to verify client host and signature: Client rights object not found in docbase for client id (dfc_DCccxjQmffMjhICbqe9XoQNvZxMa)

Tue Sep 6 12:28:12 2016 011892: 17836[17836] AT 17836: Failed to authenticate client instance: client_id=(dfc_DCccxjQmffMjhICbqe9XoQNvZxMa): error=(Client rights object not found)

Tue Sep 6 12:28:12 2016 011950: 17836[17836] AT 17836: Start-AuthenticateUser: ClientHost(hostname.com), LogonName(testuser), LogonOSName(installaccount), LogonOSDomain(), UserExtraDomain(), ServerDomain()

Tue Sep 6 12:28:12 2016 011960: 17836[17836] AT 17836: Start-AuthenticateUserName:

Tue Sep 6 12:28:12 2016 011970: 17836[17836] AT 17836: dmResolveNamesForCredentials: auth_protocol()

Tue Sep 6 12:28:12 2016 011992: 17836[17836] AT 17836: End-AuthenticateUserName: dm_user.user_login_domain(ldap)

Tue Sep 6 12:28:12 2016 011998: 17836[17836] AT 17836: success

Tue Sep 6 12:28:12 2016 012005: 17836[17836] AT 17836: Found dm_user.user_login_name(testuser), dm_user.user_login_domain(ldap)

Tue Sep 6 12:28:12 2016 012017: 17836[17836] AT 17836: Start-AuthenticateDomain:LogonName(testuser), UserExtraDomain(), auth_protocol()

Tue Sep 6 12:28:12 2016 012027: 17836[17836] AT 17836: AuthenticateDomain - no domain required:domainOverride(False), user_login_domain(ldap), serverAuthTarget(), userAuthTarget()

Tue Sep 6 12:28:12 2016 012036: 17836[17836] AT 17836: End-AuthenticateDomain:

Tue Sep 6 12:28:12 2016 012041: 17836[17836] AT 17836: success

Tue Sep 6 12:28:12 2016 012049: 17836[17836] AT 17836: Start-AuthenticateUserState:UserLoginName(testuser), UserExtraDomain()

Tue Sep 6 12:28:12 2016 012055: 17836[17836] AT 17836: Start-AuthenticateUserState:

Tue Sep 6 12:28:12 2016 012061: 17836[17836] AT 17836: dmStateForUser: auth_protocol()

Tue Sep 6 12:28:12 2016 012069: 17836[17836] AT 17836: End-AuthenticateUserState:

Tue Sep 6 12:28:12 2016 012074: 17836[17836] AT 17836: success

Tue Sep 6 12:28:12 2016 012085: 17836[17836] AT 17836: Start-AuthenticateByTrust:OSLogonName(prdwc652), UserLoginName(testuser), OSLogonDomain(), UserExtraDomain()

Tue Sep 6 12:28:12 2016 012513: 17836[17836] AT 17836: Trusted authentication failed because OS logon user name mis-match

Tue Sep 6 12:28:12 2016 012530: 17836[17836] AT 17836: End-AuthenticateByTrust:

Tue Sep 6 12:28:12 2016 012535: 17836[17836] AT 17836: failure

Tue Sep 6 12:28:12 2016 012545: 17836[17836] AT 17836: Start-AuthenticateByPassword:UserLoginName(testuser), UserExtraDomain()

Tue Sep 6 12:28:12 2016 012577: 17836[17836] AT 17836: dmResolveDefaultDomainForLogin: domain(ldap), userAuthTarget(), serverProcessDomain()

Tue Sep 6 12:28:12 2016 020344: 17836[17836] AT 17836: BindToLDAPServer(): ldap_config_id=0800a65780001000: ldap_config_name=ldap: ldap_host=test.com: port_number=3268: ssl_mode=1: ssl_port=3269: certdb_file_path=/opt/installaccount/dba/secure/ldapdb: failover_use_interval=300: ldap_handle=171680176: bind_type=bind_search_dn:

Thanks