WLS Express and in-memory replication
I will be purchasing WLS and or WLS Express. I'm looking at using Zeus as my Web Server and then using the Apache-Proxy Plugin for redirecting dynamic content to my Web-Cluster.
Question: Can WebLogic Express do clustering and in-memory session replication? If so I would be very intrested. We will be migrating our business logic into EJB's soon enough but I have a proof of concept comming up real quick and I I could use WLS Express for my Web-Cluster and then use the more "Expensive" but robust App-Server in the back I would simply love it!
Please help me:)
the Viking!
XMLViking wrote:
>
> Rob,
>
> Thanks for the rapid response. I had conducted a little research later today and arrived at the same conclusion. So it's my understanding that you create the in-memory replication through the usage of the Proxy-Plug in and the usage of a Replication Group?
>
Basically, yes. The docs should cover this in detail.
> BEA mentions a considerable overhead for the serialization of the servlets session state? Does anyone have any data on the latency we are talking about here? Does this even begin to compare with the costs of a JDBC call for session retrieval from a DB?
>
For most applications, the in-memory rep performance should be very
good. In the benchmarks I've seen, it approaches the performance of
using no session persistence. JDBC adds quite a bit of overhead.
The in-memory rep performance is proportional to how much data you are
sending across the wire. In general, I would not recommend huge
sessions.
-- Rob
> Thank you very much!
>
> Rob Woollen <[email protected]> wrote:
> >XMLViking wrote:
> >>
> >> I will be purchasing WLS and or WLS Express. I'm
> >> looking at using Zeus as my Web Server and then
> >> using the Apache-Proxy Plugin for redirecting
> >> dynamic content to my Web-Cluster.
> >
> >Zeus is not currently a supported web server, but I believe Zeus
> >supports NSAPI so our Netscape plug-in may work.
> >
> >>
> >> Question: Can WebLogic Express do clustering and
> >> in-memory session replication? If so I would be very
> >> intrested. We will be migrating our business logic
> >> into EJB's soon enough but I have a proof of concept
> >> comming up real quick and I I could use WLS Express
> >> for my Web-Cluster and then use the more "Expensive"
> >> but robust App-Server in the back I would simply
> >> love it!
> >
> >You can purchase WebLogic Express with clustering support. Essentially
> >you get the in-memory replication of servlet session state.
> >
> >Contact your sales representative or [email protected] for more info.
> >
> >-- Rob
> >
> >>
> >> Please help me:)
> >>
> >> the Viking!
Similar Messages
-
Is a clustering licence required for using In-Memory replication?
Hi,
Could you please tell me if it is possible to use In-Memory replication
without a clustering licence? (With WebLogic 6 on Linux with eval.
licence.)
I ask, because the documentation states that it can be used with
HW load-balancing devices. If that is the case, how do you configure
replication without configuring a WebLogic cluster (since you already
have a HW LB cluster!).
Regards,
Frank Olsen
Okay, so then the advice to contact your BEA account rep for a clustering eval
license is correct.
Frank Olsen wrote:
> Hi and thanks for your help,
>
> My license file does not have support for clustering/replication.
> There's "only": WebLogic, SSL/Export, 2PC, EJB 1.1, EJB 2.0, JMS,
> jDriver/MSSQLServer4, jDriver/Informix4, jDriver/Oracle.
>
> BTW, sorry for misreading the first response -- maybe I can put
> it on the account on the end of the day with a flu ;-)
>
> Robert Patrick <[email protected]> wrote:
> >My wife has the now expired eval license that came packaged
> >with WLS 6.0 GA and
> >it includes licenses for clustering and in-memory replication
> >for both servlets
> >and EJBs.
> >
> >Hope this helps,
> >Robert
> >
> >Prasad Peddada wrote:
> >
> >> I don't think replication license is part of it.
> >>
> >> -- Prasad
> >>
> >> Robert Patrick wrote:
> >>
> >> > I was under the impression that our eval licenses
> >now include clustering.
> >> > Please open up your license.bea file to see if this
> >is the case...
> >> >
> >> > Prasad Peddada wrote:
> >> >
> >> > ? Frank,
> >> > ?
> >> > ? I meant you need clustering license. Contact
> >your sales rep to get an
> >> > ? eval license.
> >> > ?
> >> > ? You can ignore groups for now.
> >> > ?
> >> > ? -- Prasad
> >> > ?
> >> > ? Frank Olsen wrote:
> >> > ?
> >> > ? ? Prasad Peddada [email protected]? wrote:
> >> > ? ? ?No, you can't use In Memory replication without
> >clustering
> >> > ? ? ?license.
> >> > ? ? ?
> >> > ? ?
> >> > ? ? Great!
> >> > ? ?
> >> > ? ? Could you please tell me how to configure this?
> >> > ? ?
> >> > ? ? The documentation took me from configuring replication
> >of HTTP
> >> > ? ? sessions in:
> >> > ? ? http://e-docs.bea.com/wls/docs60/cluster/servlet.html
> >> > ? ? to configuring Replication Groups in:
> >> > ? ? http://e-docs.bea.com/wls/docs60/cluster/setup.html#683053
> >> > ? ? which tells you to:
> >> > ? ? 1. Open the Administration Console.
> >> > ? ? 2. Select the Servers node.
> >> > ? ? 3. Select the server to configure.
> >> > ? ? 4. Select the Cluster tab.
> >> > ? ? 5. Type in values for the following attribute
> >fields:
> >> > ? ? a) Replication Group: Enter the replication
> >group name to
> >> > ? ? which this server belongs.
> >> > ? ? b) Preferred Secondary Group: Enter the name
> >of the replication
> >> > ? ? group you would like to use to host replicated
> >HTTP session states
> >> > ? ? for this server.
> >> > ? ? 6. Apply the changes.
> >> > ? ?
> >> > ? ? It's all well to give names of these groups, but
> >where do you specify
> >> > ? ? the servers in the group?
> >> > ? ?
> >> > ? ? There's a link to:
> >> > ? ? http://e-docs.bea.com/wls/docs60/adminguide/config.html#config_005
> >> > ? ? which gives a list of configuration tasks (Configuring
> >an individual
> >> > ? ? server, Cloning an indv. server, ...).
> >> > ? ?
> >> > ? ? Where to I go from here?
> >> > ? ?
> >> > ? ? Regards,
> >> > ? ? Frank Olsen
> >
-
I ran SQL Server 2012 express setup as user with administrator privileges and still it's failing to install "Database Engine Service" and "SQL Server Replication".
Any and every ideas on how to resolve this issue is greatly appreciated.Three weeks passed and I am yet to find a fix for the the failed installation of the database engine on sql server 2012 express installation. I have tried various work-around including uninstalling, deleting all the directory paths, and reinstallation. Still
not able to successfully install sql server 2012 express.
I will greatly appreciate any and every contribution towards resolving this issue. Thanks in advance.
Here is the content of log file after the latest failed installation:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2013-12-23 14:42:45
End time: 2013-12-23 15:07:51
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: mymachine1
Machine processor count: 4
OS version: Windows 7
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2012 SQLEXPRESS_GT MSSQL11.SQLEXPRESS_GT Database Engine Services
1033 Express Edition 11.0.2100.60 No
SQL Server 2012 SQLEXPRESS_GT MSSQL11.SQLEXPRESS_GT SQL Server Replication
1033 Express Edition 11.0.2100.60 No
SQL Server 2012
Management Tools - Basic 1033 Express Edition
11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9b6607e524727c7fe1defd80\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Product Update Status:
Success: KB 2674319
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, CONN, BC, SDK, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: <empty>
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Manual
SQLSYSADMINACCOUNTS: MH\gt038676t
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE53883A0%400xBE03358B%401306%4025&EvtType=0xE53883A0%400xBE03358B%401306%4025
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131223_144132\SystemConfigurationCheck_Report.htm -
In-memory replication and no. of sessions - clarification
a small question/clarification
Lets say we have 2 servers in cluster with in-memory repication. Let say maximum RAM for jvm heap can use is 1.5GB.
I understand that HTTP Session Data is stored in heap (am i wrong?).
Now lets say if we set weblogic.httpd.session.cacheEntries=1024 (default).
The documentation says...
weblogic.httpd.session.cacheEntries=x
Where x limits the number of cached sessions at any time. If you are expecting high volumes of simultaneous active sessions, you do not want these sessions to soak up the RAM of your server since this may cause performance problems swapping to and from virtual memory. When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required. If you do not use persistence, this property is ignored, and there is no soft limit to the number of sessions allowed in main memory. By default, the number of cached sessions is 1024. The minimum is 16, and maximum is Integer.MAX_VALUE. An empty session uses less than 100 bytes, but will grow as data is added to it.
If lets say 1025 user comes in what happens in followin scenario
1. no heap memory available:
Does is throw out of memory exception or what does it do to accomodate new user?
Does swapping occur for HTTP data on the heap? (or am i talking nonsense?)
2. heap memory available:
What does the following mean for in-memory replication?
When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required.
thanks in advance
shivu wrote:
> a small question/clarification
>
> Lets say we have 2 servers in cluster with in-memory repication. Let say maximum RAM for jvm heap can use is 1.5GB.
Dont' allocate 1GB for heap. Try not to allocate more than 512 MB.
> I understand that HTTP Session Data is stored in heap (am i wrong?).
>
> Now lets say if we set weblogic.httpd.session.cacheEntries=1024 (default).
>
> The documentation says...
> -----------
> weblogic.httpd.session.cacheEntries=x
> Where x limits the number of cached sessions at any time. If you are expecting high volumes of simultaneous active sessions, you do not want these sessions to soak up the RAM of your server since this may cause performance problems swapping to and from virtual memory. When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required. If you do not use persistence, this property is ignored, and there is no soft limit to the number of sessions allowed in main memory. By default, the number of cached sessions is 1024. The minimum is 16, and maximum is Integer.MAX_VALUE. An empty session uses less than 100 bytes, but will grow as data is added to it.
> ------------
>
> If lets say 1025 user comes in what happens in followin scenario
>
> 1. no heap memory available:Does is throw out of memory exception or what does it do to accomodate new user?
> Does swapping occur for HTTP data on the heap? (or am i talking nonsense?)
If you are out of memory you are out of luck.
>
> 2. heap memory available:
>
> What does the following mean for in-memory replication?
> -----
> When the cache is full, the least recently used sessions are stored in the persistent store and recalled automatically when required.
> ----
Hmm. I don't think there is any hard limit with in memory replication. But I would check and let you know.
>
> thanks in advance
Cheers
- Prasad
-
In memory replication problems when I bring up a new server
I've got in memory replication set up for 6.1. It works fine if I have 2 servers
up and 1 goes down.
However, if I have 1 server up and a bring a second server up, the sessions blow
out.
E.g. I've got server A and server B.
Both are up, both have sessions. As new sessions come in, they are replicated over
to the other server.
now I bring server B down. All sessions on B fail over to A.
so far so good.
However when I bring server A back up some of the sessions fail as soon as the server
is back up.
Is this a configuration issue, is this a know problem?
This worked fine in weblogic 5.1. In 5.1 when I brought an instance back up, everything
worked fine.
It turns out the problem was caused by using an old version of the Apache Plugin.
This problem occurred while using the 5.1 apache plugin with WLS 6.1.
Once we realized we were using the wrong plugin and swithced to the 6.1 plugin, the
problem went away.
-
Setting up in-memory replication in WLS5.1
Hi,
How do you set up in-memory replication in WLS5.1? I mean what the weblogic.properties
and what are it's values?
Thanx
Put it in the cluster level properties file. What service pack are you using? I would recommend you use the latest (SP11)
with WLS 5.1.
Kailu wrote:
> Hi,
>
> I've set up the following properties(in the server level properties, should they
> be set up in the cluster level properties?)
>
> weblogic.httpd.clustering.enable=true
> weblogic.httpd.session.persistence=true
> weblogic.httpd.session.persistentStoreType=replicated
>
> and I'm getting the following error(does it have anything do with the settings
> in the weblogic.policy file?)
>
> Mon Mar 18 10:07:55 CST 2002:<I> <ServletContext-General> session: init
> Mon Mar 18 10:07:55 CST 2002:<E> <ServletContext-General> Servlet failed with
> Exception
> java.lang.SecurityException:
> at java.lang.Throwable.fillInStackTrace(Native Method)
> at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
> at weblogic.jndi.internal.RemoteContextFactoryImpl_WLStub.getContext(RemoteContextFactoryImpl_WLStub.java:95)
> at weblogic.jndi.WLInitialContextFactoryDelegate.newRemoteContext(WLInitialContextFactoryDelegate.java:316)
> at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(Compiled Code)
> at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(Compiled
> Code)
> at weblogic.jndi.Environment.getContext(Compiled Code)
> at weblogic.jndi.Environment.getInitialContext(Compiled Code)
> at weblogic.cluster.replication.ReplicationManager.getRepMan(ReplicationManager.java:363)
> at weblogic.cluster.replication.ReplicationManager.createSecondary(Compiled
> Code)
> at weblogic.cluster.replication.ReplicationManager.register(ReplicationManager.java:617)
> at weblogic.servlet.internal.session.ReplicatedSession.<init>(ReplicatedSession.java:106)
> at weblogic.servlet.internal.session.ReplicatedSessionContext.getNewSession(ReplicatedSessionContext.java:50)
> at weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(SessionContext.java:349)
> at weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImpl.java:1307)
> at weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.java:1199)
> at examples.servlets.SessionServlet.doGet(SessionServlet.java:51)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:106)
> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:907)
> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:851)
> at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:252)
> at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:364)
> at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:252)
> at weblogic.kernel.ExecuteThread.run(Compiled Code)
>
> "Kailu" <[email protected]> wrote:
> >
> >Hi,
> >
> >How do you set up in-memory replication in WLS5.1? I mean what the weblogic.properties
> >and what are it's values?
> >
> >Thanx
Rajesh Mirchandani
Developer Relations Engineer
BEA Support
-
NullPointerException when doing in-memory-replication
I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
multi-home NT box, but when I tried to use in memory replication with adding
the the following three properties:
weblogic.httpd.clustering.enable=true
weblogic.httpd.session.persistence=true
weblogic.httpd.session.persistentStoreType=replicated
I got the exception below. if I removed the session.persistence and
session.persistentStoreType properties, the request will go through and both
instance can serve request, but I lost the session information in fail over.
Any hints will be appreciated!
Qingxiang
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.index._jspService(index.java:105)
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(ExecuteThread.java:120)
I forgot to add that I am running WLS5.1 with sp3.
"Qingxiang Ke" <[email protected]> wrote in message
news:[email protected]...
> I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
> multi-home NT box, but when I tried to use in memory replication with
adding
> the the following three properties:
>
> weblogic.httpd.clustering.enable=true
> weblogic.httpd.session.persistence=true
> weblogic.httpd.session.persistentStoreType=replicated
>
> I got the exception below. if I removed the session.persistence and
> session.persistentStoreType properties, the request will go through and
both
> instance can serve request, but I lost the session information in fail
over.
>
> Any hints will be appreciated!
>
> Qingxiang
>
> 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.index._jspService(index.java:105)
> 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(ExecuteThread.java:120)
>
>
>
-
In memory replication not working
We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
but this is in a production system and it usually takes a guarantee that
a change will fix a bug before being allowed).
We are clustering two weblogic servers.
In our test systems everything works great.
In our production systems, failover works, but not in memory
replication. With the replication debugging output turned on I see the
following output:
<WebLogicServer> WebLogic Server started
<RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
(I should point out that this RJVM message only appears on one of the
servers, appears whether or not the other server is running, and
10.100.35.80 is not the IP address of the other server nor of this
server.)
(Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
When a user connects and a session is created, we see the following:
<RepMan>Unable to create secondary for XXXXXXX
<RepMan>Registered XXXXXX
<RepMan>Get Secondary JVMID returning null for XXXXXXX
<RepMan>updateSecondary called on unpaired primary
<RepMan>lookup found for XXXXXX
The second server never outputs any new information.
It's not the code, this works in test, and we have poured over the
configuration, and all configuration files look correct.
The MulticastTest also works in the production system.
Any ideas?
Looks like they are not in cluster..
double check the configuration and check in weblogic console whether you see both servers under the cluster name...
Robert Antonucci <[email protected]> wrote:
>We are using Weblogic 4.5.1 SP5 (I know that is an old service pack -
>but this is in a production system and it usually takes a guarantee that
>a change will fix a bug before being allowed).
>
>We are clustering two weblogic servers.
>In our test systems everything works great.
>In our production systems, failover works, but not in memory
>replication. With the replication debugging output turned on I see the
>following output:
>
><WebLogicServer> WebLogic Server started
><RJVM> Creating connection to 10.100.35.90/10.100.35.80 ...
>(I should point out that this RJVM message only appears on one of the
>servers, appears whether or not the other server is running, and
>10.100.35.80 is not the IP address of the other server nor of this
>server.)
>(Note, it never prints the typical <RepMan>Adding XXXXXX to the cluster)
>
>When a user connects and a session is created, we see the following:
>
><RepMan>Unable to create secondary for XXXXXXX
><RepMan>Registered XXXXXX
><RepMan>Get Secondary JVMID returning null for XXXXXXX
><RepMan>updateSecondary called on unpaired primary
><RepMan>lookup found for XXXXXX
>
>The second server never outputs any new information.
>
>It's not the code, this works in test, and we have poured over the
>configuration, and all configuration files look correct.
>The MulticastTest also works in the production system.
>
>Any ideas?
>
-
In memory replication doesn't seem to work
We have set up a Cluster with 2 servers. Our Proxy server is NES. We can
see the round robin working but each time we are accessing the session,
the same cookie gets overriden (the browser receives the WebLogicSession
cookie from the weblogic servers) .... Loosing all the information..
Is this a WebLogic bug ?
Olivier
[olivier.vcf]
I don't think it goes in the xml file. It should be in weblogic.properties file
weblogic.httpd.session.cookie.name=foo
-- Prasad
John wrote:
> Could you tell me how I can set up the cookie in web.xml to override the WeblogicSession cookie?
>
> "Yogi Mudras" <[email protected]> wrote:
> >Is SP6 out yet ?
> >
> >
> >"Olivier Brand" <[email protected]> wrote in message
> >news:[email protected]...
> >> BEA told me that the Session bug will be fixed in SP7.
> >>
> >> Otherwise, the in-memory replication is working fine. During our stress
> >test, we got
> >> some exceptions.
> >>
> >> When we are using in-memory replicaiton, should all the objects put in the
> >HttpSession
> >> be Serializable ? My guess is that they have to be.
> >>
> >> Olivier
> >>
> >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(Compiled
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession
> >(Compiled
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
> >teSessions(Compiled
> >>
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
> >Compiled
> >> Code)
> >> at
> >> weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
> >> Code)
> >> at
> >> weblogic.time.common.internal.ScheduledTrigger.execute(Compiled Code)
> >> at weblogic.time.server.ScheduledTrigger.execute(Compiled Code)
> >> at weblogic.kernel.ExecuteThread.run(Compiled Code)
> >>
> >> weblogic.cluster.replication.NotFoundException: remove unable to find
> >> object 7173403347807782043
> >> at java.lang.Throwable.fillInStackTrace(Native Method)
> >> at java.lang.Throwable.fillInStackTrace(Compiled Code)
> >> at weblogic.rmi.extensions.AbstractRequest.sendReceive(Compiled
> >> Code)
> >> at
> >> weblogic.cluster.replication.ReplicationManager_WLStub.remove(Compiled
> >> Code)
> >> at
> >> weblogic.cluster.replication.ReplicationManager.unregister(Compiled
> >> Code)
> >> at
> >> weblogic.servlet.internal.session.ReplicatedSession.invalidate(Compiled
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.ReplicatedSessionContext.invalidateSession
> >(Compiled
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.invalida
> >teSessions(Compiled
> >>
> >> Code)
> >> at
> >>
> >weblogic.servlet.internal.session.SessionContext$SessionInvalidator.trigger(
> >Compiled
> >> Code)
> >> at
> >> weblogic.time.common.internal.ScheduledTrigger.executeLocally(Compiled
> >> Code)
> >>
> >> Prasad Peddada wrote:
> >>
> >> > Olivier Brand wrote:
> >> >
> >> > > In fact, nothing is impossible since there is a HUGE bug in WebLogic
> >and the
> >> > > sessions. This bug has been (and still is) filed under the following
> >number:
> >> > > CR033896.
> >> > > I have noticed that if you have two different web app, if you contact
> >a
> >> > > servlet in app 1 and a servlet in app 2 (2 different contexts), the
> >same
> >> > > cookie: WebLogicSession, is being overriden !!
> >> > > The workaround is to override in the web.xml the name of the session.
> >> >
> >> > Do you have problems even with the suggested workaround?
> >> >
> >> > > I got the sticky load balancing back in placing the CookieName
> >argument in the
> >> > > NES proxy (app1 and app2). This way the proxy can identify what
> >application
> >> > > server to contact depending on the requestor's cookie.
> >> > >
> >> > > I am still noticing the loss of the session when using the failover:
> >> > >
> >> > > I stop app server A, app1 is switched to app server B but recreate the
> >same
> >> > > cookie with a different value. I thought that in-memory replication
> >was...
> >> > > replicating. Does it mean that only the DB persistency (or file system
> >if
> >> > > using NFS of course) can work in a failover scenario ?
> >> >
> >> > When you failover to server B the cookie will change. The behavior is
> >correct, but
> >> > do you see loss of session data. Is it possible to post the cookies
> >before and
> >> > after failover.
> >> >
> >> > - Prasad
> >> >
> >> > >
> >> > > Olivier
> >> > >
> >> > > Prasad Peddada wrote:
> >> > >
> >> > > > Olivier Brand wrote:
> >> > > >
> >> > > > > We have set up a Cluster with 2 servers. Our Proxy server is NES.
> >We can
> >> > > > > see the round robin working but each time we are accessing the
> >session,
> >> > > > > the same cookie gets overriden (the browser receives the
> >WebLogicSession
> >> > > > > cookie from the weblogic servers) .... Loosing all the
> >information..
> >> > > >
> >> > > > What do you mean by overriden? That's not possible. Could you post
> >the two
> >> > > > sessions ids.
> >> > > >
> >> > > > - Prasad
> >> > > >
> >> > > > >
> >> > > > > Is this a WebLogic bug ?
> >> > > > >
> >> > > > > Olivier
> >> >
> >> > --
> >> > Cheers
> >> >
> >> > - Prasad
> >>
> >
> >
-
How much does in-memory replication boost txn rates?
I posted the note below on the weblogic.developer.interest.clustering" list.
As a supplement to that question, I'm wondering how much of a boost to
transaction rates that anyone sees from using in-memory replication with
WebLogic?
=====================
How many peak/average transactions per second is anyone pushing through
WebLogic? With what response time? On what version of WebLogic? With what
sort of a configuration?
If you don't have transactions per second, any other measures of performance
and scalability would be interesting.
Randy Heffner
Giga Information Group
Mike -
Thanks for the reply -- I phrased my question poorly. What I intended was
this:
- Compared to saving context to disk (so that it is accessible across
servers in a cluster), how much does in-memory replication boost transaction
throughput rates?
I'm just wondering if anyone has measured the difference in their
environment.
Randy
"Mike Reiche" <[email protected]> wrote in message
news:[email protected]...
>
> Boost transaction rates? No - it degrades transaction rates. Replicating
data is
> extra work.
>
> Mike
>
> "Randy Heffner" <[email protected]> wrote:
> >I posted the note below on the weblogic.developer.interest.clustering"
> >list.
> >As a supplement to that question, I'm wondering how much of a boost to
> >transaction rates that anyone sees from using in-memory replication with
> >WebLogic?
> >
> >=====================
> >How many peak/average transactions per second is anyone pushing through
> >WebLogic? With what response time? On what version of WebLogic? With
> >what
> >sort of a configuration?
> >
> >If you don't have transactions per second, any other measures of
performance
> >and scalability would be interesting.
> >
> >Randy Heffner
> >Giga Information Group
> >
> >
> >
> >
>
-
Database engine services and sql server replication failed in installation
hi im trying to setup sql server on my laptop but it says the 'database engine services' and 'sql server replication' have failed due to some specified module being missing can anyone help me out?
log file:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2147467259
Start time: 2015-03-17 10:47:47
End time: 2015-03-17 11:08:11
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: SHARI
Machine processor count: 2
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1033 Express Edition 10.1.2531.0 No
SQL Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication
1033 Express Edition 10.1.2531.0 No
SQL Server 2012
Management Tools - Basic 1033 Express Edition
11.0.2100.60 No
SQL Server 2012
LocalDB 1033
Express Edition 11.0.2100.60 No
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
SPLevel: 0
Installation location: c:\efa3a640a9b59ee651913f55719bf3b1\x86\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Manual
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: true
FEATURES: SQLENGINE, REPLICATION
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: c:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: c:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: SHARIINSTANCE
INSTANCENAME: SHARIINSTANCE
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SHARIINSTANCE
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: SHARI\Shari Donald
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: true
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20150317_104244\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The specified module could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xEC717F7D%400xC24842DB&EvtType=0xEC717F7D%400xC24842DB
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x80004005
Error description: The specified module could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xEC717F7D%400xC24842DB&EvtType=0xEC717F7D%400xC24842DB
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20150317_104244\SystemConfigurationCheck_Report.htmHello,
As per the log details shared, installing version is SQL server express. Please go to control panel - add and remove programs and uninstall the
SQL Server Database Engine Services Instance Features, and also Uninstall all SQL Services.
Reboot and start the start the installation with RUN as Administrator.
Thank You.
Regards, Pradyothana DP. Please Mark This As Helpful if it helps to solve your issue. ========================================================== http://www.dbainhouse.blogspot.in/ -
3rd party distributed SW load balancing with In-Memory Replication
Hi,
Could someone please comment on the feasibility of the following setup?
I've started testing replication with a software load balancing product. This
product lets all nodes receive all packets and uses a kernel-level filter
to let only one node at the time receive it. Since there's minimum 1 heartbeat
between the nodes, there are several NICs in each node.
At the moment it seems like it doesn't work: - I use the SessionServlet - with
a 2-node cluster I first have the 2 nodes up and I access it with a single client:
.the LB is configured to be sticky wrt. source IP address, so the same node gets
all the traffic - when I stop the node receiving the traffic the other node takes
over (I changed the colours of SessionServlet) . however, the counter restarts
at zero
From what I read of the in-memory replication documentation I thought that it
might work also with a distributed software load balancing cluster. Any comments
on the feasability of this?
Is there a way to debug replication (in WLS6SP1)? I don't see any replication
messages in the logs, so I'm not even sure that it works at all. - I do get a
message about "Clustering Services startting" when I start the examples server
on each node - is there anything tto look for in the console to make sure that
things are working? - the evaluation license for WLS6SP1 on NT seems to support
In-Memory Replication and Cluster. However, I've also seen a Cluster-II somewhere:
is that needed?
Thanks for your attention!
Regards, Frank Olsen
We are considering Resonate as one of the software load balancer. We haven't certified
them yet. I have no idea how long its going to take.
As a base rule if the SWLB can do the load balancing and maintain stickyness that is fine
with us as long as it doesn't modify the cookie or the URL if URL rewriting is enabled.
Having said that if you run into problems we won't be able to support you since it is not
certified.
-- Prasad
Frank Olsen wrote:
> Prasad Peddada <[email protected]> wrote:
> >Frank Olsen wrote:
> >
> >> Hi,
> >>
> > We don't support any 3rd party software load balancers.
>
> Does that mean that there are technical reasones why it won't work, or just that
> you haven't tested it?
>
> > As >I said before I am thinking your configuration is >incorrect if n-memory
> replication is not working. I would >strongly suggest you look at webapp deployment
> descriptor and >then the config.xml file.
>
> OK.
>
> >Also doing sticky based on source ip address is not good. You >should do it based
> on passive cookie persistence or active >cookie persistence (with cookie insert,
> a new one).
> >
>
> I agree that various source-based sticky options (IP, port; network) are not the
> best solution. In our current implementation we can't do this because the SW load
> balancer is based on filtering IP packets on the driver level.
>
> Currently I'm more interested in understanding whether it can our SW load balancer
> can work with your replication at all?
>
> What makes me think that it could work is that in WLS6.0 a session failed over
> to any cluster node can recover the replicated session.
>
> Can there be a problem with the cookies?
> - are the P/S for replication put in the cookie by the node itself or by the proxy/HW
> load balancer?
>
> >
> >The options are -Dweblogic.debug.DebugReplication=true and
> >-Dweblogic.debug.DebugReplicationDetails=true
> >
>
> Great, thanks!
>
> Regards,
> Frank Olsen
-
Evaluation license for ejb-in-memory-replication!!!
Hi,
Has anyone tried using in-memory replication for a stateful-session bean in the evaluation
copy of WebLogic 6.0 ? I have a simple stateful session bean with <replication-type>InMemory</replication-type>
set in weblogic-ejb-jar.xml. But when I try to generate a deployable jar file, I
get the following message,
% java weblogic.ejbc -compiler jikes std_simple_stateful.jar simple_stateful.jar
Couldn't find a license for in-memory replication of EJB's, this feature is disabled
<Jan 31, 2001 1:40:21 PM EST> <Info> <EJB> <Couldn't find a license for in-memory
replication of EJB's, this feature is disabled>
The license file seems to have the product enabled.
any suggestions ???
thanx in advance
-Ram
[email protected]
Make sure the license is in ejbc's classpath.
We fixed this for SP1 to make it so ejbc will always compile regardless
of your license. The actual license check occurs when you deploy the
bean.
-- Rob
Ram Munjuluri wrote:
>
> Hi,
>
> Has anyone tried using in-memory replication for a stateful-session bean in the evaluation
> copy of WebLogic 6.0 ? I have a simple stateful session bean with <replication-type>InMemory</replication-type>
> set in weblogic-ejb-jar.xml. But when I try to generate a deployable jar file, I
> get the following message,
>
> % java weblogic.ejbc -compiler jikes std_simple_stateful.jar simple_stateful.jar
> Couldn't find a license for in-memory replication of EJB's, this feature is disabled
> <Jan 31, 2001 1:40:21 PM EST> <Info> <EJB> <Couldn't find a license for in-memory
> replication of EJB's, this feature is disabled>
>
> The license file seems to have the product enabled.
>
> any suggestions ???
>
> thanx in advance
> -Ram
> [email protected]
Coming Soon: Building J2EE Applications & BEA WebLogic Server
by Michael Girdley, Rob Woollen, and Sandra Emerson
http://learnweblogic.com
-
Defeating In Memory Replication
I have some questions about in memory servlet session replication in
weblogic 5.1 clusters. It seems to me rather easy to create a scenario
where the session is lost. While the servers in a cluster do a good job
maintaining session state within the cluster while machines leave and
join the cluster, the web server proxy in front of the cluster relies on
state (a cookie) from the client to find the cluster server that has the
session state. There is no way for the cluster servers to stay in sync
with client cookies if the client make infrequent requests.
I hope that someone can tell me that I am wrong but please consider the
following scenario.
There is a cluster made up of 5 servers.
There is one weblogic web server acting as the proxy in front of the
cluster.
A web browser makes connection #1 and causes the creation of SessionA.
Server1 is the primary node for the session, Server2 is the backup.
Server1 is taken out of service. Server2 is now the primary, Server3 is
the backup.
Server2 is taken out of service. Server3 is now the primary, Server4 is
the backup.
The web browser makes connection #2. Its cookie refers to Server1 as
the primary and Server2 as the backup. This cookie state is stale, the
proxy server does not know where to go and the session created in
connection #1 is lost.
Am I right? Will this scenario lose the session?
- Kevin
Kevin McEntee wrote:
> Interesting, see my comments below.
>
> Prasad Peddada wrote:
> >
> > Kevin McEntee wrote:
> >
> > > I have some questions about in memory servlet session replication in
> > > weblogic 5.1 clusters. It seems to me rather easy to create a scenario
> > > where the session is lost. While the servers in a cluster do a good job
> > > maintaining session state within the cluster while machines leave and
> > > join the cluster, the web server proxy in front of the cluster relies on
> > > state (a cookie) from the client to find the cluster server that has the
> > > session state. There is no way for the cluster servers to stay in sync
> > > with client cookies if the client make infrequent requests.
> >
> > That's true. But, you don't expect the servers to go down fast either.
>
> Maybe not for errors or crashes but what about pushing new code to a
> production website? The company I work for pushes new code to the live
> internet site once per week. Typically 1/3 to 1/2 of the machines are
> taken out of service while new code is copied to the servers. These
> machines are brought back into service and more are taken out. This
> process continues until all of the machines have new code and are
> brought back into service.
>
> This is an example of a regular controlled circumstance where machines
> are taken out and brought back into a cluster.
Replication has been designed with failures in mind but not controlled
failures. We will be addressing this issue in our next release most probably.
> > > There is a cluster made up of 5 servers.
> > > There is one weblogic web server acting as the proxy in front of the
> > > cluster.
> > >
> > > A web browser makes connection #1 and causes the creation of SessionA.
> > > Server1 is the primary node for the session, Server2 is the backup.
> > > Server1 is taken out of service. Server2 is now the primary, Server3 is
> > > the backup.
> > > Server2 is taken out of service. Server3 is now the primary, Server4 is
> > > the backup.
> > > The web browser makes connection #2. Its cookie refers to Server1 as
> > > the primary and Server2 as the backup. This cookie state is stale, the
> > > proxy server does not know where to go and the session created in
> > > connection #1 is lost.
> > >
> > > Am I right? Will this scenario lose the session?
> >
> > Yes, you will lose the session information since the client didn't make
> > connection while the servers are being taken out of service. You can
> > alternatively use JDBC persistence or file persistence for this which will
> > not have the problems you mentioned.
> >
>
> This makes me wonder if anyone is depending on in-memory replication of
> servlet sessions for real data or just caching. It is so easy to defeat
> that I cannot imagine depending on it, especially given the need to
> regularly change the live site code as described in above.
Your requirements seem to be quite different what it was intended for, so I
cannot comment on this.
> Is anyone out there reading this group using in-memory replication of
> servlet sessions on a live internet site? What is your push process
> like?
>
> - Kevin
- Prasad
-
Connecting IIS6.0 to WLS Express on separate server
I've read most of the posts and followed the install guide for the IIS plugin but whatever way I have it setup I dont seem to be able to connect to my bea server
IIS on Win2003
WLS Express on Win2000
iisproxy and iisforward dlls and iisproxy.ini file are in (iis server) C:\inetpub\wwwroot
iisproxy reads
WebLogicHost=myBEAServerIp
WebLogicPort=7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WlForwardPath=/myapp.
Debug=ON
iisforward.dll added as an isapi filter
iisproxy.dll mapping added with extension of .wlforward
added iisproxy.dll and iisforward.dll as web service extensions.
also there is no log in the c:\tmp\ folder
any ideas?Skempton - Dec 14th 2004
Hi, I got this working (after some pain!!) - I think the key difference is the requirement to create Application pools in IIS6 (especially if you're redirecting to more than one website). You should not need to create Application Pools if this is for a single website redirect.
Let me know if you're still having problems
Steps below:
Based upon the following link, with some extra stuff
http://e-docs.bea.com/wls/docs81/plugins/isapi.html
For multiple products, and IIS6
Configuring IISProxy.dll for multiple websites: (IIS V6)
Step 1 Create new websites in IIS
WebSite1 (port 84)
WebSite2 (port 82)
WebSite3 (Port 86)
WebSite4 (Port 81)
WebSite5 (Port 85)
Step 2 Created new Application pools within IIS6 for the above websites
WebSite1
WebSite2
WebSite3
WebSite4
WebSite5
Step 3 Created an Isapi filter for the weblogic plugin
(put this at the top level so that it would be good for all web sites)
right click on web sites \properties
select 'isapi filters' tab
Click add, and create a link to the IISForward.dll file from BEA
Filter name = wlforward
dll file = C:\bea\weblogic81\server\bin\Hyperion\iisforward.dll (for example)
Step 4 Create a iisforward.ini file
In the same directory as the iisforward.dll file, created a iisforward.ini file with the following entries (PLEASE NOTE 'FullyQualifiedServerName> should be the actual name of the machine where IIS6 is housed):
vhost1=<FullyQualifiedServerName>:85
<FullyQualifiedServerName>:85=C:\bea\weblogic81\server\bin\Hyperion\WebSite5\iisproxy.ini
vhost2=<FullyQualifiedServerName>:82
<FullyQualifiedServerName>:82=C:\bea\weblogic81\server\bin\Hyperion\WebSite2\iisproxy.ini
vhost3=<FullyQualifiedServerName>:86
<FullyQualifiedServerName>:86=C:\bea\weblogic81\server\bin\Hyperion\WebSite3\iisproxy.ini
vhost4=<FullyQualifiedServerName>:84
<FullyQualifiedServerName>:84=C:\bea\weblogic81\server\bin\Hyperion\WebSite1\iisproxy.ini
vhost5=<FullyQualifiedServerName>:81
<FullyQualifiedServerName>:81=C:\bea\weblogic81\server\bin\Hyperion\WebSite4\iisproxy.ini
Step 5 Created the directories referenced above
WebSite5, WebSite2, WebSite3, WebSite1, WebSite4 under
C:\bea\weblogic81\server\bin\Hyperion\..
and copied the iisproxy.dll and iisforward.dll files into each of the directories
Step 6 Created a iisproxy.ini file in each directory
(example for WebSite2)
WlForwardPath=/website2URL
WebLogicHost=<FullyQualifiedServerName>
WebLogicPort=8200
Create one for each product, in the relevent folder
Step 7 Create an application extension for each product 'website'
(e.g. for WebSite2)
right click on the 'WebSite2' website
select 'properties'
select 'home directory'
click on 'configuration'
click add
extention = wlforward
executable = C:\bea\weblogic81\server\bin\Hyperion\WebSite2\iisproxy.dll
MAKE SURE THAT 'check file exists' is NOT selected
repeat this procedure for all products
You should now be able to hit the products directly via IIS
http://<FullyQualifiedServerName>:82/WebSite2URL
http://<FullyQualifiedServerName>:85/WebSite5URL
etc
Maybe you are looking for
-
FRM-47023: No such parameter named PAR1 exists in form
I have a form PARAMETER_PASSING with a command button On the button pressed trigger i have the following code DECLARE parList ParamList; parListName VARCHAR2(30):='tempParameterList'; BEGIN parList:=Create_Parameter_List(parListName);
-
Delete planning function in plan workbook
I had one query about how the deletion function should be used in plan workbook. in the plan workbook, the user would like to be able to delete the selected line / combination from plan workbook and plan cube. The options what I come up with is : 1.
-
Include posting date in interest computation
Hi, we have a payment term of 07DA (due on the 7th of billed month) If a document is posted on the first day of the month, then is it payable on the 7th. If the customer did not pay on the 7th, it will computed with interest. The standard is, interes
-
Alert with event for delayed job and long execution time
Dear All, We are planning to send alert via email in case job delayed or long execution time. I have followed below steps: 1) Create event Raise Event when job is delayed. 2) create job chain with STEP1, Job 1 and assign event in raise event paramete
-
Hi Gurus, I have multi-level assembly ,in which some of the BOM components are text items. In tcode CSMB- BOM product structutre display the text items are not shown. I tried to change the layout,but could not figure it out. Is there is