IIS Plug-in with WLS 6.1 SP2 Connection Pool ?

I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable it ?
2. How do I control the pool size ?
Thanks in advance,
Tim

"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim

Similar Messages

Weblogic 6.1 sp2 Connection Pool will not connect to oci901 driver

ok, I am trying to get weblogic to connect to the connection pool in solaris. I created
the pool in the console with the following:
URL = jdbc:weblogic:oracle
Driver Class Name = weblogic.jdbc.oci.Driver
Properties = user=sa password=*****
I also set the LD_LIBRARY PATH as directed.
LD_LIBRARY_PATH=/usr/local/wlserver6.1/lib/solaris/oci901_8:ORACLE/lib
Oracle is on a seperate box then the box that Weblogic is installed on so I think
the problem is in my LD_LIBRARY_PATH. Here is the error I am getting. Any help
would be appreciated.
Starting Loading jDriver/Oracle .....
<Jun 7, 2002 9:04:25 AM CDT> <Error> <JDBC> <Cannot startup connection pool "FargoPool"
weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: System.loadLibrary(weblogicoci37) threw java.lang.UnsatisfiedLinkError:
/usr/local/wlserver6.1/lib/solaris/oci901_8/libweblogicoci37.so: ld.so.1: /home/bea/jdk131/jre/bin/../bin/sparc/native_threads/java:
fatal: libclntsh.so.9.0: open failed: No such file or directory
at weblogic.jdbc.oci.Driver.loadLibraryIfNeeded(Driver.java:226)
at weblogic.jdbc.oci.Driver.connect(Driver.java:76)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy8.addDeployment(Unknown Source)
at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
at $Proxy17.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

"Tim" <[email protected]> wrote:
>
I have the following setup.
For QA, 1 IIS Server (using plug-in from 6.1 SP2) forwarding all request
to a
cluster on the backend. (2 Physical Servers, 4 JVM's). I do have a firewall
in
between the IIS Server & the backend servers.
According to the docs, the IIS plug-in is supposed to establish a connection
pool
to the backend. I do not see this behavior.
I see a connection created/close per request.
So , I have 2 questions:
1. Does the IIS Plug-in use connection Pooling, Do you have to enable
it ?
2. How do I control the pool size ?
Thanks in advance,
TimDoes anyone from BEA monitor this newsgroup ?
I have also opened up a case (1 week old) with tech support and still do not have
an answer. This is very frustrating considering the cost of owning this environment.
Tim

IIS plug-in config with WLS 8.1 sp2

We are currently migrating from another app server and have run into problems configuring
the IIS plug-in. We have reviewed the e-docs and developer Web pages on how to
configure the plug-in but cannot successfully find information on how to point
a single IIS virtual host to multiple app servers and URIs on WLS. We're trying
to have one IIS ip:port point to many BEA app servers which can then point to
many URIs so that we can distribute load and code updates across several clusters.
Example:
ourdomain.com -> to WLServer1:8010 /app1/uri1
/app2/uri2
WLServer2:8011 /app3/uri3
/app4/uri4
The problem so far has been getting the IISProxy file to point to more than one
application server (JVM Instance) running on the two WLS machines.
Thanks for any help you can offer!

You should provide some more information. Which IP are you binding to on
          WLS? Are you specifying the same IP in the iisproxy.ini for the
          WebLogicHost?
          Show us your configuration for the iisproxy.ini.
          My best bet is that you are specifying a different IP address in the
          iisproxy.ini or perhaps you are specifying a hostname that does not resolve
          to the bound IP on WLS.
          Regards,
          Eric
          "Farhan Kazmi" <[email protected]> wrote in message
          news:[email protected]..
          > I am having a problem with the IIS plugin. It seems that when ever I
          explicitly bind a WL app server to an IP address, the IIS plugin no longer
          forwards requests on the WL. Does any one know the reason why this is
          happening.
          >
          > Note, if I do not bind to an IP address, the plug-in works fine.
          >
          > OK.... I am not even sure if this forum is working!!. I have tried to
          contact to my BEA sales rep but he is gone for the week.
          >
          > I have posted 3 or 4 questions here, and have heard no replies.

Portal server with WLS 6.1 SP2

Hi,
Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
the following problem:
I changed my WLS6.0 to 6.1 sp2 on WinNT.
Starting install Portal 4.0, it went through well. However, I couldnot
start Portal server. Hereis the massege after start Portal server (WLS is
running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method
weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
Could you help me to finger out what's wrong.

Rahul, just wanted to thank you for the info. I was having the same
problem, and changing the classpath and capacityincrement worked.
Thanks again,
John
[email protected] (Rahul Prabhu) wrote in message news:<[email protected]>...
Hi,
Modify the 'Set Classpath' in your startPortal.bat as follows:
SET CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic_sp.jar;%WEBLOGIC_HOME%\lib\weblogic.jar;
..all the existing stuff..etc.
You might also need to change the 'capacityIncrement' in your
config.xml to > 0
let me know if it goes thru.
hth,
Rahul
"Tao Huang" <[email protected]> wrote in message news:<3c362c9a$[email protected]>...
Hi,
Has anybody installed Portal server 4.0 with WLS 6.1 with service pack 2. I got
the following problem:
I changed my WLS6.0 to 6.1 sp2 on WinNT.
Starting install Portal 4.0, it went through well. However, I couldnot
start Portal server. Hereis the massege after start Portal server (WLS is
running) :
# Note: Server initialization may take several minutes.
# Please be patient.
<Jan 3, 2002 3:57:47 PM EST> <Info> <Security> <Getting boot password from
user.
>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: try to access method
weblogic/management/internal/
Helper.preloadMBeanInfos()V from class weblogic/management/Admin
at weblogic.management.Admin.initialize(Admin.java:210)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Press any key to continue . . .
Could you help me to finger out what's wrong.

WLS 10.0 JDBC connection pool shrink not working

We seem to be having a problem with jdbc connection pools not shrinking. In the connection pool properties in the WLS console we have:
Initial Capacity 4
Maximum Capacity 15
Shrink Frequency 900
However when I look at the underlying xml config file (see below) the last two values above are not present in the config!
Any ideas what is going on here?
thankyou,
Chris
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns
:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLo
cation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<name>mdmrDataSource</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac01-vip.nzlxxx01.com) (PORT = 1521))
(ADDRESS = (PROTOCOL = TCP) (HOST = xxxrac02-vip.nzlxxx01.com) (PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA =(SERVE
R = DEDICATED) (SERVICE_NAME = xxxrac.nzlami01.com)))</url>
<driver-name>oracle.jdbc.pool.OracleDataSource</driver-name>
<properties>
<property>
<name>user</name>
<value>xxx_comms</value>
</property>
<property>
<name>fastConnectionFailoverEnabled</name>
<value>true</value>
</property>
<property>
<name>implicitCachingEnabled</name>
<value>true</value>
</property>
<property>
<name>connectionCachingEnabled</name>
<value>true</value>
</property>
<property>
<name>ONSConfiguration</name>
<value>nodes=xxxrac1:6251,xxxrac2:6251</value>
</property>
</properties>
<password-encrypted>xxx</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<initial-capacity>4</initial-capacity>
<test-connections-on-reserve>true</test-connections-on-reserve>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>jdbc/XXXX</jndi-name>
<global-transactions-protocol>None</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>

You are right that the XML seems to lask those other settings... Did you
sae those settings from the console?
This is what's in one of mine....
<jdbc-connection-pool-params>
<initial-capacity>0</initial-capacity>
<max-capacity>300</max-capacity>
<shrink-frequency-seconds>900</shrink-frequency-seconds>

Oracle: slow performance with SELECT using ojdbc14 and connection pooling

Hello,
i'm working hard the last days to solve a performance problem with our customer using a oracle 10g database. For testing I used our oracle 9.2.0.1.0 database which shows the same symptoms. All doing solved nothing: the performance while using this oracle is much slower than other databases. This result I cannot trust and so I need some advice. What is missing to improve the performance on the java side?
The webapplication I use runs fast on MySQL 4.x and SQLServer 2000, but on the above mentioned Oracle it was always 4 times slower. The webapplication uses a lot of simple SELECT-Statements without complicated joins and so on (because it should run on many different databases). Doing some days of creating tests within this webapplication, I was not able to find any entrance point for a change. All databases server I'm using, having only the default configurations after a common installation.
To reduce the complexity I wrote a simple java application with connection pooling using only the latest libraries from apache-commons(dbcp, pool), and the latest ojdbc14 for oracle 9.2.
First the results than the code: MySQL needed less than 1000 millisecond, SQLServer around 1000 milliseconds and Oracle over 2000 milliseconds. I stopped pooling and the results are for Oracle even worse: over 18000 milliseconds (mysql:2500, sqlserver:4100).
I changed the classes for Oracle and used the class oracle.jdbc.pool.OracleConnectionCacheImpl from the ojdbc14-library. No difference (around 100 milliseconds more or less).
The only Select-Statement works on this table, which has one index on HICTGID.
It contains 259 entrances.:
CREATE TABLE HIERARCHYCATEGORY (
HICTGID                 NUMBER (19)   NOT NULL,
HICTGLEVEL              NUMBER (10)   NOT NULL,
HICTGEXTID              NUMBER (19)   NOT NULL,
HICTGEXTPARENTID        NUMBER (19)   NOT NULL,
HICTGNAME               VARCHAR2(255) NOT NULL
);The application simply loops through this table using
SELECT Hictgid, Hictgname FROM HIERARCHYCATEGORY WHERE HICTGID = ?, but I always open a connection before this query and closes this connection afterwards. So I use the pooling as much as possible. That's all SQL I'm using.
    protected static DataSource setupDataSource(String sDriver, String sUrl, String sUser, String sPwd) throws SQLException {
        BasicDataSource ds = new BasicDataSource();
        ds.setDriverClassName(sDriver);
        ds.setUsername(sUser);
        ds.setPassword(sPwd);
        ds.setUrl(sUrl);
        // The maximum number of active connections:
        ds.setMaxActive(3);
        // The maximum number of active connections that can remain idle in the pool,
        // without extra ones being released, or zero for no limit:
        ds.setMaxIdle(3);
        // The maximum number of milliseconds that the pool will wait (when there are no available connections)
        // for a connection to be returned before throwing an exception, or -1 to wait indefinitely:
        ds.setMaxWait(3000);
        return ds;
    }I can switch by using external properties between three databases (oracle, mysql and sqlserver) and if I want I can switch pooling off. And all actions I'm interested are logged by Log4J.
    public static Connection getConnection() throws SQLException {
        Connection result = null;
        String sJdbcDriver = m_oJbProp.getString("jdbcDriver");
        String sJdbcUrl = m_oJbProp.getString("databaseConnection");
        String sJdbcUser = m_oJbProp.getString("dbUsername");
        String sJdbcPwd = m_oJbProp.getString("dbPassword");
            try {
                if (m_oJbProp.getString("useConnectionPooling").equals("true")) {
                     if (log.isDebugEnabled()) {
                          log.debug("ConnectionPooling true");
                    if(null == m_ds) {
                        m_ds = setupDataSource(sJdbcDriver,sJdbcUrl,sJdbcUser,sJdbcPwd);
                          if (log.isDebugEnabled()) {
                               log.debug("DataSource created");
                    result = m_ds.getConnection();
                } else {
                    // No connection pooling:
                     if (log.isDebugEnabled()) {
                          log.debug("ConnectionPooling false");
                    try {
                        Class.forName(sJdbcDriver);
                        result = DriverManager.getConnection(sJdbcUrl, sJdbcUser, sJdbcPwd);
                    } catch (ClassNotFoundException cnf) {
                        log.error("Exception: Class Not Found. ", cnf);
                        System.exit(0);
(.. ErrorHandling ...)Here is the code fragment which is doing the work:
                 StringBuffer sb = new StringBuffer();
            while (lNextBottom <= lNextCeiling) {
                 con = getConnection();
                 innerSelStmt = con.prepareStatement("SELECT Hictgid, Hictgname FROM HIERARCHYCATEGORY WHERE HICTGID = ?");
                 innerSelStmt.setLong(1, lNextBottom);
                 rsInner = innerSelStmt.executeQuery();
                 if ((rsInner != null) && (rsInner.next())) {
                     sb.append(rsInner.getLong(1) + ", " + rsInner.getString(2) + "\r");
                      if (log.isDebugEnabled()) {
                           log.debug("Inner Statement: " + rsInner.getLong(1) + "\r");
                 rsInner.close();
                 con.close();
                 lNextBottom++;
             if (log.isInfoEnabled()) {
                  log.info("\rResult values: Hictgid, Hictgname \r");
                  log.info(sb.toString());
             }and the main method:
    public static void main(String[] args) {
        try {
             long lStartTime = System.currentTimeMillis();
             JdbcBasic oJb = new JdbcBasic();
             boolean bSuccess = false;
             bSuccess = oJb.getHierarchycategories();
             if (log.isInfoEnabled()) {
                  log.info("Running time: " + (System.currentTimeMillis() - lStartTime));
             if (null != m_ds) {
                 printDataSourceStats(m_ds);
                  shutdownDataSource(m_ds);
                  if (log.isInfoEnabled()) {
                       log.info("Datasource closed.");
         } catch (SQLException sqe) {
              log.error("SQLException within main-method", sqe);
    }My database values are
databaseConnection=jdbc:oracle:thin:@SERVERDB:1521:ora
jdbcDriver=oracle.jdbc.driver.OracleDriver
databaseConnection=jdbc:jtds:sqlserver://SERVERDB:1433/testdb
jdbcDriver=net.sourceforge.jtds.jdbc.Driver
databaseConnection=jdbc:mysql://localhost/testdb
jdbcDriver=com.mysql.jdbc.Driver
dbUsername=testusr
dbPassword=testpwdThanks for your reading and maybe for your help.

A few comments.
There is of course another difference between your test cases then just the database. There is also the driver. And I suspect that in at least the case with the jtds driver it is helping you along where you are doing something silly and the Oracle driver is not.
Before I explain the next part I would say the speed differences between MS-SQL and MySQL look about right I think you are aiming here for MS-SQL level performance not MySQL. (For a bunch of reasons MySQL is inherently faster but there are MANY drawbacks as well which have been well discussed on previous threads)
Here is where I believe your problem lies
while (lNextBottom <= lNextCeiling) {
                 con = getConnection();
                 innerSelStmt = con.prepareStatement("SELECT Hictgid, Hictgname FROM HIERARCHYCATEGORY WHERE HICTGID = ?");
                 innerSelStmt.setLong(1, lNextBottom);
                 rsInner = innerSelStmt.executeQuery();
                 if ((rsInner != null) && (rsInner.next())) {
                     sb.append(rsInner.getLong(1) + ", " + rsInner.getString(2) + "\r");
                      if (log.isDebugEnabled()) {
                           log.debug("Inner Statement: " + rsInner.getLong(1) + "\r");
                 rsInner.close();
                 con.close();
                 lNextBottom++;
             }There at least four things that are wrong with above.
1) Why are you preparing the statement INSIDE the loop. Let us for a moment say that the loop will spin 100 times. That means that you are preparing the same statement 100 times. This is bad. It is also very relevant because for example the Jtds driver is going to be caching the prepared statements you make so that actually while you try and prepare it 100 times it only actually does it once... but in Oracle I don't know what it is doing for sure but if it is preparing on each pass well than that bit of it is going take 100 times longer then it should.
2) You are opening and closing the connection on each pass through the loop... also a terrible idea. You need to fix this first so that you can repeatedly use the same prepared statement.
3) Why are you looping in the first place? More on this later.
4) Where do you close the PreparedStatement? It doesn't look like you do.
Okay so for starters your loop should look a lot more like this...
code]
con = getConnection();
innerSelStmt = con.prepareStatement("SELECT Hictgid, Hictgname FROM HIERARCHYCATEGORY WHERE HICTGID = ?");
while (lNextBottom <= lNextCeiling) {
innerSelStmt.setLong(1, lNextBottom);
rsInner = innerSelStmt.executeQuery();
if ((rsInner != null) && (rsInner.next())) {
sb.append(rsInner.getLong(1) + ", " + rsInner.getString(2) + "\r");
rsInner.close();
lNextBottom++;
innerSelStmt.close();
con.close();
I think the code above (and you can put your debug stuff back if you want) which uses ONE connection and ONE prepared Statement will improve your performance dramatically.
The other question though I would as is why in the hell you are doing 100 or whatever number of queries anyway. This can be done all in ONE query which again will improve performance.
Your query and such should look like this I think.
String sql = "SELECT Hictgid, Hictgname FROM HIERARCHYCATEGORY WHERE HICTGID >=? AND HICTGID<=?";
PreparedStatement ps = conn.prepareStatement(sql);
ps.setLong(1,lNextBottom );
ps.setLong(2,lNextCeiling);
ResultSet rs = ps.executeQuery();
while(rs.next()){
// your appending to string buffer code goes here
}and I can't understand why you're not doing that in the first place.

JAAS 1.0 with WLS 6.1 SP2 "Exception from LoginContext "

Hi
Iam trying to use JAAS with weblogic 6.1. SP2
In the startweblogic.cmd I have made entries like
-Djava.security.auth.login.config=sample_jaas.config
While Iam executing the code I get the following
exception
No Configuration Class Name Supplied
java.lang.NullPointerException
at javax.security.auth.login.LoginContext.loadLoginModule(LoginContext.j
ava:101)
at javax.security.auth.login.LoginContext.<init>(LoginContext.java:54)
at jsp_servlet.__login._jspService(__login.java:144)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
java.lang.NullPointerException
at jsp_servlet.__login._jspService(__login.java:157)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

May be you are not pointing at the right location of the file.
Alternatively, you can also enter login config info entry in the JAVA_HOME\jre\lib\security\java.security
file.(please refer to Login Module Developer's guide)
hope this helps
thanks-Venkata
"Sanu Thomas" <[email protected]> wrote:
>
Hi
Iam trying to use JAAS with weblogic 6.1. SP2
In the startweblogic.cmd I have made entries like
-Djava.security.auth.login.config=sample_jaas.config
While Iam executing the code I get the following
exception
No Configuration Class Name Supplied
java.lang.NullPointerException
at javax.security.auth.login.LoginContext.loadLoginModule(LoginContext.j
ava:101)
at javax.security.auth.login.LoginContext.<init>(LoginContext.java:54)
at jsp_servlet.__login._jspService(__login.java:144)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
java.lang.NullPointerException
at jsp_servlet.__login._jspService(__login.java:157)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)

VM Crash with WLS 6.1 SP2 JDK 1.3.1 on NT/MSSQL

Has anyone seen this? If we leave the system on for overnight, WLS crashes without
further message. Our setting is 128M, of course it will get out of memory error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to check tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested 402653192
bytes
goto finish
cd config\informatica
ENDLOCAL

Thanks, you are right. It's a known bug in JDK 1.3.1 01 and it has been fixed in
JDK 1.3.1 02.
<[email protected]> wrote:
That's the CompileThread asking for 402653192 bytes, so it's probably
has
nothing to do with application, WebLogic or 0x18000008. You can look
at
this bug:
http://developer.java.sun.com/developer/bugParade/bugs/4484290.html
or several other bugs very similar to this one.
Cameron Purdy <[email protected]> wrote:
FWIW - that's hex 0x18000008 ... I'd start by looking through yourcode for
the string "18000" and then grep through the WL code for the ConstantPool
equivalent in the .class files.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Yicheng Tao" <[email protected]> wrote in message
news:3cb48efe$[email protected]..
Has anyone seen this? If we leave the system on for overnight, WLS
crashes
without
further message. Our setting is 128M, of course it will get out of
memory
error
if something is asking more than that. Question is:
who is asking for 400 MB in one shot?
P.S. We have internal scheduler threads wake up every 5 minutes to
check
tasks
thru EJBs.
Exception in thread "CompileThread0" java.lang.OutOfMemoryError: requested402653192
bytes
goto finish
cd config\informatica
ENDLOCAL
Dimitri

JMS Messaging Bridge Problems with WLS 8.1 sp2

          Thank you in advance for your help.
          I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
          Q. I have this working wonderfully in an environment without clustering but once
          I try to deploy to a cluster, I am having two major problems.
          1) When the managed servers are restarted, the messaging bridges immediately complain
          about not being able to find the resource adaptor. After I manually un-target
          the messaging bridge from the cluster and re-target them, they find the resource
          adaptor but cannot connect to the source... which leads to my next problem.
          2) The messaging bridges cannot connect to the source destination whether it is
          an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
          see relative:
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
          Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
          Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
          Bridge.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
          is deployed as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
          Bridge as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
          source configurations are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          ConnectionURL = file:/e:/private/JNDI/eBusDev02
          DestinationType = Queue
          DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
          InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
          ConnectionFactoryJNDIName = jms.oes.MQ-QCF
          .>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
          target configurations are:
          AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
          Classpath=null
          ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
          DestinationType = Queue
          DestinationJNDIName = jms/oes/ADV-REPLYQ
          InitialContextFactory = weblogic.jndi.WLInitialContextFactory
          ConnectionFactoryJNDIName = jms/oes/QCF
          .>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
          is successfully initialized.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          has been successfully initialized as a migratable.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
          Bridge.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          has been successfully activated..>
          ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
          <Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
          two adapters.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
          <Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
          Getting source connection.>
          ####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
          <ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
          <Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
          and will try again in 15 seconds. (java.lang.NullPointerException)>
          I know the queues are up and I am pretty sure my MQ client configuration is correct.
          Is there anyway to get more information about the NullPointerException or the
          error being encountered?


Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
          If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
          Tom

Problem with Weblogic 9.1 JDBC connection pooling

Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?

Roy van Rijn wrote:
Hi,
We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
Any ideas what this could be? Are there known errors?Hi. Please try setting the pool's idle-connection-timeout to 10 seconds or something
reasonable, and we'll forcibly retract any leaked connections. So you don't write any
JDBC code yourself, right?
Joe

IIS Plug for WLS 6.1 SP2: The specified procedure could not be found.

I get an the following error message "The specified procedure could not be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1 sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

Thank you for posting your answer, and then solution! :> I was fighting
with my IIS/WLS installation last night when I was about to give up, I came
across your posting. Although I'm playing with 7, I thought I would try
reading your posting anyways, and thankfully I did. What I saw, reminded me
to look at the steps one more time and I found I wasn't forwarding the
.wlforward piece on! So thank you veyr much! :>>>>
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
Fixed it.
I had mapped .wlforward to iisforward.dll instead of iisproxy.dll
/Jonas
"Jonas Klemming" <[email protected]> wrote in message
news:[email protected]..
I get an the following error message "The specified procedure could not
be
found." in my browser when trying to use the IIS-proxy plugin on WLS 6.1sp2
Windows 2000
Has anyone else encountered this message? Any solutions?
Regards,
Jonas Klemming

WLS 6.1 SP2 NSAPI and iPlanet (Sun One) issues

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

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

WLS 6.1 SP2, iPlanet 6 & NSAPI problems

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

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

Sun Identity Server 6.1 with Weblogic 8.1 sp2

Hi,
I've installed the IS 6.1 with WLS 8.1 sp2 and the agent 2.1.1 and followed the agent configuration guide to configure the xml files (web.xml and weblogic.xml) and agent authenticator.
When I login to the restricted resource, the browser is redirected to the IS server login page. After login, the browser is redirected back to the resource with 403 forbidden.
Is there any step missing? Should I additional add some policy in the IS console? .....
Clive

I have just installed Sun Identity Server 6.2 with WebLogic 8.1 SP3 and am experiencing the same results. Have you resolved this issue in your environment? We are evaluating Portal Server running on a BEA WLS Container and thus do not have Sun Support on the Identity Server Component of this configuration.

Iplanet 6.x, NSAP & WLS 6.1 SP2

This is very strange. I can get NSAPI with iplanet 4.x to come up fine (everything proxies, etc. as it should). When we try to get iPlane 6.x working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running everything on Solaris.
Does anyone have or know of some good documentation that might describe how to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet 6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonder if the differences between the two are really that great. I checked BEA's doc...and like I said...it seemed a bit cryptic...someone told me ther was a typo or two regarding what was to go in magnus or was it obj.conf...I don't recall..it's just frustrating trying to get NSAPI up and running with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

Thanks Kumar. Does the syntax change (such as WebLogicCluster=xxxxxxxxxxxxxxx) if
we are running a single instance of WebLogic (a non-clustered environment)?
Thanks,
Doug
Kumar Allamraju <[email protected]> wrote:
In iplanet 6.x
magnus.conf should have
Init fn="load-modules" funcs="wl_proxy,wl_init" shlib=/usr/local/netscape/plugins/libproxy.so
Init fn="wl_init"
and obj.conf should have
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy \
WebLogicCluster="myweblogic.com:7001,yourweblogic.com:7001,\
theirweblogic.com:7001" PathTrim="/weblogic"
</Object>
Pls post the exact errors that you are seeing, so that we can help
Kumar
"Doug E." wrote:
This is very strange. I can get NSAPI with iplanet 4.x to come up fine(everything proxies, etc. as it should). When we try to get iPlane 6.x
working with NSAPI and WLS 6.1 SP2...nothing..doesn't work. We're running
everything on Solaris.
Does anyone have or know of some good documentation that might describehow to get NSAPI working between WLS 6.1 and iPlanet 6...all the examples
I've been seeing are mostly Windows paths, .dlls', etc. I'd love to see
some working magnus.conf & obj.conf, etc. using WLS6.1 SP2 and iPlanet
6...we're not clustered and we're not using SSL (yet) so it's pretty vanilla.
What's blowing my mind is why iplanet 4.x works and 6.x doesn;t?? I wonderif the differences between the two are really that great. I checked BEA's
doc...and like I said...it seemed a bit cryptic...someone told me ther
was a typo or two regarding what was to go in magnus or was it obj.conf...I
don't recall..it's just frustrating trying to get NSAPI up and running
with WLS 6.1 SP2 and iPlanet 6. Any ideas? Thanks!!

IIS Plug-in with WLS 6.1 SP2 Connection Pool ?

Similar Messages

Maybe you are looking for