September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2106) IBM JDK, Error Shutting Down, SecurityException: unable to instantiate Subject-based policy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2106?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2106: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1006876|https://bugzilla.redhat.com/show_bug.cgi?id=1006876] from ON_QA to VERIFIED > IBM JDK, Error Shutting Down, SecurityException: unable to instantiate Subject-based policy > ------------------------------------------------------------------------------------------- > > Key: WFLY-2106 > URL: https://issues.jboss.org/browse/WFLY-2106 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Kabir Khan > Priority: Blocker > Fix For: 8.0.0.Beta1 > > > full stacktrace: > [0m[31m02:50:22,461 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-attribute") failed - address: ([]): java.lang.SecurityException: unable to instantiate Subject-based policy > at javax.security.auth.Policy.getPolicyNoCheck(Policy.java:268) [rt.jar:1.6.0] > at javax.security.auth.Policy.getPolicy(Policy.java:219) [rt.jar:1.6.0] > at javax.security.auth.SubjectDomainCombiner$5.run(SubjectDomainCombiner.java:513) [rt.jar:1.6.0] > at java.security.AccessController.doPrivileged(AccessController.java:228) [vm.jar:] > at javax.security.auth.SubjectDomainCombiner.compatPolicy(SubjectDomainCombiner.java:509) [rt.jar:1.6.0] > at javax.security.auth.SubjectDomainCombiner.combine(SubjectDomainCombiner.java:223) [rt.jar:1.6.0] > at java.security.AccessController.getContext(AccessController.java:167) [vm.jar:] > at org.jboss.as.controller.SecurityActions$CreateCallerActions$1.getCaller(SecurityActions.java:151) -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2106) IBM JDK, Error Shutting Down, SecurityException: unable to instantiate Subject-based policy

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2106?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2106: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> made a comment on [bug 1006876|https://bugzilla.redhat.com/show_bug.cgi?id=1006876] Verified on EAP 6.2.0.ER3 > IBM JDK, Error Shutting Down, SecurityException: unable to instantiate Subject-based policy > ------------------------------------------------------------------------------------------- > > Key: WFLY-2106 > URL: https://issues.jboss.org/browse/WFLY-2106 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Kabir Khan > Priority: Blocker > Fix For: 8.0.0.Beta1 > > > full stacktrace: > [0m[31m02:50:22,461 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) JBAS014612: Operation ("read-attribute") failed - address: ([]): java.lang.SecurityException: unable to instantiate Subject-based policy > at javax.security.auth.Policy.getPolicyNoCheck(Policy.java:268) [rt.jar:1.6.0] > at javax.security.auth.Policy.getPolicy(Policy.java:219) [rt.jar:1.6.0] > at javax.security.auth.SubjectDomainCombiner$5.run(SubjectDomainCombiner.java:513) [rt.jar:1.6.0] > at java.security.AccessController.doPrivileged(AccessController.java:228) [vm.jar:] > at javax.security.auth.SubjectDomainCombiner.compatPolicy(SubjectDomainCombiner.java:509) [rt.jar:1.6.0] > at javax.security.auth.SubjectDomainCombiner.combine(SubjectDomainCombiner.java:223) [rt.jar:1.6.0] > at java.security.AccessController.getContext(AccessController.java:167) [vm.jar:] > at org.jboss.as.controller.SecurityActions$CreateCallerActions$1.getCaller(SecurityActions.java:151) -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2169) Add support to change various Undertow listener options

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2169?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2169: ------------------------------ Parent: WFLY-2055 Issue Type: Sub-task (was: Feature Request) > Add support to change various Undertow listener options > ------------------------------------------------------- > > Key: WFLY-2169 > URL: https://issues.jboss.org/browse/WFLY-2169 > Project: WildFly > Issue Type: Sub-task > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha4 > Environment: Ubuntu 12.04 LTS, openjdk-7-jdk-7u25-2.3.10-1ubuntu0.12.04.2 > Reporter: Bernd Nigmann > Assignee: Tomaz Cerar > > Undertow's default for the maximum number of HTTP parameter it parses in a GET or POST is 1000: > {noformat} > 15:05:41,276 ERROR [io.undertow.request] (default task-17) > Servlet request failed HttpServerExchange{ POST /***/*******/****}: > java.lang.IllegalStateException: UT000047: The number of > parameters exceeded the maximum of 1000 > {noformat} > In the Undertow sources (https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io...), I found this to be a configurable option: "{{MAX_PARAMETERS}}". > Please allow changing some of these Undertow options through the WildFly {{standalone.xml}}. Tomaz Cerar asked me to create a ticket for this, based on the referenced forum thread. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2169) Add support to change various Undertow listener options

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2169?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2169: ------------------------------ Summary: Add support to change various Undertow listener options (was: Add support to change various Undertow options through WildFly in standalone.xml) > Add support to change various Undertow listener options > ------------------------------------------------------- > > Key: WFLY-2169 > URL: https://issues.jboss.org/browse/WFLY-2169 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha4 > Environment: Ubuntu 12.04 LTS, openjdk-7-jdk-7u25-2.3.10-1ubuntu0.12.04.2 > Reporter: Bernd Nigmann > Assignee: Tomaz Cerar > > Undertow's default for the maximum number of HTTP parameter it parses in a GET or POST is 1000: > {noformat} > 15:05:41,276 ERROR [io.undertow.request] (default task-17) > Servlet request failed HttpServerExchange{ POST /***/*******/****}: > java.lang.IllegalStateException: UT000047: The number of > parameters exceeded the maximum of 1000 > {noformat} > In the Undertow sources (https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io...), I found this to be a configurable option: "{{MAX_PARAMETERS}}". > Please allow changing some of these Undertow options through the WildFly {{standalone.xml}}. Tomaz Cerar asked me to create a ticket for this, based on the referenced forum thread. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2177) org.jboss.logmanager module needs dependency on javax.api for the SocketFactory

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2177?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2177: ----------------------------------------------- Ondrej Lukas <olukas(a)redhat.com> made a comment on [bug 1013169|https://bugzilla.redhat.com/show_bug.cgi?id=1013169] Same issue is in audit-log in syslog-handler. Audit log has P0 and it could be customer problem in Beta, because it couldn't be set and used by customer. For that reason it is candidate on Beta blocker. PR sent by James solves this issue. > org.jboss.logmanager module needs dependency on javax.api for the SocketFactory > ------------------------------------------------------------------------------- > > Key: WFLY-2177 > URL: https://issues.jboss.org/browse/WFLY-2177 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > > The {{javax.net.SocketFactory}} is part of the {{javax.api}} module. Since the {{org.jboss.logmanager}} uses this for the syslog handler on TCP and SSL connections, a dependency on the module is needed. -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2027) EE Default DataSource is not working

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2027?page=com.atlassian.jira.plugin.... ] Eduardo Martins commented on WFLY-2027: --------------------------------------- WFLY-2158 PR includes fix for this issue. > EE Default DataSource is not working > ------------------------------------ > > Key: WFLY-2027 > URL: https://issues.jboss.org/browse/WFLY-2027 > Project: WildFly > Issue Type: Bug > Components: ConfigAdmin, Domain Management, EE, JCA, JPA / Hibernate, Web Console > Affects Versions: 8.0.0.Alpha4 > Reporter: Lincoln Baxter III > > The EE spec states that a default datasource must be supplied under: java:comp/DefaultDataSource, and if none is specified by the @Resource or persistence.xml, it must be assumed: > {code}EE 5.19 > The Java EE Platform requires that a Java EE Product Provider provide a database > in the operational environment (see Section EE.2.6, “Database”). The Java EE > Product Provider must also provide a preconfigured, default data source for use by > the application in accessing this database. > The Java EE Product Provider must make the default data source accessible to > the application under the JNDI name java:comp/DefaultDataSource. > The Application Component Provider or Deployer may explicitly bind a > DataSource resource reference to the default data source using the lookup element > of the Resource annotation or the lookup-name element of the resource-ref > deployment descriptor element. For example, > @Resource(lookup="java:comp/DefaultDataSource") > DataSource myDS; > In the absence of such a binding, the mapping of the reference will default to > the product's default data source. > For example, the following will map to a preconfigured data source for the > product's default database: > @Resource > DataSource myDS;{code} > This, isn't working however: > {code} > <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/persistence/persis..."> > <persistence-unit name="default" transaction-type="JTA"> > </persistence-unit> > </persistence>{code} > Results in: > {code} > 10:41:31,002 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 50) MSC000001: Failed to start service jboss.persistenceunit."jpa-standard.war#default": org.jboss.msc.service.StartException in service jboss.persistenceunit."jpa-standard.war#default": org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:134) [wildfly-jpa-8.0.0.Alpha4.jar:8.0.0.Alpha4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:98) > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:66) > at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:193) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:88) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131) > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1844) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1802) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:844) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) > at org.jboss.as.jpa.hibernate4.management.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:115) [wildfly-jpa-8.0.0.Alpha4.jar:8.0.0.Alpha4] > ... 4 more > 10:41:31,010 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jpa-standard.war#default\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jpa-standard.war#default\": org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set"}} > {code} > Additionally, actually specifying the expected JDNI name of the default DS like this: > {code} <persistence-unit name="default" transaction-type="JTA"> > <jta-data-source>java:comp/DefaultDataSource</jta-data-source> > <exclude-unlisted-classes>false</exclude-unlisted-classes> > </persistence-unit>{code} > Results in this: > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.naming.context.java.module.jpa-standard.jpa-standard.DefaultDataSource (missing) dependents: [service jboss.persistenceunit."jpa-standard.war#default".__FIRST_PHASE__] > service jboss.persistenceunit."jpa-standard.war#default".__FIRST_PHASE__ (missing) dependents: [service jboss.deployment.unit."jpa-standard.war".POST_MODULE] > {code} -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2183: ------------------------------------------ Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1013521) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-2183: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1013521 > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Heiko Braun reassigned WFLY-2183: --------------------------------- Assignee: Brian Stansberry (was: Heiko Braun) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > -- 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

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] Heiko Braun commented on WFLY-2183: ----------------------------------- It's a server side issue. The attributes are flagged as "writable=false": {noformat} [domain@localhost:9999 /] /profile=default/subsystem=logging/custom-handler=*:read-resource-description(access-control=trim-descriptions, operations=true){role=administrator} { "outcome" => "success", "result" => [{ "address" => [ ("profile" => "default"), ("subsystem" => "logging"), ("custom-handler" => "*") ], "outcome" => "success", "result" => { "description" => undefined, "attributes" => undefined, "operations" => undefined, "children" => {}, "access-control" => { "default" => { "read" => true, "write" => true, "attributes" => { "enabled" => { "read" => true, "write" => true }, "module" => { "read" => true, "write" => false }, "class" => { "read" => true, "write" => false }, "properties" => { "read" => true, "write" => true }, "formatter" => { "read" => true, "write" => true }, "filter-spec" => { "read" => true, "write" => true }, "level" => { "read" => true, "write" => true }, "name" => { "read" => true, "write" => false }, "encoding" => { "read" => true, "write" => true }, "filter" => { "read" => true, "write" => true } }, "operations" => { "read-children-names" => {"execute" => true}, "read-operation-description" => {"execute" => true}, "remove" => {"execute" => true}, "update-properties" => {"execute" => true}, "read-resource-description" => {"execute" => true}, "enable" => {"execute" => true}, "read-resource" => {"execute" => true}, "change-log-level" => {"execute" => true}, "add" => {"execute" => true}, "read-attribute" => {"execute" => true}, "whoami" => {"execute" => true}, "read-children-types" => {"execute" => true}, "read-operation-names" => {"execute" => true}, "undefine-attribute" => {"execute" => true}, "read-children-resources" => {"execute" => true}, "disable" => {"execute" => true}, "write-attribute" => {"execute" => true} } }, "exceptions" => {} } } }] } {noformat} > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.CR1 > > -- 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

12 years, 9 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 September 2013