Weblogic.security.acl.realm.authentication... Exception

Hello All
the reason I'm moving a post-question from JMS to this section is people there
suggested this. anyway,
when I tried to use an applet which implemented MessageListener to send message,
I got the following exception ( the port 7001 had been granted to connect, resolve
in java.policy)
javax.naming.AuthenticationException [root exception is java.lang.SecurityException:Authentication
for user admin denied in realm webogic start server side trace: java.lang.SecurityException:Authentication
for user admin denied in realm weblogic at weblogic.security.acl.Realm.authentication(Realm.java
212) at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java 233) at weblogic.security.acl.internal.Security.authenticate(Security.java
135) at weblogic.kernel.bootSevicesImp.authenticat(BootServicesImp.java 119) at
weblogic.kernel.ExecuteThread.run(ExcuteThread.java:120 ..
My Question is why servlet or swing or other application out of applet don't generate
such exceptions even most codes are similar ? How to deal with this?
Thanks
John

Similar Messages

Weblogic.security.acl.DefaultRealmImpl missing

I try to implement a custom realm. I get an Exception because
weblogic.security.acl.Realm tries to use the class
weblogic.security.acl.DefaultRealmImpl which is missing. Instead the
class seems to exists in the package weblogic.security.acl.internal. Is
there a workaround out there to make the whole thing work. Or do I have
to wait for the next service pack (how long)?
Thanks, Bodo.

solved!
simply import weblogic.jar in the project

ClassCastException: weblogic.security.acl.internal.FileRealm

Hi,
I am trying to create new user through the CachingRealm.newUser(?,?,?) method..What
I do is -
weblogic.security.acl.BasicRealm baseRealm =
(weblogic.security.acl.BasicRealm)weblogic.security.acl.Security.getRealm();
weblogic.security.acl.CachingRealm realm = (weblogic.security.acl.CachingRealm)
baseRealm;
However it is not able to classcast to CachingRealm , it gives the exception -
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm..
Do I need to do anything else ?
Thx

Hi Kumar,
I took a look at config.xml
Looks like you do not have an alternate realm hooked into WebLogic and that is the
source of the problem.
If you try to cast anything to CachingRealm and call methods on it, when you don't have
an alternate realm, then the cast will fail with ClassCastException.
For example, take a look at the very, very simple JSP code
<%@ page import="
import java.util.*,
import weblogic.common.*,
import javax.servlet.*,
import javax.servlet.http.*,
import java.io.*,
import weblogic.security.*,
import weblogic.security.acl.User,
import weblogic.security.acl.Security,
import weblogic.security.acl.Realm,
import weblogic.security.acl.CachingRealm,
import weblogic.security.acl.*,
import java.security.acl.*,
import java.security.acl.Permission,
import java.security.Principal,
import javax.servlet.http.*,
import weblogic.html.*,
import weblogic.common.internal.WLColor
"%>
<%
response.setContentType("text/html");
BasicRealm basicRealm = Security.getRealm();
try {
((CachingRealm) basicRealm).clearCaches();
} catch (ClassCastException ce) {
out.println("There is a class cast.. getRealm ain't no returned a
CachingRealm");
out.println("This probably means that you don't have a pluggable realm hooked
into WebLogic.");
out.println("No pluggable Realm = no Cachingrealm!");
%>
This JSP will give you a class cast if you do not have some alternate realm hooked up
(LDAP, NTREalm, UnixRealm, RDBMSRealm)
But will work just fine if you do have an alternate realm hooked up .
I think that this is what you are seeing.
Hope this helps
Joe Jerry
kumar wrote:
Hi Jerry,
Thanks for your response.
I have attached my config.xml . It is a very small config.xml with all the default
configurations. Please look at it ..
Thx
Jerry <[email protected]> wrote:
Hi Kumar,
Do you have an alternate realm hooked into WebLogic (LDAP, UNIXrealm,
NTRealm,
CustomRealm)?
Thanks,
Joe Jerry
kumar wrote:
Hi,
I am trying to create new user through the CachingRealm.newUser(?,?,?)method..What
I do is -
weblogic.security.acl.BasicRealm baseRealm =
(weblogic.security.acl.BasicRealm)weblogic.security.acl.Security.getRealm();
weblogic.security.acl.CachingRealm realm = (weblogic.security.acl.CachingRealm)
baseRealm;
However it is not able to classcast to CachingRealm , it gives theexception -
java.lang.ClassCastException: weblogic.security.acl.internal.FileRealm..
Do I need to do anything else ?
Thx
Name: config.xml
config.xml Type: XML Document (text/xml)
Encoding: base64

Javax.security.auth.Subject and weblogic.security.acl.User

Hello,
We are trying to move some old authentication code (Weblogic 5.1) to JAAS
which comes with Weblogic 6.1. Here is my problem:
I can succesfully authenticate the Subject through my RDBMS Realm. But then, the rest of my code uses weblogic.security.acl.User
and not javax.security.auth.Subject for authorization and other tasks. So, how can I extract weblogic.security.acl.User from javax.security.auth.Subject?
I tried subject.getPrincipals(), since User indirectly implements Principal, but it comes back empty.
Any suggestions?

Hello,
We are trying to move some old authentication code (Weblogic 5.1) to JAAS
which comes with Weblogic 6.1. Here is my problem:
I can succesfully authenticate the Subject through my RDBMS Realm. But then, the rest of my code uses weblogic.security.acl.User
and not javax.security.auth.Subject for authorization and other tasks. So, how can I extract weblogic.security.acl.User from javax.security.auth.Subject?
I tried subject.getPrincipals(), since User indirectly implements Principal, but it comes back empty.
Any suggestions?

Weblogic.security.acl.internal.AuthenticatedSubject not resolved

Hi guys,
when I try to implement that code:
CallbackHandler handler = new URLCallbackHandler(username,
password);
Subject mySubject =
weblogic.security.services.Authentication.login(handler);
weblogic.servlet.security.ServletAuthentication.runAs(mySubject, request);
// Where request is the httpservletrequest object.
in my servlet I get that issue in workshop 9.2:
The type weblogic.security.acl.internal.AuthenticatedSubject cannot be resolved. It is indirectly
referenced from required .class files
Any idea??
Thanks a lot
L.

solved!
simply import weblogic.jar in the project

Location of weblogic.security.acl.internal.AuthenticatedSubject

I'm trying to compile this code:
CallbackHandler handler = new URLCallbackHandler(userName, password);
Subject subject = Authentication.login(handler);
ServletAuthentication.runAs(subject, request);
But ServletAuthentication.runAs complains that it relies on class weblogic.security.acl.internal.AuthenticatedSubject which is not found.
i agree, i don't find it in either weblogic.jar or wls-api.jar from the 10.3.4 lib directory.
Where do i get this code?

Found it!
It's in
com.bea.core.weblogic.security.identity.jar in the Middleware/modules directory

AclEntry.setNegativePermissions() implemented by weblogic.security.acl.AclEntryImpl?

I've implemented a custom realm on wl6.1 sp1 which extends the LDAPv2 realm
(implementing the ManageableRealm interface) for users and groups and
delegates to a rdbms delegate for aclentry management. I read an earlier
post about revoking a permission which requires a custom realm to augment
the weblogic.security.acl.AclImpl class. My question is similar in nature.
In a situation where a positive AclEntry needs to be changed to a negative
entry, what are the requirements imposed on the custom realm implementer?
Do I need to worry about the checkPermission call on the Acl implementation?
On the AclEntry implementation? Is there a BEA recommended path similar to
that for revoking permissions?
I would also recommend that the BEA responses to the revoking permissions
post and this be included in the documentation outlining the
responsibilities for implementing a custom realm.
Thanks!
Jon
Jon Wilmoth
Software Architect
eSage Group
(206) 264-5675 (Voice & Fax)
[email protected]
http://www.esagegroup.com

Hi Jon,
Your issue should be raised with BEA support. With regard to your second isssue:
"and this be included in the documentation outlining the
responsibilities for implementing a custom realm."
You should raise this as an enhancement either via the support channels or via
[email protected]
Kind Regards,
Richard Wallace.
Senior Developer Relations Engineer.
BEA Support.
"Jon Wilmoth" <[email protected]> wrote:
I've implemented a custom realm on wl6.1 sp1 which extends the LDAPv2
realm
(implementing the ManageableRealm interface) for users and groups and
delegates to a rdbms delegate for aclentry management. I read an earlier
post about revoking a permission which requires a custom realm to augment
the weblogic.security.acl.AclImpl class. My question is similar in nature.
In a situation where a positive AclEntry needs to be changed to a negative
entry, what are the requirements imposed on the custom realm implementer?
Do I need to worry about the checkPermission call on the Acl implementation?
On the AclEntry implementation? Is there a BEA recommended path similar
to
that for revoking permissions?
I would also recommend that the BEA responses to the revoking permissions
post and this be included in the documentation outlining the
responsibilities for implementing a custom realm.
Thanks!
Jon
Jon Wilmoth
Software Architect
eSage Group
(206) 264-5675 (Voice & Fax)
[email protected]
http://www.esagegroup.com

Weblogic.security.acl in Weblogic 6

I came across the following in the migration documention
(http://edocs.bea.com/wls/docs60/notes/migrate.html#1026915):
I'm assuming that this is just a typo or wording issue but it currently
reads "weblogic.security.acl" is deprecated? Can't be the whole package.
Anyone else notice this?
Deprecated APIs and Features
The following APIs and features are deprecated in anticipation of future
removal from the product:
a.. weblogic.security.acl
b.. WebLogic Events
WebLogic Events are deprecated and should be replaced by JMS messages with
NO_ACKNOWLEDGE or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Programming
WebLogic JMS for more information.
c.. WebLogic HTMLKona
d.. T3 Driver

request.getRemoteUser() still works fine for me after I implented a custom
Autthenication / LoginModule.
"patrik" <[email protected]> wrote in message
news:[email protected]..
>
Yes, I have. see:
http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.develo
per.interest.security&item=8553&utag=
>
But if you've managed to get out the information from it I'd be gratefulto know
how.
/Patrik
"Utpal" <[email protected]> wrote:
Have you tried weblogic.security.Security.getCurrentSubject() ??
-utpal

Weblogic.security.acl.User extends java.security.Identity which is deprecated

I have been developing a custom realm for WLS5.1 and I discovered that the
weblogic classes seem to be based on JDK1.1 classes some of which
have been deprecated (e.g. java.security.Identity). I checked the docs
for WLS6.0 and it also uses the same classes.
When do you (BEA) intend to bring the weblogic security classes up
to date? JDK 1.2 has been out for a LONG time!

The WLS security group is currently looking into this.
-Nelson

Using weblogic security roles in authentication: weblogic 9

Hi All,
I am trying to create a simple application which uses declarative authorization configured in web.xml. I use the simple form based authentication. While trying to deploy my application, I get the error:
weblogic.management.DeploymentException: [HTTP:101168]The security-role-assignment references an invalid security-role: LTVORole.
But I have defined the role LTVORole in weblogic using the administrator console.
below are the details of what I have done:
Web.xml:
========
<?xml version='1.0' encoding='UTF-8'?>
<j2ee:web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee">
<j2ee:welcome-file-list>
    <j2ee:welcome-file>login.jsp</j2ee:welcome-file>
    <j2ee:welcome-file>index.html</j2ee:welcome-file>
    <j2ee:welcome-file>index.htm</j2ee:welcome-file>
</j2ee:welcome-file-list>
<j2ee:login-config>
    <j2ee:auth-method>FORM</j2ee:auth-method>
    <j2ee:form-login-config>
      <j2ee:form-login-page>/login.jsp</j2ee:form-login-page>
      <j2ee:form-error-page>/error.jsp</j2ee:form-error-page>
    </j2ee:form-login-config>
</j2ee:login-config>
<security-constraint>
<display-name>checkAccountConstraint</display-name>
<web-resource-collection>
<web-resource-name>checkAccountCollection</web-resource-name>
        <url-pattern>test.jsp</url-pattern>
        <http-method>GET</http-method>
        <http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
        <role-name>LTVORole</role-name>
</auth-constraint>
</security-constraint>
</j2ee:web-app>Weblogic.xml
===========
<?xml version="1.0" encoding="UTF-8"?>
<ns:weblogic-web-app xmlns:ns="http://www.bea.com/ns/weblogic/90">
<security-role-assignment>
    <role-name>LTVORole</role-name>
   <externally-defined/>
</security-role-assignment>
</ns:weblogic-web-app>I have created the role in weblogic in the menu
security realms > myrealm > roles and policies > Global Roles > roles > LTVORole
Is it the right way to define a role?
Please help me find where I am going wrong.
Thanking you all in advance,
Gireesh

Hi All,
I am trying to create a simple application which uses declarative authorization configured in web.xml. I use the simple form based authentication. While trying to deploy my application, I get the error:
weblogic.management.DeploymentException: [HTTP:101168]The security-role-assignment references an invalid security-role: LTVORole.
But I have defined the role LTVORole in weblogic using the administrator console.
below are the details of what I have done:
Web.xml:
========
<?xml version='1.0' encoding='UTF-8'?>
<j2ee:web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee">
<j2ee:welcome-file-list>
    <j2ee:welcome-file>login.jsp</j2ee:welcome-file>
    <j2ee:welcome-file>index.html</j2ee:welcome-file>
    <j2ee:welcome-file>index.htm</j2ee:welcome-file>
</j2ee:welcome-file-list>
<j2ee:login-config>
    <j2ee:auth-method>FORM</j2ee:auth-method>
    <j2ee:form-login-config>
      <j2ee:form-login-page>/login.jsp</j2ee:form-login-page>
      <j2ee:form-error-page>/error.jsp</j2ee:form-error-page>
    </j2ee:form-login-config>
</j2ee:login-config>
<security-constraint>
<display-name>checkAccountConstraint</display-name>
<web-resource-collection>
<web-resource-name>checkAccountCollection</web-resource-name>
        <url-pattern>test.jsp</url-pattern>
        <http-method>GET</http-method>
        <http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
        <role-name>LTVORole</role-name>
</auth-constraint>
</security-constraint>
</j2ee:web-app>Weblogic.xml
===========
<?xml version="1.0" encoding="UTF-8"?>
<ns:weblogic-web-app xmlns:ns="http://www.bea.com/ns/weblogic/90">
<security-role-assignment>
    <role-name>LTVORole</role-name>
   <externally-defined/>
</security-role-assignment>
</ns:weblogic-web-app>I have created the role in weblogic in the menu
security realms > myrealm > roles and policies > Global Roles > roles > LTVORole
Is it the right way to define a role?
Please help me find where I am going wrong.
Thanking you all in advance,
Gireesh

Weblogic realm authentication failure getting connection from pool

We are getting this error when we try to get a connection from the
pool for a Tx Data Source. We are successfully getting connections
from a (non-Tx) Data Source.
java.lang.SecurityException: Authentication for user Fitness_demo
denied in realm weblogic
at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.security.acl.Security.doAsPrivileged(Security.java:481)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:127)
We have added the DB user as a user in the realm, which usually does
the trick; but in this case it does not. We are using Merant's
JSQLConnect type 2 driver for SQL Server, and we are running on
Solaris. The scenario works fine using Oracle Thin driver on Windows.
Do we need ACL entries or something? We do not have any ACL entries
now.
Thanks,
-wes

We are getting this error when we try to get a connection from the
pool for a Tx Data Source. We are successfully getting connections
from a (non-Tx) Data Source.
java.lang.SecurityException: Authentication for user Fitness_demo
denied in realm weblogic
at weblogic.security.acl.Realm.authenticate(Realm.java:212)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.security.acl.Security.doAsPrivileged(Security.java:481)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:127)
We have added the DB user as a user in the realm, which usually does
the trick; but in this case it does not. We are using Merant's
JSQLConnect type 2 driver for SQL Server, and we are running on
Solaris. The scenario works fine using Oracle Thin driver on Windows.
Do we need ACL entries or something? We do not have any ACL entries
now.
Thanks,
-wes

Weblogic 6.0 NT authentication

Hi,
I am trying to use NT authentication with Weblogic 6.0. I followed the
Managing Security chapter of the Weblogic Documentation. I created the
"system" user with the appropriate rights. I defined the security
realm and the caching realm. Then I log on to the domain using the
system account, and start the weblogic service. Then when I start the
weblogic server from the command line, I got the following error:
<Unable to initialize the server: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.lang.SecurityException:
Unable to assert all required priviledges -- bad domain name
java.lang.IllegalAccessError: java.lang.SecurityException: Unable to
assert all required priviledges -- bad domain name
     at weblogic.security.acl.Realm.getRealm(Realm.java:91)
     at weblogic.security.acl.Realm.getRealm(Realm.java:62)
     at weblogic.security.SecurityService.initializeRealm(SecurityService.java:265)
     at weblogic.security.SecurityService.initialize(SecurityService.java:123)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
     at weblogic.Server.main(Server.java:35)
'>
####<Aug 7, 2001 11:01:48 AM PDT> <Error> <Security> <scatech1039>
<intranetServer> <main> <> <> <090052> <Server installed as NT Service
with incorrect password for user system.>
####<Aug 7, 2001 11:01:48 AM PDT> <Emergency> <Server> <scatech1039>
<intranetServer> <main> <> <> <000000> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system
denied; contact your administrator to correct NT Service attributes
java.lang.SecurityException: Authentication for user system denied;
contact your administrator to correct NT Service attributes
     at weblogic.security.SecurityService.initializeSuid(SecurityService.java:311)
     at weblogic.security.SecurityService.initialize(SecurityService.java:125)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
     at weblogic.Server.main(Server.java:35)
'>
Any idea on this is sincerely appreciated. Thanks.
Chris

Hi Chris,
Are you running WLS from the command line or as a NT service ?
If you are running from the command line try running it as a NT service
and see if you can authenticate users from NT
Also have you defined your Primary Domain Controller correctly when you configure the
realm?
Chris Wu wrote:
Hi,
I am trying to use NT authentication with Weblogic 6.0. I followed the
Managing Security chapter of the Weblogic Documentation. I created the
"system" user with the appropriate rights. I defined the security
realm and the caching realm. Then I log on to the domain using the
system account, and start the weblogic service. Then when I start the
weblogic server from the command line, I got the following error:
<Unable to initialize the server: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: java.lang.SecurityException:
Unable to assert all required priviledges -- bad domain name
java.lang.IllegalAccessError: java.lang.SecurityException: Unable to
assert all required priviledges -- bad domain name
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.java:265)
at weblogic.security.SecurityService.initialize(SecurityService.java:123)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
####<Aug 7, 2001 11:01:48 AM PDT> <Error> <Security> <scatech1039>
<intranetServer> <main> <> <> <090052> <Server installed as NT Service
with incorrect password for user system.>
####<Aug 7, 2001 11:01:48 AM PDT> <Emergency> <Server> <scatech1039>
<intranetServer> <main> <> <> <000000> <Unable to initialize the
server: 'Fatal initialization exception
Throwable: java.lang.SecurityException: Authentication for user system
denied; contact your administrator to correct NT Service attributes
java.lang.SecurityException: Authentication for user system denied;
contact your administrator to correct NT Service attributes
at weblogic.security.SecurityService.initializeSuid(SecurityService.java:311)
at weblogic.security.SecurityService.initialize(SecurityService.java:125)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
Any idea on this is sincerely appreciated. Thanks.
Chris

Java.security.acl.NotOwnerException when Administration Port is set

I get the NOE, posted below, when I start some of my managed servers, while other managed servers
start fine. After some scrutiny I discover the differences is that in /console, I've set some of my
managed server's Administration Port to that of my admin server, and these are the ones that are
busted! Those that I left as default '0' start up just fine. Hence the question: "What the heck
is the use of this field???"
<Apr 3, 2001 3:12:02 PM PDT> <Info> <WebLogicServer> <IIOP subsystem enabled.>
<Apr 3, 2001 3:12:02 PM PDT> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:894)
at weblogic.management.Admin.start(Admin.java:311)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:894)
at weblogic.management.Admin.start(Admin.java:311)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Gene Chuang
Join Kiko.com!

Ah, I see! The introduction of an "admin server" in 6.0 caused the confusion for me. The
Administration Port is NOT the port number of the admin server!
Gene
"Kumar Allamraju" <[email protected]> wrote in message news:[email protected]...
This is equivalent to weblogic.system.AdministrationPort in 451/510.
In 451/51 if you start WLS server with
java -Dweblogic.system.administrativePort=2000 weblogic.Server
and then executing
D:\releases\510>java weblogic.Admin admin://localhost:2000 VERSION
returns the WLS version.
WebLogic Build: 5.1.0 Service Pack 8 12/20/2000 16:34:54 #95137
Bottom line is, once you set admin port, all admin stuff can be done on admin protocol only.
It appears this is not happening/broken in 6.0 . There's already an engg issue filed on thisproblem.
>
Kumar
Gene Chuang wrote:
I get the NOE, posted below, when I start some of my managed servers, while other managed
servers
start fine. After some scrutiny I discover the differences is that in /console, I've set someof my
managed server's Administration Port to that of my admin server, and these are the ones that are
busted! Those that I left as default '0' start up just fine. Hence the question: "What theheck
is the use of this field???"
<Apr 3, 2001 3:12:02 PM PDT> <Info> <WebLogicServer> <IIOP subsystem enabled.>
<Apr 3, 2001 3:12:02 PM PDT> <Emergency> <Server> <Unable to initialize the server: 'Fatal
initialization exception
Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:894)
at weblogic.management.Admin.start(Admin.java:311)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java
:244)
at weblogic.jndi.Environment.getContext(Environment.java:135)
at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:894)
at weblogic.management.Admin.start(Admin.java:311)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Gene Chuang
Join Kiko.com!

Weblogic.security.ldaprealmv2.LDAPRealmException

Environment:
WebLogic version: WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
jdk: 1.3.1
OS: Solaris 7
LDAP server: iPlanet Directory Server 5.0
Realm: LDAP2Realm CustomRealm weblogic.security.ldaprealmv2.LDAPRealm
ISSUE:
Certain LDAP users cause an Exception to propagate up to produce a 500
internal server error. How can one programmetically catch this
internal Exception? Why is this Exception thrown? I would have assumed
that the WebLogic realm componet would would prevent such Exceptions
from reaching the top?
NOTE1: Other users that exhast their login tries DO NOT produces this
Exception.
NOTE2: I know this could very well be a bug in the iPlanet Directory
Server 5.0 and/or the weblogic custom ream classes.
EXCEPTION:
<Apr 30, 2002 10:32:20 AM PDT> <Error> <HTTP>
<[WebAppServletContext(8204614,dailyrpts,/dailyrpts)] Servlet failed
with Exception
netscape.ldap.LDAPException: error result (19); Exceed password retry
limit. Please try later.; Constraint violation
at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4852)
at netscape.ldap.LDAPConnection.internalBind(LDAPConnection.java:1757)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1294)
at netscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1303)
at netscape.ldap.LDAPConnection.bind(LDAPConnection.java:1613)
at weblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:782)
at weblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
at weblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRealm.java:186)
at weblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRealm.java:127)
at weblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.java:110)
at weblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
at weblogic.security.acl.Realm.authenticate(Realm.java:200)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.servlet.security.internal.SecurityModule.checkAuthenticate(SecurityModule.java:262)
at weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:217)
at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:155)
at weblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityModule.java:169)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:144)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.security.ldaprealmv2.LDAPRealmException: caught unexpected
exception - with nested exception:
[netscape.ldap.LDAPException: error result (19); Exceed password retry
limit. Please try later.; Constraint violation]
at weblogic.security.ldaprealmv2.LDAPDelegate.handleException(LDAPDelegate.java:884)
at weblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:801)
at weblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
at weblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRealm.java:186)
at weblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRealm.java:127)
at weblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.java:110)
at weblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
at weblogic.security.acl.Realm.authenticate(Realm.java:200)
at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at weblogic.security.acl.internal.Security.authenticate(Security.java:125)
at weblogic.servlet.security.internal.SecurityModule.checkAuthenticate(SecurityModule.java:262)
at weblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecurityModule.java:217)
at weblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.java:155)
at weblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityModule.java:169)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:144)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2467)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Ok, so the only way to catch this is to create an "error-page" in the
web.xml file that will catch this exception-type. I hoping I could do
this in code somewhere...
Thanks!
Now I need to figure out why this Exceptionis being thrown!!
My Research:
http://developer.netscape.com/docs/manuals/dirsdk/jsdk30/exceptns.htm
http://developer.netscape.com/docs/manuals/dirsdk/jsdk30/exceptn1.htm
http://docs.iplanet.com/docs/manuals/dirsdk/jsdk41/Reference/netscape/ldap/LDAPException.html
CONSTRAINT_VIOLATION
An internal error occurred in the LDAP server.
Constant of Class
LDAPException
Syntax
public static final int CONSTRAINT_VIOLATION
Description
This exception corresponds to a result code of 19.
"kirann" <[email protected]> wrote in message news:<[email protected]>...
hi,
you can catch this by defining.. <exception> in the web.xml.. see that
dtd..
thanks
kiran
"Matrix" <[email protected]> wrote in message
news:[email protected]...
Environment:
WebLogic version: WebLogic Server 6.1 SP2 12/18/2001 11:13:46 #154529
jdk: 1.3.1
OS: Solaris 7
LDAP server: iPlanet Directory Server 5.0
Realm: LDAP2Realm CustomRealm weblogic.security.ldaprealmv2.LDAPRealm
ISSUE:
Certain LDAP users cause an Exception to propagate up to produce a 500
internal server error. How can one programmetically catch this
internal Exception? Why is this Exception thrown? I would have assumed
that the WebLogic realm componet would would prevent such Exceptions
from reaching the top?
NOTE1: Other users that exhast their login tries DO NOT produces this
Exception.
NOTE2: I know this could very well be a bug in the iPlanet Directory
Server 5.0 and/or the weblogic custom ream classes.
EXCEPTION:
<Apr 30, 2002 10:32:20 AM PDT> <Error> <HTTP>
<[WebAppServletContext(8204614,dailyrpts,/dailyrpts)] Servlet failed
with Exception
netscape.ldap.LDAPException: error result (19); Exceed password retry
limit. Please try later.; Constraint violation
at netscape.ldap.LDAPConnection.checkMsg(LDAPConnection.java:4852)
atnetscape.ldap.LDAPConnection.internalBind(LDAPConnection.java:1757)
atnetscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1294)
atnetscape.ldap.LDAPConnection.authenticate(LDAPConnection.java:1303)
at netscape.ldap.LDAPConnection.bind(LDAPConnection.java:1613)
atweblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:78
2)
atweblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
atweblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRea
lm.java:186)
atweblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRea
lm.java:127)
atweblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.ja
va:110)
atweblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
at weblogic.security.acl.Realm.authenticate(Realm.java:200)
atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
atweblogic.security.acl.internal.Security.authenticate(Security.java:125)
atweblogic.servlet.security.internal.SecurityModule.checkAuthenticate(Security
Module.java:262)
atweblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecu
rityModule.java:217)
atweblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.
java:155)
atweblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityMod
ule.java:169)
atweblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
tSecurityManager.java:144)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2467)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.security.ldaprealmv2.LDAPRealmException: caught unexpected
exception - with nested exception:
[netscape.ldap.LDAPException: error result (19); Exceed password retry
limit. Please try later.; Constraint violation]
atweblogic.security.ldaprealmv2.LDAPDelegate.handleException(LDAPDelegate.java
:884)
atweblogic.security.ldaprealmv2.LDAPDelegate.authenticate(LDAPDelegate.java:80
1)
atweblogic.security.ldaprealmv2.LDAPRealm.authUserPassword(LDAPRealm.java:60)
atweblogic.security.acl.AbstractListableRealm.authInternal(AbstractListableRea
lm.java:186)
atweblogic.security.acl.AbstractListableRealm.authenticate(AbstractListableRea
lm.java:127)
atweblogic.security.acl.AbstractListableRealm.getUser(AbstractListableRealm.ja
va:110)
atweblogic.security.acl.CachingRealm.authenticate(CachingRealm.java:956)
atweblogic.security.acl.CachingRealm.getUser(CachingRealm.java:863)
at weblogic.security.acl.Realm.authenticate(Realm.java:200)
atweblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
atweblogic.security.acl.internal.Security.authenticate(Security.java:125)
atweblogic.servlet.security.internal.SecurityModule.checkAuthenticate(Security
Module.java:262)
atweblogic.servlet.security.internal.FormSecurityModule.checkUserPerm(FormSecu
rityModule.java:217)
atweblogic.servlet.security.internal.SecurityModule.beginCheck(SecurityModule.
java:155)
atweblogic.servlet.security.internal.FormSecurityModule.checkA(FormSecurityMod
ule.java:169)
atweblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
tSecurityManager.java:144)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:2467)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

WebLogic 8.1 SP4 throws exception on empty markupString/

I'm not sure, but seems that WLW 8.1 SP4 doesn't like empty <markupString/> in markupResponse.
soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<getMarkupResponse
xmlns="urn:oasis:names:tc:wsrp:v1:types">
<markupContext>
<mimeType>text/html;
charset=UTF-8</mimeType>
<markupString/>
<locale>en</locale>
<requiresUrlRewriting>true</requiresUrlRewriting>
<preferredTitle>User Info</preferredTitle>
</markupContext>
</getMarkupResponse>
</soapenv:Body>
</soapenv:Envelope>
Here is Exception traces:
java.lang.NullPointerException at
weblogic.xml.babel.adapters.DOMAdapter.adapt(DOMAdapter.java:58)
at
weblogic.xml.babel.stream.DOMInputStream.open(DOMInputStream.java:53)
at
weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:95)
at
com.bea.wsrp.consumer.markup.MarkupRewriter.rewrite(MarkupRewriter.java:274)
at
com.bea.wsrp.consumer.markup.MarkupRewriter.rewriteAsString(MarkupRewriter.java:237)
at
com.bea.wsrp.consumer.controls.ProxyPortletContent.writeMarkup(ProxyPortletContent.java:370)
at
com.bea.wsrp.consumer.controls.ProxyPortletContent.beginRender(ProxyPortletContent.java:277)
at
com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:495)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:485)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:190)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:106)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:356)
at
com.bea.netuix.nf.UIControl.render(UIControl.java:512)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:405)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58)
at
jsp_servlet._framework._skeletons._default.__flowlayout._jspService(flowlayout.jsp:33)
at
weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:194)
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:96)
at
com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:491)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:485)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:190)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:106)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:356)
at
com.bea.netuix.nf.UIControl.render(UIControl.java:512)
at
com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:405)
at
com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123)
at
com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58)
at
jsp_servlet._framework._skeletons._default.__gridlayout._jspService(gridlayout.jsp:33)
at
weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:638)
at
weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:423)
at
com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:194)
at
com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:96)
at
com.bea.netuix.nf.ControlLifecycle$1.visit(ControlLifecycle.java:491)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:485)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:496)
at
com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:190)
at
com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:204)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:146)
at
com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:321)
at
com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:184)
at
com.bea.netuix.servlets.manager.PortalServlet.doPost(PortalServlet.java:767)
at
com.bea.netuix.servlets.manager.PortalServlet.doGet(PortalServlet.java:671)
at
com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:135)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1006)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
at
weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.myee.portal.YahooLoginFilter.doFilter(YahooLoginFilter.java:122)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:293)
at
weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6724)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3764)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2644)
at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

Why is the producer returning an empty string? What
is the intent?
SubbuProducer portlet speciality in this case is to return User Profile markup fragment. Because user logged into WebLogic was not succesfully authenticated by remote app server where remote producer resides), there was no user profile markup generated for such user.
But, I guess, we should talk about more general case of whether it is allowed by WSRP 1.0 spec to return empty <markupString/> element... My reading is that there is nothing illegal in returning empty <markupString/>.
Therefore, it should be handled gracefully with no exception thrown...

Weblogic.security.acl.realm.authentication... Exception

Similar Messages

Maybe you are looking for