July 2011 - jboss-jira - Jboss List Archives

[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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

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

12 years, 7 months

4
18
0 / 0

[JBoss JIRA] Created: (AS7-1369) persistence.xml in EAR/META-INF folder with <jar-file>

by wiktorowski maximilien (JIRA)

persistence.xml in EAR/META-INF folder with <jar-file> ------------------------------------------------------ Key: AS7-1369 URL: https://issues.jboss.org/browse/AS7-1369 Project: Application Server 7 Issue Type: Bug Reporter: wiktorowski maximilien adding persistence.xml in META-INF dir of an ear like this ?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" version="2.0"> <persistence-unit name="mypersistencunit"> ... <jar-file>lib/myjpa.jar</jar-file> result in exception: Caused by: java.lang.RuntimeException: error trying to scan <jar-file>: vfs:/c:/JBoss/jboss-as-7.0.0.Final/bin/content/lib/myjpa.jar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

5
17
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011