June 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1388) Cannot load module alias defined for root deployment

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/WFLY-1388?page=com.atlassian.jira.plugin.... ] Thomas Diesler updated WFLY-1388: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/4547, https://github.com/wildfly/wildfly/pull/4584 (was: https://github.com/wildfly/wildfly/pull/4547) > Cannot load module alias defined for root deployment > ---------------------------------------------------- > > Key: WFLY-1388 > URL: https://issues.jboss.org/browse/WFLY-1388 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: 8.0.0.Alpha2 > > > A module defined like this cannot get loaded by its module-alias > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <deployment> > <resources> > <resource-root path="wrapped-resource.jar" use-physical-code-source="true"/> > </resources> > <dependencies> > <module name="javax.api"/> > <module name="javax.jms.api"/> > <module name="org.apache.camel.core"/> > <module name="org.springframework.beans"/> > <module name="org.springframework.context"/> > <module name="org.springframework.core"/> > <module name="org.springframework.jms"/> > <module name="org.springframework.transaction"/> > <module name="org.slf4j"/> > </dependencies> > <module-alias name="org.apache.camel.component.jms"/> > </deployment> > </jboss-deployment-structure> > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (AS7-5761) EJB2 entity bean CMP collection toArray throws NPE

by Jay Kris (JIRA)

[ https://issues.jboss.org/browse/AS7-5761?page=com.atlassian.jira.plugin.s... ] Jay Kris commented on AS7-5761: ------------------------------- Seems this issue is still present in Jboss EAP 6.1 final. > EJB2 entity bean CMP collection toArray throws NPE > --------------------------------------------------- > > Key: AS7-5761 > URL: https://issues.jboss.org/browse/AS7-5761 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.1.Final, 7.1.3.Final (EAP) > Environment: MAC OSX, Java7 > Reporter: Lucas Galfaso > Assignee: Pieter Bos > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > From an EJB2 entity bean that has a CMP collection of entities, calling toArray() on the CMP collection throws NullPointerException > Caused by: java.lang.NullPointerException > at org.jboss.as.cmp.jdbc.bridge.RelationSet.toArray(RelationSet.java:291) [jboss-as-cmp-7.1.1.Final.jar:7.1.1.Final] > Normal iteration thru the collection using the iterator works as expected. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1448) MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1448?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1448: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=907542 > MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException > ---------------------------------------------------------------------------------------------- > > Key: WFLY-1448 > URL: https://issues.jboss.org/browse/WFLY-1448 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Fix For: 8.0.0.Alpha2 > > > MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase from EAP 6.1.0 TS fail due to NamingException. > Both tests use hardcoded address like: env.put(Context.PROVIDER_URL, "remote://localhost:4447"); > When Jenkins configures to use other address, they will failed with NamingException. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-1448) MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException

by Chao Wang (JIRA)

Chao Wang created WFLY-1448: ------------------------------- Summary: MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase failed due to NamingException Key: WFLY-1448 URL: https://issues.jboss.org/browse/WFLY-1448 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 8.0.0.Alpha1 Reporter: Chao Wang Assignee: Chao Wang Fix For: 8.0.0.Alpha2 MultipleClientRemoteJndiTestCase and NestedRemoteContextTestCase from EAP 6.1.0 TS fail due to NamingException. Both tests use hardcoded address like: env.put(Context.PROVIDER_URL, "remote://localhost:4447"); When Jenkins configures to use other address, they will failed with NamingException. -- 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

11 years

1
0
0 / 0

[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

11 years

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

11 years

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

11 years

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

11 years

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

11 years

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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2013