File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes BEA/Weblogic and the fly likes WLS6.1 SP1 console Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Products » BEA/Weblogic
Reply Bookmark "WLS6.1 SP1 console" Watch "WLS6.1 SP1 console" New topic
Author

WLS6.1 SP1 console

Steve Snodgrass
Greenhorn

Joined: Jun 12, 2001
Posts: 27
I just upgraded from WLS61 to WLS61sp1. Since I upgraded I have been unable to unlock a user using the console. The unlock button is still there (Under Security/Users) but it just doesn't have the desired effect any longer. No message is displayed or error placed in the log or anything. It is almost like it is ignored. Has anyone else noticed this?
I posted this on the BEA newsgroups but thus far have been ignored.
Thanks...
Steve
Dean Funk
Ranch Hand

Joined: Apr 20, 2001
Posts: 42
Steve
Probably the newsgroups haven't helped because nobody's replicated it.
I would suggest that you run through the Security ACL examples and see if one of them illustrates the problem, then submit a bug to BEA WLS Customer Support, even if you're just on an eval license... the tech you get may know a workaround, if not you'll at least be upping the priority for the fix for this.
If one of the examples illustrates the problem, it's that much easier for the support tech to get engineering to work on it.
You can submit a bug to BEA Customer Support by emailing a concise problem description to 'support@bea.com'; include any log files or config files, and sample code as attachments - overkill
is better in this case.
Sorry I don't have a solution, only a directions to the road to the solution...
 
 
subject: WLS6.1 SP1 console
 
Threads others viewed
RMI server threading?
Shift Operator
Greetings! - "J2EE Performance Testing" book promotion
Your brains capacity
Why throw an RecordNotFoundException in your unlock method?
developer file tools