October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-558) Add findbugs and other maven reporting related stuff to the jboss repository

by Paul Gier (JIRA)

Add findbugs and other maven reporting related stuff to the jboss repository ---------------------------------------------------------------------------- Key: JBBUILD-558 URL: https://jira.jboss.org/jira/browse/JBBUILD-558 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Fix For: Maven Build - Maint 2009 It was requested on the jboss-dev list that the findbugs plugin be added to the jboss maven repository. Other common reporting tools should also be added. -- 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

16 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-902) GossipRouter: raise SUSPECT event when GR detects (abnormal) loss of a connection from client

by Vladimir Blagojevic (JIRA)

GossipRouter: raise SUSPECT event when GR detects (abnormal) loss of a connection from client --------------------------------------------------------------------------------------------- Key: JGRP-902 URL: https://jira.jboss.org/jira/browse/JGRP-902 Project: JGroups Issue Type: Feature Request Affects Versions: 2.7, 2.6 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 2.8 Currently we only support FD-heartbeat based failure detection algorithm for Gossip Router configurations. While this works ok we do not have the same efficiency of failure detection that comes with FD/FD_SOCK combo used in default UDP/TCP configurations. We can bridge that gap by introducing FD_SOCK kind of functionality that is built in GR. -- 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

16 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-784) local_addr is null when reconnecting.

by Robert Newson (JIRA)

local_addr is null when reconnecting. ------------------------------------- Key: JGRP-784 URL: http://jira.jboss.com/jira/browse/JGRP-784 Project: JGroups Issue Type: Bug Affects Versions: 2.6.2 Reporter: Robert Newson Assigned To: Bela Ban After shunning, a channel never manages to reconnect (with AUTO_RECONNECT) successfully, reporting this endlessly; org.jgroups.ChannelException: local_addr is null at org.jgroups.JChannel.startStack(JChannel.java:1556) at org.jgroups.JChannel.connect(JChannel.java:364) at org.jgroups.JChannel$CloserThread.run(JChannel.java:1908) 2008-06-10 12:04:31,784 FATAL [CloserThread] jgroups.JChannel (JChannel.java:1555) - local_addr is null; cannot connect 2008-06-10 12:04:31,784 ERROR [CloserThread] jgroups.JChannel$CloserThread (JChannel.java:1912) - failure reconnecting to c hannel, retrying -- 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

16 years, 10 months

5
8
0 / 0

[JBoss JIRA] Commented: (JBAS-7100) Exploding vfsmemory:// contents is empty for web deployments

by Dimitris Andreadis (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7100?page=com.atlassian.jira.plug... ] Dimitris Andreadis commented on JBAS-7100: ------------------------------------------ Andrew, are you going to revert it? > Exploding vfsmemory:// contents is empty for web deployments > ------------------------------------------------------------ > > Key: JBAS-7100 > URL: https://jira.jboss.org/jira/browse/JBAS-7100 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Andrew Lee Rubinger > Assignee: Andrew Lee Rubinger > Fix For: JBossAS-5.2.0.Beta1, JBossAS-6.0.0.Alpha1 > > > The following patch addresses this: > [alrubinger@localhost Branch_5_x]$ svn di server/ > When using an in-memory archive backed by VFS, we're using an "unjar"; this leaves out any RAM-backed resources. Instead explode the contents, regardless of what's behind the virtual abstraction: > Index: server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java > =================================================================== > --- server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (revision 91204) > +++ server/src/main/org/jboss/web/deployers/AbstractWarDeployer.java (working copy) > -357,7 +357,7 @@ > > VFSDeploymentUnit vfsUnit = (VFSDeploymentUnit)unit; > VirtualFile root = vfsUnit.getRoot(); > - VirtualFile unjared = VFSUtils.unjar(root); > + VirtualFile unjared = VFSUtils.explode(root); > // file was not unjared yet > if (root != unjared) > { > This was exposed by prototyping in EMB-32. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-184) JBoss Common 2.2.16.GA

by Jesper Pedersen (JIRA)

JBoss Common 2.2.16.GA ---------------------- Key: JBJCA-184 URL: https://jira.jboss.org/jira/browse/JBJCA-184 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha5 -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-183) Use StAX for XML parsing

by Jesper Pedersen (JIRA)

Use StAX for XML parsing ------------------------ Key: JBJCA-183 URL: https://jira.jboss.org/jira/browse/JBJCA-183 Project: JBoss JCA Issue Type: Task Components: Fungal Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha5 The current setup with JAXB/XJC uses bootstrap.xml: 385 ms naming.xml: 71 ms transaction.xml: 23 ms jca.xml: 58 ms for parsing. See if it can be improved with StAX. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6640) Undeploying and deploying the same WAR in short time fails.

by Ondrej Žižka (JIRA)

Undeploying and deploying the same WAR in short time fails. ----------------------------------------------------------- Key: JBAS-6640 URL: https://jira.jboss.org/jira/browse/JBAS-6640 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-5.1.0.CR1 Environment: AS version: 5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200903190511) Reporter: Ondrej Žižka Assignee: Ales Justin Undeploying and deploying the same WAR in short time fails with a message: ---------------------------------------------------------------------------------------------------------------- Failed to create Resource hellothere.war - cause: java.lang.RuntimeException:org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS MISSING DEPLOYERS: Name vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/ DEPLOYMENTS IN ERROR: Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/ayw6m-gfnbbm-fsgkx4z8-1-fsguzifz-fnl/hellothere.war/ deployment failed -> org.jboss.deployers.client.spi.IncompleteDeploymentException:Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): *** DEPLOYMENTS MISSING DEPLOYERS: Name vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/jbas5-admin-console.war/ DEPLOYMENTS IN ERROR: Deployment "vfszip:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/deploy/hellothere.war/" is in error due to the following reason(s): org.jboss.deployers.spi.DeploymentException: URL file:/home/brq/ozizka/JoprEmbedded/jboss-as-5.x/build/output/jboss-5.1.0.CR1/server/default/tmp/ayw6m-gfnbbm-fsgkx4z8-1-fsguzifz-fnl/hellothere.war/ deployment failed ---------------------------------------------------------------------------------------------------------------- Server log contains this exception: ---------------------------------------------------------------------------------------------------------------- java.lang.IllegalArgumentException: Document base /home/ondra/work/JOPRembedded/embjopr-svn-trunk/jsfunit/target/jboss5x/tmp/3j011-ix4qw3-fshw77sa-1-fshw84bm-lj/hellothere.war does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:148) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:4021) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4188) ... (full stack trace attached.) ---------------------------------------------------------------------------------------------------------------- When tried again after a while, the WAR deploys successfully. -- 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

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2286) Requesting support for Drools Guvnor in a clustered environment

by Aaron Pestel (JIRA)

Requesting support for Drools Guvnor in a clustered environment --------------------------------------------------------------- Key: JBRULES-2286 URL: https://jira.jboss.org/jira/browse/JBRULES-2286 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-guvnor Environment: BRMS 5.0 Reporter: Aaron Pestel Assignee: Mark Proctor Requesting support for Drools Guvnor in a clustered environment for scalability, HA, and Failover. -- 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

16 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-94) Release jboss-common-core 2.2.16

by Dimitris Andreadis (JIRA)

Release jboss-common-core 2.2.16 -------------------------------- Key: JBCOMMON-94 URL: https://jira.jboss.org/jira/browse/JBCOMMON-94 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.16.GA -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-95) Upgrade jboss-loggin-spi to v2.1.0

by Dimitris Andreadis (JIRA)

Upgrade jboss-loggin-spi to v2.1.0 ---------------------------------- Key: JBCOMMON-95 URL: https://jira.jboss.org/jira/browse/JBCOMMON-95 Project: JBoss Common Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.15.GA Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.16.GA AS already points to jboss-logging-spi to 2.1.0 and we are still at 2.0.5. The update seems compatible. -- 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

16 years, 10 months

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