Servlet load balancing
I am testing load balancing of servlet on Weblogic 6.0 with Netscape
Enterprise Server 3.6. I can hit both weblogic servers if I try to hit
them heavily. However no matter what I do I can not get the round robin
work.
Has any one got load balancing work for servlets with 3rd party web
server? As I understand weblogic only supports round robin for servlets
load balancing because of DNS rotatioin, am I right?
Thanks,
Yong
Yes. I even see this behavior from clients on different hosts.
Yong
"Kumar Allamraju" <[email protected]> wrote:
>round-robin happens for new requests, not for the existing requests.
>Are you seeing the following behaviour with new clients (i.e. sending
>requests from different browsers)..
>
>--
>Kumar
>
>"Yong Sun" <[email protected]> wrote in message
>news:[email protected]..
>> I am testing load balancing of servlet on Weblogic 6.0 with Netscape
>> Enterprise Server 3.6. I can hit both weblogic servers if I try to
>hit
>> them heavily. However no matter what I do I can not get the round
>robin
>> work.
>>
>> Has any one got load balancing work for servlets with 3rd party web
>> server? As I understand weblogic only supports round robin for servlets
>> load balancing because of DNS rotatioin, am I right?
>>
>> Thanks,
>>
>>
>> Yong
>>
>>
>
>
Similar Messages
-
Load balancing for JSPs and servlets
Hi:
I am using IIS as the proxy server, with the WLS plug-in, to a WLS
cluster. This provides round robin load balancing just fine. Will it
provide weight based load balancing if I set 'weblogic.system.weight'
differently on each server, or is that not relevant for clustering JSPs
and servlets?
Sincerely,
Ashish
Currently the plugins ( for NES, IIS and Apache) just use the round robin
algorithm. the property
weblogic.system.weight is used only be weblogic's replica aware clusterable
RMI/EJB stubs.
To use this property for your JSP/Servlet load balancing you have to use
weblogic server as proxy fron-ending your weblogic cluster.
--Viresh Garg
Ashish Vimal wrote:
> Hi:
> I am using IIS as the proxy server, with the WLS plug-in, to a WLS
> cluster. This provides round robin load balancing just fine. Will it
> provide weight based load balancing if I set 'weblogic.system.weight'
> differently on each server, or is that not relevant for clustering JSPs
> and servlets?
> Sincerely,
> Ashish
-
Load Balancing Problem with WLS6.1
Hi,
I have 4 Instances of Weblogic servers two instance per box with Clustered. The
admin server is running in the first box. While stress testing it seems all the
loads are going to one instance and other instances are almost idle.
In the Secondary Group, i have given the name of the other instance on the same
server. I'm running weblogic in Solaris with SP3.
Can anyone suggest why loadbalancing doesn't work.
Typically, load balancing will work unless there is a problem with the
clusters seeing each other. Therefore first make sure that the managed
server has joined the cluster.
Other things to look at are the __WebLogicBridgeConfig (see WLS plugin
documents) to confirm that there is a primary and secondary.
The above assumes Servlet load balancing, for objects check the
deployment descriptors.
Diwan Mohideen wrote:
>
> Hi,
>
> I have 4 Instances of Weblogic servers two instance per box with Clustered. The
> admin server is running in the first box. While stress testing it seems all the
> loads are going to one instance and other instances are almost idle.
>
> In the Secondary Group, i have given the name of the other instance on the same
> server. I'm running weblogic in Solaris with SP3.
>
> Can anyone suggest why loadbalancing doesn't work.
-
Ias support for EJB, JSP/servlets,JDBC, connection pooling, XML, SOAP, load balancing etc
Please let me know where I can find more information regarding iPlanet usage/deployment/configuring/tuning etc for support of technologies - like EJB, JSP/servlets, JDBC, connection pooling, XML, load balancing, JDBC & Transactions
(I have already read the 'Getting Started with the iPlanet Application Server' part five and six - http://developer.iplanet.com/appserver/testdrive/partfive.jsp and partsix.jsp)(I am using the ias testdrive version).Hi,
It's difficult to explain unless the J2EE architecture is understood. Also, explaining things like load balancing, Transactions, tuning, are bit vague and could blow the disk space of this site.
To get started, the best way is to test the sample applications and the best part is you don't require internet connection to follow each steps. Install iWS and iAS, open browser, type in http://hostname:port/ias-samples/index.html. You can find links to the sample applications bundled. Please follow the steps given on deploying the application. This will enable you to a higher level.
Regards
Ganesh .R
Developer Technical Support
Sun Microsystems
http://www.sun.com/developers/support -
How can I support a health check, from a load balancer?
My company has load balancers which use health checks to determine if the end point is available for client traffic. The basic health check is a tcp ping, and will tell you if the device is on the network. The next level of health check is an http request. This request, and the response are static, you can’t create your own version of the request and response. The standard request is this:
http://host:port/healthcheck/hc.html
The standard response is this:
“The server is available”
I want to use the load balancer as part of my total deployment. The problem is that I am not seeing how to support this health check request and response in the MDEX engine. What I see is this request
http://host:port/admin?op=ping
Will return this response
dgraph <host>: <port> responding at <day month year time>
It is nice that there is a built in ping, but I am not able to make use of it. I am new to Endeca and still poking around. The dgraph process listens on a port set up in <…>/config/script/AppContext.xml
<dgraph id="Dgraph1" host-id="MDEXHost" port="3281">
<properties>
<property name="restartGroup" value="A" />
<property name="updateGroup" value="a" />
</properties>
<log-dir>./logs/dgraphs/Dgraph1</log-dir>
<input-dir>./data/dgraphs/Dgraph1/dgraph_input</input-dir>
<update-dir>./data/dgraphs/Dgraph1/dgraph_input/updates</update-dir>
</dgraph>
(I am not using the default port, as I only have an instance on a shared server and have to worry about port clashing. But that is a different thread.)
In a standard tc Server install I can support this health check by doing this:
* Create a directory named “healthcheck”, in the “webapps” directory.
* Place a file name “hc.html” in that directory, which contains “The server is available”
The one hack which comes to mind is to write a servlet which would be able to be a smart proxy for the load balancer health check. It would pass along any regular traffic to the MDEX engine. But if the request was a health check it would send “admin?op=ping” to the MDEX engine, and for a good response from the engine, create and pass back the correct response to the load balancer.
Ideas, comments, flames, …
ThanksHi, we are using following String to test the MDEX ping response but we get the invalid version formation on dgraph.log -
following is on F5
GET /admin?op=ping HTTP/1.1/r/nHost:myhost.endeca.com:19000/r/nConnection:close/r/n/r/n
Following gets logged on Dgraph.log
WARN 09/05/12 05:30:03.799 UTC (1346823003799) DGRAPH {dgraph} Invalid version format in 'HTTP/1.1/r/nHost:myhost.endeca.com:19000/r/nConnection:close/r/n/r/n'
Please let me know - if you have any suggestions to solve this issue.
I know that it works from browser and wget from unix with following commands.
wget http://myhost.endeca.com:19000/admin?op=ping - from unix command line
from browser:
http://myhost.endeca.com:19000/admin?op=ping
Thanks,
Ram -
ACE load-balancing-Cookie problem
In our other load-balancing environments the load-balancer-cookie contains the encrypted (real) servername or ip-address.
We think it's the same on the cisco, for that reason it's in theory not possible, that there are two 'green'-cookies with different values in the same request.
There are only two possibilities how this could happen:
a) The healthmonitor (http_probe) fails, the loadbalancer 'thinks' that the realserver is down and redistributes the traffic.
But in that case we would expect, that the old cookie will be overwritten by the new one and not simply added to the http-header.
b) The predictor in the serverfarm chooses a new realserver within the same request.
If that is really the cause of that problem this would be bug in the cisco ace.
What we found out, is that the loadbalancer performs a 'Set-Cookie'-Operation an every request even if the client submits the cookie correctly.
For example:
GET /ips-opdata/scripts/jquery.js HTTP/1.1
Host: www.xxxxx.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110303 Ubuntu/10.04 (lucid) Firefox/3.6.15
Accept: */*
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Referer: http://www.xxxxx.com/
Cookie: green=R339366665; JSESSIONID=28D91FC6FD62A3921354BB36826294C4
HTTP/1.1 200 OK
Set-Cookie: green=R339366665; path=/; expires=Tue, 29-Mar-2011 06:33:00 GMT
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5
ETag: W/"72181-1298537508000"
Last-Modified: Thu, 24 Feb 2011 08:51:48 GMT
Content-Type: text/javascript
Content-Length: 72181
Date: Mon, 28 Mar 2011 06:15:19 GMT
As you can see the cookies: green=R339366665 is transmitted from the client, but the loadbalancer does a Set-Cookie Operation of the same cookie once again. This is an unexpected behaviour.
We hope that this helps you to figure out the reason of the problem.The cookie is sent by the ACE on each response to refresh the timeout value on the client. The value of the cookie doesn't change. This is the expected behaviour and shouldn't break anything in the application / browser.
For browser-based applications, don't forget to add the "browser-expire" parameter to your cookie-based stickyness config. -
I am supporting an app server for a Forms & Reports application that uses run_report_object to run reports on a Reports Server. This is on 10gR2 (10.1.2.0.2) on Solaris & Linux.
Currently running multiple standalone Reports Servers on a single server (for 3 different projects). Need to prevent one project from affecting another as much as possible (yes, I know they are on the same box....).
I have a requirement to ensure that a hanging Reports Server doesn't prevent other jobs from running. I see that Reports Server clustering is no longer an option. The Reports documentation about how to implement HA basically say just read the AS docs and figure it out. The problem is that using the AS J2EE HA means that you'd HAVE to use the Reports Servlet. Additionally, I don't see how the reports servlet could be called so that more than one Reports server would be used.
I keep hearing about an impending doc about implementing HA on Reports. When is it coming?
Future environments will be multiple AS installs on separate boxes accessing a RAC DB.
So, what's the scoop? How can I implement this?
So, here are my questions:
1. (Two Servers) I believe I could do this on two servers if I had the same Reports Server name on each. If so, could I have two OC4J containers on each server both with the same mount point for the rwservlet application? What else would I need to do to tell OHS to load balance between both since they have the same name.
2. (Two Servers) If 1 above is okay, would it be possible to have two OC4J containers point to two different standalone Reports Servers?
3. (One Server) Can I start up multiple Reports Servers on same box with the same name (I'm pretty sure this is no :-) )
4. (One Server) Like 2 above except on a single server. Two independent OC4J containers accessing two different servlets. Each has a default Reports Server setup. URL would look the same from each.
I'm kind of graping for straws here on how to move ahead. I'm surprised the Reports Server clustering was taken away, but I suspect it is because the underlying Visibroker architecture was changed and there weren't the resources required to redo this. I'm not sure that is a good thing.
Any help would be appreciated.
:-) SteveSay you have two servers where you configured Reports, i.e. either in full Enterprise Edition or in AS10g Forms&Reports standalone.
For example:
ServerA.oracle.com with port 7777
ServerB.oracle.com with port 7777
Without using a load balancer you would call a Report with:
http://ServerA.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
http://ServerB.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
Now you put a load balancer in front of them and assign it the virtual name:
reports.oracle.comNow you can call Reports with this URL:
http://reports.oracle.com:7777/reports/rwservlet?report=test.rdf&userid=scott/tiger@orcl&destype=cache&desformat=htmlcss
To make it more interesting you create a specific Reports Server on ServerA called repserver_a and on ServerB: repserver_b. You add them into Enterprise Manager with:
$OH/bin/addNewServerTarget.sh repserver_a (on ServerA and with repserver_b on ServerB). You might need to reload opmnctl and emctl with:
opmnctl reload
emctl reloadIn $OH/reports/conf you add this line at the end (use server=repserver_b on ServerB) :
reporting: userid=scott/tiger@orcl destype=cache desformat=htmlcss server=repserver_a %* You'll call your Reports with this URL:
http://reports.oracle.com:7777/reports/rwservlet?reporting&report=test.rdf
Good luck!
Martin -
Load Balancing Directory Servers with Access Manager - Simple questions
Hi.
We are in the process of configuring 2 Access Manager instances (servers) accessing the same logical LDAP repository (comprising physically of two Directory Servers working together with Multi-Master Replication configured and tested) For doing this, we are following guide number 819-6258.
The guide uses BigIP load balancer for load balancing the directory servers. However, we intend to use Directory Proxy Server. Since we faced some (unresolved) issues last time that we used DPS, there are some simple questions that I would be very grateful to have answers to:
1. The guide, in section 3.2.10 (To configure Access Manager 1 with the Directory Server load balancer), talks about making changes at 4 places, and replacing the existing entry (hostname and port) with the load balancer's hostname and port (assuming that the load balancer has already been configured). It says that changes need not be made on Access Manager 2 since the LDAPs are in replication, and hence changes will be replicated at all places. However, the guide also states that changes have to be made in two files, namely AMConfig.properties, and the serverconfig.xml file. But these changes will not be reflected on Access Manager 2, since these files are local on each machine.
Question 1. Do changes have to be made in AMConfig.properties and serverconfig.xml files on the other machine hosting Access Manager 2?
Question 2: What is the purpose of putting these values here? Specifically, what is achieved by specifying the Directory server host and port in AMConfig.properties, as well as in serverconfig.xml?
Question 3. In the HTTP console, there is the option of specifying multiple primary LDAP servers, as well as multiple secondary LDAP servers. What is the purpose of these? Are secondary servers attempted when none of the list in the primary list are accessible? Also, if there are multiple entries in the primary server list, are they accessed in a round robin fashion (hereby providing rudimentary load balancing), or are other servers accessed only when the one mentioned first is not reachable etc.?
2. Since I do not have a load balancer setup yet, I tried the following deviation to the above, which, according to me, should have worked. If viewed in the HTTP console, LDAP / Membership / MSISDN and Policy configuration all pointed to the DS on host 1. When I changed all these to point to the directory server on host 2 (and made AMConfig.properties and serverconfig.xml on host 1 point to DS of host 2 as well), things should have worked fine, but apparently Access manager 1 could not be started. Error from Webserver:
[14/Aug/2006:04:30:36] info (13937): WEB0100: Loading web module in virtual server [https-machine_1_FQDN] at [search]
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Exception in thread "EventService" java.lang.ExceptionInInitializerError
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.iplanet.services.ldap.event.EventServicePolling.run(EventServicePolling.java:132)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at java.lang.Thread.run(Thread.java:595)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: Caused by: java.lang.InterruptedException
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: at com.sun.identity.sm.ServiceManager.<clinit>(ServiceManager.java:74)
[14/Aug/2006:04:31:48] warning (13937): CORE3283: stderr: ... 2 more
In effect, AM on 1 did not start. On rolling back the changes, things again worked like previously.
Will be really grateful for any help / insight / experience on dealing with the above.
Thanks!Update to the above, incase anyone is reading:
We setup a similar setup in Windows, and it worked. Here is a detailed account of what was done:
1. Host 1: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST1:389)
2. Host 2: Start installer, install automatically, chose Directory server, Directory Administration server, Directory Proxy server, Web server, Access Manager.
All installed, and worked fine. (AMConfig.properties, serverconfig.xml, and the info in LDAP service, all pointed to HOST2:389)
3. Host 1: Started replication. Set to Master
4. Host 2: Started replication. Set to Master
5. Host 1: Setup replication agreement to Host 2
6. Host 2: Setup replication agreement to Host 1
7. Initiated the remote replica from Host 1 ----> Host 2
Note that since default installation uses abc.....xyz as the encryption key, setting this to same was not an issue.
9. Started webserver for Host 1 and logged into AM as amadmin.
10. Added Host 2 FQDN in DNS Aliases / Realms
11. Added http://HOST2_FQDN:80 in the Platform server (instance) list.
12. Started Host 2 webserver. Logged in AM on Host 2, things worked fine.
At this stage, note the following:
a) Host 1:
AMConfig.properties file has
com.iplanet.am.directory.host=host1_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host1_FQDN" port="389" type="SIMPLE" />
b) Host 2:
AMConfig.properties file has
com.iplanet.am.directory.host=host2_FQDN
and
com.iplanet.am.directory.port=389
serverconfig.xml has:
<Server name="Server1" host="host2_FQDN" port="389" type="SIMPLE" />
c) If one logs into AM, and checks LDAP servers for LDAP / Policy Configuration / Membership etc services, they all contain Host2_FQDN:389 (which makes sense, since replica 2 was initialized from 1)
Returning back to the configuations:
13. On Host 1, login into the Admin server console of the Directory server. Navigate to the DPS, and confgure the following:
a) Network Group
b) LDAP servers
c) Load Balancing
d) Change Group
e) Action on-bind
f) Allow all actions (permit modification / deletion etc.).
g) any other configuations required - Am willing to give detailed steps if someone needs them to help me / themselves! :)
So now, we have DPS configured and running on Host1:489, and distributing load to DS1 and DS2 on a 50:50 basis.
14. Now, log into AM on Host 1, and instead of Host1_fqdn:389 (for DS) in the following places, specify Host1_fqdn:489 (for the DPS)--
LDAP Authentication
MSISDN server
Membership Service
Policy configuation.
Verified that this propagated to the Policy Configuration service and the LDAP authentication service that are already registered with the default organization.
15. Log out of AM. Following the documentation, modify directory.host and directory.port in AMConfig.properties to point to Host 1_FQDN and 489 respectively. Make this change in AMConfig.properties of both Host 1 as well as 2.
16. Edit serverconfig.xml on both hosts, and instead of they pointing to their local directory servers, point both to host1_FQDN:489
17. When you start the webserver, it will refuse to start. Will spew errors such as:
[https-host1_FQDN]: Sun ONE Web Server 6.1SP5 B06/23/2005 17:36
[https-host1_FQDN]: info: CORE3016: daemon is running as super-user
[https-host1_FQDN]: info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_04] from [Sun Microsystems Inc.]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amserver]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [ampassword]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amcommon]
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [amconsole]
[https-host1_FQDN]: warning: WEB6100: locale-charset-info is deprecated, please use parameter-encoding
[https-host1_FQDN]: info: WEB0100: Loading web module in virtual server [https-host1_FQDN] at [search]
[https-host1_FQDN]: warning: CORE3283: stderr: netscape.ldap.LDAPException: error result (32); matchedDN = dc=sun,dc=com; No such object (DN changed)
[https-host1_FQDN]: warning: CORE3283: stderr: Got LDAPServiceException code=-1
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getConnection(DSConfigMgr.java:357)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewFailoverConnection(DSConfigMgr.java:314)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewConnection(DSConfigMgr.java:253)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:184)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.services.ldap.DSConfigMgr.getNewProxyConnection(DSConfigMgr.java:194)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.initLdapPool(DataLayer.java:1248)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.(DataLayer.java:190)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:215)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ums.DataLayer.getInstance(DataLayer.java:246)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.initialize(SMSLdapObject.java:156)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ldap.SMSLdapObject.(SMSLdapObject.java:124)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
[https-host1_FQDN]: warning: CORE3283: stderr: at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance0(Class.java:350)
[https-host1_FQDN]: warning: CORE3283: stderr: at java.lang.Class.newInstance(Class.java:303)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.SMSEntry.(SMSEntry.java:216)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.identity.sm.ServiceSchemaManager.(ServiceSchemaManager.java:67)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.getServiceSchemaManager(AMClientDetector.java:219)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.am.util.AMClientDetector.(AMClientDetector.java:94)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.sun.mobile.filter.AMLController.init(AMLController.java:85)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:322)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:120)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3271)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3747)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: warning: CORE3283: stderr: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: warning: CORE3283: stderr: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: failure: WebModule[amserver]: WEB2783: Servlet /amserver threw load() exception
[https-host1_FQDN]: javax.servlet.ServletException: WEB2778: Servlet.init() for servlet LoginLogoutMapping threw exception
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:949)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]: ----- Root Cause -----
[https-host1_FQDN]: java.lang.NullPointerException
[https-host1_FQDN]: at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:921)
[https-host1_FQDN]: at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:813)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3478)
[https-host1_FQDN]: at org.apache.catalina.core.StandardContext.start(StandardContext.java:3760)
[https-host1_FQDN]: at com.iplanet.ias.web.WebModule.start(WebModule.java:251)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardHost.start(StandardHost.java:652)
[https-host1_FQDN]: at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1133)
[https-host1_FQDN]: at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:355)
[https-host1_FQDN]: at org.apache.catalina.startup.Embedded.start(Embedded.java:995)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.start(WebContainer.java:431)
[https-host1_FQDN]: at com.iplanet.ias.web.WebContainer.startInstance(WebContainer.java:500)
[https-host1_FQDN]: at com.iplanet.ias.server.J2EERunner.confPostInit(J2EERunner.java:161)
[https-host1_FQDN]:
[https-host1_FQDN]: info: HTTP3072: [LS ls1] http://host1_FQDN:58080 [i]ready to accept requests
[https-host1_FQDN]: startup: server started successfully
Success!
The server https-host1_FQDN has started up.
The server infact, didn't start up (nothing even listening on 58080).
However, if AMConfig.properties is left as it originally was, and only serverconfig.xml files were changed as mentioned above, web servers started fine, and things worked all okay. (Alright, except for some glitches when viewed in /amconsole. If /amserver/console is accessed, all is good. Can this mean that all is still not well? I am not sure).
So far so good. Now comes the sad part. When the same is done on Solaris 9, things dont work. You continue to get the above error, OR the following error, and the web server will refuse to start:
Differences in Solaris and Windows are as follows:
1. Windows hosts have 1 IP and hostname. Solaris hosts have 3 IPs and hostnames (for DS, DPS, and webserver).
No other difference from an architectural perspective.
Any help / insight on why the above is not working (and why the hell does the documentation seem so sketchy / insecure / incorrect).
Thanks a bunch! -
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 -
Can't get sticky load balancing to work
I'm really puzzled why sticky LB is not working for a simple case I'm trying. I have two simple JSP's, both registered (see web.xml and ias-web.xml below). I'm using lite session and set distributable to false. Just in case someone can tell by just looking at my session id if it's supposed to be sticky or not, it looks like following -
GXLiteSessionID-4818869464307751325
My two JSP's are also attached below, and they're pretty simple. A new session is supposed to be created in login page and clicking on the logout page invalidates the session.
What I see is that each request (whether login or logout) is randomly sent to any server. For example, if I go to login once, further request to login or logout (whether through refresh or by clicking on the link) is not necessarily sent to the same server.
Any idea what's missing in my setup? I've tried different types of load balancing (round robin, etc.) so I know that's not it.
Thanks a lot in advance.
Jitu
-----web.xml-------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN' 'http://java.sun.com/j2ee/dtds/web-app_2_2.dtd'>
<web-app>
<display-name>WebDesk</display-name>
<distributable>false</distributable>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<jsp-file>TestLogin.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogin.jsp</servlet-name>
<url-pattern>TestLogin.jsp</url-pattern>
</servlet-mapping>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<jsp-file>TestLogout.jsp</jsp-file>
</servlet>
<servlet-mapping>
<servlet-name>TestLogout.jsp</servlet-name>
<url-pattern>TestLogout.jsp</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name></realm-name>
<form-login-config>
<form-login-page></form-login-page>
<form-error-page></form-error-page>
</form-login-config>
</login-config>
</web-app>
-----ias-web.xml------
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ias-web-app PUBLIC '-//Sun Microsystems, Inc.//DTD iAS Web Application 1.0//EN' 'http://developer.iplanet.com/appserver/dtds/IASWebApp_1_0.dtd'>
<ias-web-app>
<servlet>
<servlet-name>TestLogin.jsp</servlet-name>
<guid>{A6D6B277-288D-1C22-C3CA-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<servlet>
<servlet-name>TestLogout.jsp</servlet-name>
<guid>{B88B7D19-28B9-1C22-EE63-0800209A2F7C}</guid>
<servlet-info>
<sticky>true</sticky>
<sticky-lb>true</sticky-lb>
</servlet-info>
</servlet>
<session-info>
<impl>lite</impl>
<timeout-type>last-access</timeout-type>
<timeout>60</timeout>
<secure>false</secure>
<domain></domain>
<path>/</path>
<scope></scope>
</session-info>
</ias-web-app>
-----TestLogin.jsp-------
<%
java.util.Date date = new java.util.Date();
HttpSession sess = request.getSession(true);
System.out.println(date + ":TestLogin.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogin</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
You are now logged in.<br>
<br>
TestLogin.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
Click here to logout.
</BODY>
</HTML>
----TestLogout.jsp-------
<%
java.util.Date date = new java.util.Date();
HttpSession sess = request.getSession(true);
System.out.println(date + ":TestLogout.jsp: sessionid = " + sess.getId() + ", new = " + sess.isNew());
%>
<HTML>
<HEAD>
<TITLE>TestLogout</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" topmargin=0 leftmargin=0 marginwidth=0 marginheight=0>
<p>
TestLogout.jsp: sessionid = <%=sess.getId()%>, new = <%=sess.isNew()%><br>
<br>
<%
sess.invalidate();
%>
You are now logged out.<br>
<br>
Click here to login.
</BODY>
</HTML>Hi,
I think it's best to wait for sometime and check the behaviour of sticky load balancing for sometime, the reason being one or more of the following...
- Although sticky feature ensures that the component is run at a single server, when combined with load balancing and under heavy user loads, the load balancing takes place.
- If we rule out the previous case, then, the load balancing mechanism, especially, per component based or per server based, sends request by round robin technique initally(around 128 times or so) and then calculates the effeciency of the response time and then follows the per server based or per component based.
- Meanwhile please ensure that, you have enabled the Sticky LB option under Application using iASAT and please wait for sometime sending requests(probably 130 times) after which it's good to check the mechanism of the sticky bit technique. If it doesn't behaves as it has to then, please let me know and I can help you further on this.
Regards
RG -
How to make IIS plug-in do STICKY load balancing
There are two classes of scalable services: pure and sticky. A pure service
is one where any instance of the application can respond to client requests.
A sticky service is one where a client sends its requests to the same
instance; those requests are not redirected to other instances.
It seems to me that weblogic IIS proxy plug-in does not support the sticky
load balancing.
Could someone give me some information on how to make the proxy sticky?
Is there configuration parameters for this?
Thanks,
-LeiI set the cluster.
It seems to me that there is some problem with the Set-Cookie mechanism of
the plug-in.
Sometime it set the cookie in my browser, sometime it is not.
Even from the wlproxy.log, I could set something like
Fri Aug 03 17:56:12 2001 Hdrs to
client:[Set-Cookie]=[AribaNode=O2tII92qHlP2tpZjUV0m5ued1s6X028cUPu24QcGj1Q25
AE5VXOd!1782877802312707887!ltang.ariba.com!8001!7002; domain=ariba.com;
path=/]
But the cookie is not set in my browser, what might be wrong here?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
I do believe that this will not work since if clustering is not enabled, a
cookie will not be set on the browser that contains the primary and
secondary server.
You are specifying two different ports in your servers. You need to use
clustering in order to get this functionality with the plugin.Furthermore,
you will achieve fail-over.
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
Here is what I did for the examples under the bea sample directory.
I put the following in test1/WEB-INF/weblogic.xml
<session-descriptor>
<session-param>
<param-name> CookieDomain </param-name>
<param-value> *.ariba.com </param-value>
</session-param>
<session-param>
<param-name> CookieName </param-name>
<param-value> AribaNode </param-value>
</session-param>
<session-param>
<param-name> CookiePath </param-name>
<param-value> /test1 </param-value>
</session-param>
</session-descriptor>
</weblogic-web-app>
I add the following in iisproxy.ini
# This file contains initialization name/value pairs
# for the IIS/WebLogic plug-in.
WebLogicCluster=ltang.ariba.com:8001,achu.ariba.com:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test1
DynamicServerList=OFF
CookieName=AribaNode
I use SesssionServlet.java as an example
When I involk http://proxy/test1/SessionServlet, I always get 1
if I use
http://proxy/test1/SessionServlet:AribaNode=................................
I could see the session becomes sticky.
If I do not want to use URL rewriting, what should I do in order to makethe
session STICKY
for this example.
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
If you leave the CookieName untouched on the WebLogic side, then there
should be no reason to make the change in the plug-in.
But yes, you need to make sure the cookie names are the same.
Regards,
Eric
"Mark Vaughn" <[email protected]> wrote in message
news:[email protected]...
Actually, you also need to make sure you set the "CookieName" in theplugin.
That let's the plugin read the cookie set by WebLogic to determine
who
the
primary and secondary servers are for that session. Otherwise, theplugin
has no
way of knowing if you are establishing a new session or returning to
an
existing
one. The cookie will tell it if you have a current session and who
it
should
send you to for continuing that session, or failing that session
over.
>>>>
Eric Gross wrote:
Without having clustering enabled, you will not get Sticky load
balancing.
You need to have clustering so that a cookie is sent back to the
client
that
contains information about where it's session is located.
Otherwise,
you
are just going to get round-robin each time.
You can refer to the following page for more information:
http://e-docs.beasys.com/wls/docs61/cluster/servlet.html
Regards,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
WebLogicCluster=machine1:7001,machine2:7001
ConnectTimeoutSecs=20
ConnectRetrySecs=2
Debug=ALL
WLLogFile=c:\tmp\wlproxy.log
WlForwardPath=/test,/test1
DynamicServerList=OFF
I run two standone (Admin server) weblogic servers on machine1
machine2.
Then I deploy application test.war on machine1 first, then onmachine2.
Should I make machine2 as a managed server and machine1 as an
admi
n
server?
Will this make the session sticky?
Thanks,
-Lei
"Eric Gross" <[email protected]> wrote in message
news:[email protected]...
It would help us to know how you have iisproxy.ini configured.
Sticky
load
balancing should work fine if you have the plug-in and
WebLogic
Server
setup
correctly.
How have you setup the plug-in?
Thanks,
Eric
"Lei Tang" <[email protected]> wrote in message
news:[email protected]...
There are two classes of scalable services: pure and sticky.
A
pure
service
is one where any instance of the application can respond to
client
requests.
A sticky service is one where a client sends its requests to
the
same
instance; those requests are not redirected to other
instances.
It seems to me that weblogic IIS proxy plug-in does notsupport
the
sticky
load balancing.
Could someone give me some information on how to make the
proxy
sticky?
Is there configuration parameters for this?
Thanks,
-Lei
.-. Mark Vaughn
/V\ 7024 Corona Dr.
// \\ North Richland Hills, TX 76180
/( )\ [email protected]
^^-^^
"Give a man a fish and you feed him for a day;
teach him to use the Net and he won't bother you for weeks."
Ben Woodbridge -
Load Balancing on two server nodes at the sender side...
Hi Experts,
I am sending a huge message (this message is being splitted into multiple messages depending on the load and zipped, this whole process of splitting and zipping is done by the scripts) zipped from sender side , when I am monitoring in message monitoring tool I found that all the load is on one server node and other server node is free as we have two server nodes , how to distribute the message equally between these two nodes.
The same Load balancing is working properly at the receiver end (load is getting distributed between two server nodes). Not sure why this is not the case at the sender side.
Please throw some light on this issue.
Thanks a lot for your kind help in advance.Hi,
Follow this blog this may helpful to you
Handling Large files in XI
/people/pooja.pandey/blog/2005/10/17/number-formatting-to-handle-large-numbers
file size can be handeled in client java proxy and the message is parsed in xi. this will not have much of performance issue. but yes when the smae is handeled by xi. and yes this scenario can be efficiently handeled from java client proxy
limit on the number of 'field-set' lines you can send to the ITS?
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/72e2bb90-0301-0010-e883-c390ad8a975a
Processing huge file loads through XI
Edited by: Venkataramesh Boppana on May 17, 2008 12:54 AM -
Email send issue using "Mail Server Load balancer" (Cisco ACE 20)
Please let me know if someone have experienced this kind of issue or any suggestions.
The send email action was working file in MII with smtp mail server on port 25. Recently basis did a change in mail server ip address and they installed a new Load Balancer . The Load balancer is between SMTP and MII. After this change MII does not send email (unknown source error). now MII send email action has ip address or qualified path of Load balancer in MII send email configuration instead of direct ip address of SMTP server. Below is the error message in Net Weaver logs.
MII still sends email if direct ip address of email server provided but not through email Load balancer .
Any suggestions ?
Could not authenticate mail account (Unknown Source)
[EXCEPTION]
javax.mail.AuthenticationFailedException
at javax.mail.Service.connect(Service.java:319)
at javax.mail.Service.connect(Service.java:169)
at javax.mail.Service.connect(Service.java:118)
at com.sap.xmii.storage.connections.MailConnection.sendMail(MailConnection.java:202)
at com.sap.xmii.bls.executables.actions.mail.MailActions.send(MailActions.java:223)
at sun.reflect.GeneratedMethodAccessor1412.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Switch.doExecute(Switch.java:131)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Repeater.doExecute(Repeater.java:113)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:151)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:122)
at com.sap.xmii.bls.executables.controls.Conditional.doExecute(Conditional.java:158)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseControl.execute(BaseControl.java:127)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runControl(ProductionRunner.java:97)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:64)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.bls.executables.actions.logic.LogicActions.transaction(LogicActions.java:310)
at sun.reflect.GeneratedMethodAccessor387.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.sap.xmii.bls.engine.ReflectiveAction.doExecute(ReflectiveAction.java:747)
at com.sap.xmii.bls.engine.BaseNode.executeNode(BaseNode.java:198)
at com.sap.xmii.bls.engine.BaseAction.execute(BaseAction.java:76)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runAction(ProductionRunner.java:147)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:50)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.Sequence.execute(Sequence.java:59)
at com.sap.xmii.bls.engine.runners.ProductionRunner.runSequence(ProductionRunner.java:126)
at com.sap.xmii.bls.executables.sequences.RootNode.execute(RootNode.java:39)
at com.sap.xmii.bls.engine.TransactionInstance.execute(TransactionInstance.java:1001)
at com.sap.xmii.bls.engine.TransactionInstance.run(TransactionInstance.java:680)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.processQueryRequest(XacuteRequestHandler.java:342)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteRequestHandler.QueryRequest(XacuteRequestHandler.java:135)
at com.sap.xmii.Illuminator.connectors.Xacute.XacuteConnector.doProcessRequest(XacuteConnector.java:86)
at com.sap.xmii.Illuminator.connectors.AbstractConnector.processRequest(AbstractConnector.java:83)
at com.sap.xmii.Illuminator.server.QueryEngine.run(QueryEngine.java:41)
at com.sap.xmii.Illuminator.services.handlers.IlluminatorService.processRequest(IlluminatorService.java:68)
at com.sap.xmii.Illuminator.services.ServiceManager.run(ServiceManager.java:68)
at com.sap.xmii.servlet.Illuminator.service(Illuminator.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:80)
at com.sap.xmii.servlet.ServletRunner.run(ServletRunner.java:44)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.processServletRequest(ReportParser.java:610)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseServletTag(ReportParser.java:276)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parseFile(ReportParser.java:154)
at com.sap.xmii.Illuminator.gui.irpt.ReportParser.parse(ReportParser.java:119)
at com.sap.xmii.servlet.ReportServlet.service(ReportServlet.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:96)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:468)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Date:
2014-03-25
Time:
14:04:06:176
Category:
com.sap.xmii.storage.connections.MailConnection
Location:
com.sap.xmii.storage.connections.MailConnection
Application:
sap.com/xapps~xmii~ear
Thread:
Thread[HTTP Worker [@629095796],5,Dedicated_Application_Thread]
Data Source:
j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction:Have a look at this thread please:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11f3079-b04a-4a8e-b89e-d56eb0532c42/the-mail-could-not-be-sent-to-the-recipients-because-of-the-mail-server-failure-sending-mail-using?forum=sqldatabaseengine
Saeid Hasani [sqldevelop] -
Https through load balancer breaks declarative security
Hello,
My desired setup is for a Jboss cluster serving requests behind a load balancer. Also I intend to use declarative security on the deployed units and have ssl client side authentication.
I need someone to please confirm/deny the following statements:
1) ssl has to be negotiated by the load balancer, whether hardware or software based (apache with mod_proxy/mod_jk).
2) if using apache with mod_jk it is possible to configure it to send the client side authentication details (certificate) in such a way that jboss may enforce declarative authorization as if it had done the authentication itself. This also means that the programatic means to get the authenticated user identity described in the ejb and servlet specs will still work.
3) there is no hardware load balancer that supports the behavior described in 2), which means that with a hardware load balancer it is impossible to use declarative authorization enforcement.
After a whole lot testing and digging up for info, I'm quite desperate to solve this question, so if someone could help me I would be most thankfull.
NunoAfter further research, I think the best course of action will be to create a VLAN for the zone behind the BigIP and then create the corresponding interface in the vlan and zone. Using this links as my references in case anyone is interested. I'll post what I come up with.
https://blogs.oracle.com/stw/entry/using_ip_instances_with_vlans
https://blogs.oracle.com/stw/entry/solaris_zones_and_networking_common
http://docs.oracle.com/cd/E19253-01/816-4554/816-4554.pdf # AdministeringVirtualLocalAreaNetworks
http://docs.oracle.com/cd/E19053-01/ldoms.mgr11/820-4913-10/820-4913-10.pdf # Assign VLANs to a Virtual Switch and Virtual
Network Device -
Guys,
Looking for some feedback on DMSMetricCollector when using "metric" as the selectmethod for load-balancing. What i want to know is that whether the DMSMetricCollector can be configured to use multiple metrics such jvm-heapsiize, servlet-processRequestTime etc, Connection-pools FreePoolSize.value etc ? the documentation doesn't explicitly mention that if its possible, apparently it doesn't but want to check from the experts here, Steve you might have something on this...
Or if there is any other implementation available which supports load-balancing based on multiple performance metrics
Thanks and Regardscan i use this loadbalancer.jar or not?
how to mod_oc4j in standalone app server
Maybe you are looking for
-
My iPhone 4 power button doesn't work, how can I get repair it and how much will cost, want to keep same phone everything works fine not power button not working unable used my phone. My warranty is Expired how much will cost to put it on my phone pl
-
Even after I update an app I've bought I can't get the upgrades badge to go away.
It happens with almost every program I update in the Mac App store. I update the program. It says it's updaded. the the badge shows that I have 1, 2, or 3 updates left.....they are the same updates as before I updated them. This doesn't just happen w
-
Hi Everyone, This may have been posted before, but I have a problem with dreamweaver v8 and layers. When I try and draw a layer on a normal html page, it does not allow me to pick it up and drag it. It keeps going to the top of the page, like form ob
-
What is the difference between roles and groups in Identity Server
-
I'm trying to find a good entry level gaming PC :)
Hello, I'm new to PC gaming and I'm looking for a computer that is good for me to start on. Now I've been looking around and I don't really know what I'm looking for. http://www.bestbuy.com/site/HP+-+Pavilion+Desktop+-+10GB+Memory+-+1TB+Hard+Drive