Win a copy of Terraform in Action this week in the Cloud forum!

Rejeev Divakaran

Greenhorn
+ Follow
since Aug 12, 2007
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Rejeev Divakaran

I am also having the same issue.
I have a bean with compund pk (a, b). Another bean also with compound pk (a, c). I have a CMR from first to second, where foreign key (in table first) is (a,c).
Any clue why this error comes?
Normally you cannot stop a request (query) under execution. session.invalidate will only demands re-login for subsequent requests.
13 years ago
Could you please provide the complete stacktrace?
13 years ago
weblogic.Server is the main class of Weblogic server. This present in weblogic.jar. It looks like weblogic.jar is not in classpath.
13 years ago
When a message is re-tried, same instance of MDB may not be used.
You can find the uniqueness of an object by using identityhashcode.
Looks like the object returned by JNDI lookup contains (references) an instance of EntityExistsException and EntityExistsException is not in the client side classpath.
I would suggest to use WebLogic timer. You can schedule the timers in startup class and cancel the same in shutdown class. Status communication and pause/stop communications can be through a JMS queue.
Weblogic Server has tag in it's deployment descriptors (weblogic-application.xml) for this. Tag name is [classloader-structure]
Pramati Application Server is also having similar tags. Not sure about others.
As I understand siteminder stores the username and password for each application it manages. When a new request comes it checks if the request is authenticated if not, it do the login (using stored user details) to the application and then forward the request to original request.

I provide a link the logout page where the user can click to relogin to the application. So whenever the user clicks on it he should be prompted with the siteminder login screen, instead it is directly taking me to the application.


This is more of a design issue. Re-login link should point to welcome page not the login page. If the welcome page is protected, appropriate login page will be displayed.

But if i close the window and open the new window i am getting that login prompt.


when you close and re-open the window it is new session; old login is lost

But when the users types the same URL in the same page he is taken into the application without login screen


When you type URI on the same window, it is the same session and login is carried forward.
13 years ago
No. Even if the EJB and Web modules are part of the same EAR, you need to use JNDI lookup to get the Home interface preferably through [ejb-ref] tag in the web.xml . Also you have to use Remote interface (not local interface). Most of the application servers provide optimizations if the EJB client is part of the same application (For WebLogic refer the tag enable-call-by-reference).
You can download Weblogic server. they have non expiring eval license with that.
Pramati Studio is very good IDE, but not free, one month eval license is available.
Eclipse, NetBeans also should be good. don't know about J2EE support.
14 years ago
As I understand your system:
1) if there is no cookie it assumes a first time user and redirect to registration page (for this you need to set a cookie with 0 expiry date)
2) if there a session cookie (with name JSESSIONID) and it is invalid, redirect to login page
3) if there is no session cookie redirect to login page
4) if there a valid session cookie allow to proceed

Where do you need to login twice?
You need to invalidate session during logout to invalidate the session cookie
calling helper method is thread safe so longer the method is in the same bean class or object which contains the method is instantiated per request or is instance level variable in the bean class.

Now the issue is data set can go upto a million records and we are getting the whole lot of data from the DB in one go


You can try query like below to introduce paging in DB layer.
select * from emp where empid < ?1 and rownum < 100 order by empid
You need to pass the empid of last returned row to this query.
14 years ago
you cannot look up MDB from client. if you want to access MDB you rather send a message to the Queue.
MDB is another EJB, you can see the status like any other EJB. Please explore the admin console for details.
14 years ago