August 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1629) Buttons on all alerts in AS7 Administration Console is not responding properly to Enter keystroke (on FF6 + Ubuntu 11.04).

by Burr Sutter (JIRA)

Buttons on all alerts in AS7 Administration Console is not responding properly to Enter keystroke (on FF6 + Ubuntu 11.04). -------------------------------------------------------------------------------------------------------------------------- Key: AS7-1629 URL: https://issues.jboss.org/browse/AS7-1629 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Burr Sutter Assignee: Heiko Braun Priority: Minor Buttons on all alerts in AS7 Administration Console is not responding properly to Enter keystroke (on FF6 + Ubuntu 11.04). >From Twitter: @nsudarshan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2856) Encrypted passwords in the change-set.xml

by Alessandro Lazarotti (JIRA)

Encrypted passwords in the change-set.xml ----------------------------------------- Key: JBRULES-2856 URL: https://issues.jboss.org/browse/JBRULES-2856 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: fedora 12, jdk 1.6, drools 5.1.0 expert Reporter: Alessandro Lazarotti Assignee: Mark Proctor Currently the drools client API access Guvnor by creditials declared as plain-text in change-set.xml or property files. This is a security problem for many companies. Is very important develop a mechanism to obfuscate the password -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JASSIST-144) ProxyObject#setHandler interferes with business methods of the same name

by Steve Ebersole (JIRA)

ProxyObject#setHandler interferes with business methods of the same name ------------------------------------------------------------------------ Key: JASSIST-144 URL: https://issues.jboss.org/browse/JASSIST-144 Project: Javassist Issue Type: Feature Request Affects Versions: 3.12.0.GA Reporter: Steve Ebersole Assignee: Shigeru Chiba Being reported by Hibernate/JPA users -> https://hibernate.onjira.com/browse/HHH-5731 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (AS7-830) using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage

by Bob McWhirter (JIRA)

using JMSQueueService to create and bind queues to new contexts with previously-non-existant-parents causes MockContext/BindingTrap/HornetQ to get confused on context heritage ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-830 URL: https://issues.jboss.org/browse/AS7-830 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Beta3 Reporter: Bob McWhirter Assignee: Jason Greene If I hijack JMSQueueService, and attempt to bind the queue as queue/foo/bar/baz/tacos/someQueue, it may work the first time, but subsequent created queues end up with a duplicated section in the resulting path. Trying to bind to queue/foo/bar/baz/gouda/anotherQueue might result in queue/foo/bar/baz/tacos/gouda/anotherQueue. Seems some stack doesn't get completely popped when HornetQ goes creating parent contexts in order to plant the leaf resource. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
6
0 / 0

[JBoss JIRA] Created: (HIBERNATE-100) All versions of hibernate-tools packages are broken on eclipse-3.4

by solid Iduncare (JIRA)

All versions of hibernate-tools packages are broken on eclipse-3.4 ------------------------------------------------------------------ Key: HIBERNATE-100 URL: http://jira.jboss.com/jira/browse/HIBERNATE-100 Project: Hibernate Issue Type: Bug Environment: Reproducable on Linux, Windows and Mac OSX Reporter: solid Iduncare Assigned To: Steve Ebersole All versions of the Jboss hibernate-tools eclipse plugin fail in various ways on eclipse-3.4 (Ganymede). I have obtained various versions of the plugin via the eclipse update sites (both stable and dev) and all have various problems. I first attempted to download the latest from the stable update link (http://download.jboss.org/jbosstools/updates/stable/) . I selected the hibernate tools package for install only. It installs but is unusable. It seems to have no ill effects otherwise. When you attempt to add a hibernate configuration in the hibernate console, you get an exception similar to the followng: java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117) at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165) at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932) at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012) at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041) at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827) at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340) at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270) at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652) at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106) at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) I googled this error and it brought me to a hibernate jira page hosted by atlasian. That Jira page recommended using the latest hibernate tools plugin from the dev update site(http://download.jboss.org/jbosside/hibernatetools/updates/development/) so I did. Now this is where all hell brakes loose. After installing the latest version from this site and restarting eclipse, the JEE perspective is completely disabled. JSP files open in a regular text editor and all attempts to update eclipse fail with this exception: Cannot complete the request. See the details. Cannot find a solution where both Match[requiredCompatibility: org.eclipse.equinox.p2.iu/org.eclipse.emf.ecore.xml/[2.1.0,2.1.0]] and Match[requiredCompatability: .... In short there is no usable version of hibernate tools for eclipse-3.4. -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (AS7-947) server:reload() exception

by Heiko Braun (JIRA)

server:reload() exception ------------------------- Key: AS7-947 URL: https://issues.jboss.org/browse/AS7-947 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Priority: Critical Fix For: 7.0.0.CR1 Reloading yields an exception: /host=local/server=server-one:reload {noformat} [Host Controller] 12:32:50,188 ERROR [org.jboss.as.host.controller] (pool-1-thread-24) Could not start server Server:server-one: java.lang.IllegalArgumentException: A node is already registered at '(server => server-one)' [Host Controller] at org.jboss.as.controller.registry.NodeSubregistry.registerProxyController(NodeSubregistry.java:89) [jboss-as-controller-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] {noformat} A second operation request results in "broken pipe": {noformat} [Host Controller] 12:33:03,025 ERROR [org.jboss.as.protocol] (ModelControllerClient-thread - 1) Failed to close resource org.jboss.as.protocol.SimpleByteDataOutput@37c398e: java.net.SocketException: Broken pipe {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

8
10
0 / 0

[JBoss JIRA] Created: (JBRULES-2699) OSGi support for Drools Planner

by Geoffrey De Smet (JIRA)

OSGi support for Drools Planner ------------------------------- Key: JBRULES-2699 URL: https://jira.jboss.org/browse/JBRULES-2699 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Optional Fix For: FUTURE Asked on twitter by Wouter Horré. If there's more demand, I'll look into supporting in our builds, until then they'll have to manage it themselves :/ Patches welcome too of course. -- 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

1
1
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] 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2011