[JBoss JIRA] Created: (JBBOOT-133) Update ${version} to ${project.version}
by Andrew Lee Rubinger (JIRA)
Update ${version} to ${project.version}
---------------------------------------
Key: JBBOOT-133
URL: https://jira.jboss.org/jira/browse/JBBOOT-133
Project: JBoss Bootstrap
Issue Type: Bug
Components: api, api-as, api-embedded, api-mc, build, impl-as, impl-base, impl-embedded, impl-mc
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
As reported by Bob:
"In some of your POMs (such as jboss-bootstrap-impl-base-2.1.0-alpha-5.pom), you reference property ${version}, which 99% of the time is equiv to ${project.version}, but on the off-chance someone passes -Dversion=1.0.0.Beta19 on the commandline while invoking some plugin, maven quite happily applies it to other POMs it walks sometimes. "
Update to "project.version"
--
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, 10 months
[JBoss JIRA] Created: (JBRULES-2502) Add ability to set http read and connection timeout in millis in RuleAgent/KnowledgeAgent
by Tihomir Surdilovic (JIRA)
Add ability to set http read and connection timeout in millis in RuleAgent/KnowledgeAgent
-----------------------------------------------------------------------------------------
Key: JBRULES-2502
URL: https://jira.jboss.org/jira/browse/JBRULES-2502
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 5.1.0.M1, 4.0.7
Reporter: Tihomir Surdilovic
Assignee: Mark Proctor
Currently users have to set sun.net.client.defaultConnectTimeout and sun.net.client.defaultReadTimeout system properties to a reasonable value to account for network/connection issues when rule resources are being checked for updates by RuleAgent/KnowledgeAgent. This is requesting ability to set
both the read and connection timeouts through property/configuration options in RuleAgent and KnowledgeAgent to be able to specify user-defined settings.
The code should also log any information about the tried connection (how long it took, if it timed out, or was successful) for debugging purposes by users.
--
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, 10 months
[JBoss JIRA] Created: (JBCLUSTER-249) CacheManager destroys caches when it stops
by Brian Stansberry (JIRA)
CacheManager destroys caches when it stops
------------------------------------------
Key: JBCLUSTER-249
URL: https://jira.jboss.org/jira/browse/JBCLUSTER-249
Project: JBoss Clustering
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: HA-Server-Cache-JBC
Affects Versions: HA-Server-Cache-JBC 2.1.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: HA-Server-Cache-JBC 2.1.1.GA
CacheManager.stop() destroys all running caches. This is incorrect; since it didn't create them in start(). It should just call releaseCache for all eager-start caches to reduce the ref count. Then make the releaseCache method usable after stop() so if anyone has a ref to the CacheManager they can still release the cache.
This is essentially a workaround-type solution for JBAS-7228 and JBAS-7229. The correct solution for those is to have services using the CacheManager depend on it, so they stop first. But the MC may not be aware of everything using CacheManager (e.g. a Hibernate SessionFactory created by a ServletContextListener) so it can't always enforce dependencies. And, the ^^^ behavior of stop only undoing what start did is correct anyway.
--
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, 10 months
[JBoss JIRA] Created: (JBWEB-167) Entropy value causing jsp display issues
by Mike Millson (JIRA)
Entropy value causing jsp display issues
----------------------------------------
Key: JBWEB-167
URL: https://jira.jboss.org/jira/browse/JBWEB-167
Project: JBoss Web
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Core
Affects Versions: JBossWeb-2.1.7.GA
Reporter: Mike Millson
Assignee: Jean-Frederic Clere
The entropy value is causing some JBoss jmx-console pages to not render when the native connector is used.
For example, this link under jboss.web renders fine with the Java connector:
host=localhost,path=/jmx-console,type=Manager
I get the page back in the browser listing the MBean properties and functions.
But if I swap out the Java connector and use the native APR connector, I get no response.
Add the following if statement to inspectMBean.jsp to not print out the entropy value, and the page will display:
if(!attrName.equals("entropy")){
out.print("<input type='text' size='80' name='"+attrName+"' value='"+translateMetaCharacters(attrValue)+"' "+readonly+"/>");
}
--
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, 11 months