January 2012 - jboss-jira - Jboss List Archives

[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

14 years, 3 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

14 years, 3 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

14 years, 3 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

14 years, 3 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3261) Update thread pool property modifications

by Heiko Braun (Created) (JIRA)

Update thread pool property modifications ----------------------------------------- Key: AS7-3261 URL: https://issues.jboss.org/browse/AS7-3261 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.Final -- 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, 3 months

4
4
0 / 0

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

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-3437?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran moved JBPAPP-7989 to AS7-3437: ------------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-3437 (was: JBPAPP-7989) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 DR 5) Component/s: (was: System) (was: HornetQ) Security: (was: Public) Fix Version/s: 7.1.0.Final (was: TBD EAP 6) Docs QE Status: (was: NEW) > 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 > Labels: eap6_prd_req > Fix For: 7.1.0.Final > > > 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

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka edited comment on AS7-3128 at 1/24/12 7:09 PM: ------------------------------------------------------------ Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. I suggest something like {code:xml} <waitForPorts>5050 9990</waitForPorts> {code} was (Author: ozizka): Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-1820) CLONE - CLI - provide description for "add-jms-cf " command with examples

by Rajesh Rajasekaran (JIRA)

[ https://issues.jboss.org/browse/AS7-1820?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-1820: ------------------------------------ Fix Version/s: 7.1.1.Final (was: 7.1.0.Final) > CLONE - CLI - provide description for "add-jms-cf " command with examples > ------------------------------------------------------------------------- > > Key: AS7-1820 > URL: https://issues.jboss.org/browse/AS7-1820 > Project: Application Server 7 > Issue Type: Feature Request > Components: CLI > Affects Versions: 7.0.1.Final > Reporter: Miroslav Novak > Assignee: Alexey Loubyansky > Fix For: 7.1.1.Final > > > Command "add-jms-cf" is missing description for all attributes. Could it be improved, please? Also examples of usages would be very helpful. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-3128) Arquillian doesn't wait for the process to really end, causes problems like "port in use".

by Ondrej Zizka (JIRA)

[ https://issues.jboss.org/browse/AS7-3128?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-3128: ----------------------------------- Could Arq wait for some specified processes to be free? I am affraid that would be the only option - seems like it's possible that the OS could keep the port for a while. > Arquillian doesn't wait for the process to really end, causes problems like "port in use". > ------------------------------------------------------------------------------------------ > > Key: AS7-3128 > URL: https://issues.jboss.org/browse/AS7-3128 > Project: Application Server 7 > Issue Type: Bug > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Blocker > Labels: arq_qe_blocker > > (05:54:09) dmlloyd: when running with JDWP enabled on the client or server, I occasionally get bind exceptions due to address in use > (05:54:25) dmlloyd: which means that tests are running into each other without waiting for termination of the previous one > (05:54:35) dmlloyd: which may also be causing other issues > (05:56:04) ozizka: dmlloyd: Yes, lbarrerio observed similar problem too, > (05:56:47) ozizka: And that's arq's issue too - there's no way to get around this currently AFAIK. Or is there? > (05:57:05) ozizka: Perhaps "manually" wait in @AfterClass or such > (05:57:07) dmlloyd: yeah, it can wait for the child process to terminate > (05:57:07) ozizka: which is ugly > (05:57:14) dmlloyd: I mean arq should > (05:59:17) ozizka: dmlloyd: Do you have it somewhere on hudson? > (05:59:24) ozizka: dmlloyd: It never happened to me actually > (05:59:49) ozizka: Send me a log if you have one handy > (06:01:35) dmlloyd: ozizka: no, try running with this command though: > {code} > mvn -DallTests install -Djpda -Dsurefire.jpda.args=-Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n \ > -Dmaven.surefire.debug="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" > {code} > (06:13:56) ozizka: dmlloyd: That's on linux? > (06:14:03) dmlloyd: yes -- 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, 3 months

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 January 2012