FYI: I’'ve released v6 of the SSPI-SASL bridge:
Changelog:
v6:
-
Free the SSPI model during finalize
-
Only Free/Delete security buffers that have been used (NT4 fix)
-
Made a static buffer into a member variable
-
Assert for Privileges to add SASL methods
-
Implement getMechanismName
-
Now built with Java 1.6 (with -source/-target 1.5 for compatibility with Java1.5)
So several memory leaks and threading contention issues have been removed, I haven’'t checked it in my live production Wildfire envionment yet (Java1.5), but it works in my dev testing non-Wildfire/SaslCheck env (Java1.6)
Hi!
SASL-SSPI v6.2
Wildfire 3.1.1
Pandion 2.5
-
- work, but without windows autentification.
- An unexpected error has been detected by HotSpot Virtual Machine:
- EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77fcd79a, pid=3500, tid=2796
-
Java VM: Java HotSpot™ Server VM (1.5.0_08-b03 mixed mode)
-
Problematic frame:
-
C
T H R E A D -
Current thread (0x2a690668): JavaThread “Client SR - 27525703” daemon
Please email me (see my profile for email address) a Dr Watson dump (see the info I posted in this thread on 23-Oct-2006, and 8-Nov-2006 on how to enable the dump switch). Also please try the dll from the src\SaslSspi-C\Debug folder.
Also please try the dll from the src\SaslSspi-C\Debug folder.
with SaslSspi-C working and this morning dont crash
how to enable the dump switch
sorry, cant find this swith
Message was edited by: victorae
Read the first article I linked to, it explains how to add the debug switch to the service.