February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2342) Multiple Log Directories in one tree

by Jim Tyrrell (Created) (JIRA)

Multiple Log Directories in one tree ------------------------------------ Key: AS7-2342 URL: https://issues.jboss.org/browse/AS7-2342 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell See the attached screen shot, does it make sense to have the log files in each of the server/s directories, along with the log directory in the domain context. When first looking for log files, it was odd to cd to domain, and then cd to log and not see my server directories. For a long time JBoss user what we are doing does not probably hurt that much, but for a new user, having multiple log directories is a little odd. Does it make sense to have just one log directory. In this case: domain/log/server-one domain/log/server-two ... instead of domina/log domain/servers/server-one/log domain/servers/server-two/log ... -- 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

14 years, 3 months

6
6
0 / 0

[JBoss JIRA] (AS7-3952) ClusteredBeanDeploymentTestCase is not executed

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3952: ----------------------------------- Summary: ClusteredBeanDeploymentTestCase is not executed Key: AS7-3952 URL: https://issues.jboss.org/browse/AS7-3952 Project: Application Server 7 Issue Type: Bug Components: Clustering, Test Suite Reporter: Radoslav Husar Assignee: Radoslav Husar Priority: Minor Fix For: 7.1.1.Final because of this https://github.com/jbossas/jboss-as/commit/53db4a1ce28f4979f976b852402e40... the ClusteredBeanDeploymentTestCase is not started -- 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

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3784) Make the "default-stack" attribute a child of the groups subsystem configuration

by Heiko Braun (JIRA)

Heiko Braun created AS7-3784: -------------------------------- Summary: Make the "default-stack" attribute a child of the groups subsystem configuration Key: AS7-3784 URL: https://issues.jboss.org/browse/AS7-3784 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.1.Final {noformat} <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="udp"/> {noformat} -- 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

14 years, 3 months

3
4
0 / 0

[JBoss JIRA] (AS7-3883) Remove security/auditing/form-auth.war

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3883: ----------------------------------- Summary: Remove security/auditing/form-auth.war Key: AS7-3883 URL: https://issues.jboss.org/browse/AS7-3883 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.0.Final Reporter: Stuart Douglas Assignee: Jan Lanik Priority: Critical Fix For: 7.1.1.Final Deployments are build using shrinkwrap. They should not just be be pre-built and then dumped into the resources dir as a binary blob. -- 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

14 years, 3 months

2
2
0 / 0

[JBoss JIRA] (AS7-3648) WARNING from CommandAwareRpcDispatcher: Channel Muxer already has a default up handler installed but now it is being overridden

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3648: ----------------------------------- Summary: WARNING from CommandAwareRpcDispatcher: Channel Muxer already has a default up handler installed but now it is being overridden Key: AS7-3648 URL: https://issues.jboss.org/browse/AS7-3648 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Affects Versions: 7.1.0.CR1, 7.1.0.Final Reporter: Radoslav Husar Assignee: Paul Ferraro Priority: Minor Fix For: 7.1.1.Final Full log: {noformat} WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (pool-22-thread-3) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler@36cdb4f9) but now it is being overridden {noformat} As Paul explains it: Our ChannelService sets a default up handler for a channel which does TCCL swapping. If infinispan uses the channel, it sets its own up handler (overriding ours) and writes that warning to the log if one is already defined. -- 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

14 years, 3 months

2
1
0 / 0

[JBoss JIRA] (AS7-3889) Unable to pass smoke tests part of testsuite when specify -Dnode0=<something>

by Pavel Janousek (JIRA)

Pavel Janousek created AS7-3889: ----------------------------------- Summary: Unable to pass smoke tests part of testsuite when specify -Dnode0=<something> Key: AS7-3889 URL: https://issues.jboss.org/browse/AS7-3889 Project: Application Server 7 Issue Type: Bug Components: Test Suite Affects Versions: 7.1.1.Final Reporter: Pavel Janousek Assignee: Andrew Rubinger I'm unable to pass smoke tests part of testsuite. I hope you get the same result when try: {code} ./build.sh clean install [pass] ifconfig lo:1 127.0.0.2 [pass] ./integration-tests.sh install -Dnode0=127.0.0.2 {code} I got: {code} Tests in error: testMessagingClient(org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase): java.net.ConnectException: JBAS012144: Could not connect to remote://pjanouse.brq.redhat.com:9999. The connection timed out testMessagingClient(org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase): Cannot connect to server(s). Tried with all available servers. {code} Also in IPv6 mode like: {code} ./integration-tests.sh install -Dnode0=::1 -Dipv6 {code} I got error, but it differs from above: {code} Tests in error: org.jboss.as.test.smoke.embedded.demos.jms.JmsTestCase: destination address may not be null org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase: destination address may not be null org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase: destination address may not be null org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase: destination address may not be null {code} When I specify -Dnode0=127.0.0.1 as binding address, everything works fine... PS: This state is *after* merging O. Zizka's TS-refactor branch (commit d0f1f3cef0ed90d4b655e5aec15be7b00a373f5c). -- 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

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3667) Upgrade to JSF 2.1.6

by Ove Ranheim (JIRA)

Ove Ranheim created AS7-3667: -------------------------------- Summary: Upgrade to JSF 2.1.6 Key: AS7-3667 URL: https://issues.jboss.org/browse/AS7-3667 Project: Application Server 7 Issue Type: Library Upgrade Components: Build System, JSF Affects Versions: 7.1.0.CR1b Reporter: Ove Ranheim Assignee: Paul Gier Fix For: 7.1.0.Final Upgrade JSF from 2.1.5 to 2.1.6. Release notes: http://java.net/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10985 -- 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

14 years, 3 months

5
10
0 / 0

[JBoss JIRA] Created: (JBAS-4526) JBossMQ UIL2 Read/Write Tasks should not be doing initialization

by Adrian Brock (JIRA)

JBossMQ UIL2 Read/Write Tasks should not be doing initialization ---------------------------------------------------------------- Key: JBAS-4526 URL: http://jira.jboss.com/jira/browse/JBAS-4526 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 Read/Write tasks both do their stream initialization when each thread starts. This code needs changing such that the streams are allocated before started the threads. Only if all resources can be succesfully allocated should we start the threads. -- 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

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] (AS7-3898) Improve the processing time of a request with a large number of parameters on JBossAS7.1.

by Toshio Oya (JIRA)

Toshio Oya created AS7-3898: ------------------------------- Summary: Improve the processing time of a request with a large number of parameters on JBossAS7.1. Key: AS7-3898 URL: https://issues.jboss.org/browse/AS7-3898 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.0.Final Reporter: Toshio Oya Assignee: Remy Maucherat Attachments: modified-7.1.0.Final.zip JBAS-9472 which is reported as an enhancement request for JBossAS 5.1.0.GA, is reproduced on JBossAS 7.1.0.Final. So, we have created a patch for JBossAS 7.1.0.Final. We want to incorporate this patch in JBoss AS 7.x. Please see JBAS-9472. -- 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

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] (AS7-3550) CLI: Add rollout-plan argument to high level commands

by Dominik Pospisil (JIRA)

Dominik Pospisil created AS7-3550: ------------------------------------- Summary: CLI: Add rollout-plan argument to high level commands Key: AS7-3550 URL: https://issues.jboss.org/browse/AS7-3550 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.0.Final Reporter: Dominik Pospisil Assignee: Alexey Loubyansky It seems that there is no support in high-level CLI commands (deploy, jms-queue, jms-topic, data-source) for specifying rolout-plan. -- 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

14 years, 3 months

2
2
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 February 2012