[Clustering/JBoss] - jboss 4.0.2 + cluster is not working
by xps2nini2000
Hii All
Please help me .I am not able to see the apache_home/log/mod_jk.log.But when i say http://localhost/web-console , Http page not found comes. But in error.log i can see
File does not exist: C:/Program Files/Apache Group/Apache2/htdocs/WEB_CONSOLE
My uriworkers.property file is
| # Simple worker configuration file
|
| # Mount the Servlet context to the ajp13 worker
| /jmx-console=loadbalancer
| /jmx-console/*=loadbalancer
| /web-console=loadbalancer
| /web-console/*=loadbalancer
|
my workers.property file is
|
| # Define list of workers that will be used
| # for mapping requests
| # The configuration directives are valid
| # for the mod_jk version 1.2.18 and later
| #
| worker.list=loadbalancer,status
|
| # Define Node1
| # modify the host as your host IP or DNS name.
| worker.node1.port=8009
| worker.node1.host=192.168.81.14
| worker.node1.type=ajp13
| worker.node1.lbfactor=1
| # worker.node1.connection_pool_size=10 (1)
|
| # Define Node2
| # modify the host as your host IP or DNS name.
| worker.node2.port=8009
| worker.node2.host=192.168.81.29
| worker.node2.type=ajp13
| worker.node2.lbfactor=1
| # worker.node1.connection_pool_size=10 (1)
|
| # Load-balancing behaviour
| worker.loadbalancer.type=lb
| worker.loadbalancer.balance_workers=node1,node2
|
| # Status worker for managing load balancer
| worker.status.type=status
|
|
|
my mod-jk.conf i s
|
| # 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
| # Note: Changed from +ForwardURICompat.
| # See http://tomcat.apache.org/security-jk.html
| JkOptions +ForwardKeySize +ForwardURICompatUnparsed -ForwardDirectories
|
| # JkRequestLogFormat
| JkRequestLogFormat "%w %V %T"
|
| # Mount your applications
| JkMount /EILMT/* 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
| # Note: Replaced JkShmFile logs/jk.shm due to SELinux issues. Refer to
| # https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225452
| JkShmFile run/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>
|
And i hav made changes to server.xml and jboss-service.xml
Pleastell me what shud i do.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148995#4148995
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148995
17 years, 11 months
[Messaging, JMS & JBossMQ] - Re: How to access JBOSS by providing IP address
by aneesh62003
HI priya. My server.xml is attatched below.
| <Server>
|
| <!--APR library loader. Documentation at /docs/apr.html -->
|
|
|
| <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
|
|
| <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
|
|
|
| <Listener className="org.apache.catalina.core.JasperListener" />
|
|
|
| <!-- Use a custom version of StandardService that allows the
| connectors to be started independent of the normal lifecycle
| start to allow web apps to be deployed before starting the
| connectors.
| -->
|
|
|
| <Service name="jboss.web">
|
|
|
| <!-- A "Connector" represents an endpoint by which requests are received
| and responses are returned. Documentation at :
| Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
| Java AJP Connector: /docs/config/ajp.html
| APR (HTTP/AJP) Connector: /docs/apr.html
| Define a non-SSL HTTP/1.1 Connector on port 8080
| -->
|
|
|
| <Connector port="8080" address="${jboss.bind.address}"
| maxThreads="250" maxHttpHeaderSize="8192"
| emptySessionPath="true" protocol="HTTP/1.1"
| enableLookups="false" redirectPort="8443" acceptCount="100"
| connectionTimeout="20000" disableUploadTimeout="true" />
|
|
|
|
| <!-- Define a SSL HTTP/1.1 Connector on port 8443
| This connector uses the JSSE configuration, when using APR, the
| connector should be using the OpenSSL style configuration
| described in the APR documentation -->
| <!--
| <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
| maxThreads="150" scheme="https" secure="true"
| clientAuth="false" sslProtocol="TLS" />
| -->
|
| <!-- Define an AJP 1.3 Connector on port 8009 -->
|
|
|
| <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
| emptySessionPath="true" enableLookups="false" redirectPort="8443" />
|
|
| <Engine name="jboss.web" defaultHost="localhost">
|
|
|
| <!-- The JAAS based authentication and authorization realm implementation
| that is compatible with the jboss 3.2.x realm implementation.
| - certificatePrincipal : the class name of the
| org.jboss.security.auth.certs.CertificatePrincipal impl
| used for mapping X509[] cert chains to a Princpal.
| - allRolesMode : how to handle an auth-constraint with a role-name=*,
| one of strict, authOnly, strictAuthOnly
| + strict = Use the strict servlet spec interpretation which requires
| that the user have one of the web-app/security-role/role-name
| + authOnly = Allow any authenticated user
| + strictAuthOnly = Allow any authenticated user only if there are no
| web-app/security-roles
| -->
|
|
|
| <Realm className="org.jboss.web.tomcat.security.JBossSecurityMgrRealm"
| certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
| allRolesMode="authOnly"
| />
|
|
|
| <!-- A subclass of JBossSecurityMgrRealm that uses the authentication
| behavior of JBossSecurityMgrRealm, but overrides the authorization
| checks to use JACC permissions with the current java.security.Policy
| to determine authorized access.
| - allRolesMode : how to handle an auth-constraint with a role-name=*,
| one of strict, authOnly, strictAuthOnly
| + strict = Use the strict servlet spec interpretation which requires
| that the user have one of the web-app/security-role/role-name
| + authOnly = Allow any authenticated user
| + strictAuthOnly = Allow any authenticated user only if there are no
| web-app/security-roles
|
|
| <Realm className="org.jboss.web.tomcat.security.JaccAuthorizationRealm"
| certificatePrincipal="org.jboss.security.auth.certs.SubjectDNMapping"
| allRolesMode="authOnly"
| />
| -->
|
|
|
|
| <Host name="localhost" autoDeploy="false" deployOnStartup="false" deployXML="false"
| configClass="org.jboss.web.tomcat.security.config.JBossContextConfig"
| >
|
|
|
|
|
| <!-- Uncomment to enable request dumper. This Valve "logs interesting
| contents from the specified Request (before processing) and the
| corresponding Response (after processing). It is especially useful
| in debugging problems related to headers and cookies."
| -->
| <!--
| <Valve className="org.apache.catalina.valves.RequestDumperValve" />
| -->
|
| <!-- Access logger -->
| <!--
| <Valve className="org.apache.catalina.valves.AccessLogValve"
| prefix="localhost_access_log." suffix=".log"
| pattern="common" directory="${jboss.server.home.dir}/log"
| resolveHosts="false" />
| -->
|
| <!-- Uncomment to enable single sign-on across web apps
| deployed to this host. Does not provide SSO across a cluster.
|
| If this valve is used, do not use the JBoss ClusteredSingleSignOn
| valve shown below.
|
| A new configuration attribute is available beginning with
| release 4.0.4:
|
| cookieDomain configures the domain to which the SSO cookie
| will be scoped (i.e. the set of hosts to
| which the cookie will be presented). By default
| the cookie is scoped to "/", meaning the host
| that presented it. Set cookieDomain to a
| wider domain (e.g. "xyz.com") to allow an SSO
| to span more than one hostname.
| -->
| <!--
| <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
| -->
|
| <!-- Uncomment to enable single sign-on across web apps
| deployed to this host AND to all other hosts in the cluster.
|
| If this valve is used, do not use the standard Tomcat SingleSignOn
| valve shown above.
|
| Valve uses a JBossCache instance to support SSO credential
| caching and replication across the cluster. The JBossCache
| instance must be configured separately. By default, the valve
| shares a JBossCache with the service that supports HttpSession
| replication. See the "jboss-web-cluster-service.xml" file in the
| server/all/deploy directory for cache configuration details.
|
| Besides the attributes supported by the standard Tomcat
| SingleSignOn valve (see the Tomcat docs), this version also
| supports the following attributes:
|
| cookieDomain see above
|
| treeCacheName JMX ObjectName of the JBossCache MBean used to
| support credential caching and replication across
| the cluster. If not set, the default value is
| "jboss.cache:service=TomcatClusteringCache", the
| standard ObjectName of the JBossCache MBean used
| to support session replication.
| -->
| <!--
| <Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" />
| -->
|
| <!-- Check for unclosed connections and transaction terminated checks
| in servlets/jsps.
|
| Important: The dependency on the CachedConnectionManager
| in META-INF/jboss-service.xml must be uncommented, too
| -->
| <Valve className="org.jboss.web.tomcat.service.jca.CachedConnectionValve"
| cachedConnectionManagerObjectName="jboss.jca:service=CachedConnectionManager"
| transactionManagerObjectName="jboss:service=TransactionManager" />
|
| </Host>
|
| </Engine>
|
| </Service>
|
| </Server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148990#4148990
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148990
17 years, 11 months
[JNDI/Naming/Network] - Re: javax.naming.NoInitialContextException: Can't find prope
by kahzoo
InitialContext jndiContext = new InitialContext();
| System.out.println("Now looking up session bean " + jndiName + " ...");
| java.util.Hashtable properties = new java.util.Hashtable();
| properties.put(Context.PROVIDER_URL,"localhost:1099");
| properties.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
| properties.put("java.naming.rmi.security.manager", "yes");
| javax.naming.Context context = new javax.naming.InitialContext(properties);
| Object beanHomeRef
| = jndiContext.lookup(jndiName);
|
I wonder if the the last line really should be:
Object beanHomeRef
| = context.lookup(jndiName);
|
because when you construct jndiConext, you're not passing the properties as argument:
InitialContext jndiContext = new InitialContext();
rather you do that for context,
javax.naming.Context context = new javax.naming.InitialContext(properties);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148986#4148986
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4148986
17 years, 11 months