July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9122) Integrate hornetq-ra.rar into AS 7

by Carlo de Wolf (JIRA)

Integrate hornetq-ra.rar into AS 7 ---------------------------------- Key: JBAS-9122 URL: https://issues.jboss.org/browse/JBAS-9122 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: Carlo de Wolf Assignee: Clebert Suconic Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

5
15
0 / 0

[JBoss JIRA] Created: (JBAS-8971) Implement JMS MDB integration

by David Lloyd (JIRA)

Implement JMS MDB integration ----------------------------- Key: JBAS-8971 URL: https://issues.jboss.org/browse/JBAS-8971 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1887) Messages lost during orderly shutdown of JBoss Messaging server

by Tom Ross (JIRA)

Messages lost during orderly shutdown of JBoss Messaging server --------------------------------------------------------------- Key: JBMESSAGING-1887 URL: https://issues.jboss.org/browse/JBMESSAGING-1887 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.8.SP1, 1.4.7.GA Environment: JBoss EAP 5.1.0 Reporter: Tom Ross Assignee: Yong Hao Gao During orderly shutdown of JBoss EAP server/Messaging server messages are being lost. In the above test case a publisher is publishing messages to a topic (which has several durable subscribers) on a JBM server while the user uses control-c to shutdown the server or runs shutdown.sh script. The server will first shutdown the topic service (subscribers) and then the server peer and post office. When the subscribers has been just shutdown but the server peer and post office is still alive, if a message are sent in to the post office and post office tries to route the message to subscribers, the subscribers are already deactivated so it didn't get route. In this case the post office does not throw any exceptions back to the publisher. Instead it returns without error. Following message will apear in the log file: (WorkerThread#1[192.168.1.110:56860]) Queue[37225610/2/2952-guest.mdbOne] is not active, returning null delivery for Reference[41396777574629398]:RELIABLE -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-1280) WebComponentProcessor tries to create component out of empty classname

by jaikiran pai (JIRA)

WebComponentProcessor tries to create component out of empty classname ---------------------------------------------------------------------- Key: AS7-1280 URL: https://issues.jboss.org/browse/AS7-1280 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.0.0.Final Reporter: jaikiran pai Assignee: jaikiran pai A user reported error: {code} 02:06:05,229 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."projvehimerc.war". PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."projvehimerc.war". PARSE: Failed to process phase PARSE of deployment "projvehimerc.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) 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.lang.IllegalArgumentException: Empty name segment is not allowed at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) at org.jboss.as.ee.component.ComponentDescription.<init>(ComponentDescription.java:145) at org.jboss.as.web.deployment.component.WebComponentDescription.<init>(WebComponentDescription.java:37) at org.jboss.as.web.deployment.component.WebComponentProcessor.deploy(WebComponentProcessor.java:126) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more {code} Please see the referenced forum thread for details. -- 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: (AS7-1256) <jar-file> in persistence.xml does not work

by Stuart Douglas (JIRA)

<jar-file> in persistence.xml does not work ------------------------------------------- Key: AS7-1256 URL: https://issues.jboss.org/browse/AS7-1256 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.CR1, 7.0.0.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.0.1.Final HibernateAnnotationScanner does not correctly handle jar files other than the one contained in persistence.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: (JBRULES-3125) Including compression support (gzip) to optimize network traffic between server and agent

by Tarley Lana (JIRA)

Including compression support (gzip) to optimize network traffic between server and agent ----------------------------------------------------------------------------------------- Key: JBRULES-3125 URL: https://issues.jboss.org/browse/JBRULES-3125 Project: Drools Issue Type: Patch Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.1.FINAL Environment: drools-5.1.1-guvnor-standalone, jboss-4.2.3.GA Reporter: Tarley Lana Assignee: Mark Proctor This patch makes the class "org.drools.io.impl.UrlResource" support the download of compressed rules. Below are the settings required to enable transmission of compressed rules over the network: SERVER SIDE 1) In this example I used the "drools-5.1.1-guvnor-standalone" as a rule base; 2) Include the following line in the file "{JBOSS-HOME}\server\default\deploy\jboss-web.deployer\server.xml" to enable compression of the rules: <Connector port="8080" address="${jboss.bind.address}" maxThreads="250" maxHttpHeaderSize="8192" emptySessionPath="true" protocol="HTTP/1.1" enableLookups="false" redirectPort="8443" acceptCount="100" connectionTimeout="20000" disableUploadTimeout="true" compression="force" compressableMimeType="application/x-download" compressionMinSize="100"/> CLIENT SIDE 1) Set the "ChangeSet.xml" for the rules of the server as the example below: <change-set xmlns='http://drools.org/drools-5.0/change-set' xmlns:xs='http://www.w3.org/2001/XMLSchema-instance' xs:schemaLocation='http://drools.org/drools-5.0/change-set http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-api/src/...' > <add>  <resource source='http://127.0.0.1:8080/drools-guvnor/org.drools.guvnor.Guvnor/package/arau...' type='PKG' basicAuthentication='enabled' username='ecf' password='senha'/> </add> </change-set> -- 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-1269) Injection via @EJB fails

by John Ament (JIRA)

Injection via @EJB fails ------------------------ Key: AS7-1269 URL: https://issues.jboss.org/browse/AS7-1269 Project: Application Server 7 Issue Type: Bug Reporter: John Ament https://gist.github.com/1079559 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1251) Threads subsystem writer generates incorrect XML for unbounded queue thread pool

by Trustin Lee (JIRA)

Threads subsystem writer generates incorrect XML for unbounded queue thread pool -------------------------------------------------------------------------------- Key: AS7-1251 URL: https://issues.jboss.org/browse/AS7-1251 Project: Application Server 7 Issue Type: Bug Reporter: Trustin Lee {code} <unbounded-queue-thread-pool name="jgroups"> {code} is written back as: {code} <unbounded-queue-thread-pool blocking="jgroups"> </code> Hence making the next startup fail. Similar issue was found and fixed (AS7-233). We need to check all queue types. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-1252) Infinispan subsystem writer generates incorrect XML

by Trustin Lee (JIRA)

Infinispan subsystem writer generates incorrect XML --------------------------------------------------- Key: AS7-1252 URL: https://issues.jboss.org/browse/AS7-1252 Project: Application Server 7 Issue Type: Bug Reporter: Trustin Lee The following XML configuration: {code} <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="default"> <cache-container name="default" default-cache="default" listener-executor="infinispan-listener" eviction-executor="infinispan-eviction" replication-queue-executor="infinispan-repl-queue"> <transport executor="infinispan-transport"/> <distributed-cache name="default" start="EAGER" mode="SYNC" /> </cache-container> </subsystem> <subsystem xmlns="urn:jboss:domain:datagrid:endpoint:1.0"> ... {code} is written back to: {code} <subsystem xmlns="urn:jboss:domain:infinispan:1.0" default-cache-container="default"> <cache-container name="default" default-cache="default" listener-executor="infinispan-listener" eviction-executor="infinispan-eviction" replication-queue-executor="infinispan-repl-queue"> <transport executor="infinispan-transport"> <distributed-cache mode="SYNC" name="default" start="EAGER"/> </transport> </cache-container> <subsystem xmlns="urn:jboss:domain:datagrid:endpoint:1.0"> ... {code} making the subsequent startup fail. -- 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-1224) Document the "management resource" notion in the Admin Guide

by Brian Stansberry (JIRA)

Document the "management resource" notion in the Admin Guide ------------------------------------------------------------ Key: AS7-1224 URL: https://issues.jboss.org/browse/AS7-1224 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Final In the "Core management concepts" section of the Admin Guide, add a section describing what a management resource is and outlining the basic resource tree server for both a standalone server and a managed domain. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011