July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1214) Cannot override bind address of pbcast.STREAMING_STATE_TRANSFER

by Paul Ferraro (JIRA)

Cannot override bind address of pbcast.STREAMING_STATE_TRANSFER --------------------------------------------------------------- Key: AS7-1214 URL: https://issues.jboss.org/browse/AS7-1214 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.0.0.CR1 Reporter: Paul Ferraro Assignee: Paul Ferraro You should be able to override the bind_addr by defining a specific socket-binding, however, this only sets the bind_port, not the bind_addr. That's the bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1240) Allow FS deployment scanner to treat deleting deployment content as a trigger for undeploy

by Brian Stansberry (JIRA)

Allow FS deployment scanner to treat deleting deployment content as a trigger for undeploy ------------------------------------------------------------------------------------------ Key: AS7-1240 URL: https://issues.jboss.org/browse/AS7-1240 Project: Application Server 7 Issue Type: Feature Request Components: Server Affects Versions: 7.0.0.CR1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.1.Final Currently you have to delete the .deployed file to trigger an undeploy. FileSystemDeploymentService should also treat deleting the deployment content as a trigger. Deleting the content *is the incorrect way to trigger undeployment of an exploded archive.* It's perfectly fine for a zipped deployment, but for an exploded deployment it removes the content out from under the appserver before the AS has a chance to properly undeploy. Still, even though deleting the content as a trigger is the wrong thing to do in the exploded case, it's the more intuitive thing to do in the non-exploded case, and having the AS use it as a trigger in the exploded case doesn't increase the harm. The content is gone; the app is broken, might as well try and undeploy it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1159) Running commands from file in CLI without a connection results in a NullPointerException

by Darran Lofthouse (JIRA)

Running commands from file in CLI without a connection results in a NullPointerException ---------------------------------------------------------------------------------------- Key: AS7-1159 URL: https://issues.jboss.org/browse/AS7-1159 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.0.CR1 Reporter: Darran Lofthouse Assignee: Alexey Loubyansky Fix For: 7.1.0.Alpha1 The following NPE is reported if a file is executed without specifying to connect: - java.lang.NullPointerException at org.jboss.as.cli.handlers.batch.BatchRunHandler.doHandle(BatchRunHandler.java:82) at org.jboss.as.cli.handlers.CommandHandlerWithHelp.handle(CommandHandlerWithHelp.java:92) at org.jboss.as.cli.CommandLineMain.processLine(CommandLineMain.java:437) at org.jboss.as.cli.CommandLineMain.processFile(CommandLineMain.java:363) at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:257) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:270) at org.jboss.modules.Main.main(Main.java:313) The following command from the CR1 distro will reproduce: - ./jboss-admin.sh --file=scripts/secure-standalone-mgmt.cli In addition to this it is not possible to specify the address of the native interface to connect to from the command line when using --file, if --connect is specified only the default host and port will be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1249) Implement EndpointDeployer

by Carlo de Wolf (JIRA)

Implement EndpointDeployer -------------------------- Key: AS7-1249 URL: https://issues.jboss.org/browse/AS7-1249 Project: Application Server 7 Issue Type: Sub-task Components: JCA Reporter: Carlo de Wolf Assignee: Jesper Pedersen Priority: Critical Fix For: 7.1.0.CR1 {noformat} org.jboss.jca.core.spi.rar.NotFoundException: IJ000855: hornetq-ra isn't registered at org.jboss.jca.core.rar.SimpleResourceAdapterRepository.getMessageListeners(SimpleResourceAdapterRepository.java:263) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-1186) EJB interceptor not invoked

by Juergen Zimmermann (JIRA)

EJB interceptor not invoked --------------------------- Key: AS7-1186 URL: https://issues.jboss.org/browse/AS7-1186 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Juergen Zimmermann I'll provide a testcase showing that an EJB 3 interceptor is not invoked although defined in MEAT-INF/ejb-jar.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (AS7-1233) HornetQ RA gives NPE when no activationSpecs are supplied

by Carlo de Wolf (JIRA)

HornetQ RA gives NPE when no activationSpecs are supplied --------------------------------------------------------- Key: AS7-1233 URL: https://issues.jboss.org/browse/AS7-1233 Project: Application Server 7 Issue Type: Bug Reporter: Carlo de Wolf Priority: Minor {noformat} java.lang.NullPointerException at java.util.concurrent.ConcurrentHashMap.put(ConcurrentHashMap.java:882) [:1.6.0_24] at org.hornetq.ra.HornetQResourceAdapter.endpointActivation(HornetQResourceAdapter.java:155) at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.start(MessageDrivenComponent.java:163) at org.jboss.as.ee.component.ComponentStartService.start(ComponentStartService.java:44) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) ... 4 more {noformat} It should throw a {{NotSupportedException}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
3
0 / 0

[JBoss JIRA] Created: (AS7-1248) Presence of application.xml in .ear causes nested .sar and .war deployments to be skipped from deployment

by jaikiran pai (JIRA)

Presence of application.xml in .ear causes nested .sar and .war deployments to be skipped from deployment --------------------------------------------------------------------------------------------------------- Key: AS7-1248 URL: https://issues.jboss.org/browse/AS7-1248 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.0.0.CR1 Reporter: jaikiran pai Assignee: jaikiran pai If a .ear contains a application.xml as follows: {code:xml} <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" version="6"> </application> {code} and also packages nested .sar (and .war) files within the .ear, then those nested deployments are skipped. Removing the application.xml "fixes" the issue. The nested deployment should be picked up even in the presence of the application.xml. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-941) Encountered an exception while porting a Seam application from AS5 to AS7, root cause ZipException

by Sande Gilda (JIRA)

Encountered an exception while porting a Seam application from AS5 to AS7, root cause ZipException -------------------------------------------------------------------------------------------------- Key: AS7-941 URL: https://issues.jboss.org/browse/AS7-941 Project: Application Server 7 Issue Type: Bug Affects Versions: No Release Environment: Fedora 14, porting an EAP5.x application to AS7, Reporter: Sande Gilda I am porting the TopicIndex application that was built on EAP5.x to AS7. I have worked around a number of ClassNotFound and other issues. My current build is based on git://github.com/jbossejb3/jboss-as.git which as a fix for AS7-910 and I have coded around AS7-896. I am now seeing this exception in the log: 09:46:45,570 INFO [javax.servlet.ServletContextListener] (MSC service thread 1-7) Welcome to Seam null 09:46:45,588 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/TopicIndex]] (MSC service thread 1-7) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.RuntimeException: Error handling file /content/TopicIndex.war/WEB-INF/lib/jboss-seam-remoting.jar at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:134) [jboss-seam.jar:] at org.jboss.seam.deployment.URLScanner.handle(URLScanner.java:107) [jboss-seam.jar:] at org.jboss.seam.deployment.URLScanner.scanResources(URLScanner.java:90) [jboss-seam.jar:] at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:] at org.jboss.seam.init.Initialization.create(Initialization.java:130) [jboss-seam.jar:] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3368) [jbossweb-7.0.0.CR1.jar:7.0.0.Beta4-SNAPSHOT] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3817) [jbossweb-7.0.0.CR1.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:70) [jboss-as-web-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) [:1.6.0_25] at java.util.zip.ZipFile.<init>(ZipFile.java:127) [:1.6.0_25] at java.util.zip.ZipFile.<init>(ZipFile.java:144) [:1.6.0_25] at org.jboss.seam.deployment.URLScanner.handleArchiveByFile(URLScanner.java:123) [jboss-seam.jar:] ... 12 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Closed: (AS7-766) EAR and other top level deployments should be Atomic

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-766?page=com.atlassian.jira.plugin.sy... ] Stuart Douglas closed AS7-766. ------------------------------ Fix Version/s: 7.0.0.Final Resolution: Cannot Reproduce Bug This behaviour is already present > EAR and other top level deployments should be Atomic > ---------------------------------------------------- > > Key: AS7-766 > URL: https://issues.jboss.org/browse/AS7-766 > Project: Application Server 7 > Issue Type: Bug > Components: Server > Reporter: Brad Maxwell > Fix For: 7.0.0.Final > > > Issue: If an ear or other deployment that contains sub-deployments is deployed and one of the sub-deployments fails to deploy, the ear should fail and unwind all sub-deployments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9266) java.lang.reflect.UndeclaredThrowableException when using @ApplicationException in combination with @InterceptorBinding

by Felix Ullrich (JIRA)

java.lang.reflect.UndeclaredThrowableException when using @ApplicationException in combination with @InterceptorBinding ----------------------------------------------------------------------------------------------------------------------- Key: JBAS-9266 URL: https://issues.jboss.org/browse/JBAS-9266 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB Affects Versions: 6.0.0.Final Reporter: Felix Ullrich Assignee: Carlo de Wolf If I'm using @InterceptorBinding a thrown Exception out of an EJB marked with @ApplicationException dont reach the client. Instead of the @ApplicationException I get a java.lang.reflect.UndeclaredThrowableException. I've attached a minimal example. My client-main-program looks like this: {code:title=Bar.java|borderStyle=solid} public static void main(final String[] args) throws NamingException { final InitialContext context = new InitialContext(); context.lookup("StatefulTestBean/remote"); try { statefulTest.throwApplicationError(); } catch (final Exception e) { System.out.println(e); } } {code} The excepted output would be: {code} error.AppError {code} but its: {code} java.lang.reflect.UndeclaredThrowableException {code} If you comment out the annotation @InterceptorAnnotation in the StatefulTestBean.java and redeploy the application then everything is fine - you get the expetced AppError-Exception. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

6
18
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011