getting error /j_spring_security_check HTTP/1.1" 302 -
by Mohan Singh
Hi,
I have configured Apache 2.2 on the top of two JBOSS server
using mod_jk.
When I hit the URL of application through apache server
http://localhost/Application then it alternatively get the login page from
the 2 JBOSS servers That's OK.
But when I am login into my application then I am getting error
/j_spring_security_check HTTP/1.1" 302 - in access.log file of apache
server.
One more thing.. If I stop any one JBOSS server then I am able
to login through apache server in my application and it works fine, But I
want both JBOSS server
should be running.
The configuration in worker.properties 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.12.245
worker.node1.type=ajp13
worker.node1.lbfactor=1
worker.node1.prepost_timeout=10000 #Not required if using ping_mode=A
worker.node1.connect_timeout=10000 #Not required if using ping_mode=A
worker.node1.ping_mode=A #As of mod_jk 1.2.27
# 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.2.19
worker.node2.type=ajp13
worker.node2.lbfactor=1
worker.node2.prepost_timeout=10000 #Not required if using ping_mode=A
worker.node2.connect_timeout=10000 #Not required if using ping_mode=A
worker.node2.ping_mode=A #As of mod_jk 1.2.27
# 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
In server.xml file I have added
JBOSS1: <Engine name="jboss.web" defaultHost="localhost"
jvmRoute="node1">
JBOSS2 : <Engine name="jboss.web" defaultHost="localhost" jvmRoute="node2">
Please help me if I am doing any mistake
Thanks & Regards
Mohan Singh
12 years, 8 months
[JBoss JIRA] Resolved: (MODCLUSTER-249) Doubled jvmRoute value in JSESSIONID
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-249?page=com.atlassian.jira.pl... ]
Paul Ferraro resolved MODCLUSTER-249.
-------------------------------------
Resolution: Rejected
This is actually an AS7 session id generation bug, not a mod_cluster bug. See AS7-1639.
> Doubled jvmRoute value in JSESSIONID
> ------------------------------------
>
> Key: MODCLUSTER-249
> URL: https://issues.jboss.org/browse/MODCLUSTER-249
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Michal Babacek
> Assignee: Paul Ferraro
> Labels: as7, mod_cluster
>
> If we force Mod_cluster to use an explicit jvmRoute by editing *standalone-ha.xml* in this way:
> {code:xml}
> <server xmlns="urn:jboss:domain:1.0">
> ...
> <extensions>
> ...
> </extensions>
> <system-properties>
> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/>
> </system-properties>
> <management>
> ...
> {code}
> *JSESSIONID* returned as a cookie to a client contains this (note the doubled jvmRoute):
> {noformat}
> Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node
> {noformat}
> On the other side, perf22node log says:
> {noformat}
> [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node
> {noformat}
> I tried to modify the [SystemPropertyJvmRouteFactory.java|http://anonsvn.jboss.org/repos/mod_clu...] so as to know what jvmRoute it gets:
> {code:java}
> public String createJvmRoute(Engine engine)
> {
> final String defaultJvmRoute = this.factory.createJvmRoute(engine);
> final String property = this.property;
>
> PrivilegedAction<String> action = new PrivilegedAction<String>()
> {
> public String run()
> {
> String jvmRoute = System.getProperty(property, defaultJvmRoute);
> log.info("Info HELL: "+jvmRoute);
> return jvmRoute;
> }
> };
>
> return AccessController.doPrivileged(action);
> }
> {code}
> And the result in perf22node log says:
> {noformat}
> [org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node
> {noformat}
> So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Updated: (MODCLUSTER-249) Doubled jvmRoute value in JSESSIONID
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-249?page=com.atlassian.jira.pl... ]
Michal Babacek updated MODCLUSTER-249:
--------------------------------------
Priority: Major (was: Blocker)
> Doubled jvmRoute value in JSESSIONID
> ------------------------------------
>
> Key: MODCLUSTER-249
> URL: https://issues.jboss.org/browse/MODCLUSTER-249
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Michal Babacek
> Assignee: Paul Ferraro
> Labels: as7, mod_cluster
>
> If we force Mod_cluster to use an explicit jvmRoute by editing *standalone-ha.xml* in this way:
> {code:xml}
> <server xmlns="urn:jboss:domain:1.0">
> ...
> <extensions>
> ...
> </extensions>
> <system-properties>
> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/>
> </system-properties>
> <management>
> ...
> {code}
> *JSESSIONID* returned as a cookie to a client contains this (note the doubled jvmRoute):
> {noformat}
> Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node
> {noformat}
> On the other side, perf22node log says:
> {noformat}
> [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node
> {noformat}
> I tried to modify the [SystemPropertyJvmRouteFactory.java|http://anonsvn.jboss.org/repos/mod_clu...] so as to know what jvmRoute it gets:
> {code:java}
> public String createJvmRoute(Engine engine)
> {
> final String defaultJvmRoute = this.factory.createJvmRoute(engine);
> final String property = this.property;
>
> PrivilegedAction<String> action = new PrivilegedAction<String>()
> {
> public String run()
> {
> String jvmRoute = System.getProperty(property, defaultJvmRoute);
> log.info("Info HELL: "+jvmRoute);
> return jvmRoute;
> }
> };
>
> return AccessController.doPrivileged(action);
> }
> {code}
> And the result in perf22node log says:
> {noformat}
> [org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node
> {noformat}
> So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Updated: (MODCLUSTER-249) Doubled jvmRoute value in JSESSIONID
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-249?page=com.atlassian.jira.pl... ]
Michal Babacek updated MODCLUSTER-249:
--------------------------------------
Priority: Blocker (was: Major)
> Doubled jvmRoute value in JSESSIONID
> ------------------------------------
>
> Key: MODCLUSTER-249
> URL: https://issues.jboss.org/browse/MODCLUSTER-249
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Michal Babacek
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: as7, mod_cluster
>
> If we force Mod_cluster to use an explicit jvmRoute by editing *standalone-ha.xml* in this way:
> {code:xml}
> <server xmlns="urn:jboss:domain:1.0">
> ...
> <extensions>
> ...
> </extensions>
> <system-properties>
> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/>
> </system-properties>
> <management>
> ...
> {code}
> *JSESSIONID* returned as a cookie to a client contains this (note the doubled jvmRoute):
> {noformat}
> Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node
> {noformat}
> On the other side, perf22node log says:
> {noformat}
> [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node
> {noformat}
> I tried to modify the [SystemPropertyJvmRouteFactory.java|http://anonsvn.jboss.org/repos/mod_clu...] so as to know what jvmRoute it gets:
> {code:java}
> public String createJvmRoute(Engine engine)
> {
> final String defaultJvmRoute = this.factory.createJvmRoute(engine);
> final String property = this.property;
>
> PrivilegedAction<String> action = new PrivilegedAction<String>()
> {
> public String run()
> {
> String jvmRoute = System.getProperty(property, defaultJvmRoute);
> log.info("Info HELL: "+jvmRoute);
> return jvmRoute;
> }
> };
>
> return AccessController.doPrivileged(action);
> }
> {code}
> And the result in perf22node log says:
> {noformat}
> [org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node
> {noformat}
> So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Moved: (MODCLUSTER-249) Doubled jvmRoute value in JSESSIONID
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-249?page=com.atlassian.jira.pl... ]
Michal Babacek moved JBPAPP-7067 to MODCLUSTER-249:
---------------------------------------------------
Project: mod_cluster (was: JBoss Enterprise Application Platform)
Key: MODCLUSTER-249 (was: JBPAPP-7067)
Affects Version/s: (was: EAP 6.0.0 Alpha)
Component/s: (was: mod_cluster)
Security: (was: JBoss Internal)
Fix Version/s: (was: EAP 6.0.0)
Docs QE Status: (was: NEW)
> Doubled jvmRoute value in JSESSIONID
> ------------------------------------
>
> Key: MODCLUSTER-249
> URL: https://issues.jboss.org/browse/MODCLUSTER-249
> Project: mod_cluster
> Issue Type: Bug
> Reporter: Michal Babacek
> Assignee: Paul Ferraro
> Labels: eap6, mod_cluster
>
> If we force Mod_cluster to use an explicit jvmRoute by editing *standalone-ha.xml* in this way:
> {code:xml}
> <server xmlns="urn:jboss:domain:1.0">
> ...
> <extensions>
> ...
> </extensions>
> <system-properties>
> <property name="jboss.mod_cluster.jvmRoute" value="perf22node"/>
> </system-properties>
> <management>
> ...
> {code}
> *JSESSIONID* returned as a cookie to a client contains this (note the doubled jvmRoute):
> {noformat}
> Session was created! JSESSIONID - R4PL5AAmojvW0zWd9Ddp86Qs.perf22node.perf22node
> {noformat}
> On the other side, perf22node log says:
> {noformat}
> [org.jboss.modcluster.ModClusterService] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Engine [jboss.web] will use jvmRoute: perf22node
> {noformat}
> I tried to modify the [SystemPropertyJvmRouteFactory.java|http://anonsvn.jboss.org/repos/mod_clu...] so as to know what jvmRoute it gets:
> {code:java}
> public String createJvmRoute(Engine engine)
> {
> final String defaultJvmRoute = this.factory.createJvmRoute(engine);
> final String property = this.property;
>
> PrivilegedAction<String> action = new PrivilegedAction<String>()
> {
> public String run()
> {
> String jvmRoute = System.getProperty(property, defaultJvmRoute);
> log.info("Info HELL: "+jvmRoute);
> return jvmRoute;
> }
> };
>
> return AccessController.doPrivileged(action);
> }
> {code}
> And the result in perf22node log says:
> {noformat}
> [org.jboss.modcluster.SystemPropertyJvmRouteFactory] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) Info HELL: perf22node
> {noformat}
> So it appears it is OK as far as SystemPropertyJvmRouteFactory goes...
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (MODCLUSTER-220) Extra REMOVE-APP event after failover
by Radoslav Husar (JIRA)
Extra REMOVE-APP event after failover
-------------------------------------
Key: MODCLUSTER-220
URL: https://issues.jboss.org/browse/MODCLUSTER-220
Project: mod_cluster
Issue Type: Enhancement
Reporter: Radoslav Husar
Assignee: Jean-Frederic Clere
Priority: Trivial
Trivial thing: I think there is an extra REMOVE-APP event happening after fail-over. The test scenario is simple - start a node with 6 context, kill the node and reconnect. The apps are unchanged but 5 are remembered as were and one is removed and added back? Since they happen at the same time it looks like it happens uselessly and can cause race condition.
{code}
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "INFO / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:18:34 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0"
...
127.0.0.1 - - [04/Apr/2011:19:19:03 +0200] "GET /SessionTest/SessionTestServlet? HTTP/1.1" 200 1 "-" "Jakarta Commons-HttpClient/3.1"
...
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "INFO / HTTP/1.0" 200 575 "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "CONFIG / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "ENABLE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "REMOVE-APP / HTTP/1.0" 200 - "-" "ClusterListener/1.0"
127.0.0.1 - - [04/Apr/2011:19:20:44 +0200] "STATUS / HTTP/1.0" 200 58 "-" "ClusterListener/1.0"
{code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months