Anonymous_User Absent Member.
Absent Member.
226 views

Unable to alloc data memory in NLDAPSetResponseBer


Hello,
Using the Novell JLDAP together with the DirXML LDAP Java classes
(dirxml_misc.jar).

When connected to a 64-bit eDirectory 8.8.5 FTF4 on SLES10 my LDAP
extended operation with this class fails most of the time:
'GetDriverStartOptionRequest'
(http://developer.novell.com/documentation/dirxml/dirxmlbk/api/com/novell/nds/dirxml/ldap/GetDriverStartOptionRequest.html)

I get this in the LDAP DSTrace:

Code:
--------------------
10:34:37 40D0B940 LDAP: DoExtended on connection 0x6dd41a00
10:34:37 40D0B940 LDAP: DoExtended: Extension Request OID: 2.16.840.1.113719.1.14.100.7
10:34:37 40D0B940 LDAP: malloc of 9 bytes failed
10:34:37 40D0B940 LDAP: Unable to alloc data memory in NLDAPSetResponseBer
10:34:37 40D0B940 LDAP: Sending operation result 0:"":"" to connection 0x6dd41a00
--------------------
What could be the issue?

Server has 16 GB of RAM. eDirectory has cache set to 4 GB.


--
alekz
------------------------------------------------------------------------
alekz's Profile: http://forums.novell.com/member.php?userid=1936
View this thread: http://forums.novell.com/showthread.php?t=426124

Labels (1)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Unable to alloc data memory in NLDAPSetResponseBer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Enable tracing with +DXML and +DVRS as well, please, and post the output
assuming that the driver did not behave as it should have. Also if you
have the Java-based code you were using or a JAR posted somewhere to test
this out I'll try it on my setup.

Good luck.






On 11/17/2010 03:06 AM, alekz wrote:
>
> Hello,
> Using the Novell JLDAP together with the DirXML LDAP Java classes
> (dirxml_misc.jar).
>
> When connected to a 64-bit eDirectory 8.8.5 FTF4 on SLES10 my LDAP
> extended operation with this class fails most of the time:
> 'GetDriverStartOptionRequest'
> (http://developer.novell.com/documentation/dirxml/dirxmlbk/api/com/novell/nds/dirxml/ldap/GetDriverStartOptionRequest.html)
>
> I get this in the LDAP DSTrace:
>
> Code:
> --------------------
> 10:34:37 40D0B940 LDAP: DoExtended on connection 0x6dd41a00
> 10:34:37 40D0B940 LDAP: DoExtended: Extension Request OID: 2.16.840.1.113719.1.14.100.7
> 10:34:37 40D0B940 LDAP: malloc of 9 bytes failed
> 10:34:37 40D0B940 LDAP: Unable to alloc data memory in NLDAPSetResponseBer
> 10:34:37 40D0B940 LDAP: Sending operation result 0:"":"" to connection 0x6dd41a00
> --------------------
> What could be the issue?
>
> Server has 16 GB of RAM. eDirectory has cache set to 4 GB.
>
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJM48rlAAoJEF+XTK08PnB5wgAQAJI9s2qpxEZtH6Dxc9ztiamP
hn6AV+FQqdLAdnG1YIxDO5j0lCH6EkFpNXXoDXUpwsSavP83ax/3o1pXYxiARJAT
Ak/mzZ5wvlT4fK7C9M3fmvyO1cYHrWsb45cFqiERwTQQVmPEJkk0B6GvgyVUD+MD
8LrjOKWqYqqUfqZ+nw424fIjgLE+ahBTB28JR1geXqkf5Jali22hOlrqPj7lKMwx
79UqlP2youyD8lUnwc4VrWK2jHic0OxfPIpQ/jbK6eSDImVND4vF4TFwyQ60gfAD
tCs7rrNFTTbYq2wxzK5H+p8ifPD3q0PDUcXduJ8NMOTytmt4D/lI94ht2UNfWQ6Y
8Nmz6E8bCnZ8W++H91vDW2HRg5+WNeqI7R7BMIpcxqzshG/+Njz81iVyjeNvY7S5
2h+EasjAuSMGhsab71p9e/vhcm2n2jlaljZxcZrrV+lUZtIr7cwY5OYdjCA9C+y6
pgVsAdu7M1ForSTQkRmNAjVGQRQRGESe9f5DVvZeVGm2yq7Dvj+zCvndLvJfSrCy
Q7VVB9D3RnSZD2JPyF8C4aj31F0e68ynQ463fWCGijQnEpttwwEpaQj6EU5OpzW+
b26LYXf2W1snkTI4tZWSv+Ie6UywafwIAQmHaRhtaaUL6/WnqiWy9CvpiePwYCqP
IPwooGIVF76JIpK31rzO
=cLSa
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to alloc data memory in NLDAPSetResponseBer

OK, will do next week.

On 2010-11-17 13:30, ab@novell.com wrote:
> Enable tracing with +DXML and +DVRS as well, please, and post the output
> assuming that the driver did not behave as it should have. Also if you
> have the Java-based code you were using or a JAR posted somewhere to test
> this out I'll try it on my setup.
>
> Good luck.
>
>
>
>
>
>
> On 11/17/2010 03:06 AM, alekz wrote:
>
>> Hello,
>> Using the Novell JLDAP together with the DirXML LDAP Java classes
>> (dirxml_misc.jar).

>
>> When connected to a 64-bit eDirectory 8.8.5 FTF4 on SLES10 my LDAP
>> extended operation with this class fails most of the time:
>> 'GetDriverStartOptionRequest'
>> (http://developer.novell.com/documentation/dirxml/dirxmlbk/api/com/novell/nds/dirxml/ldap/GetDriverStartOptionRequest.html)

>
>> I get this in the LDAP DSTrace:

>
>> Code:
>> --------------------
>> 10:34:37 40D0B940 LDAP: DoExtended on connection 0x6dd41a00
>> 10:34:37 40D0B940 LDAP: DoExtended: Extension Request OID: 2.16.840.1.113719.1.14.100.7
>> 10:34:37 40D0B940 LDAP: malloc of 9 bytes failed
>> 10:34:37 40D0B940 LDAP: Unable to alloc data memory in NLDAPSetResponseBer
>> 10:34:37 40D0B940 LDAP: Sending operation result 0:"":"" to connection 0x6dd41a00
>> --------------------
>> What could be the issue?

>
>> Server has 16 GB of RAM. eDirectory has cache set to 4 GB.

>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to alloc data memory in NLDAPSetResponseBer

Hi ab!
The +DXML and +DVRS don't report anything strange.

I've posted the app on Cool Solutions, would be great if you could
reproduce it.
You can download it here:
http://www.novell.com/communities/node/12387/console2upc-universal-password-control


Usually it would be enough if clicking Show IDM Drivers, selecting a
driver, and then clicking Get Driver Status.
Sometimes even Show IDM Drivers fails at well.
Usually it fails 9/10 times when I try it.
The server is SLES10SP2 64-bit, 16 GB RAM. eDir 8.8.5 build 20504.13,
tested with 8.8.6 an another server with the same result.

The ndsd process is using 5277m memory according to the VIRT column in top.

Running it against a server running 32-bit eDir works fine, works also
when running it against a DEV server where the ndsd process uses less
then 2gb memory.

On 17/11/2010 13:30, ab@novell.com wrote:
> Enable tracing with +DXML and +DVRS as well, please, and post the output
> assuming that the driver did not behave as it should have. Also if you
> have the Java-based code you were using or a JAR posted somewhere to test
> this out I'll try it on my setup.
>
> Good luck.
>
>
>
>
>
>
> On 11/17/2010 03:06 AM, alekz wrote:
>
>> Hello,
>> Using the Novell JLDAP together with the DirXML LDAP Java classes
>> (dirxml_misc.jar).

>
>> When connected to a 64-bit eDirectory 8.8.5 FTF4 on SLES10 my LDAP
>> extended operation with this class fails most of the time:
>> 'GetDriverStartOptionRequest'
>> (http://developer.novell.com/documentation/dirxml/dirxmlbk/api/com/novell/nds/dirxml/ldap/GetDriverStartOptionRequest.html)

>
>> I get this in the LDAP DSTrace:

>
>> Code:
>> --------------------
>> 10:34:37 40D0B940 LDAP: DoExtended on connection 0x6dd41a00
>> 10:34:37 40D0B940 LDAP: DoExtended: Extension Request OID: 2.16.840.1.113719.1.14.100.7
>> 10:34:37 40D0B940 LDAP: malloc of 9 bytes failed
>> 10:34:37 40D0B940 LDAP: Unable to alloc data memory in NLDAPSetResponseBer
>> 10:34:37 40D0B940 LDAP: Sending operation result 0:"":"" to connection 0x6dd41a00
>> --------------------
>> What could be the issue?

>
>> Server has 16 GB of RAM. eDirectory has cache set to 4 GB.

>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Unable to alloc data memory in NLDAPSetResponseBer

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well what do you know. I verified the mentioned (in the error) extension
is on my object (even verified it's identical to my working 32-bit system)
and ended up reporting Bug# 669418. Feel free to jump on there as desired.

Thanks for the bug report, and neat tool!

Good luck.





On 01/28/2011 06:43 AM, alekz wrote:
> Hi ab!
> The +DXML and +DVRS don't report anything strange.
>
> I've posted the app on Cool Solutions, would be great if you could
> reproduce it.
> You can download it here:
> http://www.novell.com/communities/node/12387/console2upc-universal-password-control
>
>
> Usually it would be enough if clicking Show IDM Drivers, selecting a
> driver, and then clicking Get Driver Status.
> Sometimes even Show IDM Drivers fails at well.
> Usually it fails 9/10 times when I try it.
> The server is SLES10SP2 64-bit, 16 GB RAM. eDir 8.8.5 build 20504.13,
> tested with 8.8.6 an another server with the same result.
>
> The ndsd process is using 5277m memory according to the VIRT column in top.
>
> Running it against a server running 32-bit eDir works fine, works also
> when running it against a DEV server where the ndsd process uses less
> then 2gb memory.
>
> On 17/11/2010 13:30, ab@novell.com wrote:
>> Enable tracing with +DXML and +DVRS as well, please, and post the output
>> assuming that the driver did not behave as it should have. Also if you
>> have the Java-based code you were using or a JAR posted somewhere to test
>> this out I'll try it on my setup.
>>
>> Good luck.
>>
>>
>>
>>
>>
>>
>> On 11/17/2010 03:06 AM, alekz wrote:
>>
>>> Hello,
>>> Using the Novell JLDAP together with the DirXML LDAP Java classes
>>> (dirxml_misc.jar).

>>
>>> When connected to a 64-bit eDirectory 8.8.5 FTF4 on SLES10 my LDAP
>>> extended operation with this class fails most of the time:
>>> 'GetDriverStartOptionRequest'
>>> (http://developer.novell.com/documentation/dirxml/dirxmlbk/api/com/novell/nds/dirxml/ldap/GetDriverStartOptionRequest.html)

>>
>>> I get this in the LDAP DSTrace:

>>
>>> Code:
>>> --------------------
>>> 10:34:37 40D0B940 LDAP: DoExtended on connection 0x6dd41a00
>>> 10:34:37 40D0B940 LDAP: DoExtended: Extension Request OID: 2.16.840.1.113719.1.14.100.7
>>> 10:34:37 40D0B940 LDAP: malloc of 9 bytes failed
>>> 10:34:37 40D0B940 LDAP: Unable to alloc data memory in NLDAPSetResponseBer
>>> 10:34:37 40D0B940 LDAP: Sending operation result 0:"":"" to connection 0x6dd41a00
>>> --------------------
>>> What could be the issue?

>>
>>> Server has 16 GB of RAM. eDirectory has cache set to 4 GB.

>>
>>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNS34WAAoJEF+XTK08PnB5rWUP/0rhhJ4GDh5FQ6AIwUYXBskz
bIQCJdid0HVYi/e53VY6BTQBj2II5J3EA+Xei15aZHgPAtNLkqempQxDwIYJyVqS
YdUbExMJxWzdd5UwgjL8Ir7+YSFUnKiV9ejkOxEdMFHbgbLeuOsI3vkoiaHP24xD
kSk7EldCFsmoxslXC1RMqn29w4celYsuvQ+JVZa9ZkMQOA9jXo2G2WDkN2cEUm7h
tCp+FVOtQzZvxbAbcJWgqgKCGCH9aOa/929d6xyHS7NdlS+NEPsANyi5p9h4t1/b
Ovc3uqFNXVVmHbLkEup/DX7sgcoqgIPOuvNklarckCX+iV4/je7HVasovpxYRNJh
ukkWnkMtYapdG7KVmmF2+Q/MrxXFml/jmH8Oaoc2rrTLRoj3IBRMp/BnJ1Qs90W9
Yb1J/gkr+f7Rw1SDWsiDLUVQ3g0JLrFOzgT43tXzH2zXK9m33yQ+aJ1gmI5TP0Gs
PEY5B1kxJ6GHvOvI+k8CNB/9nvHykSdqfk+HikBgHnmmoWsx//JQKb/vxuvxejsQ
RT+hYEaFUO/ohlpoyf+VPu6I5itN08wpsVbhOji6UGxRKXJxQx9QQgZ52ECiRuvQ
L4ySLZnYtME902HRlov25EHkuN7/TgiJj5byjjDSBqtAc//GjeBFHeJHNVpRRZyc
OLZwegCL/wVA2g6SamXA
=bUxi
-----END PGP SIGNATURE-----
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.