January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1905) Proper handling the timeout issue in receive(timeout)

by Yong Hao Gao (Created) (JIRA)

Proper handling the timeout issue in receive(timeout) ----------------------------------------------------- Key: JBMESSAGING-1905 URL: https://issues.jboss.org/browse/JBMESSAGING-1905 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.SP3, 1.4.0.SP3.CP14 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP15, 1.4.8.SP4 -- 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

11 years, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1880) JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer)

by Yong Hao Gao (JIRA)

JMSRedelivered not properly set when a client exits without closing the JMS resources (connection, session, consumer) --------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1880 URL: https://issues.jboss.org/browse/JBMESSAGING-1880 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 If a client consumer receives a message and exit without acknowledging it or close the connection/session/consumer object, the message will be cancelled at the server side. When the message is delivered, its JMSRedelivered flag should be true. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1870) ClientSocketWrapper constructors have a redundant call to createStreams()

by Ron Sigal (JIRA)

ClientSocketWrapper constructors have a redundant call to createStreams() ------------------------------------------------------------------------- Key: JBMESSAGING-1870 URL: https://issues.jboss.org/browse/JBMESSAGING-1870 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Ron Sigal Priority: Minor org.jboss.jms.client.remoting.ClientSocketWrapper is derived from org.jboss.remoting.transport.socket.ClientSocketWrapper. The constructors of the former look like public ClientSocketWrapper(Socket socket) throws IOException { super(socket); createStreams(socket, null); } public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception { super(socket, metadata, timeout); createStreams(socket, metadata); } and the constructors of the latter look like public ClientSocketWrapper(Socket socket) throws IOException { super(socket); createStreams(socket, null); } public ClientSocketWrapper(Socket socket, Map metadata, Integer timeout) throws Exception { super(socket, timeout); createStreams(socket, metadata); } The calls to createStreams() in the JBossMessaging versions of ClientSocketWrapper is redundant. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1866) Adapt JBM tests to new failover model

by Yong Hao Gao (JIRA)

Adapt JBM tests to new failover model ------------------------------------- Key: JBMESSAGING-1866 URL: https://issues.jboss.org/browse/JBMESSAGING-1866 Project: JBoss Messaging Issue Type: Task Components: Tests and Performance Affects Versions: 1.4.8.GA, 1.4.0.SP3.CP12 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP13, 1.4.8.SP1 In jbm test suite some tests will fail if the 'keepOldFailoverModel' is set to false. This is because with new model, the failover for a dead node doesn't happen immediately. This affects all tests which expect a failover to happen after a certain timeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
11
0 / 0

[JBoss JIRA] Created: (AS7-1440) allow default persistence provider to be configured

by Scott Marlow (JIRA)

allow default persistence provider to be configured --------------------------------------------------- Key: AS7-1440 URL: https://issues.jboss.org/browse/AS7-1440 Project: Application Server 7 Issue Type: Feature Request Components: JPA / Hibernate Reporter: Scott Marlow Fix For: 7.1.0.Alpha1 Allow default persistence provider to be configured, so that a different provider could be used by default. This helps improve our JPA plugability (users preferred persistence provider can become the default). Without this feature, the user could instead make application changes to the persistence.xml to accomplish the same (not always possible if user cannot make app changes). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWEB-193) SeLinux policy for JBoss Enterprise Web Server

by Sam Weaver (JIRA)

SeLinux policy for JBoss Enterprise Web Server ---------------------------------------------- Key: JBWEB-193 URL: https://issues.jboss.org/browse/JBWEB-193 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Sam Weaver Assignee: Remy Maucherat Priority: Minor SeLinux causes JBoss EWS to stop working, or randomly fail to start. Therefore requesting an SeLinux policy for JBoss EWS. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-2371) Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console

by Jim Tyrrell (Created) (JIRA)

Web Console: In the past the JMX console could flush queues/topics, etc, can that be added to the console ---------------------------------------------------------------------------------------------------------- Key: AS7-2371 URL: https://issues.jboss.org/browse/AS7-2371 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun -- 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

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (AS7-2334) Web Console: Eager clustering checkbox enabled/disabled

by Jim Tyrrell (Created) (JIRA)

Web Console: Eager clustering checkbox enabled/disabled ------------------------------------------------------- Key: AS7-2334 URL: https://issues.jboss.org/browse/AS7-2334 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Out of the box this probably should be checked by default so you get the typical in the past JGroups messages in the logging showing that clustering between two instances has occurred. -- 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

11 years, 8 months

6
7
0 / 0

[JBoss JIRA] (JBCL-181) Cache getResources in all layers

by Ales Justin (Created) (JIRA)

Cache getResources in all layers -------------------------------- Key: JBCL-181 URL: https://issues.jboss.org/browse/JBCL-181 Project: JBoss ClassLoader Issue Type: Enhancement Components: ClassLoader Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.4.0.Alpha1 -- 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

11 years, 8 months

3
3
0 / 0

[JBoss JIRA] (AS7-3019) Arquillian Managed Container fails to start JBoss AS with ServiceNotFoundException

by Martin Gencur (Created) (JIRA)

Arquillian Managed Container fails to start JBoss AS with ServiceNotFoundException ---------------------------------------------------------------------------------- Key: AS7-3019 URL: https://issues.jboss.org/browse/AS7-3019 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Martin Gencur Assignee: Aslak Knutsen Affects JBossAS 7.1.0.CR1-SNAPSHOT (HEAD=d9e236d - Update timeout to be more reasonable with load) When I'm starting AS with jboss-as-arquillian-container-managed (7.1.0.CR1-SNAPSHOT), I get the following exception (no configuration in standalone.xml was changed after building the distribution): 14:57:41,690 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started in 3547ms - Started 131 of 200 services (68 services are passive or on-demand) 14:57:42,037 ERROR [org.jboss.as.controller.management-operation] (pool-1-thread-1) JBAS014612: Operation ("read-attribute") failed - address: ({ "socket-binding-group" => "standard-sockets", "socket-binding" => "undefined" }): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.binding.undefined not found at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.1.GA.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler$1.execute(BindingMetricHandlers.java:66) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler.execute(BindingMetricHandlers.java:76) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$BoundAddressHandler.execute(BindingMetricHandlers.java:106) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadAttributeHandler.doExecute(GlobalOperationHandlers.java:452) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:974) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:432) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:98) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$3$1.doExecute(AbstractMessageHandler.java:268) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:424) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Starting the same AS manually works fine. -- 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

11 years, 8 months

5
4
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