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

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
              >
              

  • 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.
              

  • 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

  • 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

  • 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 :-)
              

  • Weblogic admin server cluster

    Hi,
    I'm setting up WebLogic cluster (horizontal with 2 managed servers spanning across 2 machines).I would want to have admin server on each machine and only one admin server will be active whiel the second admin server will remain shutdown
    .Can anyone please explain how I can set this up with 2 adminsitration servers and how do I make it active-passive mode for admin server and how i can bring it up in case of 1st admin server going down
    Any documents would be really helpful
    thanks

    There can be only 1 Admin per WebLogic Domain....not more than one.
    Please refer to Know more about *"What is Administration Server?"* http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
    If you are talking about *" Whole Server Migration "* then please refer to: http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/migration.html
    Note:      Server migration is only supported when you use the SSH version of Node Manager. Server migration is not supported on Windows.
    When a migratable server becomes unavailable for any reason, for example, if it hangs, loses network connectivity, or its host machine fails—migration is automatic. Upon failure, a migratable server is automatically restarted on the same machine if possible. If the migratable server cannot be restarted on the machine where it failed, it is migrated to another machine. In addition, an administrator can manually initiate migration of a server instance.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Failed to replicate non-serializable object  Weblogic 10 3 Cluster environ

    Hi,
    We have problem in cluster environment, its showing all the objects in Session needs to be serialized, is there any tool to find what objects in session needs to be serialized or any way to find. There was no issue in WLS 8 when the application again setup in WLS 10, we are facing the session replication problem.
    The setup is there are two managed server instance in cluster, they are set to mulicast(and also tried with unicast).
    stacktrace:
    ####<Jun 30, 2010 7:11:16 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939476284> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    ####<Jun 30, 2010 7:11:19 PM EDT> <Error> <Cluster> <userbser01> <rs002> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1277939479750> <BEA-000126> <All session objects should be serializable to replicate. Check the objects in your session. Failed to replicate non-serializable object.>
    Thanks,

    Hi
    Irrespective of WLS 8.x or WLS 9.x, 10.x, in general any objects that needs to be synced/replicated across the servers in cluster should be Serializable (or implement serializable). The object should be able to marshall and unmarshall. Simple reason why it did not showed in WLS 8.x is may be in that version they could not show these details like Error. May be they showed as Info or Warn or Just Ignored it. Weblogic Server became more and more stable and more efficient down the lines like from its oldest version 4.x, 5.x, 6.x, 7.x to latest 10.x. So my guess is they added more logic and more functionality to capture all possible errors and scenarios. I did worked on WLS 8.1 SP4 to SP6 long time back. Could not remember if I saw or did not see these errors for cluster domain with non-serializabe objects. I vaguley remember seeing it for Portal Domains but not sure. I do not have 8.x installed, otherwise I would have given a quick shot and confirm it.
    So even though it did not showed up in WLS 8.x, still underneath rule is any object that needs to be replicated that is getting replicated in cluster needs to implement Serializable interface.
    Thanks
    Ravi Jegga

  • Weblogic 7.0 Cluster crashed

              Hi,
              I configured one Weblogic 7 Admin server with two clustered managed servers.And
              I could start
              clustering service sucessfully.It was working fine and cluster service was healthy.Then
              I ran the weblogic IPMulticast utility (while cluster serivice was running) then
              Weblogic
              admin server console showed a exception stack trace.After that I cannot restart
              any of the servers even after deleting all existing domains and creating brand
              new domains using configuration wizard.It is giving me nullpointer exceptions
              and configuration exceptions when I run startWeblogic script.
              Do I need to reinstall WebLogic.
              Please help me to solve this problem.
              Gayan Balasooriya.
              

    Multicast test should be only conducted when the servers in the cluster are
              down.
              Cameron Purdy wrote:
              > Did you stop all servers and the test before trying to restart?
              >
              > Peace,
              >
              > Cameron Purdy
              > Tangosol, Inc.
              > http://www.tangosol.com/coherence.jsp
              > Tangosol Coherence: Clustered Replicated Cache for Weblogic
              >
              > "Gayan Balasooriya" <[email protected]> wrote in message
              > news:[email protected]...
              > >
              > > Hi,
              > > I configured one Weblogic 7 Admin server with two clustered managed
              > servers.And
              > > I could start
              > > clustering service sucessfully.It was working fine and cluster service was
              > healthy.Then
              > > I ran the weblogic IPMulticast utility (while cluster serivice was
              > running) then
              > > Weblogic
              > > admin server console showed a exception stack trace.After that I cannot
              > restart
              > > any of the servers even after deleting all existing domains and creating
              > brand
              > > new domains using configuration wizard.It is giving me nullpointer
              > exceptions
              > > and configuration exceptions when I run startWeblogic script.
              > > Do I need to reinstall WebLogic.
              > >
              > > Please help me to solve this problem.
              > >
              > >
              > > Gayan Balasooriya.
              > >
              > >
              Rajesh Mirchandani
              Developer Relations Engineer
              BEA Support
              

  • IP Multicast requirements in WebLogic 5.1 cluster

              Hi,
              Does multicast need to be available to servers containing the Weblogic plug-in?
              We have a firewall between web servers (iPlanet) and the WebLogic cluster.
              Thanks in advance,
              Julian
              

              Another way of putting my question:
              How does the plug-in become aware of the need to failover (eg. to a replica session)?:
              (i) - "A Proactive method" -Plug-ins listen to cluster heartbeats to determine
              instance availability, only send requests to available instance (e.g. compare
              list of available instances from heartbeat results against primary/secondary instances
              specified in cookie).
              (ii) - "A reactive method" - Plug-in sends client request to Primary instance
              specified in cookie, request is not fulfilled, so intercepts response to client
              and re-sends request to secondary instance.
              (iii) other ??
              Please help.
              Thanks again - Julian
              "Julian Herzel" <[email protected]> wrote:
              >
              >Hi,
              >
              >Does multicast need to be available to servers containing the Weblogic
              >plug-in?
              >We have a firewall between web servers (iPlanet) and the WebLogic cluster.
              >
              >Thanks in advance,
              >
              >Julian
              

Maybe you are looking for