Login Module changes not reflected unless server restarted!

[Former Member]

I am working on a login module and the changes are not reflected unless I restart the server. Is there a way to avoid the restart?

The restart takes anywhere between 40 to 60 mins. HELP!

[Former Member · Accepted solution]

Worked once when SDM restarted, then again doesn't work. Changes in login module are not reflected after deployment.

[Former Member · Accepted solution]

I have tried undeployment/deployment through SDM GUI. Still no luck. My productivity has plunged to new lows.

HELP!!

[Former Member · Accepted solution]

Hi,

The changes are not taking in effect even if you redeploy the LM library because the security service classloader will not refresh the new classes. This is a Java classloading limitation.

Besides that, the best practices advise to develop and test the components and then you can deploy & run onto the production in runtime or after next restart.

Kind regards,

Tsvetomir

[Former Member · Accepted solution]

Well actually, when I first started programming my login module, the changes were reflected the first few times. But after that nada.

[Former Member · Accepted solution]

Well, that's what exactly I am saying: redeploying the library does not take in effect immediately because the classloader does not "know" that a new version was uploaded.

Best Regards, Tsvetomir

[Former Member]

Restarting SDM and deploying again works. SDM usually takes 30 secs to restart. ENJOY!