CLOSE_WAIT on weblogic side

Hello,
I am getting accumulative CLOSE_WAIT connections on the weblogic side. The number
of CLOSE_WAIT connections keep growing and growing and each connection appears
to use up one thread on weblogic.
It all ends up with weblogic server toasted becuase it runs out of threads.
My platform is weblogic 6.1SP4 on Solaris and the webserver is on another Solaris
machine.
My question is: ¿Is this an applications issue (code)? ¿Is it a weblogic issue?
TIA
Cristina

Hi there,
          Yes, we do have the same problem but we have the WL 81 SP2 installed on Solaris box.
          For us this happens whenever we restart the managed server instances using the node manager.
          I suppose the Node Manager configuration is Error free.
          Thanks,
          Karthi.

Similar Messages

  • How to get remote ejb client working with Weblogic 8.1?

    I have Weblogic 8.1 running on a WinXP box behind my firewall. Port 7001 is open to WL and remote browsers can access the console.
    I have a client machine running WinXP on a different network that is remote to the WL server. It can ping the WL server machine.
    I use JVM 1.4.2_08 on all machines.
    If I put my client machine on the LAN with the WL server, then my EJB test client works fine. If I put the client machine on the remote network then the test client fails with a ClassCastException when trying to do a PortableRemoteObject.narrow on the bean home.
    I had this running fine on JBoss 3.22 using RMI over HTTP. I added an HTTP invoker service to my jboss.xml file. I don't know if something similar is needed on the Weblogic side - any ideas on that? All I've done on the WL side is turn on Tunneling - which obviously works because the remote client gets a correct home object when doing a lookup on the bean - based on the IOR string of the home obj.
    Below I include my client code, exception, ejb-jar.xml and my weblogic-ejb-jar.xml.
    Any ideas on what else needs to be done so that a remote client can do a PortableRemoteObject.narrow? My client.jar has all of the EJB classes, and runs fine when run from LAN.
    Thanks,
    --BobC
    Client Code
    Properties p = new Properties();
    p.put("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
    p.put("java.naming.provider.url", "http://66.114.140.213:7001");
    InitialContext ic = new InitialContext(p);
    // Test register bean
    Object homeObj = ic.lookup("tacplanner/register");
    RegisterHome home = (RegisterHome) PortableRemoteObject.narrow(homeObj, RegisterHome.class); // <<< ClassCastException here
    Exception
    java.lang.ClassCastException
    at com.sun.corba.se.internal.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:293)
    at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:134)
    at com.nimblus.tacplanner.test.TestUtils.<init>(TestUtils.java:60)
    at com.nimblus.tacplanner.test.TestUtils.main(TestUtils.java:196)
    ejb-jar.xml
    <?xml version="1.0"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 1.1//EN' 'http://java.sun.com/j2ee/dtds/ejb-jar_1_1.dtd'>
    <ejb-jar>
    <enterprise-beans>
    <session>
    <ejb-name>register</ejb-name>
    <home> com.nimblus.tacplanner.server.ejb.stateless.RegisterHome</home>
    <remote> com.nimblus.tacplanner.server.ejb.stateless.Register</remote>
    <ejb-class>com.nimblus.tacplanner.server.ejb.stateless.RegisterSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    <resource-ref>
    <description>The Oracle Datasource</description>
    <res-ref-name>java:/OracleDS</res-ref-name>
    <res-type>javax.sql.DataSource</res-type>
    <res-auth>Container</res-auth>
    </resource-ref>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>register</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </ejb-jar>
    weblogic-ejb-jar.xml
    <?xml version="1.0"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC
    '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN'
    'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>register</ejb-name>
    <stateless-session-descriptor>
    <pool>
    <max-beans-in-free-pool>100</max-beans-in-free-pool>
    </pool>
    </stateless-session-descriptor>
    <reference-descriptor>
    <resource-description>
    <res-ref-name>jdbc/OracleDS</res-ref-name>
    <jndi-name>OracleDS</jndi-name>
    </resource-description>
    </reference-descriptor>
    <enable-call-by-reference>True</enable-call-by-reference>
    <jndi-name>tacplanner/register</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    --------------------

    Problem solved.
    For remote clients you need to generate and use the stub classes for EJB interfaces using Weblogic's appc utility.
    See: "http://e-docs.bea.com/wls/docs81/ejb/appc_ejbc.html#1151900"
    --BobC                                                                                                                                                                                                                                                                                                                                                                                                                               

  • Deploying a jdev adf app on standalone weblogic issues

    Dear all,
    Sorry for my post which is very long but i will try to give you all information.
    I am currently developing a full stack ADF application (with BC4J to access the database) using Jdev 11g last release (5407)
    When working in JDev, my application is running perfectly.
    Now i am facing several issues regarding the deployment on a standalone weblogic.
    * 1st problem: deploying from Jdev into a remote weblogic server *
    If i try to deploy on a separate machine from jdeveloper directly using a server connection, then deployment failed with message in jdev console:
    [04:53:47 PM] Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\Temp\lara_abcf.ear' for the application 'Lara ABCF' could not be loaded to the server 'http://MYSERVER:7001/bea_wls_deployment_internal/DeploymentService'.
    Read channel closed
    [04:53:47 PM] See server logs or server console for more details.
    [04:53:47 PM] weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'D:\jdev-workspace\LaraABCF\deploy\lara_abcf.ear' to 't3://MYSERVER:7001'
    [04:53:47 PM] #### Deployment incomplete. ####
    [04:53:47 PM] Deployment Failed
    I tried to look into weblogic logs and see nothing helping me to found the problem. Any idea?
    I then tried to create a local domain on my workstaion and now deploying from JDeveloper works.
    I created an EAR file from Jdev and deployedthe EAR from the weblogic web console.
    From both method i was facing the same issue:
    * 2nd problem: deploying an application with a datasource access into a standalone weblogic *
    - Using the default configuration, i successfully deployed the application using weblogic console but the application stay on "Prepared" state in the console. Starting it from the console the application failed to start after the deployment. The error message display in the top of the web page is :
    Error weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: java.security.PrivilegedActionException: weblogic.common.ResourceException: No credential mapper entry found for password indirection user=lra_abcf for data source laraABCFConn
    -I found an entry in the forum (What does this message mean? which give an hint to solve this issue:
    Modify the application properties from JDev and uncheck the option: "Auto Generate and Synchronize weblogic-jdbc.xml Descriptors During Deployment", rebuild and deploy the application.
    I try this method and teh application successfully starts but does not work: stacktrace in weblogic console indicates that BC4J does not work properly and i think that database connection are not up. The error Message:
    javax.el.ELException: java.lang.NullPointerException
    at javax.el.BeanELResolver.setValue(BeanELResolver.java:345)
    at javax.el.CompositeELResolver.setValue(CompositeELResolver.java:283)
    at com.sun.faces.el.FacesCompositeELResolver.setValue(FacesCompositeELResolver.java:100)
    at com.sun.el.parser.AstValue.setValue(AstValue.java:140)
    at com.sun.el.ValueExpressionImpl.setValue(ValueExpressionImpl.java:255)
    Truncated. see log file for complete stacktrace
    java.lang.NullPointerException
    at com.cma.shipping.lara.view.settings.backing.TeuConversionBkB.setServicesSelectList(TeuConversionBkB.java:254)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    Truncated. see log file for complete stacktrace
    The NPE is on a line accessing a view object.
    * Final question:
    Is it possible to develop an application using a local database connection for BC4J in jdev and an external datasource when the application is deployed on a standalone weblogic without modifying the source code?
    The real issue about this is : is there a step by step tutorial explaining how to develop a simple ADF11g application using BC and deploy it successfully on a weblogic server?
    Thanks for your help

    found a workaround:
    * create a datasource on the weblogic side, mapped into the JNDI tree
    * create a new configuration in the appmodule with a new datasource mapped to this jndi reference
    * modify the databinding of my page to use this app module configuration
    * deploy again the application and this works
    but now my application does not work in jdeveloper because it seeks to a datasource in JNDI. I must revert to old settings for development en switch to these new settings to deploy on the server. Very annoying...
    Thanks for you help :)

  • Weblogic certificate is not being authenticated in Oracle HTTP Server

    I am using Oracle HTTP Server with SSL and mod_proxy set up trying to pass a url through to the weblogic server. I start with my OHS url in the browser and the proxy is switches to the url to weblogic but I get the following error on the OHS side:
    [2011-12-22T18:40:09.4683-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-2077] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] nzos proxy handshake error, nzos_Handshake returned 29024(server social.us.oracle.com:443, client 10.139.164.191)
    [2011-12-22T18:40:09.4683-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-2171] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] NZ Library Error: Invalid X509 certificate chain [Hint: the client probably doesn't provide a valid client certificate]
    [2011-12-22T18:40:09.4685-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] (20014)Internal error: proxy: pass request body failed to 10.139.164.191:7001 (denovm11-1.us.oracle.com)
    [2011-12-22T18:40:09.4685-07:00] [OHS] [INCIDENT_ERROR:32] [OHS-9999] [core.c] [host_id: denovm11-6] [host_addr: 10.139.164.196] [tid: 1155799360] [user: root] [ecid: 004hBXzInYHEOPb_THt1ic0007DM000002] [rid: 0] [VirtualHost: social.us.oracle.com:443] proxy: pass request body failed to 10.139.164.191:7001 (denovm11-1.us.oracle.com) from 10.139.164.196 ()
    And the following error on the weblogic side:
    ####<Dec 22, 2011 6:40:10 PM MST> <Warning> <Security> <denovm11-1> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <8e6c6502a1af117a:4eeee51e:13466bb040d:-8000-000000000000a764> <1324604410502> <BEA-090482> <BAD_CERTIFICATE alert was received from denovm11-6.us.oracle.com - 10.139.164.196. Check the peer to determine why it rejected the certificate chain (trusted CA configuration, hostname verification). SSL debug tracing may be required to determine the exact reason the certificate was rejected.>
    Here is my ssl.conf from OHS:
    # Oracle HTTP Server mod_ossl configuration file: ssl.conf #
    # OHS Listen Port
    Listen 443
    <IfModule ossl_module>
    ## SSL Global Context
    ## All SSL configuration in this context applies both to
    ## the main server and all SSL-enabled virtual hosts.
    # Some MIME-types for downloading Certificates and CRLs
    AddType application/x-x509-ca-cert .crt
    AddType application/x-pkcs7-crl .crl
    # Pass Phrase Dialog:
    # Configure the pass phrase gathering process.
    # The filtering dialog program (`builtin' is a internal
    # terminal dialog) has to provide the pass phrase on stdout.
    SSLPassPhraseDialog builtin
    # Inter-Process Session Cache:
    # Configure the SSL Session Cache: First the mechanism
    # to use and second the expiring timeout (in seconds).
    SSLSessionCache "shmcb:${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}/ssl_scache(512000)"
    SSLSessionCacheTimeout 300
    # Semaphore:
    # Configure the path to the mutual exclusion semaphore the
    # SSL engine uses internally for inter-process synchronization.
    <IfModule mpm_winnt_module>
    SSLMutex "none"
    </IfModule>
    <IfModule !mpm_winnt_module>
    SSLMutex pthread
    </IfModule>
    ## SSL Virtual Host Context
    <VirtualHost *:443>
    <IfModule ossl_module>
    # SSL Engine Switch:
    # Enable/Disable SSL for this virtual host.
    SSLEngine on
    # Client Authentication (Type):
    # Client certificate verification type and depth. Types are
    # none, optional and require.
    SSLVerifyClient none
    # SSL Cipher Suite:
    # List the ciphers that the client is permitted to negotiate.
    SSLCipherSuite SSL_RSA_WITH_RC4_128_MD5,SSL_RSA_WITH_RC4_128_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_DES_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA
    # SSL Certificate Revocation List Check
    # Valid values are On and Off
    SSLCRLCheck Off
    #Path to the wallet
    SSLWallet "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default"
    <FilesMatch "\.(cgi|shtml|phtml|php)$">
    SSLOptions +StdEnvVars
    </FilesMatch>
    <Directory "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/cgi-bin">
    SSLOptions +StdEnvVars
    </Directory>
    BrowserMatch ".*MSIE.*" \
    nokeepalive ssl-unclean-shutdown \
    downgrade-1.0 force-response-1.0
    </IfModule>
    <IfModule proxy_module>
    ProxyRequests Off
    <Proxy *>
    Order deny,allow
    Allow from all
    </Proxy>
    # Path to the wallet
    SSLProxyWallet "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/keystores/default"
    SSLProxyEngine on
    SSLProxyVerify none
    # ottest : denovm11-1
    ProxyPass /test https://abc.us.oracle.com:7001/test
    ProxyPassReverse /test https://abc.us.oracle.com:7001/test
    </IfModule>
    </VirtualHost>
    </IfModule>
    On the OHS side I have all the certificates needed so SSL is working properly. The weblogic environment is currently working fine with other webgates, but those are apache and we are trying to switch to OHS.
    Can OHS use mod_proxy to connect to weblogic or do I need to use mod_wl_ohs?
    Does anyone see anything wrong in my ssl.conf file in regards to the proxy section.
    Thanks in advance.

    In summary:
    You need to create a new wallet with CSR (certificate signing req)
    Send this to your certificate authority and get the signed server certificate.
    Now import the signed server cert and the trusted root cert in to the wallet that you created newly.
    Modify ssl.conf to point to the new wallet location.
    To create wallet refer to : http://docs.oracle.com/cd/E25054_01/core.1111/e10105/wallets.htm#CHDGIJDC
    Further reference: http://docs.oracle.com/cd/E25054_01/core.1111/e10105/sslconfig.htm#CBDGIJDF
    Dont mind if this doc is 500 pages ;)

  • Snmp configuration on weblogic 10 has no effect

    SNMP in MMC(Mobile Management Center, A HP Product), use joesnmp.jar internal to send snmp trap generated by mmc app. This part works well in weblogic 10;
    snmp in weblogic , configured by weblogic console. In weblogic 8, we configure such items:
    Weblogic Subsystem
    Purpose
    Level
    Deployer
    Monitor all war/ear deploy/undeploy/redeploy
    INFO
    JDBC
    Monitor all warnings/errors in jdbc operation
    WARN
    Current tests shows that the snmp configuration on weblogic 10 has no effect.
    Due to MMC4.6 gets the Weblogic updated from 8.16 to 10.3, we didn’t find the configuration about “Enable JDBC Logging”. Below is the former config page about Weblogic 8.16.
    But in Weblogic 10.3 we cannot find this configuration. We have followed the guide http://e-docs.bea.com/wls/docs100/jdbc_admin/monitor.html#wp1048793
    And tried to set the appropriate properties on the command line like this,
    -Dweblogic.debug.DebugJDBCSQL=true -Dweblogic.log.StdoutSeverity="Info"
    Actually we can get the DM, Core, SMTP, Bulk, Adaptor Class, and connection fail error messages in weblogic backend log, but seems Weblogic cannot send SNMP trap messages to SNMP monitoring tool like Openview.
    PS. Weblogic can send out the SNMP trap messages when the server starts and stops.
    So till now the SNMP cannot monitor the DM, Core, SMTP, Bulk, Adaptor Class, and connection fail for MMC4.6.

    Hi, I am on 12.1 weblogic, and I am stuck on where you set the SNMP Servername and port number.
    We are on windows 2008, I see there is a services, SNMP .
    Is there something I need to do on the weblogic side before i get into the SNMP agenets and traps, this part I understand, I am just unsure where to add the SNMP Servername and the user I wish the emails to go to.
    I see in the security realms the user i can add to the group monitors.
    -->, I am running WL 10.3 and SNMP works fine. The cluster generates traps based on particular mbeans, such as when a server's health state is not "OK", or when there are JDBC connection issues. You have to create a new SNMP agent within the admin server then build the individual traps ( String, Gauge, Counter, etc. ) and make sure you have a Trap Destination.

  • Need info regarding static file cache in weblogic

    Hi,
    I want to cache the static files at weblogic side
    I am using Apache plugin provided by weblogic
    I have gone through the e-docs about FileCache ON which is needs to be set in httpd.conf
    I want to know is there any settings which is set at weblogic to cache static files
    As i am using apache plug in provided by weblogic i want to know if there is any setting at weblogic side
    Thanks in advance

    Hello,
    Normally the statis contents are served from web servers, in your case this may be from Apache. So what statis files are you referring to in weblogic, is that a part of HTML and images from WAR / EAR ?
    In general weblogic has its own cache temp location as runtime to keep the classfiles and other resources unpacked from WAR / EAR.
    -AJ

  • UML (2.0) profile for J2EE/WebLogic

    I am currently creating UML diagrams for deployments of various software releases into various environments in an enterprise. These involve some Java applications including WebLogic. I am on the verge of creating my own UML profile for this, in particular for the WebLogic side of things, with JVMs including WebLogic instances modelled as execution environments, etc. I am also keen to drill into J2EE deployment descriptors to visualize crisp interfaces between J2EE components and the services they require from the J2EE containers, which is "pure" J2EE.
    I imagine I am not the first to do this, and someone must have created profiles already. I have found an old draft specification for a UML/EJB mapping. I imagine the profile I am looking for would be in a UML/XMI format that I can import into my tool (SparxSystems Enterprise Architect), but even just a graphical specification would be of help.
    Does anyone have some pointers to where I should look?
    Andreas

    You're absolutely right. For some reason orion.jar isn't in that distribution. However there should be an oc4j.jar file in there, which behaves exactly as the orion.jar file would. So, any place in the documentation where it refers to orion.jar, just substitute oc4j.jar.
    Ryan

  • BEA Weblogic 9.0/Open LDAP communication

    We have BEA Weblogic 9.0 and OpenLDAP running on two different machines. I am running a stress/load/performance test on my app and found that there are repetitive calls between Weblogic and OpenLDAP, even though I have configured caching thru Weblogic console? Can any one point me if they have experienced this before and let me know how to solve this or can anyone point me to a place hwere it tells clearly how to turn on caching LDAP requests on the Weblogic side so that I can save precious network calls?
    Seetharaman

    WebLogic packages these "asm" classes within one of its internal JARs. The issue is easily solved if you insert Hibernate's "cglib" library before WebLogic JARs in the server classpath. Something like this:
    set HIB_PATCH=D:\bea9\weblogic90\server\bc_patch\cglib-full-2.0.2.jar
    set CLASSPATH=%HIB_PATCH%;%CLASSPATH%
    Worked beautifully for me. B-)

  • Weblogic Server cannot find Service accounts  in my MSAD via LDAP

    Hello,
    I've configured an LDAP security provider in my WebLogic server but it's only finding some of my users, not my "service account" users.
    The users are found in the following locations in the tree:
    OU=Users,OU=Accounts,DC=dev,DC=mtb,DC=com
    OU=Service,OU=Accounts,DC=dev,DC=mtb,DC=com
    So I configured the LDAP provider with the following settings:
    User Base DN: OU=Accounts,DC=dev,DC=mtb,DC=com
    All Users Filter: (blank)
    User from Name Filter: (&(cn=%u)(objectclass=user))
    User Search Scope: subtree
    User Name Attribute: cn
    User Object Class: user
    But it cannot find users in the "Service" node, only users in the "Users" node. Both users have CN=, and "user" as part of their objectClass string. Any idea what I might be missing?
    Thank you,
    -Ben

    Hi
    1. I hope you already created a datasource on Weblogic Side using weblogic admin console and create New Data Source. Create a data source preferably with this JNDI Name "jdbc/mydbDSDS". It can be anything, but standard is jdbc/whatevernameyouwant. Once data source is created, you give db details like host, port, sid, username/password. Then deploy to appropriate server(s) like using Targets screen. Once all done. Under your domain/config/jdbc, you should see a .xml file with some unique name that has all the datasource details. The jndi name tag should be like this: <jndi-name>jdbc/mydbDSDS</jndi-name>
    2. Now, edit your persistence.xml file to refer above jndi name. By default, I know, it adds that wierd name with jdbc/jdbc etc etc. But you can edit it always. Take a backup of your persistence.xml file and edit it to look like this.
      <persistence-unit name="mydbDS">
        <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
        <jta-data-source>jdbc/mydbDSDS</jta-data-source>
        <properties>
          <property name="eclipselink.target-server" value="WebLogic_10"/>
          <property name="eclipselink.cache.shared.default" value="false"/>
        </properties>
      </persistence-unit>
    </persistence>Save it. Redeploy and see how that goes. The above file is simplified version. What it means is, just refer already deployed data source whose jndi name is "jdbc/mydbDSDS". If you really have some extra properties, you can retain them. Otherwise they are not required.
    Thanks
    Ravi Jegga

  • Issue while integrating external LDAP with weblogic

    Hi,
    i am trying integrating external LDAP (OpenLdap) with weblogic 10.3. I created a provider and provided required credentials and able to see users and group of the LDAP into the weblogic console. I am also able to login in the weblogic console with the users available in the LDAP after assigning the admin role to the ldap group. But i when i see the user's property (by clicking on the user in the admin console) it only shows the tabs for General, Password and Group only. on the other hand if i see the users from DefaultAuthenticator, it shows the Attribute tab apart from the General, Password and Group.
    Can anyone let me knwo how can we get the Attribute tab for the Ldap users.
    thx,
    Ajay

    Hi Ajay
    By default Weblogic has READ ONLY adapters for any External Security Providers that are configured like any AD Providers. READ ONLY means, you can only read the data from the ldap but not modify it, hence may be its not showing the Attributes tag. For Default Authenticator, see the first paragraph note in Attributes tab, that says the same thing. NOW, may be WLS can atleast show Attributes in READ only format, but it needs some sort of mappings to be defined. Say on Weblogic side, we have like firstName, lastName which on any typical AD will be like sn (surname = lastname), givenname (firstname) etc etc. This mapping is tough to generalize.
    One thing for sure is, from Weblogic you cannot modify or edit any attributes for any user in external AD. If you really want to get those attributes, you may need to use some javax.ldap apis or some 3rd party ready to use tools/apis. I remember Weblogic Portal has a facility to configure a xml file that defines attributes mapping and get all attributes for any user. But again thats in Weblogic Portal product and not part of weblogic server.
    If you have any SOA Software, they have some utilities for the same.
    Thanks
    Ravi Jegga

  • Jolt for weblogic (5.1) and encryption ?

    Hi.
    I'm trying to use encryption between Jolt for Weblogic clients and Jolt servers
    (JSL/JSH), but I can't get it work.
    The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo 6.5 Security
    add-on is installed. Everything works fine without the "-Z" option.
    However, the Jolt client, while connecting to JSL, always catches a SessionException
    with the following message:
    Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr: open: J_DH
    Bad Reply
    and nothing is logged on the server side...
    Is there something to configure or install on client (i.e. weblogic) side ? Has
    anyone already succeeded in using Jolt's encryption ?
    Any help welcome...
    PS: I have posted this question on several groups, as far as it seems that nobody
    knows about Jolt's encryption...

    Hi Mathieu,
    You may need to install a Tuxedo rolling patch. You need at least:
    Tuxedo 6.4 Rolling Patch level 210,
    Tuxedo 6.5 rolling patch level 47,
    see the following CR:
    CR016914 (Jolt only) DiffieHellman Key exchange for Jolt
    Also, you may need to have WLS SP 10 installed in order to use
    40-bit encryption. See CR 45413 with additional information in the Service
    Pack release notes.
    CR 45413: Added an international version of Jolt client which is required to talk
    with International Tuxedo.
    Scott Lynch
    Michael Young <[email protected]> wrote:
    Hi.
    Try posting this to one or both of the following newsgroups:
    weblogic.developer.interest.general or tuxedo.general. If you get no
    response then I
    suggest you open a case with BEA support.
    Thanks,
    Michael
    Mathieu Chauvin wrote:
    Hi.
    I'm trying to use encryption between Jolt for Weblogic clients andJolt servers
    (JSL/JSH), but I can't get it work.
    The JSL's "-Z" option is set to 40, and it boots without errors. Tuxedo6.5 Security
    add-on is installed. Everything works fine without the "-Z" option.
    However, the Jolt client, while connecting to JSL, always catches aSessionException
    with the following message:
    Reason:NwHdlr: open: J_DH Bad Reply\nbea.jolt.JoltException: NwHdlr:open: J_DH
    Bad Reply
    and nothing is logged on the server side...
    Is there something to configure or install on client (i.e. weblogic)side ? Has
    anyone already succeeded in using Jolt's encryption ?
    Any help welcome...
    PS: I have posted this question on several groups, as far as it seemsthat nobody
    knows about Jolt's encryption...--
    Developer Relations Engineer
    BEA Support

  • Weblogic Data source list in adf

    Hi Gurus,
    I am using jdev 11.1.2.3 and weblogic 10.3.6. I want to get list of all data sources available in the weblogic from adf.
    Thanks in advance

    You'll need to find the Java API that will let you access this from the WebLogic side.
    This might be a good start:
    http://docs.oracle.com/cd/E28280_01/web.1111/e13737/config.htm#i1069587

  • Weblogic stress test

    Hi,
    I have a forms 11g applications that have been installed on an HP ProLiant DL360 G7 (64GB)
    with Oracle Weblogic 1.0.3.3 64 Bit / Oracle Fusion Middleware 11.1.1.3 64 Bit(RHEL 5.5 64-Bit).
    I guess the machine is not bad for 300-400 concurrent users.
    Some tests have been done by few users (10-20), and all works fine so far.
    We are planing to do 1-2 hours tests with more users , around 100.
    Could someone give some advices about which checks should be done or what should be monitored during the tests ?
    any ideas are welcome.
    Best Regards
    Frane

    Hi Frane,
    The list is quite long but finds below the most critical performance items you should monitor during your load test exercise:
    ## Physical server and OS related
    -     CPU utilization
    -     Physical memory
    -     Disk performance and paging activity
    -     Java process memory size of your 64-bit VM (also important to monitor C Heap size of your Java process, check for any native memory leak over time etc.) and look at your physical RAM requirement per Java process under peak load
    ## JRE
    -     Java Heap utilization / footprint
    -     PermGen space utilization / footprint (if using HotSpot VM)
    -     Native memory / C Heap utilization (monitoring technique will depend of your OS)
    -     Garbage collection performance/elapsed time/frequency etc.
    ## Weblogic side
    -     Threads utilization
    -     JDBC Data Source utilization and leak verification (if applicable)
    -     HttpSession utilization (if applicable)
    -     EJB/MDB pool bean utilization (if applicable)
    -     JMS queue utilization (if applicable)
    - Cluster performance e.g. look for any packet loss etc. (if applicable)
    -     Socket / File Descriptor utilization (via netstat / lsof commands)
    ## Other recommendations
    -     A few Thread Dump snapshots should be captured during peak load and analysed; especially if high thread utilization is observed
    -     Heap Dump could be generated before, during and after load test in order to understand your application Java Heap footprint and ensure no leak
    -     If using Oracle database, AWR reports should be generated during your load test and investigate any SQL contention / tuning opportunity such as sub optimal execution plan, lack of proper indexes etc.
    - Negative testing should be added for 1 or 2 load testing cycles in order to simulate TX slowdown and physical downtime of one or many of your downstream system should be done along with timeout validation (ensure no infinite hanging Thread and domino effect)
    On top of this, you should track your application business response time and compare between each cycle.
    Your load testing strategy should include an initial run to capture a baseline, each tuning or change applied should be then compared to your initial baseline in order to validate any improvement or degradation of any performance figure.
    Regards,
    P-H
    http://javaeesupportpatterns.blogspot.com/

  • Root exception is weblogic.rjvm.PeerGoneException:

    I have a problem doing the Look onto the Weblogic server.
              Here is the code I use in a method for this purpose and call the
              method from main(). I paste the code below (enclosed within "CODE
              BEGINS", "CODE ENDS")
              -----------------CODE BEGINS-----------------------------------------
                   System.out.println("DataCollector : Look up serverHome called");
                   Hashtable props = new Hashtable();
                   props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
                   props.put(Context.PROVIDER_URL, url);
                   props.put(Context.SECURITY_PRINCIPAL, userName);
                   props.put(Context.SECURITY_CREDENTIALS, passWord);
                   System.out.println("Before Inital Context "+props);
                   Context ctx = new InitialContext(props);
                   System.out.println("Initial Context successful");
                   serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
                   System.out.println("Look up successful");
                   ctx.close();
                   System.out.println("Closed context successfully");
              -----------------CODE ENDS-----------------------------------------
              On executing this piece of code, I receive the following Exceptions
              -------------OUTPUT OF CODE BEGINS---------------------
              DataCollector : Look up serverHome called
              Before Inital Context
              {java.naming.provider.url=T3://njecomprod06:10817,
              java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
              java.naming.security.principal=system,
              java.naming.security.credentials=security}
              Initial Context successful
              Exception in thread "main" javax.naming.CommunicationException. Root
              exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
              java.io.EOFException
              java.io.EOFException
              at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
              at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
              at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              -------------OUTPUT OF CODE ENDS---------------------
              This piece of code fails in the line
              serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              The weblogic server is standalone (not on a cluster). All other
              details give for this purpose like port no, username, password etc are
              correct.
              Also, On the WebLogic server prompt, the following stack trace is
              printed. Please let me know what is wrong in this look up code
              element.
              Thanks in advance for your help.
              -------------------------------------------------------EXCEPTION ON
              WEBLOGIC SIDE BEGINS--------------------------
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ] - with nested exception:
              [java.io.EOFException]
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              <Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
              <Uncaught Throwable in processSockets
              java.io.EOFException:
              Start server side stack trace:
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ]
              Start server side stack trace:
              java.io.EOFException
              at java.io.DataInputStream.readInt(DataInputStream.java:343)
              at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              --------------- nested within: ------------------
              weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              creating response stream ] - with nested exception:
              [java.io.EOFException]
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              - with nested exception:
              [java.io.EOFException:
              Start server side stack trace:
              java.io.EOFException
                      at java.io.DataInputStream.readInt(DataInputStream.java:343)
                      at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
                      at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
                      at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
                      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
                      at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
                      at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
                      at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
                      at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
                      at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
                      at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
                      at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
                      at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
                      at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
                      at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                      at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End  server side stack trace
              at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              -------------------------------------------------------EXCEPTION ON
              WEBLOGIC SIDE ENDS--------------------------
              

    You may want to open a support case with BEA to resolve this issue. I
              suspect that you may be using some server patches which have not also
              been applied to your WebLogic client JVMs. If that is the case,
              upgrading to the latest service pack may be the easiest and best remedy.
              Sincerely,
              Charlie Therit
              Developer Relations Engineer
              BEA Support
              Lakshmi Narasimhan wrote:
              >I have a problem doing the Look onto the Weblogic server.
              >
              >Here is the code I use in a method for this purpose and call the
              >method from main(). I paste the code below (enclosed within "CODE
              >BEGINS", "CODE ENDS")
              >
              >
              >-----------------CODE BEGINS-----------------------------------------
              >{
              >     System.out.println("DataCollector : Look up serverHome called");
              >     Hashtable props = new Hashtable();
              >     props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
              >     props.put(Context.PROVIDER_URL, url);
              >     props.put(Context.SECURITY_PRINCIPAL, userName);
              >     props.put(Context.SECURITY_CREDENTIALS, passWord);
              >     System.out.println("Before Inital Context "+props);
              >     Context ctx = new InitialContext(props);
              >     System.out.println("Initial Context successful");
              >     serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              >     System.out.println("Look up successful");
              >     ctx.close();
              >     System.out.println("Closed context successfully");
              >}
              >-----------------CODE ENDS-----------------------------------------
              >
              >On executing this piece of code, I receive the following Exceptions
              >
              >-------------OUTPUT OF CODE BEGINS---------------------
              >DataCollector : Look up serverHome called
              >Before Inital Context
              >{java.naming.provider.url=T3://njecomprod06:10817,
              >java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory,
              >java.naming.security.principal=system,
              >java.naming.security.credentials=security}
              >Initial Context successful
              >
              >Exception in thread "main" javax.naming.CommunicationException. Root
              >exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
              >java.io.EOFException
              >java.io.EOFException
              > at weblogic.rjvm.t3.T3JVMConnection.endOfStream(T3JVMConnection.java:599)
              > at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:303)
              > at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:225)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >-------------OUTPUT OF CODE ENDS---------------------
              >
              >This piece of code fails in the line
              >
              >serverHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
              >
              >The weblogic server is standalone (not on a cluster). All other
              >details give for this purpose like port no, username, password etc are
              >correct.
              >
              >Also, On the WebLogic server prompt, the following stack trace is
              >printed. Please let me know what is wrong in this look up code
              >element.
              >
              >Thanks in advance for your help.
              >
              >-------------------------------------------------------EXCEPTION ON
              >WEBLOGIC SIDE BEGINS--------------------------
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ] - with nested exception:
              >[java.io.EOFException]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              ><Oct 25, 2002 10:57:04 AM EDT> <Error> <Posix Performance Pack>
              ><Uncaught Throwable in processSockets
              >java.io.EOFException:
              >Start server side stack trace:
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End server side stack trace
              >
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ]
              >
              >Start server side stack trace:
              >java.io.EOFException
              > at java.io.DataInputStream.readInt(DataInputStream.java:343)
              > at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              > at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              > at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              > at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              > at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >--------------- nested within: ------------------
              >weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Exception
              >creating response stream ] - with nested exception:
              >[java.io.EOFException]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End server side stack trace
              > - with nested exception:
              >[java.io.EOFException:
              >Start server side stack trace:
              >java.io.EOFException
              >        at java.io.DataInputStream.readInt(DataInputStream.java:343)
              >        at java.io.ObjectInputStream.readInt(ObjectInputStream.java:1980)
              >        at weblogic.rmi.internal.MethodDescriptor.readExternal(MethodDescriptor.java:333)
              >        at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1212)
              >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
              >        at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
              >        at weblogic.rjvm.InboundMsgAbbrev.readObject(InboundMsgAbbrev.java:66)
              >        at weblogic.rjvm.InboundMsgAbbrev.read(InboundMsgAbbrev.java:38)
              >        at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:175)
              >        at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              >        at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              >        at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              >        at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              >        at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              >        at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              >        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              >        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >End  server side stack trace
              >]
              > at weblogic.rjvm.MsgAbbrevJVMConnection.readMsgAbbrevs(MsgAbbrevJVMConnection.java:184)
              > at weblogic.rjvm.MsgAbbrevInputStream.readMessageContext(MsgAbbrevInputStream.java:154)
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:579)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
              > at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
              > at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              >
              >
              >
              >-------------------------------------------------------EXCEPTION ON
              >WEBLOGIC SIDE ENDS--------------------------
              >
              >
              [att1.html]
              

  • Weblogic Deploy rcf-dvt-demo.war(version 11.1.1.5)

    Hello,
    Jdevstudio11115install.exe Weblogic side, and then I installed the RCF-DVT-demo.war (11.1.1.5), deploy and when I start did I receive the following error.
    weblogic.management.DeploymentException: Error: Unresolved WebApp Library references for "ServletContext @ 1580099636 [app: RCF-DVT-demo.11.1.1.5 module: RCF-DVT-demo_11.1.1.5.war path: / faces-trunk spec-Version: 2.5] ", defined in weblogic.xml [Extension-Name: JSTL, Specification-Version: 1.2, exact-match: false], [Extension-Name: jsf, Specification-Version: 1.2, exact-match: false]
    How can I solve this error.
    Edited by: 889612 on 14.Kas.2011 02:10

    looks like you didn't install the application development runtime on WLS, or if you did, you either forgot to extend your domain with the JRF or installed the wrong version of the application development runtime.

Maybe you are looking for

  • Need example report program using PNPCE LDB in SAP HR

    Need example report program using PNPCE LDB in SAP HR. and how to create a report category in sap hr for using it as cutomised selection screen.

  • Converting PDF file to Word document

    How do I convert a pdf file to a word document using Adobe Download Assistant free version?

  • How do I parse for the 2nd CN in a line?

    Hi, Via Powershell, I list all my NTDS Settings Objects with some properties, but out of the Distinguished Name I just want the 2nd CN which contains the Server Name.  I just do a Get-Adobject on the Objectclass of nTDSDSA to get this data, so how wo

  • How to add a Button on SUS top-right corner ( Near Log off button)

    Hi Experts, It's a bit urgent for me. Please give your valuable suggestions to achieve below scenario. My requirement is :- adding a button on top-right corner(near log-off button) of SUS screen. when that button is clicked, a pop-up should appear, w

  • How long is the shuffle warranty?

    I don't know if mine has ever worked properly, always have that little orange light flashing but have been able to update etc, up till now. Now my imac doesn't recognize it anymore so I can't update. Bought it April 2005. Too late?