July 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5220) tmp/auth/ challenge files are not deleted when access is via JMX client

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/AS7-5220?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated AS7-5220: ---------------------------------- Priority: Critical (was: Major) > tmp/auth/ challenge files are not deleted when access is via JMX client > ----------------------------------------------------------------------- > > Key: AS7-5220 > URL: https://issues.jboss.org/browse/AS7-5220 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > the authentication process that creates temporary files in tmp/auth is not deleting them when a JMX client connects. > At an extreme, this would be a DOS attack, as the disk could fill up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8734) API change in deployment scanner's add cause failed deployments

by Rob Stryker (JIRA)

API change in deployment scanner's add cause failed deployments --------------------------------------------------------------- Key: JBAS-8734 URL: https://issues.jboss.org/browse/JBAS-8734 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: 6.0.0.CR1 Reporter: Rob Stryker Assignee: Ales Justin Priority: Critical When using the deployment scanner mbean to pass in a new URL that the JBossAS should scan for deployments, a path format which worked fine in JBoss 5 and below no longer works. Specifically, passing in a URL such as the one below: file:/home/rob/apps/eclipse/workspaces/main_code/runtime%20space%20workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1292215199516/deploy/Dyn888.war/ When passing this string into the addURL mbean, the following error in the jboss console results: 14:52:54,927 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] deploy, ctxPath=/Dyn888 14:52:54,930 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.web.deployment:war=/Dyn888 state=Create mode=Manual requiredState=Installed: java.net.URISyntaxException: Illegal character in path at index 56: file:/home/rob/apps/eclipse/workspaces/main_code/runtime space workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_6.0_Runtime_Server1292215199516/deploy/Dyn888.war/ at java.net.URI$Parser.fail(URI.java:2809) [:1.6.0_14] at java.net.URI$Parser.checkChars(URI.java:2982) [:1.6.0_14] Despite that I pass in a string with clear %20 blocking out the spaces, the deployment scanner does not seem to recognize this and errors. This format of a string has no problem working in AS 5.1 however. This is blocking JBossTools server integration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

10
31
0 / 0

[JBoss JIRA] (AS7-4720) Remove ProtocolTypeValidator

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4720: ------------------------------------- Summary: Remove ProtocolTypeValidator Key: AS7-4720 URL: https://issues.jboss.org/browse/AS7-4720 Project: Application Server 7 Issue Type: Task Components: Clustering Reporter: Brian Stansberry Assignee: Paul Ferraro Priority: Minor Fix For: 7.2.0.Alpha1 The ProtocolTypeValidator class is unused. This seems correct since using it would imply restricting JGroups protocols to the list in the Protocol enum, and I don't believe the intent is to prevent use of custom protocols or new ones that the JGroups project itself creates. If this class is removed, the Protocol enum itself may be a candidate for removal. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-686) Download statistics for the maven repository

by Geoffrey De Smet (JIRA)

Download statistics for the maven repository -------------------------------------------- Key: JBBUILD-686 URL: https://issues.jboss.org/browse/JBBUILD-686 Project: JBoss Build System Issue Type: Feature Request Components: Artifact Repositories Reporter: Geoffrey De Smet Fix For: Build Support 2011 Download statistics are an important requirement for project marketing. Last year, Sonatype announced download statistics for OSS projects on the central repository: http://www.sonatype.com/people/2010/12/now-available-central-download-sta... The JBoss repository should also have this. Even if a project (like drools or jbpm) is mirrored on central, only the originating repository (= the repository to which they were originally deployed) can host the download statistics. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] (LOGMGR-43) SubstituteFilter messages do not get formatted when using the PRINTF FormatStyle

by James Perkins (JIRA)

James Perkins created LOGMGR-43: ----------------------------------- Summary: SubstituteFilter messages do not get formatted when using the PRINTF FormatStyle Key: LOGMGR-43 URL: https://issues.jboss.org/browse/LOGMGR-43 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.3.2.Final Looks like by default the FormatStyle.MESSAGE_FORMAT is being used resulting the PRINTF string not properly being formatted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
2
0 / 0

[JBoss JIRA] (SECURITY-675) Tag Negotiation 2.1.1

by Darran Lofthouse (JIRA)

Darran Lofthouse created SECURITY-675: ----------------------------------------- Summary: Tag Negotiation 2.1.1 Key: SECURITY-675 URL: https://issues.jboss.org/browse/SECURITY-675 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Anil Saldhana -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] (AS7-5250) PatternFormatter: add support for "truncate from the beginning"

by Gernot P (JIRA)

Gernot P created AS7-5250: ----------------------------- Summary: PatternFormatter: add support for "truncate from the beginning" Key: AS7-5250 URL: https://issues.jboss.org/browse/AS7-5250 Project: Application Server 7 Issue Type: Feature Request Components: Logging Affects Versions: 7.1.1.Final Reporter: Gernot P Assignee: James Perkins org.jboss.logmanager.formatters.PatternFormatter does not support "truncate from the beginning" as log4j patterns do (see http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayou...) e.g. in log4j the format "%30.30c" outputs a fixed length category (30 characters) and truncates the category from the beginning if it's longer than 30 characters (especially for the category this is a reasonable choice, because the beginning of the category - which is mostly a package name - is always the same and therefore not menaingful) logmanager truncates at the end - so please add support for "truncate from the beginning" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Marco Rietveld resolved JBRULES-3318. ------------------------------------- Fix Version/s: 5.3.2.Final (was: FUTURE) Resolution: Done See attachments for an example of how to do this. It's possible that using this mechanism could result in error messages similar to the following: {noformat} 8185 25/07 16:08:44,215[main] WARN annotations.reflection.EJB3OverridenAnnotationReader.checkForOrphanProperties - Property org.drools.persistence.info.SessionInfo.rulesByteArray not found in class but described in <mapping-file/> (possible typo error) 8186 25/07 16:08:44,216[main] WARN annotations.reflection.EJB3OverridenAnnotationReader.checkForOrphanProperties - Property org.drools.persistence.info.SessionInfo.helper not found in class but described in <mapping-file/> (possible typo error) 8187 25/07 16:08:44,217[main] WARN annotations.reflection.EJB3OverridenAnnotationReader.checkForOrphanProperties - Property org.drools.persistence.info.WorkItemInfo.workItemId not found in class but described in <mapping-file/> (possible typo error) 8187 25/07 16:08:44,217[main] WARN annotations.reflection.EJB3OverridenAnnotationReader.checkForOrphanProperties - Property org.drools.persistence.info.WorkItemInfo.workitemByteArray not found in class but described in <mapping-file/> (possible typo error) 8187 25/07 16:08:44,217[main] WARN annotations.reflection.EJB3OverridenAnnotationReader.checkForOrphanProperties - Property org.drools.persistence.info.WorkItemInfo.env not found in class but described in <mapping-file/> (possible typo error) {noformat} This is a warning message because the ORM framework (hibernate, in this case) wants getter/setter methods for some private fields. However, this is _only_ a warning. The functionality works fine. > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: 5.3.2.Final > > Attachments: persistence.xml, rename-tables-orm.xml > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3318) Enable the Use of Different Table Names in drools-persistence-jpa

by Marco Rietveld (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3318?page=com.atlassian.jira.plug... ] Marco Rietveld updated JBRULES-3318: ------------------------------------ Attachment: rename-tables-orm.xml persistence.xml Attached examples of how to do this. > Enable the Use of Different Table Names in drools-persistence-jpa > ----------------------------------------------------------------- > > Key: JBRULES-3318 > URL: https://issues.jboss.org/browse/JBRULES-3318 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Jim Tyrrell > Assignee: Marco Rietveld > Fix For: FUTURE > > Attachments: persistence.xml, rename-tables-orm.xml > > > Customer is noticing a few table names that they would like to change out, ie use different ones. They also would like the table structure to match the naming conventions their organization employes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-2531) Provide better wording instead of "Unable to redirect." when accessing /console

by Radoslav Husar (Created) (JIRA)

Provide better wording instead of "Unable to redirect." when accessing /console ------------------------------------------------------------------------------- Key: AS7-2531 URL: https://issues.jboss.org/browse/AS7-2531 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Alpha1 Reporter: Radoslav Husar Assignee: Darran Lofthouse Attachments: redirect-reword.png See http://community.jboss.org/message/635278#635278 for steps to reproduce + screenshot Note that this is actually factually *wrong* because when you access from the host where the instance is running, the redirect is possible as localhost is the same. This needs better wording. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

7
7
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 July 2012