October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7150) EJB injection with indirection via web.xml is ignored

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7150?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-7150: ------------------------------------ Assignee: Stuart Douglas (was: Jason Greene) > EJB injection with indirection via web.xml is ignored > ----------------------------------------------------- > > Key: WFLY-7150 > URL: https://issues.jboss.org/browse/WFLY-7150 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > > If a web application contains a Servlet and a REST service (as CDI Bean) with an @EJB(lookup="java:comp/env/xxxx") injection for a indirection via web.xml/jboss-web.xml the CDI Bean will ignore it without any message whereas the Servlet inject the EJB proxy as expected. > This approach is used to be able to change/adjust the target EJB by changing the DD and not the application code. > Reproducer can be found here: > git@github.com:wfink/jboss-eap-quickstarts.git > BRANCH: 6.4.x_ejb-multi-server_reproducerEJB-injection2 > SubProject: ejb-multi-server (used only a part of it to have a web-app and a ejb-app) > see ejb-multi-server/README-reproducerEJB-injection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7068) Typo in help for Infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7068?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7068: --------------------------------- Component/s: Clustering (was: Web Console) > Typo in help for Infinispan subsystem > ------------------------------------- > > Key: WFLY-7068 > URL: https://issues.jboss.org/browse/WFLY-7068 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Dmitrii Tikhomirov > Assignee: Dmitrii Tikhomirov > Priority: Trivial > Original Estimate: 5 minutes > Remaining Estimate: 5 minutes > > There is a typo in Passivation paragraph. "f false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes." > There should be "If" instead of "f" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7264) Multicast address of modcluster socket-binding should be parametrized

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7264?page=com.atlassian.jira.plugin.... ] Radoslav Husar moved JBEAP-3000 to WFLY-7264: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7264 (was: JBEAP-3000) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: mod_cluster (was: mod_cluster) Affects Version/s: 10.1.0.Final (was: 7.0.0.ER4) > Multicast address of modcluster socket-binding should be parametrized > --------------------------------------------------------------------- > > Key: WFLY-7264 > URL: https://issues.jboss.org/browse/WFLY-7264 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final > Reporter: Erich Duda > Assignee: Radoslav Husar > Labels: ux > > In {{standalone-ha.xml}} and {{standalone-full-ha.xml}} a {{modcluster}} socket-binding is defined. It has multicast-address parameter which has hard-coded value 224.0.1.105. I need to change this value when I use IPv6 addresses and I can't do it without modifying configuration xml. Although the modcluster is not related to messaging, when the multicast address is IPv4, servers don't create cluster on IPv6 addresses. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7264) Multicast address of modcluster socket-binding should be parametrized

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-7264?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-7264: --------------------------------- Affects Version/s: 10.0.0.Final (was: 10.1.0.Final) > Multicast address of modcluster socket-binding should be parametrized > --------------------------------------------------------------------- > > Key: WFLY-7264 > URL: https://issues.jboss.org/browse/WFLY-7264 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.0.0.Final > Reporter: Erich Duda > Assignee: Radoslav Husar > Labels: ux > > In {{standalone-ha.xml}} and {{standalone-full-ha.xml}} a {{modcluster}} socket-binding is defined. It has multicast-address parameter which has hard-coded value 224.0.1.105. I need to change this value when I use IPv6 addresses and I can't do it without modifying configuration xml. Although the modcluster is not related to messaging, when the multicast address is IPv4, servers don't create cluster on IPv6 addresses. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1849) Wildfly OpenSSL 1.0.0.Alpha2

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1849?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-1849: ---------------------------------------- Fix Version/s: 3.0.0.Alpha10 Assignee: Stuart Douglas Resolution: Done > Wildfly OpenSSL 1.0.0.Alpha2 > ---------------------------- > > Key: WFCORE-1849 > URL: https://issues.jboss.org/browse/WFCORE-1849 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 3.0.0.Alpha10 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7260) Document in elytron model *-client-auth are mutual exclusive

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7260?page=com.atlassian.jira.plugin.... ] Martin Choma commented on WFLY-7260: ------------------------------------ So just document "If both are set to true then 'need' will always have the highest priority" . And I think documentation of difference between this two (similar) options would be also helpful for users, as not everybody is familiar with that. Btw. I like idea of "authentication mode", but not requesting it here, as I think better documentation will be enough. Also don't forget to sync new model documentation with XSD documentation. > Document in elytron model *-client-auth are mutual exclusive > ------------------------------------------------------------ > > Key: WFLY-7260 > URL: https://issues.jboss.org/browse/WFLY-7260 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Minor > > Add to documentation information that need-client-auth and want-client-auth are mutually exclusive. If one is set other is unset. > Now we just have: > * {{want-client-auth}} - "Set wantClientAuth on the underlying SSLContext - if a security domain is referenced this will automatically be set to true." > * {{need-client-auth}} - "Set needClientAuth on the underlying SSLContext." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1852) Logging configuration service for dynamic deployment resources uses wrong service name for deployments

by James Perkins (JIRA)

James Perkins created WFCORE-1852: ------------------------------------- Summary: Logging configuration service for dynamic deployment resources uses wrong service name for deployments Key: WFCORE-1852 URL: https://issues.jboss.org/browse/WFCORE-1852 Project: WildFly Core Issue Type: Bug Reporter: James Perkins Ideally if the use of a service can be removed that would be best. What's needed is a way to associate a deployments resource with a {{LogContextConfiguration}}. One option is to use a custom resource that the OSH can get the {{LogContextConfiguration}} from. This is already done for the child resources. See the {{LoggingDeploymentResources}}. The OSH can cast the resource and just get the configuration. {quote} [12:08 PM] Brian Stansberry: @jperkins this doesn't look right: https://github.com/wildfly/wildfly-core/blob/master/logging/src/main/java.... [12:09 PM] Brian Stansberry: AFAICT it is using the management name of a deployment to create an MSC ServiceName [12:10 PM] James R Perkins: @BrianStansberry Hmm. ...yeah. Let me look at why I was doing that. [12:13 PM] James R Perkins: @BrianStansberry Yes that's what it's doing which thinking about it does seem wrong. Essentially it's trying to figure out which service to use for a dynamic resource on the /deployment=some.war/subsystem=logging/configuration=whatever [12:14 PM] Brian Stansberry: you need to use the runtime-name attribute of the deployment [12:14 PM] James R Perkins: Really it's kind of a bad use case for a service. [12:14 PM] Brian Stansberry: I guess subdeployment has one too, although it's redundant {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7263) Upgrade HttpClient to 4.5.2

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7263?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-7263: -------------------------------------- Component/s: REST Web Services Assignee: Alessio Soldano (was: Jason Greene) Our org.apache.httpcomponents module is private and used by the REST and webservices subsystems, so I put those components on this as they control its version. > Upgrade HttpClient to 4.5.2 > --------------------------- > > Key: WFLY-7263 > URL: https://issues.jboss.org/browse/WFLY-7263 > Project: WildFly > Issue Type: Component Upgrade > Components: REST, Web Services > Reporter: James Netherton > Assignee: Alessio Soldano > > HttpClient 4.5.2 has been available for a while now. Various projects have started to make use of it. It'd be good if WildFly can upgrade. It'd help with integrating some Camel functionality: > https://github.com/wildfly-extras/wildfly-camel/issues/1357 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7263) Upgrade HttpClient to 4.5.2

by James Netherton (JIRA)

James Netherton created WFLY-7263: ------------------------------------- Summary: Upgrade HttpClient to 4.5.2 Key: WFLY-7263 URL: https://issues.jboss.org/browse/WFLY-7263 Project: WildFly Issue Type: Component Upgrade Reporter: James Netherton Assignee: Jason Greene HttpClient 4.5.2 has been available for a while now. Various projects have started to make use of it. It'd be good if WildFly can upgrade. It'd help with integrating some Camel functionality: https://github.com/wildfly-extras/wildfly-camel/issues/1357 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-987) Errors in Phreak under heavy and multi threaded load

by Maciej Swiderski (JIRA)

[ https://issues.jboss.org/browse/DROOLS-987?page=com.atlassian.jira.plugin... ] Maciej Swiderski commented on DROOLS-987: ----------------------------------------- it looks like the change we have done to resolve the problem are still causing some issue in ejb based tests of jbpm. That at the moment is not found what is the issue but looks like really weird one as it fails most of the time with transaction rollback due to hibernate trying to do an update on an entity that was not yet inserted. Thus causing exception as such update on JDBC layer returns 0 rows updated while the expectation is 1. So at the moment linked above PRs (especially one in jbpm) cannot be merged. > Errors in Phreak under heavy and multi threaded load > ----------------------------------------------------- > > Key: DROOLS-987 > URL: https://issues.jboss.org/browse/DROOLS-987 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final, 6.4.0.Final > Environment: linux > Java 7 > kernel 3.16 > Reporter: Jose Cavieres > Assignee: Mario Fusco > Attachments: jbpm-bussinesruletask-concurrent-6-3-NEW.tgz, jbpm-bussinesruletask-concurrent-6-3.tgz > > > Several threads are started, each one starts 1 jbpm process containing rule(s) task(s). > If the threads are few, everything works fine. Under heavy load nullPointerExceptions are thown most of the time, less frequently fireAllRules never ends and CPU remains at 100%. > Aparently the setFocus method used by rule tasks is related to the problem. > The most comon error is: > Caused by: java.lang.NullPointerException > at org.drools.core.common.LeftTupleSetsImpl.removeInsert(LeftTupleSetsImpl.java:141) > at org.drools.core.common.LeftTupleSetsImpl.addDelete(LeftTupleSetsImpl.java:80) > at org.drools.core.reteoo.LeftInputAdapterNode.doDeleteSegmentMemory(LeftInputAdapterNode.java:295) > at org.drools.core.reteoo.LeftInputAdapterNode.doDeleteObject(LeftInputAdapterNode.java:266) > at org.drools.core.reteoo.LeftInputAdapterNode.retractLeftTuple(LeftInputAdapterNode.java:361) > at org.drools.core.reteoo.ObjectTypeNode.doRetractObject(ObjectTypeNode.java:334) > at org.drools.core.reteoo.ObjectTypeNode.retractObject(ObjectTypeNode.java:317) > at org.drools.core.reteoo.EntryPointNode.propagateRetract(EntryPointNode.java:358) > at org.drools.core.phreak.PropagationEntry$Delete.execute(PropagationEntry.java:172) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:96) > at org.drools.core.phreak.SynchronizedPropagationList.flush(SynchronizedPropagationList.java:69) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.flushPropagations(StatefulKnowledgeSessionImpl.java:1993) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2016