Weblogic singleto with weblogic timer

Pls give some sample for using both weblogic singleton and weblogic timer.

weblogic sibgleton should invoke weblogic timer service?

Similar Messages

Persisting a trigger with weblogic time services

Hello,
I'm using Weblogic v4.51
Does weblogic provide a way to persist triggerable events so that if the
server is shut down and restarted, the triggerable events are still
scheduled?
Or do I have to write my own persistence system for scheduled events?
any comments are appreciated,
thanks,
Tom

Yes, you are in true.
But, I can't understand it. Weblogic allow to execute a number of threads that
couldn't go far in execution (they haven't resources) ... and maintains them runnable.
But, the thread that could progress in their execution (they have the resources)
aren't runnables ...
The only solution is the one you say ... but I think the way weblogic schedules
the execute threads isn't a good way.
Thanks
"Adam Messinger" <[email protected]> wrote:
>
"jlglez" <[email protected]> wrote in message
news:3b9899a4$[email protected]..
Ok. I have a problem with concurrency and locks with weblogic ... hereis
my thread
dump:
Number of Threads of my Server: 15
Number of Threads of my Application: 25
LDAPPool: 5
Yes, I know the second is bigger than the first. I try to create anscenario of
a number of apps over the same server.It looks like the majority of your threads are waiting while attempting
to
get an LDAP connection. Make that pool bigger (same size as number of
execute threads).
Cheers!
Adam

Deploy web application in jbuilder 9 with weblogic 7 problem

when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
where options include:
-help Print this help message.
-version Print version information.
-adminurl <https://<server>:<port>> The URL of the administration server: default
http://localhost:7001
-user <user> A user other than the default of
"installadministrator"
-password <password> Specifies the password on the command line.
If this option is absent the user is
prompted.
-verbose Displays additional status during the
deployment process, including notifications
when the application is prepared and
activated on each target.
-debug Displays debug level messages to the standard
output.
-examples Display example usage of this tool.
-upload Causes the specified source file(s) to be
transferred to the adminstration server. This
is used when the Deployer tools is not being
used on the same machine as the adminstration
server and the user does not otherwise have
access to place the targeted files on the
adminstration server.
-delete_files Causes the server to remove the files that
are specified in the file list and leave the
application activated. This option is valid
only for unarchived web applications.
-remote Signals that the tools is not runnning on the
same machine as the adminstration server and
that the source path should be made passed
through unchanged as it represents the path
on the remote server.
-nostage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged and the
original source is be used.
-external_stage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged but the
value of the staging path will be used when
preparing the application.
-stage Sets the stagingMethod staging attribute on
the application when it is created so that
the application will always be staged. This
value will override the stagingMethod
attribute on any targeted servers.
-nowait Once the action is initiated the tool will
print the task id and exit. This is used to
initiate multiple tasks and then monitor them
later using the -list action.
-timeout <seconds> The maximum time in seconds to wait for the
completion of the deployment task. When the
time expires the current status is printed
and the program exits.
-source <archive file or directory> Location of the file or directory that
represents the enterprise component or
application tha is being (re)activated. If
the source file is relative it is relative to
the current directory, unless the -remote
option is used. To specify individual files
within an application for reployment or
addition list them at the end of the command
line.
-name <application name> The name of the application being deployed.
-targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
cluster names. Each target may be qualified
with a J2EE component name. This enables
different components of the archive to
deployed on different servers.
-id <task identifier> Optional client supplied unique identifier
for the deployment task. The id is first
specified to -activate, -deactivate,
-unprepare or -remove. It is then used later
as an argument to -cancel or -list.
-activate (Re)activates the <source> application on the
<targets> with the <name>.
-deactivate Deactivates the application <name> on the
<targets> leaving an staged application files
in a state where the may be quickly
reactivated.
-unprepare Deactivates and unloads classes for the
application <name> on the <targets> leaving
an staged application files in a state where
the may be quickly reloaded.
-remove Deactivates the application <name> on the
<target> and removes any files that were
staged for this application. If there are no
longer any targets for the application, the
associated configuration is completely
removed.
-cancel Atempts to cancel the task <id> if it is has
not yet completed.
-list Lists the target status of each task <id>
-deploy a convenient alias for activate.
-undeploy a convenient alias for unprepare.
Optionally a list of the specific files in the archive that are to be
redeployed may be specified. If a directory is specified the entire subtree is
redeployed.
Full documentation on this tool is available at:
http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
No actions was specified. Please specify one and only one of:
-activate, -deactivate, -cancel, -remove, -unprepare, or -list.
Type java weblogic.Deployer -examples for example usage.

you use "deploy" under DOS-Mode to deploy your web application?
i found some differences between "deploy" and "redeploy" function in jbuilder 9.
when i choose "deploy" ,jbuilder shows me the commond below:
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility

Security violation exception with Weblogic cluster installation on OIm 9.1

Hi,
I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
e, signature={}.
at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
riptor.java:486)
at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
:80)
at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
... 126 more
ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
Interface encounter some problems: {1}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.in
Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
Any suggestions would be useful...

No Response???
Where are the good guys??

How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Weblogic SSO with AD - My Try - What's wrong?

Dear All
I'm trying to setup Weblogic to Authenticate using AD and have SSO with a Windows workstation(joined to the domain).
I just setup an Active Directory(Win2K3), a Windows XP(SP2) and a Linux System(CentOS5) with Weblogic 10.3.
I'm wondering what is wrong with my configuration. I can only logon on Adminstration Console using weblogics local users, and even with entering username(those which created on AD) and password AD Authentication does not work.
Anyone has simliar experiance or any clue?
Appreciated
TIA
Cheers
Here is the setup:
The domain is: example.com and machines are: dc.example.com (AD), winclient.example.com (Windows XP joined to the example.com domain) and weblogic.example.com (CentOS with Weblogic 10.3 installed)
The hosts file on all three machines are filled with their FQDN, Machine Name and corresponding IP addresses. They all have ping working successfully between each two of them. Firewalls are checked to be off.
These are the steps I came through based on documentation I could found on the net:
h1. 0. Configuring Your Network Domain to Use Kerberos
In Linux Machine(Weblogic Server) edit Kerberos configuration file for appropriate values:
*/etc/krb5.conf*
\[logging\]
default = FILE:/var/log/krb5libs.log
kdc = FILE:/var/log/krb5kdc.log
admin_server = FILE:/var/log/kadmind.log
\[libdefaults\]
default_realm = EXAMPLE.COM
default_tkt_enctypes = des-cbc-crc
default_tgs_enctypes = des_cbc_crc
dns_lookup_realm = false
dns_lookup_kdc = false
ticket_lifetime =28800
forwardable = yes
\[realms\]
EXAMPLE.COM = {
kdc = 192.168.1.193:88
admin_server = dc
default_domain = EXAMPLE.COM
\[domain_realm\]
.example.com = EXAMPLE.COM
example.com = EXAMPLE.COM
\[kdc\]
profile = /var/kerberos/krb5kdc/kdc.conf
\[appdefaults\]
autologin = true
forward = true
forwardable = true
encrypt = true
pkinit = {
allow_pkinit = false
h1. 1. Create two users on AD: "New->User" with "User must change password at next logon" option cleared (not tidked)
weblogic (for weblogic service) (with password = "password1")
weblogicusr (the user which should access Weblogic Administration Console) ("password2")
* Note that group membership of these two users are left default.(Domain Users)
h1. 2. For "weblogic" & "weblogicusr" user set these Account Optiones:
- Use DES encryption types for this account (ticked)
- Do not require Kerberos preauthentication (cleared)
* then reset the password again for "weblogic" (with password = "password1") and "weblogicusr" (with "password2").
h1. 3. Create Service Principal Names for Weblogic Server and User on Win2K3 machine:
- >setspn -a host/weblogic.example.com weblogic
- >setspn -a HTTP/weblogic.example.com weblogic
here is the result
C:\Documents and Settings\Administrator.DC>setspn -L weblogic
Registered ServicePrincipalNames for CN=weblogic,CN=Users,DC=example,DC=com:
HTTP/weblogic
host/weblogic
HTTP/weblogic.example.com
host/weblogic.example.com
and
- >setspn -a HTTP/weblogic.example.com weblogicusr
and the result
C:\Documents and Settings\Administrator.DC>setspn -L weblogicusr
Registered ServicePrincipalNames for CN=Weblogic User,CN=Users,DC=example,DC=com:
HTTP/weblogicsrv.example.com
HTTP/weblogicsrv
h1. 4. Create the keytab file for Weblogic Server:
On AD machine issue:
(ktpass from MS Windows Support Tools)
>ktpass -princ host/[email protected] -pass password1 -mapuser weblogic -out c:\temp\weblogic.host.keytab
>ktpass -princ HTTP/[email protected] -pass password1 -mapuser weblogic -out c:\temp\weblogic.HTTP.keytab
(ktab from JRE 6)
>ktab -k c:\temp\weblogic.keytab -a [email protected]
Password for [email protected]:*password1*
Done!
Service key for [email protected] is saved in c:\temp\weblogic.keytab
** Note I could not kinit successfully merely with weblogic.host.keytab and/or weblogic.HTTP.keytab, I got this error +"Key table entry not found while getting initial credentials"+ how ever the keytab I created using ktab("weblogic.keytab") works fine in this case, so I decided to merge whole three of them into a keytab.
>\[root@weblogic keytabs\]# kinit -k -t weblogic.host.keytab [email protected]
>kinit(v5): Key table entry not found while getting initial credentials
h1. 5. Port and Merge keytabs
Then I ported these three files to the Linux Machine(weblogic.example.com): weblogic.host.keytab, weblogic.HTTP.keytab and weblogic.keytab
and merged into one keytab:
ktutil: "rkt weblogic.host.keytab"
ktutil: "rkt weblogic.HTTP.keytab"
ktutil: "rkt weblogic.keytab"
ktutil: "wkt weblogic-keytab"
ktutil: "q"
* then put the result keytab "weblogic-keytab" somewhere in Weblogic Path:
>/root/bea/user_projects/domains/base_domain/kerberos
h2. 5.1 Test the keytab and kerberos configuration
>\[root@weblogic keytabs\]# kinit -k -t weblogic-keytab [email protected]
>\[root@weblogic keytabs\]# klist
>Ticket cache: FILE:/tmp/krb5cc_0
>Default principal: [email protected]
>
>Valid starting Expires Service principal
>09/04/09 16:16:42 09/05/09 00:16:42 krbtgt/[email protected]
>
Kerberos 4 ticket cache: /tmp/tkt0
klist: You have no tickets cached
h1. 6. Creating a JAAS Login File
Create krb5Login.conf and put it in here: "/root/bea/user_projects/domains/base_domain/kerberos/"
krb5Login.conf
com.sun.security.jgss.initiate {
com.sun.security.auth.module.Krb5LoginModule required
principal=*"[email protected]"* useKeyTab=true
keyTab=*/root/bea/user_projects/domains/base_domain/kerberos/weblogic-keytab* storeKey=true;
com.sun.security.jgss.accept {
com.sun.security.auth.module.Krb5LoginModule required
principal=*"[email protected]"* useKeyTab=true
keyTab=*/root/bea/user_projects/domains/base_domain/kerberos/weblogic-keytab* storeKey=true;
h1. 7. Modify startup options
add these option to "/root/bea/user_projects/domains/base_domain/bin/startWebLogic.sh"
h2. 7.1 Kerberos
-Djava.security.krb5.realm=EXAMPLE.COM
-Djava.security.krb5.kdc=dc.example.com
-zjava.security.auth.login.config=$PATHTOKRB/krb5Login.conf
-Djavax.security.auth.useSubjectCredsOnly=false
-Dweblogic.security.enableNegotiate=true h2. 7.2 Debug
-DDebugSecurityAdjudicator=true
-Dweblogic.debug.DebugSecurityAtn=true
-Dsun.security.krb5.debug=true
-Dweblogic.StdoutDebugEnabled=true";
-Dweblogic.log.StdoutSeverity=Debugh1. 8. Configuring the Identity Assertion Provider
In Weblogic Administration I created a Security Realm called "example.com" with everything default and made it default. Then restarted the Weblogic Server.
Again in Administation Console did this to example.com Security Realm:
h2. 8.1 -> Prividers: Add 3 Providers
Negotiate     WebLogic Negotiate Identity Assertion provider     1.0
     DIA     WebLogic Identity Assertion provider     1.0
     AD     Provider that performs LDAP authentication     1.0 (Active Directory provider)
     Default     WebLogic Authentication Provider     1.0
h2. 8.2 -> Change the default parameters
h3. 8.2.1 Negotiate     WebLogic Negotiate Identity Assertion provider
-> Base64 Decoding Required: false (No Change, but shouldn't it be true and how to change?)
-> Form Based Negotiation Enabled: Removed the tick
h3. 8.2.2 DIA     WebLogic Identity Assertion provider (no changes)
(no changes)
h3. 8.2.3 AD     Provider that performs LDAP authentication (Active Directory provider)
-> Control Flag: *SUFFICIENT*
-> User Name Attribute: *sAMAccountName*
-> Principal: *HTTP/[email protected]*
-> Host: *192.168.1.193*
-> User Base DN: *CN=Users,DC=example,dc=com*
-> Propagate Cause For Login Exception: *ticked*
-> Group Base DN: *CN=Users,DC=example,dc=com*
-> Credential: *password1*
* others left with their default values.
h1. 9. Configuring an Internet Explorer Browser
On Windows XP machine (winclient.example.com):
h2. 9.1 Configure Local Intranet Domains
- In Internet Explorer, Tools > Internet Options -> the Security tab -> Local intranet -> Sites:
> "Include all sites that bypass the proxy server" *ticked*
> "Include all local (intranet) sites not listed in other zones" *ticked*
- then in -> Advanced Dialog Box added this:
> weblogic.example.com
h2. 9.2 Configure Intranet Authentication
- In Internet Explorer, Tools > Internet Options -> the Security tab -> Local intranet -> Custome Level:
> In the Security Settings dialog box -> the User Authentication section.
> "Automatic logon only in Intranet zone" *ticked*
h2. 9.3 The Proxy Settings
No proxies are enabled
h2. 9.4 Enable Integrated Windows Authentication
- In Internet Explorer, Tools > Internet Options -> Advanced tab -> Security section:
> "Enable Integrated Windows Authentication" *ticked* by default
Edited by: Mehdi Sarmadi on Sep 4, 2009 5:51 AM

I found something in Logfile:
<Sep 4, 2009 6:17:39 PM IRDT> <Debug> <SecurityAtn> <BEA-000000> <LDAP Atn Login username: weblogicusr>
<Sep 4, 2009 6:17:39 PM IRDT> <Debug> <SecurityAtn> <BEA-000000> <new LDAP connection to host 192.168.1.193 port 389 use local conne
ction is false>
<Sep 4, 2009 6:17:39 PM IRDT> <Debug> <SecurityAtn> <BEA-000000> <created new LDAP connection LDAPConnection { ldapVersion:2 bindDN:
""}>
<Sep 4, 2009 6:17:39 PM IRDT> <Debug> <SecurityAtn> <BEA-000000> <connection failed netscape.ldap.LDAPException: error result (49);
80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece^@>
<Sep 4, 2009 6:17:39 PM IRDT> <Debug> <SecurityAtn> <BEA-000000> <[Security:090294]could not get connection>
According to this post: Re: WL10.3 and SSO and Active Directory
a correct ldap connection should look like this:
<LDAP Atn Login username: Administrator>
<userExists? user:Administrator>
<new LDAP connection to host 10.10.0.254 port 389 use local connection is false>
<created new LDAP connection LDAPConnection { ldapVersion:2 bindDN:""}>
<connection succeeded>
*<getConnection return conn:LDAPConnection {ldaps://10.10.0.254:389 ldapVersion:3 bindDN:"HTTP/[email protected]"}>
<getDNForUser search("CN=Users,DC=DOMAIN,dc=local", "(&(&(cn=Administrator)(objectclass=user))(!(userAccountControl:1.2.840.113556.1.4.803:=2)))", base DN & below)>xist>*
Moreover, I turned AD's debug logging and this is what happens when I try to login with a AD user: Why "Anonymous Logon"?!
Event Type:     Information
Event Source:     NTDS LDAP
Event Category:     LDAP Interface
Event ID:     1535
Date:          9/4/2009
Time:          6:47:07 PM
User:          NT AUTHORITY\*ANONYMOUS LOGON*
Computer:     DC
Description:
Internal event: The LDAP server returned an error.
Additional Data
Error value:
80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece
Any help would be greatly appreciated

NT Authentication in Weblogic 6 with Windows 2000

Has anyone had success getting the Ntrealm running on W2K with weblogic 6sp1?
I set everything up according to the 6.0 docs (descibed below) and when I access
my web application (that i'm protecting) the login prompt doesn't accept my NT
login, but roles over to the fileRealm(weblogic realm), If I create the same
login there (but say with a different password just to be sure which is which,
I get accepted).
Here's how I went about it:
1) Installed WebLogic 6sp1 to run as an NT service on W2K Server sp1. Running
as the local system account.
2) Created an NTrealm (myNTRealm), set primary domain to the name of the W2k server
(myServer), since i'm going to use a local nt account (testAccount, password=nt)
to try and login. (also created a fileRealm login testAccount, password=weblogic)
3) Created a Caching realm for the NTrealm (myNTCacheRealm), turned off Case-sensitive
cache.
4) Created a web application(testApp) with a single JSP file (test.jsp).
5) Entered the following into the web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<display-name>testApp</display-name>
<description>NTrealm security testing app</description>
<servlet>
<servlet-name>Test</servlet-name>
<jsp-file>test.jsp</jsp-file>
</servlet>
<security-constraint>
<web-resource-collection>
<web-resource-name>EntireApp</web-resource-name>
<description>Secures the entire Application</description>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<description>Roles valid for entire site</description>
<role-name>secureUsers</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>basic</auth-method>
<realm-name>myNTRealm</realm-name>
</login-config>
<security-role>
<description>Web app security role</description>
<role-name>secureUsers</role-name>
</security-role>
</web-app>
6) And the following into the weblogic.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 2.2//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
<weblogic-web-app>
<description>WebLogic Deployment Descriptor</description>
<security-role-assignment>
<role-name>secureUsers</role-name>
<principal-name>testAccount</principal-name>
</security-role-assignment>
</weblogic-web-app>
7) Everything deploys fine and when I point my browser to http://myServer:7003/testApp/test.jsp.
The login prompt has:
Site: myServer
Realm: myNTRealm
but the server doesn't accept my NT login+password testAccount+nt, but I can
entered the weblogic login+password testAccount+weblogic and got in.
Any ideas? I've spent just about all the time I care to on this one.

"Barrett" <[email protected]> wrote:
>
Has anyone had success getting the Ntrealm running on W2K with weblogic
6sp1?
I set everything up according to the 6.0 docs (descibed below) and when
I access
my web application (that i'm protecting) the login prompt doesn't accept
my NT
login, but roles over to the fileRealm(weblogic realm), If I create
the same
login there (but say with a different password just to be sure which
is which,
I get accepted).
Here's how I went about it:
1) Installed WebLogic 6sp1 to run as an NT service on W2K Server sp1.
Running
as the local system account.
2) Created an NTrealm (myNTRealm), set primary domain to the name of
the W2k server
(myServer), since i'm going to use a local nt account (testAccount, password=nt)
to try and login. (also created a fileRealm login testAccount, password=weblogic)
3) Created a Caching realm for the NTrealm (myNTCacheRealm), turned off
Case-sensitive
cache.
4) Created a web application(testApp) with a single JSP file (test.jsp).
5) Entered the following into the web.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application
2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<display-name>testApp</display-name>
<description>NTrealm security testing app</description>
<servlet>
<servlet-name>Test</servlet-name>
<jsp-file>test.jsp</jsp-file>
</servlet>
<security-constraint>
<web-resource-collection>
<web-resource-name>EntireApp</web-resource-name>
<description>Secures the entire Application</description>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<description>Roles valid for entire site</description>
<role-name>secureUsers</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>basic</auth-method>
<realm-name>myNTRealm</realm-name>
</login-config>
<security-role>
<description>Web app security role</description>
<role-name>secureUsers</role-name>
</security-role>
</web-app>
6) And the following into the weblogic.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application
2.2//EN"
"http://www.bea.com/servers/wls600/dtd/weblogic-web-jar.dtd">
<weblogic-web-app>
<description>WebLogic Deployment Descriptor</description>
<security-role-assignment>
<role-name>secureUsers</role-name>
<principal-name>testAccount</principal-name>
</security-role-assignment>
</weblogic-web-app>
7) Everything deploys fine and when I point my browser to http://myServer:7003/testApp/test.jsp.
The login prompt has:
Site: myServer
Realm: myNTRealm
but the server doesn't accept my NT login+password testAccount+nt, but
I can
entered the weblogic login+password testAccount+weblogic and got in.
Any ideas? I've spent just about all the time I care to on this one.
Have you specified the Cacheing Realm on the Security tab?
i.e. Change it from '(none)' to 'myNTCacheRealm'

JSTL 1.1 issue with Weblogic 9.2

I am having tough time to make JSTL 1.1 work with Weblogic 9.2.Here the issue goes
When i user JSTL core tags like out,forEach weblogic is unable to understand the EL and throwing a compile time exception saying can't read request time values.
However the same page worked fine when i rolled back to JSTL 1.0 and weblogic 8.1.
I couldnt able to understand why JSTL 1.1 is not working in Weblogic 9.2.I assume weblogic 9.2 comes with servlet 2.4 and JSP 1.2.So JSTL 1.2 should work fine.
Am i ignoring anything involved with new JSP specs and JSTL
OR
Is this a bug with Weblogic 9.2 ?
Any comments highly appreciated.
Thanks,
Mallik

hey check the servlet spec version you're using in your web.xml. I think you want 2.3 not 2.4.

Memory Leak with Weblogic 6.1

Hello everyone.
I need some help with a problem we are having with our application. It consists on Servlets, JMS with MDBs, Xml parsing...
Our application dequeues messages from an Oracle Queue and sends xml-text message to a servlet. It also receives xml-text and enqueues objects in an Oracle Queue.
And it also has access to Oracle Database (context tables, etc).
We are doing everything on Tru64 Unix (and our tests on Win 2000) and we are using WebLogic 6.1.
Our problem is that we have found that it seems that the garbage collector is not running well. I mean, with the time our system is degrading. The memory use increases. It seems to be a memory leak.
We have used a testing tool, OptimizeIt, and we have found that there are
objects that are increasing the use of memory. If we use the option 'java -verbose' we find that it seems to be Hash objects (HashMap, Hashtable) which are increasing the use of memory. In our code we are not using any hashtable nor any class that extends from it (we have deleted everyone).
Can it be due to a problem with WebLogic? A problem with JMS, queues, etc? A problem with JNDI?
Could anybody please help us?
Thanks in advanced.

Yes, we see that there are some entries of the type:
java/util/Hahstable$Entry
java/util/Hahstable
weblogic/jndi/Environment
This entries keep growing and growing with the time.
We have deleted all the Hashtable, Properties and all the kind of Collection objects. I guess WebLogic is using this objects in order to arrange our application runs.
Am I right? Do you know if we can do anything?
Thank you.

Iplanet LDAP with Weblogic

Hello All,
I forgot the subject line. I'm trying to set up iPlanet Directory 4.1 with
WebLogic 5.1 Sp3 on Solaris7. Weblogic will see the users I specify
(username,groupname) but not
the group, additionally it will allow you to login if you know the
username and anypassword. I get the following error when loading the
http://localhost:port/AdminRealm. I've gone through the LDAP
properties file a million times. Lastly, now it does a core - dump
while trying to start.
Please help.
Richard
################# Begin Error ###############################3
java.lang.NullPointerException
at weblogic.security.ldaprealm.LDAPDelegate.magicBunny(Compiled Code)
at weblogic.security.ldaprealm.LDAPDelegate.addGroupMember
(Compiled Code)
at weblogic.security.ldaprealm.LDAPDelegate.getGroupMembers
(Compiled Code)
at weblogic.security.ldaprealm.LDAPDelegate.getGroupMembers
(LDAPDelegate.java:518)
at weblogic.security.ldaprealm.LDAPRealm.getGroupMembersInternal
(LDAPRealm.java:81)
at weblogic.security.acl.AbstractListableRealm.getGroupMembers
(AbstractListableRealm.java:302)
at weblogic.security.acl.FlatGroup.ensureFreshness
(FlatGroup.java:149)
at weblogic.security.acl.FlatGroup.members(FlatGroup.java:236)
at admin.AdminRealm.composePage(Compiled Code)
at admin.AdminServlet.service(AdminServlet.java:257)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865) at
weblogic.servlet.internal.ServletStubImpl.invokeServlet
(ServletStubImpl.java:123)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet
(ServletContextImpl.java:744)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet
(ServletContextImpl.java:692)
at weblogic.servlet.internal.ServletContextManager.invokeServlet
(ServletContextManager.java:251)
at weblogic.socket.MuxableSocketHTTP.invokeServlet
(MuxableSocketHTTP.java:363)
at weblogic.socket.MuxableSocketHTTP.execute
(MuxableSocketHTTP.java:263)
at weblogic.kernel.ExecuteThread.run(Compiled Code)

I have the same requirement too. I have been looking at many sources and havent
come across any that mentions anything related to this. If you come across anything
please do let me know.
Regards
Vijay
"Licheng" <[email protected]> wrote:
>
I also face the similar problem. In our case, one of the business requirements
for the authentication process is that when a user is authenticated,
but his password
expires, the system should force the user to change password.
With JAAS and WebLogic 7.0, I don't know the standard or "preferred"
approach
to this problem
regards
Licheng

Integrating Weblogic Portal with Oracle BPMS

Hello,
I need to integrate the Weblogic Portal with the OBPMS, but i need to show only the portlet with the work list. Anyone here already did something like this ?
I have a tutorial at Oracle with that but in this document says that i need to :
Add the following portlets by dragging and dropping them from the Design Palette View:
Menu Action
Work List
Instance Detail
The tutorial is :
http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html?t=modules/enterprise/wlp/t_WLP_Config_Overview.html
But i need to show only the worklist , its possible ?
the section with the portlets is : http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html?t=modules/enterprise/wlp/t_WLP_Config_Overview.html

Here's my thoughts on how I think this works. I think you need to have an Authentication Provider or Identity Asserter that plugs into the WLS Security Provider framework that understands the Oracle Access Manager provided token (or whatever mechanism OAM is using to pass the user credentials). That piece will be responsible for creating the principal and groups in the WLS security framework. In WLP, you use Visitor Entitlement Roles to secure things like portlets. The visitor entitlements roles can be defined by many attributes (user profile, date time, request, etc). One of which is the groups that the Authorization Provider or Identity Asserter reports. You might want to post this in the WebLogic Portal forum as well.

Problems with weblogic clustering in 6.1 sp3

We have spent a lot of time trying to get our application deployed to
          a cluster using weblogic 6.1 sp3 and we consistently receive a failure
          when we attempt to start the managed server. This was not a problem
          with weblogic sp1--we got our application to deploy to the cluster
          successfully; although there was another weblogic bug there with
          clients accessing EJB clusters--we won't go into that here...
          We have tried this on both a Windows 2000 machine and an HP machine
          running weblogic sp3. The same error occurs on both platforms.
          The error in deploying our application to the cluster against weblogic
          sp3 looks to have to do with our custom security realm. Inside our
          custom realm we make use of a configurable providerUrl which we set to
          the cluster address/port. The custom realm makes a call where it
          passes in the providerUrl to:
               weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
          When we have our providerUrl set to the cluster address/port--e.g.,
               t3://clustermember1:7001
          and attempt to start the managed server we get the error:
          Starting WebLogic Server ....
          Connecting to http://adminserver:7117...
          The WebLogic Server did not start up properly.
          Exception raised:
          weblogic.management.configuration.ConfigurationException:
          clustermember1 not found
               at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
               at weblogic.management.Admin.initialize(Admin.java:340)
               at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
               at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          When we have our providerUrl set to the admin server address--e.g.,
               t3://adminserver:7117
          everything starts up fine.
          Does anyone know why this would work on sp1 and not sp3 of weblogic
          6.1?
          We verified that all passwords are correct and everything else we
          could determine--any ideas would be helpful.
          We don't want the providerUrl to point at our admin server, we want it
          to point at the cluster address/port.
          When we get the managed server error, we received this error on the
          AdminServer:
          2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
          'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
          Caught naming exception null; throwing RuntimeException.
          javax.naming.CommunicationException. Root exception is
          java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
          unreachable; nested exception is:
               java.net.ConnectException: Connection refused; No available router to
          destination
               at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
               at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
               at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
               at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
               at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
               at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
               at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
               at javax.naming.InitialContext.init(InitialContext.java:222)
               at javax.naming.InitialContext.<init>(InitialContext.java:198)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
               at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
               at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
               at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
               at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
               at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
          <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
          Servlet failed with Exception
          java.lang.RuntimeException
               at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
               at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
               at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
               at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
               at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
               at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Thanks for any help.
          Rich


Bottom line:
          In our custom realm we were not handling user guest correctly. Even if you
          have guest user disabled, Weblogic seems to have hard-coded guest to
          send messages to the cluster every-so-often. Not sure there--couldn't get
          an answer out of bea as to exactly why we see guest still being used...
          It seems that with sp3, the user guest interaction started happening earlier
          than it did with sp1, consequently making our realm code fail when trying to
          retrieve the guest user like someone we knew about in our system.
          Hence, our getUser and authUserPassword methods now return null for both
          users guest and system, making the secondary realm (file realm) be used to
          authenticate and resolve guest & system. BEA helped get our code fixed;
          however, we still don't have a lot of depth in understanding Weblogic
          server's use of guest...
          Apparently, in 7.x the guest & system user behavior and configuration is
          different also... We'll see when we start digging into that migration.
          Rich
          [email protected] (Rich Koch) wrote in message news:<[email protected]>...
          > Thanks for the responses--we're working with weblogic support now. We
          > think that the custom realm that we have [the developer that wrote it
          > left the company] is the problem.
          >
          > The original developer was told by someone to check:
          > weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
          >
          > In order to determine if the JNDI was available/ready for the whole
          > cluster.
          >
          > It seems that the meaning/setting of THE_ONE changed with this respect
          > from
          > sp1 to sp3--i.e., this is no longer a valid test to tell us if the
          > JNDI is
          > ready for the cluster.
          >
          > We believe this was used because the 'system' user has to be
          > authenticated before the custom realm is up. Originally, before this
          > check was in place, an exception was received when authenticating
          > 'system'. This appears to be a weblogic limitation/issue. Support
          > has told us that this is different in weblogic 7.0. Unfortunately, we
          > can't upgrade from 6.1 yet.
          >
          > We'll post the solution when this gets figured out.
          >
          > Rak
          >
          > "Sabha" <[email protected]> wrote in message news:<[email protected]>...
          > > There was a security restriction enforced from sp2/sp3 onwards in terms of
          > > looking up mbeans from admin server.
          > >
          > > This might cause things to fail if you are attempting to lookup Mbeans with
          > > guest priviliges from admin server. Also, can you try doing the following:
          > >
          > > Run " java weblogic.Admin -url adminServer -username system -password
          > > .... -GET -pretty -type Server" and check whether the named clustermember1
          > > is available in the list or not.
          > >
          > > Also you seem to be getting some security exception - can you check that.
          > >
          > > t3://tomtate.msais.com:7119: Destination
          > > unreachable; nested exception is:
          > >
          > > --- Try running weblogic.Admin PING on this one and see whether you are
          > > able to reach this server upon the error message.
          > >
          > > --Sabha
          > >
          > > "Rich Koch" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > We have spent a lot of time trying to get our application deployed to
          > > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
          > > > when we attempt to start the managed server. This was not a problem
          > > > with weblogic sp1--we got our application to deploy to the cluster
          > > > successfully; although there was another weblogic bug there with
          > > > clients accessing EJB clusters--we won't go into that here...
          > > >
          > > > We have tried this on both a Windows 2000 machine and an HP machine
          > > > running weblogic sp3. The same error occurs on both platforms.
          > > >
          > > > The error in deploying our application to the cluster against weblogic
          > > > sp3 looks to have to do with our custom security realm. Inside our
          > > > custom realm we make use of a configurable providerUrl which we set to
          > > > the cluster address/port. The custom realm makes a call where it
          > > > passes in the providerUrl to:
          > > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
          > > >
          > > > When we have our providerUrl set to the cluster address/port--e.g.,
          > > > t3://clustermember1:7001
          > > >
          > > > and attempt to start the managed server we get the error:
          > > >
          > > > Starting WebLogic Server ....
          > > > Connecting to http://adminserver:7117...
          > > >
          > ***************************************************************************
          > > > The WebLogic Server did not start up properly.
          > > > Exception raised:
          > > > weblogic.management.configuration.ConfigurationException:
          > > > clustermember1 not found
          > > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
          > > > at weblogic.management.Admin.initialize(Admin.java:340)
          > > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
          > > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
          > > > at weblogic.Server.main(Server.java:35)
          > > > Reason: Fatal initialization exception
          > > >
          > ***************************************************************************
          > > >
          > > > When we have our providerUrl set to the admin server address--e.g.,
          > > > t3://adminserver:7117
          > > >
          > > > everything starts up fine.
          > > >
          > > > Does anyone know why this would work on sp1 and not sp3 of weblogic
          > > > 6.1?
          > > > We verified that all passwords are correct and everything else we
          > > > could determine--any ideas would be helpful.
          > > >
          > > > We don't want the providerUrl to point at our admin server, we want it
          > > > to point at the cluster address/port.
          > > >
          > > > When we get the managed server error, we received this error on the
          > > > AdminServer:
          > > >
          > > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
          > > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
          > > > Caught naming exception null; throwing RuntimeException.
          > > > javax.naming.CommunicationException. Root exception is
          > > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
          > > > unreachable; nested exception is:
          > > > java.net.ConnectException: Connection refused; No available router to
          > > > destination
          > > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
          > > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
          > > > at
          > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:307)
          > > > at
          > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
          > > textFactoryDelegate.java:211)
          > > > at
          > > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
          > > ory.java:149)
          > > > at
          > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
          > > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
          > > > at javax.naming.InitialContext.init(InitialContext.java:222)
          > > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
          > > Realm.java:416)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
          > > lm.java:347)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
          > > java:51)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
          > > 225)
          > > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
          > > Realm.java:578)
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
          > > a:221)
          > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
          > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
          > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
          > > > at
          > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
          > > ava:356)
          > > > at
          > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          > > tSecurityManager.java:205)
          > > > at
          > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          > > ntext.java:2518)
          > > > at
          > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          > > :2260)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
          > > >
          > > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
          > > al2)]
          > > > Servlet failed with Exception
          > > > java.lang.RuntimeException
          > > > at
          > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
          > > a:260)
          > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
          > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
          > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
          > > > at
          > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
          > > ava:356)
          > > > at
          > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
          > > tSecurityManager.java:205)
          > > > at
          > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
          > > ntext.java:2518)
          > > > at
          > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
          > > :2260)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > >
          > > >
          > > > Thanks for any help.
          > > >
          > > > Rich

How to implement the security in web service with Weblogic 9.2

I've generated web service by Web Logic 9.2 using existing WSDL (as per client requirement) and want to add security policy for authentications.
I have used following annotation in service class.
@Policies({
@Policy(uri="policy:Auth.xml" , direction=Policy.Direction.inbound)
But it gives compilation time error with following message.
The Policy and Policies annotations are not allowed on jws file when compiledWsdl option is specified
I've also tried to modify the WSDL to accommodate policy configuration and again generate the web service but problem is being as it is.
If anybody has solution of this issue then please let me know ASAP.

Did you get an answer to your question? I have the same problem with WebLogic 10.0.

HOWTO: Monitoring WebLogic Server with Hyperic HQ

For those of you that administer WebLogic Server deployments, you may be interested in this HOWTO - it demonstrates how to get up and running monitoring your WebLogic deployments with Hyperic HQ. HQ auto-discovers WebLogic instances, thus shortening your time to deployment and delivering WebLogic metrics in minutes.
To read the article:
http://support.hyperic.com/confluence/display/hypcomm/Monitoring+Weblogic+with+HQ
Download the open source (GPL) HQ:
http://www.hyperic.com/downloads/other-register.jsp?product=hqfree
Enjoy!
John Mark

can any one in the community please help for sorting out this issue.
I have been with this error for a long time.

Stylesheet error with weblogic application server 9.1

Hi ALL,
I deployed my application on weblogic AS 9.1.
i have created my own domain using sun JDK 1.5.
i am able to log in into my application & able to do all the tasks.
but when i click on a specific tab weblogic AS 9.1 waits for some time & give this error on its console :-
<b>ERROR: 'Variable 'can-modify' is multiply defined in the same scope.'
FATAL ERROR: 'Could not compile stylesheet'</b>
i am not find any more details in the weblogic server error log.
the same application works fine with weblogic 8.1 sp4 + jdk 1.4 & tomcat 5.0.27 + jdk 1.5( without any error)
so i think the problem is not because of jdk, it something to do with weblogic!
does anybody has info about this.
it will be great help.
regards
Rahul

I found that error is coming from this line.
<b><xsl:variable name="can-modify" select="/dashboard/@can-save|/dashboard/@can-saveas" /></b>
can somebody suggest why this happening, same code works is weblogic 8.1 & give error in 9.1.
-Rahul

Weblogic singleto with weblogic timer

Similar Messages

Maybe you are looking for