April 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-690) Ability to modify server-group, subresource system properties

by Heiko Braun (JIRA)

Ability to modify server-group, subresource system properties ------------------------------------------------------------- Key: AS7-690 URL: https://issues.jboss.org/browse/AS7-690 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9296) Deployment from hosted mode fails

by Heiko Braun (JIRA)

Deployment from hosted mode fails --------------------------------- Key: JBAS-9296 URL: https://issues.jboss.org/browse/JBAS-9296 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta4 The binary gets uploaded, but seems to be corrupted. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4859) No facility to change location of Tomcat 'work' directory (catalina home)

by Chris Lee (JIRA)

No facility to change location of Tomcat 'work' directory (catalina home) ------------------------------------------------------------------------- Key: JBAS-4859 URL: http://jira.jboss.com/jira/browse/JBAS-4859 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.1.GA Environment: n/a Reporter: Chris Lee Assigned To: Remy Maucherat Presently the location for Tomcat's 'work' directory is hard-coded to jboss.server.home.dir; it would be nice to override this (as is done with jboss.server.data.dir, jboss.server.log.dir, and jboss.server.temp.dir) to move 'data' directories outside the server home. -- 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

15 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-685) DomainControllerImpl treats some ops intended for a single host as domain-wide

by Brian Stansberry (JIRA)

DomainControllerImpl treats some ops intended for a single host as domain-wide ------------------------------------------------------------------------------ Key: AS7-685 URL: https://issues.jboss.org/browse/AS7-685 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Beta3 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.Beta4 See comments on AS7-270. If DomainControllerImpl analyzes an operation and determines it requires a two-phase approach (exec on HostController(s) and then push to servers) the master DC treats it as a domain-wide op even if it's entirely limited to a single remote host. If it's limited to a single remote host, the master DC should route it to that host and let it coordinate the two-phase op. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9201) NPE in Server on bad input

by Heiko Rupp (JIRA)

NPE in Server on bad input -------------------------- Key: JBAS-9201 URL: https://issues.jboss.org/browse/JBAS-9201 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Heiko Rupp Priority: Minor With this (bogus) input over the json interface, the server throws a NPE and does not return an error message to the caller {"address":[{"host":"/host/pintsize"},{"server-config":"newServer"}],"operation":"add","name":"newServer","auto-start":"true","group":"main-server-group"} Stack trace is [Host Controller] 11:55:21,170 ERROR [org.jboss.as.domain.http.api] (pool-1-thread-10) Unexpected error executing model request: java.lang.NullPointerException [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl.execute(DomainControllerImpl.java:354) [Host Controller] at org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:101) [Host Controller] at org.jboss.as.domain.controller.DomainControllerImpl.execute(DomainControllerImpl.java:219) [Host Controller] at org.jboss.as.domain.http.server.DomainHttpServer.processRequest(DomainHttpServer.java:173) [Host Controller] at org.jboss.as.domain.http.server.DomainHttpServer.handle(DomainHttpServer.java:104) [Host Controller] at com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) [:1.6.0_24] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Resolved: (AS7-655) Support JNDI binding of cache containers

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-655?page=com.atlassian.jira.plugin.sy... ] Paul Ferraro resolved AS7-655. ------------------------------ Resolution: Done > Support JNDI binding of cache containers > ---------------------------------------- > > Key: AS7-655 > URL: https://issues.jboss.org/browse/AS7-655 > Project: Application Server 7 > Issue Type: Enhancement > Components: Clustering > Affects Versions: 7.0.0.Beta3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.0.0.Beta4 > > > This is needed for Hibernate 2LC integration. > Leverage BinderService to bind cache containers to JNDI. > Add jndi-name attribute to <cache-container>. > A dependent service can declare a dependency on the jndi binding, to demand relevant cache manager to start. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-9025) Update Maven source plugin to include javadoc resources.

by David Lloyd (JIRA)

Update Maven source plugin to include javadoc resources. -------------------------------------------------------- Key: JBAS-9025 URL: https://issues.jboss.org/browse/JBAS-9025 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.CR1 Ensure that the Maven source plugin includes source resources including src/main/javadoc files in the source bundle. Ensure that the org.jboss:parent POM includes the correct source plugin version. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2718) Ruleflows are not working correctly in Stateless session

by GrÃ©goire Botquin (JIRA)

Ruleflows are not working correctly in Stateless session -------------------------------------------------------- Key: JBRULES-2718 URL: https://jira.jboss.org/browse/JBRULES-2718 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: Windows 7 Reporter: GrÃ©goire Botquin Assignee: Mark Proctor We are currently migrating from 5.0.1 to 5.1.1. and our RuleFlows are not working anymore. After some investigations it seems it could be related to the knowledgesession type (Statefull / Stateless). When launching a ruleflow in stateless session, it seems that the process stops it's execution after the first RuleFlowGroup found in the flow (maybe after some other node types (?)), and that without any reason nor exception/error trace. In attach, I made a ruleflow sample with two nodes (one ruleflow group and one script node). The nodes are only making a simple System.out.println. When executing it in Statefull session, we have two outputs. When executing it in Stateless session, there is only one output, this one of the RuleFlowGroup. The script node has not been executed as it should be. No exceptions were found in logs. -- 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

15 years, 3 months

6
8
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1860) Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database

by Miroslav Novak (JIRA)

Enhacement - Consumer should be able to read all the messages when another node in cluster lost connection to database ---------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1860 URL: https://issues.jboss.org/browse/JBMESSAGING-1860 Project: JBoss Messaging Issue Type: Enhancement Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA Reporter: Miroslav Novak Assignee: Miroslav Novak There should be made an enhancement in JBM clustering. For now the behaviour is following: Clustered queue is used and Session_Transacted mode is used. 1. cluster of 3 nodes - A - B - C 2. send 500 to each (db status - A:500, B:500, C:500) 3. disconnect B from DB (db unchanged) 4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs 5. read A - 0 messages read (db status A:0, B:500, C:0) 6. connect B to DB (db status A:0, B:417, C:83) 7. read B - 500 messages read (db status A:0, B:0, C:0) In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are still 500 messages left in the db. As an enhancement there should be that client on node C in step 4. will read all the messages from clustered queue. Thanks, Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1861) Enhacement - Producer should be reconnected to another node in cluster when node to which he's sending lost connection to database

by Miroslav Novak (JIRA)

Enhacement - Producer should be reconnected to another node in cluster when node to which he's sending lost connection to database ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1861 URL: https://issues.jboss.org/browse/JBMESSAGING-1861 Project: JBoss Messaging Issue Type: Enhancement Components: JMS Clustering Affects Versions: 1.4.0.SP3.CP12, 1.4.8.GA Reporter: Miroslav Novak Assignee: Miroslav Novak There should be made an enhancement in JBM clustering. For now the behaviour is following: Clustered queue is used and Session_Transacted mode is used. 1. cluster of 3 nodes - A - B - C 2. send 500 to each (db status - A:500, B:500, C:500) 3. disconnect B from DB (db unchanged) 4. read C - 1000 messages read (db status A:0, B:500, C:0) - hangs 5. read A - 0 messages read (db status A:0, B:500, C:0) 6. connect B to DB (db status A:0, B:417, C:83) 7. read B - 500 messages read (db status A:0, B:0, C:0) In step 4. consumer received 1000 from 1500 messages from nodes A and C and there are still 500 messages left in the db. As an enhancement there should be that client on node C in step 4. will read all the messages from clustered queue. Thanks, Mirek -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
6
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 April 2011