[JBoss JIRA] (JGRP-2024) Receiving messages out of order.
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2024?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2024:
--------------------------------
Any feedback, Dylan? Do you agree?
> Receiving messages out of order.
> --------------------------------
>
> Key: JGRP-2024
> URL: https://issues.jboss.org/browse/JGRP-2024
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: RedHat 6.7
> Java 1.8.0 Update 45
> Reporter: Dylan Turnbull
> Assignee: Bela Ban
> Fix For: 4.0
>
> Attachments: jGroups Unit Test.zip, JGroupsMessageTest.java, jGroupsTestReciever.java
>
>
> After splitting a file into smaller messages and send them down the channel the messages are received on the other side out of order.
> Below is a sample output:
> *+On the sender:+*
> Sending...
> Data Sent:
> Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy te
> -----------------------------------------------------
> Data Sent:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Sent:
> vived not only five centuries, but also the leap into electronic typesetting, re
> -----------------------------------------------------
> Data Sent:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passag
> *+On the receiver:+*
> Listening...
> Data Received:
> xt ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has sur
> -----------------------------------------------------
> Data Received:
> vived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularise
> -----------------------------------------------------
> Data Received:
> d in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
> Data Received:
> ftware like Aldus PageMaker including versions of Lorem Ipsum.Lorem Ipsum passages, and more recently with desktop publishing so
> -----------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-414) Allow the authentication in SecurityDomainTrustManager to be optional
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-414?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse commented on ELY-414:
--------------------------------------
In addition to this we also need to be able to control want and need client auth independently of the security domain.
> Allow the authentication in SecurityDomainTrustManager to be optional
> ---------------------------------------------------------------------
>
> Key: ELY-414
> URL: https://issues.jboss.org/browse/ELY-414
> Project: WildFly Elytron
> Issue Type: Task
> Components: SSL
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.1.0.Beta5
>
>
> Validating the certificate chain using the delegate trust manager must never be skipped but this change is to allow the authentication step to be flagged as optional.
> i.e. If for any reason the authentication fails silently allow it through so other authentication mechanisms can be tried.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-3456) Can not call method with generic type parameter with null value
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-3456?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-3456:
------------------------------------
Would anyone like to do any additional testing of the WFLY-6280 fix (see [https://github.com/jboss/jboss-el-api_spec/pull/18]), before we release 1.0.6.Final of org.jboss.spec.javax.el:jboss-el-api_3.0_spec?
If yes, we can discuss how to bring the change into your wildfly environment (probably build the jboss-el-api-spec change and wildfly). I'd like to release 1.0.6.Final soon, so if you intend to help test, please comment here so I know and can help you. If I don't hear back soon, I'll release 1.0.6.Final so you could also test a nightly WildFly build later.
> Can not call method with generic type parameter with null value
> ---------------------------------------------------------------
>
> Key: WFLY-3456
> URL: https://issues.jboss.org/browse/WFLY-3456
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.1.0.Final
> Reporter: Marcel Neuwohner
> Assignee: Farah Juma
> Fix For: 9.0.0.Alpha1
>
>
> If you call a method with a generic type parameter from EL with null as parameter value you get
> {code}
> javax.el.MethodNotFoundException
> Unable to find unambiguous method: SimpleOrderHandler$Proxy$_$$_WeldClientProxy.getLastUpdate(null)
> at
> javax.el.Util.findWrapper(Util.java:322)
> javax.el.Util.findMethod(Util.java:203)
> javax.el.ELUtil.findMethod(ELUtil.java:288)
> javax.el.BeanELResolver.invoke(BeanELResolver.java:527)
> javax.el.CompositeELResolver.invoke(CompositeELResolver.java:256)
> com.sun.el.parser.AstValue.getValue(AstValue.java:136)
> com.sun.el.parser.AstValue.getValue(AstValue.java:204)
> com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:226)
> org.jboss.weld.el.WeldValueExpression.getValue(WeldValueExpression.java:50)
> com.sun.faces.facelets.el.TagValueExpression.getValue(TagValueExpression.java:109)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBMETA-392) The flushOnSessionInvalidation attribute is missing in the jboss-web schema and the parser
by Ivo Studensky (JIRA)
Ivo Studensky created JBMETA-392:
------------------------------------
Summary: The flushOnSessionInvalidation attribute is missing in the jboss-web schema and the parser
Key: JBMETA-392
URL: https://issues.jboss.org/browse/JBMETA-392
Project: JBoss Metadata
Issue Type: Bug
Components: web
Reporter: Ivo Studensky
Assignee: Ivo Studensky
The class {{org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser}} doesn't support reading {{"flushOnSessionInvalidation"}} attribute on {{"security-domain"}} element. And also the schema files for {{jboss-web.xml}} doesn't mention this attribute.
The class {{org.jboss.metadata.web.jboss.JBossWebMetaData}} contains the attribute {{flushOnSessionInvalidation}}, which comes from old JBoss versions (3.2 and 4.0). [The description|https://developer.jboss.org/wiki/CachingLoginCredentials] says:
??The jboss-web.xml security-domain element now supports a flushOnSessionInvalidation boolean attribute that when true, will flush the security-domain JAAS authentication cache for the associated user principal.??
This attribute is also supported in WildFly integration with Undertow ([look at source|https://github.com/wildfly/wildfly/blob/10.0.0.CR3/undertow/src/ma...]), but the code is never reached as the flushOnSessionInvalidation attribute value stays always *false*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month