Using PrincipalValidator in WLS 8.1

In Weblogic 8.1 Instantiating Default Weblogic PrincipalValidator gives problem

On 6 Feb 2004 01:33:16 -0800, kishore <[email protected]> wrote:
>
In Weblogic 8.1 Instantiating Default Weblogic PrincipalValidator gives
problemYour note is a bit sparse on details. What is the stack trace and what
are you trying to do?
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/

Similar Messages

  • Convert JMS Headers from EBCDIC to ASCII when using JMS Bridge (WLS - WMQ)

    I have a Java app on Weblogic 11g using a Message Bridge to talk JMS with IBM Websphere MQ. The MQ server is running on IBM z/OS platform which uses EBCDIC encoding. I need to use the Weblogic message selector feature to filter messages on the bridge coming from Websphere MQ. But the JMS Headers of MSGs posted by WMQ are in EBCDIC format. How can I instruct MQ to convert the msg headers to ASCII before put on the bridge? Is there any flag on bindings config file? Or can I set some WMQ specific header before sending the msg on WLS side?
    Thanks in advance.

    Hi,
    Such option is not possible in weblogic but I think this property will help you with in MQ.
    Property - Convert EBCDIC newline
    Description - EBCDIC code pages contain a new line (NL) character that is not supported by the ASCII code pages (although some ISO variants of ASCII contain an equivalent). If messages are sent from a system that uses EBCDIC code pages (for example, a z/OS system) to a system that uses ASCII, you can control how the EBCDIC newline character is converted into ASCII format.
    The default value is NL_TO_LF, which means that the EBCDIC NL character (X'15') is converted to the ASCII line feed character LF (X'0A') for all EBCDIC to ASCII conversions. To convert the EBCDIC NL character according to the conversion tables on your operating system, click TABLE. Note that the results of a TABLE conversion can vary from platform to platform and from language to language; even on the same platform the results might vary if you use different coded character set identifiers (CCSIDs). To convert ISO CCSIDs using the TABLE method and use the NL_TO_LF method for all other CCSIDs, click ISO.
    Registry Stanza Key - ConvEBCDICNewline
    Also, the MQSeries (not MQSC) adapter provides the data conversion property may handle this conversion as well.
    Regards,
    Kal

  • Stateless Session EJB hangs using URLConnection but WLS doesn't clean up

    Hi
    We have a stateless session EJB running under WLS 5.1 with service
    pack 10 on Solaris.
    The bean calls a remote HTTP server using the java.net.URLConnection
    class and forwards the response to the EJB client. The bean is largely
    working fine but some threads hang waiting on the HTTP response. Debug
    statements, which are written immediately after the response has been
    read and the connection has been closed, do not appear in our log for
    the hung threads. The WebLogic Console displays these threads as "in
    use" and a "netstat -an" displays the tcp connections as ESTABLISHED.
    However, the access logs of the remote Apache server show the HTTP
    connections of the threads in question completed successfully with
    HTTP code 200. The Apache server is using keep-alive connections.
    Some EJB threads are still waiting for something it seems.
    Has anyody else experienced this when using URLConnection from
    stateless session EJBs under WLS?
    The second problem is why doesn't WLS time these threads out after
    trans-timeout-seconds (we're using the default of 300 seconds)? The
    WLS log shows no error messages relating to this problem.
    I'm grateful for any info offered.
    Thanks in advance
    Steve

    If you suspect that WLS protocol handler is at fault (and quite often it is),
    one thing to try is (if you use Sun's JVM) to use Sun's HTTP protocol handler
    instead of WLS (the most common symptom is when code which makes HTTP requests
    works fine outside of WebLogic and you have problems getting it to work inside
    WebLogic) :
    replace
    URL url = new URL("http://...");
    HttpURLConnection conn = (HttpURLConnection)url.openConnection();
    with
    URL url = new URL(null, "http://...", new sun.net.www.protocol.http.Handler());
    HttpURLConnection conn = (HttpURLConnection)url.openConnection();
    You will have to edit weblogic.policy to allow your code to specify protocol
    handler.
    Also note that transaction timeout is only checked on method boundaries, or
    when your code attempts to do something with the database - it is not going to
    interrupt thread which is waiting for HTTP response.
    Steve Lock <[email protected]> wrote:
    Hi
    Thanks for the info. The remote HTTP server's access log shows that
    the requests were successfully processed. Doesn't this mean that the
    connection is then closed? I know the web server is using keep-alive
    connections but I thought this was transparent to the client...?
    Also why doesn't WLS remove the hung threads?
    Steve
    "Ignacio G. Dupont" <[email protected]> wrote in message news:<[email protected]>...
    We have had a problem like yours with Weblogic 6.1 SP2 on Linux
    The problem is sun's implementation of the HTTP connections doesn't have a
    timeout, so if the other peer doesn't close the connection your threads will
    be "locked" on the connection.
    We have found searching the web that the Jakarta project has a package
    called Jakarta commons that implements HTTP connections with an
    setSoTimeout(int timeout) method so you can open the connections with your
    desired timeout. You have to download the code from the CVS as the released
    version doesn't support the timedout sockets yet.
    When support for the JDK 1.4 version will be announced by Bea you could use
    one of its new features that will allow you to pass arguments to the JVM to
    specify the maximum socket connection stablising timeout and the max
    inactivity on the socket too.
    Hope it helps you.
    Dimitri

  • Using a  foreign WLS JMS queue (no bridge)

              Hi,
              We have a configuration from which we communicate from WLS 7 to a foreign MQ via
              JMS. This works well and we have loaded the foreign MQ jms objects into WLS JNDI
              using a statup class (as the whitepaper available describes) and we look them
              up successfully.
              However, we now have a siutation where we briefly need to switch our application
              to point to a WLS JMS queue on another remote WLS server. Is there an easy way
              to load foreign (maybe remote would be a better word in this case) WLS JMS QCF's
              and destinations into my local WLS JNDI so that I can treat them the same way
              as my MQ objects?
              I can't seem to find any information on how to do this as all information seems
              to point towards the messaging bridge (we can't use this as the bridge changes
              the message JMSMessageID and screws our correlation mechanism up).
              I know we could just look the foreign objects up by using the JNDI environment
              of the remote WLS machine but this would mean changing code and this I can't to
              do (as all our code uses the local default WLS JNDI).
              Any ideas would be gratefully received.
              Cheers,
              Jay.
              

    WLS JMS and MQ JMS handle their JNDI objects a little differently, so I can
              see how this can be confusing. An MQ JMS "ConnectionFactory" or
              "Destination" object is like a little configuration file that tells you
              where the queue manager or queue is, so you can serialize it and look it up
              later and use it to find the queue manager.
              A WLS JMS ConnectionFactory or Destination object is a reference to an
              object on a running server. So, you connect to the server and look them up,
              and then you can use it for messaging. You don't have to store these objects
              in a separate place, like MQ makes you do. But it means that the WLS JNDI
              objects have to be looked up from a running server, and if the server
              restarts, you have to look them up again.
              Doing what you're asking is definitely trickier in 7.0. One thing you could
              do is, again using a servlet or an EJB, connect to the remote JMS cluster
              and look up the objects at the time you want to make the switch. (If the
              remote cluster is down, you'll have to retry from time to time.) If the
              remote cluster is down, you won't be able to look up those objects, but then
              again, if it were down you wouldn't be able to send messages there anyway.
              Using 8.1 would be less complicated, but this method should also work.
              greg
              "Jay Green" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Thanks Greg. When I was searching the BEA website I read about the
              facility in
              > 8.1. Unfortunatley, as you point out, it doesn't help me much with WLS
              7.0.
              >
              > My first thought was to copy my exisiting MQ startup class but I couldn't
              work
              > out how to do this for the remote WLS jms objects as the standard jms
              classes
              > (for QCF etc) don't have methods that allow me to define the foreign WLS
              jms
              > host IP address etc. I checked the WLS 7 API and the jms package didn't
              seem
              > to offer anything to help me do this (as IBM do for MQ). Any ideas?
              >
              > Apologies if I'm being a bit slow here!
              >
              > "Greg Brail" <[email protected]> wrote:
              > >WLS 8.1 includes a feature called "Foreign JMS Providers" that lets you
              > >configure (using the console or config.xml) a link between a JMS JNDI
              > >object
              > >in your WLS servers' tree, and a JNDI object in another provider -- which
              > >could be WLS JMS, or a foreign vendor.
              > >
              > >Using this feature, your application could just look up the local JNDI
              > >objects in the local WLS tree, and then the server in turn performs the
              > >lookup from the actual JNDI provider using the parameters you put in
              > >the
              > >console (or config.xml). So, when you make a change in the console, new
              > >JNDI
              > >lookups will go to the new place.
              > >
              > >Unfortunately, this doesn't help you with 7.0. You could always
              > >programmitically update the local JNDI tree the way you're doing in your
              > >startup class, but instead do it from a servlet or an EJB.
              > >
              > > greg
              > >
              > >"Jay Green" <[email protected]> wrote in message
              > >news:[email protected]...
              > >>
              > >> Hi,
              > >>
              > >> We have a configuration from which we communicate from WLS 7 to a
              foreign
              > >MQ via
              > >> JMS. This works well and we have loaded the foreign MQ jms objects
              > >into
              > >WLS JNDI
              > >> using a statup class (as the whitepaper available describes) and we
              > >look
              > >them
              > >> up successfully.
              > >>
              > >> However, we now have a siutation where we briefly need to switch our
              > >application
              > >> to point to a WLS JMS queue on another remote WLS server. Is there
              > >an easy
              > >way
              > >> to load foreign (maybe remote would be a better word in this case)
              > >WLS JMS
              > >QCF's
              > >> and destinations into my local WLS JNDI so that I can treat them the
              > >same
              > >way
              > >> as my MQ objects?
              > >> I can't seem to find any information on how to do this as all
              information
              > >seems
              > >> to point towards the messaging bridge (we can't use this as the bridge
              > >changes
              > >> the message JMSMessageID and screws our correlation mechanism up).
              > >>
              > >> I know we could just look the foreign objects up by using the JNDI
              > >environment
              > >> of the remote WLS machine but this would mean changing code and this
              > >I
              > >can't to
              > >> do (as all our code uses the local default WLS JNDI).
              > >>
              > >> Any ideas would be gratefully received.
              > >>
              > >> Cheers,
              > >>
              > >> Jay.
              > >
              > >
              >
              

  • Configuring the file T3 servives using WLST in WLS 10.3

    Hi,
    I am trying to use WLST to configure the File T3 services in Weblogic 10.3.
    I can do it using the console.
    Please find the link for configuring through console:
    http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/filet3/TargetFileT3Services.html
    Can some one help me in configuring it through WLST?

    Hi,
    did you try to record the console configuration?

  • Configuring and using CipherSuites in WLS 6.1

    I have a few questions about the supported CipherSuites in WLS 6.1 and the
    the handshake mechanism works with this default:
    1) Edocs specifies that the CipherSuite that WLS uses is configured in the
    config.xml. I understand this and can see the tag <Ciphersuites> with a
    default setting of SSL_RSA_EXPORT_WITH_RC4_40_MD5 in the docs on the
    config.xml file. My question is: Is there anywhere in the console to
    configure this???
    2) From my understanding, in the handshake phase of the SSL protocol, the
    client send over which it's list of CipherSuites it would like to use in
    order of preference. The server then selects which one will be used. My
    question is: If the CipherSuite defined in the config.xml is not in the
    client's preferred list what will happen? Will WLS pick one of it's other
    CipherSuites that is in the client's list? What if WLS doesn't support any
    of the suites specified in the client's preferred list?
    Answers to any or all of these would be greatly appreciated.
    Thanks,
    Mich

    hi it is unlikely people will answer you here because it is about netbeans. this is a java site so they will probably tell you to go to a netbeans site. the one i use is nabbles netbeans just do a search on google to find it.
    you might get lucky here but i doubt it because most people here use notepad and run programs from command prompt. so they might not even know anyway. also i think there is a tutorial at the netbeans sites about transfering libraries they tell you how in some of the introductory tutorials. i think one of the tutorials in relation to setting up a database using derby shows you how to do it but i can't remember.
    your best bet is nabble good luck.

  • WLS 6.1 Webapp using EJB from WLS 9.0

    I have a WLS 6.1.7 based webapp that currently accesses an EJB deployed to WLS 8.1.5. I just tried upgrading the 8.1 server to 9.0.0. I was able to deploy the EJB just fine but the 6.1.7 based webapp is giving me the following error:
    javax.naming.CommunicationException. Root exception is
    weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible version:Incompatible versions - this server: '9.0.0' client: '6.1.7.0']
    at weblogic.socket.Login.checkLoginSuccess(Login.java:77)
    at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:273)
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:325)
    at weblogic.rjvm.Protocol.createConnection(Protocol.java:206)
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1121)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:373)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:274)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:222)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:189)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:186)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:157)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:309)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:213)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
    at javax.naming.InitialContext.init(InitialContext.java:217)
    at javax.naming.InitialContext.<init>(InitialContext.java:193)
    The Initial Context is being created with the following properties:
    java.naming.provider.url=t3://localhost:7001
    java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
    java.naming.security.principal=system
    java.naming.security.credentials=xxxx
    Is there a way to get WLS 6.1 to talk to WLS 9.0?
    Thanks,
    Rick

    I believe the constraint is communicating within 2 releases. ie 6.0 can talk to 7.0 and 8.1, but 9.0 is 3 releases away.
    That being said, you can double-check this with [email protected]
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Using realms in wls 5.1

    is it possible to invoke authentication by getting a handle on a securty realm?
    How would i go about doing this? If I can get a hold of the realm from jndi or
    something...i think i might be golden.
    thanks

    Trash Pages 5.1 and use Pages 09.

  • Help on create a object for an application using startup in wls 8.1

    hi guys
    i am trying to figure out a way to create a initial data object that can used by session beans in a ear deployed in weblogic 8.1. so far i figured out to extend ApplicationLifecycleListener and override the postStart() to instantiate the initial data object (will use JDBC to load data). but i can't figure out how to make this object apparent to other components in the ear. i.e. how can my session ejb access it? whatt is the strategy used here for thing like this? i really appreciate if any one can provide some help.

    hi guys
    i am trying to figure out a way to create a initial data object that can used by session beans in a ear deployed in weblogic 8.1. so far i figured out to extend ApplicationLifecycleListener and override the postStart() to instantiate the initial data object (will use JDBC to load data). but i can't figure out how to make this object apparent to other components in the ear. i.e. how can my session ejb access it? whatt is the strategy used here for thing like this? i really appreciate if any one can provide some help.

  • How to create a JMS persistent file store using WLST in WLS 9.0?

    Anybody have a good example of this? When I try to create a fileStore and set it on my jms server I am getting the following error: "TypeError: setPersistentStore(): 1st arg can't be coerced to weblogic.management.configuration.PersistentStoreMBean'
    Thanks :)

    Hi,
    First Create Persistent Store ( FileStore / JDBCStore).
    File Store Creation is as follows:
    Store = create("PStore","FileStore")
    Set it's File Directory and Targets.
    then Create JMS Server and set its Persistent Store as File Store. Set JMS Server Target.

  • Problem using integrated WLS in jDeveloper 11.1.2.1.0

    Hey there,
    I got a problem using the integrated WLS from the jDeveloper 11.1.2.1.0.
    After trying to deploy an ADF Web Application on the integrated WLS, I get the following log message:
    LOG
    +[Waiting for the domain to finish building...]+
    +[11:26:04 AM] Creating Integrated Weblogic domain...+
    +[11:28:13 AM] Extending Integrated Weblogic domain...+
    +[11:30:06 AM] Integrated Weblogic domain processing completed successfully.+
    *** Using HTTP port 7101 ***
    *** Using SSL port 7102 ***
    +/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/bin/startWebLogic.sh+
    +[waiting for the server to complete its initialization...]+
    +.+
    +.+
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m  -XX:MaxPermSize=512m
    +.+
    WLS Start Mode=Development
    +.+
    CLASSPATH=/home/robin/bin/wls/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/home/robin/bin/wls/patch_wls1211/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_oepe100/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/robin/bin/wls/jdk160_29/lib/tools.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic_sp.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.jar:/home/robin/bin/wls/modules/features/weblogic.server.modules_12.1.1.0.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/webservices.jar:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/robin/bin/wls/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/home/robin/bin/wls/wlserver_12.1/common/derby/lib/derbyclient.jar:/home/robin/bin/wls/wlserver_12.1/server/lib/xqrl.jar
    +.+
    PATH=/home/robin/bin/wls/wlserver_12.1/server/bin:/home/robin/bin/wls/modules/org.apache.ant_1.7.1/bin:/home/robin/bin/wls/jdk160_29/jre/bin:/home/robin/bin/wls/jdk160_29/bin:/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3:/usr/games/bin
    +.+
    +*  To start WebLogic Server, use a username and   *+
    +*  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:
    java version "1.6.0_29"
    Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
    Java HotSpot(TM) Client VM (build 20.4-b02, mixed mode)
    Starting WLS with line:
    +/home/robin/bin/wls/jdk160_29/bin/java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=DefaultServer -Djava.security.policy=/home/robin/bin/wls/wlserver_12.1/server/lib/weblogic.policy -Djavax.net.ssl.trustStore=/tmp/trustStore7618453572230021232.jks -Dhttp.proxyHost=emea-proxy.uk.oracle.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|localhost.localdomain|127.0.0.1|::1|MUELLER-BADY-GENTOO|MUELLER-BADY-GENTOO -Dhttps.proxyHost=emea-proxy.uk.oracle.com -Dhttps.proxyPort=80 -Doracle.jdeveloper.adrs=true -Dweblogic.nodemanager.ServiceEnabled=true -Xverify:none -Djava.endorsed.dirs=/home/robin/bin/wls/jdk160_29/jre/lib/endorsed:/home/robin/bin/wls/wlserver_12.1/endorsed -da -Dplatform.home=/home/robin/bin/wls/wlserver_12.1 -Dwls.home=/home/robin/bin/wls/wlserver_12.1/server -Dweblogic.home=/home/robin/bin/wls/wlserver_12.1/server -Djps.app.credential.overwrite.allowed=true -Dcommon.components.home=/home/robin/bin/wls/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain -Djrockit.optfile=/home/robin/bin/wls/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/servers/DefaultServer -Doracle.domain.config.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig -Digf.arisidbeans.carmlloc=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/carml -Digf.arisidstack.home=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/home/robin/bin/wls/oracle_common/modules/oracle.ossoiap_11.1.1,/home/robin/bin/wls/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dwsm.repository.path=/home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/oracle/store/gmds -Dweblogic.management.discover=true -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=/home/robin/bin/wls/patch_wls1211/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_oepe100/profiles/default/sysext_manifest_classpath:/home/robin/bin/wls/patch_ocp371/profiles/default/sysext_manifest_classpath weblogic.Server+
    +<Feb 10, 2012 11:30:09 AM CET> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>+
    +<Feb 10, 2012 11:30:10 AM CET> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>+
    +<Feb 10, 2012 11:30:11 AM CET> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 20.4-b02 from Sun Microsystems Inc..>+
    +<Feb 10, 2012 11:30:12 AM CET> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.1.0 Wed Dec 7 08:40:57 PST 2011 1445491 >+
    +<Feb 10, 2012 11:30:15 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>+
    +<Feb 10, 2012 11:30:15 AM CET> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>+
    +<Feb 10, 2012 11:30:15 AM CET> <Notice> <Log Management> <BEA-170019> <The server log file /home/robin/.jdeveloper/system11.1.2.1.38.60.81/DefaultDomain/servers/DefaultServer/logs/DefaultServer.log is opened. All server side log events will be written to this file.>+
    Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager saveKeyStore
    WARNING: Failed to save farm keystore. Reason {0}
    Feb 10, 2012 11:30:24 AM oracle.security.jps.internal.keystore.file.FileKeyStoreManager createKeyStore
    WARNING: Failed to save farm keystore. Reason {0}
    oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:64)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)+
    +     at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)+
    +     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)+
    +     at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:850)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)+
    +     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)+
    +     at java.lang.Class.newInstance0(Class.java:355)+
    +     at java.lang.Class.newInstance(Class.java:308)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1343)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:148)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)+
    +<Feb 10, 2012 11:30:24 AM CET> <Error> <Security> <BEA-090892> <The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider>+
    +<Feb 10, 2012 11:30:24 AM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider failed due to exception, see the exception stack trace or the server log file for root cause. If still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1402)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1022)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:148)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsRuntimeException: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:293)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:899)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: java.security.PrivilegedActionException: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:284)+
    +     at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:270)+
    +     Truncated. see log file for complete stacktrace+
    +Caused By: oracle.security.jps.JpsException: [PolicyUtil] Unable to obtain default JPS Context!+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:860)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:844)+
    +     at java.security.AccessController.doPrivileged(Native Method)+
    +     at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:844)+
    +     at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:291)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: oracle.security.jps.service.keystore.KeyStoreServiceException: JPS-06513: Failed to save farm keystore. Reason
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreManager.createKeyStore(FileKeyStoreManager.java:309)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.doInit(FileKeyStoreServiceImpl.java:95)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:73)+
    +     at oracle.security.jps.internal.keystore.file.FileKeyStoreServiceImpl.<init>(FileKeyStoreServiceImpl.java:63)+
    +     at oracle.security.jps.internal.keystore.KeyStoreProvider.getInstance(KeyStoreProvider.java:157)+
    +     Truncated. see log file for complete stacktrace+
    +>+
    +<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>+
    +<Feb 10, 2012 11:30:24 AM CET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>+
    +<Feb 10, 2012 11:30:24 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>+
    Process exited.
    */LOG*
    After that, I tried setting permissions for the cwallet.sso file to ugo+rwx, but this leads to the same problems as mentioned above.
    My second try was to setup an external WLS 12c, but it seems to be not yet possible to connect to a WLS 12c from within jDeveloper.
    Do you have any ideas ?
    Thank you in advance for your help.
    Regards,
    Robin

    After debugging the WLS Initialisation with jdb, I recognized that there was some trouble with dependent libraries.
    In the end, I solved my problem by using another OS (Ubuntu 11.10) for development. There, the WLS works out of the box, even with 64-Bit libraries.
    Thank you for your help.
    Regards,
    Robin

  • Why are the weblogic.kernel.Default Execute Threads used by WLS Kernel

    In my Admin Console, it's displaying 10 out of the 15 weblogic.kernel.Default Execute Threads are used by the WLS Kernel user. The total requests column for these threads are showing 0. The other 5 threads are showing 20K to 40K requests. Why is the WLS Kernel users hogging these threads and not allowing the applications to use them?

    Hi,
    As work enters a WebLogic Server, it is placed in an execute queue. This work is then assigned to a thread within the queue that performs the work.
    By default, a new server instance is configured with a default execute queue, weblogic.kernel.default, that contains 15 threads.
    Go through the following link and find the usefull information on this issue.
    http://e-docs.bea.com/wls/docs81/ConsoleHelp/domain_executequeuetable.html
    Regards
    Anilkumar kari

  • Errors encountered while using a Custom Security Realm on a Platform Domain

    Hi,
    We have created a WebLogic Platform Domain. A WebLogic Portal application(Portal
    7.0) and some Web Service apps are running on this domain.
    We have created a Custom Security Realm b'cos of our application requirements
    and now when I startup the Platform Domain, I see lot of errors.
    Some of the errors typically are
    "<Jan 16, 2003 4:07:02 PM EST> <Error> <HTTP> <101256> <The run-as user: wlisystem,
    for the servlet: ApplicationView for the webapp: /WLI_AI_Workshop_Control_Web,
    could not be resolved to a valid user in the system. Please check if the user
    exists.
    javax.security.auth.login.LoginException: Authentication Failed: User wlisystem
    denied in Realm Adapter realm weblogic"
    or
    Unable to deploy EJB: wlai-eventprocessor-ejb.jar from wlai-eventprocessor-ejb.jar:weblogic.ejb20.WLDeploymentException:
    weblogic.ejb20.interfaces.PrincipalNotFoundException: Authentication Failed: User
    wlisystem denied in Realm Adapter realm weblogic
    Do we have to create any predefined user accounts in the Security Store to get
    rid of these errors. I would appreciate if anyone can suggest some tips or workarounds
    for configuring or creating a Custom Security Realm for Web Logic Platform Domain.
    Thanks
    Vikram

    Hello Vikram,
    Are you using the new WLS 7.0 security framework? It is not supported for
    Portal 7.0. For Portal 7.0 apps you have to use compatibility mode (6.x
    style) security.
    Ture Hoefner
    BEA Systems, Inc.
    www.bea.com
    "Vikram Datla" <[email protected]> wrote in message
    news:3e273015$[email protected]..
    >
    Hi,
    We have created a WebLogic Platform Domain. A WebLogic Portalapplication(Portal
    7.0) and some Web Service apps are running on this domain.
    We have created a Custom Security Realm b'cos of our applicationrequirements
    and now when I startup the Platform Domain, I see lot of errors.
    Some of the errors typically are
    "<Jan 16, 2003 4:07:02 PM EST> <Error> <HTTP> <101256> <The run-as user:wlisystem,
    for the servlet: ApplicationView for the webapp:/WLI_AI_Workshop_Control_Web,
    could not be resolved to a valid user in the system. Please check if theuser
    exists.
    javax.security.auth.login.LoginException: Authentication Failed: Userwlisystem
    denied in Realm Adapter realm weblogic"
    or
    Unable to deploy EJB: wlai-eventprocessor-ejb.jar fromwlai-eventprocessor-ejb.jar:weblogic.ejb20.WLDeploymentException:
    weblogic.ejb20.interfaces.PrincipalNotFoundException: AuthenticationFailed: User
    wlisystem denied in Realm Adapter realm weblogic
    Do we have to create any predefined user accounts in the Security Store toget
    rid of these errors. I would appreciate if anyone can suggest some tips orworkarounds
    for configuring or creating a Custom Security Realm for Web Logic PlatformDomain.
    >
    Thanks
    Vikram

  • WLS Performance .. Socket Exception...

    Hi
    Recently we encounter the problem when we press the "Refresh" button(Browser MS IE) so quickly then WLS shows the error message as below: (The scenario is calling an entity bean from JSP.)
    GMT+08:00 2000:<E> <HTTP>
    Connection failure
    java.net.SocketException: ReadFile on fd=916 failed with err=64
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
         at
    weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java,
    Compiled Code)
         at
    weblogic.socket.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java,
    Compiled Code)
         at
    weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
         at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
    Compiled Code)
    Basicly it's not hurt for our application, but we
    usually need to convert the encoding of the string
    selected from Database in the EJB(it mean I need to
    convert the String because we need chinese). But if we
    press the "Refresh" button so quickly, the chinese is
    incorrect and appeared as "???????". And if we press
    the button later and slowly then the chinese is
    correct.
    Can someone give me some clue about that ? Or is it related with the "Performance Pack" of WLS...?
    BEST & THANKS
    andrew :)
    PS :
    I use Window 2000, WLS 5.1 SP6 and both JDK 1.3 and JDK 1.2.2.
    [weblogic.log]

    Hi Srikant
    Thanks, below the get method of my Entity Bean
    public String getEname() {
    // SBgen: Get variable
    String empName = null;
    try{
    // 'ename' is the filed of the 'emp' table..., it's stored
    // as chinese in Oracle...
    empName = new String(new String(ename).getBytes("iso-8859-
    1"));
    catch (Exception e){
         e.printStackTrace(); }          
    return empName;
    ----------------------------------------------------------------- I use the getByte('iso-8859-1') to convert the string select from database (Oracle 8.1.6, the string in the DB is stored as Chinese) because I need Chinese in web page. The tricky thing is that if I press the 'Refresh' button so quickly then the chinese is displayed as '???' in my web page. If I press the 'Refresh' button slowly then the Chinese is correct in web page(JSP).
    mmmmm...., I do really have no idea about that... Can someone give me some clue about that ? Thanks a lots...
    BEST
    andrew:O
    Srikant Subramaniam <[email protected]> wrote:
    This is a benign error msg ... the client closed the socket without telling the server! We've since turned off this error msg in subsequent service packs.
    Srikant, [email protected], http://weblogic.bea.com/, etc.
    AndrewWang wrote:
    Hi
    Recently we encounter the problem when we press the "Refresh" button(Browser MS IE) so quickly then WLS shows the error message as below: (The scenario is calling an entity bean from JSP.)
    GMT+08:00 2000:<E> <HTTP>
    Connection failure
    java.net.SocketException: ReadFile on fd=916 failed with err=64
    at weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
    at
    weblogic.socket.NTSocketMuxer.read(NTSocketMuxer.java,
    Compiled Code)
    at
    weblogic.socket.MuxableSocketHTTP.requeue(MuxableSocketHTTP.java,
    Compiled Code)
    at
    weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java,
    Compiled Code)
    at
    weblogic.kernel.ExecuteThread.run(ExecuteThread.java,
    Compiled Code)
    Basicly it's not hurt for our application, but we
    usually need to convert the encoding of the string
    selected from Database in the EJB(it mean I need to
    convert the String because we need chinese). But if we
    press the "Refresh" button so quickly, the chinese is
    incorrect and appeared as "???????". And if we press
    the button later and slowly then the chinese is
    correct.
    Can someone give me some clue about that ? Or is it related with the "Performance Pack" of WLS...?
    BEST & THANKS
    andrew :)
    PS :
    I use Window 2000, WLS 5.1 SP6 and both JDK 1.3 and JDK 1.2.2.
    Name: weblogic.log
    weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
    Encoding: base64

  • WLS 5.1 and TX support

              The Weblogic 5.10 documentation states:
              "WebLogic Server Version 5.1 is compliant with the JavaSoft EJB 1.1 specification."
              Yet elsewhere in the documentation it states:
              "The following sections describe EJBs in several transaction scenarios. Note that in all cases EJB transactions should be restricted to a single persistent store, because WebLogic Server does not provide a two-phase commit protocol. EJBs that engage in distributed transactions (transactions that make updates in multiple datastores) cannot guarantee that all branches of the transaction commit or roll back as a logical unit."
              Wait a minute. I thought EJB 1.1 specified that an EJB container must provide a transaction coordinator to support distributed two-phase commit across multiple EJB servers.
              From the spec:
              "Regardless whether an enterprise bean uses bean-managed or container-managed transaction demarcation,
              the burden of implementing transaction management is on the EJB Container and Server Provider.
              The EJB Container and Server implement the necessary low-level transaction protocols, such as the
              two-phase commit protocol between a transaction manager and a database system, transaction context
              propagation, and distributed two-phase commit."
              The spec goes on to show several distributed transaction use cases that must be supported by the EJB container.
              This "single repository" limitation of Weblogic severely limits my options.
              What am I missing?
              Greg
              

    I used Loadrunner's WLS monitor while running some performance scripts on our application. I ended up relying on the WLS Console and some SNMP traps (using HP Openview to review data) in order to acurately guauge utilization of system resources...Regards,Steve

Maybe you are looking for