June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1640) RELAY2: use strings as site IDs

by Bela Ban (JIRA)

Bela Ban created JGRP-1640: ------------------------------ Summary: RELAY2: use strings as site IDs Key: JGRP-1640 URL: https://issues.jboss.org/browse/JGRP-1640 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.4 Investigate using strings instead of shorts as site-ids. This would eliminate the need for the string-short mapping file and would make life simpler for JDG and EAP as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1410) Weld EL resolver is not registered in a JSP environment

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-1410?page=com.atlassian.jira.plugin.... ] Jozef Hartinger resolved WFLY-1410. ----------------------------------- Fix Version/s: 8.0.0.Alpha2 Resolution: Done Thanks Stuart! > Weld EL resolver is not registered in a JSP environment > ------------------------------------------------------- > > Key: WFLY-1410 > URL: https://issues.jboss.org/browse/WFLY-1410 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Web (Undertow) > Affects Versions: 8.0.0.Alpha1 > Reporter: Martin Kouba > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha2 > > > It seems the {{org.jboss.as.weld.webtier.jsp.JspInitializationListener}} or some other integration code is not working properly. > See also TCK test: > https://github.com/jboss/cdi-tck/blob/master/impl/src/main/java/org/jboss... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1402) Too Many Dependencies

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.... ] jaikiran pai commented on WFLY-1402: ------------------------------------ You can even just download the latest nightly binary from here https://community.jboss.org/thread/224262 and give it a try. That way, you can be sure that Alpha2 will have this fixed for your application. > Too Many Dependencies > --------------------- > > Key: WFLY-1402 > URL: https://issues.jboss.org/browse/WFLY-1402 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Alpha1 > Environment: W7 64 bit > Reporter: Michael McGovern > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha2 > > > Large app ~ 1000 SLSB gets > Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383) > at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142) [jboss-msc-1.1.2.Final.jar:1.1.2.Final] > at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha1.jar:8.0.0.Alpha1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-826) ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/WFLY-826?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori edited comment on WFLY-826 at 6/4/13 3:31 AM: ---------------------------------------------------------------- Seems others are hitting this issue as well: http://forum.springsource.org/archive/index.php/t-113581.html http://pushpendrasinghbaghel.blogspot.fi/2013/01/spring-aop-and-jbossas-7... http://stackoverflow.com/a/16867315/365237 was (Author: jrantav): Seems others are hitting this issue as well: http://forum.springsource.org/archive/index.php/t-113581.html http://pushpendrasinghbaghel.blogspot.fi/2013/01/spring-aop-and-jbossas-7... http://stackoverflow.com/questions/13943110/aspectj-aspect-under-jboss-as... > ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects > ---------------------------------------------------------------- > > Key: WFLY-826 > URL: https://issues.jboss.org/browse/WFLY-826 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Environment: Windows 7 > Reporter: Jarkko Rantavuori > Assignee: David Lloyd > Attachments: MyMethodTrace.java, MyMethodTraceAspect.java, spring-app-aop-datasource-1.0.0-BUILD-SNAPSHOT.war, spring-mvc-aop-datasource-app.zip > > > Special measures need to be taken for load-time-weaving with aspects, but using them without load-time weaving works normally OOB. However, if this kind of Spring configuration is used: >  > <jee:jndi-lookup id="dataSource" jndi-name="jboss/datasources/ExampleDS"/> >  > <bean id="methodTraceAspect" class="fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect"/> > <aop:aspectj-autoproxy /> >  > <bean class="fi.eis.applications.controllers.HomeController"> > <constructor-arg ref="dataSource" /> > </bean> > JBoss tries to use methodTraceAspect also on the data source. Data source is loaded by ModuleClassLoader that in has only visibility to org.jboss.jca.adapters* classes (confirmed with a debugger), so it cannot find the aspect class anymore, making aspect-j throw org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine implemented interfaces of missing type > fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect [Xlint:cantFindType]. > This has large problems in bigger applications, where general AOP pointcuts are used - no jboss-module stuff can be used as beans, anywhere. I'm aware of no workaround for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] Heiko Braun resolved WFLY-336. ------------------------------ Resolution: Done > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-336: ---------------------------------------------- Heiko Braun <hbraun(a)redhat.com> changed the Status of [bug 910675|https://bugzilla.redhat.com/show_bug.cgi?id=910675] from ASSIGNED to MODIFIED > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-826) ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects

by Jarkko Rantavuori (JIRA)

[ https://issues.jboss.org/browse/WFLY-826?page=com.atlassian.jira.plugin.s... ] Jarkko Rantavuori commented on WFLY-826: ---------------------------------------- Seems others are hitting this issue as well: http://forum.springsource.org/archive/index.php/t-113581.html http://pushpendrasinghbaghel.blogspot.fi/2013/01/spring-aop-and-jbossas-7... http://stackoverflow.com/questions/13943110/aspectj-aspect-under-jboss-as... > ModuleClassLoader breaks Aspect-J non-load-time-weaving aspects > ---------------------------------------------------------------- > > Key: WFLY-826 > URL: https://issues.jboss.org/browse/WFLY-826 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Environment: Windows 7 > Reporter: Jarkko Rantavuori > Assignee: David Lloyd > Attachments: MyMethodTrace.java, MyMethodTraceAspect.java, spring-app-aop-datasource-1.0.0-BUILD-SNAPSHOT.war, spring-mvc-aop-datasource-app.zip > > > Special measures need to be taken for load-time-weaving with aspects, but using them without load-time weaving works normally OOB. However, if this kind of Spring configuration is used: >  > <jee:jndi-lookup id="dataSource" jndi-name="jboss/datasources/ExampleDS"/> >  > <bean id="methodTraceAspect" class="fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect"/> > <aop:aspectj-autoproxy /> >  > <bean class="fi.eis.applications.controllers.HomeController"> > <constructor-arg ref="dataSource" /> > </bean> > JBoss tries to use methodTraceAspect also on the data source. Data source is loaded by ModuleClassLoader that in has only visibility to org.jboss.jca.adapters* classes (confirmed with a debugger), so it cannot find the aspect class anymore, making aspect-j throw org.aspectj.weaver.reflect.ReflectionWorld$ReflectionWorldException: warning can't determine implemented interfaces of missing type > fi.eis.applications.jboss.poc.gemini.spring.aop.support.api.MyMethodTraceAspect [Xlint:cantFindType]. > This has large problems in bigger applications, where general AOP pointcuts are used - no jboss-module stuff can be used as beans, anywhere. I'm aware of no workaround for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-336) Wrong value of "runtime-name" property for unmanaged deployments

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-336?page=com.atlassian.jira.plugin.s... ] Heiko Braun updated WFLY-336: ----------------------------- Labels: console_1.5.2 console_1.5.3 merged (was: console_1.5.2 console_1.5.3) > Wrong value of "runtime-name" property for unmanaged deployments > ----------------------------------------------------------------- > > Key: WFLY-336 > URL: https://issues.jboss.org/browse/WFLY-336 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Labels: console_1.5.2, console_1.5.3, merged > Fix For: 8.0.0.Alpha2 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6759) Console should react properly to loss of connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6759?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6759: ---------------------------------------------- Heiko Braun <hbraun(a)redhat.com> made a comment on [bug 910718|https://bugzilla.redhat.com/show_bug.cgi?id=910718] should be fixed in 1.5.2 already > Console should react properly to loss of connection > --------------------------------------------------- > > Key: AS7-6759 > URL: https://issues.jboss.org/browse/AS7-6759 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > > Codesplit error handling leads to freeze -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-6759) Console should react properly to loss of connection

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6759?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6759: ---------------------------------------------- Heiko Braun <hbraun(a)redhat.com> changed the Status of [bug 910718|https://bugzilla.redhat.com/show_bug.cgi?id=910718] from ASSIGNED to MODIFIED > Console should react properly to loss of connection > --------------------------------------------------- > > Key: AS7-6759 > URL: https://issues.jboss.org/browse/AS7-6759 > Project: Application Server 7 > Issue Type: Feature Request > Components: Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > > Codesplit error handling leads to freeze -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2013