January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1678) ARQ test runner error stack trace is not intuitive

by Richard Opalka (JIRA)

ARQ test runner error stack trace is not intuitive -------------------------------------------------- Key: AS7-1678 URL: https://issues.jboss.org/browse/AS7-1678 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.1.Final Reporter: Richard Opalka Assignee: Aslak Knutsen Fix For: 7.0.2.Final >From the stack trace below it's not clear what's going wrong and how to fix this problem. I had to include my *TestCase class file in deployed archive to workaround it. 11:04:06,903 ERROR [org.jboss.arquillian.protocol.jmx.JMXMethodExecutor] (main) Failed: org.jboss.as.testsuite.integration.as1675.AS1675TestCase.testEjb3EndpointInjection: java.lang.IllegalStateException: Cannot obtain Arquillian config for: org.jboss.as.testsuite.integration.as1675.AS1675TestCase at org.jboss.as.arquillian.service.ArquillianService.getArquillianConfig(ArquillianService.java:178) at org.jboss.as.arquillian.service.ArquillianService.getArquillianConfig(ArquillianService.java:188) at org.jboss.as.arquillian.service.ArquillianService.access$300(ArquillianService.java:64) at org.jboss.as.arquillian.service.ArquillianService$ExtendedJMXTestRunner.runTestMethod(ArquillianService.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:111) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:45) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:226) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:251) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:857) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:795) at org.jboss.as.jmx.tcl.TcclMBeanServer.invoke(TcclMBeanServer.java:214) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1450) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:90) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1285) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1383) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:807) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322) at sun.rmi.transport.Transport$1.run(Transport.java:177) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:173) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:553) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:808) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:667) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
7
0 / 0

[JBoss JIRA] (AS7-3438) Create (and ship) EJB specific xsds for security, resource-adapter and other supported configurations

by jaikiran pai (JIRA)

jaikiran pai created AS7-3438: --------------------------------- Summary: Create (and ship) EJB specific xsds for security, resource-adapter and other supported configurations Key: AS7-3438 URL: https://issues.jboss.org/browse/AS7-3438 Project: Application Server 7 Issue Type: Task Components: EJB Reporter: jaikiran pai Assignee: jaikiran pai Fix For: 7.1.0.Final Currently we don't have a xsd with the schema supported for resource-adapter, security configurations (and probably others) in jboss-ejb3.xml. We need to create and ship these xsds. -- 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

12 years, 8 months

1
1
0 / 0

[JBoss JIRA] (AS7-3040) IPv6: IP address proccessing in pure IPv6 (only) network stack environment

by Pavel Janousek (Created) (JIRA)

IPv6: IP address proccessing in pure IPv6 (only) network stack environment -------------------------------------------------------------------------- Key: AS7-3040 URL: https://issues.jboss.org/browse/AS7-3040 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.0.Beta1b Reporter: Pavel Janousek Assignee: Jason Greene Priority: Blocker Actual implementation of processing IP address (e.g. from XML cfg) as 127.0.0.1 is +totally+ useless in IPv6 environment (it has its own *incompatible* ekvivalent - _::1_). The default behavior of AS7 is IPv6 disabled at all, so user should be forced to *reconfigure* his instance of AS7 to run it in pure IPv6 network stack only (the are also missing some document described this process yet! - AS7-3039). So one issue is when AS7 instance is bring up with default configuration (distributed standalone.xml), but in an IPv6 network environment available only like: {code} bin/standalone.sh -Djava.net.preferIPv4Stack=false {code} It uses configured address 127.0.0.1 (default from standalone.xml if key _jboss.bind.address_ isn't defined) as binding point which it could try to use. It is bad and should be avoided, because 127.0.0.1 isn't +valid IPv6 address+, nor allowed IPv6 address format specification (see [RFC 5952|http://tools.ietf.org/html/rfc5952]), and note - IPv4-Compatible IPv6 Address are deprecated (see [RFC 4291 section 2.5.1.1|http://tools.ietf.org/html/rfc4291#section-2.5.5]). Only one possibility is allowed now - IPv4-Mapped IPv6 Address, but it has it's own format and regulary defined address space, also it doesn't make sense to use it in pure IPv6 environment. *So conclusion - a such address setting (127.0.0.1) in pure IPv6 environment is miss-configuration error at all and starting AS7 instance in this case should only report valid error message about what happens and end itself, not trying to do with a such address format anything - nor convert to other address format, nor use its own inside logic (convert to ::ffff:<IPv4>) etc..* This error relates to other one - produced log contains nonsense messages as:{code}12:59:31,222 INFO [org.jboss.as.remoting] (MSC service thread 1-2) Listening on localhost.localdomain/127.0.0.1:4447 {code} even though it is bound and listening only on _::ffff:127.0.0.1:4447_. -- 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

12 years, 8 months

8
12
0 / 0

[JBoss JIRA] (AS7-3437) JMS clients - Remote JNDI lookup does not work in EAP6/AS7

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.s... ] Jason Greene closed AS7-3437. ----------------------------- Labels: (was: eap6_prd_req) Fix Version/s: No Release (was: 7.1.0.Final) Resolution: Duplicate Issue > JMS clients - Remote JNDI lookup does not work in EAP6/AS7 > ---------------------------------------------------------- > > Key: AS7-3437 > URL: https://issues.jboss.org/browse/AS7-3437 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Miroslav Novak > Assignee: David Lloyd > Priority: Blocker > Fix For: No Release > > > EAP6/AS7 have not yet implemented remote jndi lookups. This feature is important for standalone jms clients to work and also ensure backward compatibility with EAP5/AS6 applications. Following piece of code should work without change: > Properties properties = new Properties(); > properties.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); > properties.setProperty("java.naming.provider.url", "jnp://server_hostname:1099"); > properties.setProperty("java.naming.factory.url.pkgs", "org.jnp.interfaces.NamingContextFactory"); > context = new InitialContext(properties); > ConnectionFactory cf = (ConnectionFactory) context.lookup("RemoteConnectionFactory"); > con = cf.createConnection(); > session = con.createSession(false, Session.CLIENT_ACKNOWLEDGE); > Queue queue = (Queue) context.lookup("/queue/test"); > For now there is a workaround but it's not suitable for us. Example code: > https://github.com/jbossas/jboss-as/tree/master/demos/legacy/src/main/jav... > There are AS7 jiras related to this missing feature which are closed as rejected/duplicated. In AS7-1338 J. Green explains that some kind of remote jndi functionality will be in AS 7.1 (as part of the EE full profile). Unfortunately AS 7.1 is still missing this feature. -- 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-3134) Upgrade to JBossTS 4.16.1

by Paul Robinson (Created) (JIRA)

Upgrade to JBossTS 4.16.1 ------------------------- Key: AS7-3134 URL: https://issues.jboss.org/browse/AS7-3134 Project: Application Server 7 Issue Type: Component Upgrade Components: Transactions Affects Versions: 7.1.0.CR1 Reporter: Paul Robinson Assignee: Jonathan Halliday Priority: Critical Fix For: 7.1.0.Final Contains a critical fix for a bug in JBossTS-4.16.0 that ships with AS7.1.0.CR1. See link for more info. -- 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

12 years, 8 months

3
2
0 / 0

[JBoss JIRA] (AS7-3006) Deploy error for ejb2 remote interface which extends other interface

by Ondřej Chaloupka (Created) (JIRA)

Deploy error for ejb2 remote interface which extends other interface -------------------------------------------------------------------- Key: AS7-3006 URL: https://issues.jboss.org/browse/AS7-3006 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: John Bailey The scenario is following. The interface marked to define remote interface of bean (e.g. by @Remote annotation) extends other interface. This other interface specifies method which bean has to implement and the children interface (mentioned in bean) does not define any method for implementation. Deployment on container ends up with following exception: 19:09:57,601 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.deployment.unit."reference-ejb2-ejb3-a.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."reference-ejb2-ejb3-a.jar".POST_MODULE: Failed to process phase POST_MODULE of deployment "reference-ejb2-ejb3-a.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] Caused by: java.lang.NullPointerException at org.jboss.as.ejb3.deployment.processors.EjbIIOPDeploymentUnitProcessor.processEjb(EjbIIOPDeploymentUnitProcessor.java:188) at org.jboss.as.ejb3.deployment.processors.EjbIIOPDeploymentUnitProcessor.deploy(EjbIIOPDeploymentUnitProcessor.java:133) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] ... 5 more Test could be checked on: https://github.com/ochaloup/jboss-as/commit/d381c88f78a6b1d52b44d281f6c73... -- 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

12 years, 8 months

3
4
0 / 0

[JBoss JIRA] (AS7-2097) Add missing attribute to the JBoss EJB3 XML Schema

by Andrig Miller (Created) (JIRA)

Add missing attribute to the JBoss EJB3 XML Schema -------------------------------------------------- Key: AS7-2097 URL: https://issues.jboss.org/browse/AS7-2097 Project: Application Server 7 Issue Type: Task Components: EJB Affects Versions: 7.1.0.Alpha1 Reporter: Andrig Miller Assignee: Carlo de Wolf Fix For: 7.1.0.Beta1 I have been looking over all the XML schemas for my performance tuning work. In looking at the EJB 3 schema, I don't see anything where you can reference the cache configuration for the Stateful session beans. There is a stateful session bean cache configuration in the Infinispan schema, and I would assume there should be a reference to it, via its name in the EJB 3 schema. -- 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

12 years, 8 months

8
8
0 / 0

[JBoss JIRA] (AS7-2729) Implement the ability to turn dynamic stubs on and off via xml config

by Stuart Douglas (Created) (JIRA)

Implement the ability to turn dynamic stubs on and off via xml config --------------------------------------------------------------------- Key: AS7-2729 URL: https://issues.jboss.org/browse/AS7-2729 Project: Application Server 7 Issue Type: Feature Request Reporter: Stuart Douglas Some of the TCK tests are not compatible with dynamic stubs. Another option could be to implement a delegating factory, that first tries the static factory then resorts to dynamic stubs. -- 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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] (AS7-3030) Create a new bulid of jacorb

by Paul Gier (Created) (JIRA)

Create a new bulid of jacorb ---------------------------- Key: AS7-3030 URL: https://issues.jboss.org/browse/AS7-3030 Project: Application Server 7 Issue Type: Task Components: IIOP Reporter: Paul Gier Assignee: Nick Cross Fix For: 7.1.0.Final We're currently using a patched rebuild of jacorb (version 2.3.1jboss.patch01-brew). Ideally the patches could be pushed upstream and we can switch to an official 2.3.2 build with jars in Maven central. As a backup solution, we should create a new patched build (2.3.1-jbossorg-1) and add that to our thirdparty releases repository as described in the wiki (http://community.jboss.org/wiki/MavenDeployingAThirdpartyRelease) -- 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

12 years, 8 months

5
5
0 / 0

[JBoss JIRA] (AS7-3372) Viewframework: Don't pull runtime attributes by default

by Heiko Braun (JIRA)

Heiko Braun created AS7-3372: -------------------------------- Summary: Viewframework: Don't pull runtime attributes by default Key: AS7-3372 URL: https://issues.jboss.org/browse/AS7-3372 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Stan Silvert Fix For: 7.1.0.Final this may increase the overall payload quiet a lot. Please provide an API to explicitly enable this behavior. -- 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

12 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012