September 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3351) WildFly self-monitoring (history storage + REST API + web console plugin)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-3351?page=com.atlassian.jira.plugin.... ] James Perkins reassigned WFLY-3351: ----------------------------------- Assignee: (was: James Perkins) > WildFly self-monitoring (history storage + REST API + web console plugin) > ------------------------------------------------------------------------- > > Key: WFLY-3351 > URL: https://issues.jboss.org/browse/WFLY-3351 > Project: WildFly > Issue Type: Feature Request > Components: Logging > Reporter: Ondrej Zizka > Priority: Optional > > Would be nice if WildFly had it's optional own submodule which would monitor the AS, store the data, and allow it's retrieval later through REST API. Also, the console could have a plugin to read and display these data. > This was discussed some time ago as one of requirements by different parties - JON, JBDS, end users. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5340) Unable to specify module when specifying custom JACC policy class.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-5340?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-5340: ----------------------------------------------- Bartek Spyrko-Smietanko <bspyrkos(a)redhat.com> changed the Status of [bug 1263336|https://bugzilla.redhat.com/show_bug.cgi?id=1263336] from NEW to ASSIGNED > Unable to specify module when specifying custom JACC policy class. > ------------------------------------------------------------------ > > Key: WFLY-5340 > URL: https://issues.jboss.org/browse/WFLY-5340 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.0.0.Beta2 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 10.0.0.CR1 > > > It is currently possible to specify the 'javax.security.jacc.policy.provider' system property, however it is not possible to specify a module. > From the JACC specification: - > _For each JRE of a J2EE 1.4 or later version Java EE application server, if the > system property > “javax.security.jacc.policy.provider > ” is defined, > the application server must construct an > instance of the class identified by the > system property, confirm that the > resulting object is an instance of > java.security.Policy, > and set, by calling the > java.security.Policy.setPolicy > method, the resulting object as the > corresponding Policy object u > sed by the JRE. _ > The specification only specifies that the system property identifies the class, it does not specify how. > In it's simplest form we should assume this is just a class name, in a more complex form we should allow the module to be specified. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2982) refactor two phase persistence unit services (PhaseOnePersistenceUnitServiceImpl + PersistenceUnitServiceImpl) into one service

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2982?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-2982: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > refactor two phase persistence unit services (PhaseOnePersistenceUnitServiceImpl + PersistenceUnitServiceImpl) into one service > ------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2982 > URL: https://issues.jboss.org/browse/WFLY-2982 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 8.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > > Related feedback from https://github.com/wildfly/wildfly/pull/4722: > {quote} > This is asymetrical, so if this service , and phase one are stopped, and then phase 1 is started again, phase 2 will appear started. The side effects seem minor though > {quote} > {quote} > We have a long term goal to somehow verify every service can be stopped and started with the expected effect. Right now many of our services are not restartable which makes potential new features like partial deployment standby hard to achieve. So Im just offering pointers whenever I see lifecycle symmetry issues. > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3853) Cache PersistenceProviders within the same deployment

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3853?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-3853: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > Cache PersistenceProviders within the same deployment > ----------------------------------------------------- > > Key: WFLY-3853 > URL: https://issues.jboss.org/browse/WFLY-3853 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > > See wildfly-dev ml discussion [http://lists.jboss.org/pipermail/wildfly-dev/2014-September/002984.html] about calls to PersistenceProviderResolver.getPersistenceProviders() should return a cached list. The cache should be per deployment. > We can probably reuse our PersistenceProviderResolverImpl.persistenceProviderPerClassLoader map, just need to be careful that addDeploymentSpecificPersistenceProvider() is called early before any calls to getPersistenceProviders(). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5319) fix org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase.test_negativeTxTimeoutVerifyReaperThreadCanceledTxTest failure

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-5319?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-5319: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > fix org.jboss.as.test.integration.jpa.mockprovider.txtimeout.TxTimeoutTestCase.test_negativeTxTimeoutVerifyReaperThreadCanceledTxTest failure > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5319 > URL: https://issues.jboss.org/browse/WFLY-5319 > Project: WildFly > Issue Type: Feature Request > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > > https://gist.github.com/scottmarlow/6409290362f35f2d1320 contains the error exception -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5425) http-listener requires 'https' socket-binding, part 2

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-5425?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-5425: ------------------------------ Fix Version/s: 9.0.0.Beta2 > http-listener requires 'https' socket-binding, part 2 > ----------------------------------------------------- > > Key: WFLY-5425 > URL: https://issues.jboss.org/browse/WFLY-5425 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Vsevolod Golovanov > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta2 > > > Continuing WFLY-2836. > Is there a way to override {{http-listener}}'s {{redirect-socket}} attribute default value ("https") to be null? > {quote}This is just default value, looking at the downside of not having default value for redirect-socket would be that people would not configure it, which would result in problems when having apps that require secure transport.{quote} > Our app doesn't require secure transport. > {code}redirect-socket=""{code} > results in > {noformat} > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[956,166] > Message: "JBAS014704: '' is an invalid value for parameter redirect-socket. Values must have a minimum length of 1 characters" > {noformat} > This: > {code}redirect-socket="null"{code} > treats it literally: > {noformat} > ]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.undertow.listener.someapp-http-listener is missing [jboss.binding.null]"]} > {noformat} > So we're forced to have a https socket-binding. Which is not a "just define some binding" problem. It's a "negotiate with customers&sysadmins/document it/provide options to configure it" problem. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-300) Absence of key-store-credential NPEs

by Kabir Khan (JIRA)

Kabir Khan created ELY-300: ------------------------------ Summary: Absence of key-store-credential NPEs Key: ELY-300 URL: https://issues.jboss.org/browse/ELY-300 Project: WildFly Elytron Issue Type: Bug Reporter: Kabir Khan Assignee: Darran Lofthouse Fix For: 1.1.0.Alpha1 Trying to parse {code} <authentication-client xmlns="urn:elytron:1.0"> <key-stores> <key-store name="test" type="PasswordFile"> <file name="keystore/xml-client-keystore-credential-test.keystore"/>  </key-store> </key-stores> </authentication-client> {code} I end up with {code} java.lang.NullPointerException at org.wildfly.security.auth.client.ElytronXmlParser$AbstractKeyStoreFactory.create(ElytronXmlParser.java:1082) at org.wildfly.security.auth.client.ElytronXmlParser$AbstractKeyStoreFactory.create(ElytronXmlParser.java:1067) at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseKeyStoreRefType$115(ElytronXmlParser.java:709) at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$4/1929600551.create(Unknown Source) at org.wildfly.security.auth.client.KeyStoreEntrySecurityFactory.create(KeyStoreEntrySecurityFactory.java:47) at org.wildfly.security.auth.client.KeyStoreEntrySecurityFactory.create(KeyStoreEntrySecurityFactory.java:30) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRuleType$106(ElytronXmlParser.java:425) at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$5/1053782781.create(Unknown Source) at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRuleType$113(ElytronXmlParser.java:474) at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$6/2012232625.create(Unknown Source) at org.wildfly.security.auth.client.ElytronXmlParser.lambda$parseAuthenticationClientRulesType$88(ElytronXmlParser.java:242) at org.wildfly.security.auth.client.ElytronXmlParser$$Lambda$7/627150481.create(Unknown Source) at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:45) at org.wildfly.security.auth.client.XmlClientKeyStoreCredentialTest.testKeystoreCredential(XmlClientKeyStoreCredentialTest.java:110) {code} This appears to be because the passwordFactory is only instantiated when parsing the key-store-credential element -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2858) JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2858?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-2858: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > JPA doesn't parse for "urn:jboss:jpa" namespace in jboss-all.xml > ---------------------------------------------------------------- > > Key: WFLY-2858 > URL: https://issues.jboss.org/browse/WFLY-2858 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 8.0.0.CR1 > Reporter: Radoslav Husar > Assignee: Scott Marlow > Priority: Minor > > Looks like the parser is only parsing for "http://www.jboss.com/xml/ns/javaee" and never for "urn:jboss:jpa". This makes the schema less useful. > https://github.com/wildfly/wildfly/blob/master/build/src/main/resources/d... > Example file: > https://github.com/wildfly/wildfly/blob/master/testsuite/integration/basi... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2387) CDI injection in entity listeners failing

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2387?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-2387: ------------------------------- Fix Version/s: (was: 10.0.0.Final) > CDI injection in entity listeners failing > ----------------------------------------- > > Key: WFLY-2387 > URL: https://issues.jboss.org/browse/WFLY-2387 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Class Loading, JPA / Hibernate > Affects Versions: 8.0.0.Beta1 > Reporter: Emond Papegaaij > Assignee: Scott Marlow > Attachments: TEST-org.jboss.as.test.integration.ee.injection.support.jpa.EntityListenerInjectionSupportTestCase.xml > > > When trying to use CDI injection in JPA entity listeners, deployment fails with the following exception: > {code} > 16:16:37,448 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 15) MSC000001: Failed to start service jboss.persistenceunit."inject-ear.ear#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."inject-ear.ear#primary": java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:169) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) > at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_25] > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:463) [wildfly-security-manager-1.0.0.Beta3.jar:1.0.0.Beta3] > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:178) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] > Caused by: java.lang.IllegalStateException: JBAS016071: Singleton not set for org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader@4eeb95dc. This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:75) > at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:128) > at org.jboss.weld.Container.instance(Container.java:65) > at org.jboss.weld.manager.BeanManagerImpl.getBeans(BeanManagerImpl.java:563) > at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:90) > at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:358) > at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:369) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:72) > at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:60) > at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:66) > at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) > at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:64) > at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:90) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:82) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory$BeanMetaData.<init>(BeanManagerListenerFactory.java:71) > at org.hibernate.jpa.event.internal.jpa.BeanManagerListenerFactory.buildListener(BeanManagerListenerFactory.java:57) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.resolveCallbacks(LegacyCallbackProcessor.java:168) > at org.hibernate.jpa.event.internal.jpa.LegacyCallbackProcessor.processCallbacksForEntity(LegacyCallbackProcessor.java:71) > at org.hibernate.jpa.event.spi.JpaIntegrator.integrate(JpaIntegrator.java:150) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1837) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:854) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:847) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:396) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:846) > at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:151) > ... 8 more > {code} > I've created a small showcase of the problem: https://github.com/papegaaij/listener-injection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5432) Wildfly SOAP webservice causes JVM crash

by Davide Marchetti (JIRA)

[ https://issues.jboss.org/browse/WFLY-5432?page=com.atlassian.jira.plugin.... ] Davide Marchetti updated WFLY-5432: ----------------------------------- Priority: Blocker (was: Major) > Wildfly SOAP webservice causes JVM crash > ---------------------------------------- > > Key: WFLY-5432 > URL: https://issues.jboss.org/browse/WFLY-5432 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.1.Final, 10.0.0.CR2 > Environment: Tested on Mac OSX 10.10.2, jdk 1.8.60, wildfly 9.0.1. Final / 10.cr2 > Also tested on Centos 6.5, jdk 1.7.51, wildfly 9.0.1. Final > Reporter: Davide Marchetti > Assignee: Alessio Soldano > Priority: Blocker > Labels: crash, jvm, soap, webservice > Attachments: SOAPTest.war > > > The JVM crashes with either a sigsegv or sigbus error when performing a SOAP load test. > The error printed is: > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f5da922afb8, pid=75645, tid=140039627204352 > # > # JRE version: OpenJDK Runtime Environment (7.0_51-b02) (build 1.7.0_51-mockbuild_2014_01_15_01_39-b00) > # Java VM: OpenJDK 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # J org.apache.cxf.message.ExchangeImpl.get(Ljava/lang/Class;)Ljava/lang/Object; > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > > # > # If you would like to submit a bug report, please include > # instructions on how to reproduce the bug and visit: > # 15:56:03,314 INFO [stdout] (default task-17) Submitted order request received with transId: <XXXXX>, opId: <SCO>, ... > http://icedtea.classpath.org/bugzilla > # > The webservice does nothing, just a System.out.print("xxxxx"). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 September 2015