March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-150) The jboss-jstl-api_1.2_spec artifact depends on xalan artifact that is not present in Maven Central

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBEE-150?page=com.atlassian.jira.plugin.s... ] Shelly McGowan edited comment on JBEE-150 at 3/11/14 9:16 PM: -------------------------------------------------------------- [~trepel] Does it help your situation if include the Java EE API BOM for full or web profile as the artifact to your maven project instead of just jboss-jstl-api_1.2_spec. Full Profile APIs: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... or Web Profile APIs only: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... I thought I had resolve that problem with exclusions using the BOMS (see also: JBEE-97, JBEE-112, JBEE-118) was (Author: shelly.mcgowan): [~trepel] Does it help your situation if include the Java EE API BOM for full or web profile as the artifcat to your maven project instead of just jboss-jstl-api_1.2_spec. Full Profile APIs: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... or Web Profile APIs only: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... I thought I had resolve that problem with exclusions using the BOMS (see also: JBEE-97, JBEE-112, JBEE-118) > The jboss-jstl-api_1.2_spec artifact depends on xalan artifact that is not present in Maven Central > --------------------------------------------------------------------------------------------------- > > Key: JBEE-150 > URL: https://issues.jboss.org/browse/JBEE-150 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Tomas Repel > Assignee: Shelly McGowan > > The org.jboss.spec.javax.servlet.jstl:jboss-jstl-api_1.2_spec:1.1.0.Final depends on xalan:xalan:2.7.1.jbossorg-2 artifact, this one is not present in Maven Central. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3099) management authorization throws an exception when an LDAP group contains a slash/backslash character

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3099?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3099: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1074560|https://bugzilla.redhat.com/show_bug.cgi?id=1074560] from MODIFIED to POST > management authorization throws an exception when an LDAP group contains a slash/backslash character > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-3099 > URL: https://issues.jboss.org/browse/WFLY-3099 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Tom Fonteyne > > management authorization throws an exception when an LDAP group contains a slash/backslash character -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2004) Formatter "COLOR-PATTERN" is not found

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2004?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-2004. ------------------------------- Fix Version/s: (was: 8.0.1.Final) Resolution: Cannot Reproduce Bug I can't seem to reproduce this. If it's still an issue, please reopen. > Formatter "COLOR-PATTERN" is not found > -------------------------------------- > > Key: WFLY-2004 > URL: https://issues.jboss.org/browse/WFLY-2004 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Attachments: domain.xml, host.xml > > > Failed to start a server on a second host: > {noformat} > [Host Controller] INFO [org.jboss.as.host.controller] JBAS010919: Registering server stage1 > [Server:stage1] ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([ > [Server:stage1] ("subsystem" => "logging"), > [Server:stage1] ("console-handler" => "CONSOLE") > [Server:stage1] ]): java.lang.IllegalArgumentException: Formatter "COLOR-PATTERN" is not found > [Server:stage1] at org.jboss.logmanager.config.HandlerConfigurationImpl$1.validate(HandlerConfigurationImpl.java:83) [jboss-logmanager-1.5.0.Final.jar:1.5.0.Final] > [Server:stage1] at org.jboss.logmanager.config.HandlerConfigurationImpl$1.validate(HandlerConfigurationImpl.java:80) [jboss-logmanager-1.5.0.Final.jar:1.5.0.Final] > [Server:stage1] at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:338) [jboss-logmanager-1.5.0.Final.jar:1.5.0.Final] > [Server:stage1] at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:291) [jboss-logmanager-1.5.0.Final.jar:1.5.0.Final] > [Server:stage1] at org.jboss.as.logging.logmanager.ConfigurationPersistence.prepare(ConfigurationPersistence.java:303) > [Server:stage1] at org.jboss.as.logging.LoggingOperations$CommitOperationStepHandler.execute(LoggingOperations.java:97) > [Server:stage1] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:320) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:288) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > [Server:stage1] at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3102) EJB in WAR should inherit WAR's security domain

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3102?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-3102: -------------------------------------- The big problem would be that this change would break backwards compatibility, although I am not sure how much of an issue it would be in practice. >From a technical point of view this is not a difficult change. > EJB in WAR should inherit WAR's security domain > ----------------------------------------------- > > Key: WFLY-3102 > URL: https://issues.jboss.org/browse/WFLY-3102 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Final > Reporter: Bill Burke > Assignee: Stuart Douglas > > If you define an EJB within WEB-INF/classes it does not inherit the security domain from the WAR file and defaults to "other". Counter-intuitive, IMO. Not sure if it is easily fixable though -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3102) EJB in WAR should inherit WAR's security domain

by Bill Burke (JIRA)

Bill Burke created WFLY-3102: -------------------------------- Summary: EJB in WAR should inherit WAR's security domain Key: WFLY-3102 URL: https://issues.jboss.org/browse/WFLY-3102 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 8.0.0.Final Reporter: Bill Burke Assignee: Stuart Douglas If you define an EJB within WEB-INF/classes it does not inherit the security domain from the WAR file and defaults to "other". Counter-intuitive, IMO. Not sure if it is easily fixable though -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2920) StackOverflowError when org.jboss.as.jacorb.rmi.InterfaceAnalysis is analyzing javax.ejb.EJBObject

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2920?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2920: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1064644|https://bugzilla.redhat.com/show_bug.cgi?id=1064644] from MODIFIED to ON_QA > StackOverflowError when org.jboss.as.jacorb.rmi.InterfaceAnalysis is analyzing javax.ejb.EJBObject > -------------------------------------------------------------------------------------------------- > > Key: WFLY-2920 > URL: https://issues.jboss.org/browse/WFLY-2920 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: IIOP > Affects Versions: 8.0.0.Final > Reporter: Osamu Nagano > Assignee: Stefan Guilhen > Attachments: td.dump > > > Depending on when a thread context switch happens, an IIOP enabled EJB fails to be deployed by throwing {{java.lang.StackOverflowError}}. Here is the stack trace from the attached thread dump. > {code} > "MSC service thread 1-7" prio=10 tid=0x00007f52e8001800 nid=0x4d12 at breakpoint[0x00007f534093f000] > java.lang.Thread.State: RUNNABLE > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > at org.jboss.as.jacorb.rmi.OperationAnalysis.<init>(OperationAnalysis.java:91) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.analyzeOperations(InterfaceAnalysis.java:116) > at org.jboss.as.jacorb.rmi.ContainerAnalysis.doAnalyze(ContainerAnalysis.java:186) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.doAnalyze(InterfaceAnalysis.java:62) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.as.jacorb.rmi.WorkCacheManager.doTheWork(WorkCacheManager.java:177) > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > at org.jboss.as.jacorb.rmi.OperationAnalysis.<init>(OperationAnalysis.java:91) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.analyzeOperations(InterfaceAnalysis.java:116) > at org.jboss.as.jacorb.rmi.ContainerAnalysis.doAnalyze(ContainerAnalysis.java:186) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.doAnalyze(InterfaceAnalysis.java:62) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > ... > at org.jboss.as.jacorb.rmi.WorkCacheManager.doTheWork(WorkCacheManager.java:177) > at org.jboss.as.jacorb.rmi.WorkCacheManager.getAnalysis(WorkCacheManager.java:105) > at org.jboss.as.jacorb.rmi.InterfaceAnalysis.getInterfaceAnalysis(InterfaceAnalysis.java:53) > at org.jboss.as.jacorb.rmi.Util.getTypeIDLName(Util.java:104) > at org.jboss.as.jacorb.rmi.ParameterAnalysis.<init>(ParameterAnalysis.java:50) > Locked ownable synchronizers: > - <0x00000000f9698790> (a java.util.concurrent.ThreadPoolExecutor$Worker) > {code} > The last part including {{Util.getTypeIDLName}} has been repeated as many as possible and the bottom of the stack has been lost. The same stack has been appeared in a different MSC service thread which is also executing an IIOP enabled EJB deployment. > The customer identified an improper synchronization in {{org.jboss.as.jacorb.rmi.WorkCacheManager#getAnalysis()}}. It is reproducible by manually controlling a thread context switch using a debugger. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3094) Warn if there is no resource bound for address-settings expiry and dead-letter addresses

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3094?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3094: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1014099|https://bugzilla.redhat.com/show_bug.cgi?id=1014099] from MODIFIED to ON_QA > Warn if there is no resource bound for address-settings expiry and dead-letter addresses > ---------------------------------------------------------------------------------------- > > Key: WFLY-3094 > URL: https://issues.jboss.org/browse/WFLY-3094 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > > Warns the user if a address-setting has defined an expiry-address or a dead-letter-address with no queue bound for them as this will result in unintended message loss. > WildFly default full configuration specifies an expiry address (jms.queue.ExpiryQueue) and dead-letter-addres (jms.queue.DLQ) for the # address settings (i.e. matching all addresses). > To have a consistent configuration, we must also define 2 queues that will be bound to these settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3073) MBeanServer.createMBean methods that take a classloader don't work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3073?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3073: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1073106|https://bugzilla.redhat.com/show_bug.cgi?id=1073106] from MODIFIED to ON_QA > MBeanServer.createMBean methods that take a classloader don't work > ------------------------------------------------------------------ > > Key: WFLY-3073 > URL: https://issues.jboss.org/browse/WFLY-3073 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: 8.0.0.Final > Reporter: Stuart Douglas > Assignee: Kabir Khan > Fix For: 8.0.1.Final > > > The MBeanServer.createMBean methods that take an "ObjectName loaderName" argument are completely broken in EAP 6. > These methods call findDelegate to make sure there is already an existing MBean registered with the given name passed in for the new MBean, or else it throws an exception. > This is obviously wrong, as there'd be no point in calling createMBean if it already existed. > javax.management.InstanceNotFoundException: test:service=Test > at org.jboss.as.jmx.PluggableMBeanServerImpl.findDelegate(PluggableMBeanServerImpl.java:1083) > at org.jboss.as.jmx.PluggableMBeanServerImpl.createMBean(PluggableMBeanServerImpl.java:253) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3069) slaves cannot reconnect to a restarted master if RBAC is enabled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3069: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1072915|https://bugzilla.redhat.com/show_bug.cgi?id=1072915] from MODIFIED to ON_QA > slaves cannot reconnect to a restarted master if RBAC is enabled > ---------------------------------------------------------------- > > Key: WFLY-3069 > URL: https://issues.jboss.org/browse/WFLY-3069 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Final > Reporter: Tom Fonteyne > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 8.0.1.Final > > > Enable RBAC in an Wilfly domain setup. "reload --host=master" and the slaves will no longer be connected to the master -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3071) upgrade Generic JMS RA to 1.0.2.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3071?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3071: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1073354|https://bugzilla.redhat.com/show_bug.cgi?id=1073354] from MODIFIED to ON_QA > upgrade Generic JMS RA to 1.0.2.Final > ------------------------------------- > > Key: WFLY-3071 > URL: https://issues.jboss.org/browse/WFLY-3071 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2014