Excessive LDAP Queries from WLS 6.0 SP2 RP3

We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/2002 17:46:45
#167070
WLS has been configured to query an LDAP server for user authentication. The issue
we are experiencing is that WLS performs the LDAP query on EVERY page load in
the application. This is resulting in excessive calls to the LDAP server, and
increased response times.
We have attempted to change the caching realm settings such that the cache is
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing the excessive
calls? How can we reduce the number of calls?
thanks
Bavini

"Bavini Naidoo" <[email protected]> wrote in message
news:3fc741c1$[email protected]..
>
We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/200217:46:45
#167070
WLS has been configured to query an LDAP server for user authentication.The issue
we are experiencing is that WLS performs the LDAP query on EVERY page loadin
the application. This is resulting in excessive calls to the LDAP server,and
increased response times.
We have attempted to change the caching realm settings such that the cacheis
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing theexcessive
calls? How can we reduce the number of calls?
Turn on weblogic.security.ldaprealm.verbose and see if the debugging output
indicates
the operation that the ldap realm is performing.

Similar Messages

Calling db2 stored procedures from wls 8.1 sp2

Hi,
We noticed strange behaviour when moving customers applications from wls 6.1 to 8.1 sp2. We have a use case where we call db2 stored procedure two times (same prcedure) to make inserts to a database. The first time when procedure is called, everything goes smoothly but at the second time db2 claims that statement is not prepared and gives us sql error sql0518n.
We do see this error only if we use wls prepared statement cache and without cache (size=0) everything seems to work. We also did some db2 level tracing and noticed that statement is not prepared when using wls cache and db2 cannot execute statement which is not prepared....
Why I'm asking this? because this is the first time I had disable wls cache. We have used it and even optimized software performance using prepared statement cache in several projects before this.
Procedure call is done from web container lavel and no EJBs is used. We have tested the use case using autommit option and also committed firts transaction manually and closed connection.
We are using DB2 8.2 fp7 as a database and IBM level 2 JDBC driver without XA support. Honor global transactions support is on at a datasource.
Is this normal behaviour? Db2 problem or maybe WLS problem?
Regards,
Mika

I am getting the same exception about an assertion failed at weblogic.t3.srvr.T3Srvr.checkServerLock. Any ideas?

URGENT: external LDAP configuration from WLS 6.1

Hi,
I am trying to configure the LDAP Realm(Netscape directory server) for Weblogic
Server6.1. For any user to perform a bind
on my Directory Server it needs CN + serial number. But the Users actually don't
know all this and they use LoginID (which is unique in LDAP) in Login Screens.
How do I configure the
BEA server or how do I achieve this (please listout the steps).
DO I need to write a custom realm?
Thanks in Advance,
Srinivas

Hi,
I am trying to configure the LDAP Realm(Netscape directory server) for Weblogic
Server6.1. For any user to perform a bind
on my Directory Server it needs CN + serial number. But the Users actually don't
know all this and they use LoginID (which is unique in LDAP) in Login Screens.
How do I configure the
BEA server or how do I achieve this (please listout the steps).
DO I need to write a custom realm?
Thanks in Advance,
Srinivas

Re: WLS 6.0 SP2 hangs due to many sockets in CLOSE_WAIT state

We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000 platform.
Currently we are using running some stablity tests and noticing that there are
lot of sockets in close_wait state and handle count keeps going up and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay as suggested
in this newsgroup, and we are still noticing this problem. Does any body have
the same issue?. is this a know problem with weblogic http server?. and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

BEA acknowledges this problem in 6.0 SP2 with iPlanet plug-in.
Solution that they recommend is to use 6.1 SP2 plug-in (they claim
full compatibility). Also, you may have to set KeepAliveEnabled to
false in obj.conf (the problem is in wrong pooling).
Hope it helps,
Bala
Robert Patrick <[email protected]> wrote in message news:<[email protected]>...
There are a couple of issues.
1.) You need to tune the machine running the web server and the machine
running WebLogic to make sure that it is configured appropriately for a
high-volume HTTP server. See
http://e-docs.bea.com/wls/platforms/sun/index.html for details on tuning
Solaris.
2.) I believe that there is a bug in the plugins in 6.0 where it is not
properly closing sockets. Try using the plugin from WLS 6.1 SP2...
Hope this helps,
Robert
Kevin Phillips wrote:
Tim Funk <[email protected]> wrote:
I am experiencing similar problems with WL 6.0 SP2 on Solaris 2.6.
We are already proxying all HTTP traffic through a
cluster of apache servers. Unfortuantely, the apache-WL
bridge seems to work so efficiently that our servers are
still flooded with open sockets in the TCP_CLOSE_WAIT state.
It seems to be bound by WebLogic's capacity to respond to
the requests in a speedy enough fashion.
Anybody have any suggestions?
Kevin
We have the same issue with HPUX and Weblogic 5.1 SP8. In fact, we get
errors on the ListenThread because occasionally it (the ListenThread)
says too many files open. Running a monitoring tool - the process
typically only has ~130 file handles open at any time. When we start
getting a lot of sockets "stuck" in close_wait state the number of open
files increases dramatically occasionally freezing the server until (I
believe) the OS steps in and cleans house.
For those curious, our box is configured to have a max of 1024 files
open. Please don't even suggest that we raise that parameter because
it
is already high enough.
We are tempted to use apache as the webserver and proxy request through
apache to weblogic. Apache doesn't suffer from this issue AFAIK.
-Tim
sogal nagavardhan wrote:
Hi !!
We are using weblogic 6.0 SP2 with jdk1.3.1 running on windows 2000
platform.
Currently we are using running some stablity tests and noticing that
there are
lot of sockets in close_wait state and handle count keeps going up
and eventually
crashes the weblogic. We also tried reducing the TcpTimedWaitDelay
as suggested
in this newsgroup, and we are still noticing this problem. Does any
body have
the same issue?. is this a know problem with weblogic http server?.
and finally
any fixes or workarounds to this issue.
Thanks
Sogal.N

ERROR: Error from ejbc: in WLS 6.1 sp2 Win2K

Never had this problem before. Started new project using WLS 6.1 sp2 under Windows
2K Prof., using ANT & get;
ERROR: Error from ejbc:
In EJB NOTiFYEJB, method createUser defined in the remote interface either does
not exist in the bean class, or it is not a public method. Each method in the
remote interface must have a corresponding public method in the bean class.
BUILD FAILED
I saw a posting which referred to a problem with Win2K & an old (1.2) JDK in the
path. I have put C:\bea\jdk131 at the front of my class path but still get this
error.

The problem was nothing to do with classpaths etc.
CMP does not support "Date" types and in my EJB I had Date types, I changed these
to "long" and converted all Dates to number of milleseconds from 1970 and persisted
them to a number column in Oracle.
It was the entries in the weblogic-cmp-rdbms.xml which was the root of the problem.
"Roger Lee" <[email protected]> wrote:
>
Matthew,
Thanks for yor suggestions.
My classpath is set in the ANT.BAT & only points to the tools.jar, weblogic_sp.jar
& weblogic.jar.
I have my JARs in a manfest file in each directory with the "Class-Path:"
entry.
I have also added a new Bean with compiles & ejbcs fine. But I still
get an error
with my "createUser" method, saying the interface does not exist in the
bean class
or is not a public method.
I have even changed it's name to "createUserCandidate" just in case it
was clashing
with an existing method.
Any other ideas for investigation?
Thanks.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Roger Lee wrote:
The "warnings saying classes are being loaded from your classpath"are, I believe
just warning from Ant. I searched the newsgroups and it appears thatthis is not
a problem.These warnings are from ejbc. They are there to let you know that classes\interfaces
needed by your EJB are being loaded from your classpath and not your
jar. They
should be taken seriously. This could definitely be the cause of your
problem. As I
said in my previous posting, ejbc could be loading an old version of
your bean class
from your classpath. This old class may not contain the createUsermethod
with the
same signature as the method in your remote interface.
Is this an issue with WLS 6.1 sp2?I don't believe so.
I've wasted so much time on this any help would be appreciated.You essentially have three options.
1. Take my advice and make sure your classes are being loaded fromyour
jar and not
the classpath.
2. Post your entire jar so we can try to reproduce the problem.
3. Contact support.
- Matt
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Your bean and interface look fine. One thing you might try is explicitly
declaring
your createUser method to be public in your remote interface. I
don't
think this
will change the outcome but it's worth a try. When you run ejbcdo
you
get any
warnings saying classes are being loaded from your classpath ratherthan
your jar?
If this were the case, you could have an old copy of your bean inyour
classpath
that ejbc is picking up. If this doesn't help, I think the next
step
is to send me
or post your entire jar.
- Matt
Roger Lee wrote:
Typo that should have been "path", I had added "C:\bea\jdk131"
to
the
front of
my path & was getting the error.
Enclose my two classes in the attached file.
Thanks for you help.
Matthew Shinn <[email protected]> wrote:
Hi Roger,
Make sure you put C:\bea\jdk131 in front of your path (not classpath).
:) Assuming
this isn't the problem, can you please post any createUser method
declarations
in your
remote interface and the corresponding createUser methods in yourbean
class?
- Matt
Name: NOTiFY_&_NOTiFYBean.java
NOTiFY_&_NOTiFYBean.java Type: java/*
Encoding: base64

LDAPRealm Failover in WLS 6.0 SP2

We have WLS 6.0 SP2 using a Netware LDAP server to authenticate. Given recent problems with the LDAP server, we have to build in failover capability. As far as I know 6.0 does not support failover for LDAP. Is there any way around this apart from building another jar file? We want to avoid having to manually restart the weblogic server each time with different config setting.
thanks
Bavini

We have WLS 6.0 SP2 using a Netware LDAP server to authenticate. Given recent problems with the LDAP server, we have to build in failover capability. As far as I know 6.0 does not support failover for LDAP. Is there any way around this apart from building another jar file? We want to avoid having to manually restart the weblogic server each time with different config setting.
thanks
Bavini

Problem starting wls 6.1 sp2

Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server

Hi.
Try placing the wl_management_internal2.war file from the mydomain/.wlstaging directory into the directory your server is expecting.
Regards,
Michael
Peter Buus wrote:
Hi
I have developed an appliaction using wls 6.1 sp2 on w2k, which I want to migrate
to Solaris 8.
I have modified my windows statup scripts to Solaris, but I get a strange error
when starting weblogic. I am starting the server as root and my weblogic.policy
file is modified according to my installation.
Has anybody encountered anything similar?
<Feb 20, 2002 12:08:09 PM CET> <Critical> <Management> <Unable to deploy an internal
management web application - <all-internal-apps>. Managed servers may be unable
to start.
java.io.FileNotFoundException: ./config/Certifikat/.wlstaging/wl_management_internal2.war
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
at java.io.FileOutputStream.<init>(FileOutputStream.java:62)
at java.io.FileOutputStream.<init>(FileOutputStream.java:132)
at weblogic.management.mbeans.custom.ApplicationManager.stageGlobalWarFile(ApplicationManager.java:398)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:334)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:152)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:606)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:590)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:350)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:444)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:185)
at $Proxy35.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:479)
at weblogic.management.Admin.startApplicationManager(Admin.java:1138)
at weblogic.management.Admin.finish(Admin.java:561)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:501)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:198)
at weblogic.Server.main(Server.java:35)
>
My startup script is as follows
bash-2.03$ more startWeblogic.sh
#!/usr/bin/bash
# Set user-defined variables.
export PROJECT=postdanmark
export ENVIRONMENT=test
export RELEASE_DIR=/opt/projects/$PROJECT/$ENVIRONMENT/lib
export JAVA_HOME=/opt/jdk/j2sdk1_3_1_02
export WEBLOGIC_HOME=/opt/bea/weblogic/6.1
export PATH=$WEBLOGIC_HOME/bin:$JAVA_HOME/jre/bin:$JAVA_HOME/bin:.:$PATH
export CLASSPATH=$RELEASE_DIR/internal/util/1.0/Util.jar
export CLASSPATH=$CLASSPATH:$WEBLOGIC_HOME/lib/weblogic.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/sun/jaxb/1.0ea/lib/jaxb-rt-1.0-ea.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/postdanmark/1.0/PostDanmarkPC.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/EntrustCAEjb/1.0/EntrustCAEjb.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/websupport/1.0/WebSupport.jar
export CLASSPATH=$CLASSPATH:/opt/projects/$PROJECT/$ENVIRONMENT/batch/properties
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/internal/corba/interfaces/entrustca/1.2/EntrustCA.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/mysql/jdbc/2.0.4/mm.mysql-2.0.4-bin.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entbase.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entuser.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entp7.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entmisc.jar
export CLASSPATH=$CLASSPATH:$RELEASE_DIR/external/entrust/java_toolkit/6.0/lib/application/entcertlist.jar
echo off
echo *********************************************
echo * Starting weblogic application server *
echo *********************************************
# Set WLS_PW equal to your system password for no password prompt server startup.
export WLS_PW=certifikat
# Set Production Mode. When set to true, the server starts up in production mode.
When set to false, the server starts up i
n development mode. The default is false.
export STARTMODE=false
export WEBLOGIC_OPTIONS='-Dweblogic.Domain=Certifikat'
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.Name=PostDanmarkServer"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.discover=false"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dbea.home=/opt/bea/weblogic/6.1"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.home=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Duser.dir=/opt/projects/$PROJECTS/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.management.password=$WLS_PW"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.ProductionModeEnabled=$STARTMODE"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.security.policy=$WEBLOGIC_HOME/lib/weblogic.policy"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Dweblogic.RootDirectory=/opt/projects/$PROJECT/$ENVIRONMENT/weblogic"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.util.logging.config.file=/opt/projects/$PROJECT/$ENVIRONMENT/batch/proper
ties/logging.properties"
export WEBLOGIC_OPTIONS=${WEBLOGIC_OPTIONS}" -Djava.library.path=$WEBLOGIC_HOME/lib/solaris:$WEBLOGIC_HOME/lib/solaris/oci816
_8"
export JAVA_OPTIONS='-hotspot -ms64m -mx64m -classpath '
export JAVA_OPTIONS=${JAVA_OPTIONS}$CLASSPATH
echo on
echo "using JAVA OPTIONS : "$JAVA_OPTIONS"
echo "using WEBLOGIC OPTIONS : "$WEBLOGIC_OPTIONS"
"$JAVA_HOME/bin/java" $JAVA_OPTIONS $WEBLOGIC_OPTIONS weblogic.Server--
Michael Young
Developer Relations Engineer
BEA Support

Word 2013 - Publish as PDF or XPS button causes excessive registry queries / high CPU when added to quick access toolbar

After installing Office 2013 Pro Plus on our XenApp 6.5 environment we noticed a drop in performance. Using taskmanager we could see winword.exe hit 20+% CPU usage when filling just 1 line with the same letter.
Some investigating lead us to the "Publish as PDF or XPS button", when it is added to the quick access toolbar the cpu usage doubles during keystrokes. Using procmon I noticed excessive registry reading, up to 150,000 lines in 10 seconds.
It seems to be a constant loop of the same queries to approx. 100 components in HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\
I reproduced this in 3 different setups:
Win2008R2 + Office2013 Pro Plus 32-bit + Office 2013 updates until 12-nov 2014
Win 8.1 Laptop + Office2013 Pro Plus 32-bit + Office 2013 updates until 05-jan 2015
Win 8.1 Desktop + Office2013 Pro Plus 64-bit + Office 2013 updates until 17-dec 2014
Can anyone verify this behaviour? For now we've removed the shortcut from the quick access toolbar in our environment.
Here's a small portion of the queries.
19:22:49,7117781 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7117861 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D SUCCESS Desired Access: Read
19:22:49,7117969 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 130, Data: C:\?Program Files\Common
Files\Microsoft Shared\OFFICE15\MSO.DLL
19:22:49,7118058 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\1A89310DF62F54544A1465F790A7757D SUCCESS
19:22:49,7118154 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7118232 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20 SUCCESS Desired Access: Read
19:22:49,7118332 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 112, Data: C:\Program Files\Microsoft
Office\Office15\OUTLFLTR.DLL
19:22:49,7118415 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\837CF31208764B643868B58117357D20 SUCCESS
19:22:49,7118511 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7118586 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855 SUCCESS Desired Access: Read
19:22:49,7118694 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855\00005109110000000100000000F01FEC BUFFER OVERFLOW Length: 144
19:22:49,7118769 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 134, Data: C:\Program Files\Common
Files\Microsoft Shared\OFFICE15\FLTLDR.EXE
19:22:49,7118849 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\FDFFB7C3B3B7DA048B21B3A72D1BF855 SUCCESS
19:22:49,7118949 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7119023 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3 SUCCESS Desired Access: Read
19:22:49,7119123 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 100, Data: 20:\CLSID\{000C0126-0000-0000-C000-000000000046}\
19:22:49,7119203 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\BF574A30F66E6D54186C7F15B116E7A3 SUCCESS
19:22:49,7119295 WINWORD.EXE 1484 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
19:22:49,7119369 WINWORD.EXE 1484 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6 SUCCESS Desired Access: Read
19:22:49,7119466 WINWORD.EXE 1484 RegQueryValue HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6\00005109110000000100000000F01FEC SUCCESS Type: REG_SZ, Length: 128, Data: 22:\Software\Microsoft\Office\15.0\User
Settings\Mso_Core\Count
19:22:49,7119544 WINWORD.EXE 1484 RegCloseKey HKLM\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\017CCC9DE12773C4FAD559D2951B14C6 SUCCESS

I'll do that, I'm however still interested if somebody can confirm the excessive registry queries.
As a brief test, I captured winword.exe (2013) registry-reads on my Win8.1 pc (64bit Windows), with ProcMon.
this is over a capture period of less than one second
2092 of 2352 contain "component" in the reg path
this is when I have winword open and whilst "File, Export" is displayed (this is what offers the export-to-PDF option)
vs. 168 registry operations in an interval of 10 seconds, by winword.exe, if word is simply "running in background with an open blank document"
I'm not sure if that is useful, but it seems an awful lot of registry reads/writes from an application which isn't apparently doing anything at the time..
EDIT: similar registry read/write rate, when save-as-pdf is added to QAT (again sitting idle on a blank document). the registry read/write rate drops back down to 160 if the save-as-pdf feature is then removed from QAT.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Wls 8.1 sp2: weblogic.jspc complains about struts-html tags

          Hi,
          I am trying to compile jsps with weblogic.jspc, which use struts' html tags. However,
          the compilation fails with the following message:
          [java] Translation of /views/viewPageBody.jsp failed: (line 3): Error in using
          tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
          has no setter method corresponding to TLD declared attribute 'server', (JSP 1.1
          spec, 5.4.1)
          I opened the BaseTag class from the struts jar and found the setter exists for
          the attribute 'server' of html tld. So does the property 'server'. The property
          'server' is a string and the parameter in the setter is a string. I read about
          the jspc errors in wls 8.1 about the setter parameter being of different type
          than the property. However, that is not the case here. I tried using both Sun's
          and BEA's jdk. None of them help. Btw, there is another attribute mentioned in
          the html tld, which is 'target'. The compiler doesn't complain yet about this.:(
          Also, I happened to compile other apps which have struts logic tags.
          My environment:
          OS: Win2k sp3
          WLS: 8.1 sp2
          JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
          Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
          without any mention supports only ant 1.5.3.)
          I would appreciate any help in this regard.
          Thanks,
          Abbas


          What version of Struts are you trying to use?
          Are you certain you're not encountering a different instance of that class in
          an unexpected location in your classpath?
          "Abbas" <[email protected]> wrote:
          >
          >Hi,
          >I am trying to compile jsps with weblogic.jspc, which use struts' html
          >tags. However,
          >the compilation fails with the following message:
          >
          >[java] Translation of /views/viewPageBody.jsp failed: (line 3): Error
          >in using
          >tag library uri='/tags/struts-html' prefix='html': The Tag class 'org.apache.struts.taglib.html.BaseTag'
          >has no setter method corresponding to TLD declared attribute 'server',
          >(JSP 1.1
          >spec, 5.4.1)
          >
          >I opened the BaseTag class from the struts jar and found the setter exists
          >for
          >the attribute 'server' of html tld. So does the property 'server'. The
          >property
          >'server' is a string and the parameter in the setter is a string. I read
          >about
          >the jspc errors in wls 8.1 about the setter parameter being of different
          >type
          >than the property. However, that is not the case here. I tried using
          >both Sun's
          >and BEA's jdk. None of them help. Btw, there is another attribute mentioned
          >in
          >the html tld, which is 'target'. The compiler doesn't complain yet about
          >this.:(
          >Also, I happened to compile other apps which have struts logic tags.
          >
          >
          >My environment:
          >OS: Win2k sp3
          >WLS: 8.1 sp2
          >JDK: Sun's 1.4.2 sp4 / Bea's 1.4.1 sp5 (tried both)
          >Ant: 1.5.3 (I had an issue earlier with ant until I found that Bea officially
          >without any mention supports only ant 1.5.3.)
          >
          >I would appreciate any help in this regard.
          >
          >Thanks,
          >
          >Abbas

WLS 7.0 sp2 - Servlet Problems with SOAP messages

          I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
          XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
          support of JAXM? The System.out.println's indicate I have successfully received
          the incoming SOAP request and then successfully formatted the SOAP response, but
          upon returning saving the response it appears to blow up. Does anyone have any
          suggestions?
          I need to do the following in a servlet:
          - receive an incoming SOAP request with an embedded XML message
          - perform some processing
          - return a SOAP response with an embedded XML message
          Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
          <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
          7,name=isd.war,context-path=)] Root cause of ServletException
          java.lang.Error: NYI
          at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
          eImpl.java:360)
          at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
          (ServletStubImpl.java:1058)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:401)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
          n.run(WebAppServletContext.java:5445)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          eManager.java:780)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
          rvletContext.java:3105)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
          pl.java:2588)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          I've stripped the code down so that all it does is verifies the incoming SOAP/XML
          request and creates a hard-coded response... be gentle... I'm a novice at this
          import javax.xml.soap.*;
          import javax.servlet.*;
          import javax.servlet.http.*;
          // import javax.xml.transform.*;
          import java.util.*;
          import java.io.*;
          public class RegisterServlet extends HttpServlet
          static MessageFactory fac = null;
          static
          try
          fac = MessageFactory.newInstance();
          catch (Exception ex)
          ex.printStackTrace();
          public void init(ServletConfig servletConfig) throws ServletException
          super.init(servletConfig);
          public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
          IOException
          try
          System.out.println("** Note: doPost() Entering req = " + req);
          // Get all the headers from the HTTP request
          MimeHeaders headers = getHeaders(req);
          // Get the body of the HTTP request
          InputStream is = req.getInputStream();
          // Now internalize the contents of a HTTP request
          // and create a SOAPMessage
          SOAPMessage msg = fac.createMessage(headers, is);
          System.out.println("** Note: doPost() Step A");
          SOAPMessage reply = null;
          reply = onMessage(msg);
          System.out.println("** Note: doPost() Step B reply = " + reply);
          if (reply != null)
          * Need to call saveChanges because we're
          * going to use the MimeHeaders to set HTTP
          * response information. These MimeHeaders
          * are generated as part of the save.
          if (reply.saveRequired())
          System.out.println("** Note: doPost() Step C reply.saveRequired()");
          reply.saveChanges();
          resp.setStatus(HttpServletResponse.SC_OK);
          putHeaders(reply.getMimeHeaders(), resp);
          // Write out the message on the response stream
          OutputStream os = resp.getOutputStream();
          System.out.println("** Note: doPost() Step D os = " + os);
          reply.writeTo(os);
          os.flush();
          else
          resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
          catch (Exception ex)
          throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
          static MimeHeaders getHeaders(HttpServletRequest req)
          Enumeration enum = req.getHeaderNames();
          MimeHeaders headers = new MimeHeaders();
          while (enum.hasMoreElements())
          String headerName = (String)enum.nextElement();
          String headerValue = req.getHeader(headerName);
          StringTokenizer values =
          new StringTokenizer(headerValue, ",");
          while (values.hasMoreTokens())
          headers.addHeader(headerName,
          values.nextToken().trim());
          return headers;
          static void putHeaders(MimeHeaders headers, HttpServletResponse res)
          Iterator it = headers.getAllHeaders();
          while (it.hasNext())
          MimeHeader header = (MimeHeader)it.next();
          String[] values = headers.getHeader(header.getName());
          if (values.length == 1)
          res.setHeader(header.getName(),
          header.getValue());
          else
          StringBuffer concat = new StringBuffer();
          int i = 0;
          while (i < values.length)
          if (i != 0)
          concat.append(',');
          concat.append(values[i++]);
          res.setHeader(header.getName(), concat.toString());
          // This is the application code for handling the message.
          public SOAPMessage onMessage(SOAPMessage message)
          SOAPMessage replymsg = null;
          try
          System.out.println("** Note: OnMessage() Entering msg = " + message);
          //Extract the ComputerPart element from request message and add to reply SOAP
          message.
          SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
          SOAPBody reqsb = reqse.getBody();
          //System.out.println("** Note: OnMessage() Step B");
          System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
          + reqsb);
          //Create a reply mesage from the msgFactory of JAXMServlet
          System.out.println("** Note: OnMessage () Step B");
          replymsg = fac.createMessage();
          SOAPPart sp = replymsg.getSOAPPart();
          SOAPEnvelope se = sp.getEnvelope();
          SOAPBody sb = se.getBody();
          System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
          = " + sb);
          se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
          System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
          = " + sb);
          replymsg.saveChanges();
          System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
          catch (Exception ex)
          ex.printStackTrace();
          return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

Assigned User Role Mirgation from EP 6.0 SP2 to SAP NW2004s (EP 7.00 SP7)

Our users are stored in LDAP and their role assignment is driven by the roles assigned to the groups. For example...
      Manager Group : MSS and other role assigned
      Employee Group : ESS and other role assigned
but some users are assigned additional roles not driven through groups, for example, some manager may have business specific reporting role assigned to them. In this case, the assigned role did not move to EP 7.0 because the role assignment information is stored in the portal database (Oracle) for EP 6.0 SP2 and the new EP 7.0 portal database (Oracle) does not have that information since we did not use migration tools for the upgrade.
Is there any way I can extract the roll assignment information from EP 6.0 SP2 and upload them to EP 7.0 database since both environments have identical roles and we are using the same LDAP for both environments ??

Our users are stored in LDAP and their role assignment is driven by the roles assigned to the groups. For example...
      Manager Group : MSS and other role assigned
      Employee Group : ESS and other role assigned
but some users are assigned additional roles not driven through groups, for example, some manager may have business specific reporting role assigned to them. In this case, the assigned role did not move to EP 7.0 because the role assignment information is stored in the portal database (Oracle) for EP 6.0 SP2 and the new EP 7.0 portal database (Oracle) does not have that information since we did not use migration tools for the upgrade.
Is there any way I can extract the roll assignment information from EP 6.0 SP2 and upload them to EP 7.0 database since both environments have identical roles and we are using the same LDAP for both environments ??

WLS 6.1 sp2 & Xerces 2.0.0 - ClassCastException

I'm porting our application from WLS 5.1 to 6.1 sp2 under NT 4.0 w/sp6a.
I'm using the JDK that ships with WLS 6.1. A 3rd party library
we need for XML signature support requires Xerces 2.0.0, when I put
that library before weblogic.jar in the classpath, most of our API calls
pass, but
about 15% fail with the runtime error:
java.lang.ClassCastException: weblogic.apache.xerces.dom.DocumentImpl
(com.eoriginal.engine.core.session.objectManagement.TCUSignedObjectDataAcces
sSessionBean_65hpm7_Impl::storeBlob)
Our storeBlob() method has no XML processing code and I have been
unsuccessful trying to find
the cast in the EJBC generated stubs. I have read a few posts where people
are successfully using
Xerces 2.0 & WLS 6.1, and none reference this error. Can anyone explain
what's going on?
Any workarounds?
TIA
Gordon

I'm porting our application from WLS 5.1 to 6.1 sp2 under NT 4.0 w/sp6a.
I'm using the JDK that ships with WLS 6.1. A 3rd party library
we need for XML signature support requires Xerces 2.0.0, when I put
that library before weblogic.jar in the classpath, most of our API calls
pass, but
about 15% fail with the runtime error:
java.lang.ClassCastException: weblogic.apache.xerces.dom.DocumentImpl
(com.eoriginal.engine.core.session.objectManagement.TCUSignedObjectDataAcces
sSessionBean_65hpm7_Impl::storeBlob)
Our storeBlob() method has no XML processing code and I have been
unsuccessful trying to find
the cast in the EJBC generated stubs. I have read a few posts where people
are successfully using
Xerces 2.0 & WLS 6.1, and none reference this error. Can anyone explain
what's going on?
Any workarounds?
TIA
Gordon

WLS 6.1 SP2 NSAPI and iPlanet (Sun One) issues

Hi. I am going nuts with this NSAPI issue. I am working in a Solaris 8 environment,
WLS 6.1 SP2 and iPlanet (Sun One)and NSAPI. I can get everything to work fine
and dandy in aniPlanet 4.1 environment. I can not get it to work in an Iplanet
(Sun One) 6.x environment. It appears that some things work differently between
the versions of iPlanet (ie. things contained in magnus.conf and/or obj.conf).
I have tried moving things, removing things, adding things and nothing seems
to work....it's almost as though the NSAPI, etc. are being ignored.
I've attached my magnus.conf and obj.conf files (I cut and pasted them into a
single file so I could upload it). Can anyone help me out here...I've been working
for weeks on this and can't seem to get any answers.
Thanks!
Doug
P.S. For security purpses I changed the first part of the IP add. in the files
to 1234567, etc.
Thanks
[conf_files.txt]

Hi Doug
U have to put the following section
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="./libproxy.so"
Init fn="wl_init"
into magus.conf
and put the rest into obj.conf
Best Regards
Alex
"Doug E" <[email protected]> wrote:
>
Does anybody know of a good reference document on how to properly install
the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references
that
I have been finding are either incomplete, have typo's and are mostly Windows
oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies,
etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many
of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other,
etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x
then many
of the docs out there are inaccurate. Does anyone know if there is a newer
version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc
from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix
(Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas?
Thanks!
-Doug

WLS 6.1 SP2, iPlanet 6 & NSAPI problems

Does anybody know of a good reference document on how to properly install the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references that
I have been finding are either incomplete, have typo's and are mostly Windows oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies, etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other, etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x then many
of the docs out there are inaccurate. Does anyone know if there is a newer version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix (Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas? Thanks!
-Doug

Hi Doug
U have to put the following section
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib="./libproxy.so"
Init fn="wl_init"
into magus.conf
and put the rest into obj.conf
Best Regards
Alex
"Doug E" <[email protected]> wrote:
>
Does anybody know of a good reference document on how to properly install
the NSAPI
plug-in for WLS6.1 & iPlanet6(SunOne) on Unix (Solaris). Many of the references
that
I have been finding are either incomplete, have typo's and are mostly Windows
oriented
(ie. with the .dll's, paths, examples, etc.)
My problem is that our old iPlanet 4.x works fine...everything proxies,
etc. iPlanet
6 just doesn't want to seem to communicate with WLS 6.1 SP2 We tried many
of the
saem things from the 4.x magnus & obj.confs...but things look somewhat different
in iPlanet 6.x (did they move tings..such as the fn's from one to the other,
etc.)
If so..and there are big differences in installing iPlanet 4.x vs. 6.x
then many
of the docs out there are inaccurate. Does anyone know if there is a newer
version
of the NSAPI plug-in for Unix.
I would love to see a basic, working set of magnus.conf obj.conf, MIME,etc
from someone
who has actually gotten NSAPI to work between WLS 6.1 and iPlanet 6 on Unix
(Solaris)
It blows my mind that 4.x works and 6.x doesn't. An updated NSAPI plug-in
, if it exists and perhaps fixes the problem, would make my day. Any ideas?
Thanks!
-Doug

WLS 6.1 SP2 proxy server timeout

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

We are using WLS 6.1 SP2 server as a proxy server. When accessing a
page that has a long running process, the server times out in 5
minutes and throws an internal server error on the browser. Is there a
way to prevent this from happening or increase the timeout period?

Excessive LDAP Queries from WLS 6.0 SP2 RP3

Similar Messages

Maybe you are looking for