February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBJCA-742) Annotation based resource adapter without @Connector fails

by Jesper Pedersen (JIRA)

Jesper Pedersen created JBJCA-742: ------------------------------------- Summary: Annotation based resource adapter without @Connector fails Key: JBJCA-742 URL: https://issues.jboss.org/browse/JBJCA-742 Project: IronJacamar Issue Type: Bug Components: Common Affects Versions: 1.1.0.Alpha5, 1.0.7.Final Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Critical Fix For: 1.0.8.Final, 1.1.0.Alpha6 An annotation based resource adapter without a @Connector fails -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (JBAOP-810) jboss-aop (single jar) build failed

by gil cattaneo (JIRA)

gil cattaneo created JBAOP-810: ---------------------------------- Summary: jboss-aop (single jar) build failed Key: JBAOP-810 URL: https://issues.jboss.org/browse/JBAOP-810 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Components: Aspect Library Affects Versions: 2.2.2.GA Environment: Java-Version: 1.7.0_b147-icedtea Os-Arch: i386 Os-Name: Linux Os-Version: 3.2.2-desktop586-1.mga2 Reporter: gil cattaneo Priority: Minor [INFO] --- maven-assembly-plugin:2.2.2:attached (single) @ jboss-aop --- [INFO] Reading assembly descriptor: src/assembly/single.xml [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Skipping JBoss AOP Parent POM [INFO] This project has been banned from the build due to previous failures. [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss AOP Parent POM .............................. SUCCESS [1.937s] [INFO] JBoss AOP Framework ............................... FAILURE [13:05.747s] [INFO] JBoss AOP Maven Plugin ............................ SKIPPED [INFO] JBoss AOP Pluggable Instrumentor .................. SKIPPED [INFO] JBoss AOP Aspects ................................. SKIPPED [INFO] JBoss AOP AS Integration Core ..................... SKIPPED [INFO] JBoss AOP Helper .................................. SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 13:16.522s [INFO] Finished at: Mon Feb 06 14:26:14 CET 2012 [INFO] Final Memory: 48M/909M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.2:attached (single) on project jboss-aop: Failed to create assembly: Error creating assembly archive single: Failed to retrieve numeric file attributes using: '/bin/sh -c ls -1nlaR /' -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-3636) Multi deployment does not work for Arquillian for AS7 protocol

by Ondřej Chaloupka (JIRA)

Ondřej Chaloupka created AS7-3636: ------------------------------------- Summary: Multi deployment does not work for Arquillian for AS7 protocol Key: AS7-3636 URL: https://issues.jboss.org/browse/AS7-3636 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.CR1b Reporter: Ondřej Chaloupka Assignee: Aslak Knutsen Priority: Minor For Arquillian the multideployment does not work over AS7 protocol. This issue was discussed with Aslak Knutsen and you can check the forum https://community.jboss.org/message/714601 for more details. When you want to create two deployments (two jars to deploy) in a one test file and each deployment has its own test (test operates on the deployment) then test does not find correct module in which is executed. One test passes while second one fails with CNFE when it tries to make JNDI lookup for own session bean. The test class is like this: {code} @Deployment(managed=true, testable = true, name = "postconstruct", order = 1) public static Archive<?> deploy() { ... return jar1; } @Deployment(managed=true, testable = true, name = "postconstruct2", order = 2) public static Archive<?> deploy2() { ... return jar2; } @Test @OperateOnDeployment("postconstruct") public void test() throws NamingException { CountedSessionBean bean = (CountedSessionBean) ctx.lookup("java:global/postconstruct/" + CountedSessionBean.class.getSimpleName()); ... } @Test @OperateOnDeployment("postconstruct2") public void test2() { CountedSessionBean2 bean = (CountedSessionBean2) ctx.lookup("java:global/postconstruct2/" + CountedSessionBean2.class.getSimpleName()); ... } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-3635) IllegalStateException in ejb remote client

by Richard Opalka (JIRA)

Richard Opalka created AS7-3635: ----------------------------------- Summary: IllegalStateException in ejb remote client Key: AS7-3635 URL: https://issues.jboss.org/browse/AS7-3635 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Richard Opalka Assignee: jaikiran pai Priority: Minor Fix For: 7.1.0.Final When running TCK6 I see many ERROR messages (see example below). These messages are not affecting TCK6 results. --- [javatest.batch] 08:03:13,670 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.ejb3.ejbClientContext.default: org.jboss.msc.service.StartException in service jboss.ejb3.ejbClientContext.default: Failed to start service [javatest.batch] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [javatest.batch] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29] [javatest.batch] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29] [javatest.batch] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] [javatest.batch] Caused by: java.lang.IllegalStateException [javatest.batch] at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [javatest.batch] at org.jboss.as.ejb3.remote.DefaultEjbClientContextService.start(DefaultEjbClientContextService.java:89) [javatest.batch] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [javatest.batch] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] [javatest.batch] ... 3 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (AS7-3622) basic operation description for composite

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created AS7-3622: -------------------------------------- Summary: basic operation description for composite Key: AS7-3622 URL: https://issues.jboss.org/browse/AS7-3622 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.1.0.Final 'composite' is missing operation description. Its structure is not easy describe in detail but even a basic description would already be something. And also it would help with basic validation in the CLI and, probably, other tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (REMJMX-24) Release 1.0.0.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-24: -------------------------------------- Summary: Release 1.0.0.Final Key: REMJMX-24 URL: https://issues.jboss.org/browse/REMJMX-24 Project: Remoting JMX Issue Type: Task Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.GA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (REMJMX-8) Connection state notification suppport

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-8?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-8: ---------------------------------- Fix Version/s: 1.0.1.GA (was: 1.0.0.GA) > Connection state notification suppport > -------------------------------------- > > Key: REMJMX-8 > URL: https://issues.jboss.org/browse/REMJMX-8 > Project: Remoting JMX > Issue Type: Task > Components: Connection, Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.1.GA > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-646) Release Negotiation 2.2.0.SP1

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-646: ----------------------------------------- Summary: Release Negotiation 2.2.0.SP1 Key: SECURITY-646 URL: https://issues.jboss.org/browse/SECURITY-646 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2_2_0_SP1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] (AS7-3533) TS: Add assert descriptions.

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3533: --------------------------------- Summary: TS: Add assert descriptions. Key: AS7-3533 URL: https://issues.jboss.org/browse/AS7-3533 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: Vladimir Rastseluev Fix For: 7.1.0.Final Hi Vladimir, could you please add assert descriptions, as per https://docs.jboss.org/author/display/AS71/AS+7+Testsuite+Test+Developer+... ? Thanks. {code} AsseassertTrue(result2 != null); Assert.assertTrue(result2.hasDefined("driver-module-name")); Assert.assertTrue(result2.hasDefined("module-slot")); Assert.assertTrue(result2.hasDefined("driver-name")); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[JBoss JIRA] (REMJMX-23) Upgrade to JBoss Remoting 3.2.0.GA

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-23: -------------------------------------- Summary: Upgrade to JBoss Remoting 3.2.0.GA Key: REMJMX-23 URL: https://issues.jboss.org/browse/REMJMX-23 Project: Remoting JMX Issue Type: Task Components: Connection Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.GA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
2
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 February 2012