July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8778) Problem with deployment order of EAR and JMS queues

by Frank Langelage (JIRA)

Problem with deployment order of EAR and JMS queues --------------------------------------------------- Key: JBAS-8778 URL: https://issues.jboss.org/browse/JBAS-8778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers, JMS (HornetQ) Affects Versions: 6.0.0.Final Reporter: Frank Langelage Assignee: Ales Justin Our application deployed as one EAR file contains two MDB. The queues are defined in $JBOSS_HOME/deploy/hornetq/mbi2e-lafr-sb2000-ipc-hornetq-jms.xml: <?xml version="1.0" encoding="UTF-8"?> <configuration xmlns="urn:hornetq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd"> <queue name="mbi2e-lafr-sb2000-ipc/MessageDistributorQueue"> <entry name="queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue"/> </queue> <queue name="mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue"> <entry name="queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue"/> </queue> </configuration> If I first startup JBossAS, already including the queue definitions shown above, and then deploy my ear file everything is fine. No Errors. But if I bounce and restart the engine after that, with everything deployed, I get Warnings and Errors. Right after the start of the MDB listening on the 'MessageDistributorQueue' I get this: 11:48:58,754 WARN [HornetQActivation] Failure in HornetQ activation org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:] at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:] at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:] at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:] at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:] at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:573) [:] at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT] at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7] And then a few more times during the further startup process I see this: 11:49:00,759 INFO [HornetQActivation] Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 11:49:00,998 ERROR [HornetQActivation] Unable to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CONSUME for address jms.queue.mbi2e-lafr-sb2000-ipc/MessageDistributorQueue] at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:] at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateConsumer(ClientSessionImpl.java:1556) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:447) [:] at org.hornetq.core.client.impl.ClientSessionImpl.createConsumer(ClientSessionImpl.java:392) [:] at org.hornetq.core.client.impl.DelegatingSession.createConsumer(DelegatingSession.java:201) [:] at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:165) [:] at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:] at org.hornetq.ra.inflow.HornetQActivation.handleFailure(HornetQActivation.java:539) [:] at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:577) [:] at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.1-SNAPSHOT] at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7] at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:821) [:2.0.0.CR7] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7] At the very end of the startup process connect succeeds: 2010-12-28 11:49:09,133 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/SalesOrderImportQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 2010-12-28 11:49:09,156 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Attempting to reconnect org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@1fe97f9 destination=queue/mbi2e-lafr-sb2000-ipc/MessageDistributorQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15) 2010-12-28 11:49:09,236 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 2010-12-28 11:49:09,241 INFO [org.apache.coyote.http11.Http11Protocol.start] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 2010-12-28 11:49:09,243 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer.run] (Thread-2) JBossAS [6.0.1.SNAPSHOT "Neo"] Started in 3m:57s:688ms 2010-12-28 11:49:09,259 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-1) Reconnected with HornetQ 2010-12-28 11:49:09,292 INFO [org.hornetq.ra.inflow.HornetQActivation.info] (pool-1-thread-2) Reconnected with HornetQ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

7
16
0 / 0

[JBoss JIRA] Created: (AS7-925) Expose the transaction logs via the domain management API

by Brian Stansberry (JIRA)

Expose the transaction logs via the domain management API --------------------------------------------------------- Key: AS7-925 URL: https://issues.jboss.org/browse/AS7-925 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, Transactions Reporter: Brian Stansberry Fix For: 7.1.0.CR1 Michael Musgrove wrote: "We also have an MBean for exposing the transaction logs - it would be highly desirable to expose these via the management console (com.arjuna.ats.arjuna.tools.osb.mbean.ObjStoreBrowser). However, the implementation requires the presence of an MBeanServer." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JGRP-1025) Harden FLUSH

by Bela Ban (JIRA)

Harden FLUSH ------------ Key: JGRP-1025 URL: https://jira.jboss.org/jira/browse/JGRP-1025 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Vladimir Blagojevic Fix For: 2.9 Make sure no FLUSH is left hanging, e.g. due to the crash of the flush leader after the START-FLUSH round. In other words, make analyze the code and make sure STOP-FLUSH is eventually called. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-9121) CLONE - Cannot build JBoss AS 7 using OpenJDK

by Shelly McGowan (JIRA)

CLONE - Cannot build JBoss AS 7 using OpenJDK --------------------------------------------- Key: JBAS-9121 URL: https://issues.jboss.org/browse/JBAS-9121 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 7.0.0.Beta1 Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 7.0.0.Beta2 Compilation fails with: ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.1:compile (default-compile) on project jboss-as-arquillian-common: Compilation failure [ERROR] /qa/services/hudson/hudson_workspace/workspace/JBoss-AS-7.0.x-testSuite-openjdk/arquillian/common/src/main/java/org/jboss/as/arquillian/container/JBossASDeploymentPackager.java:[59,16] inconvertible types [ERROR] found : org.jboss.shrinkwrap.api.Archive<capture#470 of ?> [ERROR] required: org.jboss.shrinkwrap.api.spec.WebArchive I've confirmed this is the latest version of OpenJDK: java-1.6.0-openjdk-1.6.0.0-1.20.b17.el5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

7
10
0 / 0

[JBoss JIRA] Created: (JASSIST-127) interface proxy creation fails if there are methods with covariant return types

by Paul Pogonyshev (JIRA)

interface proxy creation fails if there are methods with covariant return types ------------------------------------------------------------------------------- Key: JASSIST-127 URL: https://jira.jboss.org/browse/JASSIST-127 Project: Javassist Issue Type: Bug Affects Versions: 3.12.0.GA Environment: Java 1.6. Reporter: Paul Pogonyshev Assignee: Shigeru Chiba Creation of proxy class for interface Bar fails: public interface Foo { Foo getSelf (); } public interface Bar extends Foo { Bar getSelf (); } This is because of covariant return types of method getSelf(). However, as this is permitted by the language (i.e. subtype can restrict the return type further), I consider this a bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBLOGGING-61) Support for log4j Logger.getLogger(String, LogFactory)

by Elias Ross (JIRA)

Support for log4j Logger.getLogger(String, LogFactory) ------------------------------------------------------ Key: JBLOGGING-61 URL: https://issues.jboss.org/browse/JBLOGGING-61 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Elias Ross Assignee: David Lloyd Attachments: 0001-Create-custom-appender-use-it-to-output-messages-if-.patch org.apache.log4j.Logger(String, LogFactory) does not function. This patch adds support using a custom Log4j appender that sends messages to JBoss's appender. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1617) Create a MC bean handle in the likes of java.ejb.Handle

by Carlo de Wolf (JIRA)

Create a MC bean handle in the likes of java.ejb.Handle ------------------------------------------------------- Key: EJBTHREE-1617 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1617 Project: EJB 3.0 Issue Type: Feature Request Components: common Reporter: Carlo de Wolf Assignee: Ales Justin Priority: Critical Fix For: 1.0.0-CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-153) EJB timer clustering and failover support

by Galder Zamarreno (JIRA)

EJB timer clustering and failover support ----------------------------------------- Key: JBCLUSTER-153 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-153 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Galder Zamarreno Assigned To: Brian Stansberry Support for clustered EJB timer service providing failover -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-9028) JARs with OSGi metadata cannot be used by EE

by David Lloyd (JIRA)

JARs with OSGi metadata cannot be used by EE -------------------------------------------- Key: JBAS-9028 URL: https://issues.jboss.org/browse/JBAS-9028 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Critical Fix For: 7.0.0.Beta3 If a JAR such as a JDBC driver or other service provider (like MSC ServiceActivation) is deployed, and that JAR happens to have OSGi metadata on it, the deployment is invisible to, or incompatible with, most of the other deployers which actually enable these services, usually on behalf of one or more subsystems. We need OSGi JARs to coexist on at least some level. A first step might be to have OSGi's modularization process use the same attachment set so that modules and resource roots can reliably be found in the DU attachments. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

6
10
0 / 0

[JBoss JIRA] Created: (JBEE-73) Create a uber-jar for the JBoss JavaEE APIs

by Aslak Knutsen (JIRA)

Create a uber-jar for the JBoss JavaEE APIs ------------------------------------------- Key: JBEE-73 URL: https://issues.jboss.org/browse/JBEE-73 Project: JBoss JavaEE APIs Issue Type: Feature Request Components: javaee_6.0_spec Affects Versions: 1.0.0.Final-javaee_6.0 Reporter: Aslak Knutsen Assignee: Shelly McGowan My Windows users are having problems.. Windows has a limitation on how long the ClassPath can be, when you start to include libraries like, jbossas-client(249 deps) and jboss-javaee-6.0 (x) windows refuse to execute the java process. http://community.jboss.org/message/586381#586381 Would it be possible to release a uber-jar v. of the jboss-javaee-6.0 pom? Basically merge it into one artifact. Most users don't care about the individual specs, they use EE. And as long as the pom is there as well, they have both options. <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-6.0-all</artifactId> <-- using a different artifact id is probably easier to setup --> <version>1.0.0.Final</version> <type>jar</type> <-- a single jar --> </dependency> http://maven.apache.org/plugins/maven-shade-plugin/ ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
10
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 July 2011