[JBoss JIRA] Created: (JBAS-7736) weld-numberguess example doesn't work with jboss-6.0.0.M2 in cluster
5:04 a.m.
weld-numberguess example doesn't work with jboss-6.0.0.M2 in cluster
--------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description how
to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
10:33 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) weld-numberguess example doesn't work with jboss-6.0.0.M2 in cluster
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-7736:
----------------------------------------
As I experiment with this, the webapp isn't using the clustered session manager; it
acts like <distributable/> isn't in web.xml at all. I'm looking into
deployer/metadata issues, as which session manager is used is all metadata-driven.
weld-numberguess example doesn't work with jboss-6.0.0.M2 in
cluster
--------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
11:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) weld-numberguess example doesn't work with jboss-6.0.0.M2 in cluster
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-7736:
----------------------------------------
This is due to the following in MergedJBossWebMetaDataDeployer.deploy()
// Augment with meta data from fragments and annotations from the corresponding
JAR
for (String jar : order)
{
WebFragmentMetaData webFragmentMetaData = webFragments.get(jar);
if (webFragmentMetaData == null)
{
webFragmentMetaData = new WebFragmentMetaData();
}
key = AnnotationMetaDataDeployer.WEB_ANNOTATED_ATTACHMENT_NAME + ":" +
jar;
WebMetaData jarAnnotatedMetaData = unit.getAttachment(key, WebMetaData.class);
if ((isComplete || webFragmentMetaData.isMetadataComplete()) &&
jarAnnotatedMetaData != null)
{
// Discard @WebFilter, @WebListener and @WebServlet
jarAnnotatedMetaData.setFilters(null);
jarAnnotatedMetaData.setFilterMappings(null);
jarAnnotatedMetaData.setListeners(null);
jarAnnotatedMetaData.setServlets(null);
jarAnnotatedMetaData.setServletMappings(null);
}
if (jarAnnotatedMetaData != null)
{
// Merge annotations corresponding to the JAR
webFragmentMetaData.augment(jarAnnotatedMetaData, null, true);
}
// Merge fragment meta data according to the conflict rules
try
{
mergedFragmentMetaData.augment(webFragmentMetaData, specMetaData, false); //
PROBLEM IS HERE!!!
}
catch (Exception e)
{
DeploymentException.rethrowAsDeploymentException("Deployment error
processing fragment for JAR: " + jar, e);
}
}
The line marked above with // PROBLEM IS HERE!!! results in this, which clears the
distributable status from specMetaData:
public void augment(WebCommonMetaData webFragmentMetaData, WebCommonMetaData
webMetaData, boolean resolveConflicts)
{
// Distributable
if (!resolveConflicts && webFragmentMetaData.getDistributable() == null
&& webMetaData != null)
{
webMetaData.setDistributable(null);
}
weld-numberguess example doesn't work with jboss-6.0.0.M2 in
cluster
--------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
12:43 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry updated JBAS-7736:
-----------------------------------
Summary: Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib (was: weld-numberguess example doesn't work with
jboss-6.0.0.M2 in cluster)
Component/s: Web (Tomcat) service
Fix Version/s: JBossAS-6.0.0.M2
Priority: Blocker (was: Major)
This really has nothing to do with Weld; the problem will happen with any webapp with jars
in WEB-INF/lib. The problem is the deploy method in it's handling of such jars
1) if the jar *does not contain a web.xml fragment* it creates a new WebFragmentMetaData()
which has getDistributable() == null.
2) augments that metadata object with information from annotations, none of which are
related to distributable behavior
3) Augments the specMetaData with the values from that WebFragmentMetaData.
At least a temporary fix is, to set the distributable property on the new
WebFragmentMetaData() to the value of the specMetaData. Only do this for
WebFragmentMetaData created in this method as placeholders for annotation data; if the
WebFragmentMetaData came from an actual web.xml fragment, the fragment's value must be
respected.
Perhaps a better idea is to also catch cases where there is a) no web.xml fragment and b)
no jarAnnotatedMetaData and in those cases skip the jar altogether. That will help avoid
other subtle bugs like this one. But that's a more far-reaching change that I
don't want to introduce right before M2, so I'll stick to the temporary fix above
for M2 and open a subtask for M3.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
1:18 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry reassigned JBAS-7736:
--------------------------------------
Assignee: Brian Stansberry
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
1:47 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-7736:
--------------------------------------
I see. II think that without a fragment (but with annotations), the default is a problem.
Since the fragment's value only overrides when it is not present, it could be changed
to something like:
if (webFragmentMetaData == null)
{
webFragmentMetaData = new WebFragmentMetaData();
// Add non overriding distributable flag
webFragmentMetaData.setDistributable(new EmptyMetaData());
}
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
1:56 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry resolved JBAS-7736.
------------------------------------
Resolution: Done
Fixed as described in my "temporary fix" comment above. Thank you very much,
Martin, for the report.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
2:17 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Brian Stansberry commented on JBAS-7736:
----------------------------------------
Missed your comment, Remy. That's pretty close to what I did; I used
specMetaData.getDistributable() as the value. In trunk I'll change it to your way; for
M2 I don't want to retest.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
2:29 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Remy Maucherat commented on JBAS-7736:
--------------------------------------
I changed it already in trunk. It does the same but it's clearer.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
1:57 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Martin Gencur closed JBAS-7736.
-------------------------------
Verified with current build (from
http://reports.qa.atl.jboss.com/release_tests/binaries/JBossAS/jboss-6.0....) updated
with WELD 1.0.1.CR1.
Clustering works fine!
Closing.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
1:59 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-7736) Webapp's <distributable/> configuration disabled if war includes jars in WEB-INF/lib
[
https://jira.jboss.org/jira/browse/JBAS-7736?page=com.atlassian.jira.plug...
]
Martin Gencur commented on JBAS-7736:
-------------------------------------
Verified with Weld 1.0.1 CR2 of course.
Webapp's <distributable/> configuration disabled if war
includes jars in WEB-INF/lib
------------------------------------------------------------------------------------
Key: JBAS-7736
URL: https://jira.jboss.org/jira/browse/JBAS-7736
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-6.0.0.M2
Environment: JBoss AS 6.0.0.M2, Weld 1.0.1 CR2
Reporter: Martin Gencur
Assignee: Brian Stansberry
Priority: Blocker
Fix For: JBossAS-6.0.0.M2
Session replication doesn't work in WELD using JBoss AS 6.0.0.M2. More description
how to run weld-numberguess example in cluster is in linked issue (except using JBoss AS
6.0.0.M2 instead of 6.0.0.M1).
Additional tested configurations:
1) JBoss 6.0.0.M1 updated with current trunk of WELD (works fine !!)
2) JBoss 6.0.0.M2 updated with current trunk of WELD - doesn't work, after going to
second browser to test session replication the application starts from scratch and
doesn't continue with current session. The jboss AS's console doesn't output
any error message
3) JBoss 6.0.0.M2 updated with WELD 1.0.1 CR2 - the same as 2)
--
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
6016
days inactive
6017
days old
10 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
Martin Gencur (JIRA)
-
Remy Maucherat (JIRA)