October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2265) multi-line log output makes munging logs difficult

by Rich Lucente (Created) (JIRA)

multi-line log output makes munging logs difficult -------------------------------------------------- Key: AS7-2265 URL: https://issues.jboss.org/browse/AS7-2265 Project: Application Server 7 Issue Type: Enhancement Components: EJB Affects Versions: 7.1.0.Alpha1 Environment: jboss-as-7.1.0.Alpha2-SNAPSHOT, java-1.6.0-openjdk, Fedora 14 Reporter: Rich Lucente Assignee: Carlo de Wolf Priority: Minor Fix For: Open To Community Multi-line log entry, as shown below, complicates use of scripts to munge the log. 15:50:30,986 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named MemberRegistration in deployment unit subdeployment "multi-ejb-0.0.1-SNAPSHOT.jar" of deployment "multi-ear.ear" are as follows: java:global/multi-ear/multi-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.jboss.as.quickstarts.example.qs.controller.MemberRegistration java:app/multi-ejb-0.0.1-SNAPSHOT/MemberRegistration!org.jboss.as.quickstarts.example.qs.controller.MemberRegistration java:module/MemberRegistration!org.jboss.as.quickstarts.example.qs.controller.MemberRegistration java:global/multi-ear/multi-ejb-0.0.1-SNAPSHOT/MemberRegistration java:app/multi-ejb-0.0.1-SNAPSHOT/MemberRegistration java:module/MemberRegistration 15:50:30,991 INFO [org.jboss.weld] (MSC service thread 1-5) Starting Services for CDI deployment: multi-ear.ear -- 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

13 years

6
6
0 / 0

[JBoss JIRA] Created: (AS7-1422) Add a generic query facility

by Heiko Rupp (JIRA)

Add a generic query facility ---------------------------- Key: AS7-1422 URL: https://issues.jboss.org/browse/AS7-1422 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry To find out, which e.g. jdbc drivers are deployed on a server group, I have to visit each managed server and query it. This is cumbersome - first the server group should have the same driver for all servers, so asking the server group should be enough - as the server group does not even know its connected managed servers (there is no :list-servers) operation, I need to potentially loop over the whole domain including tons of remote HC in order to query for e.g. the jdbc drivers or other stuff There should be a mechanism to fire queries at which then get relayed to the HCs and the answers combined and returned. Still I don't get why if a server-group is meant to contain an identical configuration for all its managed servers (besides VM params, ports and IPs) it does not just have "proxy methods" like :installed-drivers-list or :server-list etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1416) Too many resources/properties in the domain api are read-only

by Heiko Rupp (JIRA)

Too many resources/properties in the domain api are read-only ------------------------------------------------------------- Key: AS7-1416 URL: https://issues.jboss.org/browse/AS7-1416 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Heiko Rupp Assignee: Brian Stansberry >From http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003223.html: just looked at the configuration side of the API again and most of the attibutes in there are read-only. So I can not e.g. change the max post size for the http connector (*) via API - other than dropping the http connector completely and re-creating it, which is nothing people will do (especially when there is no ":clone" operation that fills in the existing properties when not passed explicitly). People will in this case just start hacking on standalone.xml and other files, which completely renders the api void. Do we really want that? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
1
0 / 0

[JBoss JIRA] Created: (AS7-1198) Add a Deployment Exception Transformer for the Arquillian container

by Jason Porter (JIRA)

Add a Deployment Exception Transformer for the Arquillian container ------------------------------------------------------------------- Key: AS7-1198 URL: https://issues.jboss.org/browse/AS7-1198 Project: Application Server 7 Issue Type: Feature Request Reporter: Jason Porter A discussion on IRC: http://echelog.matzon.dk/logs/browse/jbosstesting/1309903200 We're not reporting back to ARQ users the actual error during deployment, just whatever the app server gives us. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1218) Ability to specify a delay between URL round-robin attempts in HA datasource

by Daniel Marchese (JIRA)

Ability to specify a delay between URL round-robin attempts in HA datasource ---------------------------------------------------------------------------- Key: AS7-1218 URL: https://issues.jboss.org/browse/AS7-1218 Project: Application Server 7 Issue Type: Feature Request Components: JCA Affects Versions: 7.0.0.CR1 Reporter: Daniel Marchese We have a configuration with Oracle RAC One Node (1 active database, 1 standby database) and we are testing HA possibilities. In one test, if we try to obtain a connection during the starting of the standby database after the active database crash, we get an ORA-12514 error because the standby instance is not ready to respond. Besides the fact that Oracle should not return an error but wait for the standby database to be ready to respond, it would be interesting if it was possible to specify a delay between URL round-roubin attempts in the HA datasource (ex: url-retry-wait-millis). This way, it would be possible to ask JBoss to wait before it tries the next URL in the list, giving the standby database the time to start. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1109) can't specifiy correct JNDI name when creating datasource in console

by Darrin Mison (JIRA)

can't specifiy correct JNDI name when creating datasource in console -------------------------------------------------------------------- Key: AS7-1109 URL: https://issues.jboss.org/browse/AS7-1109 Project: Application Server 7 Issue Type: Bug Environment: AS7 built from git repo master, updated Morning of June 24th 2011 Reporter: Darrin Mison I have a sample app with a persistence.xml with <jta-data-source>java:/todos-ds</jta-data-source> The *-ds.xml I was using for AS6 has <jndi-name>todos-ds</jndi-name> This works in AS6. But when I try to create a datasource in the AS7 managment console I can't create it with the name java:/todos-ds. I just get a red exclamation mark next to the JNDI name box until I remove the java:/ and then it lets me create the datasource but the app doesn't work of course. If I open up the standalone.xml I can edit the jndi-name and add the prefix, then the app works as expected. (I haven't looked at using the CLI to create a DS yet) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1036) Arquillian Managed Container does not honor configured ports

by Karel Piwko (JIRA)

Arquillian Managed Container does not honor configured ports ------------------------------------------------------------ Key: AS7-1036 URL: https://issues.jboss.org/browse/AS7-1036 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Karel Piwko When starting a managed container, following configuration is not used by Arquillian: {code} <container qualifier="container" default="true"> <configuration> <property name="jbossHome">target/jbossas-2</property> <property name="managementPort">19999</property> <property name="jmxPort">1190</property> <property name="httpPort">8180</property> <property name="startupTimeoutInSeconds">180</property> </configuration>  <protocol type="jmx-as7"> <configuration> <property name="executionType">REMOTE</property> </configuration> </protocol> </container> {code} The standalone container is always started on default ports, e.g. 9999, 1099, 8180. The ports are defined in standalone.xml and it seems difficult to change them without touching the file. See http://community.jboss.org/thread/168140 for related question. This makes customization of the test runs with managed containers difficult and for clusters even more difficult. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1011) JBoss AS lifecycle controlling tests

by Karel Piwko (JIRA)

JBoss AS lifecycle controlling tests ------------------------------------ Key: AS7-1011 URL: https://issues.jboss.org/browse/AS7-1011 Project: Application Server 7 Issue Type: Task Components: Test Suite Affects Versions: 7.0.0.Beta3 Reporter: Karel Piwko Assignee: Karel Piwko Create a test suite that uses Arquillian to control JBoss AS 7 lifecycle in a more precise way, that is: * DomainClient specific controller * Asynchronous start, stop * Manual start after modifying a domain configuration * Monitoring of container and deployment status * Forced / programmable kill (cleanup to be investigated here though) Some of the features would require modifications of Arquillian. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1018) Allow TM to run in local only recover mode

by Scott Stark (JIRA)

Allow TM to run in local only recover mode ------------------------------------------ Key: AS7-1018 URL: https://issues.jboss.org/browse/AS7-1018 Project: Application Server 7 Issue Type: Feature Request Components: Transactions Reporter: Scott Stark Assignee: Scott Stark When running under constrained environments (either resources, and or selinux), it would be good if the transaction manager could run in a local only recover mode that did not require any network interfaces to be brought up. I have an example prototype of this change in my https://github.com/starksm64/jboss-as/tree/tmwork branch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
3
0 / 0

[JBoss JIRA] Created: (AS7-696) Console in standalone mode: deploy / undeploy / enable / disable

by Stan Silvert (JIRA)

Console in standalone mode: deploy / undeploy / enable / disable ---------------------------------------------------------------- Key: AS7-696 URL: https://issues.jboss.org/browse/AS7-696 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.0.Beta3 Reporter: Stan Silvert Assignee: Stan Silvert -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
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