October 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4041) Upgrade to JBossWS 4.3.2.Final, Apache CXF 2.7.13, Apache WSS4J 1.6.17

by Alessio Soldano (JIRA)

Alessio Soldano created WFLY-4041: ------------------------------------- Summary: Upgrade to JBossWS 4.3.2.Final, Apache CXF 2.7.13, Apache WSS4J 1.6.17 Key: WFLY-4041 URL: https://issues.jboss.org/browse/WFLY-4041 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 8.2.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4036) update EclipseLink/OpenJPA test case to filter out javax.persistence classes

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-4036?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-4036: ------------------------------- Description: JBoss modules is improving the case when two modules have bi-directional dependencies (a depends on b and b depends on a). Part of this is ensuring that module level classes are used over classes from dependencies (child first). This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA static module test). was: WildFly-core upgrade is improving the case when two deployments have bi-directional dependencies (a depends on b and b depends on a). Part of this is ensuring that application level classes are used over classes from dependencies. This introduces an issue for application that include api jars or other jars that previlously used to be overriden by dependency level classes. This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA test). > update EclipseLink/OpenJPA test case to filter out javax.persistence classes > ---------------------------------------------------------------------------- > > Key: WFLY-4036 > URL: https://issues.jboss.org/browse/WFLY-4036 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > Attachments: module.xml, module.xml, stacktrace.txt > > > JBoss modules is improving the case when two modules have bi-directional dependencies (a depends on b and b depends on a). Part of this is ensuring that module level classes are used over classes from dependencies (child first). > This jira is about fixing this for two of our unit tests that willl have this problem (an EclipseLink + OpenJPA static module test). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1231) Allow existing connection to be obtained during MARKED_FOR_ROLLBACK

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1231?page=com.atlassian.jira.plugin... ] Jesper Pedersen resolved JBJCA-1231. ------------------------------------ Resolution: Done > Allow existing connection to be obtained during MARKED_FOR_ROLLBACK > ------------------------------------------------------------------- > > Key: JBJCA-1231 > URL: https://issues.jboss.org/browse/JBJCA-1231 > Project: IronJacamar > Issue Type: Task > Components: Core > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Fix For: 1.2.1.Final > > > Strategy for interleaved connections stays the same -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBJCA-1231) Allow existing connection to be obtained during MARKED_FOR_ROLLBACK

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-1231: -------------------------------------- Summary: Allow existing connection to be obtained during MARKED_FOR_ROLLBACK Key: JBJCA-1231 URL: https://issues.jboss.org/browse/JBJCA-1231 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.2.1.Final Strategy for interleaved connections stays the same -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4040) add support for persistence-fragment.xml

by Mathieu Lachance (JIRA)

Mathieu Lachance created WFLY-4040: -------------------------------------- Summary: add support for persistence-fragment.xml Key: WFLY-4040 URL: https://issues.jboss.org/browse/WFLY-4040 Project: WildFly Issue Type: Feature Request Components: EE Reporter: Mathieu Lachance Assignee: David Lloyd It would be nice if JBoss / Hibernate could support the TomEE / OpenJPA persistence-fragment.xml vendor specific feature. This feature would allow easier application modularization by not relying on any custom build process to compose a valid persistence.xml from many fragments. See TomEE exemple here: http://tomee.apache.org/examples-trunk/persistence-fragment/README.html -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-2632) JGroups drops unicast messages after shutdown/restart (dropping unicast message to wrong destination)

by MOHAMED RIYAZ (JIRA)

[ https://issues.jboss.org/browse/WFLY-2632?page=com.atlassian.jira.plugin.... ] MOHAMED RIYAZ commented on WFLY-2632: ------------------------------------- Hello Radoslav Husar, Due to this error we aren't able to bring the server up in the clustering mode. As you said the fix has in 9.0.0 Beta version. So Do you have any tentative option for this issue in wildfly? Thanks & Regards, Mohammad > JGroups drops unicast messages after shutdown/restart (dropping unicast message to wrong destination) > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-2632 > URL: https://issues.jboss.org/browse/WFLY-2632 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 9.0.0.Beta1 > > > JGroups drops unicast messages (citing wrong destination) after a node in a cluster is shutdown and then restarted. > The JGroups version in use is 3.4.1.Final. > Steps to reproduce: > - start two nodes A, B using the server configuration standalone-ha.xml to create a cluster > - shutdown A > - restart A > - after restart, we see these messages: > {noformat} > 13:15:03,227 INFO [stdout] (ServerService Thread Pool -- 63) > 13:15:03,228 INFO [stdout] (ServerService Thread Pool -- 63) ------------------------------------------------------------------- > 13:15:03,228 INFO [stdout] (ServerService Thread Pool -- 63) GMS: address=lenovo/web, cluster=web, physical address=127.0.0.1:55200 > 13:15:03,229 INFO [stdout] (ServerService Thread Pool -- 63) ------------------------------------------------------------------- > 13:15:03,414 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 63) ISPN000094: Received new cluster view: [fred/ > web|3] (2) [fred/web, lenovo/web] > 13:15:03,422 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 63) ISPN000079: Cache local address is lenovo/web > , physical addresses are [127.0.0.1:55200] > 13:15:03,427 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 63) ISPN000128: Infinispan version: Infinispan 'Infinium' 6 > .0.0.CR1 > 13:15:03,533 WARN [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: lenovo/web: dropping unicast message to wrong destination ac84f3e5 > -f005-ddb2-b377-46b165e2aa77 > 13:15:03,609 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 61) ISPN000031: MBeans were successfully registered to the platform > MBean server. > 13:15:03,610 INFO [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 62) ISPN000031: MBeans were successfully registered to the platform > MBean server. > 13:15:03,765 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) JBAS010281: Started default-host/distributable cache from web contain > er > 13:15:03,768 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 61) JBAS010281: Started dist cache from web container > 13:15:03,906 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Register web context: /distributable > 13:15:03,978 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "distributable.war" (runtime-name : "distributable.war") > 13:15:04,033 WARN [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: lenovo/web: dropping unicast message to wrong destination ac84f3e5 > -f005-ddb2-b377-46b165e2aa77 > 13:15:04,059 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 13:15:04,060 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 13:15:04,060 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Beta2-SNAPSHOT "WildFly" started in 5193ms - Started 293 of 410 services (178 services are lazy, passive or on-demand) > 13:15:04,533 WARN [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: lenovo/web: dropping unicast message to wrong destination ac84f3e5-f005-ddb2-b377-46b165e2aa77 > 13:15:05,034 WARN [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: lenovo/web: dropping unicast message to wrong destination ac84f3e5-f005-ddb2-b377-46b165e2aa77 > 13:15:05,534 WARN [org.jgroups.protocols.TP$ProtocolAdapter] (INT-1,shared=udp) JGRP000031: lenovo/web: dropping unicast message to wrong destination ac84f3e5-f005-ddb2-b377-46b165e2aa77 > {noformat} > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4030) wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/WFLY-4030?page=com.atlassian.jira.plugin.... ] Rafael Benevides commented on WFLY-4030: ---------------------------------------- [~sebastian.laskawiec] I don't think we should remove the arquetype files since we need to track the sources in a determined release. Anyway it's a good idea to have this synch information at README. I placed some information about releasing them at https://github.com/wildfly/wildfly-archetypes/blob/master/RELEASE_PROCEDU... > wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml > ---------------------------------------------------------------------------------------------- > > Key: WFLY-4030 > URL: https://issues.jboss.org/browse/WFLY-4030 > Project: WildFly > Issue Type: Bug > Reporter: Arun Gupta > Assignee: Sebastian Łaskawiec > Priority: Minor > Labels: archetypes, maven, wildfly > > mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final > The app has the following files: > ./src/main/webapp/WEB-INF/beans.xml > ./src/main/webapp/WEB-INF/faces-config.xml > beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-644) no-loop attribute and named consequences

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-644?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-644. -------------------------------- Resolution: Rejected The no-loop attribute works on a consequence basis. This means that annotating a rule with no-loop causes that a consequence cannot reactive itself but nothing prevent it to activate a different consequence of the same rule. The test case I pushed here https://github.com/droolsjbpm/drools/commit/bc29b6653 demonstrates this behavior. If you have a use case where what I am saying doesn't apply, feel free to reopen this ticket and add a small reproducer for the issue you found. > no-loop attribute and named consequences > ---------------------------------------- > > Key: DROOLS-644 > URL: https://issues.jboss.org/browse/DROOLS-644 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Reporter: Pedro Martins > Assignee: Mario Fusco > Labels: named_consequence, no-loop > > I wrote a rule that modifies a fact from within a named consequence. The no-loop attribute failed to prevent the rule from reactivating. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3900) Unable to inject EJB Context into CDI Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3900: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1149646|https://bugzilla.redhat.com/show_bug.cgi?id=1149646] from NEW to POST > Unable to inject EJB Context into CDI Interceptor > ------------------------------------------------- > > Key: WFLY-3900 > URL: https://issues.jboss.org/browse/WFLY-3900 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > Attachments: inject-ejb-context-into-cdi-interceptor.jar, server.log > > > CDI Interceptor cannot inject EJB session context. > If the Interceptor is changed to EJB interceptor by removing the @Interceptor on the interceptor and removing it from the beans.xml, and adding @Interceptors(...) to the EJB, then it is able to inject. > See attached reproducer with source and log file. > private @Resource SessionContext sessionContext; > Caused by: javax.naming.NameNotFoundException: env/test.ServiceLoggedInterceptor/sessionContext -- service jboss.naming.context.java.comp.inject-ejb-context-into-cdi-interceptor.inject-ejb-context-into-cdi-interceptor.HelloEJB.env."test.ServiceLoggedInterceptor".sessionContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) > ... 127 more -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3900) Unable to inject EJB Context into CDI Interceptor

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3900?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3900: ----------------------------------------------- baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1149644|https://bugzilla.redhat.com/show_bug.cgi?id=1149644] from NEW to POST > Unable to inject EJB Context into CDI Interceptor > ------------------------------------------------- > > Key: WFLY-3900 > URL: https://issues.jboss.org/browse/WFLY-3900 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > Attachments: inject-ejb-context-into-cdi-interceptor.jar, server.log > > > CDI Interceptor cannot inject EJB session context. > If the Interceptor is changed to EJB interceptor by removing the @Interceptor on the interceptor and removing it from the beans.xml, and adding @Interceptors(...) to the EJB, then it is able to inject. > See attached reproducer with source and log file. > private @Resource SessionContext sessionContext; > Caused by: javax.naming.NameNotFoundException: env/test.ServiceLoggedInterceptor/sessionContext -- service jboss.naming.context.java.comp.inject-ejb-context-into-cdi-interceptor.inject-ejb-context-into-cdi-interceptor.HelloEJB.env."test.ServiceLoggedInterceptor".sessionContext > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51] > at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185) > ... 127 more -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

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 2014