Hellu,
Please some help on the following transaction scenario ?:
I am receing some information through a HTTP post method. The servlet,
running as part of a J2EE application, calls a EJB method A. The EJB method
does some little processing. After this, it checks some conditions, and
might do
Hellu,
Elephantwalker,
I was looking at the security role/group mapping but don't understand quite
well how and where to define it.
I have a user/group defined in the principles.xml, but don't know how and
where to I define a role and map this on the goup ?
I was going through the xml files,
Hello everyone!
I think I have found bug in orion 1.5.2.
There is problem with sessions. When I invalidate session and then get new
session, sometimes (not always) I get same invalidated session.
Does anybody have same problem? Any solution except that I remove all data
from session?
Thanks in
Hello,
I have the following problem. I created a Java Client application that
accesses an EJB. I start the client with the following batch file.
set
CLASSPATH=H:\oc4j\j2ee\home\ejb.jar;.;H:\oc4j\j2ee\home\orion.jar;H:\oc4j\j2
ee\home\jndi.jar
java HelloClient
where H:\oc4j\j2ee\home ist the
Just wondering if anyone has fixed SSL load balancing in Orion yet.
Thanks
Steve Best
Unix Systems Administrator
www.simpledevices.com
AFAIK, still broken.
regards,
the elephantwalker
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Steve Best
Sent: Tuesday, September 18, 2001 9:14 AM
To: Orion-Interest
Subject: Is this fixed yet?
Just wondering if anyone has fixed SSL load
Eddie wrote:
Hellu,
Please some help on the following transaction scenario ?:
I am receing some information through a HTTP post method. The servlet,
running as part of a J2EE application, calls a EJB method A. The EJB method
does some little processing. After this, it checks some
Hello Denis,
Try doing this:
session = request.getSession(true);
System.out.println(session = request.getSession(false);\t +
session.hashCode());
System.out.println(session = + session);
session.invalidate();
System.out.println(session.invalidate();\t + session.hashCode());
Rafael,
This won't work reliably on a post request, because the session management
also depends on cookies. In order to make sure you get a new session, you
will need to put in something like this (only for post request):
session.invalidate()
session = request.getSession(true);
I've run into a similar problem, which expressed itself in certain browsers.
In some browsers the url http://somehost and http://somehost:80 are treated
as different URLs. This means that the browser will not send a session
cookie created at http://somehost to http://somehost:80, and the
I was also having same problem but it is not always only sometime.
If any one find solution please let me know
Thanks
Ritesh
-Original Message-
From: Denis Kranjcec [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 18, 2001 9:45 AM
To: Orion-Interest
Subject: session bug
Hello
Peter,
The problem you are experiencing is because the JNDI locations need to be
changed when the location of the client jar is changed -- namely change
'java:comp/env/' to 'java:hello/client/' or some other path that is
appropriate. 'java:comp/env' is reserved for the application server's
i have the same issue
- Original Message -
From: "Denis Kranjcec" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 1:44 PM
Subject: session bug
Hello everyone!
I think I have found bug in orion 1.5.2.
There is problem with sessions. When I
This problem seems to be similar to what I have been running into when
trying to start an Application Client from WebStart - which also involves
copying the jars to the webstart cache.
It's got something to do with Orions jndi implementation, I suspect - we got
the same thing running in another
If I read your output correctly, your session object is still there in
Tomcat after the invalidate; only when you do a new getSession() a new
session ID is obtained. I have not read the spec on what the behaviour
should be, but the required behaviour may only say that at the *next
incoming
I have reported an instance of this bug on Orion's bugzilla Bug #566 which
still remains marked as 'New' well after 1 month, so I still have no
feedback as to whether this is a bug or not.
My login_form.jsp file has the purpose of invalidating the current session
(to effectively logout any
We had exactly the same problem. If you click on a link to a servlet (thats
a get method), and the servlet cleans up the session (session.invalidate(),
session = request.getSession(true),) and then forwards to a logout.html or
logout.jsp...no problem, the new session is created.
If you click on
17 matches
Mail list logo
