March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-7818) RMIAdaptor replacement based on JSR160

by Scott Marlow (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-7818?page=com.atlassian.jira.plug... ] Scott Marlow commented on JBAS-7818: ------------------------------------ I tried enabling the sun remote jmx connector but got the "Failed to initalize plugin: org.jboss.logging.logmanager.LoggerPluginImpl@359ecd80..." problem mentioned on http://community.jboss.org/wiki/UseJDK5JConsole As recommend, I added to run.conf: JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_ARGS="$JAVA_OPTS -Dorg.jboss.logging.Logger.pluginClass=org.jboss.logging.logmanager.LoggerPluginImpl" JBOSS_CLASSPATH="lib/jboss-logmanager.jar" But, that seems to cause an initial ten second pause before the AS boot echos the "INFO [HornetQServerImpl] live server is starting.." message. Then, right after the "[remoting] JBoss Remoting version 3.1.0.Beta2" console message, I see the "[service] Removing bootstrap log handlers" message. The AS server seems to pause at that point. The last messages on the console are: " 14:33:32,432 INFO [remoting] JBoss Remoting version 3.1.0.Beta2 14:33:32,562 INFO [service] Removing bootstrap log handlers " If I run without the above run.conf changes, I see a normal boot sequence: " 14:37:07,974 INFO [remoting] JBoss Remoting version 3.1.0.Beta2 14:37:08,083 INFO [TomcatDeployment] deploy, ctxPath=/ 14:37:08,165 INFO [service] Removing bootstrap log handlers 14:37:08,205 INFO [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Loading profile: ProfileKey@1c5ab93[domain=default, server=default, name=default] 14:37:08,215 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080 14:37:08,229 INFO [org.apache.coyote.ajp.AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 14:37:08,229 INFO [org.jboss.bootstrap.impl.base.server.AbstractServer] JBossAS [6.0.0.SNAPSHOT "Neo"] Started in 18s:284ms " > RMIAdaptor replacement based on JSR160 > -------------------------------------- > > Key: JBAS-7818 > URL: https://jira.jboss.org/jira/browse/JBAS-7818 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMX > Reporter: Scott M Stark > Assignee: Scott Marlow > Fix For: JBossAS-6.0.0.M3 > > > A replacement for the proprietary RMIAdaptor is needed that supports authentication, authorization and SSL. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBXB-244) don't use repeatable handlers for terms inside unordered sequences

by Alexey Loubyansky (JIRA)

don't use repeatable handlers for terms inside unordered sequences ------------------------------------------------------------------ Key: JBXB-244 URL: https://jira.jboss.org/jira/browse/JBXB-244 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.2.Beta5 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA People are asking for over-the-edge freedom in (un)ordering their elements in xml. Not only terms of unordered sequences should be allowed to appear in any order but also repeatable terms should be allowed to be spread and mixed with other terms, i.e. not necessarily appear in a sequence. Which of course breaks collecting and setting values by repeatable particle handlers. So, the only way to have repeatable terms collected correctly is to disable repeatable particle handlers and add items directly to the properties. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBXB-242) binding repeatable elements into model group all should fail

by Alexey Loubyansky (JIRA)

binding repeatable elements into model group all should fail ------------------------------------------------------------ Key: JBXB-242 URL: https://jira.jboss.org/jira/browse/JBXB-242 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.2.Beta5 Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA AllBinding currently silently accepts repeatable elements which it shouldn't according to the spec. Schema Component Constraint: All Group Limited When a model group has {compositor} all, then all of the following must be true: 1 It appears only as the value of one or both of the following properties: 1.1 the {model group} property of a model group definition. 1.2 the {term} property of a particle with {max occurs}=1which is part of a pair which constitutes the {content type} of a complex type definition. 2 The {max occurs} of all the particles in the {particles} of the group must be 0 or 1. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-106) Remove System.out.println call from UclDelegatingClassPoolFactory

by Flavia Rainone (JIRA)

Remove System.out.println call from UclDelegatingClassPoolFactory ----------------------------------------------------------------- Key: JBREFLECT-106 URL: https://jira.jboss.org/jira/browse/JBREFLECT-106 Project: JBoss Reflection Issue Type: Task Components: Class Pool Affects Versions: JBossReflection.2.2.0-Alpha4 Reporter: Flavia Rainone Assignee: Flavia Rainone Fix For: JBossReflection.2.2.0-Alpha5 This System.out.prinltn call have been copied from original class in JBoss AOP. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-780) Fix line overflows in documentation

by Flavia Rainone (JIRA)

Fix line overflows in documentation ----------------------------------- Key: JBAOP-780 URL: https://jira.jboss.org/jira/browse/JBAOP-780 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Flavia Rainone There are several messages such as this one, when building a release: WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: -1/-1) This accounts for broken lines in the pdf version, and should be fixed. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBEE-40) Add jboss-el-api_2.2_spec 1.0.0.Beta1 missing PrivateMessages.properties

by Shelly McGowan (JIRA)

Add jboss-el-api_2.2_spec 1.0.0.Beta1 missing PrivateMessages.properties ------------------------------------------------------------------------- Key: JBEE-40 URL: https://jira.jboss.org/jira/browse/JBEE-40 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 Detected during testing: Received: java.util.MissingResourceException: Can't find bundle for base name javax.el.PrivateMessages, locale en_US at tests.el.api.javax_el.beanelresolver.ELClient.beanELResolverPNWETest(ELClient.java:316) Similar to JBEE-35. Need to adjust the build so PrivateMessages.properties gets included in the .jar. -- 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

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7814) Integrate VFS 3.0.0.CR5

by John Bailey (JIRA)

Integrate VFS 3.0.0.CR5 ----------------------- Key: JBAS-7814 URL: https://jira.jboss.org/jira/browse/JBAS-7814 Project: JBoss Application Server Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Components: VFS Affects Versions: JBossAS-6.0.0.M2 Reporter: John Bailey Assignee: John Bailey Fix For: JBossAS-6.0.0.M3 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7823) Integrate EJBContextBinder

by Carlo de Wolf (JIRA)

Integrate EJBContextBinder -------------------------- Key: JBAS-7823 URL: https://jira.jboss.org/jira/browse/JBAS-7823 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Carlo de Wolf Assignee: Carlo de Wolf Fix For: JBossAS-6.0.0.M3 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7821) Application server can not be started with a java security manager

by Dmitri Voronov (JIRA)

Application server can not be started with a java security manager ------------------------------------------------------------------ Key: JBAS-7821 URL: https://jira.jboss.org/jira/browse/JBAS-7821 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-6.0.0.M2 Environment: Windows Vista, jdk 1.6.0 (build 1.6.0_07-b06) Reporter: Dmitri Voronov If JBoss is started with a java security manager: -Djava.security.manager ^ an exception is thrown: java.security.AccessControlException: access denied (java.util.PropertyPermission * read,write) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323) at java.security.AccessController.checkPermission(AccessController.java:546) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.SecurityManager.checkPropertiesAccess(SecurityManager.java:1252) at java.lang.System.getProperties(System.java:582) at org.jboss.Main.<init>(Main.java:146) at org.jboss.Main$1.run(Main.java:737) at java.lang.Thread.run(Thread.java:619) this issue occurs even if a policy file with the required permission is provided: -Djava.security.policy=C:/server.policy containing: grant { permission java.util.PropertyPermission "*", "read,write"; ... }; -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7820) StackoverflowError during login

by Stefan Ries (JIRA)

StackoverflowError during login ------------------------------- Key: JBAS-7820 URL: https://jira.jboss.org/jira/browse/JBAS-7820 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.GA Environment: windows XP Reporter: Stefan Ries Assignee: Anil Saldhana I'm using a custom loginmodule which accesses a secured bean "SecurityBean". I'm using module-stacking with the RunAsLoginModule to gain access to the secured bean. The bean again accesses another beans "WorkflowBean" to collect userdata. With JBoss 4.3 everything was working fine. Now with JBoss 5.0, the behaviour is like this: - The loginmodule successfully accesses the SecurityBean - When the SecurityBean accesses the WorkflowBean, the interceptor kicks in and forces another authentication with the loginmodule. This leads to an endless recursion. Both beans have the same securitycontext. -- 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

16 years, 4 months

1
0
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 March 2010