2:39 p.m.
[
https://jira.jboss.org/jira/browse/MODCLUSTER-152?page=com.atlassian.jira...
]
Gábor Auth commented on MODCLUSTER-152:
----------------------------------------
As I've wrote, the undeploy is perfect, the "bug" exists only when I deploy
the JAR:
2010-05-12 13:29:30,777 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer]
(HDScanner) Encountered deployment
AbstractVFSDeploymentContext@399098209{vfszip:/opt/jboss-5.1.0.GA/server/esb/deploy/Test-1.0.0.jar/}
2010-05-12 13:29:30,777 INFO [org.jboss.ejb3.deployers.Ejb3DependenciesDeployer]
(HDScanner) Encountered deployment
AbstractVFSDeploymentContext@399098209{vfszip:/opt/jboss-5.1.0.GA/server/esb/deploy/Test-1.0.0.jar/}
2010-05-12 13:29:30,789 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Created
KernelDeployment for: Test-1.0.0.jar
2010-05-12 13:29:30,789 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
installing bean: jboss.j2ee:jar=Test-1.0.0.jar,name=TestBean,service=EJB3
2010-05-12 13:29:30,789 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) with
dependencies:
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and
demands:
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jboss.ejb:service=EJBTimerService
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) and
supplies:
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:TestBean/local-hu.javaforum.modcluster.webservice.test.service.Test
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:hu.javaforum.modcluster.webservice.test.service.Test
2010-05-12 13:29:30,790 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
Class:hu.javaforum.modcluster.webservice.test.service.Test
2010-05-12 13:29:30,791 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)
jndi:TestBean/local
2010-05-12 13:29:30,791 INFO [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added
bean(jboss.j2ee:jar=Test-1.0.0.jar,name=TestBean,service=EJB3) to KernelDeployment of:
Test-1.0.0.jar
2010-05-12 13:29:30,793 INFO [org.jboss.ejb3.endpoint.deployers.EJB3EndpointDeployer]
(HDScanner) Deploy
AbstractBeanMetaData@55169568{name=jboss.j2ee:jar=Test-1.0.0.jar,name=TestBean,service=EJB3_endpoint
bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container]
constructor=null autowireCandidate=true}
2010-05-12 13:29:30,887 INFO [org.jboss.ejb3.session.SessionSpecContainer] (HDScanner)
Starting jboss.j2ee:jar=Test-1.0.0.jar,name=TestBean,service=EJB3
2010-05-12 13:29:30,888 INFO [org.jboss.ejb3.EJBContainer] (HDScanner) STARTED EJB:
hu.javaforum.modcluster.webservice.test.service.TestBean ejbName: TestBean
2010-05-12 13:29:30,900 INFO
[org.jboss.ejb3.proxy.impl.jndiregistrar.JndiSessionRegistrarBase] (HDScanner) Binding the
following Entries in Global JNDI:
hu.javaforum.modcluster.webservice.test.service.Test - EJB3.x Default Local
Business Interface
TestBean/local-hu.javaforum.modcluster.webservice.test.service.Test - EJB3.x Local
Business Interface
2010-05-12 13:29:31,025 INFO [org.jboss.wsf.stack.jbws.WSDLFilePublisher] (HDScanner)
WSDL published to:
file:/opt/jboss-5.1.0.GA/server/esb/data/wsdl/Test-1.0.0.jar/TestBeanService450762680237527502.wsdl
2010-05-12 13:29:31,032 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry]
(HDScanner) register: jboss.ws:context=ModCluster-test,endpoint=TestBean
2010-05-12 13:29:31,060 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment]
(HDScanner) deploy, ctxPath=/ModCluster-test
2010-05-12 13:29:31,085 DEBUG [org.jboss.modcluster.CatalinaEventHandler] (HDScanner)
Start context [/ModCluster-test] in host [localhost]
2010-05-12 13:29:31,086 TRACE [org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler]
(HDScanner) Sending command
[org.jboss.modcluster.mcmp.impl.DefaultMCMPRequest{requestType=ENABLE-APP,wildcard=false,jvmRoute=10.8.27.10,parameters={Alias=localhost,
Context=/ModCluster-test}}] to proxy [10.8.27.5:8080]
2010-05-12 13:29:31,098 WARNING [javax.enterprise.resource.webcontainer.jsf.config]
(HDScanner) Unable to process deployment descriptor for context
'/ModCluster-test'
2010-05-12 13:29:31,100 INFO [javax.enterprise.resource.webcontainer.jsf.config]
(HDScanner) Initializing Mojarra (1.2_12-b01-FCS) for context '/ModCluster-test'
...and I've seen these lines in the access.log of the node1 JBoss (output of the
AccessLogValve):
client - - [12/May/2010:13:19:14 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
client - - [12/May/2010:13:19:14 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
client - - [12/May/2010:13:19:14 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 404 1020
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 404 1020
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032
...and I've seen these lines in the access.log of the Apache:
client - - [12/May/2010:13:29:30 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:30 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:30 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
node1 - - [12/May/2010:13:29:31 +0200] "ENABLE-APP / HTTP/1.0" 200 -
"-" "ClusterListener/1.0"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 404 1020 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 404 1020 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
client - - [12/May/2010:13:29:31 +0200] "GET /ModCluster-test/service?wsdl
HTTP/1.1" 200 2032 "-" "Java/1.6.0_17"
Redeploy EAR with @WebService annotated beans cause 404
-------------------------------------------------------
Key: MODCLUSTER-152
URL: https://jira.jboss.org/jira/browse/MODCLUSTER-152
Project: mod_cluster
Issue Type: Bug
Affects Versions: 1.0.3.GA, 1.1.0.CR1
Environment: Linux hostname 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:01:26 EDT 2010
x86_64 x86_64 x86_64 GNU/Linux
JBoss 5.1.0.GA
ModCluster 1.3.0.GA
Reporter: Gábor Auth
Assignee: Jean-Frederic Clere
Attachments: Common-test.zip, Test-1.0.0.jar
I've tested a ModCluster 1.0.3.GA with the load-demo.war, and it works; I've
started a JMeter testcase with 200 threads, then I've stopped and started the one of
the two AS node; I've undeployed in the node1 the load-demo.war, then I've
deployed again the load-demo.war: not found any errors, it works, except some CacheManager
NPE while the SessionCache is synchronizing:
14:16:28,261 ERROR [load-demo] Caught exception rolling back transaction
java.lang.NullPointerException
at
org.jboss.web.tomcat.service.session.JBossCacheManager.loadSession(JBossCacheManager.java:1857)
at
org.jboss.web.tomcat.service.session.JBossCacheManager.findSession(JBossCacheManager.java:489)
).
I've created a simple "echo" EJB with these annotations:
@MTOM
@Local
@WebService
@Stateless(mappedName =
"hu.javaforum.modcluster.webservice.test.service.Test")
@LocalBinding(jndiBinding =
"hu.javaforum.modcluster.webservice.test.service.Test")
@WebContext(contextRoot = "/ModCluster-test", urlPattern =
"/service")
@SOAPBinding(style = SOAPBinding.Style.DOCUMENT, parameterStyle =
SOAPBinding.ParameterStyle.WRAPPED)
public class TestBean implements Test
{
@Override
@TransactionAttribute(TransactionAttributeType.SUPPORTS)
public String process(@WebParam(name = "request") String request)
{
return request;
}
}
I've created a JAR, and I've deployed it to the cluster nodes, it works, I've
started a JMeter and soapUI tests, it works.
Then I've undeployed this JAR in the node1, it works, all test passes.
Then I've deployed again (or redeploy) this JAR in the node1, and I've seen some
HTTP/404 error in the reply:
HTTP Status 404 - /ModCluster-test/service
[...]
The requested resource (/ModCluster-test/service) is not available.
I've seen it in the httpd's access_log:
x.x.x.x - - [07/May/2010:14:26:20 +0200] "POST /ModCluster-test/service
HTTP/1.1" 404 1056 "-" "Jakarta Commons-HttpClient/3.1"
And I've seen it in the access.log in the node1:
x.x.x.x - - [07/May/2010:14:26:20 +0200] "POST /ModCluster-test/service
HTTP/1.1" 404 1056
It is bug? :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira