Hello Together

I have a strange issue. And its very simple to reproduce.

I have a XPage and on this XPages is a computed Field. I acces for the value a bean called testBean.getState(). In this bean I access the ExtLibUtil.getCurrenSessionAsSigner(). Then I  test if this session is null and make some returns:

Cocde Sample of the testBean:

    public String getState() {
        StringBuffer sbCurrent = new StringBuffer("State");
        try {
            Session sesSigner = ExtLibUtil.getCurrentSessionAsSigner();
            fillSessionData("Signer Session             - ", sesSigner, sbCurrent);
        } catch (Exception e) {
            e.printStackTrace();
        }
        return sbCurrent.toString();
    }

    public void fillSessionData(String strType, Session sesCurrent, StringBuffer sb) {
        try {
            if (sesCurrent != null) {
                sb.append(strType + " EffektiveUser : " + sesCurrent.getEffectiveUserName() + "
");
                sb.append(strType + " Notes Version : " + sesCurrent.getNotesVersion() + "
");
                sb.append(strType + " Plattform     : " + sesCurrent.getPlatform() + "
");
            } else {
                sb.append(strType + " is null!\n");
            }
            sb.append("
");
        } catch (Exception e) {
            e.printStackTrace();
        }
    }

The strange thing is. Whenn I stop the http server, start the server and access directly the application with that page. The first access send a "Signer - Session is null" back. Secound Access, everything is fine.

This case is only a case to reproduce the behaivor, but in the realworld (like the myWebGate Application API) is this a big problem, because we do many call with signer rights :)

Any Ideas how to handle this?