January 2009 - jboss-jira - Jboss List Archives

[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

13 years, 9 months

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

13 years, 9 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

13 years, 9 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

13 years, 9 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

13 years, 9 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

13 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-421) Classpath is incorrect when running javadoc reports

by Paul Gier (JIRA)

Classpath is incorrect when running javadoc reports --------------------------------------------------- Key: JBBUILD-421 URL: http://jira.jboss.com/jira/browse/JBBUILD-421 Project: JBoss Build System Issue Type: Bug Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 JBoss Cache build has an issue with the javadoc plugin. The javadocs work fine when run from the main build, but fail with errors when generating the site. It appears that the testng jar is required for the javadoc generation, but this jar is not getting included in the classpath when run from the reports section. The issue could be related to this one: http://jira.codehaus.org/browse/MJAVADOC-140 -- 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

13 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-442) Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files

by pether (JIRA)

Fix pom.xmls so that maven-eclipse-plugin generate correct eclipse settings files --------------------------------------------------------------------------------- Key: JBBUILD-442 URL: http://jira.jboss.com/jira/browse/JBBUILD-442 Project: JBoss Build System Issue Type: Feature Request Components: Maven Affects Versions: Maven Build - Maint 2008 Reporter: pether Priority: Minor Fix For: Maven Build - Maint 2008 Two different cases that should work for developers to choose from 1. Using eclipse project references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true 2. Using maven repository jar references generate files with : mvn eclipse:clean eclipse:eclipse -Declipse.useProjectReferences=true In some ways an audit of http://jira.jboss.org/jira/browse/JBBUILD-258 and resolve any issues with dependencies. Current issues with jboss/trunk The projects below have compile errors, mostly incorrect project dependencies jboss-as-deployment jboss-as-console jboss-as-iiop jboss-as-varia -- 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

13 years, 10 months

2
13
0 / 0

[JBoss JIRA] Created: (JBBUILD-469) Create a bouncycastle dist without IDEA code

by Scott M Stark (JIRA)

Create a bouncycastle dist without IDEA code -------------------------------------------- Key: JBBUILD-469 URL: http://jira.jboss.com/jira/browse/JBBUILD-469 Project: JBoss Build System Issue Type: Feature Request Reporter: Scott M Stark Assigned To: Scott M Stark Create a dist from the http://www.bouncycastle.org/ code that does not include the patent encumbered IDEA algorithms. -- 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

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JGRP-685) Perf test

by Bela Ban (JIRA)

Perf test --------- Key: JGRP-685 URL: http://jira.jboss.com/jira/browse/JGRP-685 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.7 Things to do with the perf test: - Mimick buddy replication: send messages not to self, but only to a selected buddy - Measure time to send 100MB to A, B, C, D - New look at HTOTAL, might help with perf in this scenario - TcpTransport (95MB/sec) versus JGroupsTransport/tcp.xml (54MB/sec): why the diff ? - Members: A (send), B (receive) - Might get better perf with impl of first bullet item (above) - JPerf (between A and B) gets 113MB/sec ! -- 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

13 years, 10 months

1
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2009