February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (LOGBRIDGE-5) Unreferenced loggers retain their settings when log4j configuration changes

by David Lloyd (JIRA)

Unreferenced loggers retain their settings when log4j configuration changes --------------------------------------------------------------------------- Key: LOGBRIDGE-5 URL: https://issues.jboss.org/browse/LOGBRIDGE-5 Project: Log Bridge Issue Type: Bug Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.CR2 Because the old loggers are not cleared first. All known loggers which were not reconfigured should have their level cleared as part of the update. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2241) Restore user's settings and portlets to default

by Brian Dill (JIRA)

Restore user's settings and portlets to default ----------------------------------------------- Key: JBPORTAL-2241 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2241 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.6 Final Reporter: Brian Dill Allow portal users to restore their portal to the original settings/portlets. Excerpt from discussion with Thomas Heute. "They could store the location of the reference as a portal object property of the copied page. And copy what exists for 'Copy this page to my dashboard' link. If the referenced page didn't change, they could then delete the current page, and copy the one referenced as portal object property." -- 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

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1252) TCP Gossip Discovery Issue

by Grahame Rogers (JIRA)

TCP Gossip Discovery Issue -------------------------- Key: JGRP-1252 URL: https://jira.jboss.org/browse/JGRP-1252 Project: JGroups Issue Type: Bug Affects Versions: 2.11 Environment: Windows XP and Solaris 5.10 Reporter: Grahame Rogers Assignee: Bela Ban Fix For: 2.11.1 I run the chat demo app that was shipped with an older version of Jgroups. Using tcp transport, with tcpgossip for discovery I start up 2 instances of the chat application. I then restart the gossip server and also another instance of the chat application. The 3rd instance of the chat application receives a view update (membershipListener.viewAccepted) only the logical name of one of the 2 previous instances of the chat client is incorrect. I have detailed the results in: http://old.nabble.com/TCPGossip-Discovery-Issue-td30227966.html I will attach the test client to this bug report. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

4
44
0 / 0

[JBoss JIRA] Created: (JBREM-1274) Release 2.5.4.SP1

by Ron Sigal (JIRA)

Release 2.5.4.SP1 ----------------- Key: JBREM-1274 URL: https://issues.jboss.org/browse/JBREM-1274 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2909) Build: development setup howto's, tips & tricks in the README.txt file for git, maven, eclipse, intellij, ...

by Geoffrey De Smet (JIRA)

Build: development setup howto's, tips & tricks in the README.txt file for git, maven, eclipse, intellij, ... ------------------------------------------------------------------------------------------------------------- Key: JBRULES-2909 URL: https://issues.jboss.org/browse/JBRULES-2909 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2911) Planner: simulated annealing should work for planning problems with many hard constraints broken

by Geoffrey De Smet (JIRA)

Planner: simulated annealing should work for planning problems with many hard constraints broken ------------------------------------------------------------------------------------------------ Key: JBRULES-2911 URL: https://issues.jboss.org/browse/JBRULES-2911 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: 5.2.0.M2 This code is bad in SimulatedAnnealingAcceptor: // TODO don't abuse translateScoreToGraphValue // TODO do hard and soft separately and then average their acceptChance Double diff = localSearchSolverScope.getScoreDefinition().translateScoreToGraphValue(scoreDifference); if (diff == null) { // more hard constraints broken, ignore it for now return 0.0; } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-8876) Add JSF to AS7

by Stan Silvert (JIRA)

Add JSF to AS7 -------------- Key: JBAS-8876 URL: https://issues.jboss.org/browse/JBAS-8876 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JSF Affects Versions: 7.0.0.Alpha1 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 7.0.0.Alpha2 Add Mojarra 2.0.4 to AS7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2861) HttpSession sharing between WAR modules

by Eugeniusz Neugebauer (JIRA)

[ https://issues.jboss.org/browse/JBAS-2861?page=com.atlassian.jira.plugin.... ] Eugeniusz Neugebauer commented on JBAS-2861: -------------------------------------------- I'm to interesting in this improvement. Is possible to do this in another way ? regard ENE > HttpSession sharing between WAR modules > --------------------------------------- > > Key: JBAS-2861 > URL: https://issues.jboss.org/browse/JBAS-2861 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering, Web (Tomcat) service > Affects Versions: JBossAS-3.2.6 Final, JBossAS-3.2.7 Final > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: TBD > > > Creating a redacted version of JBAS-1909, which was opened as a non-public JIRA issue by a customer. > Our J2EE application is composed of several modules, each one addressing one facet of our business process, and currently this application has one web module (WAR) and several JAR modules (EJB). > We need to divide this web module into several smaller web modules. > In order to separate our unique WAR file into several WARs we must guarantee HttpSession sharing. This is due to the fact that we have a lot of session attributes that are used throughout the entire application and we cannot afford to refactor the application, in fact, that's impossible. > The security aspects for this requirement are completely addressed by the JBoss/Tomcat Single Sign-On mechanism but the session sharing requirements are not. > The ideal scenario is to keep the same HttpSession (same object in the heap, same session ID) when authenticating into one application (HttpSession created) and then forwarding to another application. > The current SSO mechanism allows the user to access the second application without reauthentication, as you know, but it creates a new HttpSession object. Also, if the two WARs have different session timeouts, if you access application A, migrates to application B, stays there until session in application A expires and then returns to application A from application B, a new HttpSession is also created in application A. > The ideal solution is to have one unique, monolithic session to all web applications configured to share a common session. IBM WebSphere and BEA WebLogic do have this configuration and feature. Please check the links below in case you want more information: > WebSphere Application Server V5: Sharing Session Context - http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0215.ht... > BEA Weblogic - Enabling Web applications to share the same session - http://e-docs.bea.com/wls/docs90/webapp/sessions.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1297) Make generation of addresses pluggable

by Bela Ban (JIRA)

Make generation of addresses pluggable -------------------------------------- Key: JGRP-1297 URL: https://issues.jboss.org/browse/JGRP-1297 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 Sometimes it might be desirable to provide custom addresses (classes implementing org.jgroups.Address). One example is an address which contains additional data, e.g. an attribute that's shipped around with the address. SOLUTION: JChannel provides a setAddressGenerator(AddressGenerator). AddressGenerator has a method generateAddress(), which returns an Address. One could create a subclass of UUID, for instance, and add a string to it, and then create an instance of this subclass in generateAddress(). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-8906) Service in START_FAILED state does not transition when mode is changed to REMOVE

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/JBAS-8906?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved JBAS-8906. ------------------------------------ Fix Version/s: 7.0.0.Alpha2 Resolution: Done Resolved with commits in http://github.com/jbossas/jboss-as/compare/f232102...63046a5 > Service in START_FAILED state does not transition when mode is changed to REMOVE > -------------------------------------------------------------------------------- > > Key: JBAS-8906 > URL: https://issues.jboss.org/browse/JBAS-8906 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Assignee: Brian Stansberry > Fix For: 7.0.0.Alpha2 > > Attachments: forceNPE.patch, w2.war > > > Here's an example service dump: > ^C13:22:49,405 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Stopping Coyote HTTP/1.1 on http-8080 > 13:22:49,425 INFO [org.jboss.as.logging] Restored bootstrap log handlers > 13:22:49,431 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped > ^C > 13:27:25,270 INFO [stdout] Services for jboss-as: > 13:27:25,276 INFO [stdout] Service "jboss.as" (class org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED) > 13:27:25,276 INFO [stdout] Service "jboss.as.external-module-service" (class org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) > 13:27:25,279 INFO [stdout] Service "jboss.as.server-controller" (class org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) (dependencies: jboss.as.external-module-service, jboss.as.service-module-loader, jboss.deployment-repository) > 13:27:25,279 INFO [stdout] Service "jboss.as.service-module-loader" (class org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) > 13:27:25,280 INFO [stdout] Service "jboss.deployment.chains" (class org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller) > 13:27:25,280 INFO [stdout] Service "jboss.deployment.unit."test3.jar"" (class org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies: jboss.deployment.chains, jboss.deployment-repository) > 13:27:25,282 INFO [stdout] Service "jboss.deployment.unit."test3.jar".CONFIGURE_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".DEPENDENCIES) (dependencies: jboss.deployment.chains, jboss.deployment.unit."test3.jar".DEPENDENCIES) > 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".DEPENDENCIES" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".PARSE) (dependencies: jboss.deployment.unit."test3.jar".PARSE, jboss.deployment.chains) > 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".INSTALL" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state START_FAILED (parent: jboss.deployment.unit."test3.jar".POST_MODULE) (dependencies: jboss.deployment.unit."test3.jar".POST_MODULE, jboss.deployment.chains) (has failed dependency) > 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".PARSE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".STRUCTURE) (dependencies: jboss.deployment.unit."test3.jar".STRUCTURE, jboss.deployment.chains) > 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".POST_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: module.service."deployment.test3.jar".main, jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.chains) > 13:27:25,285 INFO [stdout] Service "jboss.deployment.unit."test3.jar".STRUCTURE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar") (dependencies: jboss.deployment.chains) > 13:27:25,285 INFO [stdout] Service "jboss.deployment-repository" (class org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) > 13:27:25,285 INFO [stdout] Service "module.service."deployment.test3.jar".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.as.service-module-loader, module.spec.service."deployment.test3.jar".main) > 13:27:25,286 INFO [stdout] Service "module.spec.service."deployment.test3.jar".main" (class org.jboss.msc.service.ValueService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.unit."test3.jar") > 13:27:25,286 INFO [stdout] 15 services displayed -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2011