IIS to weblogic 6.0 cluster

Hi Everyone,
Hope that you can help me with this problem.
I am trying to configure my IIS to proxy to a cluster.
However, when I try to access a simple jsp, it returns a http 403.1 error.
Can anyone help me with this?
Thanks
Alex

Seems 6.0 has more than a few proxy problems. We are running IPlanet and have
had no success in running the 6.0 proxy.
FYI. We have started using the 5.1 proxy in 6.0 successfully; you might give
it a try. Not sure we want to put this in production in this condition however.
Matt Raible wrote:
Has anyone been successfully able to get the IIS Proxy working with WLS 6.0
on Win2K? I've been trying for days, working with a support engineer at BEA
and everything, but no luck.
Thanks,
Matt

Similar Messages

Jaas.jar conflict in Weblogic 6.1 cluster

We are using a Custom realm for Weblogic which communicates with Tivoli Policy
director for user authentication and authorization.
For communicating with PolicyDirector, We need to have IBM's jaas.jar as a JDK
extension(in jre/lib/ext directory)along with some more jar files.We never had
problems when running Weblogic in stand alone mode.But when we are trying to run
Weblogic as a cluster, Managed Server is not able to communicate with Admin Server
giving following exception:
Starting WebLogic Server ....
Connecting to http://166.57.31.66:8101...
<Feb 7, 2002 1:52:26 PM EST> <Info> <Logging> <FileLogger Opened.>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <System has file
descriptor limits of - soft: '1024', hard: '1024'>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <Using effective
file descriptor limit of: '1024' open sockets/files.>
<Feb 7, 2002 1:52:27 PM EST> <Info> <Posix Performance Pack> <Allocating: '3'
POSIX reader threads>
<Feb 7, 2002 1:52:28 PM EST> <Emergency> <Configuration Management> <Errors detected
attempting to connect to admin server at 166.57.31.66:8101 during initialization
of managed server ( 166.57.31.69:8001 ). The reported error was: < null > This
condition generally results when the managed and admin servers are using the same
listen address and port.>
<Feb 7, 2002 1:52:28 PM EST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException - with nested
exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set]]
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set
     at javax.security.auth.Subject$SecureSet.add(d:/jn130-userlvl/src/classes/sov/javax/security/auth/Subject.java:1098)
     at weblogic.common.internal.BootServicesStub.writeUserInfoToSubject(BootServicesStub.java:72)
     at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:80)
     at weblogic.security.acl.internal.Security.authenticate(Security.java:108)
     at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:509)
     at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:364)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:336)
     at weblogic.jndi.Environment.getContext(Environment.java:156)
     at weblogic.jndi.Environment.getInitialContext(Environment.java:139)
     at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:950)
     at weblogic.management.Admin.start(Admin.java:351)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
     at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException - with nested exception:
[javax.naming.AuthenticationException [Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set]]
     at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:959)
     at weblogic.management.Admin.start(Admin.java:351)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:372)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
     at weblogic.Server.main(Server.java:35)
When we removed IBM's jaas.jar from jdk/jre/lib/ext to check the clustering.It
works fine.But We need to have jaas.jar for our custom realm.
Thanks.
Jagan.

Hi jerry
i already got that problem solved by removing jaas.jar file
from class path.
i don'nt how it is working with out in classpath...?
Jerry <[email protected]> wrote:
Hi Nivas,
I think that the problem you are seeing has something to do with the
placement of jaas.jar in your classpath
On WebLogic server, put jaas.jar in the classpath after weblogic.jar.
I would bet that you have it placed before weblogic.jar right now.
I don't think the exception that you're seeing right now has anything
to do with your weblogic.policy file right now, so I think it is
safe to not worry about it right now.
Hope this helps,
Joe Jerry

Javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean

Hi,everyone:
I am running into this error when I call a webService :My weblogic version is 10.3.5 and have applied the patch N5G9.
javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy117.getLoginUserInfoByCzryDm(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy118.getLoginUserInfoByCzryDm(Unknown Source)
at com.hkgt.sso.access.ZRWebServiceProxyImpl.getLoginUserInfoByCzryDm(ZRWebServiceProxyImpl.java:106)
at com.hkgt.sso.access.WebServiceAuthenticationHandler.doAuthentication(WebServiceAuthenticationHandler.java:71)
at com.hkgt.sso.access.AMManagerImpl.doAuthentication(AMManagerImpl.java:165)
at com.hkgt.sso.authserver.SSOLoginServlet.doPost(SSOLoginServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3723)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3689)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
However it works fine under another machine(say machine A) when I call the same webservice. I tried to copy the whole domain to the problematic machine, this error still appears.
Does anyone have any suggestions. Thank you !

Hi,everyone:
I am running into this error when I call a webService :My weblogic version is 10.3.5 and have applied the patch N5G9.
javax.xml.ws.soap.SOAPFaultException: ClusterRoutingTubeUtils weblogic.wsee.jaxws.cluster.ClusterRoutingTubeUtils@6ad8e382 not ready, no WseeClusterRoutingRuntimeMBean/WseeRuntimeMBean
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:197)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:125)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:95)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:136)
at $Proxy117.getLoginUserInfoByCzryDm(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.wsee.jaxws.spi.ClientInstanceInvocationHandler.invoke(ClientInstanceInvocationHandler.java:84)
at $Proxy118.getLoginUserInfoByCzryDm(Unknown Source)
at com.hkgt.sso.access.ZRWebServiceProxyImpl.getLoginUserInfoByCzryDm(ZRWebServiceProxyImpl.java:106)
at com.hkgt.sso.access.WebServiceAuthenticationHandler.doAuthentication(WebServiceAuthenticationHandler.java:71)
at com.hkgt.sso.access.AMManagerImpl.doAuthentication(AMManagerImpl.java:165)
at com.hkgt.sso.authserver.SSOLoginServlet.doPost(SSOLoginServlet.java:175)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3723)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3689)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2285)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2184)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1459)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
However it works fine under another machine(say machine A) when I call the same webservice. I tried to copy the whole domain to the problematic machine, this error still appears.
Does anyone have any suggestions. Thank you !

Problems processing a large batch of data within a Weblogic 5.1 cluster

I have about exhausted my sources of information on this, so I ask the
          experts:
          The project I am involved with is attempting to build a scheduled
          process on a 5.1 cluster which will retrieve hundreds to thousands of
          database rows from a small group of Oracle tables and then submit them
          into a legacy system for processing. The problems we face are:
          1. We cannot have duplicate data submitted from startup classes on
          different servers in the cluster
          2. We need the process to run if even only one machine in the cluster is
          available and therefore do not want to tie the process to a single
          machine
          3. We would prefer to distribute the workload across all servers
          currently available in the cluster, but this is not mandatory.
          One solution is to retrieve each record as an Entity bean, attempting to
          update it to "in process" and rejecting any failures thus utilizing
          database locking, but due to the large number of records being processed
          this is much too resource intensive as well as time consuming.
          We have looked into JMS based solutions, but it appears that JMS under
          5.1 is tied to a specific server (failing case 2).
          One acceptable approach that we have yet to find a way of implementing
          is to have a "singleton" session bean, only one of which exists on the
          cluster (though it may exist anywhere on the cluster). I have run
          across a number of other applications for just this sort of EJB, but is
          it possible to implement?
          Sadly, Weblogic 6.0 cannot be part of the solution as our company will
          not be adopting it until well after this project's delivery date.
          Are we missing something obvious?
          Many thanks!
          -Steve


You have to have all the servers in the cluster polling for work out of the
          database. Use the database as a scheduling / routing mechanism. Use timers
          on each server in the cluster to kick off a "find me one thing to do"
          process every n minutes or seconds.
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com
          +1.617.623.5782
          WebLogic Consulting Available
          "Steven Wicklund" <[email protected]> wrote in message
          news:[email protected]...
          > I have about exhausted my sources of information on this, so I ask the
          > experts:
          > The project I am involved with is attempting to build a scheduled
          > process on a 5.1 cluster which will retrieve hundreds to thousands of
          > database rows from a small group of Oracle tables and then submit them
          > into a legacy system for processing. The problems we face are:
          > 1. We cannot have duplicate data submitted from startup classes on
          > different servers in the cluster
          > 2. We need the process to run if even only one machine in the cluster is
          > available and therefore do not want to tie the process to a single
          > machine
          > 3. We would prefer to distribute the workload across all servers
          > currently available in the cluster, but this is not mandatory.
          >
          > One solution is to retrieve each record as an Entity bean, attempting to
          > update it to "in process" and rejecting any failures thus utilizing
          > database locking, but due to the large number of records being processed
          > this is much too resource intensive as well as time consuming.
          >
          > We have looked into JMS based solutions, but it appears that JMS under
          > 5.1 is tied to a specific server (failing case 2).
          >
          > One acceptable approach that we have yet to find a way of implementing
          > is to have a "singleton" session bean, only one of which exists on the
          > cluster (though it may exist anywhere on the cluster). I have run
          > across a number of other applications for just this sort of EJB, but is
          > it possible to implement?
          >
          > Sadly, Weblogic 6.0 cannot be part of the solution as our company will
          > not be adopting it until well after this project's delivery date.
          >
          > Are we missing something obvious?
          > Many thanks!
          > -Steve
          >

WL 9.2 - IIS plugin - WebLogic Realm

We are upgrading from WebLogic 8.1 to WebLogic 9.2. We use IIS 6.0 as a proxy. IIS has an ISAPI plugin that authenticates our users using SPENGO and then forwards the request to WL.
In 8.1, the request was authenticated by our ISAPI plugin, before the request was forwarded to our application running in WL.
In 9.2, logs show that the request gets authenticated by our ISAPI plugin, but when the request is forwarded to WL, WL sends back another authentication prompt to login to WebLogic. I am using the default WebLogic security realm without any changes.
HTTP header
WWW-Authenticate: Basic realm="WebLogic Server"
If I access our application directly on WebLogic (bypassing IIS), I can access the application without being prompted to login by WL. The ear does not have any security configured in it. I believe having an authenticated header in the request to WL is causing the additional request. I would like to disable WL from asking to login to its security because we already have our security mechanism in place on IIS.
Is there a way to disable WL security?
Thanks.

In case anyone else gets this error, it is a known issue that WebLogic support provided the resolution.
In config.xml, I had to add the following tag before the end of the </security-configuration> section:
<enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>
After this tag was added and the server restarted, WebLogic did not prompt to login to the WebLogic realm.

Error when running weblogic 10 in cluster

I am testing out weblogic 10 and when I run it with a single managed server and an admin server then everything works fine. When I run it in a cluster with a valid test cluster license, I get the following error. Does anyone know what the cause of this error is and how to fix it? Thanks for the help.
          <Sep 14, 2007 7:06:03 PM UTC> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.dgc.DGCServerImpl.renewLease([I)
          java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext.
          java.lang.ClassCastException: weblogic.rjvm.ImmutableServiceContext
          at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:369)
          at weblogic.utils.io.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:265)
          at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1534)
          at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
          at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1591)
          at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
          at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
          at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:195)
          at weblogic.rjvm.MsgAbbrevInputStream.readObject(MsgAbbrevInputStream.java:565)
          at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:191)
          at weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
          at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
          at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
          at weblogic.security.service.SecurityManager.runAs(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
          at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
          at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
          at weblogic.work.SelfTuningWorkManagerImpl.schedule(SelfTuningWorkManagerImpl.java:126)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:321)
          at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:918)
          at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1084)
          at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1001)
          at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:230)
          at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:877)
          at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:446)
          at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:368)
          at weblogic.socket.AbstractMuxableSocket.dispatch(AbstractMuxableSocket.java:383)
          at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:872)
          at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:818)
          at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:192)
          at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:174)
          at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
          at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
          >

We solved this by increasing the number of open files, by adding the following in the /etc/security/limits.conf
* soft nofile 50000
* hard nofile 50000

Problem connecting weblogic server to cluster

          Hi,
          I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
          -Dweblogic.admin.host=http://admin-ipaddr:7001....,
          I get the following error
          Starting WebLogic Server ....
          <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
          weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
          denied in realm weblogic
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
          at weblogic.management.Admin.initialize(Admin.java:275)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          at weblogic.Server.main(Server.java:32)
          >
          <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
          Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
          weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
          m denied in realm weblogic]
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
          at weblogic.management.Admin.initialize(Admin.java:275)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          at weblogic.Server.main(Server.java:32)
          >
          I understand that all managed servers are supposed to use the same config file as the Admin server.
          Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
          I am struck up on this. I'd greatly appreciate it some body could help me out.
          thanks a lot,
          Anil.


-Dweblogic.admin.host=admin-ipaddr:7001, you shouldn't specify protocol. Also please use beta newsgroup for 6.0 related questions.
          anil wrote:
          > Hi,
          > I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
          > -Dweblogic.admin.host=http://admin-ipaddr:7001....,
          >
          > I get the following error
          > Starting WebLogic Server ....
          > <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
          > weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
          > denied in realm weblogic
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
          > at weblogic.management.Admin.initialize(Admin.java:275)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          > at weblogic.Server.main(Server.java:32)
          > >
          > <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
          > Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
          > weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
          > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
          > m denied in realm weblogic]
          > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
          > at weblogic.management.Admin.initialize(Admin.java:275)
          > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
          > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
          > at weblogic.Server.main(Server.java:32)
          > >
          > ***************************************************************************
          > I understand that all managed servers are supposed to use the same config file as the Admin server.
          >
          > Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
          >
          > I am struck up on this. I'd greatly appreciate it some body could help me out.
          >
          > thanks a lot,
          > Anil.

Reg. Weblogic 8.1 cluster licence?

Hi,
I have received Weblogic platform 8.1 CD with the 1 year developer licence.
Can i create a cluster and test my application in this cluster.
Do i need a seperate cluster licence to test my application,
to support load balancing and failover??
rgds,
girish

On 3 Jun 2004 01:50:03 -0700, "girish" <[email protected]>
wrote:
>
Hi,
I have received Weblogic platform 8.1 CD with the 1 year developer licence.
Can i create a cluster and test my application in this cluster.
Do i need a seperate cluster licence to test my application,
to support load balancing and failover??
rgds,
girishIn general the developer license gives you the ability to configure
and run clusters. One really easy way to tell is to install it and
look @ licence.bea. You'll see(or not see) a cluster component
in there.
~Ryan Upton

Weblogic 9.2 cluster install across 2 linux servers - authentication errors

Hello all,
                    I am currently trying to install a 9.2 cluster across two Linux machines, but am having a few problems that I was hoping someone here could help with. I?ve been reading the documentation, but feel as though it?s getting me nowhere.
                    I have two servers, on which I have installed weblogic portal 9.2. On the first I have then used the configuration wizard to great an admin server and cluster members 1, 2 and 3.
                    A cluster is created and the three cluster members are assigned to it.
                    Then I configure two unix machines, for the servers 1 and 2.
                    I assign the admin server and cluster member 1 to the first server. Cluster members 2 and 3 are assigned to the second server.
                    The connection pools and JMS stores I left as the default values.
                    The configuration completes and a domain is created on the first server.
                    I have copied the complete user_projects directory to the second server. I didn?t want to go through the configuration steps on each server that weblogic was to be installed on, so this looked like the easiest way to get the startManagedWeblogic scripts onto the second server. Also I didn?t find anything in the documentation that mentioned how to set up a cluster across multiple machines in any detail, only how to install multiple instances on a single server and run them as a cluster.
                    I manage to start the admin server ok and can connect through the web based admin console.
                    The first cluster member also starts up on the first server.
                    Now I go to the second server again, and when I try to start the cluster members here I get Authentication errors:
                    <Jan 31, 2007 2:56:22 PM CET> <Error> <Security> <BEA-090854> <SAMLCredentialMapper provider initialization failed: Could not retrieve credentials for AssertionSigningKey.>
          <Jan 31, 2007 2:56:23 PM CET> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
          <Jan 31, 2007 2:56:23 PM CET> <Error> <com.bea.weblogic.kernel> <000000> <[Security:090735]The DBMS connection was not usable>
          <Jan 31, 2007 2:56:23 PM CET> <Critical> <Security> <BEA-090403> <Authentication for user weblogic denied>
          <Jan 31, 2007 2:56:23 PM CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
          weblogic.security.SecurityInitializationException: Authentication for user weblogic denied
                  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:947)
                  at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
                  at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
                  at weblogic.security.SecurityService.start(SecurityService.java:141)
                  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
                  Truncated. see log file for complete stacktrace
          >
          <Jan 31, 2007 2:56:24 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
          <Jan 31, 2007 2:56:24 PM CET> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
          <Jan 31, 2007 2:56:24 PM CET> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
          Autonomy engine processes stopped
                              What am I doing wrong / forgetting to do.
                    Any help or suggestions are most helpful
                    Regards
                              IV

Hello ,
          I can help you in this regard, (let me see).
          Let me start from the beginning.
          Assumptions:
          M1 is hosting 1-Admin server(AdminServer), 2-Managed Server(ms1,ms2),
          M2 is hosting 1 -managed server (ms3)
          1. Install WebLogic Server/Portal product on M1 and M2 say /home/user1/bea1 - on M1
          /home/user1/bea1 - on M2
          2. Create Cluster Domain using ConfigWiz/WLST.
               [ here I will talk abt Config Wiz)
               - Open config Wiz
          - Create domain in Production Mode.(ideally Cluster is not supported in Dev mode )
               - Create 1 Admin server, 3 Managed server Host = <M1> and config SSL port
                    AdminServer ? Host_M1
                    Ms1     ? Host_M1
                    Ms2     ? Host_M1
                    Ms3     ? Host_M2
          NOTE: *** Don't use IP addresses - use hostnames. The hostnames need to be specified in the correct format. When specifying a hostname, use the receiving server side's rules for SSL certificate hostname format when specifying the server address. The address that a client uses needs to match up with the server's SSL certificate host identity field ((example: pint21.bea.com on both server/client side, not just pint21 and other pint21.bea.com)
          Using the 'keytool' Java utility, verify the content of hostname identity embedded in the demo SSL certificate
          $ keytool -list -v -alias demoidentity -keystore DemoIdentity.jks
          Owner: CN=pisol18, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
          -     Config Data Source (conn pool) to Any DB Type you like, test them and run the DB scripts if applicable (Run DB).
          3. Create Managed Server template Using Pack/Unpack tool
          3.1     Using <WL_HOME>\common\bin\pack.cmd with ?managed option create managed server template.
          3.2     Using <WL_HOME>\common\bin\unpack.cmd on M2 to create the domain on Host2
          4. Starting the Admin Server
          5. Start the Managed server in many way. As given on edocs.
          http://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/clusters/StartOrStopAServer.html
          I hope this helps you,
          Thanks
          Viswa
          ------------

ORA-01017: invalid username/password; logon denied on Weblogic 9.0 cluster

I am experiencing the following exception in Weblogic 9.0 server cluster environment. The same code works fine in non-cluster environment. The problem happens every now and then and would go away temporarily after recycling the domains. The Oracle database that the backend system connects to is 9.0.2.6. I am using the ocjdbc14.jar jdbc driver that comes with the Weblogic 9.0 on the client side to connect. I really appreciate any help or clue.
Ashkan
Error on dequeuing requests
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.O3log.receive2nd(O3log.java:496)
     at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:278)
     at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
     at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:291)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:277)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:259)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:241)
     at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
     at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:810)
     at org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:857)
     at org.springframework.jdbc.object.StoredProcedure.execute(StoredProcedure.java:102)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDequeue.dequeue(ServiceProviderDequeue.java:32)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDAO.dequeueRequest(ServiceProviderDAO.java:48)
     at com.rwi.wam.ejb.WAMRequestMessageBean.onMessage(WAMRequestMessageBean.java:168)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:425)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3069)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2989)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:3448)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

Hi, I can tell you that you're not using any WebLogic
JDBC code. You're getting a connection directly from
the Oracle drive, and you can change the vesion of the
drive if you want by changing the ojdbc14.jar in the
weblogic server\lib directory.
However, I believe the problem is an inherent weakness
at the DBMS. The DBMS listener process can sometimes
be temporarily swamped if it gets too many connection
requests at one time, and will fail some of them even if
they are all identical and correct.
This is one of the major reasons you should use WebLogic
connection pools so you always get already-made and
tested connections.
Another huge danger is that you are using DriverManager
calls. These are very bad in multithreaded applications
like WebLogic, because all DriverManager calls (including
some internal ones that all JDBC drivers call all the time,
are class-synchronized! This means that one call to
getConnection() will probably bolock all other running
JDBC in the whole JVM. If you can change the springframework
code to use WebLogic DataSources to pools, you'll be much
better off.
Joe
Ashkan Gholam-Zadeh wrote:
I am experiencing the following exception in Weblogic 9.0 server cluster environment. The same code works fine in non-cluster environment. The problem happens every now and then and would go away temporarily after recycling the domains. The Oracle database that the backend system connects to is 9.0.2.6. I am using the ocjdbc14.jar jdbc driver that comes with the Weblogic 9.0 on the client side to connect. I really appreciate any help or clue.
Ashkan
Error on dequeuing requests
org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: ORA-01017: invalid username/password; logon denied
java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:289)
     at oracle.jdbc.ttc7.O3log.receive2nd(O3log.java:496)
     at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:278)
     at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:346)
     at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;Ljava.lang.ClassLoader;)Ljava.sql.Connection;(Unknown Source)
     at java.sql.DriverManager.getConnection(Ljava.lang.String;Ljava.util.Properties;)Ljava.sql.Connection;(Unknown Source)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:291)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:277)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnectionFromDriverManager(DriverManagerDataSource.java:259)
     at org.springframework.jdbc.datasource.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:241)
     at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
     at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:810)
     at org.springframework.jdbc.core.JdbcTemplate.call(JdbcTemplate.java:857)
     at org.springframework.jdbc.object.StoredProcedure.execute(StoredProcedure.java:102)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDequeue.dequeue(ServiceProviderDequeue.java:32)
     at com.rwi.wam.dao.serviceprovider.ServiceProviderDAO.dequeueRequest(ServiceProviderDAO.java:48)
     at com.rwi.wam.ejb.WAMRequestMessageBean.onMessage(WAMRequestMessageBean.java:168)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:425)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:332)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:288)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3069)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2989)
     at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:3448)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)

Weblogic - Fusion Middleware Cluster - Clarification - 11g

Hello All,
I've checked the forum and would need just a little clarification regarding weblogic cluster & fusion Middleware + Load Balancing.
My current Setup is:
==============
1 APP Server: Runs Fusion Middleware 11g Forms and Reports + Weblogic + OHS (windows 2008R2)
1 DB Server: Standalone database 11gR2 installation (windows 2008R2)
I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
What do I do? Do I install the new app server like the first one and just add it to an existing domain(clustering)? Is there a difference between fusion middleware clustering and weblogic clustering (as in database RAC - the whole idea being failover 24/7 no single point of failure?)
I would appreciate any assistance, and need not great detail, just need to make sense of the whole thing.
I'm already on with the following document: [http://docs.oracle.com/cd/E21764_01/web.1111/e13709/toc.htm]
Thanks in advance
Jan S.

Hi Jan
You are almost there. I would like to clarify some points for you.
1. You already have WLS + Forms/Reports and of course Backend RCU Database that has all the meta data for Forms/Reports. This RCU database is on single server Oracle database.
I've been asked to add a new app server and setup load balancing between the two app servers in order to split the incoming forms & reports requests.
2. The first question for above requirement is, do you need the new Server on the same Existing physical box or a different remote physical box. If on the same physical box (which I doubt), then there is NO need to install any new software like WLS, Forms/Reports etc. All you do is create a new Managed Server and add it to your existing Domain. NOW, do you currently have a Clustered Domain. If you, all you do is add this new server to that cluster. If not, then you need to add a New cluster and add your old and this NEW managed server to that Cluster. If your existing domain is only single server and is very recent, I would prefer create a brand new Cluster domain with Different Port numbers (you can change port numbers anytime later also). Then add/create one or two managed servers.
3. If you are give a new physical box for this new managed server, then YES, you do need to install exactly SAME version of Weblogic Server and same version of Forms/Reports server on this new machine. Then create a Cluster Domain with 2 managed servers. One managed server on first box where you will have Admin Server + Managed Server 1. Then run pack command. Go to other machine. Run unpack command to create second Managed Server. Now you got 2 managed servers in a Single Clustered Domain.
4. Now comes the Load Balancing Part. Never ever expose the individual managed server host and port and WebApp urls for any Clustered Domain. Instead install Apache Http Web App Server which I guess is same as Oracle Http Server. Oracle renamed it (there is no need for this, but it may be company policy). Anyhow all you do is, just install Apache Web Server. Copy some .dll (.so on linux) files to this apache installation. Then update httpd.conf file or weblogic.conf file with details of clustered weblogic domain managed servers host, port, url patterns etc.
5. All the External Requests will now go to Apache Web Server like http://apachehost:apacheport/xxxUrl. This Apache will take care of LOAD Balancing, Failover etc and based on input url pattern will redirect requests to back end cluster of weblogic managed servers.
6. The backend RCU database that has Metadata for Forms/Reports NEED NOT be Clustered. If you really have extremely heavy data, then you can have Oracle RAC database. Have multiple DB Nodes in RAC. For each Node, create a DataSource in Weblogic conolse and finally one master Multi Data Soiurce that uses all these single Datasources. But very rarely you really need RAC or clustered database for RCU. So for now, just go with single non-clustered Database that has RCU Schemas.
In conclusion, even though you have Forms/Reports, just follow the standard normal Weblogic Clustered domain Architecture for your requirement. All clustering is at application server level and nothing to do with any Oracles softwares like SOA/BPM, Forms/Report, BI etc etc.
Thanks
Ravi Jegga

Can't get IIS to WebLogic Proxying to Work

Hi all,
It seems this post adds to many similar ones - the issue being that of successfully
deploying iisproxy.dll, iisforward.dll and iisproxy.ini. I have IIS 4.0 running
on NT 4.0 Server, and WebLogic 6.0 SP1 running on a seperate machine under Windows
2000.
I can proxy by file type no problem, it's proxying by path/proxying servlets that's
biting me.
I have followed the instructions at http://e-docs.bea.com/wls/docs60/adminguide/isapi.html#100367.
Here are the instructions and what I've done in response to them:
"1. Place the iisforward.dll file in the same directory as the iisproxy.dll file
and add the iisforward.dll file as a filter service in IIS"
I copied iisforward.dll and iisproxy.dll from my weblogic machine to C:\WINNT\system32\inetsrv
on the IIS machine.
I added iisforward.dll as a filter service in MS Management Console by choosing
properties > ISAPI FIlters tab > Add. Here I browsed to iisforward.dll and named
the filter WebLogic Filter Servlet (The name is not important, right?)
"2. Register .wlforward as a special file type to be handled by iisproxy.dll."
So, in MS Management Console I chose properties > home directory > Configuration
Add and browsed to iisproxy.dll and registered it with the file type .wlforward."3. Define the property WlForwardPath in iisproxy.ini. WlForwardPath defines the
path that is proxied to WebLogic Server."
So I added the following line to iisproxy.ini on the WebLogic machine AND on the
IIS machine:
WLForwardPath=/CIM2WebApplication
My web app is in exploded directory form at E:\bea\wlserver6.0sp1\config\terrance\applications\CIM2WebApplication
(where CIM2WebApplication is the root directory of the app in which WEB_INF and
my jsps and html files are located.)
In addition, in web.xml, I have defined a servlet as follows:
<servlet>
<servlet-name>register</servlet-name>
<servlet-class>net.companyname.cimsweb.RegisterUser</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>register</servlet-name>
<url-pattern>/register</url-pattern>
</servlet-mapping>
(Excuse all this the verbosity, but hopefully no-one will wonder what exactly
I did!)
When I use the following URL http://iiserverip/CIMS2WebApplication/register I
get a 404 from IIS (i.e. nothing at all is getting proxied to WL, not even a wrong
url)
OK, I've finished! If someone would like to catch their breath and help me out
I'd be extremely grateful! Thanks so much.
Terrance

I think we honor both WLForwardPath and WlForwardPath in the latest 5.1 service
pack and 61 release.
thanks
Jong
"Nasir" <[email protected]> wrote:
>
I have had similar problems, there is an error in the documentation,
WlForwardPath
needs to be spelled with a lower case "l".
Nasir
WLForwardPath=/CIM2WebApplication
"Anurag Wakhlu" <[email protected]> wrote:
Hi,
I have a similar problem. (WLS sp8, win2k, IIS)
Proxy by path does not work. Proxy by extension works.
AW
"Jong Lee" <[email protected]> wrote in message
news:[email protected]...
Did you try to request the servlet without IIS proxy?
Please feel free to contact customer support to help you with thissetup
step-by-step.
thanks
Jong
"Terrance Goldman" <[email protected]> wrote:
Hi all,
It seems this post adds to many similar ones - the issue being that
of
successfully
deploying iisproxy.dll, iisforward.dll and iisproxy.ini. I have IIS4.0
running
on NT 4.0 Server, and WebLogic 6.0 SP1 running on a seperate machine
under Windows
2000.
I can proxy by file type no problem, it's proxying by path/proxyingservlets
that's
biting me.
I have followed the instructions at
http://e-docs.bea.com/wls/docs60/adminguide/isapi.html#100367.
Here are the instructions and what I've done in response to them:
"1. Place the iisforward.dll file in the same directory as theiisproxy.dll
file
and add the iisforward.dll file as a filter service in IIS"
I copied iisforward.dll and iisproxy.dll from my weblogic machineto
C:\WINNT\system32\inetsrv
on the IIS machine.
I added iisforward.dll as a filter service in MS Management Consoleby
choosing
properties > ISAPI FIlters tab > Add. Here I browsed to iisforward.dll
and named
the filter WebLogic Filter Servlet (The name is not important, right?)
"2. Register .wlforward as a special file type to be handled byiisproxy.dll."
So, in MS Management Console I chose properties > home directoryConfiguration
Add and browsed to iisproxy.dll and registered it with the filetype
.wlforward.
"3. Define the property WlForwardPath in iisproxy.ini. WlForwardPath
defines the
path that is proxied to WebLogic Server."
So I added the following line to iisproxy.ini on the WebLogic machine
AND on the
IIS machine:
WLForwardPath=/CIM2WebApplication
My web app is in exploded directory form atE:\bea\wlserver6.0sp1\config\terrance\applications\CIM2WebApplication
(where CIM2WebApplication is the root directory of the app in whichWEB_INF
and
my jsps and html files are located.)
In addition, in web.xml, I have defined a servlet as follows:
<servlet>
<servlet-name>register</servlet-name>
<servlet-class>net.companyname.cimsweb.RegisterUser</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>register</servlet-name>
<url-pattern>/register</url-pattern>
</servlet-mapping>
(Excuse all this the verbosity, but hopefully no-one will wonder
what
exactly
I did!)
When I use the following URL
http://iiserverip/CIMS2WebApplication/register
I
get a 404 from IIS (i.e. nothing at all is getting proxied to WL,not
even a wrong
url)
OK, I've finished! If someone would like to catch their breath andhelp
me out
I'd be extremely grateful! Thanks so much.
Terrance

Weblogic 6.1 cluster startup issue

We've recently experienced a horrendous morning with Weblogic 6.1 SP3. We were
restarting all of our servers (4 Servlet containers (clustered), 2 EJB containers
(clustered)), and found that after doing so, the web servers started dying off
one by one with a hotspot error message. The stack sometimes seemed to indicate
a failure in an weblogic 'internalLookup' method.
After a while, I noticed that one of the EJB servers was consuming 0 CPU. I suspected
that this EJB server had not properly started up, and bounced it. After I made
sure that i had started up properly, I then proceeded to restart all of the Web
servers, one by one. Since then everything has been fine.
When restarting the clustered servers, we noticed that it took an inordinate amount
of time compared to starting each one up individually... Is there a known problem
related to starting up multiple clustered servers simultaneously?
Thanks in Advance, Chad Stansbury

Forget about it. Turns out that the instability was due to someone inadvertently
modifying our startup scripts and limiting all our VMs to -mx64m. Not good.
Anyway, sorry for any time you may have wasted.
Chad
Rajesh Mirchandani <[email protected]> wrote:
Take multiple thread dumps of the servers in the cluster and post it
here. What happens if
you start one server after the other ?
Chad Stansbury wrote:
We've recently experienced a horrendous morning with Weblogic 6.1 SP3.We were
restarting all of our servers (4 Servlet containers (clustered), 2EJB containers
(clustered)), and found that after doing so, the web servers starteddying off
one by one with a hotspot error message. The stack sometimes seemedto indicate
a failure in an weblogic 'internalLookup' method.
After a while, I noticed that one of the EJB servers was consuming0 CPU. I suspected
that this EJB server had not properly started up, and bounced it. After I made
sure that i had started up properly, I then proceeded to restart allof the Web
servers, one by one. Since then everything has been fine.
When restarting the clustered servers, we noticed that it took an inordinateamount
of time compared to starting each one up individually... Is there aknown problem
related to starting up multiple clustered servers simultaneously?
Thanks in Advance, Chad Stansbury--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

IIS WLS6.1 SP3 and cluster load balancing

I am setting up an installation with IIS, WLS6.1 SP3 using a cluster. Monitoring
the instances in the cluster the entire load is going to one instance. If that
instance is stopped the other takes over, no problem. If I set DynamicServerList
to off in the iisproxy.ini file the load balances correctly.
Is there a way to ensure WLS sends the dynamic server list as advertised? Failing
that what are the problems that may arrise from not using the Dynamic Server List?

I would like to see the entries in your iisproxy.ini file?
Can you post 'em?
Kumar
Danny Newman wrote:
I am setting up an installation with IIS, WLS6.1 SP3 using a cluster. Monitoring
the instances in the cluster the entire load is going to one instance. If that
instance is stopped the other takes over, no problem. If I set DynamicServerList
to off in the iisproxy.ini file the load balances correctly.
Is there a way to ensure WLS sends the dynamic server list as advertised? Failing
that what are the problems that may arrise from not using the Dynamic Server List?

Problem with weblogic.deploy and cluster

          I'm having some problems with the weblogic.deploy class when trying to refresh
          a jsp file. Using the following command to redeploy the entire application works
          fine:
          java weblogic.deploy -port 9876 -host apptest01 update
          administrator portal c:\portal-site
          However using the following command to refresh just one jsp
          file:
          java weblogic.deploy -url t3://apptest01:9876 -username system
          -jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
          refresh administrator portal
          produces the following stack trace:
          javax.naming.NameNotFoundException: Unable to resolve
          weblogic.management.home.olbcluster.
          Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
          remaining name ''
          at weblogic.rmi.internal.BasicOutboundRequest.
          sendReceive(BasicOutboundRequest.java:85)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          invoke(ReplicaAwareRemoteRef.java:255)
          at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          invoke(ReplicaAwareRemoteRef.java:222)
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          at $Proxy0.lookup(Unknown Source)
          at weblogic.jndi.internal.WLContextImpl.
          lookup(WLContextImpl.java:323)
          at weblogic.management.tools.WebAppComponentRefreshTool.
          getMBeanHomeForManagedServer
          WebAppComponentRefreshTool.java:498)
          at weblogic.management.tools.
          WebAppComponentRefreshTool.
          getComponentMBeanForServer
          (WebAppComponentRefreshTool.java:225)
          at weblogic.management.tools.
          WebAppComponentRefreshTool.findInternalPaths
          (WebAppComponentRefreshTool.java:187)
          at weblogic.management.tools.WebAppComponentRefreshTool.
          refresh(WebAppComponentRefreshTool.java:151)
          at weblogic.deploy.refresh(deploy.java:704)
          at weblogic.deploy.runBody(deploy.java:374)
          at weblogic.utils.compiler.Tool.run(Tool.java:79)
          at weblogic.deploy.main(deploy.java:1601)
          Unable to resolve weblogic.management.home.olbcluster.
          Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
          Any ideas?


          "John Murphy" <[email protected]> wrote:
          >
          >I'm having some problems with the weblogic.deploy class when trying to
          >refresh
          >a jsp file. Using the following command to redeploy the entire application
          >works
          >fine:
          >
          >java weblogic.deploy -port 9876 -host apptest01 update
          >administrator portal c:\portal-site
          >
          >However using the following command to refresh just one jsp
          >file:
          >
          >java weblogic.deploy -url t3://apptest01:9876 -username system
          >-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
          >refresh administrator portal
          >
          >produces the following stack trace:
          >
          >javax.naming.NameNotFoundException: Unable to resolve
          >weblogic.management.home.olbcluster.
          >Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
          >remaining name ''
          > at weblogic.rmi.internal.BasicOutboundRequest.
          > sendReceive(BasicOutboundRequest.java:85)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          > invoke(ReplicaAwareRemoteRef.java:255)
          > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
          > invoke(ReplicaAwareRemoteRef.java:222)
          > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
          > at $Proxy0.lookup(Unknown Source)
          > at weblogic.jndi.internal.WLContextImpl.
          > lookup(WLContextImpl.java:323)
          > at weblogic.management.tools.WebAppComponentRefreshTool.
          > getMBeanHomeForManagedServer
          > WebAppComponentRefreshTool.java:498)
          > at weblogic.management.tools.
          > WebAppComponentRefreshTool.
          > getComponentMBeanForServer
          > (WebAppComponentRefreshTool.java:225)
          > at weblogic.management.tools.
          > WebAppComponentRefreshTool.findInternalPaths
          > (WebAppComponentRefreshTool.java:187)
          > at weblogic.management.tools.WebAppComponentRefreshTool.
          > refresh(WebAppComponentRefreshTool.java:151)
          > at weblogic.deploy.refresh(deploy.java:704)
          > at weblogic.deploy.runBody(deploy.java:374)
          > at weblogic.utils.compiler.Tool.run(Tool.java:79)
          > at weblogic.deploy.main(deploy.java:1601)
          >Unable to resolve weblogic.management.home.olbcluster.
          >Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
          >
          >Any ideas?
          >
          Hi John,
          How's tricks?
          It looks to me as though the olbcluster JNDI reference isn't being resolved from
          the tree. A similar error results when a Connection Pool cannot be resolved, the
          JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
          it often turns out to be an error in the correlation between the deployment descriptors,
          settings applied via the console and references made in the code.
          That's my tuppence worth,
          James :-)

IIS to weblogic 6.0 cluster

Similar Messages

Maybe you are looking for