WebLogic 12.1: PDT vs. RDT in clusters
Hi,
we are using a dynamic cluster with a clustered JMS server configured.
Because a clustered JMS server only accepts Partitioned Distributed Topics (PDT) we are forced to use them.
This works fine. Except for one atypical use case:
There we have one MDB deployed serveral times as a part of different Ear files.
And we want to have each instance of the MDBs served with the messages.
But the messages coming from a PDT are only forwarded to one of these MDBs, regardless how we configure it.
I understand that for PDTs it is intended to have such behaviour.
To use a Replicated Distributed Topic (RDT) would help us here, since it behaves exactly like this.
But there is again a drawback, that RDTs just can not be deployed to clustered JMS servers as part of a dynamic cluster.
1. Are we really forced to go back from a dynamic cluster to a manual configured one, just to be able to use RDT like
behaviour of topics?
2. Or is there somehow a 'secret' configuration possible, that would make PDTs behave like RDTs?
I already tried all kinds of settings for topicMessagesDistributionMode for the MDB.
But unfortunatley 'compatibility' mode is not applicable here as it is for RDTs.
Thanks,
Mark
Hi Mark
Dynamic clusters help a lot in the JMS administration, but they have these limitations.
As per the description, the configuration you are trying to achieve needs to have static cluster
References:
10 Configuring and Deploying MDBs Using JMS Topics (12c (12.1.3))
A Topic Deployment Scenarios (12c (12.1.3))
Best Regards
Luz
Similar Messages
-
WebLogic 10.3.4 Adminserver Performance Issues - Clustered Environment.
I am running WL 10.3.4 64 bit version on 64 bit hardware (blade serves) running Solaris 10 and I have the servers setup in a cluster. There are 3 machines are part of the cluster.
Managed Server1 is on Blade Server 1
Managed Server2 is on Blade Server 2
Managed Server3 is on Blade Server 3
We have about 20 different clusters setup and 60 servers across those 20 clusters.
The adminserver runs on a separate box (not a blade server). Tasks that do NOT involve the servers or deployments tabs are relatively fast however, when I go to the servers or deployments tab, and to some extent the clusters tab, the response is very slow.
For example, I am running WL 10.3.0 on less robust hardware. I installed the patch that Oracle published to resolve this particular issue. We have a similar number of clusters and servers on in that environment (3 severs to a cluster). The servers tab responds in 10 seconds.
In WL 10.3.4, the servers and deployments tabs take about 45 - 60 seconds to respond. This adds a LOT of overhead to doing any server or deployment related tasks.
I realize that the admin server has to query all the managed servers but performance in 10.3.4 is much worse than WL 10.3.0 with the performance patch.
Has anyone else run into similar performance issues with the WL 10.3.4 ADMIN Console running in a clustered environment? If so, does anyone have any suggestions to help improve performance.
I also run a WL 10.3.4 instance in a single server environment and the servers and deployments tabs respond withing 10 seconds (very fast). It is just in a clustered environment.
Regards,
Markhi Mark, it's a very interesting story, any follow-up? I would be curious to know the reason for the delay...
-
Problems with weblogic clustering in 6.1 sp3
We have spent a lot of time trying to get our application deployed to
a cluster using weblogic 6.1 sp3 and we consistently receive a failure
when we attempt to start the managed server. This was not a problem
with weblogic sp1--we got our application to deploy to the cluster
successfully; although there was another weblogic bug there with
clients accessing EJB clusters--we won't go into that here...
We have tried this on both a Windows 2000 machine and an HP machine
running weblogic sp3. The same error occurs on both platforms.
The error in deploying our application to the cluster against weblogic
sp3 looks to have to do with our custom security realm. Inside our
custom realm we make use of a configurable providerUrl which we set to
the cluster address/port. The custom realm makes a call where it
passes in the providerUrl to:
weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
When we have our providerUrl set to the cluster address/port--e.g.,
t3://clustermember1:7001
and attempt to start the managed server we get the error:
Starting WebLogic Server ....
Connecting to http://adminserver:7117...
The WebLogic Server did not start up properly.
Exception raised:
weblogic.management.configuration.ConfigurationException:
clustermember1 not found
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
at weblogic.management.Admin.initialize(Admin.java:340)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
When we have our providerUrl set to the admin server address--e.g.,
t3://adminserver:7117
everything starts up fine.
Does anyone know why this would work on sp1 and not sp3 of weblogic
6.1?
We verified that all passwords are correct and everything else we
could determine--any ideas would be helpful.
We don't want the providerUrl to point at our admin server, we want it
to point at the cluster address/port.
When we get the managed server error, we received this error on the
AdminServer:
2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
Caught naming exception null; throwing RuntimeException.
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
unreachable; nested exception is:
java.net.ConnectException: Connection refused; No available router to
destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
<[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
Servlet failed with Exception
java.lang.RuntimeException
at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks for any help.
Rich
Bottom line:
In our custom realm we were not handling user guest correctly. Even if you
have guest user disabled, Weblogic seems to have hard-coded guest to
send messages to the cluster every-so-often. Not sure there--couldn't get
an answer out of bea as to exactly why we see guest still being used...
It seems that with sp3, the user guest interaction started happening earlier
than it did with sp1, consequently making our realm code fail when trying to
retrieve the guest user like someone we knew about in our system.
Hence, our getUser and authUserPassword methods now return null for both
users guest and system, making the secondary realm (file realm) be used to
authenticate and resolve guest & system. BEA helped get our code fixed;
however, we still don't have a lot of depth in understanding Weblogic
server's use of guest...
Apparently, in 7.x the guest & system user behavior and configuration is
different also... We'll see when we start digging into that migration.
Rich
[email protected] (Rich Koch) wrote in message news:<[email protected]>...
> Thanks for the responses--we're working with weblogic support now. We
> think that the custom realm that we have [the developer that wrote it
> left the company] is the problem.
>
> The original developer was told by someone to check:
> weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
>
> In order to determine if the JNDI was available/ready for the whole
> cluster.
>
> It seems that the meaning/setting of THE_ONE changed with this respect
> from
> sp1 to sp3--i.e., this is no longer a valid test to tell us if the
> JNDI is
> ready for the cluster.
>
> We believe this was used because the 'system' user has to be
> authenticated before the custom realm is up. Originally, before this
> check was in place, an exception was received when authenticating
> 'system'. This appears to be a weblogic limitation/issue. Support
> has told us that this is different in weblogic 7.0. Unfortunately, we
> can't upgrade from 6.1 yet.
>
> We'll post the solution when this gets figured out.
>
> Rak
>
> "Sabha" <[email protected]> wrote in message news:<[email protected]>...
> > There was a security restriction enforced from sp2/sp3 onwards in terms of
> > looking up mbeans from admin server.
> >
> > This might cause things to fail if you are attempting to lookup Mbeans with
> > guest priviliges from admin server. Also, can you try doing the following:
> >
> > Run " java weblogic.Admin -url adminServer -username system -password
> > .... -GET -pretty -type Server" and check whether the named clustermember1
> > is available in the list or not.
> >
> > Also you seem to be getting some security exception - can you check that.
> >
> > t3://tomtate.msais.com:7119: Destination
> > unreachable; nested exception is:
> >
> > --- Try running weblogic.Admin PING on this one and see whether you are
> > able to reach this server upon the error message.
> >
> > --Sabha
> >
> > "Rich Koch" <[email protected]> wrote in message
> > news:[email protected]...
> > > We have spent a lot of time trying to get our application deployed to
> > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
> > > when we attempt to start the managed server. This was not a problem
> > > with weblogic sp1--we got our application to deploy to the cluster
> > > successfully; although there was another weblogic bug there with
> > > clients accessing EJB clusters--we won't go into that here...
> > >
> > > We have tried this on both a Windows 2000 machine and an HP machine
> > > running weblogic sp3. The same error occurs on both platforms.
> > >
> > > The error in deploying our application to the cluster against weblogic
> > > sp3 looks to have to do with our custom security realm. Inside our
> > > custom realm we make use of a configurable providerUrl which we set to
> > > the cluster address/port. The custom realm makes a call where it
> > > passes in the providerUrl to:
> > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
> > >
> > > When we have our providerUrl set to the cluster address/port--e.g.,
> > > t3://clustermember1:7001
> > >
> > > and attempt to start the managed server we get the error:
> > >
> > > Starting WebLogic Server ....
> > > Connecting to http://adminserver:7117...
> > >
> ***************************************************************************
> > > The WebLogic Server did not start up properly.
> > > Exception raised:
> > > weblogic.management.configuration.ConfigurationException:
> > > clustermember1 not found
> > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
> > > at weblogic.management.Admin.initialize(Admin.java:340)
> > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
> > > at weblogic.Server.main(Server.java:35)
> > > Reason: Fatal initialization exception
> > >
> ***************************************************************************
> > >
> > > When we have our providerUrl set to the admin server address--e.g.,
> > > t3://adminserver:7117
> > >
> > > everything starts up fine.
> > >
> > > Does anyone know why this would work on sp1 and not sp3 of weblogic
> > > 6.1?
> > > We verified that all passwords are correct and everything else we
> > > could determine--any ideas would be helpful.
> > >
> > > We don't want the providerUrl to point at our admin server, we want it
> > > to point at the cluster address/port.
> > >
> > > When we get the managed server error, we received this error on the
> > > AdminServer:
> > >
> > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
> > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
> > > Caught naming exception null; throwing RuntimeException.
> > > javax.naming.CommunicationException. Root exception is
> > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
> > > unreachable; nested exception is:
> > > java.net.ConnectException: Connection refused; No available router to
> > > destination
> > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
> > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:307)
> > > at
> > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
> > textFactoryDelegate.java:211)
> > > at
> > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
> > ory.java:149)
> > > at
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
> > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
> > > at javax.naming.InitialContext.init(InitialContext.java:222)
> > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
> > Realm.java:416)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
> > lm.java:347)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
> > java:51)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
> > 225)
> > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
> > Realm.java:578)
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:221)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
> > >
> > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
> > al2)]
> > > Servlet failed with Exception
> > > java.lang.RuntimeException
> > > at
> > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
> > a:260)
> > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
> > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
> > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
> > > at
> > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
> > ava:356)
> > > at
> > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
> > tSecurityManager.java:205)
> > > at
> > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
> > ntext.java:2518)
> > > at
> weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
> > :2260)
> > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> > >
> > >
> > > Thanks for any help.
> > >
> > > Rich
-
WebLogic 7.0 & WebLogic 6.1 Clusters on the same Sun Machine
HI All !!
can we have two different versions of Weblogic running on same machine in different
clusters i.e. Weblogic 6.1 on one cluster with a different domain and Weblogic
7.0 on another cluster with a different domain.
Plzz reply ASAP...
Thanx
Nitesh
Yes, you can.
Nitesh wrote:
> HI All !!
>
> can we have two different versions of Weblogic running on same machine in different
> clusters i.e. Weblogic 6.1 on one cluster with a different domain and Weblogic
> 7.0 on another cluster with a different domain.
>
> Plzz reply ASAP...
>
> Thanx
>
> Nitesh
>
>
-
How to setup Clustering with Weblogic?
Dear All,
I am a beginner of using Weblogic. Now i need to setup Clustering in
company. I have 3 NT Server and install Weblogic 5.1.0 on each machine, the
name is Cluster1, Cluster2 and Cluster3. At the First Step, can someone tell
me how to setup the clustering and how to test it to esure that is work???
Thanks so much!
hk-beginnermore specifically,
http://www.weblogic.com/docs51/cluster/index.html
Ketan
"Billy Bunter" <[email protected]> wrote in message
news:[email protected]..
Look at the BEA docs.
beginner wrote:
Dear All,
I am a beginner of using Weblogic. Now i need to setup Clustering
in
company. I have 3 NT Server and install Weblogic 5.1.0 on each machine,the
name is Cluster1, Cluster2 and Cluster3. At the First Step, can someonetell
me how to setup the clustering and how to test it to esure that iswork???
Thanks so much!
hk-beginner -
Special consideration for coding clients while using weblogic clustering
Hi.
I wanted to know whether there are any special consdirations to
be taken while coding clients(servlets in our case) for EJBs when
we are using clustering of App servers.
In our setup, we are following the recommended 2-tier architecture
for Weblogic5.1
thanks and regards,
Amol
Amol wrote:
> Hi,
> adding a couple of points to the previous mail:
> 1. In case of servlet failure after doXXX() method has been
> called and before the method returns, if the app server
> fails, will doXXX() be called again on the servlet in the
> secondary server?
> 2. How much time does it take for the servlet session on
> one machine to be replicated on the second machine when
> using in-memory replication.
It depends on the size of the object and complexity.
-- Prasad
>
> Thanks,
> Amol
>
> "Amol" <[email protected]> wrote:
> >
> >Hi kumar (and everybody),
> >
> >Your opinion resolves the doubt i had in mind, since even
> >WebLogic
> >docs do not say anything about clustering affecting the
> >coding
> >of bean clients.
> >
> >However may I request you to please evaluate the same
> >query with
> >respect to the following conditions:
> >1. The Session bean calls a stored proc on the db. After
> >the call
> >to stored proc and before the stored proc returns with
> >the results,
> >the app server fails.
> >Here there could be two cases of interest, a) Stored proc
> >does
> >a write on db -OR- b) Stored proc does only a read on
> >db
> >2. The Session bean calls an Entity bean which "writes"
> >to the
> >db. The db write is successful, but before the entire
> >call to the
> >session bean is completed(that is before user gets his
> >results)
> >the Server fails. Now permanent changes have been made
> >to the db,
> >but client doesnt get the results.
> >
> >Please note the fact that we are using recommended 2-tier
> >architecture
> >and in this case server failure would imply failure of
> >Servlet
> >as well as the beans.
> >
> >Regards,
> >Amol
> >--------------------------
> >
> >Kumar Allamraju <[email protected]> wrote:
> >>Absolutely not. Make sure the objects you are putting
> >>in the session are
> >>serializable.
> >>
> >>
> >>
> >>Amol wrote:
> >>
> >>> Hi.
> >>> I wanted to know whether there are any special consdirations
> >>to
> >>> be taken while coding clients(servlets in our case)
> >>for EJBs when
> >>> we are using clustering of App servers.
> >>>
> >>> In our setup, we are following the recommended 2-tier
> >>architecture
> >>> for Weblogic5.1
> >>>
> >>> thanks and regards,
> >>> Amol
> >>
> >
Cheers
- Prasad
-
Clustered Remote Object Bound To JNDI
Hello,
I'd like to know if Weblogic 5.1 (service pack 10) supports
clusterable remote objects.
What I am trying to do is to implement a remote object that extends
UnicastRemoteObject interface and bind it to JNDI. When the client
needs the services, it will lookup that object in JNDI and call its
methods remotely.
What happens to my test implementation is that it all works well when
I run Weblogic locally, but if it is run on the remote server, it
gives me the exception to the extend that the stub for my remote
object is not found (although it is in the classpath). I understand
that this is because I should be using weblogic.rmic instead of
regular rmic, is that right?
Thanks,
Eugene Kononov.
Hello,
I'd like to know if Weblogic 5.1 (service pack 10) supports
clusterable remote objects.
What I am trying to do is to implement a remote object that extends
UnicastRemoteObject interface and bind it to JNDI. When the client
needs the services, it will lookup that object in JNDI and call its
methods remotely.
What happens to my test implementation is that it all works well when
I run Weblogic locally, but if it is run on the remote server, it
gives me the exception to the extend that the stub for my remote
object is not found (although it is in the classpath). I understand
that this is because I should be using weblogic.rmic instead of
regular rmic, is that right?
Thanks,
Eugene Kononov.
-
WebLogic 5.1 sp6 .. session in cluster not working properly
It seems like there is a problem in Weblogic 5.1 with sessions in a
clustered environment. The problem is immediately visible with sp3 but
also appears in different form with sp6 . I discovered the problem is
actually with session while testing the cluster with a Session servlet
given with the Weblogic 5.1 kit.
I regiestered the servlet as servlet/session.
The environment is briefly as follows:
Solaris 2.6
Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
machine with two multihome addreses like home1:7001 and home2:7001
Cluster properties in mycluster/weblogic.properties are set as,
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
and also started with required cluster properties in startup.
iPlanet 4.0 webserver - obj.conf has entries like
WebLogicCluster="home1:7001,home2:7001"
All requests are made as http://<host>/servlet/session
sp3 ) After both members are booted up, the first call to session
servlet from any new browser session throws a NullException in server,
but subsequent calls work fine. Single server works fine.
After looking at sp6 release notes it appeared to me that it was a known
problem with cluster.
sp6 ) After both members are booted up, all calls to session servlet do
not complete and eventually it times out. Other servlets work fine.
It only works if we do these steps,
- one of the member is booted up and then session servlet is called and
response comes back.
- second member is booted up and it works well if session servlet is
called. Subsequent requests to both members work fine.
Another strange behaviour:
While running a snoop servlet in cluster subsequent requests show,
Requested url :
either http://<host>/servlet/snoop
or http://<host>:7001/servlet/snoop alternatively
which is strange.
You are not using the same service pack on both the servers. let try do that and see how it goes.
1. Also, if you are doing testing why do you so many threads.
2. The servers are unable to open sockets to each other. Could be network related. Please check into that also, but first start the servers with the same service pack.
- Prasad
Sutanu Ghosh wrote:
> Here are the thread dumps from both members of the cluster. I took the dumps
> about 5 times in 10 secs interval. It will be helpful for us if you can give
> some insight about this problem.
> Also about the snoop servlet, can you explain why the requested url is
> different (one with weblogic port another without it) in every alternate
> requests ?
> thanks
>
> Prasad Peddada wrote:
>
> > Sutanu Ghosh wrote:
> >
> > > It seems like there is a problem in Weblogic 5.1 with sessions in a
> > > clustered environment. The problem is immediately visible with sp3 but
> > > also appears in different form with sp6 . I discovered the problem is
> > > actually with session while testing the cluster with a Session servlet
> > > given with the Weblogic 5.1 kit.
> > > I regiestered the servlet as servlet/session.
> > >
> > > The environment is briefly as follows:
> > > Solaris 2.6
> > > Weblogic 5.1.0 sp3 or sp6 - 2 servers clustered and running on same
> > > machine with two multihome addreses like home1:7001 and home2:7001
> > > Cluster properties in mycluster/weblogic.properties are set as,
> > > weblogic.httpd.clustering.enable=true
> > > weblogic.httpd.session.enable=true
> > > weblogic.httpd.session.persistence=true
> > > weblogic.httpd.session.persistentStoreType=replicated
> > > and also started with required cluster properties in startup.
> > >
> > > iPlanet 4.0 webserver - obj.conf has entries like
> > > WebLogicCluster="home1:7001,home2:7001"
> > >
> > > All requests are made as http://<host>/servlet/session
> > >
> > > sp3 ) After both members are booted up, the first call to session
> > > servlet from any new browser session throws a NullException in server,
> > > but subsequent calls work fine. Single server works fine.
> > > After looking at sp6 release notes it appeared to me that it was a known
> > > problem with cluster.
> > >
> > > sp6 ) After both members are booted up, all calls to session servlet do
> > > not complete and eventually it times out. Other servlets work fine.
> > > It only works if we do these steps,
> >
> > Take thread dumps in intervals of 10 seconds and post them again.
> >
> > > - one of the member is booted up and then session servlet is called and
> > > response comes back.
> > > - second member is booted up and it works well if session servlet is
> > > called. Subsequent requests to both members work fine.
> > >
> > > Another strange behaviour:
> > > While running a snoop servlet in cluster subsequent requests show,
> > > Requested url :
> > > either http://<host>/servlet/snoop
> > > or http://<host>:7001/servlet/snoop alternatively
> > > which is strange.
>
> ------------------------------------------------------------------------
> SIGQUIT
> A SIGQUIT has been received. Do you want to:
> [ 0 ] continue program
> [ 1 ] check & print one deadlock
> [ 2 ] check & print all deadlocks
> [ 3 ] dump thread stacks
> [ 4 ] dump lock registry
> [ 5 ] heap inspection
> [ 6 ] terminate program
> Type number corresponding to selected action: Found 0 deadlock
>
> Full thread dump:
> "HighPriority TimeEventGenerator" (TID:0xe7f658, sys_thread_t:0xe7f590, state:CW, thread_t: t@90, threadID:0xc9751dd8, stack_bottom:0xc9752000, stack_size:0x20000) prio=9
>
> [1] weblogic.time.common.internal.TimeTable.snooze(TimeTable.java:256)
> [2] weblogic.time.common.internal.TimeEventGenerator.run(TimeEventGenerator.java:131)
> [3] java.lang.Thread.run(Thread.java:479)
> -------------------
> "SSLListenThread" (TID:0xe4e270, sys_thread_t:0xe4e1a8, state:R, thread_t: t@89, threadID:0xc9841dd8, stack_bottom:0xc9842000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:240)
> [4] java.net.ServerSocket.accept(ServerSocket.java:224)
> [5] weblogic.security.SSL.SSLServerSocket.acceptNoHandshake(SSLServerSocket.java:121)
> [6] weblogic.security.SSL.SSLServerSocket.accept(SSLServerSocket.java:112)
> [7] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "ListenThread" (TID:0xe247f0, sys_thread_t:0xe24728, state:R, thread_t: t@88, threadID:0xc9801dd8, stack_bottom:0xc9802000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainSocketImpl.socketAccept(Native Method)
> [2] java.net.PlainSocketImpl.accept(PlainSocketImpl.java:406)
> [3] java.net.ServerSocket.implAccept(ServerSocket.java:238)
> [4] java.net.ServerSocket.accept(ServerSocket.java:223)
> [5] weblogic.t3.srvr.ListenThread.run(ListenThread.java:226)
> -------------------
> "NBExecuteThread-1" (TID:0xa9b748, sys_thread_t:0xa9b680, state:CW, thread_t: t@84, threadID:0xc9891dd8, stack_bottom:0xc9892000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "NBExecuteThread-0" (TID:0xa9a388, sys_thread_t:0xa9a2c0, state:CW, thread_t: t@83, threadID:0xc98c1dd8, stack_bottom:0xc98c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-69" (TID:0xa98fc8, sys_thread_t:0xa98f00, state:R, thread_t: t@82, threadID:0xc9911dd8, stack_bottom:0xc9912000, stack_size:0x20000) prio=5
>
> [1] java.net.PlainDatagramSocketImpl.peek(Native Method)
> [2] java.net.DatagramSocket.receive(DatagramSocket.java:348)
> [3] weblogic.cluster.TDMSocketIPM.receive(TDMSocketIPM.java:80)
> [4] weblogic.cluster.TMSocket.execute(TMSocket.java:233)
> [5] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-68" (TID:0xa97be8, sys_thread_t:0xa97b20, state:R, thread_t: t@81, threadID:0xc9941dd8, stack_bottom:0xc9942000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.poll(Native Method)
> [2] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [3] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [4] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-67" (TID:0xa96828, sys_thread_t:0xa96760, state:MW, thread_t: t@80, threadID:0xc9991dd8, stack_bottom:0xc9992000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-66" (TID:0xa95468, sys_thread_t:0xa953a0, state:MW, thread_t: t@79, threadID:0xc99c1dd8, stack_bottom:0xc99c2000, stack_size:0x20000) prio=5
>
> [1] weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:259)
> [2] weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-65" (TID:0xa940a8, sys_thread_t:0xa93fe0, state:CW, thread_t: t@78, threadID:0xc9a11dd8, stack_bottom:0xc9a12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-64" (TID:0xa92ce8, sys_thread_t:0xa92c20, state:CW, thread_t: t@77, threadID:0xc9a41dd8, stack_bottom:0xc9a42000, stack_size:0x20000) prio=5
>
> [1] weblogic.rjvm.ResponseImpl.waitForData(ResponseImpl.java:43)
> [2] weblogic.rjvm.ResponseImpl.getThrowable(ResponseImpl.java:58)
> [3] weblogic.rmi.extensions.BasicResponse.getThrowable(BasicResponse.java:13)
> [4] weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:74)
> [5] weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
> [6] weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
> [7] weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:224)
> [8] weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:164)
> [9] weblogic.jndi.Environment.getContext(Environment.java:122)
> [10] weblogic.jndi.Environment.getInitialContext(Environment.java:104)
> [11] weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:362)
> [12] weblogic.cluster.replication.ReplicationManager.createSecondary(ReplicationManager.java:406)
> [13] weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:585)
> [14] weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
> [15] weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
> [16] weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:331)
> [17] weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1215)
> [18] weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1118)
> [19] examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
> [20] javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> [21] javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> [22] weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:123)
> [23] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:761)
> [24] weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:708)
> [25] weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
> [26] weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:346)
> [27] weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:246)
> [28] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-63" (TID:0xa91b10, sys_thread_t:0xa91a48, state:CW, thread_t: t@76, threadID:0xc9a91dd8, stack_bottom:0xc9a92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-62" (TID:0xa90750, sys_thread_t:0xa90688, state:CW, thread_t: t@75, threadID:0xc9ac1dd8, stack_bottom:0xc9ac2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-61" (TID:0xa8f390, sys_thread_t:0xa8f2c8, state:CW, thread_t: t@74, threadID:0xc9b11dd8, stack_bottom:0xc9b12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-60" (TID:0xa8dfd0, sys_thread_t:0xa8df08, state:CW, thread_t: t@73, threadID:0xc9b41dd8, stack_bottom:0xc9b42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-59" (TID:0xa8cc10, sys_thread_t:0xa8cb48, state:CW, thread_t: t@72, threadID:0xc9b91dd8, stack_bottom:0xc9b92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-58" (TID:0xa8ba38, sys_thread_t:0xa8b970, state:CW, thread_t: t@71, threadID:0xc9bc1dd8, stack_bottom:0xc9bc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-57" (TID:0xa89670, sys_thread_t:0xa895a8, state:CW, thread_t: t@70, threadID:0xc9c11dd8, stack_bottom:0xc9c12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-56" (TID:0xa882b0, sys_thread_t:0xa881e8, state:CW, thread_t: t@69, threadID:0xc9c41dd8, stack_bottom:0xc9c42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-55" (TID:0xa86ef0, sys_thread_t:0xa86e28, state:CW, thread_t: t@68, threadID:0xc9c91dd8, stack_bottom:0xc9c92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-54" (TID:0xa85b30, sys_thread_t:0xa85a68, state:CW, thread_t: t@67, threadID:0xc9cc1dd8, stack_bottom:0xc9cc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-53" (TID:0xa84958, sys_thread_t:0xa84890, state:CW, thread_t: t@66, threadID:0xc9d11dd8, stack_bottom:0xc9d12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-52" (TID:0xa83598, sys_thread_t:0xa834d0, state:CW, thread_t: t@65, threadID:0xc9d41dd8, stack_bottom:0xc9d42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-51" (TID:0xa821d8, sys_thread_t:0xa82110, state:CW, thread_t: t@64, threadID:0xc9d91dd8, stack_bottom:0xc9d92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-50" (TID:0xa80a10, sys_thread_t:0xa80948, state:CW, thread_t: t@63, threadID:0xc9dc1dd8, stack_bottom:0xc9dc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-49" (TID:0xa7f650, sys_thread_t:0xa7f588, state:CW, thread_t: t@62, threadID:0xc9e11dd8, stack_bottom:0xc9e12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-48" (TID:0xa7e478, sys_thread_t:0xa7e3b0, state:CW, thread_t: t@61, threadID:0xc9e41dd8, stack_bottom:0xc9e42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-47" (TID:0xa7d0b8, sys_thread_t:0xa7cff0, state:CW, thread_t: t@60, threadID:0xc9e91dd8, stack_bottom:0xc9e92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-46" (TID:0xa7bcf8, sys_thread_t:0xa7bc30, state:CW, thread_t: t@59, threadID:0xc9ec1dd8, stack_bottom:0xc9ec2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-45" (TID:0xa7a938, sys_thread_t:0xa7a870, state:CW, thread_t: t@58, threadID:0xc9f11dd8, stack_bottom:0xc9f12000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-44" (TID:0xa79578, sys_thread_t:0xa794b0, state:CW, thread_t: t@57, threadID:0xc9f41dd8, stack_bottom:0xc9f42000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-43" (TID:0xa783a0, sys_thread_t:0xa782d8, state:CW, thread_t: t@56, threadID:0xc9f91dd8, stack_bottom:0xc9f92000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-42" (TID:0xa76fe0, sys_thread_t:0xa76f18, state:CW, thread_t: t@55, threadID:0xc9fc1dd8, stack_bottom:0xc9fc2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-41" (TID:0xa74c18, sys_thread_t:0xa74b50, state:CW, thread_t: t@54, threadID:0xca011dd8, stack_bottom:0xca012000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-40" (TID:0xa73858, sys_thread_t:0xa73790, state:CW, thread_t: t@53, threadID:0xca041dd8, stack_bottom:0xca042000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-39" (TID:0xa72498, sys_thread_t:0xa723d0, state:CW, thread_t: t@52, threadID:0xca091dd8, stack_bottom:0xca092000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-38" (TID:0xa712c0, sys_thread_t:0xa711f8, state:CW, thread_t: t@51, threadID:0xca0c1dd8, stack_bottom:0xca0c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-37" (TID:0xa6ff00, sys_thread_t:0xa6fe38, state:CW, thread_t: t@50, threadID:0xca111dd8, stack_bottom:0xca112000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-36" (TID:0xa6eb40, sys_thread_t:0xa6ea78, state:CW, thread_t: t@49, threadID:0xca141dd8, stack_bottom:0xca142000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-35" (TID:0xa6d780, sys_thread_t:0xa6d6b8, state:CW, thread_t: t@48, threadID:0xca191dd8, stack_bottom:0xca192000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-34" (TID:0xa3c940, sys_thread_t:0xa3c878, state:CW, thread_t: t@47, threadID:0xca1c1dd8, stack_bottom:0xca1c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-33" (TID:0xa3c720, sys_thread_t:0xa3c658, state:CW, thread_t: t@46, threadID:0xca211dd8, stack_bottom:0xca212000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-32" (TID:0xa3aa60, sys_thread_t:0xa3a998, state:CW, thread_t: t@45, threadID:0xca241dd8, stack_bottom:0xca242000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-31" (TID:0xa3a658, sys_thread_t:0xa3a590, state:CW, thread_t: t@44, threadID:0xca291dd8, stack_bottom:0xca292000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-30" (TID:0xa45828, sys_thread_t:0xa45760, state:CW, thread_t: t@43, threadID:0xca2c1dd8, stack_bottom:0xca2c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-29" (TID:0xa23d00, sys_thread_t:0xa23c38, state:CW, thread_t: t@42, threadID:0xca311dd8, stack_bottom:0xca312000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-28" (TID:0xa14fe8, sys_thread_t:0xa14f20, state:CW, thread_t: t@41, threadID:0xca341dd8, stack_bottom:0xca342000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-27" (TID:0xa21eb0, sys_thread_t:0xa21de8, state:CW, thread_t: t@40, threadID:0xca391dd8, stack_bottom:0xca392000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-26" (TID:0xa0fee0, sys_thread_t:0xa0fe18, state:CW, thread_t: t@39, threadID:0xca3c1dd8, stack_bottom:0xca3c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-25" (TID:0x9c54c8, sys_thread_t:0x9c5400, state:CW, thread_t: t@38, threadID:0xca411dd8, stack_bottom:0xca412000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-24" (TID:0x9c7cc8, sys_thread_t:0x9c7c00, state:CW, thread_t: t@37, threadID:0xca441dd8, stack_bottom:0xca442000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-23" (TID:0xa0acc8, sys_thread_t:0xa0ac00, state:CW, thread_t: t@36, threadID:0xca491dd8, stack_bottom:0xca492000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-22" (TID:0xa17b08, sys_thread_t:0xa17a40, state:CW, thread_t: t@35, threadID:0xca4c1dd8, stack_bottom:0xca4c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-21" (TID:0x9c8498, sys_thread_t:0x9c83d0, state:CW, thread_t: t@34, threadID:0xca511dd8, stack_bottom:0xca512000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-20" (TID:0x9fb8f8, sys_thread_t:0x9fb830, state:CW, thread_t: t@33, threadID:0xca541dd8, stack_bottom:0xca542000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-19" (TID:0x9fd4f8, sys_thread_t:0x9fd430, state:CW, thread_t: t@32, threadID:0xca591dd8, stack_bottom:0xca592000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-18" (TID:0xa0f628, sys_thread_t:0xa0f560, state:CW, thread_t: t@31, threadID:0xca5c1dd8, stack_bottom:0xca5c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-17" (TID:0x9c0cf8, sys_thread_t:0x9c0c30, state:CW, thread_t: t@30, threadID:0xca611dd8, stack_bottom:0xca612000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-16" (TID:0x9bc4f8, sys_thread_t:0x9bc430, state:CW, thread_t: t@29, threadID:0xca641dd8, stack_bottom:0xca642000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-15" (TID:0x9b38f8, sys_thread_t:0x9b3830, state:CW, thread_t: t@28, threadID:0xca691dd8, stack_bottom:0xca692000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-14" (TID:0x9b3cf8, sys_thread_t:0x9b3c30, state:CW, thread_t: t@27, threadID:0xca6c1dd8, stack_bottom:0xca6c2000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.kernel.ExecuteThread.waitForRequest(ExecuteThread.java:103)
> [3] weblogic.kernel.ExecuteThread.run(ExecuteThread.java:111)
> -------------------
> "ExecuteThread-13" (TID:0x9c94f8, sys_thread_t:0x9c9430, state:CW, thread_t: t@26, threadID:0xca711dd8, stack_bottom:0xca712000, stack_size:0x20000) prio=5
>
> [1] java.lang.Object.wait(Object.java:424)
> [2] weblogic.ke -
Load balancing with multiple clusters (HTTPProxyServlet)
Hello!
I'm newbie in Weblogic. I would like to have clustering and load balancing in
development environment. I've created 2 clusters, with one managed server each.
I've created a web application for deploying the http proxy servlet and put it
under another managed server without clustering. Below is my configuration:
managed server without cluster (as proxy) - Port 8002
admin server - Port 8001
cluster_1 - multicast address 237.0.0.11, multicast port 8004, cluster address
- t3://localhost:8006, t3://localhost:8007
cluster_2 - multicast address 237.0.0.10, multicast port 8014, cluster address
- t3://localhost:8006, t3://localhost:8007
managed_cluster1 - under cluster_1, port 8006
managed_cluster2 - under cluster_2, port 8007
in the web.xml of the proxy, i put the following parameters:
<param-name>WebLogicCluster</param-name>
<param-value>localhost:8006|localhost:8007</param-value>
However, when i send the requests to http://localhost:8002/sms, the requests always
go to the same server, for eg: managed_cluster2?
If i configure using single cluster, the load balancing will be in proper. What's
the cause fo the problem? and any solution?
Thanx in advance.
Regards,
joey
You have 2 options here Jordi, either you can use BGP loadbalancing, this requires multipath as BGP by default would only install one route from the BGP table to the RIB hence FIB.
But this may result in excessive IRL (inter rack link) usage in the cluster when traffic coming in on rack0 wants to take the bGP path out on rack1
You could also use ABF (access-list based forwarding) to forcelly push traffic received on rack0 out on the link on rack0 and use an ipsla tracker to fallback to rack1 in case the uplink is gone.
Alternatively to extend this by IGP signaling to redirect traffic preferably to rack1 to start with to minimize the IRL usage.
And then you also have the ability to use RPL in the uplink path to make one link more preferred on teh internet then the other in case you want to control a bit which link is preferably used on rack0 or rack1
regards
xander -
Stateless session bean in clustered environment
Is there any option in ejbc (Stateless Session Bean) for clustered environment?
Do I have to take care for clustered environment?
Mukesh <[email protected]> wrote:
>Is there any option in ejbc (Stateless Session Bean) for clustered environment?
>Do I have to take care for clustered environment?
Use the following line in your weblogic-ejb-jar.xml
<stateless-bean-is-clusterable> true </stateless-bean-is-clusterable>
This will make the container aware that your stateless bean is to be clustered.
The ejbc can be run as usual.
-
Folks,
I have 3 UNIX machines with 3 Managed WebLogic servers.If I want to do clustering,
is it necessary to have the same port number for these 3 managed weblogic servers?
MachineA:30000, MachineB:30000, MachineB:30000
what happens if I give different port number for the above managed server instances
and try to do WL clustering?
Thanks
- Robot
"Majic Robot" <[email protected]> wrote:
>
>Folks,
>
>I have 3 UNIX machines with 3 Managed WebLogic servers.If I want to do
>clustering,
>is it necessary to have the same port number for these 3 managed weblogic
>servers?
>
>MachineA:30000, MachineB:30000, MachineB:30000
>
>what happens if I give different port number for the above managed server
>instances
>and try to do WL clustering?
>
>Thanks
>- Robot
You can use the same or different port numbers. The key to providing managed server
listening addresses is to ensure unique IPaddress:port combination for each managed
server.
Regards,
Rob
-
Apache configuration for weblogic
Hi All
I need your help for configuring my apache for weblogic. Actually we created 2 non clustered server and deployed an application on them. Now we want to achieve the load balancing on the apache side. So, I am just wondering what exactly I should write down in http.conf to achieve it.
e.g in clustered environment we give :
<Location /process>
WebLogicCluster abc:7210,xyz:7210
SetHandler weblogic-handler
</Location>
where abc and xyz are cluster members.
If you have any idea then please share it.
Thanks in Advance.To configure Apache Plug-in with Weblogic Server, follow the steps below
1. To make Apache server run on a different port say 8080, other than the dafault (80).
Modify the httpd.conf present at
D:\Program Files\Apache Group\Apache2\conf
Change the Listen port to 8080 in the httpd.conf file
Listen 8080
2. Copy the mod_wl_20.so from \wlserver_10.3\server\plugin\win\32 to
D:\Program Files\Apache Group\Apache2\modules
3. Apply the plug-n module by adding these in the httpd.conf file
LoadModule weblogic_module modules/mod_wl_20.so
<Location />
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicCluster localhost:7003,localhost:7005
Debug ON
WLLogFile c:/temp/wlproxy.log
WLTempDir c:/temp
</IfModule>
4. Restart the Apache Server -
Hi,
In the Weblogic documentation with regards to JMS and Clusters it is stated that "Automatic failover is not supported by WebLogic JMS in this release." In my case, this release is 8.1.2. Can anyone clarify exactly what this means?
Thanks,
AoifeNot sure whether it is just me or not - the new security stuff in WebLogic 8.1
just makes life so much tougher.
Thanks for the suggestion anyways.
Eric
Tom Barnes <[email protected].bea.com>
wrote:
>Even though its meant for foreign providers, perhaps credential
>mapping would work? See:
>
>http://edocs.bea.com/wls/docs81/ejb/message_beans.html#1151409
>
>Also, you might want to try posting to the
>security and/or ejb newsgroups.
>
>Tom
>
>P.S. This question has come up before, so it seems likely
>that the security section of the MDB documentation
>may need more detail. If you post any feedback here,
>I'll make sure it gets sent directly to the
>documentation folks...
>
>Eric Ma wrote:
>
>> I have a JMS Topic living in one WebLogic 8.1 domain and a MDB that
>listens to
>> this JMS Topic living in another domain. Do I need to configure trusted
>domain
>> relationship for both domains?
>
-
Deploy error on primaveraweb.ear during Web Access installation on weblogic
Hi
i installed on
weblogic 10.3
jdk-6u14-windows
P6_70_Web_Access
*try to start the all services got this error and failed"
<05/05/2010 2:02:32 PM GMT+10:00> <Warning> <HTTP> <BEA-101162> <User defined li
stener com.primavera.pvweb.listeners.PVContextListener failed: org.springframewo
rk.beans.factory.BeanCreationException: Error creating bean with name 'registryS
ervice' defined in class path resource [/com/primavera/pvweb/servlet/webconf.xml
]: Invocation of init method failed; nested exception is com.primavera.common.ex
ceptions.InvalidBootstrapException: System property 'primavera.bootstrap.home' n
ot found.
org.springframework.beans.factory.BeanCreationException: Error creating bean wit
h name 'registryService' defined in class path resource [/com/primavera/pvweb/se
rvlet/webconf.xml]: Invocation of init method failed; nested exception is com.pr
imavera.common.exceptions.InvalidBootstrapException: System property 'primavera.
bootstrap.home' not found
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory$1.run(AbstractAutowireCapableBeanFactory.java:383)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBean
Factory.createBean(AbstractAutowireCapableBeanFactory.java:353)
Truncated. see log file for complete stacktrace
com.primavera.common.exceptions.InvalidBootstrapException: System property 'prim
avera.bootstrap.home' not found
at com.primavera.common.BootstrapHome.get(Unknown Source)
at com.primavera.infr.admin.MetaCfg.a(Unknown Source)
at com.primavera.infr.admin.MetaCfg.getMetaJDBCURL(Unknown Source)
at com.primavera.infr.srvcs.RegistryServiceImpl.init(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<05/05/2010 2:02:32 PM GMT+10:00> <Error> <Deployer> <BEA-149265> <Failure occur
red in the execution of deployment request with ID '1273032137841' for task '1'.
Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.jav
a:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:60)
Truncated. see log file for complete stacktrace
com.primavera.common.exceptions.InvalidBootstrapException: System property 'prim
avera.bootstrap.home' not found
at com.primavera.common.BootstrapHome.get(Unknown Source)
at com.primavera.infr.admin.MetaCfg.a(Unknown Source)
at com.primavera.infr.admin.MetaCfg.getMetaJDBCURL(Unknown Source)
at com.primavera.infr.srvcs.RegistryServiceImpl.init(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<05/05/2010 2:02:32 PM GMT+10:00> <Error> <Deployer> <BEA-149202> <Encountered a
n exception while attempting to commit the 7 task for the application 'primavera
web'.>
<05/05/2010 2:02:32 PM GMT+10:00> <Warning> <Deployer> <BEA-149004> <Failures we
re detected while initiating start task for application 'primaveraweb'.>
<05/05/2010 2:02:32 PM GMT+10:00> <Warning> <Deployer> <BEA-149078> <Stack trace
for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.jav
a:1373)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleSta
teDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStat
eDriver.java:60)
Truncated. see log file for complete stacktrace
com.primavera.common.exceptions.InvalidBootstrapException: System property 'prim
avera.bootstrap.home' not found
at com.primavera.common.BootstrapHome.get(Unknown Source)
at com.primavera.infr.admin.MetaCfg.a(Unknown Source)
at com.primavera.infr.admin.MetaCfg.getMetaJDBCURL(Unknown Source)
at com.primavera.infr.srvcs.RegistryServiceImpl.init(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
any idea how to fix this issue?For me I recieved this error in one of my managed servers in a cluster, but not the other. It was caused due to the fact that the application had been redeployed, but the managed servers had different bre.bootstrap files. Looks like lessons leared from this error are:
#1 Ensure your JAVA_OPTIONS are set correctly (especially for the bre.bootstrap home)
NOTE: The JAVA_OPTIONS can be set in startWeblogic.cmd, but in a clustered environment they should be set in the server start tab for each managed server in the Weblogic Admin Console.
#2 In a clustered Weblogic environment make sure both bre.bootstrap files are exactly the same. -
Is there a weblogic server sdk?
I only need the classes and the jar file.
I don't want to install the whole thing which takes about 250mb.If you are just developing and don't want to test, just use the j2ee.jar
that comes with the J2EESDK from Sun. That's all you need.
Otherwise, delete some of those popular .jpg files in your IE cache to free
up some space and install 250mb of Weblogic ;-)
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Khan" <[email protected]> wrote in message
news:3c5ed1e4$[email protected]..
Is there a weblogic server sdk?
I only need the classes and the jar file.
I don't want to install the whole thing which takes about 250mb.
Maybe you are looking for
-
Hi frnds, How I will upload Logo in SAPSCRIPT? I have created Header window, Now I want to add Logo in Header Window. Regards.
-
Milestone billing without sales Order
Hi Experts, We have a requirement to use SAP PS to produce a material and be used in the same company or the sister companies. The project will be only for OPEX cost. They have requested us to do by milestone billing as the fund will be paid at inter
-
Solman setup maintenance optimizer
Hi all, I'm trying to setup my Solman Maintenance Optimizer to download SP. When I read the configuration guide. It says the prerequisite is as below :- The Maintenance Optimizer contains a lot of scenarios for maintenence procedures. The scenarios h
-
Parallel user for oc4jadmin for monitoring BPEL processes
Dear All We need to create one user which can be used to monitoring the BPEL processes on console, we dont want to user oc4jadmin user, so how can we create a user who can monitor the BPEL processes, but cant do any change on the BPEL processes / con
-
hi i have a problem that i m not able to start dbconsole process. when i type emctl status dbconsole it is diving me the message oracle enter prise manager is not running logs are generated in directory 'c:\app\hpuser\..............\sysman\log I did