October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2364) CLI Response Verbosity

by Rich Sharples (Created) (JIRA)

CLI Response Verbosity ---------------------- Key: AS7-2364 URL: https://issues.jboss.org/browse/AS7-2364 Project: Application Server 7 Issue Type: Clarification Components: CLI Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Rich Sharples Assignee: Alexey Loubyansky Fix For: 7.1.0.Beta1 The output of the CLI easily interpreted by a machine. Not so easy for a human. For example, typical error : { "outcome" => "failed", "failure-description" => "No handler for read-operation-namess at address [ (\"server-group\" => \"main-server-group\"), (\"jvm\" => \"default\") ]", "rolled-back" => true } could be translated to : ERROR : No handler for "read-operation-namess" command at address server-group=main-server-group, jvm=default I suggest two modes of operation - human readable responses and verbose (machine readable) responses. -- 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

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-9045) Support for EJB2 views

by David Lloyd (JIRA)

Support for EJB2 views ---------------------- Key: JBAS-9045 URL: https://issues.jboss.org/browse/JBAS-9045 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 Support for @LocalHome, @RemoteHome etc as well as EJB2-style deployment descriptors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

9
12
0 / 0

[JBoss JIRA] (JBMESSAGING-1902) JBMessaging cluster stops working after a node gets suspended (kill -STOP) and unsuspended (kill -CONT) after few minutes

by Tom Ross (Created) (JIRA)

JBMessaging cluster stops working after a node gets suspended (kill -STOP) and unsuspended (kill -CONT) after few minutes ------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1902 URL: https://issues.jboss.org/browse/JBMESSAGING-1902 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Clustering Affects Versions: 1.4.8.SP3 Environment: JBoss EAP 5.1.0 Reporter: Tom Ross Assignee: Yong Hao Gao Priority: Blocker This is a very simple cases where two node JBoss Messaging cluster stops working after one node gets suspended (kill -STOP) for few minutes. It would appear that when the node wakes up from the suspension it misses jgroups notifications and carries on as if nothing ever happened. Meantime while the node was suspended the remaining node performed failover and deleted the suspended node from the jbm_cluster table. How to reproduce the problem. Create a two node cluster using all profile. start node 1 start node 2 after both nodes are running find out pid of the JVM hosting node 2 and pid of the shell process ps -fu ${user-name} | grep java kill -STOP pid-jvm kill -STOP shell running jvm wait 5 minutes kill -CONT shell running jvm kill -CONT pid-jvm Observe that node 1 has noticed that node 2 is missing and performed failover node 2 has been remved from JBM_CLUSTER table. JGroups is functioning normally JBM cluster is not working node 2 is not part of the cluster any longer. -- 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

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] (AS7-2257) Statistics not kept in Virtual Machine view of AS7 Console

by Chuck Mosher (Created) (JIRA)

Statistics not kept in Virtual Machine view of AS7 Console ---------------------------------------------------------- Key: AS7-2257 URL: https://issues.jboss.org/browse/AS7-2257 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Alpha1 Environment: Thinkpad T510 w/ 4cores, 8Gb, running CSB Reporter: Chuck Mosher Assignee: Heiko Braun Priority: Minor In the Console Virtual Machine view, the statistics go away whenever you move away from the window; you have to keep it up if you want to gather any info over time. Might be better to have a sliding window, or even better be able to specify the window. -- 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

12 years, 11 months

5
4
0 / 0

[JBoss JIRA] (AS7-2326) Build fails on Windows in cmp module due to org.codehaus.mojo:javacc-maven-plugin:2.3-jboss-1

by Marko Strukelj (Created) (JIRA)

Build fails on Windows in cmp module due to org.codehaus.mojo:javacc-maven-plugin:2.3-jboss-1 --------------------------------------------------------------------------------------------- Key: AS7-2326 URL: https://issues.jboss.org/browse/AS7-2326 Project: Application Server 7 Issue Type: Bug Components: Build System Environment: JBoss AS 7.1.0.Alpha2-SNAPSHOT, Windows 7 Reporter: Marko Strukelj Assignee: Paul Gier Build of current master fails on Windows in cmp module with: [ERROR] Failed to execute goal org.codehaus.mojo:javacc-maven-plugin:2.3-jboss-1:jjtree (jjtree-jbossql) on project jboss-as-cmp: Execution jjtree-jbossql of goal org.codehaus.mojo:javacc-maven-plugin:2.3-jboss-1:jjtree failed: basedir C:\development\git-root\jboss-as7\cmp\C:\development\git-root\jboss-as7\cmp\src\main\jjtree does not exist -> [Help 1] Looks like a bug (or misconfiguration) in org.codehaus.mojo:javacc-maven-plugin:2.3-jboss-1 - wrong source path generation. AS 7.1.0.Alpha1 builds 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

12 years, 11 months

4
5
0 / 0

[JBoss JIRA] (AS7-2312) Console: buttons in dialogs looks different

by Michal Vanco (Created) (JIRA)

Console: buttons in dialogs looks different ------------------------------------------- Key: AS7-2312 URL: https://issues.jboss.org/browse/AS7-2312 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Michal Vanco Assignee: Heiko Braun Attachments: console-dialog-buttons.png See screenshot. Buttons in dialog: OK is a button, Cancel is a link. This should be unified -- 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

12 years, 11 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1458) CDI Injections do not work in EAR deployments

by Scott Kroll (JIRA)

CDI Injections do not work in EAR deployments --------------------------------------------- Key: AS7-1458 URL: https://issues.jboss.org/browse/AS7-1458 Project: Application Server 7 Issue Type: Bug Components: CDI / Weld Affects Versions: 7.0.0.Final Reporter: Scott Kroll Assignee: Stuart Douglas A project with CDI jars in an EAR lib are not being injected into EJBs. However, the exact same project deployed as a standalone WAR, with everything in WEB-INF/lib works properly. In the EAR deployment, the EJB's method that calls in the injected bean throws a NullPointerException. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
12
0 / 0

[JBoss JIRA] (AS7-2316) Autocomplete does not work in some locations

by Kevin Barfield (Created) (JIRA)

Autocomplete does not work in some locations -------------------------------------------- Key: AS7-2316 URL: https://issues.jboss.org/browse/AS7-2316 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Kevin Barfield Assignee: Alexey Loubyansky The autocomplete works in some nodes but not others. For example, it works in the root node, but not when I cd to host. The operations like :read-resource seem to still work here. -- 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

12 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-688) Re-enable repository browsing on repo.jboss.org/nexus

by Paul Gier (JIRA)

Re-enable repository browsing on repo.jboss.org/nexus ----------------------------------------------------- Key: JBBUILD-688 URL: https://issues.jboss.org/browse/JBBUILD-688 Project: JBoss Build System Issue Type: Task Components: Artifact Repositories Reporter: Paul Gier Fix For: Build Support 2011 Repository browsing in Nexus was temporarily disabled due to the large number of requests (possibly repo scraping) that were affecting server stability. These should eventually be re-enabled. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-2206) Distributable apps fail with ClassNotFoundException when marshalling infinispan bits across jgroups

by Bob McWhirter (Created) (JIRA)

Distributable apps fail with ClassNotFoundException when marshalling infinispan bits across jgroups --------------------------------------------------------------------------------------------------- Key: AS7-2206 URL: https://issues.jboss.org/browse/AS7-2206 Project: Application Server 7 Issue Type: Bug Reporter: Bob McWhirter Attachments: node-info.war, output.log When running a 2-cluster in domain mode, deploying a simple distributable app causes class-not-found exceptions in the clustering bits. -- 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

12 years, 11 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011