June 2013 - jboss-jira - Jboss List Archives

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

by Michael McGovern (JIRA)

[ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.... ] Michael McGovern commented on WFLY-1402: ---------------------------------------- great - thanks - I will try next week when Alpha 2 is out. > 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-308) Provide facility for running ejb3 ws endpoints authorization independently

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/WFLY-308?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on WFLY-308: ----------------------------------- I'm planning to have this for Alpha2. > Provide facility for running ejb3 ws endpoints authorization independently > -------------------------------------------------------------------------- > > Key: WFLY-308 > URL: https://issues.jboss.org/browse/WFLY-308 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Alessio Soldano > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > We'd need a mean of checking auth for ejb3 ws endpoints before the actual invocation is performed. This is basically required to enforce security before running JAXWS handler. -- 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 Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-1402?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-1402. ---------------------------------- Fix Version/s: 8.0.0.Alpha2 Resolution: Done I have made some changes that should reduce the number of services by a significant factor. It is still possible to hit this limit, but it will require significanty more EJB's. > 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-308) Provide facility for running ejb3 ws endpoints authorization independently

by Arun Neelicattu (JIRA)

[ https://issues.jboss.org/browse/WFLY-308?page=com.atlassian.jira.plugin.s... ] Arun Neelicattu commented on WFLY-308: -------------------------------------- Wondering if there was any update on this one? > Provide facility for running ejb3 ws endpoints authorization independently > -------------------------------------------------------------------------- > > Key: WFLY-308 > URL: https://issues.jboss.org/browse/WFLY-308 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Alessio Soldano > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha2 > > > We'd need a mean of checking auth for ejb3 ws endpoints before the actual invocation is performed. This is basically required to enforce security before running JAXWS handler. -- 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-1447) jconsole.sh no longer works

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-1447: ------------------------------------ Summary: jconsole.sh no longer works Key: WFLY-1447 URL: https://issues.jboss.org/browse/WFLY-1447 Project: WildFly Issue Type: Bug Components: JMX Reporter: Stuart Douglas Assignee: Kabir Khan Attempting to connect remotly results in a NoClassDefFound for org.wildfly.security.manager.WildFlySecurityManager, which is needed by the CLI plugin. -- 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-1446) Test Failure: basic-integration-default-web.surefire

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-1446?page=com.atlassian.jira.plugin.... ] Frank Langelage updated WFLY-1446: ---------------------------------- Attachment: wf_error.tar Logfiles from surefire about failing test. > Test Failure: basic-integration-default-web.surefire > ---------------------------------------------------- > > Key: WFLY-1446 > URL: https://issues.jboss.org/browse/WFLY-1446 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha2 > Reporter: Frank Langelage > Assignee: Ondrej Zizka > Attachments: wf_error.tar > > > When running the complete testsuite on current WildFly-8.0.0.Alpha2-SNAPSHOT there is a failure in basic-integration-default-web.surefire: > Results : > Failed tests: testSchedulesAnnotation(org.jboss.as.test.integration.ejb.timerservice.schedule.SimpleScheduleFirstTestCase) > Tests in error: > testProperties(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Cannot deploy: Properties-property-editors-beans.sar > Tests run: 1294, Failures: 1, Errors: 1, Skipped: 40 -- 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-1446) Test Failure: basic-integration-default-web.surefire

by Frank Langelage (JIRA)

Frank Langelage created WFLY-1446: ------------------------------------- Summary: Test Failure: basic-integration-default-web.surefire Key: WFLY-1446 URL: https://issues.jboss.org/browse/WFLY-1446 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 8.0.0.Alpha2 Reporter: Frank Langelage Assignee: Ondrej Zizka When running the complete testsuite on current WildFly-8.0.0.Alpha2-SNAPSHOT there is a failure in basic-integration-default-web.surefire: Results : Failed tests: testSchedulesAnnotation(org.jboss.as.test.integration.ejb.timerservice.schedule.SimpleScheduleFirstTestCase) Tests in error: testProperties(org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase): Cannot deploy: Properties-property-editors-beans.sar Tests run: 1294, Failures: 1, Errors: 1, Skipped: 40 -- 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-1442) Web console branding across community and product versions

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-1442?page=com.atlassian.jira.plugin.... ] Harald Pehl updated WFLY-1442: ------------------------------ Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/4580) > Web console branding across community and product versions > ----------------------------------------------------------- > > Key: WFLY-1442 > URL: https://issues.jboss.org/browse/WFLY-1442 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > > Define a way to specify the branding for the web console across different community and product versions. The name and version used for the branding should be read from the {{product-name}} and {{product-version}} attributes of the root DMR resource. Regarding the logo there are different options: > # Use a unique logo for the web console across all community and products / versions > # Choose between a community (WildFly) and a product logo (RedHat) > # Hold up all logos for any community / product version in the HAL release stream and choose dynamically. -- 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-1432) ClassCastException when JBoss LogManager is initialized before the logging subsystem expects

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1432?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1432: ----------------------------------------------- James Perkins <jperkins(a)redhat.com> changed the Status of [bug 969530|https://bugzilla.redhat.com/show_bug.cgi?id=969530] from NEW to POST > ClassCastException when JBoss LogManager is initialized before the logging subsystem expects > -------------------------------------------------------------------------------------------- > > Key: WFLY-1432 > URL: https://issues.jboss.org/browse/WFLY-1432 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: Kyle Lape > Assignee: James Perkins > > When making the following modifications to put JBoss LogManager on the boot classpath to make it available to Java agents: > {noformat} > diff --git a/bin/standalone.conf b/bin/standalone.conf > index 97895a5..9517129 100644 > --- a/bin/standalone.conf > +++ b/bin/standalone.conf > -35,7 +35,7 @@ > #JAVA="" > > if [ "x$JBOSS_MODULES_SYSTEM_PKGS" = "x" ]; then > - JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman" > + JBOSS_MODULES_SYSTEM_PKGS="org.jboss.logmanager,org.jboss.logmanager.config,org.jboss.logmanager.errormanager,org.jboss.logmanager.filters,org.jboss.logmanager.formatters,org.jboss.logmanager.handlers" > fi > > # Uncomment the following line to prevent manipulation of JVM options > -48,7 +48,7 @@ fi > # > if [ "x$JAVA_OPTS" = "x" ]; then > JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true" > - JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true" > + JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:$JBOSS_HOME/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-1.4.0.Final-redhat-1.jar -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true -Dcom.sun.management.jmxremote=x -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.manager=org.jboss.logmanager.LogManager" > else > echo "JAVA_OPTS already set in environment; overriding default settings with values: $JAVA_OPTS" > fi > {noformat} > I get the following error: > {noformat} > 09:28:18,984 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 5) JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "logging"), > ("console-handler" => "CONSOLE") > ]): java.lang.ClassCastException: org.jboss.logmanager.PropertyConfigurator cannot be cast to org.jboss.as.logging.logmanager.ConfigurationPersistence > at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:93) > at org.jboss.as.logging.logmanager.ConfigurationPersistence.getOrCreateConfigurationPersistence(ConfigurationPersistence.java:81) > at org.jboss.as.logging.LoggingOperations$LoggingOperationStepHandler.execute(LoggingOperations.java:154) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:334) [jboss-as-controller-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final-redhat-1.jar:2.1.0.Final-redhat-1] > {noformat} -- 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-1418) Update JSF based on Mojarra 2.2.0 final

by Stan Silvert (JIRA)

[ https://issues.jboss.org/browse/WFLY-1418?page=com.atlassian.jira.plugin.... ] Stan Silvert resolved WFLY-1418. -------------------------------- Resolution: Done > Update JSF based on Mojarra 2.2.0 final > --------------------------------------- > > Key: WFLY-1418 > URL: https://issues.jboss.org/browse/WFLY-1418 > Project: WildFly > Issue Type: Feature Request > Components: JSF > Affects Versions: 8.0.0.Alpha1 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 8.0.0.Alpha2 > > > Update JSF version based on Mojarra 2.2.0 final. -- 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