January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2735) Add a non-interactive form of the add-user utility

by Darran Lofthouse (Created) (JIRA)

Add a non-interactive form of the add-user utility -------------------------------------------------- Key: AS7-2735 URL: https://issues.jboss.org/browse/AS7-2735 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 Allow the add-user utility to be used non-interactively i.e. the details are passed in on the command line and no further confirmation is sought from the user. If two parameters are received the first will be the username and the second the password. If three parameters are received the first will be the username, the second the password and the third the realm. -- 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, 1 month

4
4
0 / 0

[JBoss JIRA] (AS7-3110) Enhance validation message when multiple persistence units are found

by Markus Dahm (Created) (JIRA)

Enhance validation message when multiple persistence units are found -------------------------------------------------------------------- Key: AS7-3110 URL: https://issues.jboss.org/browse/AS7-3110 Project: Application Server 7 Issue Type: Enhancement Reporter: Markus Dahm Priority: Minor The current message is Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 9 persistence unit definitions in application deployment "test.ear". Either change the application to have only one persistence unit definition or specify the unitName for each reference to a persistence unit. Yet what is always helpful in search of such validation errors is the context. In that case the offending class name would suffice, you should have this information at hands since you're scanning the classes, right? Given that information I'd have found the problem immediately. -- 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, 1 month

6
14
0 / 0

[JBoss JIRA] Created: (JBBOOT-138) Failure To Start JBoss on Java 7

by Jimmy Wilson (JIRA)

Failure To Start JBoss on Java 7 -------------------------------- Key: JBBOOT-138 URL: https://issues.jboss.org/browse/JBBOOT-138 Project: JBoss Bootstrap Issue Type: Bug Components: legacy Reporter: Jimmy Wilson Assignee: Andrew Rubinger JBoss fails to boot on Java 7: Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190) at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173) at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143) at org.jboss.Main.boot(Main.java:218) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
9
0 / 0

[JBoss JIRA] (AS7-3401) Provide AS7 schema for jboss-web.xml and jboss-app.xml

by Stephen Coy (JIRA)

Stephen Coy created AS7-3401: -------------------------------- Summary: Provide AS7 schema for jboss-web.xml and jboss-app.xml Key: AS7-3401 URL: https://issues.jboss.org/browse/AS7-3401 Project: Application Server 7 Issue Type: Feature Request Components: EE, Web Reporter: Stephen Coy Assignee: David Lloyd At the moment we only have JBossAS 6.x schema for these files. -- 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, 1 month

7
7
0 / 0

[JBoss JIRA] (AS7-2991) Gzip compression support

by Humberto Ferreira da Luz Jr. (Created) (JIRA)

Gzip compression support ------------------------ Key: AS7-2991 URL: https://issues.jboss.org/browse/AS7-2991 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.0.2.Final Environment: Any. Reporter: Humberto Ferreira da Luz Jr. Since JBoss AS 7 there's no support for gzip compression. I think that's an important feature which reduces substantially the page size. -- 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, 1 month

10
25
0 / 0

[JBoss JIRA] Created: (JGRP-989) TCPPING: add new member addresses to initial_hosts dynamically

by Bela Ban (JIRA)

TCPPING: add new member addresses to initial_hosts dynamically -------------------------------------------------------------- Key: JGRP-989 URL: https://jira.jboss.org/jira/browse/JGRP-989 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When we have A,B and C listed in initial_hosts but later D and E join, and we have a partition {A,B,C} and {D,E}, when the partition heals later, we have no way of merging the 2 subgroups back into 1 because initial_hosts doesn't contain D or E. SOLUTION: dynamically add members not in initial_hosts to initial_hosts on view changes. Keep the number of dynamically added members bounded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBLOGGING-6) DatasourceAppender

by Luca Stancapiano (JIRA)

DatasourceAppender ------------------ Key: JBLOGGING-6 URL: https://jira.jboss.org/jira/browse/JBLOGGING-6 Project: JBoss Logging Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jboss-logging-log4j Affects Versions: 1.0.0.GA-slf4j-jboss-logging, 2.0.6.GA-spi Reporter: Luca Stancapiano Assignee: Dimitris Andreadis Fix For: 2.0.6.GA-spi, 1.0.0.GA-slf4j-jboss-logging hi.... what do you think about a DatasourceAppender? This is very simple. It overrides getConnection and closeConnection methods of org.apache.log4j.jdbc.JDBCAppender class and it is configurable by a *-log4j.xml file. Here there is an example of xml file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd"> <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false"> <appender name="DATABASE" class="org.jboss.logging.appender.DatasourceAppender"> <param name="Threshold" value="INFO"/> <param name="datasource" value="java:/PortalDS"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value= "INSERT INTO JBP_LOGGING_SAMPLES_USERS (log_date, log_type, log_user, operation) VALUES ( '%d{yyyy-MM-dd HH:mm:ss.SSS}','%p', '%C;%L', '%C;%L')"/> </layout> </appender> <category name="org.jboss.portal.core.identity.UsersActivityStatsServiceImpl"> <appender-ref ref="DATABASE"/> </category> </log4j:configuration> it is the same configuration for JDBCAppender but there is a 'datasource' parameter so you can specify the datasource location. Below there is the whole class: /* * JBoss, Home of Professional Open Source * Copyright 2005, JBoss Inc., and individual contributors as indicated * by the @authors tag. See the copyright.txt in the distribution for a * full listing of individual contributors. * * This is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as * published by the Free Software Foundation; either version 2.1 of * the License, or (at your option) any later version. * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA * 02110-1301 USA, or see the FSF site: http://www.fsf.org. */ package org.jboss.logging.appender; import java.sql.Connection; import java.sql.SQLException; import javax.naming.InitialContext; import javax.naming.NamingException; import javax.sql.DataSource; /** * An extension of the default Log4j JDBCAppender which will use a datasource to * handle datas into database. * * @version <tt>$Revision: 1958 $</tt> * @author <a href="mailto:jedim@vige.it">Luca Stancapiano</a> */ public class DatasourceAppender extends org.apache.log4j.jdbc.JDBCAppender { /** * URL of the DB for default connection handling */ protected String datasource = "java:/DefaultDS"; protected DataSource ds; public void setDatasource(final String datasource) { this.datasource = datasource; } /** * I override this method to get a connection from datasource. */ protected Connection getConnection() throws SQLException { if (connection == null || connection.isClosed()) { if (ds == null) try { InitialContext ic = new InitialContext(); ds = (DataSource) ic.lookup(datasource); } catch (NamingException e) { e.printStackTrace(); } connection = ds.getConnection(); } return connection; } protected void closeConnection(Connection con) { try { connection.close(); } catch (SQLException ex) { ex.printStackTrace(); } } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

4
14
0 / 0

[JBoss JIRA] Created: (JBLOGGING-55) NPE in FileAppender$Helper

by Ondrej Zizka (JIRA)

NPE in FileAppender$Helper -------------------------- Key: JBLOGGING-55 URL: https://issues.jboss.org/browse/JBLOGGING-55 Project: JBoss Logging Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ondrej Zizka Assignee: David Lloyd When you set the file="..." to just a file, i.e. file="foobar.log", then you get a NPE at line if (!dir.exists()) { probably because dir = new File(filename.trim()).getParentFile(); returns null. I'd expect the appender to write to a file in new File( new File(System.getProperty("user.dir")), filename.trim() ). package org.jboss.logging.appender; import java.io.File; import java.net.MalformedURLException; import java.net.URL; import org.apache.log4j.helpers.LogLog; public class FileAppender$Helper { public static void makePath(String filename) { File dir; try { URL url = new URL(filename.trim()); dir = new File(url.getFile()).getParentFile(); } catch (MalformedURLException e) { dir = new File(filename.trim()).getParentFile(); } if (!dir.exists()) { boolean success = dir.mkdirs(); if (!success) LogLog.error("Failed to create directory structure: " + dir); } } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3076) Support declarative configuration of event listeners (process, agenda, working memory)

by Vinod Kiran Paidimarry (JIRA)

Support declarative configuration of event listeners (process, agenda, working memory) --------------------------------------------------------------------------------------- Key: JBRULES-3076 URL: https://issues.jboss.org/browse/JBRULES-3076 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-spring Reporter: Vinod Kiran Paidimarry Assignee: Mark Proctor Support declarative configuration of event listeners (process, agenda, working memory) using Spring XML -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1826) Removing a reference and deleting a message in DB should be wrapped in a single transaction in JDBCPersistenceManager

by Yong Hao Gao (JIRA)

Removing a reference and deleting a message in DB should be wrapped in a single transaction in JDBCPersistenceManager ---------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1826 URL: https://jira.jboss.org/browse/JBMESSAGING-1826 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.4.7.GA, 1.4.0.SP3.CP10 Reporter: Yong Hao Gao Assignee: Yong Hao Gao Fix For: 1.4.0.SP3.CP11, 1.4.8.GA In JDBCPersistenceManager, when a message is delivered and completed, the message is removed from DB. It includes two deletes in the DB - the reference in JBM_MSG_REF and the message in JBM_MSG. The two deletes are currently done in two separate local transactions as in removeReference() method: ... new RemoveReferenceRunner().executeWithRetry(); deleteMessage(ref.getMessage().getMessageID()); ... If a server crashes between the two operations, it will leave the tables in an inconsistent state, i.e. ref removed but the message still there. This may result in message stuck, as in this case: 1. A server is crashing when a client_ack comes in, the clienk_ack will cause the message to be cleared from the server. If the client_ack processing goes as far as that the removing of reference succeeds but failed to delete the message due to the crashing, the message is left in JBM_MSG table but the corresponding entry in JBM_MSG_REF is gone. 2. Eventually the jms client will get ack failure exception. It then expects the messages to be re-delivered after server start-up. But that will never happen. When the server starts up it loads references in JBM_MSG_REF for delivery, but this message's ref is gone. -- 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

14 years, 1 month

4
18
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 January 2012