InitialContextFactory

Hi,
I have a Weblogic Server 6.1 SP1 on a SunOS Machin, and I test the StatelessSession EJB, but the client doesn t work on the client machin
I test on a NT client machin, and I have this exception.
/////////Code
Context ctx = null ;
Properties h = new Properties();
h.put(Context.PROVIDER_URL, url);
h.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
try {
     ctx = new InitialContext(h);
catch(Exception e)
     e.printStackTrace() ;
Object objRef = ctx.lookup(JNDI_NAME);
TraderHome home = (TraderHome) narrow(objRef, TraderHome.class);
//////////Exception
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory. Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at examples.ejb.basic.statelessSession.Client.bigFunction(Client.java:351)
at examples.ejb.basic.statelessSession.Client.<init>(Client.java:58)
at examples.ejb.basic.statelessSession.Client.main(Client.java:90)
Is it necessary to copy the weblogic.jar on the client machin ?
If it exists another way to execute the client, could U help me ?
Thanks.

the WLInitialContextFactory class should be in your classpath, in other words the jar file should be in the classpath of the machine running the code that references this class. it is best to put that code into a class on the server and have the client make a call to this class. typically a generic factory type of class.
here's some psuedocode to do this:
public class EJBFactory {
     /** constructor made private to prevent instantiation */
     private EJBFactory() {}
     public static void findEJBHome(String sJNDIName) {
          // get the intitial context by calling the method below
          // use the initial context & the jndi name passed in
          // look up the bean
          // once the home is obtained the remote can be
          // created by using reflection
     public static InitiaContext getInitialContext() {
          // do the WLInitialContext thing here
          // and return the initial context
}

Similar Messages

  • InitialContextFactory to connect from java to OID

    Hi,
    I have a problem to connect from my application java to OID, I was using the following InitialContextFactory in my code in this way:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
    env.put(Context.PROVIDER_URL, "ormi://192.168.3.112:3061/dn=fedco,dn=com");
    but it gives back the following error to me:
    Problem looking up : javax.naming.NamingException: META-INF/application-client.xml resource not found (see J2EE spec, application-client chapter for requirements and format of the file).
    I have been looking for about the xml files but I have found that they are necessary when one works with EJBs which is not my case, I need to know if I am using the appropriate InitialContextFactory or if another one is the appropriate for this case.
    Please, help me.
    Thanks.

    Hi there,
    You are definately using the incorrect InitialContextFactory. The com.evermind.server.ApplicationClientInitialContextFactory is intended for Standalone Java clients that require access to remote EJBs AND have been configured with a client-application.xml file.
    Try the following:
    //Setup intial context for OID server
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory");
    env.put(Context.PROVIDER_URL, ldapURL);
    env.put(Context.SECURITY_AUTHENTICATION, "none");
    env.put(Context.SECURITY_PRINCIPAL, dn);
    // Anonymous bind to create the intial context
    try
    dirCtx = new InitialDirContext(env);
    log.debug("New LDAP context created " + dirCtx);
    catch (NamingException ne)
    log.error("Failed to create InitialContext for LDAP server:", ne);
    throw new RuntimeException("LDAP server is not available");
    Where ldapURL is "ldap://<host>:<port>" and dn is the OID content you are interested in e.g. "dc=site,dc=company,dc=com".
    Hope this helps.
    Cheers,
    Sepand

  • I need an suitable InitialContextFactory to connect from java to OID

    Hi,
    I have a problem to connect from my application java to OID, I was using the following InitialContextFactory in my code in this way:
    Hashtable env = new Hashtable();
    env.put(Context.INITIAL_CONTEXT_FACTORY,           "com.evermind.server.ApplicationClientInitialContextFactory");
    env.put(Context.PROVIDER_URL, "ormi://192.168.3.112:3061/dn=fedco,dn=com");
    but it gives back the following error to me:
    Problem looking up : javax.naming.NamingException: META-INF/application-client.xml resource not found (see J2EE spec, application-client chapter for requirements and format of the file).
    I have been looking for about the xml files but I have found that they are necessary when one works with EJBs which is not my case, I need to know if I am using the appropriate InitialContextFactory or if another one is the appropriate for this case.
    Please, help me.
    Thanks.

    Hi,
    Have a look at my response to this thread :InitialContextFactory to connect from java to OID
    Let me know how you go.
    Cheers,
    Sepand

  • ClassNotFoundException: trying to load OC4J JNDI InitialContextFactory

    Hello!
    Trying to make a call to an EJB deployed in OCJ4 from a oracle java stored proc. After loaded orion.jar and crimson.jar lib into SCOTT schema, I can't get the JNDI Context working because of this error:
    ============================================
    javax.naming.NoInitialContextException: Cannot instantiate class:
    com.evermind.server.ApplicationClientInitialContextFactory. Root exception is
    java.lang.ClassNotFoundException:
    com/evermind/server/ApplicationClientInitialContextFactory
    at java.lang.Class.forName0(Class.java)
    at java.lang.Class.forName(Class.java)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:45)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java)
    at javax.naming.InitialContext.init(InitialContext.java)
    at javax.naming.InitialContext.<init>(InitialContext.java)
    ===============================
    I did load the java with "loadjava" with on time with the "resolve" option and time time no option and still no working.
    Here is the EJB client code:
    =======================================
    import java.sql.*;
    import java.util.*;
    import javax.naming.*;
    import com.evermind.server.ApplicationClientInitialContextFactory;
    class EmpRemoteCall {
    public static void main(String[] args) {
    System.out.println(getEmpName());
    public static String getEmpName() {
    String ejbUrl = "java:comp/env/ejb/Emp";
    String username = "admin";
    String password = "admin";
    Hashtable environment = new Hashtable();
    environment.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.ApplicationClientInitialContextFactory");
    environment.put(Context.PROVIDER_URL, "ormi://127.0.0.1/testemp");
    environment.put(Context.SECURITY_PRINCIPAL, username);
    environment.put(Context.SECURITY_CREDENTIALS, password);
    //environment.put(Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
    //environment.put(javax.naming.Context.URL_PKG_PREFIXES, "oracle.aurora.jndi");
    com.kboum.sertir.essais.EmpHome homeInterface = null;
    try {
    Class.forName("com.evermind.server.ApplicationClientInitialContextFactory", true, ClassLoader.getSystemClassLoader());
    System.out.println("Creating an initial context");
    Context ic = new InitialContext(environment);
    System.out.println("Looking for the EJB published as 'java:comp/env/ejb/Emp'");
    homeInterface = (com.kboum.sertir.essais.EmpHome) ic.lookup(ejbUrl);
    catch (CommunicationException e) {
    System.out.println("Unable to connect: " + ejbUrl);
    e.printStackTrace();
    //System.exit(1);
    catch (NamingException e) {
    System.out.println("Exception occurred!");
    System.out.println("Cause: This may be an unknown URL, or some" +
    " classes required by the EJB are missing from your classpath.");
    System.out.println("Suggestion: Check the components of the URL," +
    " and make sure your project includes a library containing the" +
    " EJB .jar files generated by the deployment utility.");
    e.printStackTrace();
    //System.exit(1);
    catch (ClassNotFoundException e) {
    System.out.println("Unable to connect: " + ejbUrl);
    e.printStackTrace();
    //System.exit(1);
    try {
    System.out.println("Creating a new EJB instance");
    com.kboum.sertir.essais.Emp remoteInterface = homeInterface.findByPrimaryKey(Integer.valueOf("7369"));
    System.out.println(remoteInterface.getENAME());
    System.out.println(remoteInterface.getSAL());
    remoteInterface.setSAL(2);
    System.out.println(remoteInterface.getSAL());
    return remoteInterface.getENAME();
    catch (Exception e) {
    System.out.println(e.getMessage());
    e.printStackTrace();
    return "error";
    }

    Is there a way to add jar libraries to the Oracle JVM CLASSPATH? Is this the same as the system's CLASSPATH env. variable?
    Thank you!
    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Alex McClennan ([email protected]):
    The package prefix in the code extract was correct - i.e. "oracle.aurora.jndi". A value of "oracle.aurora.jndi.*" would be incorrect.
    The problem is that the context factory implementation specified (com.evermind.server.ApplicationClientInitialContextFactory
    ) can't be found, the mostly likely reason being that the library containing the class isn't on the classpath.
    Cheers,
    ax<HR></BLOCKQUOTE>
    null

  • How to get InitialContextFactory using RMI/IIOP without using weblogic.jar

    Hi Robert
    I know this is an old post. but I am interested in knowing how to get the
    initial context using RMI/IIOP without the use weblogic specific classes
    like weblogic.jndi.WLInitialContextFactory . If you have a code snippet that
    you can provide as an example, it would be just great.
    thanx in advance
    Daya Sharma
    See comments inline...
    Stewart Wachs wrote:
    I would like to get an initial context to Weblogic JNDI from a client.
    code snippet:
    Hashtable ht = new Hashtable();
    ht.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFacorty");
    ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
    try {
    Context ctx = new InitialContext(ht);
    catch(...) {
    This works fine when I include weblogic.jar (and other dependend weblogic
    jar's) in the classpath.
    Is there a way to access WL JNDI from a client without the weblogicclasses
    in the classpath?If you are using WLS 6.1, you could use RMI/IIOP to do this but in general,
    the
    answer is no, you will need at least some of the weblogic classes on the
    client.
    If not, is there a lightweight jar available for distribution for client
    JNDI connectivity?This is something in the works. In addition, a colleague and I are working
    on
    a white paper that describes the "Thin Client Options with WebLogic Server"
    that we hope to make available in the not too distant future...
    Are there any licencing issues with distributing the weblogic classes to
    clients that need to access WL JNDI?No. WLS is licensed by the server so you are free to distribute
    weblogic.jar
    to your clients.
    Hope this helps,
    Robert

    Take a look at the RMI/IIOP section of our whitepaper "Small Footprint
    Client options for BEA WebLogic Server" at:
    http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
    Daya Sharma wrote:
    Hi Robert
    I know this is an old post. but I am interested in knowing how to get the
    initial context using RMI/IIOP without the use weblogic specific classes
    like weblogic.jndi.WLInitialContextFactory . If you have a code snippet that
    you can provide as an example, it would be just great.
    thanx in advance
    Daya Sharma
    See comments inline...
    Stewart Wachs wrote:
    I would like to get an initial context to Weblogic JNDI from a client.
    code snippet:
    Hashtable ht = new Hashtable();
    ht.put(Context.INITIAL_CONTEXT_FACTORY,
    "weblogic.jndi.WLInitialContextFacorty");
    ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
    try {
    Context ctx = new InitialContext(ht);
    catch(...) {
    This works fine when I include weblogic.jar (and other dependend weblogic
    jar's) in the classpath.
    Is there a way to access WL JNDI from a client without the weblogic
    classes
    in the classpath?
    If you are using WLS 6.1, you could use RMI/IIOP to do this but in general,
    the
    answer is no, you will need at least some of the weblogic classes on the
    client.
    If not, is there a lightweight jar available for distribution for client
    JNDI connectivity?
    This is something in the works. In addition, a colleague and I are working
    on
    a white paper that describes the "Thin Client Options with WebLogic Server"
    that we hope to make available in the not too distant future...
    Are there any licencing issues with distributing the weblogic classes to
    clients that need to access WL JNDI?
    No. WLS is licensed by the server so you are free to distribute
    weblogic.jar
    to your clients.
    Hope this helps,
    Robert

  • URGENT: Cannot create InitialContextFactory

    We are building an RMI Framework on Weblogic 6.1 sp1. However, for some
    reason I am now even unable to run my sample RMI Hello programs to run. This
    is the kind of error I keep getting for any access to Weblogic (currently
    running locally on Win 2000)
    I was successfully executing this and my own programs, however I do have a
    gut feeling it is dealing with some sort of SecurityManger issue setting.
    C:\bea\wlserver6.1\config\examples\clientclasses>java
    examples.rmi.hello.HelloClient 127.0.0.1 7001
    javax.naming.NoInitialContextException: Cannot instantiate class:
    weblogic.jndi.WLInitialContextFactory. Root exception is
    java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:195)
    at
    com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:45)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
    at javax.naming.InitialContext.init(InitialContext.java:222)
    at javax.naming.InitialContext.<init>(InitialContext.java:198)
    at
    examples.rmi.hello.HelloClient.getInitialContext(HelloClient.java:68)
    at examples.rmi.hello.HelloClient.main(HelloClient.java:48)
    Can somebody please help !!
    Thanks a lot!
    Chirag Shah

    Did you set your client classpath with weblogic.jar in it? Try running
    java -classpath path_to_weblogic.jar;%classpath%
    examples.rmi.hello.HelloClient 127.0.0.1 7001
    Chirag Shah wrote:
    We are building an RMI Framework on Weblogic 6.1 sp1. However, for some
    reason I am now even unable to run my sample RMI Hello programs to run. This
    is the kind of error I keep getting for any access to Weblogic (currently
    running locally on Win 2000)
    I was successfully executing this and my own programs, however I do have a
    gut feeling it is dealing with some sort of SecurityManger issue setting.
    C:\bea\wlserver6.1\config\examples\clientclasses>java
    examples.rmi.hello.HelloClient 127.0.0.1 7001
    javax.naming.NoInitialContextException: Cannot instantiate class:
    weblogic.jndi.WLInitialContextFactory. Root exception is
    java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:297)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:253)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:195)
    at
    com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:45)
    at
    javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at
    javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
    at javax.naming.InitialContext.init(InitialContext.java:222)
    at javax.naming.InitialContext.<init>(InitialContext.java:198)
    at
    examples.rmi.hello.HelloClient.getInitialContext(HelloClient.java:68)
    at examples.rmi.hello.HelloClient.main(HelloClient.java:48)
    Can somebody please help !!
    Thanks a lot!
    Chirag Shah--
    Rajesh Mirchandani
    Developer Relations Engineer
    BEA Support

  • How specify a diff. InitialContextFactory to WL 6.1 ?

    When I write new InitialContext(), the WL factory is used. But why? I passed -Djava.naming.initial.factory=xxx
    to java, I have also made a jndi.properties in the JAVA_HOME/lib and in a place
    in the application classpath. The server ignores these three and still uses the
    WL factory. I can only persuade it to use xxx by System.setProperty("java.naming.factory",
    "xxx") in the code.
    How does the server get its "java.naming.factory" setting?

    Downloading is not supported at all.  Doing so will void your warranty and forfeit your access to any further help from Apple including this forum.

  • InitialContextFactory class

    I try writing JUnit test for my EJB in SJSE 8. I use JNDI to find my bean:
    Hashtable env=new Hashtable();
                env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
                javax.naming.Context c = new javax.naming.InitialContext(env);
                Object remote = c.lookup("java:comp/env/ejb/SayHalloBean");
                com.roko.ejb.SayHalloRemoteHome rv = (com.roko.ejb.SayHalloRemoteHome) javax.rmi.PortableRemoteObject.narrow(remote, com.roko.ejb.SayHalloRemoteHome.class);Which class should I use as InitialContextFactoryClass?

    SJSAS Developer's Guide contains useful information.
    Using a Stand-Alone Client to Access an EJB Component:
    http://docs.sun.com/source/819-0079/dgacc.html#wp1022105

  • Active directory copnnection problem

    Hi all,
    I try to connect to an Active Directory using JNDI but I'm not successfull. I always get the same error saying that my credentials are not valid. It seems that I have to use an UPN to connect, but I don't know how to use it. The usual parameter don't work. The UPN should be [email protected] where xxx is the domain. I'm going crazy, I've tried several stuff but unsuccessfully.
    Here is my initial config file:
    <config-file>
         <ldap>
              <initialContextFactory>com.sun.jndi.ldap.LdapCtxFactory</initialContextFactory>
              <providerUrl>ldap://luinternal.xxxxx.xxxxx:389/</providerUrl>
              <securityAuthentication>simple</securityAuthentication>
              <securityPrincipal>
                   <user>webtemp</user>
              </securityPrincipal>
              <securityCredentials>Password0123456789</securityCredentials>
              <ldapVersion>3</ldapVersion>
         </ldap>
    </config-file>Thiss does not work, I get an error 49.
    I've tried to change webtemp to webtemp@[email protected] but this does not work as well.
    I'm also using ldap browser v2.8.2, a Java client, to test my connections.
    Hope you can help me.
    Cheers :)

    I have no idea what application is using this configuration, nor how it uses the credentials to bind to Active Directory.
    However from a pure LDAP perspective, you can use three forms of user name to perform a simple bind.
    1. Distinguished Name
    cn=John Smith, OU=Scientists,DC=Antgipodes,DC=Com
    2. NT style domain name
    ANTIPODES\jsmith
    3. User Principal Name
    [email protected]
    In your example, if you wanted to use the userPrincipalName, I can only guess that it will be [email protected]

  • Why josso has no DataSource Credential Store?

    Hello everyone,
    Do you take care of studying the josso-gateway-config.xml and find the Credential Stroe block is lacking of a way to store the username/passport pairs by DataSource?
    this is the josso-gateway-config.xml listed as below:
    <?xml version="1.0" encoding="ISO-8859-1" ?>
    <!--
    ~ Copyright (c) 2004-2006, Novascope S.A. and the JOSSO team
    ~ All rights reserved.
    ~ Redistribution and use in source and binary forms, with or
    ~ without modification, are permitted provided that the following
    ~ conditions are met:
    ~
    ~ * Redistributions of source code must retain the above copyright
    ~ notice, this list of conditions and the following disclaimer.
    ~
    ~ * Redistributions in binary form must reproduce the above copyright
    ~ notice, this list of conditions and the following disclaimer in
    ~ the documentation and/or other materials provided with the
    ~ distribution.
    ~
    ~ * Neither the name of the JOSSO team nor the names of its
    ~ contributors may be used to endorse or promote products derived
    ~ from this software without specific prior written permission.
    ~
    ~ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
    ~ CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
    ~ INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
    ~ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
    ~ DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
    ~ BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
    ~ EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
    ~ TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
    ~ DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
    ~ ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
    ~ OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
    ~ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
    ~ POSSIBILITY OF SUCH DAMAGE.
    -->
    <domain>
    <name>JOSSO</name>
    <type>web</type>
    <!--sso-web-config-->
    <!-- Optional : The URL where the user will be redirected after a successfull login only if josso_back_to request parameter
    is not present when accessing the login url
    <loginBackToURL>http://localhost:8080/partnerapp/protected/</loginBackToURL>
    -->
    <!-- Optional : The URL where the user will be redirected after a logout only if josso_back_to is not present
    when accessing the logout url
    <logoutBackToURL>http://localhost:8080/partnerapp/protected/</logoutBackToURL>
    -->
    <!-- Session token properties -->
    <!--session-token-->
    <!-- Optional : Use a secure session token, a secure channel like SSL must be available for this to work
    <secure>false</secure>
    -->
    <!--/session-token-->
    <!--/sso-web-config-->
    <authenticator>
    <class>org.josso.auth.AuthenticatorImpl</class>
    <authentication-schemes>
    <!-- Basic Authentication Scheme -->
    <authentication-scheme>
    <name>basic-authentication</name>
    <class>org.josso.auth.scheme.UsernamePasswordAuthScheme</class>
    <!--
    The message digest algorithm to be used when hashing passwords.
    This must be an algorithm supported by the java.security.MessageDigest class
    on your platform.
    In J2SE 1.4.2 you can check :
    Java Cryptography Architecture API Specification & Reference - Apendix B : Algorithms
    Values are : MD2, MD5, SHA-1, SHA-256, SHA-384, SHA-512,etc.
    To provide LDAP support, also CRYPT is available.
    -->
    <hashAlgorithm>MD5</hashAlgorithm>
    <!-- Supported values are HEX, BASE64. Mandatory if hashAlgorithm was specified -->
    <hashEncoding>HEX</hashEncoding>
    <!-- Some hash algorithms, like CRYPT, use this property. The default value is 2.
    <saltLength>2</saltLength>
    -->
    <ignorePasswordCase>false</ignorePasswordCase>
    <ignoreUserCase>false</ignoreUserCase>
    <!-- ========================================================= -->
    <!-- JDBC Credential Store -->
    <!-- -->
    <!-- Always scape comma chars [,] in queries because -->
    <!-- jakarta commons-configuration uses them to define arrays. -->
    <!-- ========================================================= -->
    <!--
    <credential-store>
    <class>org.josso.gateway.identity.service.store.db.JDBCIdentityStore</class>
    <credentialsQueryString>
    SELECT login AS username , password AS password FROM josso_user WHERE login = ?
    </credentialsQueryString>
    <connectionName>josso</connectionName>
    <connectionPassword>josso</connectionPassword>
    <connectionURL>jdbc:oracle:thin:@localhost:1521:josso_db</connectionURL>
    <driverName>oracle.jdbc.driver.OracleDriver</driverName>
    </credential-store>
    <credential-store>
    <class>org.josso.gateway.identity.service.store.db.DataSourceIdentityStore</class>
    <credentialsQueryString>SELECT login AS username , password AS password FROM josso_user WHERE login = ?</credentialsQueryString>
    <dsJndiName>java:jdbc/JossoSamplesDB</dsJndiName>
    </credential-store>
    -->
    <!-- =============================================================== -->
    <!-- LDAP Credential Store -->
    <!-- -->
    <!-- Chcek javadoc for configuration details : -->
    <!-- org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore -->
    <!-- =============================================================== -->
    <!--
    <credential-store>
    <class>org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore</class>
    <initialContextFactory>com.sun.jndi.ldap.LdapCtxFactory</initialContextFactory>
    <providerUrl>ldap://ldaphost</providerUrl>
    <securityPrincipal>cn=Manager,dc=my-domain,dc=com</securityPrincipal>
    <securityCredential>secret</securityCredential>
    <securityAuthentication>simple</securityAuthentication>
    <ldapSearchScope>SUBTREE</ldapSearchScope>
    <usersCtxDN>ou=People,dc=my-domain,dc=com</usersCtxDN>
    <principalUidAttributeID>uid</principalUidAttributeID>
    <rolesCtxDN>ou=Roles,dc=my-domain,dc=com</rolesCtxDN>
    <uidAttributeID>uniquemember</uidAttributeID>
    <roleAttributeID>cn</roleAttributeID>
    <credentialQueryString>uid=username,userPassword=password</credentialQueryString>
    <userPropertiesQueryString>mail=mail,cn=description</userPropertiesQueryString>
    </credential-store>
    -->
    <!-- ================================================= -->
    <!-- Memory Credential Store -->
    <!-- ================================================= -->
    <credential-store>
    <class>org.josso.gateway.identity.service.store.MemoryIdentityStore</class>
    <credentialsFileName>josso-credentials.xml</credentialsFileName>
    </credential-store>
    <!-- ================================================= -->
    <!-- Credential Store Key adapter -->
    <!-- ================================================= -->
    <credential-store-key-adapter>
    <class>org.josso.gateway.identity.service.store.SimpleIdentityStoreKeyAdapter</class>
    </credential-store-key-adapter>
    </authentication-scheme>
    <!-- Strong Authentication Scheme -->
    <authentication-scheme>
    <name>strong-authentication</name>
    <class>org.josso.auth.scheme.X509CertificateAuthScheme</class>
    <!-- ========================================================= -->
    <!-- JDBC Credential Store -->
    <!-- -->
    <!-- Always scape comma chars [,] in queries because -->
    <!-- jakarta commons-configuration uses them to define arrays. -->
    <!-- ========================================================= -->
    <!--
    <credential-store>
    <class>org.josso.gateway.identity.service.store.db.JDBCIdentityStore</class>
    <credentialsQueryString>
    SELECT login AS username , password AS password FROM josso_user WHERE login = ?
    </credentialsQueryString>
    <connectionName>josso</connectionName>
    <connectionPassword>josso</connectionPassword>
    <connectionURL>jdbc:oracle:thin:@localhost:1521:josso_db</connectionURL>
    <driverName>oracle.jdbc.driver.OracleDriver</driverName>
    </credential-store>
    -->
    <!-- =============================================================== -->
    <!-- LDAP Credential Store -->
    <!-- -->
    <!-- Chcek javadoc for configuration details : -->
    <!-- org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore -->
    <!-- =============================================================== -->
    <!--
    <credential-store>
    <class>org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore</class>
    <initialContextFactory>com.sun.jndi.ldap.LdapCtxFactory</initialContextFactory>
    <providerUrl>ldap://ldaphost</providerUrl>
    <securityPrincipal>cn=Manager,dc=my-domain,dc=com</securityPrincipal>
    <securityCredential>secret</securityCredential>
    <securityAuthentication>simple</securityAuthentication>
    <ldapSearchScope>SUBTREE</ldapSearchScope>
    <usersCtxDN>ou=People,dc=my-domain,dc=com</usersCtxDN>
    <principalUidAttributeID>uid</principalUidAttributeID>
    <rolesCtxDN>ou=Roles,dc=my-domain,dc=com</rolesCtxDN>
    <uidAttributeID>uniquemember</uidAttributeID>
    <roleAttributeID>cn</roleAttributeID>
    <credentialQueryString>uid=username,userCertificate;binary=userCertificate</credentialQueryString>
    <userPropertiesQueryString>mail=mail,cn=description</userPropertiesQueryString>
    </credential-store>
    -->
    <!-- ================================================= -->
    <!-- Memory Credential Store -->
    <!-- ================================================= -->
    <credential-store>
    <class>org.josso.gateway.identity.service.store.MemoryIdentityStore</class>
    <credentialsFileName>josso-credentials.xml</credentialsFileName>
    </credential-store>
    <!-- ================================================= -->
    <!-- Credential Store Key adapter -->
    <!-- ================================================= -->
    <credential-store-key-adapter>
    <class>org.josso.gateway.identity.service.store.SimpleIdentityStoreKeyAdapter</class>
    </credential-store-key-adapter>
    </authentication-scheme>
    </authentication-schemes>
    </authenticator>
    <sso-identity-manager>
    <class>org.josso.gateway.identity.service.SSOIdentityManagerImpl</class>
    <!-- ========================================================= -->
    <!-- DataSource Identity Store -->
    <!-- -->
    <!-- Always scape comma chars [,] in queries because -->
    <!-- jakarta commons-configuration uses them to define arrays. -->
    <!-- ========================================================= -->
    <!--
    <sso-identity-store>
    <class>org.josso.gateway.identity.service.store.db.DataSourceIdentityStore</class>
    <userQueryString>
    SELECT login FROM josso_user WHERE login = ?
    </userQueryString>
    <userPropertiesQueryString>
    SELECT 'user.description' AS name , description AS value FROM josso_user WHERE login = ?
    UNION
    SELECT name AS name , value AS value FROM josso_user_property WHERE login = ?
    </userPropertiesQueryString>
    <rolesQueryString>
    SELECT josso_role.name FROM josso_role , josso_user_role , josso_user WHERE josso_user.login = ? AND josso_user.login = josso_user_role.login AND josso_role.name = josso_user_role.name
    </rolesQueryString>
    <dsJndiName>java:jdbc/JossoSamplesDB</dsJndiName>
    </sso-identity-store>
    -->
    <!-- ========================================================= -->
    <!-- JDBC Identity Store -->
    <!-- -->
    <!-- Always scape comma chars [,] in queries because -->
    <!-- jakarta commons-configuration uses them to define arrays. -->
    <!-- ========================================================= -->
    <!--sso-identity-store>
    <class>org.josso.gateway.identity.service.store.db.JDBCIdentityStore</class>
    <userQueryString>
    SELECT login FROM josso_user WHERE login = ?
    </userQueryString>
    You could use a UNION to select properties from different tables/columns :
    SELECT 'user.lastName' AS name , lastName AS value FROM josso_user WHERE login = ?
    UNION
    SELECT 'user.name' AS name , name AS value FROM josso_user WHERE login = ?
    UNION
    SELECT name AS name , value AS value FROM josso_user_properties WHERE login = ?
    <userPropertiesQueryString>
    SELECT 'user.description' AS name , description AS value FROM josso_user WHERE login = ?
    UNION
    SELECT name AS name , value AS value FROM josso_user_property WHERE login = ?
    </userPropertiesQueryString>
    <rolesQueryString>
    SELECT josso_role.name FROM josso_role , josso_user_role , josso_user WHERE josso_user.login = ? AND josso_user.login = josso_user_role.login AND josso_role.name = josso_user_role.name
    </rolesQueryString>
    <connectionName>josso</connectionName>
    <connectionPassword>josso</connectionPassword>
    <connectionURL>jdbc:oracle:thin:@localhost:1521:josso_db</connectionURL>
    <driverName>oracle.jdbc.driver.OracleDriver</driverName>
    </sso-identity-store-->
    <!-- =============================================================== -->
    <!-- LDAP Identity Store -->
    <!-- -->
    <!-- Chcek javadoc for configuration details : -->
    <!-- org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore -->
    <!-- ================================================= -->
    <!--
    <sso-identity-store>
    <class>org.josso.gateway.identity.service.store.ldap.LDAPIdentityStore</class>
    <initialContextFactory>com.sun.jndi.ldap.LdapCtxFactory</initialContextFactory>
    <providerUrl>ldap://ldaphost</providerUrl>
    <securityPrincipal>cn=Manager,dc=my-domain,dc=com</securityPrincipal>
    <securityCredential>secret</securityCredential>
    <securityAuthentication>simple</securityAuthentication>
    <ldapSearchScope>SUBTREE</ldapSearchScope>
    <usersCtxDN>ou=People,dc=my-domain,dc=com</usersCtxDN>
    <principalUidAttributeID>uid</principalUidAttributeID>
    <rolesCtxDN>ou=Roles,dc=my-domain,dc=com</rolesCtxDN>
    <uidAttributeID>uniquemember</uidAttributeID>
    <roleAttributeID>cn</roleAttributeID>
    <credentialQueryString>uid=username,userPassword=password</credentialQueryString>
    <userPropertiesQueryString>mail=mail,cn=description</userPropertiesQueryString>
    </sso-identity-store>
    -->
    <!-- ================================================= -->
    <!-- Memory Identity Store -->
    <!-- ================================================= -->
    <sso-identity-store>
    <class>org.josso.gateway.identity.service.store.MemoryIdentityStore</class>
    <usersFileName>josso-users.xml</usersFileName>
    </sso-identity-store>
    <!-- ================================================= -->
    <!-- Identity Store Key adapter -->
    <!-- ================================================= -->
    <sso-identity-store-key-adapter>
    <class>org.josso.gateway.identity.service.store.SimpleIdentityStoreKeyAdapter</class>
    </sso-identity-store-key-adapter>
    </sso-identity-manager>
    <sso-session-manager>
    <class>org.josso.gateway.session.service.SSOSessionManagerImpl</class>
    <!--
    Set the maximum time interval, in minutes, between client requests before the SSO Service will invalidate
    the session. A negative time indicates that the session should never time out.
    -->
    <maxInactiveInterval>30</maxInactiveInterval>
    <!-- Max number of sessions per user, default 1
    A negative value indicates that an unlimited number of sessions per user is allowed.
    -->
    <maxSessionsPerUser>-1</maxSessionsPerUser>
    <!--
    If true, when the max number of sessions per user is exceeded,
    an already existing session will be invalidated to create a new one.
    If false, when the max number of sessions per user is exceeded,
    an exception is thrown and the new session is not created.
    -->
    <invalidateExceedingSessions>false</invalidateExceedingSessions>
    <!--
    Time interval, in milliseconds, between exired sessions cleanup.
    -->
    <sessionMonitorInterval>10000</sessionMonitorInterval>
    <!-- =================================================================== -->
    <!-- Serialized Session Store -->
    <!-- -->
    <!-- Session Store implementation which uses Java Serialization to -->
    <!-- persist Single Sign-On user sessions. -->
    <!-- It allows to reconstruct the session state after a system shutdown. -->
    <!-- =================================================================== -->
    <!--
    <sso-session-store>
    <class>org.josso.gateway.session.service.store.SerializedSessionStore</class>
    file where serialized sessions will be stored (optional)
    <serializedFile>/tmp/josso_sessions.ser</serializedFile>
    </sso-session-store>
    -->
    <!-- =============================================================== -->
    <!-- DataSource Session Store -->
    <!-- -->
    <!-- This store persists SSO sessions in a RDBMS, it's usefull for -->
    <!-- example when multiple SSO servers must share session information-->
    <!-- like in a cluster. -->
    <!-- -->
    <!-- NOTE :Remember to escape spetial chars like < with < , etc -->
    <!-- -->
    <!-- -->
    <!-- Chcek javadoc for configuration details : -->
    <!-- org.josso.gateway.session.service.store.db.DataSourceSessionStore -->
    <!-- =============================================================== -->
    <!--
    <sso-session-store>
    <class>org.josso.gateway.session.service.store.db.DataSourceSessionStore</class>
    <dsJndiName>java:jdbc/JossoSamplesDB</dsJndiName>
    <sizeQuery>SELECT COUNT(*) FROM JOSSO_SESSION</sizeQuery>
    <keysQuery>SELECT session_id FROM JOSSO_SESSION</keysQuery>
    <loadAllQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION</loadAllQuery>
    <loadQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE session_id = ?</loadQuery>
    <loadByUserNameQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE username = ?</loadByUserNameQuery>
    <loadByLastAccessTimeQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE last_access_time < ?</loadByLastAccessTimeQuery>
    <loadByValidQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE valid = ?</loadByValidQuery>
    <deleteDml>DELETE FROM JOSSO_SESSION WHERE session_id = ?</deleteDml>
    <deleteAllDml>DELETE FROM JOSSO_SESSION</deleteAllDml>
    <insertDml>INSERT INTO JOSSO_SESSION (session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid) VALUES (?, ?, ?, ?, ?, ?, ?) </insertDml>
    <dsJndiName>java:jdbc/JossoSamplesDB</dsJndiName>
    </sso-session-store>
    -->
    <!-- =============================================================== -->
    <!-- Jdbc Session Store -->
    <!-- -->
    <!-- This store persists SSO sessions in a RDBMS, it's usefull for -->
    <!-- example when multiple SSO servers must share session information-->
    <!-- like in a cluster. -->
    <!-- -->
    <!-- NOTE :Remember to escape spetial chars like < with < , etc -->
    <!-- -->
    <!-- Chcek javadoc for configuration details : -->
    <!-- org.josso.gateway.session.service.store.db.JdbcSessionStore -->
    <!-- =============================================================== -->
    <!--
    <sso-session-store>
    <class>org.josso.gateway.session.service.store.db.JdbcSessionStore</class>
    <connectionName>josso</connectionName>
    <connectionPassword>josso</connectionPassword>
    <connectionURL>jdbc:oracle:thin:@localhost:1521:josso_db</connectionURL>
    <driverName>oracle.jdbc.driver.OracleDriver</driverName>
    <sizeQuery>SELECT COUNT(*) FROM JOSSO_SESSION</sizeQuery>
    <keysQuery>SELECT session_id FROM JOSSO_SESSION</keysQuery>
    <loadAllQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION</loadAllQuery>
    <loadQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE session_id = ?</loadQuery>
    <loadByUserNameQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE username = ?</loadByUserNameQuery>
    <loadByLastAccessTimeQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE last_access_time < ?</loadByLastAccessTimeQuery>
    <loadByValidQuery>SELECT session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid FROM JOSSO_SESSION WHERE valid = ?</loadByValidQuery>
    <deleteDml>DELETE FROM JOSSO_SESSION WHERE session_id = ?</deleteDml>
    <deleteAllDml>DELETE FROM JOSSO_SESSION</deleteAllDml>
    <insertDml>INSERT INTO JOSSO_SESSION (session_id, userName, creation_time, last_access_time, access_count, max_inactive_interval, valid) VALUES (?, ?, ?, ?, ?, ?, ?) </insertDml>
    </sso-session-store>
    -->
    <!-- =============================================================== -->
    <!-- Memory Session Store -->
    <!-- =============================================================== -->
    <sso-session-store>
    <class>org.josso.gateway.session.service.store.MemorySessionStore</class>
    </sso-session-store>
    <sso-session-id-generator>
    <class>org.josso.gateway.session.service.SessionIdGeneratorImpl</class>
    <!--
    The message digest algorithm to be used when generating session
    identifiers. This must be an algorithm supported by the
    java.security.MessageDigest class on your platform.
    In J2SE 1.4.2 you can check :
    Java Cryptography Architecture API Specification & Reference - Apendix A : Standard Names
    Values are : MD2, MD5, SHA-1, SHA-256, SHA-384, SHA-512
    -->
    <algorithm>MD5</algorithm>
    </sso-session-id-generator>
    </sso-session-manager>
    <!-- SSO Audit Manager compoment -->
    <sso-audit-manager>
    <class>org.josso.gateway.audit.service.SSOAuditManagerImpl</class>
    <!--
    List of handlers that will process this request
    Every handler must have its own unique name.
    -->
    <handlers>
    <!-- This handler logs all audit trails using Log4J, under the given category -->
    <handler>
    <class>org.josso.gateway.audit.service.handler.LoggerAuditTrailHandler</class>
    <name>LoggerAuditTrailHandler</name>
    <category>org.josso.gateway.audit.SSO_AUDIT</category>
    </handler>
    <!--
    <handler>
    <class>MyOtherHandler</class>
    <name>MyOhterHandlerName</name>
    <myProperty>value</myProperty>
    </handler>
    -->
    </handlers>
    </sso-audit-manager>
    <!-- SSO Event Manager component -->
    <sso-event-manager>
    <class>org.josso.gateway.event.security.JMXSSOEventManagerImpl</class>
    <!--
    JMX Name of the EventManager MBean that will send SSO Events as JMX Notifications
    The MBean will be registered by the MBeanComponentKeeper.
    -->
    <oname>josso:type=SSOEventManager</oname>
    <!-- You can add your own listeners here : -->
    <!-- Every listener should have a unique name -->
    <!--
    <listeners>
    <listener>
    <class>com.myCompany.MyEventListener</class>
    <name>MyEventListener</name>
    <property1>MyListenerProperty1Value</property1>
    </listener>
    <listener>
    <class>com.myCompany.MyOtherEventListener</class>
    <name>MyOtherEventListener</name>
    <propertyA>MyOtherListenerPropertyAValue</propertyA>
    </listener>
    </listeners>
    -->
    </sso-event-manager>
    </domain>
    Is it means there is only way in Josso to save the username/passport by use of JDBC?
    If you find the datasource can be used, plz tell me how?

    oH, sorry , I found it !
    there is no problem here!

  • An unexpected error has been detected by HotSpot Virtual Machine:

    Hi
    When I upload the xml file with dubug window.
    When I have debug then this message will come..
    So give me a solution..
    Here at below I have pasted files. in which I want to by pass the ldap..
    So give me suggestion what to do with that files.
    What's wrong with that file ?
    Jiten
    18 Oct 2007 17:02:09 0 INFO [main] security.SecurityUtil - SecurityUtil.login: Called with [email protected]; password=[C@1797795; sourceIpAddress=192.168.5.14; weblogin=false; realm=null
    18 Oct 2007 17:02:09 16    INFO  [main] security.SecurityUtil - login: start login: username: [email protected]
    18 Oct 2007 17:02:09 125 INFO [main] BOOT - -- boot log messages -->
    [BOOT] INFO: Loading OJB's properties: file:/C:/LMS/gsnx/deploy/webapp/gsnx.ear/webapp.war/WEB-INF/classes/OJB.properties
    [BOOT] WARN: Can't read logging properties file using path 'OJB-logging.properties', message is:
    C:\LMS\gsnx\OJB-logging.properties (The system cannot find the file specified)
    Will try to load logging properties from OJB.properties file
    [BOOT] INFO: Logging: Found 'log4j.properties' file, use class org.apache.ojb.broker.util.logging.Log4jLoggerImpl
    [BOOT] INFO: Log4J is already configured, will not search for log4j properties file
    18 Oct 2007 17:02:12 3282 INFO [main] security.SecurityUtil - SecurityUtil.login: Calling authentication with [email protected]; password=[C@1797795; realm=null
    # An unexpected error has been detected by HotSpot Virtual Machine:
    #  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d85c14f, pid=4032, tid=3260
    # Java VM: Java HotSpot(TM) Client VM (1.5.0_11-b03 mixed mode)
    # Problematic frame:
    # V  [jvm.dll+0x11c14f]
    # An error report file with more information is saved as hs_err_pid4032.log
    # If you would like to submit a bug report, please visit:
    # http://java.sun.com/webapps/bugreport/crash.jsp
    Here :This is my login.config file..
    * Copyright (c) 2003-2005 E2open Inc. All rights reserved.
    * gnsx security configuration file
    * Note:
    * 1. At installation time, java.security file in your jre's lib/security/ directory should
    * be edited add the following line (ganx.home} is the home directory of gsnx install
    * login.config.url.1=file:{gsnx.home}/conf/login.config
    * 2. Edit this file to replace ldap-url with the correct url for your
    * LoginModule configuration.
    * @version $Id: login.config,v 1.8 2006/02/04 18:38:11 vgeorge Exp $
    gsnx.security.Login
    * LdapLoginModule Options:
    * ldap-url - LDAP connection URL, such as ldap://localhost:389
    * e.g. ldap-url="ldap://192.168.31.63:389"
    * dn-mask - The DN mask for user. The number 0 refers to the parameter
    * number for username. If this is specified then user search is ingored.
    * **This option is DEPRECATED**.
    * e.g. dn-mask="cn={0},ou=People,dc=gsnx,dc=com"
    * initialContextFactory - Class name of the initial context factory
    * e.g. initialContextFactory="com.sun.jndi.ldap.LdapCtxFactory"
    * connection-username - The DN used by the login module itself for authentication to
    * the directory server.
    * e.g. connection-username="uid=admin,ou=system"
    * connection-password - Password that is used by the login module to authenticate
    * itself to the directory server
    * e.g. connection-password="password"
    * connectionProtocol - The security protocol to use. This value is determined by the
    * service provider. An example would be SSL.
    * e.g. connectionProtocol="ldap"
    * authentication - The security level to use. Its value is one of the following
    * strings: "none", "simple", "strong".
    * e.g. authentication="simple"
    * user-search-base - the base DN for the user search
    * e.g. user-search-base="ou=users,ou=system"
    * user-search-pattern - filter specification how to search for the user object.
    * RFC 2254 filters are allowed. For example: (uid=user1). To parameterize the value
    * of the CN attribute type, specify (uid = {0}). The number 0 refers to the parameter
    * number for username. This query must return exactly one object.
    * e.g. user-search-pattern="uid={0}"
    * user-search-scope-subtree - Directory search scope for the user (ture | false)
    * ture - directory search scope is SUBTREE
    * false - directory search scope is ONE-LEVEL
    * e.g. user-search-scope-subtree="true"
    * user-password-changepw-gsnx-handler - hander to change password
    * If this handler is not specified, the change password feature will not be available
    * if "com.gsnx.core.server.security.LdapLoginModule", is used the the
    * option - user-password-attribute is required.
    * e.g. user-password-changepw-gsnx-handler="com.gsnx.core.server.security.LdapLoginModule"
    * user-password-attribute - attribute in LDAP that stores the user password
    * If this is not specified, the change password feature will not be work
    * when "com.gsnx.core.server.security.LdapLoginModule", is used as
    * user-password-changepw-gsnx-handler
    * e.g. user-password-attribute="userPassword"
    * role-search-base - The base DN for the group membership search
    * e.g. role-search-base="ou=groups,ou=system"
    * role-name-attribute - LDAP attribute type that identifies group name attribute in the object
    * returned from the group membership query. The group membership query is defined
    * by the role-search-pattern parameter. Typically the group name parameter is "cn".
    * e.g. role-name="cn"
    * role-search-pattern - The filter specification how to search for the role object.
    * RFC 2254 filters are allowed. For example: (uniqueMember = {0}). The number 0
    * refers refers to the DN of the authenticated user. Note that if role membership
    * for the user is defined in the member-of-like attribute (see user-role-name
    * parameter) you may not need to search for group membership with the query.
    * e.g. role-search-pattern="(uniqueMember={0})"
    * role-search-scope-subtree - Directory search scope for the role (ture | false).
    * ture - directory search scope is SUBTREE
    * false - directory search scope is ONE-LEVEL
    * e.g. role-search-scope-subtree="false"
    * user-role-attribute - LDAP attribute type for the user group membership. Different LDAP
    * schemas represent user group membership in different ways such as memberOf,
    * isMemberOf, member, etc. Values of these attributes are identifiers of groups that
    * a user is a member of. For example, if you have: memberOf: cn=admin,ou=groups,dc=gsnx,
    * specify "memberOf" as the value for the user-role-name attribute. Be aware of the
    * relationship between this parameter and group membership query. Typically
    * they will return the same data.
    * e.g. user-role-name="memberOf"
    * ldap://ldap-qa.dev.e2open.com:389
    * ldap://192.168.31.63:389
    com.gsnx.core.server.security.PassthruLoginModule required
    *com.gsnx.core.server.security.LdapLoginModule required
    initial-context-factory="com.sun.jndi.ldap.LdapCtxFactory"
    ldap-url="ldap://ldap-qa.dev.e2open.com:389"
    connection-username="cn=Manager,dc=gsnx,dc=com"
    connection-password="slapface"
    connection-protocol="ldap"
    authentication="simple"
    user-search-base="dc=gsnx,dc=com"
    user-search-pattern="cn={0}"
    user-search-scope-subtree="true"
    user-password-changepw-gsnx-handler="com.gsnx.core.server.security.PassthruLoginModule"
    user-password-attribute="userPassword"
    role-search-base=""
    role-name-attribute=""
    role-search-pattern=""
    role-search-scope-subtree=""
    user-role-attribute="";
    This is LoginConfig.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- The XML based JAAS login configuration read by the
    org.jboss.security.auth.login.XMLLoginConfig mbean. Add
    an application-policy element for each security domain.
    The outline of the application-policy is:
    <application-policy name="security-domain-name">
    <authentication>
    <login-module code="login.module1.class.name" flag="control_flag">
    <module-option name = "option1-name">option1-value</module-option>
    <module-option name = "option2-name">option2-value</module-option>
    </login-module>
    <login-module code="login.module2.class.name" flag="control_flag">
    </login-module>
    </authentication>
    </application-policy>
    $Revision: 1.12.2.2 $
    --><!DOCTYPE policy PUBLIC "-//JBoss//DTD JBOSS Security Config 3.0//EN" "http://www.jboss.org/j2ee/dtd/security_config.dtd">
    <policy>
    <!-- Used by clients within the application server VM such as
    mbeans and servlets that access EJBs.
    -->
    <application-policy name="gsnx.security.Login">
    <authentication>
    <!-- <login-module code="com.gsnx.core.server.security.LdapLoginModule" flag="required">-->
    <login-module code="com.gsnx.core.server.security.PassthruLoginModule" flag="required">
    <module-option name="initial-context-factory">com.sun.jndi.ldap.LdapCtxFactory
    </module-option>
    <!--<module-option name="user-password-changepw-gsnx-handler">com.gsnx.core.server.security.LdapLoginModule-->
    <module-option name="user-password-changepw-gsnx-handler">com.gsnx.core.server.security.PassthruLoginModule
    </module-option>
    <!-- <module-option name="ldap-url">ldap://192.168.31.63:389</module-option> -->
    <!-- <module-option name="ldap-url">ldap://10.120.17.253:389</module-option> -->
    <module-option name="ldap-url">ldap://ldap-qa.dev.e2open.com:389</module-option>
    <module-option name="connection-username">cn=Manager,dc=gsnx,dc=com</module-option>
    <module-option name="connection-password">slapface</module-option>
    <module-option name="connection-protocol">ldap</module-option>
    <module-option name="authentication">simple</module-option>
    <module-option name="user-search-base">dc=gsnx,dc=com</module-option>
    <module-option name="user-search-pattern">cn={0}</module-option>
    <module-option name="user-search-scope-subtree">true</module-option>
    <module-option name="user-password-attribute"/>
    <module-option name="role-search-base"/>
    <module-option name="role-name-attribute"/>
    <module-option name="role-search-pattern"/>
    <module-option name="role-search-scope-subtree"/>
    <module-option name="user-role-attribute"/>
    </login-module>
    </authentication>
    </application-policy>
    <application-policy name="client-login">
    <authentication>
    <login-module code="org.jboss.security.ClientLoginModule" flag="required">
    </login-module>
    </authentication>
    </application-policy>
    <!-- Security domain for JBossMQ -->
    <application-policy name="jbossmq">
    <authentication>
    <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
    <module-option name="unauthenticatedIdentity">guest</module-option>
    <module-option name="dsJndiName">java:/DefaultDS</module-option>
    <module-option name="principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
    <module-option name="rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <!-- Security domain for JBossMQ when using file-state-service.xml
    <application-policy name = "jbossmq">
    <authentication>
    <login-module code = "org.jboss.mq.sm.file.DynamicLoginModule"
    flag = "required">
    <module-option name = "unauthenticatedIdentity">guest</module-option>
    <module-option name = "sm.objectname">jboss.mq:service=StateManager</module-option>
    </login-module>
    </authentication>
    </application-policy>
    -->
    <!-- Security domains for testing new jca framework -->
    <application-policy name="HsqlDbRealm">
    <authentication>
    <login-module code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag="required">
    <module-option name="principal">sa</module-option>
    <module-option name="userName">sa</module-option>
    <module-option name="password"/>
    <module-option name="managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=DefaultDS</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <application-policy name="JmsXARealm">
    <authentication>
    <login-module code="org.jboss.resource.security.ConfiguredIdentityLoginModule" flag="required">
    <module-option name="principal">guest</module-option>
    <module-option name="userName">guest</module-option>
    <module-option name="password">guest</module-option>
    <module-option name="managedConnectionFactoryName">jboss.jca:service=TxCM,name=JmsXA</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <!-- A template configuration for the jmx-console web application. This
    defaults to the UsersRolesLoginModule the same as other and should be
    changed to a stronger authentication mechanism as required.
    -->
    <application-policy name="jmx-console">
    <authentication>
    <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
    <module-option name="usersProperties">props/jmx-console-users.properties</module-option>
    <module-option name="rolesProperties">props/jmx-console-roles.properties</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <!-- A template configuration for the web-console web application. This
    defaults to the UsersRolesLoginModule the same as other and should be
    changed to a stronger authentication mechanism as required.
    -->
    <application-policy name="web-console">
    <authentication>
    <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
    <module-option name="usersProperties">web-console-users.properties</module-option>
    <module-option name="rolesProperties">web-console-roles.properties</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <!-- A template configuration for the JBossWS web application (and transport layer!).
    This defaults to the UsersRolesLoginModule the same as other and should be
    changed to a stronger authentication mechanism as required.
    -->
    <application-policy name="JBossWS">
    <authentication>
    <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required">
    <module-option name="unauthenticatedIdentity">anonymous</module-option>
    </login-module>
    </authentication>
    </application-policy>
    <!-- The default login configuration used by any security domain that
    does not have a application-policy entry with a matching name
    -->
    <application-policy name="other">
    <!-- A simple server login module, which can be used when the number
    of users is relatively small. It uses two properties files:
    users.properties, which holds users (key) and their password (value).
    roles.properties, which holds users (key) and a comma-separated list of
    their roles (value).
    The unauthenticatedIdentity property defines the name of the principal
    that will be used when a null username and password are presented as is
    the case for an unuathenticated web client or MDB. If you want to
    allow such users to be authenticated add the property, e.g.,
    unauthenticatedIdentity="nobody"
    -->
    <authentication>
    <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" flag="required"/>
    </authentication>
    </application-policy>
    </policy>
    This is : java.security
    # This is the "master security properties file".
    # In this file, various security properties are set for use by
    # java.security classes. This is where users can statically register
    # Cryptography Package Providers ("providers" for short). The term
    # "provider" refers to a package or set of packages that supply a
    # concrete implementation of a subset of the cryptography aspects of
    # the Java Security API. A provider may, for example, implement one or
    # more digital signature algorithms or message digest algorithms.
    # Each provider must implement a subclass of the Provider class.
    # To register a provider in this master security properties file,
    # specify the Provider subclass name and priority in the format
    # security.provider.<n>=<className>
    # This declares a provider, and specifies its preference
    # order n. The preference order is the order in which providers are
    # searched for requested algorithms (when no specific provider is
    # requested). The order is 1-based; 1 is the most preferred, followed
    # by 2, and so on.
    # <className> must specify the subclass of the Provider class whose
    # constructor sets the values of various properties that are required
    # for the Java Security API to look up the algorithms or other
    # facilities implemented by the provider.
    # There must be at least one provider specification in java.security.
    # There is a default provider that comes standard with the JDK. It
    # is called the "SUN" provider, and its Provider subclass
    # named Sun appears in the sun.security.provider package. Thus, the
    # "SUN" provider is registered via the following:
    # security.provider.1=sun.security.provider.Sun
    # (The number 1 is used for the default provider.)
    # Note: Statically registered Provider subclasses are instantiated
    # when the system is initialized. Providers can be dynamically
    # registered instead by calls to either the addProvider or
    # insertProviderAt method in the Security class.
    # List of providers and their preference orders (see above):
    security.provider.1=sun.security.provider.Sun
    security.provider.2=sun.security.rsa.SunRsaSign
    security.provider.3=com.sun.net.ssl.internal.ssl.Provider
    security.provider.4=com.sun.crypto.provider.SunJCE
    security.provider.5=sun.security.jgss.SunProvider
    security.provider.6=com.sun.security.sasl.Provider
    # Select the source of seed data for SecureRandom. By default an
    # attempt is made to use the entropy gathering device specified by
    # the securerandom.source property. If an exception occurs when
    # accessing the URL then the traditional system/thread activity
    # algorithm is used.
    # On Solaris and Linux systems, if file:/dev/urandom is specified and it
    # exists, a special SecureRandom implementation is activated by default.
    # This "NativePRNG" reads random bytes directly from /dev/urandom.
    # On Windows systems, the URLs file:/dev/random and file:/dev/urandom
    # enables use of the Microsoft CryptoAPI seed functionality.
    securerandom.source=file:/dev/urandom
    # The entropy gathering device is described as a URL and can also
    # be specified with the system property "java.security.egd". For example,
    # -Djava.security.egd=file:/dev/urandom
    # Specifying this system property will override the securerandom.source
    # setting.
    # Class to instantiate as the javax.security.auth.login.Configuration
    # provider.
    login.configuration.provider=com.sun.security.auth.login.ConfigFile
    # Default login configuration file
    login.config.url.1=C:\LMS\gsnx\core\src\conf\login.config
    # Class to instantiate as the system Policy. This is the name of the class
    # that will be used as the Policy object.
    policy.provider=sun.security.provider.PolicyFile
    # The default is to have a single system-wide policy file,
    # and a policy file in the user's home directory.
    policy.url.1=file:${java.home}/lib/security/java.policy
    policy.url.2=file:${user.home}/.java.policy
    # whether or not we expand properties in the policy file
    # if this is set to false, properties (${...}) will not be expanded in policy
    # files.
    policy.expandProperties=true
    # whether or not we allow an extra policy to be passed on the command line
    # with -Djava.security.policy=somefile. Comment out this line to disable
    # this feature.
    policy.allowSystemProperty=true
    # whether or not we look into the IdentityScope for trusted Identities
    # when encountering a 1.1 signed JAR file. If the identity is found
    # and is trusted, we grant it AllPermission.
    policy.ignoreIdentityScope=false
    # Default keystore type.
    keystore.type=jks
    # Class to instantiate as the system scope:
    system.scope=sun.security.provider.IdentityDatabase
    # List of comma-separated packages that start with or equal this string
    # will cause a security exception to be thrown when
    # passed to checkPackageAccess unless the
    # corresponding RuntimePermission ("accessClassInPackage."+package) has
    # been granted.
    package.access=sun.
    # List of comma-separated packages that start with or equal this string
    # will cause a security exception to be thrown when
    # passed to checkPackageDefinition unless the
    # corresponding RuntimePermission ("defineClassInPackage."+package) has
    # been granted.
    # by default, no packages are restricted for definition, and none of
    # the class loaders supplied with the JDK call checkPackageDefinition.
    #package.definition=
    # Determines whether this properties file can be appended to
    # or overridden on the command line via -Djava.security.properties
    security.overridePropertiesFile=true
    # Determines the default key and trust manager factory algorithms for
    # the javax.net.ssl package.
    ssl.KeyManagerFactory.algorithm=SunX509
    ssl.TrustManagerFactory.algorithm=PKIX
    # Determines the default SSLSocketFactory and SSLServerSocketFactory
    # provider implementations for the javax.net.ssl package. If, due to
    # export and/or import regulations, the providers are not allowed to be
    # replaced, changing these values will produce non-functional
    # SocketFactory or ServerSocketFactory implementations.
    #ssl.SocketFactory.provider=
    #ssl.ServerSocketFactory.provider=
    # The Java-level namelookup cache policy for successful lookups:
    # any negative value: caching forever
    # any positive value: the number of seconds to cache an address for
    # zero: do not cache
    # default value is forever (FOREVER). For security reasons, this
    # caching is made forever when a security manager is set.
    # NOTE: setting this to anything other than the default value can have
    # serious security implications. Do not set it unless
    # you are sure you are not exposed to DNS spoofing attack.
    #networkaddress.cache.ttl=-1
    # The Java-level namelookup cache policy for failed lookups:
    # any negative value: cache forever
    # any positive value: the number of seconds to cache negative lookup results
    # zero: do not cache
    # In some Microsoft Windows networking environments that employ
    # the WINS name service in addition to DNS, name service lookups
    # that fail may take a noticeably long time to return (approx. 5 seconds).
    # For this reason the default caching policy is to maintain these
    # results for 10 seconds.
    networkaddress.cache.negative.ttl=10
    # Properties to configure OCSP for certificate revocation checking
    # Enable OCSP
    # By default, OCSP is not used for certificate revocation checking.
    # This property enables the use of OCSP when set to the value "true".
    # NOTE: SocketPermission is required to connect to an OCSP responder.
    # Example,
    # ocsp.enable=true
    # Location of the OCSP responder
    # By default, the location of the OCSP responder is determined implicitly
    # from the certificate being validated. This property explicitly specifies
    # the location of the OCSP responder. The property is used when the
    # Authority Information Access extension (defined in RFC 3280) is absent
    # from the certificate or when it requires overriding.
    # Example,
    # ocsp.responderURL=http://ocsp.example.net:80
    # Subject name of the OCSP responder's certificate
    # By default, the certificate of the OCSP responder is that of the issuer
    # of the certificate being validated. This property identifies the certificate
    # of the OCSP responder when the default does not apply. Its value is a string
    # distinguished name (defined in RFC 2253) which identifies a certificate in
    # the set of certificates supplied during cert path validation. In cases where
    # the subject name alone is not sufficient to uniquely identify the certificate
    # then both the "ocsp.responderCertIssuerName" and
    # "ocsp.responderCertSerialNumber" properties must be used instead. When this
    # property is set then those two properties are ignored.
    # Example,
    # ocsp.responderCertSubjectName="CN=OCSP Responder, O=XYZ Corp"
    # Issuer name of the OCSP responder's certificate
    # By default, the certificate of the OCSP responder is that of the issuer
    # of the certificate being validated. This property identifies the certificate
    # of the OCSP responder when the default does not apply. Its value is a string
    # distinguished name (defined in RFC 2253) which identifies a certificate in
    # the set of certificates supplied during cert path validation. When this
    # property is set then the "ocsp.responderCertSerialNumber" property must also
    # be set. When the "ocsp.responderCertSubjectName" property is set then this
    # property is ignored.
    # Example,
    # ocsp.responderCertIssuerName="CN=Enterprise CA, O=XYZ Corp"
    # Serial number of the OCSP responder's certificate
    # By default, the certificate of the OCSP responder is that of the issuer
    # of the certificate being validated. This property identifies the certificate
    # of the OCSP responder when the default does not apply. Its value is a string
    # of hexadecimal digits (colon or space separators may be present) which
    # identifies a certificate in the set of certificates supplied during cert path
    # validation. When this property is set then the "ocsp.responderCertIssuerName"
    # property must also be set. When the "ocsp.responderCertSubjectName" property
    # is set then this property is ignored.
    # Example,
    # ocsp.responderCertSerialNumber=2A:FF:00

    user564785 wrote:
    I am trying to installl Oracle 11gR2 on VM machine with Redhat Linux 6-64bit. That is a Oracle database problem. Even though the Oracle product uses java it still represents a problem with that product (Oracle) rather than java. So you need to start with an Oracle database forum.

  • Out of memory Error While deploying and building the application

    # An unexpected error has been detected by HotSpot Virtual Machine:
    # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0808f7ef, pid=5036, tid=5072
    # Java VM: Java HotSpot(TM) Client VM (1.4.2_11-b06 mixed mode)
    # Problematic frame:
    # V [jvm.dll+0x8f7ef]
    --------------- T H R E A D ---------------
    Current thread (0x078b4ac0): JavaThread "ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" daemon [_thread_in_vm, id=5072]
    siginfo: ExceptionCode=0xc0000005, reading address 0x079c7ffc
    Registers:
    EAX=0x00000000, EBX=0x078b4ac0, ECX=0x079c7ff0, EDX=0x0080908c
    ESP=0x0823f5a0, EBP=0x0823f5f8, ESI=0x0718ac70, EDI=0x00000000
    EIP=0x0808f7ef, EFLAGS=0x00010246
    Top of Stack: (sp=0x0823f5a0)
    0x0823f5a0: 08064249 0080908c 079c7ff0 0823f618
    0x0823f5b0: 0718ac20 0808f80a 0080908c 0808f7e5
    0x0823f5c0: 0718a220 0808eda6 0080908c 0003bc78
    0x0823f5d0: 0808eec6 0080908c 0823f618 00000001
    0x0823f5e0: 080925ab 0080908c 078b4d7c 00000001
    0x0823f5f0: 00000000 078b4ac0 0823f60c 0095f4f4
    0x0823f600: 0080908c 0823f618 078b4b5c 0823f628
    0x0823f610: 0095f4ac 078b4b5c 0080908c 0823f624
    Instructions: (pc=0x0808f7ef)
    0x0808f7df: 02 33 c0 c2 04 00 8b 4c 24 08 8b 54 24 04 33 c0
    0x0808f7ef: 3b 51 0c 0f 94 c0 c3 56 8b f1 68 e5 f7 08 08 ff
    Stack: [0x08200000,0x08240000), sp=0x0823f5a0, free space=253k
    Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
    V [jvm.dll+0x8f7ef]
    C [jdwp.dll+0xf4f4]
    C [jdwp.dll+0xf4ac]
    C [jdwp.dll+0xbf91]
    C [jdwp.dll+0xbe23]
    C [jdwp.dll+0x7b6b]
    C [jdwp.dll+0x89c8]
    V [jvm.dll+0x8fc00]
    V [jvm.dll+0x909e4]
    V [jvm.dll+0x90291]
    V [jvm.dll+0x6df8a]
    j jsp_servlet._data_usage.__new_request._jspService(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V+2387
    j com.telus.smartdesktop.framework.JSPControllerServlet.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+74
    j weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava/lang/Object;+12
    j weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl;)V+387
    j weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl;)V+618
    j weblogic.servlet.internal.TailFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+10
    j weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+28
    j com.sun.identity.agents.filter.AmAgentFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+175
    j weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+28
    j weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;+79
    j weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;+34
    j weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;+18
    j weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V+685
    j weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic/kernel/ExecuteThread;)V+141
    j weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V+23
    j weblogic.kernel.ExecuteThread.run()V+66
    v ~StubRoutines::call_stub
    V [jvm.dll+0x72846]
    V [jvm.dll+0xac976]
    V [jvm.dll+0x72753]
    V [jvm.dll+0x7244f]
    V [jvm.dll+0x72488]
    V [jvm.dll+0x8a3a0]
    V [jvm.dll+0xd0de8]
    V [jvm.dll+0xd0db6]
    C [MSVCRT.dll+0x2a3b0]
    C [kernel32.dll+0xb729]
    Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
    j jsp_servlet._data_usage.__new_request._jspService(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V+2387
    j com.telus.smartdesktop.framework.JSPControllerServlet.service(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+74
    j weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava/lang/Object;+12
    j weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl;)V+387
    j weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Lweblogic/servlet/internal/FilterChainImpl;)V+618
    j weblogic.servlet.internal.TailFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+10
    j weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+28
    j com.sun.identity.agents.filter.AmAgentFilter.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;Ljavax/servlet/FilterChain;)V+175
    j weblogic.servlet.internal.FilterChainImpl.doFilter(Ljavax/servlet/ServletRequest;Ljavax/servlet/ServletResponse;)V+28
    j weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava/lang/Object;+79
    j weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic/security/subject/AbstractSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;+34
    j weblogic.security.service.SecurityManager.runAs(Lweblogic/security/acl/internal/AuthenticatedSubject;Lweblogic/security/acl/internal/AuthenticatedSubject;Ljava/security/PrivilegedAction;)Ljava/lang/Object;+18
    j weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic/servlet/internal/ServletRequestImpl;Lweblogic/servlet/internal/ServletResponseImpl;)V+685
    j weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic/kernel/ExecuteThread;)V+141
    j weblogic.kernel.ExecuteThread.execute(Lweblogic/kernel/ExecuteRequest;)V+23
    j weblogic.kernel.ExecuteThread.run()V+66
    v ~StubRoutines::call_stub
    --------------- P R O C E S S ---------------
    Java Threads: ( => current thread )
    0x071c8520 JavaThread "JDWP Command Reader" daemon [_thread_in_native, id=5340]
    0x07aa37b0 JavaThread "Thread-20" daemon [_thread_in_native, id=3248]
    0x07f777f0 JavaThread "HvcReferenceDataPeriodicRefreshThread" daemon [_thread_blocked, id=1448]
    0x07aa30f0 JavaThread "SD-PerformanceMonitorThread" daemon [_thread_blocked, id=5856]
    0x08bb2b48 JavaThread "cache-PrepareThread" daemon [_thread_blocked, id=3968]
    0x07cfe008 JavaThread "cache-CommitThread" daemon [_thread_blocked, id=4128]
    0x00a59410 JavaThread "Thread-14" daemon [_thread_in_native, id=2096]
    0x073e0a20 JavaThread "ListenThread.Default" [_thread_in_native, id=4432]
    0x07b2b808 JavaThread "Thread-12" [_thread_blocked, id=4472]
    0x072ad9f8 JavaThread "Thread-11" daemon [_thread_in_native, id=4160]
    0x0893b648 JavaThread "RulesCachePeriodicRefreshThread" daemon [_thread_blocked, id=2024]
    0x07485828 JavaThread "ReferenceDataRefreshThread" daemon [_thread_blocked, id=2204]
    0x07e80408 JavaThread "ExecuteThread: '4' for queue: 'weblogic.socket.Muxer'" daemon [_thread_in_native, id=1588]
    0x071fb3e8 JavaThread "ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'" daemon [_thread_in_native, id=3532]
    0x07bf4240 JavaThread "ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" daemon [_thread_in_native, id=112]
    0x07bf40d8 JavaThread "ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" daemon [_thread_in_native, id=3680]
    0x07294ea0 JavaThread "ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" daemon [_thread_in_native, id=6016]
    0x00a71e60 JavaThread "com.telus.provider.scheduling.Scheduler@b245dc" daemon [_thread_blocked, id=4636]
    0x07204828 JavaThread "ExecuteThread: '3' for queue: 'JMS.TimerClientPool'" daemon [_thread_blocked, id=5604]
    0x07b2cea0 JavaThread "ExecuteThread: '2' for queue: 'JMS.TimerClientPool'" daemon [_thread_blocked, id=1520]
    0x0791bea0 JavaThread "ExecuteThread: '1' for queue: 'JMS.TimerClientPool'" daemon [_thread_blocked, id=5496]
    0x07849ce0 JavaThread "ExecuteThread: '0' for queue: 'JMS.TimerClientPool'" daemon [_thread_blocked, id=3828]
    0x0739af88 JavaThread "Thread-6" daemon [_thread_blocked, id=2784]
    0x072241d0 JavaThread "ExecuteThread: '0' for queue: 'JMS.TimerTreePool'" daemon [_thread_blocked, id=4004]
    0x072eb7b8 JavaThread "weblogic.health.CoreHealthMonitor" daemon [_thread_blocked, id=3976]
    0x0754ace0 JavaThread "Thread-5" [_thread_blocked, id=3236]
    0x078eac38 JavaThread "DoSManager" [_thread_blocked, id=3740]
    0x07893190 JavaThread "VDE Transaction Processor Thread" [_thread_blocked, id=3408]
    0x07938408 JavaThread "ExecuteThread: '2' for queue: 'weblogic.admin.RMI'" daemon [_thread_blocked, id=4372]
    0x07abb408 JavaThread "ExecuteThread: '1' for queue: 'weblogic.admin.RMI'" daemon [_thread_blocked, id=5148]
    0x07aafda8 JavaThread "ExecuteThread: '0' for queue: 'weblogic.admin.RMI'" daemon [_thread_blocked, id=2656]
    0x0739c898 JavaThread "ExecuteThread: '1' for queue: 'weblogic.admin.HTTP'" daemon [_thread_blocked, id=4264]
    0x074009b8 JavaThread "ExecuteThread: '0' for queue: 'weblogic.admin.HTTP'" daemon [_thread_blocked, id=5196]
    0x078004a8 JavaThread "weblogic.security.SpinnerRandomSource" daemon [_thread_blocked, id=3516]
    0x077ffea8 JavaThread "weblogic.time.TimeEventGenerator" daemon [_thread_blocked, id=1296]
    0x0718aea0 JavaThread "ExecuteThread: '4' for queue: 'weblogic.kernel.System'" daemon [_thread_blocked, id=2072]
    0x0718a220 JavaThread "ExecuteThread: '3' for queue: 'weblogic.kernel.System'" daemon [_thread_blocked, id=2832]
    0x071895d8 JavaThread "ExecuteThread: '2' for queue: 'weblogic.kernel.System'" daemon [_thread_blocked, id=3696]
    0x071d6ed8 JavaThread "ExecuteThread: '1' for queue: 'weblogic.kernel.System'" daemon [_thread_blocked, id=4064]
    0x071d6ac0 JavaThread "ExecuteThread: '0' for queue: 'weblogic.kernel.System'" daemon [_thread_blocked, id=5168]
    0x071d5640 JavaThread "ExecuteThread: '14' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=1184]
    0x071d4ab8 JavaThread "ExecuteThread: '13' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=2200]
    0x07401b68 JavaThread "ExecuteThread: '12' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4608]
    0x07a99900 JavaThread "ExecuteThread: '11' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=5900]
    0x078b4df8 JavaThread "ExecuteThread: '10' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4028]
    =>0x078b4ac0 JavaThread "ExecuteThread: '9' for queue: 'weblogic.kernel.Default'" daemon [_thread_in_vm, id=5072]
    0x078b4018 JavaThread "ExecuteThread: '8' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4108]
    0x07380448 JavaThread "ExecuteThread: '7' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4740]
    0x07477c30 JavaThread "ExecuteThread: '6' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4668]
    0x07477a28 JavaThread "ExecuteThread: '5' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=844]
    0x07bdda60 JavaThread "ExecuteThread: '4' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4588]
    0x07bdd8f8 JavaThread "ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=3732]
    0x07195918 JavaThread "ExecuteThread: '2' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=5588]
    0x071957b0 JavaThread "ExecuteThread: '1' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=5116]
    0x0787d008 JavaThread "ExecuteThread: '0' for queue: 'weblogic.kernel.Default'" daemon [_thread_blocked, id=4956]
    0x07a7b1f8 JavaThread "Thread-1" daemon [_thread_blocked, id=5328]
    0x00a148a8 JavaThread "CompilerThread0" daemon [_thread_blocked, id=5716]
    0x00a139c0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3524]
    0x00a12538 JavaThread "JDWP Event Helper Thread" daemon [_thread_in_native, id=5680]
    0x009d4d38 JavaThread "JDWP Transport Listener: dt_socket" daemon [_thread_in_native, id=5748]
    0x009d1530 JavaThread "Finalizer" daemon [_thread_blocked, id=4868]
    0x009d0120 JavaThread "Reference Handler" daemon [_thread_blocked, id=4184]
    0x0003ce58 JavaThread "main" [_thread_blocked, id=420]
    Other Threads:
    0x00a116f8 VMThread [id=3084]
    0x00a164f8 WatcherThread [id=4416]
    VM state:not at safepoint (normal execution)
    VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
    [0x0003bc78/0x00000f20] Threads_lock - owner thread: 0x078b4ac0
    Heap
    def new generation total 36288K, used 13059K [0x10010000, 0x12770000, 0x12770000)
    eden space 32256K, 32% used [0x10010000, 0x10a2b788, 0x11f90000)
    from space 4032K, 67% used [0x12380000, 0x12625788, 0x12770000)
    to space 4032K, 0% used [0x11f90000, 0x11f90000, 0x12380000)
    tenured generation total 483968K, used 27091K [0x12770000, 0x30010000, 0x30010000)
    the space 483968K, 5% used [0x12770000, 0x141e4ec0, 0x141e5000, 0x30010000)
    compacting perm gen total 44544K, used 44391K [0x30010000, 0x32b90000, 0x34010000)
    the space 44544K, 99% used [0x30010000, 0x32b69d30, 0x32b69e00, 0x32b90000)
    Dynamic libraries:
    0x00400000 - 0x0040b000      C:\bea\jdk142_11\jre\bin\java.exe
    0x7c900000 - 0x7c9b2000      C:\WINDOWS\system32\ntdll.dll
    0x7c800000 - 0x7c8f6000      C:\WINDOWS\system32\kernel32.dll
    0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
    0x77e70000 - 0x77f03000      C:\WINDOWS\system32\RPCRT4.dll
    0x77fe0000 - 0x77ff1000      C:\WINDOWS\system32\Secur32.dll
    0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
    0x08000000 - 0x0813f000      C:\bea\jdk142_11\jre\bin\client\jvm.dll
    0x7e410000 - 0x7e4a1000      C:\WINDOWS\system32\USER32.dll
    0x77f10000 - 0x77f59000      C:\WINDOWS\system32\GDI32.dll
    0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
    0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.DLL
    0x10000000 - 0x10007000      C:\bea\jdk142_11\jre\bin\hpi.dll
    0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
    0x003a0000 - 0x003ae000      C:\bea\jdk142_11\jre\bin\verify.dll
    0x003c0000 - 0x003d9000      C:\bea\jdk142_11\jre\bin\java.dll
    0x003e0000 - 0x003ee000      C:\bea\jdk142_11\jre\bin\zip.dll
    0x00950000 - 0x0096c000      C:\bea\jdk142_11\jre\bin\jdwp.dll
    0x003f0000 - 0x003f5000      C:\bea\jdk142_11\jre\bin\dt_socket.dll
    0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\ws2_32.dll
    0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
    0x71a50000 - 0x71a8f000      C:\WINDOWS\system32\mswsock.dll
    0x662b0000 - 0x66308000      C:\WINDOWS\system32\hnetcfg.dll
    0x71a90000 - 0x71a98000      C:\WINDOWS\System32\wshtcpip.dll
    0x06fb0000 - 0x06fbf000      C:\bea\jdk142_11\jre\bin\net.dll
    0x76f20000 - 0x76f47000      C:\WINDOWS\system32\DNSAPI.dll
    0x76fb0000 - 0x76fb8000      C:\WINDOWS\System32\winrnr.dll
    0x76f60000 - 0x76f8c000      C:\WINDOWS\system32\WLDAP32.dll
    0x76fc0000 - 0x76fc6000      C:\WINDOWS\system32\rasadhlp.dll
    0x070d0000 - 0x070d8000      C:\bea\jdk142_11\jre\bin\nio.dll
    0x070e0000 - 0x070e6000      C:\bea\jdk142_11\jre\bin\ioser12.dll
    0x09940000 - 0x09945000      C:\bea\weblogic81\server\bin\stackdump.dll
    0x09950000 - 0x09955000      C:\bea\weblogic81\server\bin\wlntio.dll
    0x68000000 - 0x68036000      C:\WINDOWS\system32\rsaenh.dll
    0x769c0000 - 0x76a74000      C:\WINDOWS\system32\USERENV.dll
    0x5b860000 - 0x5b8b5000      C:\WINDOWS\system32\netapi32.dll
    VM Arguments:
    jvm_args: -Xmx512M -Xms512M -Dcom.telus.provider.initialContextFactory=weblogic.jndi.WLInitialContextFactory -Dcom.telus.provider.providerURL=t3://wlpt168smartdteca:6382 -Dcom.telus.credit.providerURL=t3://wlpt168eascommonservices:8623 -Dcom.telusmobility.config.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory -Dcom.telusmobility.config.java.naming.provider.url=ldap://ldapread-pt168.tmi.telus.com:589/cn=pt168_81,o=telusconfiguration -DignoreIdentity=true -Dbranding=super -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=9090,suspend=n,server=y -Dweblogic.Domain=smartdesktop -Dbea.home=C:\bea -Djava.security.policy==C:\bea\weblogic81\server\lib\weblogic.policy -Dweblogic.ProductionModeEnabled=false
    java_command: weblogic.Server
    Launcher Type: SUN_STANDARD
    Environment Variables:
    JAVA_HOME=C:\bea\jdk142_11
    CLASSPATH=C:\bea\JROCKI~1\lib\tools.jar;C:\bea\WEBLOG~1\server\lib\weblogic_sp.jar;C:\bea\WEBLOG~1\server\lib\weblogic.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbserver44.jar;C:\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\bea\JROCKI~1\jre\lib\rt.jar;C:\bea\WEBLOG~1\server\lib\webservices.jar;.;C:\Program Files\Java\jre1.5.0_09\lib\ext\QTJava.zip;..\..\..\..\common\ThirdParty\sun\mail\activation.jar;..\..\..\..\common\ThirdParty\sun\mail\mail.jar
    PATH=C:\bea\WEBLOG~1\server\bin;C:\bea\jdk142_11\jre\bin;C:\bea\jdk142_11\bin;C:\bea\WEBLOG~1\server\bin;C:\bea\jdk142_11\jre\bin;C:\bea\jdk142_11\bin;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files\Borland\CaliberRM SDK 2008\lib;C:\Program Files\Borland\StarTeam SDK 10.0\Lib;C:\Program Files\Borland\StarTeam SDK 10.0\Bin;C:\Program Files\Borland\CaliberRM SDK 2008;C:\Program Files\Borland\StarTeam SDK 10.0;C:\Program Files\Windows Imaging\;C:\Program Files\Oracle\jre\1.1.8\bin\;C:\Oracle9i\bin\;C:\ORACLE\Product\11.2.0\client_1;C:\WINDOWS\system32\;C:\WINDOWS\system32\Wbem;C:\Program Files\InstallShield\AdminStudio\6.0\ConflictSolver;C:\Program Files\ClickSoftware\Service Optimization\Bin;C:\Program Files\Windows Imaging;C:\Program Files\QuickTime\QTSystem\;C:\bea\WEBLOG~1\server\bin\oci920_8;C:\bea\WEBLOG~1\server\bin\oci920_8
    USERNAME=x120751
    OS=Windows_NT
    PROCESSOR_IDENTIFIER=x86 Family 6 Model 37 Stepping 5, GenuineIntel
    --------------- S Y S T E M ---------------
    OS: Windows XP Build 2600 Service Pack 3
    CPU:total 4 family 6, cmov, cx8, fxsr, mmx, sse, sse2
    Memory: 4k page, physical 2097151k(1723568k free), swap 4194303k(4117288k free)
    vm_info: Java HotSpot(TM) Client VM (1.4.2_11-b06) for windows-x86, built on Feb 13 2006 10:19:30 by "java_re" with MS VC++ 6.0
    My ant build.xml is as given below
    <case value="pt">
    <property name="jvmArgs" value="-hotspot -Xmx512M -Xms512M -Dcom.telus.provider.initialContextFactory=weblogic.jndi.WLInitialContextFactory -Dcom.telus.provider.providerURL=cc://wlpt111smartdteca:4444 -Dcom.telus.cd.providerURL=w3://wlpt111eascommonservices:444 -Dcom.mobility.config.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory -Dcom.bility.config.java.naming.provider.url=ldap://ldapread-pt.tmi.cins.com:555/cn=pt33_181,o=telusconfiguration"/>
    </case>
    <java failonerror="true" fork="true" dir="${deployDir}/jspc" classname="weblogic.appc" classpathref="appc.classpath">
    <jvmarg line="-Xmx1024M -Xms1024M"/>
    <arg line="-forceGeneration -verbose -deprecation ${sourceDir}/html"/>
    </java>

    Hi user13118647,
    It looks like your application is triggering an existing Sun HotSpot VM bug from the older 1.4.2_11 JDK.
    Please review the Sun bug references below.
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6405062
    http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6385867
    The problem appears to be resolved in JDK 1.4.2_13(b01). You may want to download and attempt to replicate with this service pack upgrade.
    Another potential problem I noticed is at your classpath level. It looks like you are using a mix of runtime JDK jar files from the Sun JDK and JRockit. Please ensure your JDK classpath; including any reference to any JDK related runtime jar files (tools.jar, rt.jar etc.) is consistent and unique e.g. Sun HotSpot or Oracle JRockit but not both.
    ## Example:
    JAVA_HOME=C:\bea\jdk142_11 // JDK home is setup to the Sun JDK
    CLASSPATH=C:\bea\JROCKI~1\lib\tools.jar; // tools.jar is loaded from the JRockit JDK home
    Regards,
    P-H
    http://javaeesupportpatterns.blogspot.com/

  • How to obtain PROVIDER_URL in the bean

    I want to get access in my bean to the Context.PROVIDER_URL property which
    was used by the client to create the initial context.
    I know the ejbContext.getEnvironment() method is deprecated so I tried the
    following:
    javax.naming.InitialContext ctx = new InitialContext();
    String sURL =
    (String)ctx.lookup("java:comp/env/"+javax.naming.Context.PROVIDER_URL);
    This gives me a null back. What am I doing wrong?
    Or is there another way to get the provider url inside the bean code?
    Ashish P. Narvekar
    email: [email protected]

    Ashish,
    FWIW, this is how we're doing it...
    InputStream inp =
    ClassLoader.getSystemResourceAsStream("weblogic.properties");
    if(inp != null)
    Properties env = new Properties();
    env.load(inp);
    String icf = env.getProperty("databroker.initialContextFactory");
    env.put(Context.INITIAL_CONTEXT_FACTORY, icf);
    String url = env.getProperty("databroker.providerUrl");
    env.put(Context.PROVIDER_URL, url);
    entCtx = new InitialContext(env);
    We then use entCtx to lookup the home interface. This allows us to "soft code"
    our icf and url values in the weblogic.properties file. To my knowledge, nothing
    here is deprecated. If anyone knows differently, please let me know.
    Guy :)
    Jim Zhou wrote:
    You probably need to do:
    javax.naming.InitialContext ctx = new InitialContext("t3"//host:port");
    new InitialContext() will only works when client and server are in the same
    JVM.
    Regards,
    Jim Zhou.
    Ashish P. Narvekar <[email protected]> wrote in message
    news:[email protected]..
    I want to get access in my bean to the Context.PROVIDER_URL property which
    was used by the client to create the initial context.
    I know the ejbContext.getEnvironment() method is deprecated so I tried the
    following:
    javax.naming.InitialContext ctx = new InitialContext();
    String sURL =
    (String)ctx.lookup("java:comp/env/"+javax.naming.Context.PROVIDER_URL);
    This gives me a null back. What am I doing wrong?
    Or is there another way to get the provider url inside the bean code?
    Ashish P. Narvekar
    email: [email protected]

  • Problem using file based JNDI with JMS Bridge, WL 6.1sp3

              I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
              WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
              I am having trouble getting the bridge to look up the MQ queue in the file based
              JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
              instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
              to use. I am getting the following error:
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              Bridge" is getting the connections to the two adapters.>
              <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
              <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
              = weblogic.jms.adapter.JMSConnectionSpec@27166f>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              Principal for Container Managed Security Context.>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              Principal for Container Managed Security Context.>
              <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
              Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
              <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
              request.>
              <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              Bridge" failed to connect to the source destination and will try again in 25 seconds.
              (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
              <
              The configuration of the bridge, printed out in the log, is:
              <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              STARTUP! Bridge Provd Messaging Bridge's source properties are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              ConnectionFactoryJNDIName = PMS.mqQcf
              ConnectionURL = file:/opt/mqm/java/mq-jndi
              InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
              DestinationType = Queue
              DestinationJNDIName = PMS.mqProvdRequest>
              <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              STARTUP! Bridge Provd Messaging Bridge's target properties are:
              AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              Classpath=null
              DestinationType = Queue>
              Am I correct in assuming it should be using the fscontext connection factory?
              Why is it using the weblogic one?
              Jason
              

    CR081511_61sp3.jar patch should fix the problem. Make sure that the
              jar file is picked up. It should be put before other weblogic jar files.
              You should be able to tell if it is picked up by looking at the first
              couple of lines of your server log file.
              Dongbo
              Jason Kriese wrote:
              >
              > I am trying to connect an MQ queue to a Weblogic JMS queue using the JMS bridge,
              > WLS6.1sp3. I have the CR081404_61sp3.jar and CR081511_61sp3.jar patches.
              >
              > I am having trouble getting the bridge to look up the MQ queue in the file based
              > JNDI. According to the log it is trying to use a weblogic.jndi.WLInitialContextFactory
              > instead of a com.sun.jndi.fscontext.RefFSContextFactory, which is what it is configured
              > to use. I am getting the following error:
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              > Bridge" is getting the connections to the two adapters.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > RUNTIME! Bridge Provd Messaging Bridge In getConnections: isStopped = false>
              > <Sep 29, 2002 12:16:22 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > RUNTIME! Bridge Provd Messaging Bridge Getting source connection: sourceConnSpec
              > = weblogic.jms.adapter.JMSConnectionSpec@27166f>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              > Principal for Container Managed Security Context.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to locate context: java:/comp/env/wls-connector-resref>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <Connector> <Unable to determine Resource
              > Principal for Container Managed Security Context.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Warning> <Connector> << Weblogic Messaging Bridge
              > Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest on createManagedConnection.>
              >
              > <Sep 29, 2002 12:16:22 PM EDT> <Error> <Connector> <Error granting connection
              > request.>
              > <Sep 29, 2002 12:16:22 PM EDT> <Info> <MessagingBridge> <Bridge "Provd Messaging
              > Bridge" failed to connect to the source destination and will try again in 25 seconds.
              > (javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
              > ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
              > url = file:/opt/mqm/java/mq-jndi, user name = guest, password = guest)>
              > <
              >
              > The configuration of the bridge, printed out in the log, is:
              >
              > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > STARTUP! Bridge Provd Messaging Bridge's source properties are:
              > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              > Classpath=null
              > ConnectionFactoryJNDIName = PMS.mqQcf
              > ConnectionURL = file:/opt/mqm/java/mq-jndi
              > InitialConnectionFactory = com.sun.jndi.fscontext.RefFSContextFactory
              > DestinationType = Queue
              > DestinationJNDIName = PMS.mqProvdRequest>
              > <Sep 29, 2002 12:16:00 PM EDT> <Debug> <MessagingBridge> <Messaging Bridge Debugging
              > STARTUP! Bridge Provd Messaging Bridge's target properties are:
              > AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
              > Classpath=null
              > DestinationType = Queue>
              >
              > Am I correct in assuming it should be using the fscontext connection factory?
              > Why is it using the weblogic one?
              >
              > Jason
              

  • InitialContext lookup over HTTP using a full PROVIDER_URL (including path)

    Hi,
    We have a standalone Java JMS client application that is sending messages to a queue on a WebLogic (WLS 9.2 MP3) server. It uses the WLInitialContextFactory (WebLogic implementation of InitialContextFactory) class to look up the initial context over HTTP when making the connection to send messages to the queue.
    This all works fine when the client connects directly to the server - i.e. supplies the address of the server as the PROVIDER_URL. However, in our infrastructure, we cannot connect directly from this client to the server; we need to go via a HTTP proxy.
    In a basic configuration HTTP proxy we set the provider URL to be the address of the proxy server, with the proxy is configured to route all requests straight through to the WebLogic server. This configuration also works fine - the JMS client can send messages successfully.
    Unfortunately, this basic proxy configuration is still not sufficient for our Production environment. Our production proxy "fronts" multiple servers, each one identified by the first portion of the URL. So, the proxy is be configured such that requests to "http://proxy/server1/test_request" will be routed on to "http://server1/test_request", whereas a request to "http://proxy/server2/test_request" will be routed to "http://server2/test_request". This configuration works fine for basic HTTP requests, to webpages etc.
    However, when we try we use this mechanism with our JMS client over HTTP, it is not working. We set the provider URL on the client to "http://proxy/server1" in order to send a message to server1. However, we find that the WLInitialContextFactory class seems to be ignoring the final part of the URL ("server1") and still sending requests directly to the root proxy address of "http://proxy", so it doesn't work.
    I appreciate that this can be viewed as a WebLogic specific implementation issue for their WLInitialContextFactory, and I've raised a query with their support people on this. From my own research however, it seems the behaviour of their factory is not different to most other implementations - i.e. the major implementations would all have this issue.
    I'm wondering if anyone is aware of any implementations that would handle the situation I've described. If not (or otherwise!) is there something crazy about our approach that noone has catered for it?! It seems a reasonable situation to me, but maybe I'm missing something!
    Any comments, advice, etc. would be greatly appreciated, thanks.
    Regards,
    Adrian
    Edited by: AdrianFitz on 08-Apr-2010 12:21

    Hi,
    Thanks for the quick response. Would you mind providing a bit more detail on your suggestion, as am not 100% sure I understand it fully.
    If I see what you are getting at, are you talking about configuring proxy settings on my client side, similar to how I have to configure my internet browser with proxy settings when accessing the internet from within my companys LAN?
    If I'm interpreting that right, then I guess my use of the word proxy might be a bit inaccurate or lead to some confusion. What my orginal post described as a proxy should have been more accurately describes as a reverse proxy (acting primarily as a load balancer).
    Ideally, other than changing the URL slightly, the client should be 'unaware' that it is going through a proxy at all.
    Hope that clarifies somewhat, any further comments would be great! Thanks.
    Regards,
    Adrian

Maybe you are looking for

  • How do i get my B210 to use A4 tray when i send a photo by email. It keeps asking for photot tray?

    When I send an email to my printer via ePrint if there is a photo attachment it wants to use the photo tray - how can I choose which tray to use?

  • Leave attachments on the server unless i save them

    is there a way to keep attachments on my IMAP mail server unless I specifically download them? I have a fast enough internet connection that if i want to download something its not a problem so it doesnt need to be stored locally and I'd rather not w

  • Oracle Wallet manager password for B2B Host trading partner

    Hi All, I have exported one trusted certificate from B2B midtier wallet manager. I have saved it as ora_wallet.txt and and oracle.tip.adapter.b2b.WalletLocation refers to its path. I associated host trading partner delivery channel with non-repudiati

  • How can I creat a filter in ADF

    I am beginner in using ADF,so I need help PLZ I want to know how to use filter in ADF 10g I want to make filter for the month and year, I have this format(Mon,dd,yyyy) and how to do the look and feel? Regards Edited by: user807547 on Aug 5, 2009 12:2

  • Trigger Edge Animation on page load

    I am using multiple Edge Animations in a DPS document I am creating.  When I open the book, all of the animation begin to play at the same time. Is there a way to trigger the animation to start when the user turns to the page the animation is on?