Mp Ramkumar

Hi,
I have 3 machines namely A, B and C. I have to install IBM Websphere 6.1.0.23 version in machines B and C. Then create a cluster with 2 nodes in Machine B, create another cluster with 2 nodes in Machine C.

Now I would like to configure IBM HTTP server as proxy(which is installed in Machine A) for the cluster in Machine B and Machine C.


Is this possible to proxying/load balancing of multiple clusters which are available in different machines with one IBM HTTP Server.

Thanks
RAM

Hi All,
As per my knowledge there are two ways of weblogic clustering.
1. Using Managed Server - Which will be used to create multiple nodes in single machine to utilize the ram more effectively. (We start the weblogic using the startManagedWeblogic.cmd file with Node name and the Admin url arguments)
2. Using Node Manager - Which will be used to create a single node per machine. (We start the weblogic node using the startNodeManager.cmd file without any arguments)

Is there a way to confirgure multiple nodes in single machine using the node manager clustering. Quick response would be appriciated.

Thanks & Regards,
RamkumarMP

Hi All,
I have prepared a document which explains the IIS 7 on Windows 2008(64/32 bit environment) configuration with JBOSS EAP 4.3.0 CP02 for Load balancing and also as proxy.

This document explains about SSL Certification configuration also. All the details are given step by step with screen shots. You can refer the below given URL. Hope this will help you in your work.

http://www.scribd.com/doc/20684887/IIS-7-On-windows-2008-with-JBOSS-EAP-430-CP02

Thanks
RAM

Hi Guys,
We have used Jconsole with Weblogic with our product. When 100 concurrent users accessing the application we have observered the jVM usage and response times of the transactions. (When Jconsole is not used with weblogic), and (When Jconsole is used with weblogic to collect JVM details).

The response times and the server resources consumtion seems normal. No difference. Hence planning to JConsole.

Thanks to all.

Can some one suggest a good tool for Oracle monitoring. We would like to monitor Sessions, SGA, Cursors etc., We need a opensource tool.

Thanks & Regards,
Ram

Thanks Kees Jan. I will publish our experiment status once we verify. We need to verify the load on the appserver during performance testing with some no. of users, due to this monitoring work.

Thanks Peter, We are using JBOSS 4.3.0 EAP CP02 with JDK 1.6

Hi
I am testing two web applications(example webappA and webappB) which are deployed on two different machines(example webappA on Machine1, webappB on Machine2).

WebappB will be pinging or calling the webservice of WebappA. If the two applications are not integrated(means if the webappA webservice URL is not given in WebappB), then the active session on the MachineA/webappA deployment is showing 0 to 5. But if the both the apps are integrated then active sessions for the webappA deployment are touching to some 2000 above, though nobody using the applications.

Does it get impacted in the performance of the application or it causes any bottleneck in handling more no. of users(approx. 150Users), since the intended target end users are 150.

What will probably happen if the no. of active sessions(in JBOSS for a webapp) increase in the above said manner. what are the impact areas.

The below is the extract of webappA deployment description from JBOSS webconsole
localhost/WebappA
Start time: Tue Jan 05 11:06:43 IST 2010 Startup time: 140 ms TLD scan time: 0 ms
Active sessions: 2189 Session count: 2189 Max active sessions: 2189 Rejected session creations: 0 Expired sessions: 0 Longest session alive time: 0 s Average session alive time: 0 s Processing time: 0 ms
JSPs loaded: 0 JSPs reloaded: 0

Thanks & Regards,
RamkumarMP

Thanks Tim... Can this be used in our Performance Testing environment. Because if it uses resources considerably then our response times varies. So I am asking?

Thanks
Ram

Hi,
We are using Load Runner for the performance Testing of our application. We do not have java heap size monitoring tool, Oracle connections,sqls monitoring tool and also the Netword bandwidth and Latency monitoring tool when the concurrent user test execution is inprogress.

Using Load runner we are capturing the server level resources like available MBytes, Java process utilization, CPU utilization etc., we do not have license for may other counters to monitor.

Can some one please suggest us a free tool which will help us to track the JVM heap size utilization and GC etc., Network idle/usage etc., Oracle

Thanks
Ram

I am new to this combination Apache with Weblogic. We have a situation as given below.

We are using the following configuration in the load balancer setup.

- Weblogic 9.2.3 with a cluster having two servers - The cluster node and both the servers are running on the same machine.
- Apache 2.2.1.1 server with the proxy plugin for weblogic on another machine.
- We are using HttpSession based session tracking in the application.
- We are not you using cookies or url parameters to maintain the session id in the application.

Setup Example:
We have Machine A - D,
Machine A is having Apache and Weblogic Admin
Machine B,C,D - having Weblogic Cluster Nodes for Application

Apache is balancing the cluster.

Problem
We are facing a problem with the session stickyness - Sometimes we see that the apache server redirects the user to the server which was NOT initially serving the user request... and hence the user gets kicked out from the initial session.

Our Restrictions
We can not use any type of session replication since the architecture of the application doesn't support it (Objects that we keep in session are not Serializable) . We need a round robin load balancing to balance the load on the servers to have a better performance. However, once a client establishes a session between a given server we need the same server to serve the client. The plugin should NOT switch the client to the other server.

For your reference - httpd.conf file is as below(in case if needed):


ServerRoot "C:/Apache2213ssl32bit" Listen 80 LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule asis_module modules/mod_asis.so LoadModule auth_basic_module modules/mod_auth_basic.so LoadModule authn_default_module modules/mod_authn_default.so LoadModule authn_file_module modules/mod_authn_file.so LoadModule authz_default_module modules/mod_authz_default.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so LoadModule cgi_module modules/mod_cgi.so LoadModule dir_module modules/mod_dir.so LoadModule env_module modules/mod_env.so LoadModule include_module modules/mod_include.so LoadModule isapi_module modules/mod_isapi.so LoadModule log_config_module modules/mod_log_config.so LoadModule mime_module modules/mod_mime.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule setenvif_module modules/mod_setenvif.so LoadModule ssl_module modules/mod_ssl.so LoadModule userdir_module modules/mod_userdir.so LoadModule weblogic_module modules/mod_wl_22.so <IfModule !mpm_netware_module> <IfModule !mpm_winnt_module> User daemon Group daemon </IfModule> </IfModule> ServerAdmin admin@agi.com DocumentRoot "C:/Apache2213ssl32bit/htdocs" <Directory /> Options FollowSymLinks AllowOverride None Order deny,allow Deny from all </Directory> <Directory "C:/Apache2213ssl32bit/htdocs"> Options Indexes FollowSymLinks AllowOverride None Order allow,deny Allow from all </Directory> <IfModule dir_module> DirectoryIndex index.html </IfModule> <FilesMatch "^\.ht"> Order allow,deny Deny from all Satisfy All </FilesMatch> ErrorLog "logs/error.log" LogLevel warn <IfModule log_config_module> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common <IfModule logio_module> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> CustomLog "logs/access.log" common </IfModule> <IfModule alias_module> ScriptAlias /cgi-bin/ "C:/Apache2213ssl32bit/cgi-bin/" </IfModule> <IfModule cgid_module> </IfModule> <Directory "C:/Apache2213ssl32bit/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> DefaultType text/plain <IfModule mime_module> TypesConfig conf/mime.types AddType application/x-compress .Z AddType application/x-gzip .gz .tgz </IfModule> <VirtualHost *:80> ServerAdmin admin@agi.com ServerName rentsrv14s4.agi.com ErrorLog logs/error_log <Location /console> SetHandler weblogic-handler Debug ALL DebugConfigInfo ON WLLogFile C:\wlproxy.log </Location> <IfModule mod_weblogic.c> MatchExpression /communications WeblogicCluster=192.168.111.208:7020,192.168.111.194:7021,192.168.111.151:7022 KeepAliveEnabled ON KeepAliveSecs 15 WLIOTimeoutSecs 1800 </IfModule> </VirtualHost>

Hi,

I am getting the following error on IIS7 setup on windows 2008(64bit) environment.

I followed the guide http://www.jboss.org/community/wiki/UsingModjk12WithJBossAndIIS7.pdf and used the 64bit connecter(i.e., http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win64/jk-1.2.28/ia64/isapi_redirect-1.2.28.dll). It is not working. The same instruction given in the guide is working fine for 32bit environment with 32bit mod_jk connector.

Just after installing the IIS, I am able to see the IIS page on accessing http://localhost/. Once I place the isapi_redirect.dll from the above mentioned location, I am getting the following error.
Calling LoadLibraryEx on ISAPI filter C:\JK\bin\isapi_redirect.dll failed


I have set the parameter "enable 32 applications" in default app pool to Only http://localhost/ is giving the IIS7 page. But when I access the url http//localhost/awebapp I am getting the error mentioned under Error Summary section. If I access the url without IIS then it is working fine(ie., http://rentsrv15s1:8080/awebapp/)

On IE the error displayed is as follows:

Error Summary: -------------------
HTTP Error 404.0 - Not FoundThe resource you are looking for has been removed, had its name changed, or is temporarily unavailable. Detailed Error Information:Module: IIS Web Core Notification: MapRequestHandler Handler: StaticFile Error Code: 0x80070002 Requested URL: http://localhost:80/awebapp/ Physical Path: C:\inetpub\wwwroot\awebapp\ Logon Method: Anonymous Logon User: Anonymous
Failed Request Tracing Log Directory: C:\inetpub\logs\FailedReqLogFiles

Most Likely Causes:The directory or file specified does not exist on the Web server. The URL contains a typographical error.
A custom filter or module, such as URLScan, restricts access to the file

Things you can Try:Create the content on the Web server. Review the browser URL.
Create a tracing rule to track failed requests for this HTTP status code and see which module is calling SetStatus. For more information about creating a tracing rule for failed requests, click here.
--------------------------------


Can some one help me out on this.

Thanks & Regards,

RamkumarMP

Hi,
I have successfully configured, IIS7 on Windows 2008 (32 bit environmnet) with JBOSS 4.3.0 Cluster. I have prepared a document with screen shots and step by step instructions. May be this can help you people in your work.

Please find the document in the following location with screen shots.
http://www.scribd.com/doc/20623913/IIS7-on-Windows-2008-Configuration-with-JBOSS-430-CP02

Thanks & Regards,
RamkumarMP

Hi All,
I have got success on JBOSS 4.3.0 EAP Clustering. I am updating the steps what are followed to cluster the JBOSS instances. following are the steps. Let me know if there are clarification. I can try to answer(If I come across)

JBOSS 4.3.0 EAP Clustering with multiple instances running on Same machine balanced with Apache HTTP Server 2.2.11
In case if you want to run two instances on the same machine, copy production machine to two folders with different node names, Search for ports-01 and Uncomment the following in one node and do not uncomment in another node. If you need third instance also running on the same machine then copy the production folder to another node folder as third instance and uncomment the bleow content and change the ports-01 to ports-02.
The above ports change to be done on the file <jboss_home>\jboss-as\server\<node name>\conf\serverl.xml

<mbean code="org.jboss.services.binding.ServiceBindingManager" name="jboss.system:service=ServiceBindingManager"> <attribute name="ServerName">ports-01</attribute> <attribute name="StoreURL">${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml</attribute> <attribute name="StoreFactoryClassName"> org.jboss.services.binding.XMLServicesStoreFactory </attribute> </mbean>


Note:
1. If you comment <mbean> tag section, JBoss considers the default ports. Example: 8080, 1099 etc..,
2. If you specify ports-01, JBoss uses the ports by incrementing the second digit by 1. example: 8180, 1199 etc.,
3. If you specify ports-02, JBoss uses the ports by incrementing the second digit by 2. example: 8280, 1299 etc..,
Port numbers will get increased by 100.


JBOSS 4.3.0 EAP Clustering with Apache HTTP Server 2.2.11

1. Configure Apache HTTP Server 2.0.63(without SSL)
1. Install Apache HTTP Server 2.0.63(without SSL).

2. Download the mod_jk-1.2.28-httpd-2.0.52.so from below link
http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.28/
(Tried with different mod_jk.so/mod_jk.dll’s but not working)

If you are using Apache HTTP server 2.2.11, then use the following binary from the location mentioned below
Binary Name: mod_jk-1.2.28-httpd-2.2.3.so
Location is http://www.apache.org/dist/tomcat/tomcat-connectors/jk/binaries/win32/jk-1.2.28/


2. Update httpd.conf file available under <Apache_HOME>\Apache2\conf with the following lines at the end.

# Include mod_jk's
# specific configuration file
Include conf/mod-jk.conf

3. Create a file called mod-jk.conf under <Apache_HOME>\Apache2\conf folder with the following content.

# Load mod_jk module
# Specify the filename of the mod_jk lib
LoadModule jk_module modules/mod_jk.so
# Where to find workers.properties
JkWorkersFile conf/workers.properties
# Where to put jk logs
JkLogFile logs/mod_jk.log
# Set the jk log level [debug/error/info]
JkLogLevel info
# Select the log format
JkLogStampFormat "[%a %b %d %H:%M:%S %Y]"
# JkOptions indicates to send SSK KEY SIZE
JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories
# JkRequestLogFormat
JkRequestLogFormat "%w %V %T"
# Mount your applications
JkMount /* loadbalancer
# You can use external file for mount points.
# It will be checked for updates each 60 seconds.
# The format of the file is: /url=worker
# /examples/*=loadbalancer
JkMountFile conf/uriworkermap.properties
# Add shared memory.
# This directive is present with 1.2.10 and
# later versions of mod_jk, and is needed for
# for load balancing to work properly
JkShmFile logs/jk.shm
# Add jkstatus for managing runtime data
<Location /jkstatus/>
JkMount status
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Location>

4. Create a file called uriworkermap.properties under <Apache_HOME>\Apache2\conf folder with the following content.

# Simple worker configuration file
# Mount the Servlet context to the ajp13 worker
/jmx-console=loadbalancer
/jmx-console/*=loadbalancer
/web-console=loadbalancer
/web-console/*=loadbalancer

5. Create a file called workers.properties under <Apache_HOME>\Apache2\conf folder with the following content and change the host name and Port numbers as required.

# Define list of workers that will be used
# for mapping requests
worker.list=loadbalancer,status

# Define Node1
# modify the host as your host IP or DNS name.
worker.node1.port=8009
worker.node1.host=agi-607.agi.com
worker.node1.type=ajp13
worker.node1.lbfactor=1
worker.node1.cachesize=10

# Define Node2
# modify the host as your host IP or DNS name.
worker.node2.port=8009
worker.node2.host=agi-678.agi.com
worker.node2.type=ajp13
worker.node2.lbfactor=1
worker.node2.cachesize=10

# Load-balancing behaviour
worker.loadbalancer.type=lb
worker.loadbalancer.balance_workers=node1,node2
worker.loadbalancer.sticky_session=1
#worker.list=loadbalancer
# Status worker for managing load balancer
worker.status.type=status

2. Configuring JBOSS 4.3.0 EAP – CP02 GA Clustering
6. Make sure the Java 1.5.0.11 is installed and the JAVA_HOME in environment variable is set as mentioned below.
Example: C:\Program Files\Java\jdk1.5.0_10
7. Extract JBOSS 4.3.0 Enterprise Application Platform CP02 build in to Hard disk after downloading it from the location.
https://support.redhat.com/jbossnetwork/restricted/listSoftware.html?downloadType=distributions&product=appplatform&version=4.3.0.GA_CP02

8. Copy the production folder under jboss-eap-4.3\jboss-as\server folder into another folder named Node1 to create a node instance.
9. Add the jvmRoute= <Node name> parameter to the given line as shown in the example in the file server.xml available under jboss-eap-4.3\jboss-as\server\Node2\deploy\jboss-web.deployer folder.
Eg:
<Engine name="jboss.web" defaultHost="localhost" jvmRoute="Node1">

10. Locate the <attribute> element with a name of UseJK, and set its value to true in the file jboss-service.xml available under jboss-eap-4.3\jboss-as\server\Node2\deploy\jboss-web.deployer\META-INF folder.
Eg:
<attribute name="UseJK">true</attribute>

11. Update the tag <distributable/> in the file “web.xml” available at JBoss_HOME\server\all\deploy\jmx-console.war\WEB-INF\web.xml as given below:
Eg:
<?xml version="1.0"?>
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>

 update the below line after the above content.
<distributable/>


12. Uncomment the line #admin=admin in the files web-console-users.properties, jmx-console-users.properties files which are available under folders JBOSS_HOME\server\Node3\deploy\management\console-mgr.sar\web-console.war\WEB-INF\classes and JBoss_HOME\server\Node3\conf\props respectively.



13. To disable to JMS clustering, change the following parameter to true in the file clustered-hsqldb-persistence-service.xml or if you are using different database then <XXX>-persistence-service.xml file.

<attribute name="Clustered">false</attribute>
14. Jboss clustered environment will not support exploded war file. Hence the war file should be placed in the farm folder. But each time you restart the jboss server the deployments get restarted due to which the arispwd.dat and property files will change after deployment. The bold lines to be added to the file web.xml which is available under jboss-eap-4.3\jboss-as\server\node1\deploy\jboss-web.deployer\conf to avoid this problem.

<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>enablepooling</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>development</param-name>
<param-value>false</param-value>
</init-param>
<init-param>
<param-name>xpoweredBy</param-name>
<param-value>false</param-value>
</init-param>

15. Perform the steps from 7 to 10 on machine to for Node2.
16. Start the JBOSS using run.bat file from the location jboss-eap-4.3\jboss-as\bin after connecting to command prompt, with the parameter –c and argument <Node>. Example given below.
a. From Node1 the command should be executed at the dos prompt under folder jboss-eap-4.3\jboss-as\bin as mentioned below
i. Run.bat –c Node1 –b agi-607.agi.com

b. From Node2 the command should be executed at the dos prompt under folder jboss-eap-4.3\jboss-as\bin as mentioned below
i. Run.bat –c Node2 –b agi-678.agi.com
17. Verify the cluster by logging into the jmx console using the following with user admin and password as admin.
http://agi-607.agi.com/
The following screens will display.


Figure 1: JBOSS console page.

Figure 2: Username admin and password as admin(as given in the jmx-console-users.properties file in the JBoss_HOME\server\Node3\conf\props folder)


Figure 3: Screen after log into jmx console002




Figure 4: Service=DefaultPartition under JBOSS section in the jmx console screen.


Figure 5: Service=DefaultPartition under JBOSS section in the jmx console screen. Clustered machines shall be viewed in the current view.

18. Place the .war file in the folder jboss-eap-4.3\jboss-as\server\Node2\farm, after starting the two nodes.
19. Check if the deployment is pushed into the both nodes under farm folder and accessible with the default port number.
Example:
a. http://agi-607:8080/Admin/wflogin.jsp
b. http://agi-678:8080/Admin/wflogin.jsp


Note: Any one approach to be chosen to configure the datasource either section 3 or section 4.
3. Oracle 10g JDBC Source configuration(Alternative database)
1. Copy the JDBC driver ojdbc14.jar from the oracle installation folder Oracle\product\10.1.0\Client_1\jdbc\lib in to the jboss-eap-4.3\jboss-as\server\node1\lib

2. JBoss AS connects to relational databases via datasources. These datasource definitions can be found in the jboss-as\server\production\deploy directory. The datasource definitions are deployable just like WAR and EAR files. The datasource files can be recognized by looking for the XML files that end in *-ds.xml.

3. Configure default data source to Oracle by following the below steps

a) Copy the oracle-ds.xml file from jboss-as\docs\examples\jca to jboss-as\server\Node3\deploy folder.
b) Modify as mentioned below
<datasources>
<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:oracle:thin:@192.167.104.22:1521:orcl</connection-url>
<!--

Here are a couple of the possible OCI configurations.
For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm

<connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url>
Or
<connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url>

Clearly, it’s better to have TNS set up properly.
-->
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>jbossuser</user-name>
<password>jbosspass</password>
<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
<!-- Checks the Oracle error codes and messages for fatal errors -->
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->

<!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->

<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml -->
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
</local-tx-datasource>

</datasources>

Note: If multiple database schemas to be configured then just replicate the data sources block again by changing the credentials.

4. Oracle 10g JDBC Source Configuration(Using shared database)

1. Create a database user with name jbossuser and password as jbosspass.

2. Copy the JDBC driver ojdbc14.jar from the oracle installation folder Oracle\product\10.1.0\Client_1\jdbc\lib in to the jboss-eap-4.3\jboss-as\server\node1\lib

3. JBoss AS connects to relational databases via datasources. These datasource definitions can be found in the jboss-as\server\production\deploy directory. The datasource definitions are deployable just like WAR and EAR files. The datasource files can be recognized by looking for the XML files that end in *-ds.xml.

4. Configure default data source to Oracle by following the below steps

a) Copy the oracle-ds.xml file from jboss-as\docs\examples\jca to jboss-as\server\Node3\deploy folder.
b) Modify as mentioned below
<datasources>
<local-tx-datasource>
<jndi-name>DefaultDS</jndi-name>
<connection-url>jdbc:oracle:thin:@192.167.104.22:1521:orcl</connection-url>
<!--

Here are a couple of the possible OCI configurations.
For more information, see http://otn.oracle.com/docs/products/oracle9i/doc_library/release2/java.920/a96654/toc.htm

<connection-url>jdbc:oracle:oci:@youroracle-tns-name</connection-url>
or
<connection-url>jdbc:oracle:oci:@(description=(address=(host=youroraclehost)(protocol=tcp)(port=1521))(connect_data=(SERVICE_NAME=yourservicename)))</connection-url>

Clearly, its better to have TNS set up properly.
-->
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>jbossuser</user-name>
<password>jbosspass</password>
<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
<!--valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name-->
<!-- Checks the Oracle error codes and messages for fatal errors -->
<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->

<!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->

<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml -->
<metadata>
<type-mapping>Oracle9i</type-mapping>
</metadata>
</local-tx-datasource>

</datasources>

Note: If multiple database schemas to be configured then just replicate the data sources block again by changing the credentials.

5. The JMS service in the JBoss AS uses relational databases to persist its messages. For improved performance, you should change the JMS service to take advantage of the external database. To do that, you need to replace the file jboss-as/server/production/deploy/jboss-messaging.sar/clustered-hsqldb-persistence-service.xml with a file oracle-persistence-service.xml in jboss-as/docs/examples/jms folder and restart your server.

6. Next, change the jboss-as/server/production/conf/standardjbosscmp-jdbc.xml file so that the fk-constraint property is true. That is needed for all external databases we supported bythe JBoss Enterprise Application Platform. This file configures the database connection settings for the EJB2 CMP beans deployed in the JBoss AS.

<fk-constraint>true</fk-constraint>

7. The Java Persistence API (JPA) entity manager can save EJB3 entity beans to any backend database. Hibernate provides the JPA implementation in JBoss AS. In order for Hibernate to work correctly with alternative databases, JBOSS recommend you configure the database dialect in the jboss-as/server/production/deploy/ejb3.deployer/META-INF/persistence.properties file. Add the following line below #hibernate.dialect=org.hibernate.dialect.HSQLDialect.

hibernate.dialect=org.hibernate.dialect.Oracle10gDialect

Perform the entire section 3 on both the nodes of the cluster.

Hi,
We are doing performance test for our product with 100 Users. The application has been deployed on Weblogic 9.2.3 Cluster and configured Apache HTTP server as load balancer.

If I access as single user then it is working fine. But if I give a test with load runner for 100 Users, then after about 60 users are ramped up then the application is responding very slowly.

If I directly access the weblogic deploying bypassing Apache, it is responding normally. Can any one please suggest what can be done.

I have configured the httpd.conf as below


# # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.2> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html> # for a discussion of each configuration directive. # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # Configuration and logfile names: If the filenames you specify for many # of the server's control files begin with "/" (or "drive:/" for Win32), the # server will use that explicit path. If the filenames do *not* begin # with "/", the value of ServerRoot is prepended -- so "logs/foo.log" # with ServerRoot set to "C:/apache22" will be interpreted by the # server as "C:/apache22/logs/foo.log". # # NOTE: Where filenames are specified, you must use forward slashes # instead of backslashes (e.g., "c:/apache" instead of "c:\apache"). # If a drive letter is omitted, the drive on which httpd.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths to avoid confusion. # # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # Do not add a slash at the end of the directory path. If you point # ServerRoot at a non-local disk, be sure to point the LockFile directive # at a local disk. If you wish to share the same ServerRoot for multiple # httpd daemons, you will need to change at least LockFile and PidFile. # ServerRoot "C:/apache22" # # Listen: Allows you to bind Apache to specific IP addresses and/or # ports, instead of the default. See also the <VirtualHost> # directive. # # Change this to Listen on specific IP addresses as shown below to # prevent Apache from glomming onto all bound IP addresses. # #Listen 12.34.56.78:80 Listen 80 # # Dynamic Shared Object (DSO) Support # # To be able to use the functionality of a module which was built as a DSO you # have to place corresponding `LoadModule' lines at this location so the # directives contained in it are actually available _before_ they are used. # Statically compiled modules (those listed by `httpd -l') do not need # to be loaded here. # # Example: # LoadModule foo_module modules/mod_foo.so # LoadModule actions_module modules/mod_actions.so LoadModule alias_module modules/mod_alias.so LoadModule asis_module modules/mod_asis.so LoadModule auth_basic_module modules/mod_auth_basic.so #LoadModule auth_digest_module modules/mod_auth_digest.so #LoadModule authn_alias_module modules/mod_authn_alias.so #LoadModule authn_anon_module modules/mod_authn_anon.so #LoadModule authn_dbd_module modules/mod_authn_dbd.so #LoadModule authn_dbm_module modules/mod_authn_dbm.so LoadModule authn_default_module modules/mod_authn_default.so LoadModule authn_file_module modules/mod_authn_file.so #LoadModule authnz_ldap_module modules/mod_authnz_ldap.so #LoadModule authz_dbm_module modules/mod_authz_dbm.so LoadModule authz_default_module modules/mod_authz_default.so LoadModule authz_groupfile_module modules/mod_authz_groupfile.so LoadModule authz_host_module modules/mod_authz_host.so #LoadModule authz_owner_module modules/mod_authz_owner.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule cache_module modules/mod_cache.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule charset_lite_module modules/mod_charset_lite.so LoadModule dav_module modules/mod_dav.so LoadModule dav_fs_module modules/mod_dav_fs.so #LoadModule dav_lock_module modules/mod_dav_lock.so #LoadModule dbd_module modules/mod_dbd.so #LoadModule deflate_module modules/mod_deflate.so LoadModule dir_module modules/mod_dir.so #LoadModule disk_cache_module modules/mod_disk_cache.so #LoadModule dumpio_module modules/mod_dumpio.so LoadModule env_module modules/mod_env.so #LoadModule expires_module modules/mod_expires.so #LoadModule ext_filter_module modules/mod_ext_filter.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule filter_module modules/mod_filter.so #LoadModule headers_module modules/mod_headers.so #LoadModule ident_module modules/mod_ident.so #LoadModule imagemap_module modules/mod_imagemap.so LoadModule include_module modules/mod_include.so #LoadModule info_module modules/mod_info.so LoadModule isapi_module modules/mod_isapi.so #LoadModule ldap_module modules/mod_ldap.so #LoadModule logio_module modules/mod_logio.so LoadModule log_config_module modules/mod_log_config.so #LoadModule log_forensic_module modules/mod_log_forensic.so #LoadModule mem_cache_module modules/mod_mem_cache.so LoadModule mime_module modules/mod_mime.so #LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule negotiation_module modules/mod_negotiation.so #LoadModule proxy_module modules/mod_proxy.so #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so #LoadModule proxy_balancer_module modules/mod_proxy_balancer.so #LoadModule proxy_connect_module modules/mod_proxy_connect.so #LoadModule proxy_ftp_module modules/mod_proxy_ftp.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule rewrite_module modules/mod_rewrite.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule speling_module modules/mod_speling.so LoadModule ssl_module modules/mod_ssl.so #LoadModule status_module modules/mod_status.so #LoadModule substitute_module modules/mod_substitute.so #LoadModule unique_id_module modules/mod_unique_id.so LoadModule userdir_module modules/mod_userdir.so #LoadModule usertrack_module modules/mod_usertrack.so #LoadModule version_module modules/mod_version.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so LoadModule weblogic_module modules/mod_wl_22.so <IfModule !mpm_netware_module> <IfModule !mpm_winnt_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon </IfModule> </IfModule> # 'Main' server configuration # # The directives in this section set up the values used by the 'main' # server, which responds to any requests that aren't handled by a # <VirtualHost> definition. These values also provide defaults for # any <VirtualHost> containers you may define later in the file. # # All of these directives may appear inside <VirtualHost> containers, # in which case these default settings will be overridden for the # virtual host being defined. # # # ServerAdmin: Your address, where problems with the server should be # e-mailed. This address appears on some server-generated pages, such # as error documents. e.g. admin@your-domain.com # ServerAdmin admin@agi.com # # ServerName gives the name and port that the server uses to identify itself. # This can often be determined automatically, but we recommend you specify # it explicitly to prevent problems during startup. # # If your host doesn't have a registered DNS name, enter its IP address here. # #ServerName ptts.agi.com:80 # # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "C:/apache22/htdocs" # # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # <Directory /> Options FollowSymLinks AllowOverride None Order deny,allow Deny from all </Directory> # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # This should be changed to whatever you set DocumentRoot to. # <Directory "C:/apache22/htdocs"> # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information. # Options Indexes FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride None # # Controls who can get stuff from this server. # Order allow,deny Allow from all </Directory> # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # <IfModule dir_module> DirectoryIndex index.html </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <FilesMatch "^\.ht"> Order allow,deny Deny from all Satisfy All </FilesMatch> # # ErrorLog: The location of the error log file. # If you do not specify an ErrorLog directive within a <VirtualHost> # container, error messages relating to that virtual host will be # logged here. If you *do* define an error logfile for a <VirtualHost> # container, that host's errors will be logged there and not here. # ErrorLog "logs/error.log" # # LogLevel: Control the number of messages logged to the error_log. # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. # LogLevel warn <IfModule log_config_module> # # The following directives define some format nicknames for use with # a CustomLog directive (see below). # LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined LogFormat "%h %l %u %t \"%r\" %>s %b" common <IfModule logio_module> # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio </IfModule> # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # CustomLog "logs/access.log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # #CustomLog "logs/access.log" combined </IfModule> <IfModule alias_module> # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://ptts.agi.com/bar # # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a <Directory> section to allow access to # the filesystem path. # # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target directory are treated as applications and # run by the server when requested rather than as documents sent to the # client. The same rules about trailing "/" apply to ScriptAlias # directives as to Alias. # ScriptAlias /cgi-bin/ "C:/apache22/cgi-bin/" </IfModule> <IfModule cgid_module> # # ScriptSock: On threaded servers, designate the path to the UNIX # socket used to communicate with the CGI daemon of mod_cgid. # #Scriptsock logs/cgisock </IfModule> # # "C:/apache22/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # <Directory "C:/apache22/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> # # DefaultType: the default MIME type the server will use for a document # if it cannot otherwise determine one, such as from filename extensions. # If your server contains mostly text or HTML documents, "text/plain" is # a good value. If most of your content is binary, such as applications # or images, you may want to use "application/octet-stream" instead to # keep browsers from trying to display binary files as though they are # text. # DefaultType text/plain <IfModule mime_module> # # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig conf/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # AddHandler allows you to map certain file extensions to "handlers": # actions unrelated to filetype. These can be either built into the server # or added with the Action directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # #AddType text/html .shtml #AddOutputFilter INCLUDES .shtml </IfModule> # # The mod_mime_magic module allows the server to use various hints from the # contents of the file itself to determine its type. The MIMEMagicFile # directive tells the module where the hint definitions are located. # #MIMEMagicFile conf/magic # # Customizable error responses come in three flavors: # 1) plain text 2) local redirects 3) external redirects # # Some examples: #ErrorDocument 500 "The server made a boo boo." #ErrorDocument 404 /missing.html #ErrorDocument 404 "/cgi-bin/missing_handler.pl" #ErrorDocument 402 http://ptts.agi.com/subscription_info.html # # # EnableMMAP and EnableSendfile: On systems that support it, # memory-mapping or the sendfile syscall is used to deliver # files. This usually improves server performance, but must # be turned off when serving from networked-mounted # filesystems or if support for these functions is otherwise # broken on your system. # #EnableMMAP off #EnableSendfile off Win32DisableAcceptEx # Supplemental configuration # # The configuration files in the conf/extra/ directory can be # included to add extra features or to modify the default configuration of # the server, or you may simply copy their contents here and change as # necessary. # Server-pool management (MPM specific) #Include conf/extra/httpd-mpm.conf # Multi-language error messages #Include conf/extra/httpd-multilang-errordoc.conf # Fancy directory listings #Include conf/extra/httpd-autoindex.conf # Language settings #Include conf/extra/httpd-languages.conf # User home directories #Include conf/extra/httpd-userdir.conf # Real-time info on requests and configuration #Include conf/extra/httpd-info.conf # Virtual hosts #Include conf/extra/httpd-vhosts.conf # Local access to the Apache HTTP Server Manual #Include conf/extra/httpd-manual.conf # Distributed authoring and versioning (WebDAV) #Include conf/extra/httpd-dav.conf # Various default settings #Include conf/extra/httpd-default.conf # Secure (SSL/TLS) connections #Include conf/extra/httpd-ssl.conf # # Note: The following must must be present to support # starting without SSL on platforms with no /dev/random equivalent # but a statically compiled-in mod_ssl. # #<IfModule ssl_module> #SSLRandomSeed startup builtin #SSLRandomSeed connect builtin #</IfModule> <IfModule mod_ssl.c> Include conf/extra/httpd-ssl.conf </IfModule> ### Section 3: Virtual Hosts # # VirtualHost: If you want to maintain multiple domains/hostnames on your # machine you can setup VirtualHost containers for them. Most configurations # use only name-based virtual hosts so the server doesn't need to worry about # IP addresses. This is indicated by the asterisks in the directives below. # # Please see the documentation at # <URL:http://httpd.apache.org/docs/2.0/vhosts/> # for further details before you try to setup virtual hosts. # # You may use the command line option '-S' to verify your virtual host # configuration. # # Use name-based virtual hosting. # #NameVirtualHost *:80 # # VirtualHost example: # Almost any Apache directive may go into a VirtualHost container. # The first VirtualHost section is used for requests without a known # server name. # #<VirtualHost *:80> # ServerAdmin webmaster@dummy-host.example.com # DocumentRoot /www/docs/dummy-host.example.com # ServerName dummy-host.example.com # ErrorLog logs/dummy-host.example.com-error_log # CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost> <VirtualHost *:80> ServerAdmin admin@agi.com #DocumentRoot /www/docs/dummy-host.example.com ServerName ptts.agi.com ErrorLog logs/error_log #sCustomLog logs/access_log <Location /weblogic> SetHandler weblogic-handler #WebLogicCluster 192.168.111.159:3263,192.168.111.161:3263 #WebLogicHost srv64 #WebLogicPort 7011 #PathTrim /weblogic Debug ALL DebugConfigInfo ON WLLogFile C:\wlproxy.log </Location> <IfModule mod_weblogic.c> #WebLogicCluster 192.168.111.159:3263,192.168.111.161:3263 MatchExpression /Aris WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /Admin WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /agEncoder WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /agx WeblogicCluster=192.168.111.155:3262,192.168.111.156:3262 MatchExpression /agComposer WeblogicCluster=192.168.111.159:3263,192.168.111.161:3263 MatchExpression /CCM12B5 WeblogicCluster=192.168.111.154:3264,192.168.111.157:3264 MatchExpression /agSingals WeblogicCluster=192.168.111.159:3263,192.168.111.161:3263 KeepAliveEnabled ON KeepAliveSecs 15 ConnectTimeoutSecs 1800 EnforceBasicConstraints OFF </IfModule> DavLockDB /DavLock <Location /agComposer/templates> Dav On <Limit PROPFIND PUT POST DELETE PROPPATCH MKCOL COPY MOVE LOCK UNLOCK> Allow from localhost 192.168.111.159 192.168.111.161 </Limit> </Location> <Location /agComposer/documents> Dav On <Limit PROPFIND PUT POST DELETE PROPPATCH MKCOL COPY MOVE LOCK UNLOCK> Allow from localhost 192.168.111.159 192.168.111.161 </Limit> </Location> <Location /agComposer/reports> Dav On <Limit PROPFIND PUT POST DELETE PROPPATCH MKCOL COPY MOVE LOCK UNLOCK> Allow from localhost 192.168.111.159 192.168.111.161 </Limit> </Location> Alias /agComposer/ "z:/" <Directory "z:/"> Options Indexes MultiViews AllowOverride None Order allow,deny Allow from all </Directory> </VirtualHost>


httd-ssl.conf is as below


# # This is the Apache server configuration file providing SSL support. # It contains the configuration directives to instruct the server how to # serve pages over an https connection. For detailing information about these # directives see <URL:http://httpd.apache.org/docs/2.2/mod/mod_ssl.html> # # Do NOT simply read the instructions in here without understanding # what they do. They're here only as hints or reminders. If you are unsure # consult the online docs. You have been warned. # # # Pseudo Random Number Generator (PRNG): # Configure one or more sources to seed the PRNG of the SSL library. # The seed data should be of good random quality. # WARNING! On some platforms /dev/random blocks if not enough entropy # is available. This means you then cannot use the /dev/random device # because it would lead to very long connection times (as long as # it requires to make more entropy available). But usually those # platforms additionally provide a /dev/urandom device which doesn't # block. So, if available, use this one instead. Read the mod_ssl User # Manual for more details. # SSLRandomSeed startup builtin SSLRandomSeed connect builtin #SSLRandomSeed startup file:/dev/random 512 #SSLRandomSeed startup file:/dev/urandom 512 #SSLRandomSeed connect file:/dev/random 512 #SSLRandomSeed connect file:/dev/urandom 512 # # When we also provide SSL we have to listen to the # standard HTTP port (see above) and to the HTTPS port # # Note: Configurations that use IPv6 but not IPv4-mapped addresses need two # Listen directives: "Listen [::]:443" and "Listen 0.0.0.0:443" # Listen 443 ## ## SSL Global Context ## ## All SSL configuration in this context applies both to ## the main server and all SSL-enabled virtual hosts. ## # # Some MIME-types for downloading Certificates and CRLs # AddType application/x-x509-ca-cert .crt AddType application/x-pkcs7-crl .crl # Pass Phrase Dialog: # Configure the pass phrase gathering process. # The filtering dialog program (`builtin' is a internal # terminal dialog) has to provide the pass phrase on stdout. SSLPassPhraseDialog builtin # Inter-Process Session Cache: # Configure the SSL Session Cache: First the mechanism # to use and second the expiring timeout (in seconds). #SSLSessionCache "dbm:C:/apache22/logs/ssl_scache" #SSLSessionCache "shmcb:C:/apache22/logs/ssl_scache(512000)" #SSLSessionCacheTimeout 300 SSLSessionCache "shmcb:C:/apache22/logs/ssl_scache(1024000)" SSLSessionCacheTimeout 900 # Semaphore: # Configure the path to the mutual exclusion semaphore the # SSL engine uses internally for inter-process synchronization. SSLMutex default ## ## SSL Virtual Host Context ## DocumentRoot "C:/apache22/htdocs" <VirtualHost _default_:443> # General setup for the virtual host ServerName ptts.agi.com:443 ServerAdmin admin@agi.com ErrorLog "C:/apache22/logs/error.log" TransferLog "C:/apache22/logs/access.log" <IfModule mod_weblogic.c> #WebLogicCluster 192.168.111.159:3263,192.168.111.161:3263 MatchExpression /Aris WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /Admin WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /agEncoder WeblogicCluster=192.168.111.149:3261,192.168.111.151:3261 MatchExpression /agx WeblogicCluster=192.168.111.155:3262,192.168.111.156:3262 MatchExpression /agComposer WeblogicCluster=192.168.111.159:3263,192.168.111.161:3263 MatchExpression /agSingals WeblogicCluster=192.168.111.159:3263,192.168.111.161:3263 #MatchExpression /CCM12B5 WeblogicCluster=192.168.111.154:3264,192.168.111.157:3264 #MatchExpression /CCM12B5 WeblogicHost=192.168.111.154|Port=3264 #MatchExpression /Aris WeblogicHost=192.168.111.149|Port=3261 #MatchExpression /Admin WeblogicHost=192.168.111.149|Port=3261 #WebLogicCluster 192.168.111.159:3263,192.168.111.161:3263 KeepAliveEnabled ON KeepAliveSecs 15 ConnectTimeoutSecs 1800 </IfModule> <Location /web> SetHandler weblogic-handler </Location> # SSL Engine Switch: # Enable/Disable SSL for this virtual host. SSLEngine on # SSL Cipher Suite: # List the ciphers that the client is permitted to negotiate. # See the mod_ssl documentation for a complete list. SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL # Server Certificate: # Point SSLCertificateFile at a PEM encoded certificate. If # the certificate is encrypted, then you will be prompted for a # pass phrase. Note that a kill -HUP will prompt again. Keep # in mind that if you have both an RSA and a DSA certificate you # can configure both in parallel (to also allow the use of DSA # ciphers, etc.) SSLCertificateFile "C:/apache22/conf/ssl.crt/server.crt" #SSLCertificateFile "C:/apache22/conf/server-dsa.crt" # Server Private Key: # If the key is not combined with the certificate, use this # directive to point at the key file. Keep in mind that if # you've both a RSA and a DSA private key you can configure # both in parallel (to also allow the use of DSA ciphers, etc.) SSLCertificateKeyFile "C:/apache22/conf/ssl.key/server.key" #SSLCertificateKeyFile "C:/apache22/conf/server-dsa.key" # Server Certificate Chain: # Point SSLCertificateChainFile at a file containing the # concatenation of PEM encoded CA certificates which form the # certificate chain for the server certificate. Alternatively # the referenced file can be the same as SSLCertificateFile # when the CA certificates are directly appended to the server # certificate for convinience. #SSLCertificateChainFile "C:/apache22/conf/server-ca.crt" # Certificate Authority (CA): # Set the CA certificate verification path where to find CA # certificates for client authentication or alternatively one # huge file containing all of them (file must be PEM encoded) # Note: Inside SSLCACertificatePath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCACertificatePath "C:/apache22/conf/ssl.crt" #SSLCACertificateFile "C:/apache22/conf/ssl.crt/ca-bundle.crt" # Certificate Revocation Lists (CRL): # Set the CA revocation path where to find CA CRLs for client # authentication or alternatively one huge file containing all # of them (file must be PEM encoded) # Note: Inside SSLCARevocationPath you need hash symlinks # to point to the certificate files. Use the provided # Makefile to update the hash symlinks after changes. #SSLCARevocationPath "C:/apache22/conf/ssl.crl" #SSLCARevocationFile "C:/apache22/conf/ssl.crl/ca-bundle.crl" # Client Authentication (Type): # Client certificate verification type and depth. Types are # none, optional, require and optional_no_ca. Depth is a # number which specifies how deeply to verify the certificate # issuer chain before deciding the certificate is not valid. #SSLVerifyClient require #SSLVerifyDepth 10 # Access Control: # With SSLRequire you can do per-directory access control based # on arbitrary complex boolean expressions containing server # variable checks and other lookup directives. The syntax is a # mixture between C and Perl. See the mod_ssl documentation # for more details. #<Location /> #SSLRequire ( %{SSL_CIPHER} !~ m/^(EXP|NULL)/ \ # and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \ # and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \ # and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \ # and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20 ) \ # or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/ #</Location> # SSL Engine Options: # Set various options for the SSL engine. # o FakeBasicAuth: # Translate the client X.509 into a Basic Authorisation. This means that # the standard Auth/DBMAuth methods can be used for access control. The # user name is the `one line' version of the client's X.509 certificate. # Note that no password is obtained from the user. Every entry in the user # file needs this password: `xxj31ZMTZzkVA'. # o ExportCertData: # This exports two additional environment variables: SSL_CLIENT_CERT and # SSL_SERVER_CERT. These contain the PEM-encoded certificates of the # server (always existing) and the client (only existing when client # authentication is used). This can be used to import the certificates # into CGI scripts. # o StdEnvVars: # This exports the standard SSL/TLS related `SSL_*' environment variables. # Per default this exportation is switched off for performance reasons, # because the extraction step is an expensive operation and is usually # useless for serving static content. So one usually enables the # exportation for CGI and SSI requests only. # o StrictRequire: # This denies access when "SSLRequireSSL" or "SSLRequire" applied even # under a "Satisfy any" situation, i.e. when it applies access is denied # and no other module can change it. # o OptRenegotiate: # This enables optimized SSL connection renegotiation handling when SSL # directives are used in per-directory context. #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire <FilesMatch "\.(cgi|shtml|phtml|php)$"> SSLOptions +StdEnvVars </FilesMatch> <Directory "C:/apache22/cgi-bin"> SSLOptions +StdEnvVars </Directory> # SSL Protocol Adjustments: # The safe and default but still SSL/TLS standard compliant shutdown # approach is that mod_ssl sends the close notify alert but doesn't wait for # the close notify alert from client. When you need a different shutdown # approach you can use one of the following variables: # o ssl-unclean-shutdown: # This forces an unclean shutdown when the connection is closed, i.e. no # SSL close notify alert is send or allowed to received. This violates # the SSL/TLS standard but is needed for some brain-dead browsers. Use # this when you receive I/O errors because of the standard approach where # mod_ssl sends the close notify alert. # o ssl-accurate-shutdown: # This forces an accurate shutdown when the connection is closed, i.e. a # SSL close notify alert is send and mod_ssl waits for the close notify # alert of the client. This is 100% SSL/TLS standard compliant, but in # practice often causes hanging connections with brain-dead browsers. Use # this only for browsers where you know that their SSL implementation # works correctly. # Notice: Most problems of broken clients are also related to the HTTP # keep-alive facility, so you usually additionally want to disable # keep-alive for those clients, too. Use variable "nokeepalive" for this. # Similarly, one has to force some clients to use HTTP/1.0 to workaround # their broken HTTP/1.1 implementation. Use variables "downgrade-1.0" and # "force-response-1.0" for this. #BrowserMatch ".*MSIE.*" \ SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 # Per-Server Logging: # The home of a custom SSL log file. Use this when you want a # compact non-error SSL logfile on a virtual host basis. CustomLog "C:/apache22/logs/ssl_request.log" \ "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" </VirtualHost>

After some time there is an error saying

[Wed Jul 29 20:23:47 2009] [error] READ_ERROR_FROM_SERVER [os error=10054, line 200 of ../nsapi/Reader.cpp]: socket read failure
[Wed Jul 29 20:23:48 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.161:3263
[Wed Jul 29 20:23:48 2009] [error] READ_ERROR_FROM_SERVER [os error=10054, line 200 of ../nsapi/Reader.cpp]: socket read failure
[Wed Jul 29 20:23:48 2009] [error] READ_ERROR_FROM_SERVER [os error=10054, line 200 of ../nsapi/Reader.cpp]: socket read failure
[Wed Jul 29 20:23:48 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.161:3263
[Wed Jul 29 20:23:49 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.161:3263
[Wed Jul 29 20:23:49 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.159:3263
[Wed Jul 29 20:23:50 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.161:3263
[Wed Jul 29 20:23:51 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.159:3263
[Wed Jul 29 20:23:52 2009] [error] CONNECTION_REFUSED [os error=0, line 1732 of ../nsapi/URL.cpp]: Error connecting to host 192.168.111.161:3263



Please suggest me what could be the problme

Thanks and Regards,
RamkumarMP

Hi Mark,
ThanQ very much.. Now the warning message is not coming by giving the run command to start jboss as below

run -c <folder name of the server> -b <hostname or IP address of the machine> -u 224.0.0.1

Thanks
RamkumarMP