java.lang.NullPointerException at DocbaseSpecification.<init>

Hello!

We have written a custom code.

We are getting the below error

java.lang.NullPointerExceptionat com.documentum.fc.client.impl.docbase.DocbaseSpecification.<init>(DocbaseSpecification.java:23)at com.documentum.fc.client.DfSessionManager.getDocbaseSpec(DfSessionManager.java:243)at com.documentum.fc.client.DfSessionManager.getIdentityContext(DfSessionManager.java:231)at com.documentum.fc.client.DfSessionManager.getIdentity(DfSessionManager.java:218)at com.documentum.fc.client.DfSessionManager.hasIdentity(DfSessionManager.java:259)at com.documentum.fc.client.DfSessionManager.createSessionHelper(DfSessionManager.java:625)at com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.java:559)at com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.java:362)at com.documentum.web.formext.component.Component.getDfSession(Component.java:2224)at com.documentum.web.formext.component.Component.getDfSession(Component.java:2189)

I see many same error in application log.

Each error ending with

java.lang.NullPointerException

at com.documentum.fc.client.impl.docbase.DocbaseSpecification.<init>(DocbaseSpecification.java:23)

at com.documentum.fc.client.DfSessionManager.getDocbaseSpec(DfSessionManager.java:243)

at com.documentum.fc.client.DfSessionManager.getIdentityContext(DfSessionManager.java:231)

at com.documentum.fc.client.DfSessionManager.getIdentity(DfSessionManager.java:218)

at com.documentum.fc.client.DfSessionManager.hasIdentity(DfSessionManager.java:259)

at com.documentum.fc.client.DfSessionManager.createSessionHelper(DfSessionManager.java:625)

at com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.java:559)

at com.documentum.fc.client.DfSessionManager.getSession(DfSessionManager.java:362)

at com.documentum.web.formext.component.Component.getDfSession(Component.java:2224)

at com.documentum.web.formext.component.Component.getDfSession(Component.java:2189)

but begining from different component.

Please help me to resolve this.

Thanks. (And sorry for my English.)

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

DCTM_Guru

Its kind of hard to help you without seeing your code My guess is that is probably related to how you are trying to establish repository session.

All comments

DCTM_Guru

Its kind of hard to help you without seeing your code My guess is that is probably related to how you are trying to establish repository session.

IreneKa

For example

IDfSession session = null

IDfSessionManager sessionManager = null;

try {sessionManager = SessionManagerHttpBinding.getSessionManager();

session = sessionManager.getSession(SessionManagerHttpBinding.getCurrentDocbase()); !!!!! error

Thanks for your help

DCTM_Guru

Is this part of WDK/Webtop framework or a custom app all together? What happens if you hard-code the docbase name?

IreneKa

This is a part of a custom app all.

Another example is

if"<td align='left' nowrap " + strControlWidth + ">");renderInternalChildControl((TagSupport) firstValueCtrl); !!!!! errorout.println("</td>");}I have no chance to check working with "hard-code the docbase name" on PROD (where working a lot of users).On DEV this error not repeat.thanks:) (valueCtrl.isVisible()) {out.println(

IreneKa

I find that

SessionManagerHttpBinding.getCurrentDocbase() return null:(

IreneKa

And in CS log I see

Current Session ID: 0100000181c2860bLast SQL statement executed by DB was:SELECT KB_.R_OBJECT_ID FROM usi.DM_ACL_S KB_ WHERE (KB_.R_OBJECT_ID=:objectp AND KB_.I_VSTAMP=:versionp); :objectp = 450000018d1a3e8e; :versionp = 018415: ./documentum -init_file /opt/documentum/dba/config/usi/server1.ini -dofee4c91c waitid (0, 4dc3, ffbfc868, 3)fee3c2a4 waitpid (4dc3, 0, 0, 0, feeb5800, ff0c2a00) + 600059cdec __1cSdmExceptionManagerJWalkStack6MpnLdmException_ipnHsiginfo_pv_v_ (148c8b8, ffbfcb08, a, 11b57d7, ffbfca28, 143e228) + 1100059c8dc dmExceptionHandlerProc (a, ffbfd040, ffbfcd88, 1, 11b5400, ffbfcb08) + 354fee48a18 __sighndlr (a, ffbfd040, ffbfcd88, 59c588, 0, 1) + cfee3d0f8 call_user_handler (a, ffbfbefd, 8, 0, ff0c2a00, ffbfcd88) + 3b8fee3d2cc sigacthandler (a, ffbfd040, ffbfcd88, 3965a80, ff0c2a00, 0) + 4c--- called from signal handler with signal 10 (SIGBUS) ---004b5a90 __1cbAdmDistContentMapCollection2T6M_v_ (3a494f0, ffbfcfec, 0, 1377220, ffbfcfec, 3a5ecd8) + 12c004b5dbc __SLIP.DELETER__K (3a494f0, 1, 5d8bfc, 1, 29395c, 137ed6c) + 4004b3160 __1cTdmGetDistContentMap6FpcnEdmID_pnIdmObject_pnJdmSession__pnMdmCollection__ (824cd95f, ffbfd250, 3df8ae0, 13af134, 3a494f0, 1) + 8800232924 __1cJdmSessionFApply6MlnEdmID_pnIdmObject_lnGdmBool__pnMdmCollection__ (3905cd8, 2b7, ffbfd2e8, 3df8ae0, 137cca8, 4b30d8) + 384001b10e8 __1cHDoApply6FpnQdmSessionContext_lnEdmID_pcnGdmBool__pnMdmCollection__ (16f9700, 2b7, 3e0ab78, 13cd660, 0, 16f9700) + 3fc001b1208 __1cNApplyInternal6FnEdmID_l0pcpl_nQapply_result_ext__ (ffbfd6dc, 2b7, ffbfd6d0, 390c480, ffbfdad8, 1000000) + 7c001d68b4 Apply_string (1, ffbfd724, ffbfd734, ffbfd724, 2, ffbfd724) + 1c0001cb76c iIXApply_string (ffbfdb1c, 2b7, 38f6413, ffbfdaec, ffbfdb04, ffbfdad8) + 340075a08c _nwvss_ (14, ffbfe058, 759e98, ffbfdfa0, 36, 0) + 1b8001cb860 S_Apply_string (ffbfdae4, ffbfdae8, ffbfded8, 1cb400, ffbfdab0, ffbfdb1c) + dc001c4774 driver_Proc (ffbfe070, ffbfe058, ffbfe060, 1c3824, 5, ffbfdfa0) + e08001bff14 __1cTdmNetwiseConnectionIDispatch6MrnGdmBool__1_ (3646bf4, ffbfe574, ffbfe084, 1440f08, 0, 0) + cc001d9860 __1cUdmSessionThreadStart6FpnSdmExecutionContext_pv_I_ (5797f8, 3646bf4, 19016400, 1, 137851c, 3646bf4) + 5ac005793f0 __1cGdmForkGLaunch6M_nGdmBool__ (ffbfe6d8, 3646b90, 3646b90, 1, 3896b18, 3646b90) + 400001da1c0 __1cbCdmServerExecutionContextPoolPProcessRequests6M_nGdmBool__ (17c13d0, 137800c, 1d9000, 137800c, ffbfe888, ffbfe88c) + 228001da9c4 __1cIrpc_main6FpkcrnVdmServiceFailoverList_pnJdmSession__nGdmBool__ (0, ffbff130, 1f168a0, 172bdc8, 1148c46, 17c13d0) + 1e4001b6ef8 __1cJdmRPCInit6Fpkc1kl1rnVdmServiceFailoverList_rnIdmObject__nGdmBool__ (1, 19abb08, 1377000, 1, ffbfea24, ffbfea34) + b3c001b8908 __1cSdmRPCMainProtected6FippkcnGdmBool_3_i_ (14f31a4, 53b94, 0, 1527908, 2a, 149f708) + 12f0001b8fb0 __1cJdmRPCMain6FippkcnGdmBool_3_i_ (1, ffbff3c0, 1377000, 1377220, 0, ffbff3c0) + 150001b94c4 main (7, ffbff5d4, 0, 1, 1448c90, 1444580) + 1c0001afb40 _start (0, 0, 0, 0, 0, 0) + 108PID(18415) failure during processing of request: Apply_string. SIGBUS: bus error: (10) at (Apply_string)

DCTM_Guru

"...I have no chance to check working with "hard-code the docbase name" on PROD (where working a lot of users)."

- Well, if your users are not getting a docbase session, I doubt they can work with the docbase in PROD Have you tried instantiating the SessionManager using normal DfClientX class instead of httpbinding? Look at the DFC Development Guide for more details.