Clustering Problem on WLS 5.1 sp 2/3

I've set up a multihomed machine running four instances of WLS 5.1 sp2 on
          solaris 7. When I initially added them to a cluster and tested them for
          serving JSPs everything seemed fine. I've since tried deploying an EJB
          (which works in a non clustered server) and I'm suddenly getting the
          following errors:
          stdout:
          ... <E> <MutlicastSocket> Multicast socket receive error:
          java.lang.runtimeException: I/O error opening JAR file from
          file:/export/home0/weblogic/cluster1/serverclasses
          stderr:
          java.util.zip.ZipException: error in opening zip file
          at java.util.zip.ZipFile.open(Native Method)
          at java.util.zip.ZipFile.open(Compiled Code)
          at java.util.zip.ZipFile.<init>(Compiled Code)
          at java.util.zip.ZipFile.<init>(Compiled Code)
          at
          weblogic.boot.ServerClassLoader.deploy(ServerClassLoader.java:141)
          at
          weblogic.cluster.AnnotatedServiceOffer.expandClassPath(AnnotatedServiceOffer
          .java:74)
          at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
          iled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
          Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readArrayList(Compiled
          Code)
          at weblogic.cluster.Announcement.readObject(Announcement.java:73)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
          iled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
          Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled Code)
          at
          weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled Code)
          at weblogic.cluster.TMSocket.execute(Compiled Code)
          at weblogic.kernel.ExecuteThread.run(Compiled Code)
          (My EJB is deployed it its expanded directory form, which worked in a single
          server, this error happens repeatedly, regardless of accessing the EJB. The
          weblogic log says that the EJB deployed successfully)
          I've also tried upgrading to sp3, now it cannot even serve jsps, I get the
          following error:
          Wed Jun 14 10:36:06 GMT+01:00 2000:<I> <ServletContext-General> file: init
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: init
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          verbose initialized to: true
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          packagePrefix initialized to: jsp_servlet
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          compileCommand initialized to: /usr/java1.2/bin/javac
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          srcCompiler initialized to weblogic.jspc
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          superclass initialized to null
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp: param
          pageCheckSeconds initialized to: 1
          Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          initialization complete
          Wed Jun 14 10:36:24 GMT+01:00 2000:<E> <ServletContext-General> Servlet
          failed with Exception
          java.lang.NullPointerException
          at
          weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
          eplicatedSession.java:339)
          at
          weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
          onContext.java:322)
          at
          weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
          l.java:1104)
          at
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          ava:1007)
          at
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          ava:981)
          at
          weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
          at
          weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
          at
          weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
          at jsp_servlet.simpleSession._jspService(simpleSession.java:64)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :123)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :141)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:744)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:692)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager.java:251)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          at weblogic.kernel.ExecuteThread.run(Compiled Code)
          Thanks in advance, tell me if you need more info
          Loz (ECsoft/MyNet)
          

I got that working. Never mind.
          Amit Bhutra <[email protected]> wrote in message
          news:[email protected]...
          > I am getting same error. How did you resolved it?
          > Weblogic creates a jar file in mycluster/tmp_deployment directory.
          >
          > Do i need to include this jar file in my weblogic.properties?
          >
          > Loz <[email protected]> wrote in message
          > news:[email protected]...
          > > OK, I got rid of the EJB problem by deploying as a jar, how about the
          sp3
          > > problem?
          > >
          > > Loz
          > >
          > > "Loz" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > I've set up a multihomed machine running four instances of WLS 5.1 sp2
          > on
          > > > solaris 7. When I initially added them to a cluster and tested them
          for
          > > > serving JSPs everything seemed fine. I've since tried deploying an EJB
          > > > (which works in a non clustered server) and I'm suddenly getting the
          > > > following errors:
          > > >
          > > > stdout:
          > > > ... <E> <MutlicastSocket> Multicast socket receive error:
          > > > java.lang.runtimeException: I/O error opening JAR file from
          > > > file:/export/home0/weblogic/cluster1/serverclasses
          > > >
          > > > stderr:
          > > > java.util.zip.ZipException: error in opening zip file
          > > > at java.util.zip.ZipFile.open(Native Method)
          > > > at java.util.zip.ZipFile.open(Compiled Code)
          > > > at java.util.zip.ZipFile.<init>(Compiled Code)
          > > > at java.util.zip.ZipFile.<init>(Compiled Code)
          > > > at
          > > > weblogic.boot.ServerClassLoader.deploy(ServerClassLoader.java:141)
          > > > at
          > > >
          > >
          >
          weblogic.cluster.AnnotatedServiceOffer.expandClassPath(AnnotatedServiceOffer
          > > > .java:74)
          > > > at weblogic.cluster.AnnotatedServiceOffer.readObject(Compiled
          > > Code)
          > > > at
          > > >
          > >
          >
          weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
          > > > iled Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled
          > > Code)
          > > > at
          > > >
          weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
          > > > Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
          > Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled
          > > Code)
          > > > at
          > > >
          weblogic.common.internal.WLObjectInputStreamBase.readArrayList(Compiled
          > > > Code)
          > > > at
          > weblogic.cluster.Announcement.readObject(Announcement.java:73)
          > > > at
          > > >
          > >
          >
          weblogic.common.internal.WLObjectInputStreamBase.readPublicSerializable(Comp
          > > > iled Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readLeftover(Compiled
          > > Code)
          > > > at
          > > >
          weblogic.common.internal.WLObjectInputStreamBase.readObjectBody(Compiled
          > > > Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readObject(Compiled
          > Code)
          > > > at
          > > > weblogic.common.internal.WLObjectInputStreamBase.readObjectWL(Compiled
          > > Code)
          > > > at weblogic.cluster.TMSocket.execute(Compiled Code)
          > > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          > > >
          > > > (My EJB is deployed it its expanded directory form, which worked in a
          > > single
          > > > server, this error happens repeatedly, regardless of accessing the
          EJB.
          > > The
          > > > weblogic log says that the EJB deployed successfully)
          > > >
          > > > I've also tried upgrading to sp3, now it cannot even serve jsps, I get
          > the
          > > > following error:
          > > >
          > > > Wed Jun 14 10:36:06 GMT+01:00 2000:<I> <ServletContext-General> file:
          > init
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > init
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > verbose initialized to: true
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > packagePrefix initialized to: jsp_servlet
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > compileCommand initialized to: /usr/java1.2/bin/javac
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > srcCompiler initialized to weblogic.jspc
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > superclass initialized to null
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > workingDir initialized to: /export/home0/weblogic/cluster1/classfiles
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > param
          > > > pageCheckSeconds initialized to: 1
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<I> <ServletContext-General> *.jsp:
          > > > initialization complete
          > > > Wed Jun 14 10:36:24 GMT+01:00 2000:<E> <ServletContext-General>
          Servlet
          > > > failed with Exception
          > > > java.lang.NullPointerException
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
          > > > eplicatedSession.java:339)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
          > > > onContext.java:322)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
          > > > l.java:1104)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          > > > ava:1007)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          > > > ava:981)
          > > > at
          > > >
          weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
          > > > at
          > > > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
          > > > at
          > > >
          > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
          > > > at
          jsp_servlet.simpleSession._jspService(simpleSession.java:64)
          > > > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > > > :123)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > > > :141)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > > l.java:744)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > > > l.java:692)
          > > > at
          > > >
          > >
          >
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          > > > Manager.java:251)
          > > > at
          > > >
          > >
          >
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          > > > at
          > > > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          > > > at weblogic.kernel.ExecuteThread.run(Compiled Code)
          > > >
          > > > Thanks in advance, tell me if you need more info
          > > >
          > > > Loz (ECsoft/MyNet)
          > > >
          > > >
          > >
          > >
          >
          >
          

Similar Messages

  • Clustering Problems with WLS 4.5.1

    Hi!
              I'm trying to configure a WebLogic 4.5.1 cluster (named "cluster1", on two
              WinNT4 SP5 servers (instances WLS "server A" and "server B")
              When I start each WLS instance in each server, both create a cluster where I
              can only find one WLS server, not two! So I have on each NT server, one
              cluster which contain one WLS server!!!
              To see that, I use the WLS console on the 2 servers, and I see that in each
              server, there is a cluster "cluster1" and only one server ("server A" in the
              first NT Server, and "server B" in the second one).
              The two server are identical, same OS, same SP, same WLS version, same WLS
              Service Pack, same IP Multicast address, same TCP port (7001), and there is
              no multihoming.
              I can't see how to put the two WLS servers in the same cluster!
              Do someone have a clue?
              Best regards,
              Jean-Michel Gautreau
              [email protected]
              

    Here is a console screendump, taken after the two WLS servers' boot.
              I forgot to tell we have installed WLBS on both NT servers, before
              installing WebLogic 4.5.1. Is there a problem in the communication between
              the two servers? I'm not sure but I feel it is a network problem, the two NT
              servers don't seem to communicate correctly through WLBS with the WLS
              cluster?
              Any hint?
              [dump.bmp]
              

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • Apache-soap Problem with WLS 5.1sp9

    I have problem with WLS 5.1sp9.
    My environment is the following :
    jaf-1.0.1
    javamail-1.2
    soap-2.2
    xerces-1.4.4
    and I want to call EJB.
    So, I write some EJB and deploy it.
    And rpcrouter work!!
    Success to deploy the Service.
    But I run into problem with calling this ejb.
    This error is the following.
    SOAP-ENV:Server.BadTargetObjectURI
    Unable to resolve target object: BC2_BoardSync
    please, help me.
    here's my example..
    ps.
    sorry for my poor English..T_T
    [ws5.10.zip]
    [vb.zip]

    I have problem with WLS 5.1sp9.
    My environment is the following :
    jaf-1.0.1
    javamail-1.2
    soap-2.2
    xerces-1.4.4
    and I want to call EJB.
    So, I write some EJB and deploy it.
    And rpcrouter work!!
    Success to deploy the Service.
    But I run into problem with calling this ejb.
    This error is the following.
    SOAP-ENV:Server.BadTargetObjectURI
    Unable to resolve target object: BC2_BoardSync
    please, help me.
    here's my example..
    ps.
    sorry for my poor English..T_T
    [ws5.10.zip]
    [vb.zip]

  • Clustering problem WLS 5.1

    Hi,
    we have an environment with 2 clusters ( 1 JSP & 1 EJB)
    both cluster consist each of 2 nodes, where 1 JSP and 1 EJB are running on a machine.
    although both clusters seem to act correctly at runtime ( and are also visible
    in the console as clusters), we get an exception at startup - only at th JSP tier
    which is rather confusing:
    Do Aug 08 06:11:15 CEST 2002:<E> <WebLogicServer> Unable to bind cluster MO as
    "WebLogic" into JNDI tree
    javax.naming.NameAlreadyBoundException; remaining name 'weblogic.cluster.WebLogic'
    at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
    at weblogic.jndi.toolkit.BasicWLContext_WLStub.bind(BasicWLContext_WLStub.java:1261)
    at weblogic.jndi.toolkit.WLContextStub.bind(WLContextStub.java:484)
    at weblogic.cluster.ClusterMain.start(ClusterMain.java:290)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1447)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:869)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Server.java:97)
    at weblogic.Server.main(Server.java:58)
    None of our clusters is named MO !
    Does anybody have a clue ?!

    Hi,
    we have an environment with 2 clusters ( 1 JSP & 1 EJB)
    both cluster consist each of 2 nodes, where 1 JSP and 1 EJB are running on a machine.
    although both clusters seem to act correctly at runtime ( and are also visible
    in the console as clusters), we get an exception at startup - only at th JSP tier
    which is rather confusing:
    Do Aug 08 06:11:15 CEST 2002:<E> <WebLogicServer> Unable to bind cluster MO as
    "WebLogic" into JNDI tree
    javax.naming.NameAlreadyBoundException; remaining name 'weblogic.cluster.WebLogic'
    at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
    at weblogic.jndi.toolkit.BasicWLContext_WLStub.bind(BasicWLContext_WLStub.java:1261)
    at weblogic.jndi.toolkit.WLContextStub.bind(WLContextStub.java:484)
    at weblogic.cluster.ClusterMain.start(ClusterMain.java:290)
    at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1447)
    at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:869)
    at java.lang.reflect.Method.invoke(Native Method)
    at weblogic.Server.startServerDynamically(Server.java:140)
    at weblogic.Server.main(Server.java:97)
    at weblogic.Server.main(Server.java:58)
    None of our clusters is named MO !
    Does anybody have a clue ?!

  • WLS 5.1 SP8 Clustering problems

    Hi all,
              I am trying to create a cluster with 2 instances of WLS and third WLS
              instance to be used as a proxy. The two servers in the cluster have joined
              the Multicast Address correctly (I hope, because thats what the log file
              says). Now the proxy also started succesfully. But when I make a request
              for a JSP page, it is going into an infinite loop. The request is not going
              beyond the proxy i think, because, on the proxy, it says *.jsp:init.
              Then i tried to use ISAPI plug-in to call this JSP, but i am getting an
              ISAPI error (I don't know why it is looking for localhost:7001 when I have
              specified
              WebLogicCluster=192.200.1.251:7001,192.200.1.252:7001,192.200.1.253:7001
              in the iisproxy.ini File:
              Internal Server Error
              Reason:Cannot connect to WebLogic: timed out after 10 seconds. Cluster list:
              localhost:7001
              Line 427 of iisproxy.cpp
              Can Some one help ?
              Thank You in advance.
              Ramesh
              

    Seems ISAPI plugin could not locate iisproxy.ini.
              Here is the search order:
              - current directory (same as the dll)
              - WebLogic installation directory (finds it from the regirstry) -
              c:\weblogic
              Try to save iisproxy.ini at the same location of the dll.
              "ramesh" <[email protected]> wrote in message
              news:[email protected]...
              > Hi all,
              >
              > I am trying to create a cluster with 2 instances of WLS and third WLS
              > instance to be used as a proxy. The two servers in the cluster have
              joined
              > the Multicast Address correctly (I hope, because thats what the log file
              > says). Now the proxy also started succesfully. But when I make a request
              > for a JSP page, it is going into an infinite loop. The request is not
              going
              > beyond the proxy i think, because, on the proxy, it says *.jsp:init.
              >
              > Then i tried to use ISAPI plug-in to call this JSP, but i am getting an
              > ISAPI error (I don't know why it is looking for localhost:7001 when I have
              > specified
              > WebLogicCluster=192.200.1.251:7001,192.200.1.252:7001,192.200.1.253:7001
              > in the iisproxy.ini File:
              >
              > Internal Server Error
              > Reason:Cannot connect to WebLogic: timed out after 10 seconds. Cluster
              list:
              > localhost:7001
              > Line 427 of iisproxy.cpp
              >
              > Can Some one help ?
              >
              > Thank You in advance.
              >
              > Ramesh
              >
              >
              >
              

  • Problems with WLS 4.5.1 and F5 Big IP HA+ Switch

    Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
              4.5.1 servers (two in the pool currently). At seemly random intervals the
              Big IP believes the one or both of the servers are not responding, so they
              are removed from the pool. We have a growing body of anecdotal evidence to
              suggest that the servers are actually on-line and available during the
              event. Either the switch is confused or the WLS servers aren't always
              responding correctly to the HTTP requests sent by the switch for polling.
              We're having problems catching the problem with the right diagnostics.
              Has anyone out there observed similar behavior with these components?
              Thanks.
              - Sean McRae
              

    Sort of,
              I use iplanet between the 2, so I havent had this problem, but I have had
              several problems with clustering, here is what I recomend doing:
              write a simple java program (or whatever your prefered language) to do a HTTP
              ping on your distinct weblogic servers every X seconds/minutes where X is less
              than Big IPs death tolerance. Time how long/or if ever each of your pings take.
              turn on verbose gc.
              My guess is its one of 3 things:
              1.) your have a big gc going on and your server isnt responding quick enough
              and big ip is marking it dead
              2.) you have thread contention that is causing your server not to respond quick
              enough
              3.) your network has some issues and the packets arent making it there, or not
              quick enough.
              the ping program will prove/disprove #2 and lead you to or away from 3. Verbose
              gc will prove/disprove #1.
              hope this helps
              -Joel
              Sean wrote:
              > Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
              > 4.5.1 servers (two in the pool currently). At seemly random intervals the
              > Big IP believes the one or both of the servers are not responding, so they
              > are removed from the pool. We have a growing body of anecdotal evidence to
              > suggest that the servers are actually on-line and available during the
              > event. Either the switch is confused or the WLS servers aren't always
              > responding correctly to the HTTP requests sent by the switch for polling.
              > We're having problems catching the problem with the right diagnostics.
              >
              > Has anyone out there observed similar behavior with these components?
              >
              > Thanks.
              >
              > - Sean McRae
              

  • Communication between Clusters Problem

    Hi all
              1. Is it possible for a bean, being hosted in a cluster to call a bean which is hosted in another cluster?
              We have a problem with the role information, which gets wrong at every second call.
              We have the following setup:
              - A cluster called "web-cluster" consists of two machines with one weblogic 9.2 server per machine.
              - We have another cluster called "ID-Cluster" with the same setup (2 Machines, 2 WLS).
              - In the "Web-Cluster" we have a bean deployed called "SecurityProxy".
              - In the "Web-Cluster" we have a Web-Application ("WebApp") deployed which use the "SecurityProxy"
              - In the ID-Cluster we have a Bean called "SecurityBean". - The SecurityProxy makes a login to the ID-Cluster with a technical user, role "techSecurityProxy".
              - Calls from SecurityProxy to SecurityBean alternate with each call.
              Problem:
              User logs in to the "WebApp" and gets role "customer" associated.
              First call from SecurityProxy to SecurityBean: call is done with the correct role "techSecurityProxy" second call is done with the role "customer" !?! It seams as if the security context gets propageted...
              We have no trust defined between the clusters and we have no runas configured in den deployment descriptors. Can anyone help?

    <p>Frank, the security context is propagted between the JVM's. I have asked BEA support to specify if this can be configured or turned off to resolve another issue I have but to date I have not had a response.</p>
              <p>In your case can you not add the new principle like -useProxy to authenticated users which allows them to use the proxy once they are authenticated?</p>
              <p>
              Hussein Badakhchani
              London Middleware
              </p>

  • Problems starting WLS 7 server ... checkLicense NullPointerException

    Hi there,
    We have a clustered environment running WebLogic Server 7.0 Service Pack 4. In our cluster we're running two WLS instances essentially as webservers, to serve up static content.
    Starting and stopping the WLS instances is done using scripts written by a group of now-departed developers (we are not using NodeManager).
    The problem that we're having is that the "webserver" instances are very difficult to start up, and may require seven or eight attempts to start properly. Most of the time, we see the following NullPointerException in the server log:
    ====================================================
    <9-Nov-04 12:36:30 EST PM> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
    <9-Nov-04 12:36:30 EST PM> <Emergency> <WebLogicServer> <000209> <ListenThread.run() failed: java.lang.NullPointerException
    java.lang.NullPointerException
         at weblogic.t3.srvr.ListenThread.checkLicense(ListenThread.java:595)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:333)
    >
    <9-Nov-04 12:36:30 EST PM> <Emergency> <WebLogicServer> <000210> <The WebLogic Server is no longer listening for connections. You should probably restart it.>
    ====================================================
    If WebLogic was having a hard time finding the license.bea file, I would expect that something more user-friendly than a NullPointerException would occur. Also, a simple problem with locating the license file doesn't really explain why the server eventually does come up properly, despite the fact that it can sometimes take many attempts.
    Unfortunately, since these servers are running in production we don't have the luxury to start and stop them at will to perform testing.
    Does anyone have any hints as to what might be causing this issue? Any advice would be much appreciated.
    Regards,
    jodym

    I'm guess you changed owner of config/mydomain to weblogic? To
    confirm - try touching/create a test file in config/mydomain,
    i.e. touch mytest.perm;ls -l mytest.perm;rm mytest.perm
    You could start weblogic with truss:
    truss -t open -o /tmp/truss.out -f "your start command"
    Then examine /tmp/truss.out
    "Dariusz" <[email protected]> wrote in message news:<3d08b130$[email protected]>...
    I have installed WLS in the sun solaris machine and have problems starting up a mydomain
    test server. I am getting:
    weblogic.management.configuration.ConfigurationException: - with nested exception:
    [weblogic.security.internal.FileUtilsException: couldn't create temporary file for
    SerializedSystemIni.dat, .new, /config/mydomain - with nested exception:
    [java.io.IOException: No such file or directory]]
    I am suspecting the problem might be that we have installed it as root and then change
    the rights to weblogic. Any pointers are greatly appreciated.
    Thanks.

  • JMS Messaging Bridge Problems with WLS 8.1 sp2

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

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

  • JDBC Type 3 driver problem with WLS 6.1 SP4

    We have Oracle 8.1.7.4 client running on WebLogic 6.1 SP4 on Solaris 2.6 connecting to Oracle OPS 8.1.7 running on Solaris 2.6. We are getting core dumps while running stress testing using Load Runner for 100 concurrent users. The performance is very good for a while in the beginning of the test and all of a sudden we see requests for connections queueing up on the WLS and the server crashes. Please send us details of any previous instances any one faced similar problem and the fix applied will be very helpful.
    Regards,
    Raj

    The Member Feedback forum is for suggestions and feedback for OTN Developer Services. This forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. We recommend that you post this thread to the SQLJ/JDBC forum.
    The URL is: http://forums.oracle.com/forums/forum.jsp?forum=99
    Thanks, OTN Team

  • Spring 2.5.5 and EJB 3.0 Deployment problem in WLS 10.3

    Hi,
    I am attempting to deploy a EAR file that previously ran on SJSAS 9.1 update 1 to WLS 10.3. As part of the deployment I get the following error related to the EJB3 classes.
    There are 1 nested errors: weblogic.j2ee.dd.xml.AnnotationProcessException: [EJB:015002]Unable to load class au.edu.cqu.cis.web.ajaxservice.AjaxServicesBean in Jar D:\dev\env\oracle\middleware\jdeveloper\system\system11.1.1.0.31.51.56\DefaultDomain\servers\DefaultServer\tmp\_WL_user\ProgEnrol-ear-3\v540rk\ProgEnrol-ejb-3.0.4-SNAPSHOT.jar : java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
    I suspect that this is related to the @Autowired spring annotation in use in the session bean. Either, the server is not finding the Spring JAR correctly or it has a problem with the annotation.
    Can anyone point me in the right direction? Do I need to deploy the spring jar as a library?
    Thank you.
    Regards,
    Graeme.

    Hi, Graeme.
    Seems there is an existing CR on something related from v10.0: CR353213
    * WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
    According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
    Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
    I hope this helps,
    -Adrian

  • Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

    Hi all,
    I'm posting this just to document a problem I had when converting an Enterprise Application from WLS 10.3.0 across to WLS 10.3.2 environment.
    Upon deployment of the application I was getting this error:
    Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.ApplicationParamBeanImpl@b720894d(/ApplicationParams[webapp.encoding.default])"
         at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:227)
         at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setApplicationParams(WeblogicApplicationBeanImpl.java:560)
         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 com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
         at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:536)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
         at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
         at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
         at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
         at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
         at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
         at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
         at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
         at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:329)
         at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
         at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
         at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
         at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
         at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
         at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
         at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
         at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
         at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
         at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
         at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
         at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    It turns out this was an issue with the META-INF/weblogic-application.xml having duplicate entries for the "webapp.encoding.default" parameter.
    This obviously got duplicated when my app was re-imported into the Eclipse OPEP environment for WLS 10.3.2
    <?xml version="1.0" encoding="UTF-8"?>
    <wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd">
    <!-- server-version: 10.3 -->
    <!--weblogic-version:10.3.2-->
    <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
    </wls:application-param>
    <wls:application-param>
    <wls:param-name>webapp.encoding.default</wls:param-name>
    <wls:param-value>UTF-8</wls:param-value>
    </wls:application-param>
    </wls:weblogic-application>
    Removing the duplicate entry resolved this problem.
    I hope this helps anyone else that experiences this issue.
    Regards,
    Paul

    Below link might be helpful.
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
    Regards,
    Anandraj
    http://weblogic-wonders.com/

  • Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

    We are using simplified chinese, after swith to bea jdriver, it messed up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince except webservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error. Is
    there a way to turn off isolation level in workshop? I tried manually edit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

    I did try to change the value in this config file as well, but did not help.
    In fact, the installation default setting is with
    '<transaction-isolation-level>' commented out.
    And when I use bea oracle jdriver, it somehow messed up with database
    character set encoding, so our Chinese characters could not be retrieved
    correctly. And I try to set the encoding of jdriver to 'GBK', it did not
    work.
    "Anurag Pareek" <[email protected]> дÈëÏûÏ¢ÐÂÎÅ
    :[email protected]..
    Hello Ma,
    The transaction isolation level value for EJBs backing the JWS files is
    specified in the <transaction-isolation-level> tag in the
    WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
    manipulate this value to serve your purpose.
    Please do let me know how it goes.
    Regards,
    Anurag
    Workshop Support
    "Ma Jie" <[email protected]> wrote in message
    news:[email protected]..
    We are using simplified chinese, after swith to bea jdriver, it messed
    up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince exceptwebservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error.Is
    there a way to turn off isolation level in workshop? I tried manuallyedit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

  • Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

    We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
              node servers. Two nodes have been clustered. We are at the point where we
              need to configure JMS. Has any one implemented JMS in WLS 7 clustered
              environment? What are the things to watch out when clustering JMS? Can JMS
              topics and queues be clustered?
              TIA for any helpful hints and comments.
              Regards
              

    "Karim Ali" <[email protected]> wrote:
              >> Has any one implemented JMS in WLS 7 clustered
              >> environment?
              I'm currently working on a project with WLS 7 here at work, involving
              the implementation of BEA's JMS Cluster. So far, I really haven't had
              many hiccups.
              "Karim Ali" <[email protected]> wrote:
              >> What are the things to watch out when clustering JMS?
              At least in WLS 7, the biggest thing that stands out is the lack of
              automatic failover. Also, Message Paging -- make sure you configure
              paging high/low thresholds. Or, if you don't wish for it to occur but
              can't stop the server (very common these days with SLAs), set that
              byte/message high threshold to a very large number (correct me if I'm
              wrong, but I believe BEA recommends 2^63 -1).
              "Karim Ali" <[email protected]> wrote:
              >> Can JMS topics and queues be clustered?
              Well, since Topics and Queues are extensions of the
              javax.jms.Destination interface, the answer is: Yes!
              (SIDE NOTE: most people usually refer to them as a [JMS] "destination"
              -- it avoids a lot of conceptual baggage and plus, less typing!)
              You'll probably want to see this section of BEA's e-docs:
              http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
              later,
              Brian J. Mitchell
              BEA Systems Administrator
              TRX
              Atlanta, GA
              email: [email protected]
              office: 404-327-7238
              mobile: 678-283-6530
              

Maybe you are looking for

  • How much ram is supported on my late 2011 Macbook pro?

    8 GB or 16 GB? and if 16 GB can OSX Lion take advantage of all of the ram?

  • MacBook Pro scratching and destroying DVD's

    I thought it was originally a faulty DVD but after the second time I knew something was up. The DVD kept ejecting and refusing to play on my MacBook so I decided to play it on a DVD player and the disc does not exist. This is the second time the disc

  • OBIEE11g  Presentation services down

    Hi Experts, I have installed OBIEE 11g(11.1.1.6) on my Laptop ( Windows-7 64 Bit).. All the components are up & running except the "coreapplication_obips1".. Error messages are as follows: when I am trying to access http://XXXXXX:7001/analytics/ gett

  • I am sick of the bad customer service

    I called to set up new service.  I had to use my grandson's phone (personal cell phone) who happens to work for AT&T, and these people refused to help me.  He was in the other rooom doing school work while I was on the phone with the company to try a

  • How do i get boyond terms and conditions loop I am currently trapped in

    I had to do a restore as part of ios7 download and am now trapped in the terms and condition page. No matter how often I 'agree' I cannot exit this page