July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1020) CLOUD_PING: investigate discovery protocol (similar to FILE_PING) on S3 etc

by Bela Ban (JIRA)

CLOUD_PING: investigate discovery protocol (similar to FILE_PING) on S3 etc --------------------------------------------------------------------------- Key: JGRP-1020 URL: https://jira.jboss.org/jira/browse/JGRP-1020 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.x -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JGRP-973) DistributedLockManager: lock() should block for timeout ms until it can acquire lock

by Bela Ban (JIRA)

DistributedLockManager: lock() should block for timeout ms until it can acquire lock ------------------------------------------------------------------------------------ Key: JGRP-973 URL: https://jira.jboss.org/jira/browse/JGRP-973 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.8 Currently, lock() throw an exception *immediately* if the lock is held by someone else. It doesn't respect the timeout parameter, change this. This might be possible by picking a different VotingAdapter, have to investigate. -- 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

15 years, 6 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-6307) Cross-cluster cross-talk on JBM-DATA channel

by Brian Stansberry (JIRA)

Cross-cluster cross-talk on JBM-DATA channel -------------------------------------------- Key: JBAS-6307 URL: https://jira.jboss.org/jira/browse/JBAS-6307 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, JMS (JBoss Messaging) Affects Versions: JBossAS-5.0.0.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.1.CR1 The configuration syntax in the jbm-data protocol stack config's MPING.mcast_addr attribute is not understood by the JGroups parser; it's syntax only supported by the String property replacement code in jboss-common-core.jar. <MPING timeout="5000" mcast_addr="${jboss.messaging.datachanneludpaddress,jboss.partition.udpGroup:228.6.6.6}" will be evaluated by JGroups as "use value for system property 'jboss.messaging.datachanneludpaddress,jboss.partition.udpGroup', if not found use 228.6.6.6". Which results in 228.6.6.6. Fix is to replace with <MPING timeout="5000" mcast_addr="${jboss.partition.udpGroup:228.6.6.6}" in which case setting -u at AS startup will set jboss.partition.udpGroup, which JGroups will find and use. -- 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

15 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1582) Info logging should have no more than 1 line per step

by Geoffrey De Smet (JIRA)

Info logging should have no more than 1 line per step ----------------------------------------------------- Key: JBRULES-1582 URL: http://jira.jboss.com/jira/browse/JBRULES-1582 Project: JBoss Drools Issue Type: Task Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Refactor logging so it's smaller and more readable. Watch out for logging a move after it has been taken, as it's logging info doesn't hold true no more. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-191) JAXPDeployer should set the setXIncludeAware on the DocumentBuilderFactory

by Anil Saldhana (JIRA)

JAXPDeployer should set the setXIncludeAware on the DocumentBuilderFactory -------------------------------------------------------------------------- Key: JBDEPLOY-191 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-191 Project: JBoss Deployers Issue Type: Feature Request Components: deployer Reporter: Anil Saldhana Set state of XInclude processing. If XInclude markup is found in the document instance, should it be processed as specified in XML Inclusions (XInclude) Version 1.0. (http://www.w3.org/TR/xinclude/) XInclude processing defaults to false. -- 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

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (SECURITY-56) SecurityContextAssociation missing in client path

by Thomas Diesler (JIRA)

SecurityContextAssociation missing in client path ------------------------------------------------- Key: SECURITY-56 URL: http://jira.jboss.com/jira/browse/SECURITY-56 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Anil Saldhana bin/twiddle.sh doe not work in AS5.0 because of missing security classes. A scan on client jars shows that SecurityContextAssociation is not part of any client jar [tdiesler@jbws jboss-5.0.0.Beta3]$ bin/twiddle.sh -s jnp://jbws2:1099 get jboss.system:type=Server Started Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/security/plugins/SecurityContextAssociation at org.jboss.proxy.SecurityActions$1.getPrincipal(SecurityActions.java:57) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:58) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy0.getAttributes(Unknown Source) at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168) at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305) -- 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

15 years, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-6180) create a security lock-up script

by Aleksandar Kostadinov (JIRA)

create a security lock-up script -------------------------------- Key: JBAS-6180 URL: https://jira.jboss.org/jira/browse/JBAS-6180 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.CR2 Reporter: Aleksandar Kostadinov Assignee: Aleksandar Kostadinov Create a security lock-up script for use before network deployment. Create a test script to check if the protected resources have been really protected. -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-292) org.jboss.security.plugins.FilePassword requires write permission for decoding

by Alan Feng (JIRA)

org.jboss.security.plugins.FilePassword requires write permission for decoding ------------------------------------------------------------------------------ Key: SECURITY-292 URL: https://jira.jboss.org/jira/browse/SECURITY-292 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.2.CR8, 2.0.2.CR7, 2.0.2.CR6, 2.0.2.CR5, 2.0.2.CR4, 2.0.2.CR3, 2.0.2.CR2, 2.0.2.CR1, 2.0.2.Beta7, 2.0.2-BETA6, 2.0.2-BETA5, 2.0.2-BETA4, 2.0.2-BETA3, 2.0.1-BETA2, 2.0.1-BETA1, 2.0.2-BETA, 2.0.1.GA Environment: JBoss AS 4.2.3.GA Reporter: Alan Feng Assignee: Anil Saldhana Priority: Minor We use org.jboss.security.plugins.FilePassword to avoid storing passwords in clear text. Once created, we'd like to change the file's permission to read-only for regular users in order to ensure that only trusted users can update it. However, this won't work as the class FilePassword always requires write permission even for decoding the password. The class should be modified so that write permission is only required when create / update the password file. -- 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

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-512) Create a maven plugin that can pull a pom from the repository and compare versions

by Paul Gier (JIRA)

Create a maven plugin that can pull a pom from the repository and compare versions ---------------------------------------------------------------------------------- Key: JBBUILD-512 URL: https://jira.jboss.org/jira/browse/JBBUILD-512 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2009 Dimitris suggested that it would be useful to have a maven plugin that can read a pom from a given URL (or maybe from the maven repo). The plugin would then compare the dependencies listed in this pom to the dependency versions of the current project. It would then report on the results showing where the versions conflict. Note: Possibly this could be added as a feature to the maven dependency plugin. -- 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

15 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3703) Update JRMPInvoker to not cast exported object to RemoteStub

by Scott M Stark (JIRA)

Update JRMPInvoker to not cast exported object to RemoteStub ------------------------------------------------------------ Key: JBAS-3703 URL: http://jira.jboss.com/jira/browse/JBAS-3703 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1 Reporter: Scott M Stark Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 If one runs with the jdk5 java.rmi.server.ignoreStubClasses dynamic stub override to force the server to generate stubs for exported objects, the JRMPInvoker fails to start with the following exception: [starksm@succubus bin]$ run.sh -D-Djava.rmi.server.ignoreStubClasses=true ========================================================================= ... 11:55:52,477 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp java.lang.ClassCastException: $Proxy13 at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:437) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:359) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:136) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274) The reason is that the code creating the remote object is explictly casting the export result to a RemoteStub: protected void exportCI() throws Exception { this.invokerStub = (RemoteStub) UnicastRemoteObject.exportObject (this, rmiPort, clientSocketFactory, serverSocketFactory); } even though the public contract for this stub only requires a Serializable instance. The type of the invokerStub should just be relaxed to Serializable. -- 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

15 years, 7 months

4
3
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 2009