BEA-280101 on WLS 10.3.5 on Solaris 10 (64b) with JDK 1.6_24(32b)

Hi,
We get this error on starting the Admin Server instance:
<25-may-2011 08H49' CEST> <Warning> <Store> <BEA-280101> <The persistent file store "_WLS_Server-Unica" is forced to use buffered I/O and so may have
significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is mi
ssing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration
for advice.>
We check the Thread "BEA-280101 warning while using Weblogic 10.3.3 on SPARC 64bit sun jvm" and it's not my case, so... I search a good solution, but I don't find it.
Can anybody helps me?
Bond2

Hi,
Go to <Middleware_Home>\user_projects\domains\<SOA Domain>\bin\SetSOADomainEnv.cmd (or SetSOADomainEnv.sh if Linux) and add the -Djava.library.path to JAVA_OPTIONS as shown below;
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.library.path=<Middleware_Home>\wlserver_10.3\server\native\win\x64 [Depending on whether your OS is Windows or Linux the path might slightly change]
For additional information please refer to the following: http://sathyam-soa.blogspot.com/2011_04_01_archive.html

Similar Messages

  • BEA-280101 warning while using Weblogic 10.3.3 on SPARC 64bit sun jvm

    Hi all:
    I got this warning when start Weblogic 10.3.3 on SPARC 64bit sun jvm
    <BEA-280101> <The persistent file store "_WLS_xxxdomain" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    I have checked that Native I/O is enabled,but it seems JMS can't find correct .so file
    Any idea? Thanks in advance!
    Best regards,
    James

    We are also getting the same error on a Linux 10.3.3 installation with 64bit jrockit
    Red Hat Enterprise Linux Server release 5.5
    Linux 2.6.18-194.3.1.el5 #1 SMP x86_64 x86_64 x86_64 GNU/Linux
    Is that the correct driver? This is a default weblogic installation, what is missing so it uses the correct I/O method?
    ####<Jun 22, 2010 6:04:12 PM CEST> <Info> <Store> <server> <wlserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <12772226524
    27> <BEA-280008> <Opening the persistent file store "_WLS_admdominio1" for recovery: directory=/weblogic103/user_projects/domain/servers/server/data/store/default requestedWritePolicy="Dire
    ct-Write" fileLockingEnabled=true driver="NIO".>
    ####<Jun 22, 2010 6:04:12 PM CEST> <Warning> <Store> <wlserver> <wlserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277222652564> <BEA-280101> <The persistent file store "_WLS_wlserver" is forced to use buffered I/O and so may have significantly degraded performance. Either the OS/hardware environment does not support the chosen write policy or the native wlfileio library is missing. See store open log messages for the requested and final write policies. See the documentation on store synchronous write policy configuration for advice.>
    Edited by: ezra-s on 22-jun-2010 18:46

  • Login on to WLS with jdk 1.4 doesnot work

    Hi,
    I had ealier posted a question on how to debug ejb's on wls with eclipse and
    was directed to this site "http://www.genuitec.com/products.htm#weblogic_jdk14".
    There I found a document on how to setup WLS into debug and how to setup WLS to
    work with jdk 1.4.
    I followed the instructions but the password I am enetering is revoked. form
    the trace given bellow the NT username taken from the profile is bk608, is it
    the username for which I have to give the password or the ususal WLS management
    password ? Please help.
    Thanks,
    Gavin.
    PS: Here is the trace.....
    C:\bea\wlserver6.0>set PATH=C:\java\j2sdk1.4.0\bin;C:\WINNT\MS\SMS\CORE\BIN;c:\d
    mi\win32\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\MSSQL7\BINN;C:
    \java\jdk1.3.1_02\bin;C:\java\jakarta-ant-1.4.1\bin
    C:\bea\wlserver6.0>set PATH=.\bin;C:\java\j2sdk1.4.0\bin;C:\WINNT\MS\SMS\CORE\BI
    N;c:\dmi\win32\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\MSSQL7\B
    INN;C:\java\jdk1.3.1_02\bin;C:\java\jakarta-ant-1.4.1\bin
    C:\bea\wlserver6.0>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    C:\bea\wlserver6.0>"C:\java\j2sdk1.4.0\bin\java" -hotspot -ms64m -mx64m -classpa
    th .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=mydomain -Dweblo
    gic.Name=myserver "-Dbea.home=C:\bea" "-Djava.security.policy==C:\bea\wlserver6.
    0/lib/weblogic.policy" -Dweblogic.management.password= "-Djava.security.auth.log
    in.config=C:\bea\wlserver6.0/lib/login.conf" weblogic.Server
    [NTLoginModule] succeeded importing info:
    userID = bk608
    domain = HK2OSL
    domainSID = S-1-5-21-161959346-607994573-1935560845
    userSID = S-1-5-21-161959346-607994573-1935560845-14617
    primary group ID = S-1-5-21-161959346-607994573-19355608
    45-513
    group ID = S-1-5-21-161959346-607994573-1935560845-513
    group ID = S-1-1-0
    group ID = S-1-5-21-314861234-1864712239-1573738576-1007
    group ID = S-1-5-32-544
    group ID = S-1-5-32-545
    group ID = S-1-5-21-161959346-607994573-1935560845-1796
    group ID = S-1-5-21-161959346-607994573-1935560845-1898
    group ID = S-1-5-21-161959346-607994573-1935560845-1904
    group ID = S-1-5-21-161959346-607994573-1935560845-1907
    group ID = S-1-5-21-161959346-607994573-1935560845-1908
    group ID = S-1-5-21-161959346-607994573-1935560845-1934
    group ID = S-1-5-21-161959346-607994573-1935560845-10808
    group ID = S-1-5-5-0-49130
    group ID = S-1-2-0
    group ID = S-1-5-4
    group ID = S-1-5-11
    impersonationToken = 928
    [NTLoginModule] added NTPrincipal to Subject
    Starting WebLogic Server ....
    <Apr 16, 2002 10:11:19 AM CEST> <Notice> <Management> <Loading configuration fil
    e .\config\mydomain\config.xml ...>
    log file: C:\bea\wlserver6.0\.\config\mydomain\logs\weblogic.log
    <Apr 16, 2002 10:11:21 AM CEST> <Info> <Logging> <Only log messages of severity
    "Error" or worse will be displayed in this window. This can be changed at Admin
    Console> mydomain> Servers> myserver> Logging> General> Stdout severity threshol
    d>
    <Apr 16, 2002 10:11:22 AM CEST> <Emergency> <Security> <Authentication failure
    reenter password to boot weblogic server:>
    <Apr 16, 2002 10:11:23 AM CEST> <Emergency> <Security> <Authentication failure
    reenter password to boot weblogic server:>
    <Apr 16, 2002 10:11:27 AM CEST> <Emergency> <Server> <Unable to initialize the
    s
    erver: 'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user guest denied
    java.lang.SecurityException: Authentication for user guest denied
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :360)
    at weblogic.security.SecurityService.initialize(SecurityService.java:125
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user guest den
    ied
    java.lang.SecurityException: Authentication for user guest denied
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :360)
    at weblogic.security.SecurityService.initialize(SecurityService.java:125
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    C:\bea\wlserver6.0>goto finish
    C:\bea\wlserver6.0>cd config\mydomain
    C:\bea\wlserver6.0\config\mydomain>ENDLOCAL

    add -Dweblogic.management.password=yoursystempassword to the java command line
    when you start WebLogic. Or specify it in the startWebLogic.cmd if you use the
    standard startup script:
    @rem Set WLS_PW equal to your system password for no password prompt server startup.
    set WLS_PW=yoursystempassword
    Gavin <[email protected]> wrote:
    Hi,
    I had ealier posted a question on how to debug ejb's on wls with eclipse and
    was directed to this site "http://www.genuitec.com/products.htm#weblogic_jdk14".
    There I found a document on how to setup WLS into debug and how to setup WLS to
    work with jdk 1.4.
    I followed the instructions but the password I am enetering is revoked. form
    the trace given bellow the NT username taken from the profile is bk608, is it
    the username for which I have to give the password or the ususal WLS management
    password ? Please help.
    Thanks,
    Gavin.
    PS: Here is the trace.....
    C:\bea\wlserver6.0>set PATH=C:\java\j2sdk1.4.0\bin;C:\WINNT\MS\SMS\CORE\BIN;c:\d
    mi\win32\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\MSSQL7\BINN;C:
    \java\jdk1.3.1_02\bin;C:\java\jakarta-ant-1.4.1\bin
    C:\bea\wlserver6.0>set PATH=.\bin;C:\java\j2sdk1.4.0\bin;C:\WINNT\MS\SMS\CORE\BI
    N;c:\dmi\win32\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\MSSQL7\B
    INN;C:\java\jdk1.3.1_02\bin;C:\java\jakarta-ant-1.4.1\bin
    C:\bea\wlserver6.0>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
    C:\bea\wlserver6.0>"C:\java\j2sdk1.4.0\bin\java" -hotspot -ms64m -mx64m -classpa
    th .;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogic.Domain=mydomain -Dweblo
    gic.Name=myserver "-Dbea.home=C:\bea" "-Djava.security.policy==C:\bea\wlserver6.
    0/lib/weblogic.policy" -Dweblogic.management.password= "-Djava.security.auth.log
    in.config=C:\bea\wlserver6.0/lib/login.conf" weblogic.Server
    [NTLoginModule] succeeded importing info:
    userID = bk608
    domain = HK2OSL
    domainSID = S-1-5-21-161959346-607994573-1935560845
    userSID = S-1-5-21-161959346-607994573-1935560845-14617
    primary group ID = S-1-5-21-161959346-607994573-19355608
    45-513
    group ID = S-1-5-21-161959346-607994573-1935560845-513
    group ID = S-1-1-0
    group ID = S-1-5-21-314861234-1864712239-1573738576-1007
    group ID = S-1-5-32-544
    group ID = S-1-5-32-545
    group ID = S-1-5-21-161959346-607994573-1935560845-1796
    group ID = S-1-5-21-161959346-607994573-1935560845-1898
    group ID = S-1-5-21-161959346-607994573-1935560845-1904
    group ID = S-1-5-21-161959346-607994573-1935560845-1907
    group ID = S-1-5-21-161959346-607994573-1935560845-1908
    group ID = S-1-5-21-161959346-607994573-1935560845-1934
    group ID = S-1-5-21-161959346-607994573-1935560845-10808
    group ID = S-1-5-5-0-49130
    group ID = S-1-2-0
    group ID = S-1-5-4
    group ID = S-1-5-11
    impersonationToken = 928
    [NTLoginModule] added NTPrincipal to Subject
    Starting WebLogic Server ....
    <Apr 16, 2002 10:11:19 AM CEST> <Notice> <Management> <Loading configuration fil
    e .\config\mydomain\config.xml ...>
    log file: C:\bea\wlserver6.0\.\config\mydomain\logs\weblogic.log
    <Apr 16, 2002 10:11:21 AM CEST> <Info> <Logging> <Only log messages of severity
    "Error" or worse will be displayed in this window. This can be changed at Admin
    Console> mydomain> Servers> myserver> Logging> General> Stdout severity threshol
    d>
    <Apr 16, 2002 10:11:22 AM CEST> <Emergency> <Security> <Authentication failure
    reenter password to boot weblogic server:>
    <Apr 16, 2002 10:11:23 AM CEST> <Emergency> <Security> <Authentication failure
    reenter password to boot weblogic server:>
    <Apr 16, 2002 10:11:27 AM CEST> <Emergency> <Server> <Unable to initialize the
    s
    erver: 'Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user guest denied
    java.lang.SecurityException: Authentication for user guest denied
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :360)
    at weblogic.security.SecurityService.initialize(SecurityService.java:125
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.SecurityException: Authentication for user guest den
    ied
    java.lang.SecurityException: Authentication for user guest denied
    at weblogic.security.SecurityService.initializeSuid(SecurityService.java
    :360)
    at weblogic.security.SecurityService.initialize(SecurityService.java:125
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:343)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    C:\bea\wlserver6.0>goto finish
    C:\bea\wlserver6.0>cd config\mydomain
    C:\bea\wlserver6.0\config\mydomain>ENDLOCAL
    Dimitri

  • Troubleshooting tuneables, WLS 6.1/SP2 on Solaris 8/SPARC.

    Hi,
    Is there a way to monitor dynamic or otherwise the memory, filedescriptor and
    CPU allocation per application and/or thread?
    If this is not available in 6.1 is it available in later releases/patchlevels
    such as 7.x or 8.x?
    rgds
    /PL

    Yes i tried that, but it says, incorrect option, JVM could not be created.
    any was i cd identify is the install binary was correct?
    like any indication in jdk131/jre/bin folder?
    Kumar Allamraju <[email protected]> wrote:
    i think it does.
    Have you tried to start with java -server weblogic.Server?
    Are you getting any errors?
    Kumar
    vinay wrote:
    Greetings
    I installed, wls 6.1 sp2 on Solaris 7.
    But it seems the built in jdk131 that installed doesnt support
    -server option.
    i checked the jdk131/jre/bin folder, but i dont see any client, serverfolders...how
    is this possible?
    how to correct this?

  • Jdk131 of wls 6.1 sp2 on Solaris 7 doesnt support -server option?

    Greetings
    I installed, wls 6.1 sp2 on Solaris 7.
    But it seems the built in jdk131 that installed doesnt support
    -server option.
    i checked the jdk131/jre/bin folder, but i dont see any client, server folders...how
    is this possible?
    how to correct this?

    Yes i tried that, but it says, incorrect option, JVM could not be created.
    any was i cd identify is the install binary was correct?
    like any indication in jdk131/jre/bin folder?
    Kumar Allamraju <[email protected]> wrote:
    i think it does.
    Have you tried to start with java -server weblogic.Server?
    Are you getting any errors?
    Kumar
    vinay wrote:
    Greetings
    I installed, wls 6.1 sp2 on Solaris 7.
    But it seems the built in jdk131 that installed doesnt support
    -server option.
    i checked the jdk131/jre/bin folder, but i dont see any client, serverfolders...how
    is this possible?
    how to correct this?

  • [HELP] Can WLS 8.1 run on JRE (instead of JDK)?

    Hello everybody,
    I dimly remember reading not long ago that WLS must be run from JDK's java
    not JRE's for full functionality, but now I can not find that explicitily
    stated anywhere.
    Platform is WLS 8.1 sp2 on solaris 8, .sh installer (full version with
    internal JDK).
    On install, the JAVA_HOME in the startup script is set to the WLS's own
    internal JDK:
    JAVA_HOME="/home/bea81/jdk141_03"
    and the java startup command in the script refers to the java in that
    internal JDK
    ${JAVA_HOME}/bin/java ... weblogic.Server
    Now I am faced with a troublesome WLS install where the java startup command
    has been customized to the java in the JRE within the internal JDK:
    ${JAVA_HOME}/jre/bin/java ... weblogic.Server
    My question is:
    will WLS work properly when started from JRE that way? Or shallI expect some
    malfunction as a result?
    TIA
    Paola R.

    Hello everybody,
    I dimly remember reading not long ago that WLS must be run from JDK's java
    not JRE's for full functionality, but now I can not find that explicitily
    stated anywhere.
    Platform is WLS 8.1 sp2 on solaris 8, .sh installer (full version with
    internal JDK).
    On install, the JAVA_HOME in the startup script is set to the WLS's own
    internal JDK:
    JAVA_HOME="/home/bea81/jdk141_03"
    and the java startup command in the script refers to the java in that
    internal JDK
    ${JAVA_HOME}/bin/java ... weblogic.Server
    Now I am faced with a troublesome WLS install where the java startup command
    has been customized to the java in the JRE within the internal JDK:
    ${JAVA_HOME}/jre/bin/java ... weblogic.Server
    My question is:
    will WLS work properly when started from JRE that way? Or shallI expect some
    malfunction as a result?
    TIA
    Paola R.

  • Wls-10.3.4 AD auth failed with ADF 11.1.1.3 app after upgrade from 10.3.3

    Hi,
    i have posted same issue on wls-10.3.4 Active Directory Authentication failed after Upgrade from 10.3.3
    I'm not sure if this could be an adf or wls topic.
    we have a wls 10.3.3 Installation with ActiveDirectory authentication provider.
    Delegated authentication against AD has worked very well.
    Now we have installed wls 10.3.4 and have configured the ActiveDirectory authentication provider in the same manner.
    Users and groups are listed like before in wls console, but authentication from our running ADF application is answered with "invalid username or passwort".
    No exceptions are logged in domain or admin server logs.
    The application was developed and compiled (ojdeploy) with jdev 11.1.1.3.
    wls 10.3.4 domain is upgraded with adf 11.1.1.3 libs.
    Authenication over wls console with AD credentials also fails.
    Has anybody made same experiences or workarounds?
    Thanks in advance
    Andre

    Hi,
    you should take a look at the ADF security files , especially the jazn xml file. Try to open your PS2 application in the new Ps3 Jdev and look if there are changes to the jazn.xml.
    Or you can check the jazn data xml file in the fmwconfig folder of the config domain folder.
    and check all the authenticators if everything has the sufficient control flag.
    hope this helps

  • RUn WLS 7 as Windows 2K service with JDK 1.4.1

    Has anyone able to get WLS 7 to run as Windows 2K service with JDK 1.4.1?

    NO -- the first product to support JDK 1.4 is WLS 8.1. Period.
    Wayne
    cdd wrote:
    Has anyone able to get WLS 7 to run as Windows 2K service with JDK 1.4.1?

  • Cannot run BEA WebLogic 8.1 SP 3 with JDK 1.6

    Hi,
    Im using BEA Weblogic 8.1 SP3 trying to run a sample where a Robot from Kapow Mashup Server is called from a WebService hosted in the server.
    The thing is that I keep getting a EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder (I attach the full exception below). I realised that by default the server uses the JDK which comes with the software (version 1.4) and that the class java.lang.StringBuilder is only available from JDK 1.5 onwards.
    I have JDK 1.6 in my system, so in WebLogic -> Tools -> Application Properties -> JDK Home, I set that folder but still same exception occurs.
    Through the Configuration Wizard I create a new “Basic WebLogic Server Domain” and in the step to configure the Java SDK I set the JDK 1.6 folder. However, when I try to start that server I get this error.
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=;C:\bea\WEBLOG~1\server\lib\weblogic_knex_patch.jar;C:\bea\WEBLOG~1\common\lib\log4j.jar;C:\bea\WEBLOG~1\server\lib\debugging.jar;C:\bea\WEBLOG~1\server\lib\knex.jar;C:\bea\WEBLOG~1\javelin\lib\javelin.jar;C:\bea\WEBLOG~1\server\lib\wlw-lang.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\server\lib\ant\ant.jar;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\lib\rt.jar;;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient.jar;C:\bea\WEBLOG~1\server\lib\webserviceclient+ssl.jar;C:\bea\WEBLOG~1\server\lib\xbean.jar;C:\bea\WEBLOG~1\server\lib\wlxbean.jar;C:\bea\WEBLOG~1\server\lib\xqrl.jar;C:\bea\WEBLOG~1\server\lib\netui\netui-compiler.jar;C:\bea\WEBLOG~1\server\lib\wli.jar;C:\bea\WEBLOG~1\server\lib\fop.jar;C:\bea\WEBLOG~1\integration\adapters\sample\lib\sample-eis.jar;
    PATH=C:\bea\WEBLOG~1\server\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\jre\bin;C:\ARCHIV~1\Java\JDK16~1.0_1\bin;C:\Archivos de programa\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\Archivos de programa\Archivos comunes\Adobe\AGL;c:\Archivos de programa\Microsoft SQL Server\90\Tools\binn\;c:\matlab6p5\bin\win32;C:\Nokia\Update_Manager\bin;C:\Archivos de programa\QuickTime\QTSystem\;C:\Sun\jwsdp-2.0\jwsdp-shared\bin;C:\Archivos de programa\Kapow Mashup Server 6.3\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Archivos de programa\Intel\DMIX;C:\Archivos de programa\HPQ\IAM\bin;C:\Archivos de programa\Java\jdk1.6.0_10\bin;C:\eclipseJava\plugins\org.apache.ant_1.7.0.v200803061910\bin;C:\bea\WEBLOG~1\server\bin\oci920_8
    * To start WebLogic Server, use a username and *
    === Debugging ===
    This window is necessary for debugging code using WebLogic Workshop
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http:\\hostname:port\console *
    starting weblogic with Java version:
    Listening for transport dt_socket at address: 8453
    Starting WLS with line:
    C:\ARCHIV~1\Java\JDK16~1.0_1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=C:\bea\WEBLOG~1 -Dwls.home=C:\bea\WEBLOG~1\server -Dwli.home=C:\bea\WEBLOG~1\integration -Dlog4j.configuration=file:C:\bea\WEBLOG~1\common\lib\workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=C:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
    Listening for transport dt_socket at address: 8453
    <27-abr-2009 11H22' CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 11.0-b15 from Sun Microsystems Inc.>
    <27-abr-2009 11H22' CEST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
    <27-abr-2009 11H22' CEST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Integration 8.1 SP3 Wed Jun 30 14:05:38 PDT 2004 405464>
    Stopping the Weblogic Workshop debugger...
    Debugger Stopped.
    Stopping Pointbase server...
    Pointbase server stopped.
    If I modify the settings of this new domain an pick a BEA Supplied SDKs, everything works just fine.
    Someone can give a hand on that? It seems like Bea WebLogic 8.1 and JDK 1.6 are not compatible. Completely stacked here.
    Regards.
    Full Exception
    EJB Exception: : java.lang.NoClassDefFoundError: java/lang/StringBuilder
    at robosuite.wizard.jws5a1dbbea00000001.ApiKapowIN.toString(ApiKapowIN.java:141)
    at java.lang.String.valueOf(String.java:2131)
    at java.lang.StringBuffer.append(StringBuffer.java:370)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.logInvoke(WlwThreadContext.java:363)
    at com.bea.wlw.runtime.core.context.WlwThreadContext.startInvocation(WlwThreadContext.java:608)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:414)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:248)
    at com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:198)
    at com.bea.wlw.runtime.core.bean.SLSBContainerBean.invoke(SLSBContainerBean.java:103)
    at com.bea.wlwgen.StatelessContainer_ly05hg_ELOImpl.invoke(StatelessContainer_ly05hg_ELOImpl.java:153)
    at com.bea.wlwgen.GenericStatelessSLSBContAdpt.invokeOnBean(GenericStatelessSLSBContAdpt.java:62)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at com.bea.wlw.runtime.core.bean.SyncDispatcherBean.invoke(SyncDispatcherBean.java:160)
    at com.bea.wlw.runtime.core.bean.SyncDispatcher_k1mrl8_EOImpl.invoke(SyncDispatcher_k1mrl8_EOImpl.java:100)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.remoteDispatch(Dispatcher.java:161)
    at com.bea.wlw.runtime.core.dispatcher.Dispatcher.dispatch(Dispatcher.java:49)
    at com.bea.wlw.runtime.core.dispatcher.HttpServerHelper.executePostRequest(HttpServerHelper.java:713)
    at com.bea.wlw.runtime.core.dispatcher.HttpServer.doPost(HttpServer.java:49)
    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:996)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:419)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:315)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6456)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
    at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3661)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2630)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

    Even if it is a very naive question but I just cannot get it worked, what do you mean by using jdk 1.5 on client side?
    I guess client side is completely out of WLS so the jdk to be used on the client side is not set in the environment.
    However, the Exception Im getting is on the server side, when it tries to run the code automatically generated from Kapow Mashup Server 6.3. That code is embedded in a jar file, but it seems it makes a call to the java.lang.StringBuilder class which as said before, it is only available from jdk 1.5 onwards.
    Should I contact Kapow Mashup Server support to see how the sample code is generated or I am missing something?
    Regards.

  • WLS 10.3.0.0 Solaris SPARC and DBMS Oracle 10gR2 connection pooling issue

    Hi all,
    we are currently testing Weblogic Server 10.3.0.0 in order to migrate our production system from WLS 8.1 to it.
    While testing the new setup, we encountered some strange behaviour of the connection pooling within WLS.
    We configured a XA-Connection pool to our DB (Oracle 10gR2) by using
    a) the Oracle XA-thin-driver delivered within WLS 10.3.0.0
    and alternatively
    b) the Oracle 11.2.0.2 OCI-driver of the Oracle 11g database client.
    We´ve got the same issue with both variants. We defined an initial capacity of 5 connections and a maximum capacity of 30 connections.
    Our application is running flawlessly using the connection pool, but the amount of active sessions between the application server and the database server is increasing rapidly and the maximum capacity is exceeded. We are seeing up to multiple hundreds of sessions from the application server to our database server. Obviously the connections aren´t cleaned up.
    We are using the following settings for the JDBC-Connection:
    initial capacity = 5
    max. capacity = 30
    Capacity increment = 1
    Statement cache type = LRU
    Statement cache size = 10
    Test connections on reserve = true
    Test frequency = 120
    Test table name = "sql select 1 from dual"
    seconds to trust an idle pool connection = 10
    shrink frequency = 0
    connecttion creation retry frequency = 120
    login delay = 0
    incative connection timeout = 10
    max. waiting for connection = 2147483647
    connection reserve timeout= = -1
    Ignare in-use connections = true
    pinned-to-thread = false
    remoce infected connections enabled = true
    Does anyone have an idea how to track/solve this issue?
    Kind regards
    Marc

    Hi Joe,
    we´ve tested with the thin driver using an initial capacity of 5 and a maximum capacity of 15. During our tests (in a very short time period) the maximum capacity has not been exceeded. But we saw some exceptions in the managed server logfile which made us curious.
    When these exceptions are occuring, a new connection to the database server is established. We are seeing for a short time a total count of 6 connections which is immediately decreasing to the initial capacity of 5. We will do some further testing over the next hours and monitor the connection usage.
    The connection we are dealing with is the one called "ZDB2".
    This is an excerpt of the logfile:
    ####<18.10.2010 19:45 Uhr MESZ> <Debug> <JDBCConn> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-02F7EA174F1D84653A69> <> <1287423940610> <BEA-000000> <java.lang.Exception: Pinned: autoCommit=true,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=ZDB2,appname=null,moduleName=null,connectTime=177,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=true,lastSuccessfulConnectionUse=1287423940605,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
         at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:308)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:314)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:427)
         at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
         at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
         at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1473)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1272)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:425)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:382)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:338)
         at org.hibernate.connection.DatasourceConnectionProvider.getConnection(DatasourceConnectionProvider.java:69)
         at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:423)
         at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
         at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139)
         at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547)
         at org.hibernate.loader.Loader.doQuery(Loader.java:673)
         at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236)
         at org.hibernate.loader.Loader.doList(Loader.java:2220)
         at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104)
         at org.hibernate.loader.Loader.list(Loader.java:2099)
         at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:912)
         at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172)
         at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121)
         at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
         at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:811)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderPersistenceGenerated.findByPrimaryKey(OrderPersistenceGenerated.java:45)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1356)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:830)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1276)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:19812)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1289)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:823)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImplStandard.findOrderByPrimaryKey(OrderManagementServiceImplStandard.java:1341)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKeyTx(OrderManagementServiceTransactionHandler.java:816)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.findOrderByPrimaryKey(OrderManagementServiceSessionBean.java:1255)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_ELOImpl.findOrderByPrimaryKey(OrderManagementEJB_yb2dzq_ELOImpl.java:7332)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceApplicationProxy.findOrderByPrimaryKey(OrderManagementServiceApplicationProxy.java:1266)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.findOrderByPrimaryKey(OrderManagementServiceTransactionHandler.java:809)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1636)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    ,currentThread=Thread[[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={} is set to be refreshed
         at weblogic.jdbc.common.internal.ConnectionEnv.setRefreshNeeded(ConnectionEnv.java:518)
         at weblogic.jdbc.wrapper.Connection.getVendorConnection(Connection.java:292)
         at de.dpcom.persistence.hibernate.BinaryBlobType.nullSafeSet(BinaryBlobType.java:109)
         at org.hibernate.type.CustomType.nullSafeSet(CustomType.java:146)
         at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1997)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2371)
         at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2307)
         at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2607)
         at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:92)
         at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:248)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:232)
         at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
         at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
         at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
         at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CertificatePersistenceGenerated.updateCertificate(CertificatePersistenceGenerated.java:116)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceImplStandard.updateCertificate(CustomerManagementServiceImplStandard.java:1282)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceTransactionHandler.updateCertificateTx(CustomerManagementServiceTransactionHandler.java:711)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceSessionBean.updateCertificate(CustomerManagementServiceSessionBean.java:1104)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementEJB_ap2i9a_ELOImpl.updateCertificate(CustomerManagementEJB_ap2i9a_ELOImpl.java:19199)
         at APPNAME-ROOT-PATH.components.customermanagement.biz.CustomerManagementServiceApplicationProxy.updateCertificate(CustomerManagementServiceApplicationProxy.java:1101)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceImpl.publishCertificate(ProductionResultProcessingServiceImpl.java:1131)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceTransactionHandler.publishCertificateTx(ProductionResultProcessingServiceTransactionHandler.java:298)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean.publishCertificate(ProductionResultProcessingServiceSessionBean.java:517)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.publishCertificate(ProductionResultProcessingServiceSessionBean_yaua6q_ELOImpl.java:1804)
         at APPNAME-ROOT-PATH.components.productionresultprocessing.biz.ProductionResultProcessingServiceApplicationProxy.publishCertificate(ProductionResultProcessingServiceApplicationProxy.java:471)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishCertificate(OrderManagementServiceImpl.java:1825)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.publishOrder(OrderManagementServiceImpl.java:1664)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceImpl.savePublishedOrder(OrderManagementServiceImpl.java:1606)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceTransactionHandler.savePublishedOrderTx(OrderManagementServiceTransactionHandler.java:3467)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementServiceSessionBean.savePublishedOrder(OrderManagementServiceSessionBean.java:5272)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl.savePublishedOrder(OrderManagementEJB_yb2dzq_EOImpl.java:3263)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke2(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.internalInvoke1(Unknown Source)
         at APPNAME-ROOT-PATH.components.ordermanagement.biz.OrderManagementEJB_yb2dzq_EOImpl_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
         at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940797> <BEA-001072> <Connection for XA pool "ZDB2" created.>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <JDBC> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-001132> <Initialized statement cache of size "10" for connection in pool "ZDB2".>
    ####<18.10.2010 19:45 Uhr MESZ> <Info> <Common> <SERVER-NAME> <MANAGED SERVER NAME> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1287423940808> <BEA-000628> <Created "1" resources for pool "ZDB2", out of which "1" are available and "0" are unavailable.>
    Any suggestions?
    Kind regards
    Marc

  • NSAPI Plug-in problems for WLS 6.1 SP4 on Solaris 8

    I recently upgraded our dev weblogic 6.1 to SP4. Around the same time, the
    netscape plugin inexplicably starts to behave differently.
    I have the following configuration lines in the obj.conf file
    <Object name="test" ppath="*/apps/*">
    Service fn=wl_proxy WebLogicHost=appserver.mycompany.com WebLogicPort=7001
    </Object>
    I did not configure the plugin to proxy by mime type.
    But no matter what I put in the url, it automatically gets proxied to
    appserver host.
    I tried:
    http://web.mycompany.com/index.html - I see the WebLogic Index page instead
    of the default Netscape Webserver home page.
    http://web.mycompany.com/test/test.jsp - I see the test jsp page, even
    though it is not a path that I configured to proxy over to weblogic.
    Anybody experience this before?
    TIA,
    John

    Thanks for your response.
    The plugin inexplicably starts to work again after several days
    without changes to obj.conf file but the webserver was restarted.
    However, when I first spotted the problem, I restarted the webserver several
    times with no visible effect on the problem. I need to trace this
    and see if I can duplicate the problem again, but for now, the
    problem has gone away.
    "Eric Gross" <[email protected]> wrote in message
    news:[email protected]..
    This may be a netscape issue since, from what you are saying, the weblogic
    plugin gets invoked on any request.
    The only time the plugin gets invoked is if it goes into the object tag.
    Can you paste your full obj.conf?
    Thanks,
    Eric
    "newsgroups.bea.com" <[email protected]> wrote in message
    news:3e63bef3$[email protected]..
    I recently upgraded our dev weblogic 6.1 to SP4. Around the same time,the
    netscape plugin inexplicably starts to behave differently.
    I have the following configuration lines in the obj.conf file
    <Object name="test" ppath="*/apps/*">
    Service fn=wl_proxy WebLogicHost=appserver.mycompany.com
    WebLogicPort=7001
    </Object>
    I did not configure the plugin to proxy by mime type.
    But no matter what I put in the url, it automatically gets proxied to
    appserver host.
    I tried:
    http://web.mycompany.com/index.html - I see the WebLogic Index page
    instead
    of the default Netscape Webserver home page.
    http://web.mycompany.com/test/test.jsp - I see the test jsp page, even
    though it is not a path that I configured to proxy over to weblogic.
    Anybody experience this before?
    TIA,
    John

  • Kerberos, Active Directory & WLS 10.3.5 on Solaris 10 (also UCM 11g)

    The story so far :
    I have a keytab from the kdc and have configured krb5.conf such that kinit and using the Kinit class from rt.jar (from the 1.5 OS JDK not the 1.6 used with WLS) are working.
    An AD authentication provider in WLS is allowing logins to UCM using AD domain accounts, this is the top provider.
    I've configured a negotiate identity assertion provider (default settings).
    I've created a JAAS configuration file that includes debug=true.
    I've set a bunch of start parameters for the UCM managed server which point to the JAAS config file, enable negotiation and set Kerberos debug on.
    I've cleared the managed server and admin server caches umpteen times and performed umpteen + n restarts but to no avail. Needless to say, it (ie Kerberos ticket negotiation resulting in not having to reenter my network credentials, having already authenticated to the AD domain, to UCM) is not working.
    But, curious oddity #1, I am getting no debug regarding krb5 in the managed server logs/out at all (the start up parameters do register in the log!) even if I incorporate a deliberate error. Nothing, de nada, zilch.
    Has anyone got WNA/Kerberos working with WLS 10.3.5 using java 1.6 on Solaris 10 64bit SPARC with or without UCM? Or any other platform/application? Is anyone able to cast any light on why there is no debug?

    It could be related to the size of the kerberos ticket (not sure here, just a guess).
    When a user belongs to many groups, it affects the size of the ticket, some tips are provided here: http://support.microsoft.com/kb/327825
    (not related to JRockit, but to the MaxTokenSize in the Windows registry).
    Could also run into trouble when using a front-end such as Apache HTTP Server (and WebCache)
    - http://httpd.apache.org/docs/2.2/mod/core.html (set the LimitRequestFieldSize http://httpd.apache.org/docs/2.2/mod/core.html#limitrequestfieldsize appropriately)
    - WebCache: WXE-11355 Single request header length exceeds configured maximum. A forbidden error response is returned to the client. Client IP: %s error
    - Cause: One of the headers in the request exceeded the configured maximum.
    - Action: Adjust the maximum individual header size limit in the Security page of OracleAS Web Cache Manager. If the problem persists, contact Oracle Support Services.

  • Installation of webgate on Solaris (sparcv9) with WLS 10.3.5 and Apache2

    Problem Description: We have installed IDM 11g and OAM 10.1.4.3 on RHEL5.5 hosts, respectively. We have successfully installed all the components:
    Environment Details:
    - Server1 -- 64 bit Intel RHEL5
    Fusion Middleware Identity Management - 11.1.1.2
    WLS 10.3.2
    ODSM,OID,OVD
    DB 10.2.0.4
    - Server 2 32-bit Intel RHEL5
    OAM 10.1.4.3
    OHS 11.1.1.2
    After successfully installing these hosts, we needed to create a webhost from where we could test our protected resources. This host would have a sparc v9 OS, include WLS 10.3.5, and use apache2 as its web server. These have all been successfully installed by root and are running.
    Our next step was to create the webgate/access gate on the OAM host and setup the necessary policy. This was successful.
    We then copied Oracle_Access_Manager10_1_4_3_0_sparc-s2_APACHE2_WebGate to the host and started the installation. Since the host is headless (just a host -- no keyboard, mouse, or gui attached to it) we have to ssh to the host and execute all the installs from the command line without gui. When we got to entering the webgate id and hit return... the process just ended without any error or logfiles. We are assuming that at that point the webgate software was installed but not configured.
    We went ahead and tried the configureWebGate script:
    ./start_configureWebGate -i /opt/oracle/middleware/webgate -l WebGate
    ld.so.1: configureWebGate: fatal: /opt/oracle/middleware/webgate/access/oblix/tools/configureWebGate/../../../oblix/lib/libstdc++.so.5: wrong ELF data format: ELFDATA2LSB
    Killed
    We have successfully installed OAM and IDM many times and have installed webhosts as well... but the webhosts have always been RHEL5 with WLS and OHS instead of Sparc, wls, and apache. Is there anything special about a sparc or apache install?
    WLS and apache were installed as root... we have tried installing the webgate as root, oracle, even apache... but get the same results. The gcc libs are downloaded and available, but the error we see during configuration seems to indicate that they are not found. We have tried seting the LD_LIBRARY_PATH to include the directory containing the libs.
    Edited by: OldGuy on Jul 7, 2011 4:04 AM

    On another note... is there a Sparc equivalent for the mod_wl_ohs.conf where we would place
    <Location /<deployed app>>
    SetHandler weblogic-handler
    WebLogicHost <weblogichost>
    WebLogicPort 7001
    </Location>
    It appears that this goes into the apache httpd.conf file, correct? Or does the mod_wl_ohs.conf equivalent exist?
    We have just about completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host.
    When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, no logfile entries... just a blank browser.

  • Accesing protectred URIs on Solaris (sparcv9) with WLS 10.3.5 and Apache2

    I had started to ask questions about this on another thread of mine, but since I had listed that one as answered and this being different from the original question on that thread...I felt it better to create its own thread.
    Problem Description: Environment Details:
    - Server1 -- 64 bit Intel RHEL5
    Fusion Middleware Identity Management - 11.1.1.2
    WLS 10.3.2
    ODSM,OID,OVD
    DB 10.2.0.4
    - Server 2 32-bit Intel RHEL5
    OAM 10.1.4.3
    OHS 11.1.1.2
    - Server 3 64-bit SparcV9 Webhost -- deployed app as protected uri
    WLS 10.3.5
    Apache2
    Webgate 10.1.4.3
    We believe we have completed everything in regard to being able to include a solaris host in our list of hosts that are tied to OAM. We have installed webhost with XP and RHEL5.6 successfully using OHS 11.1.1.2. This is the first time creating a webhost on Sparc. The webgate was created and software installed, the deployed app protected, etc... Everything that we have done for Linux and XP in the past we have done for this Sparc host. The only differences are the SUN OS, Apache2, and WLS 10.3.5. I believe those are all acceptable for these Oracle products and versions.
    When we try to access the Sparc's protected uri... nothing happens. The browser stays blank... the url does not change to display the oamsso login.html (as the other installs do)... nothing is returned... no error, no remarks, ... just a blank browser.
    Doing an apachectl -l I receive the following:
    Compiled in modules:
    core.c
    prefork.c
    http_core.c
    mod_so.c
    So mod_so.c is included.
    If I go directly to the protected uri through 7001 instead of the 8890 -- the port httpd.conf has configured to listen on -- the page displays. If I open the oamsso/login.html using 8890... it displays. But if I use 8890 to bring up the protected uri... as described above nothing displays.
    One other thing, since the Sparc host is "headless" -- as described by our SysAdmin... no access directly through the sun console and no gui access via the sun host since there is no sun console just the server -- we have to access the gui via a browser on the same network. The browser is actually on the OAM host.
    From apache2 error_log on SUN host:
    15-7-2011 14:35:51Sending message: 0 13
    protocol=NAP version=3 oldest=1
    15-7-2011 14:35:51Received message: 0 13
    protocol=NAP version=3 oldest=1
    15-7-2011 14:35:51Sending NMP STS negotiation message: 0 0
    sts=open
    15-7-2011 14:35:51Received NMP STS negotiation message: 0 0
    sts=open
    15-7-2011 14:35:51Sending message: 0 14
    cm=mtisunfireHost_AG challenge=b516f1a00c2a95ee
    15-7-2011 14:35:51Received message: 0 14
    cm=access_svrid1 challenge=95520d6315ad3865 st=ma%3d25 rt=1
    15-7-2011 14:35:51Sending message: 0 15
    response=531be0a851cb2773c90aa0c91d9f779c
    15-7-2011 14:35:51Received message: 0 15
    response=2b62c22a9458e962c35d8d7d358f4fc1 st=ma%3d25 rt=1
    15-7-2011 14:35:51Sending message: 0 8
    cm=mtisunfireHost_AG ct=0 version=3
    15-7-2011 14:35:51Received message: 0 8
    ci=id%3dmtisunfireHost_AG%20maxConnections%3d1%20debug%3d0%20maxSessionTime%3d24%20sleepFor%3d60%20security%3dopen%20failoverThreshold%3d1%20aaaTimeoutThreshold%3d%20cookieSessionTime%3d3600%20maxCacheElems%3d100000%20cacheTimeout%3d1800%20configLastUpdateTime%3d1310754351%20preferredHost%3dmtisunfire:8890%20state%3dEnabled%20primaryCookieDomain%3d%20idleSessionTimeout%3d3600%20accessClientPasswd%3d02434564584046435641510409%20primaryServer1%3dhost%253dirsam-oam.dchc.smil.mil%2520port%253d8887%2520numOfConnections%253d1%20denyOnNotProtected%3d0%20cachePragmaHeader%3dno-cache%20cacheControlHeader%3dno-cache%20ipValidation%3d1 st=ma%3d25%20mi%3d2%20sg%3d32%20sm%3d rt=1
    [Fri Jul 15 14:35:52 2011] [notice] child pid 18581 exit signal Segmentation fault (11)
    [Fri Jul 15 14:35:58 2011] [notice] child pid 18582 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:01 2011] [notice] child pid 18583 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:04 2011] [notice] child pid 18585 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:07 2011] [notice] child pid 18586 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:11 2011] [notice] child pid 18590 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:12 2011] [notice] child pid 18591 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:14 2011] [notice] child pid 18592 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:15 2011] [notice] child pid 18593 exit signal Segmentation fault (11)
    [Fri Jul 15 14:36:16 2011] [notice] child pid 18594 exit signal Segmentation fault (11)
    [Fri Jul 15 14:38:35 2011] [notice] child pid 18595 exit signal Segmentation fault (11)
    [Fri Jul 15 14:38:38 2011] [notice] child pid 18596 exit signal Segmentation fault (11)
    I believe that apache is currently setup correctly at this point, but cannot understand what we are missing.

    I would say that OAM does support Apache (according to the certified Apache versions and OS's). However, there are so many distributions out there and it can be configured with countless options, be compiled with a number of different compilers, and include any number of modules that some compatibility issues are bound to arise. The Solaris distribution - also Oracle - is a case in point. I have also encountered issues with the Apache version bundled with some Linux versions (for different reasons than the Solaris bundle) for which the easiest solution has also been to download and build from source. I would imagine that is the reason for what you were told about support for generic Apache, though of course I do not know the context.
    Regards,
    Colin

  • How to use JDK 1.4 and WLS 5.1 on SUN Solaris 5.7

    Hello,
    I run into trouble after I tried to use the JDK 1.4.1_01- b01 with WLS 5.1
    I got the following error message:
    Exception in thread "main" java.security.AccessControlException: access
    denied (java.lang.RuntimePermission createSecurityManager)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :270)
    at
    java.security.AccessController.checkPermission(AccessController.java:401)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:542)
    at java.lang.SecurityManager.<init>(SecurityManager.java:298)
    at
    weblogic.boot.ServerSecurityManager.<init>(ServerSecurityManager.java:11)
    at weblogic.Server.main(Server.java:66)
    at weblogic.Server.main(Server.java:58)
    We used to use SDK 1.3.0 without any problems.
    Do I have to change the weblogic.policy file??
    Thanx
    Uwe Froehlich

    JDK 1.4 is not supported yet. You have to use the certified versions.
    Wayne Scott
    Uwe Fröhlich wrote:
    Hello,
    I run into trouble after I tried to use the JDK 1.4.1_01- b01 with WLS 5.1
    I got the following error message:
    Exception in thread "main" java.security.AccessControlException: access
    denied (java.lang.RuntimePermission createSecurityManager)
    at
    java.security.AccessControlContext.checkPermission(AccessControlContext.java
    :270)
    at
    java.security.AccessController.checkPermission(AccessController.java:401)
    at
    java.lang.SecurityManager.checkPermission(SecurityManager.java:542)
    at java.lang.SecurityManager.<init>(SecurityManager.java:298)
    at
    weblogic.boot.ServerSecurityManager.<init>(ServerSecurityManager.java:11)
    at weblogic.Server.main(Server.java:66)
    at weblogic.Server.main(Server.java:58)
    We used to use SDK 1.3.0 without any problems.
    Do I have to change the weblogic.policy file??
    Thanx
    Uwe Froehlich

Maybe you are looking for