July 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2011) jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2011?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2011: ----------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 1004856|https://bugzilla.redhat.com/show_bug.cgi?id=1004856] from NEW to ASSIGNED > jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element > ------------------------------------------------------------------------------------- > > Key: WFLY-2011 > URL: https://issues.jboss.org/browse/WFLY-2011 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Beta1 > Reporter: Wolf-Dieter Fink > Assignee: Stuart Douglas > Labels: ejb-jar.xml > Fix For: 8.0.0.CR1 > > > If beans of an application are marked as clustered by using the jboss-ejb3.xml DD the behaviour is not consistent. > From the XSD the <ejb-name> element can not be added multiple times. > And the following configuration will be not valid: > <assembly-descriptor> > <c:clustering> > <ejb-name>Bean1</ejb-name> > <ejb-name>Bean2</ejb-name> > <c:clustered>true</c:clustered> > </c:clustering> > </assembly-descriptor> > The parser should throw an Exception and the application should not be deployed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-19) Properly cancel active mgmt operation on channel close

by Emanuel Muckenhuber (JIRA)

[ https://issues.jboss.org/browse/WFCORE-19?page=com.atlassian.jira.plugin.... ] Emanuel Muckenhuber resolved WFCORE-19. --------------------------------------- Resolution: Done > Properly cancel active mgmt operation on channel close > ------------------------------------------------------ > > Key: WFCORE-19 > URL: https://issues.jboss.org/browse/WFCORE-19 > Project: WildFly Core > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Priority: Critical > Fix For: 1.0.0.Alpha4 > > > Active mgmt operation don't get properly cancelled if there is no associated pending request and the remoting channel gets closed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3686) "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final

by Lars Michaelis (JIRA)

[ https://issues.jboss.org/browse/WFLY-3686?page=com.atlassian.jira.plugin.... ] Lars Michaelis edited comment on WFLY-3686 at 7/29/14 6:45 AM: --------------------------------------------------------------- Thank you! I will look for it. edit: {code}<server-identities> <ssl protocol="TLS"> <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx" provider="PKCS12"/> </ssl> </server-identities>{code} does it! was (Author: larmic): Thank you! I will look for it. > "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final > --------------------------------------------------------------------------------------- > > Key: WFLY-3686 > URL: https://issues.jboss.org/browse/WFLY-3686 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Lars Michaelis > Assignee: Darran Lofthouse > Fix For: 8.2.0.CR1 > > > Up to now I am using a JKS file to activate SSL. > This works > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="mykeystore.jks" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > This does not work: > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > Exception is > {code}Caused by: java.io.IOException: Invalid keystore format > at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) [rt.jar:1.7.0_55] > at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) [rt.jar:1.7.0_55] > at java.security.KeyStore.load(KeyStore.java:1214) [rt.jar:1.7.0_55] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:113) > ... 6 more{code} > WFLY-2229 says PKCS12 is supported. I found no way to specify a keystore format in documentation (https://docs.jboss.org/author/display/WFLY8/Detailed+Configuration) . Is it correct? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3686) "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final

by Lars Michaelis (JIRA)

[ https://issues.jboss.org/browse/WFLY-3686?page=com.atlassian.jira.plugin.... ] Lars Michaelis commented on WFLY-3686: -------------------------------------- Thank you! I will look for it. > "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final > --------------------------------------------------------------------------------------- > > Key: WFLY-3686 > URL: https://issues.jboss.org/browse/WFLY-3686 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Lars Michaelis > Assignee: Darran Lofthouse > Fix For: 8.2.0.CR1 > > > Up to now I am using a JKS file to activate SSL. > This works > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="mykeystore.jks" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > This does not work: > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > Exception is > {code}Caused by: java.io.IOException: Invalid keystore format > at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) [rt.jar:1.7.0_55] > at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) [rt.jar:1.7.0_55] > at java.security.KeyStore.load(KeyStore.java:1214) [rt.jar:1.7.0_55] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:113) > ... 6 more{code} > WFLY-2229 says PKCS12 is supported. I found no way to specify a keystore format in documentation (https://docs.jboss.org/author/display/WFLY8/Detailed+Configuration) . Is it correct? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3686) "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3686?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved WFLY-3686. ------------------------------------ Fix Version/s: 8.2.0.CR1 Resolution: Rejected For configuration issues please also consult the schemas included in the distribution, in this case you need to add a 'provider' attribute to the keystore element - this defaults to JKS. > "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final > --------------------------------------------------------------------------------------- > > Key: WFLY-3686 > URL: https://issues.jboss.org/browse/WFLY-3686 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: 8.1.0.Final > Reporter: Lars Michaelis > Assignee: Darran Lofthouse > Fix For: 8.2.0.CR1 > > > Up to now I am using a JKS file to activate SSL. > This works > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="mykeystore.jks" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > This does not work: > {code}<server-identities> > <ssl protocol="TLS"> > <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx"/> > </ssl> > </server-identities>{code} > Exception is > {code}Caused by: java.io.IOException: Invalid keystore format > at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) [rt.jar:1.7.0_55] > at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) [rt.jar:1.7.0_55] > at java.security.KeyStore.load(KeyStore.java:1214) [rt.jar:1.7.0_55] > at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:113) > ... 6 more{code} > WFLY-2229 says PKCS12 is supported. I found no way to specify a keystore format in documentation (https://docs.jboss.org/author/display/WFLY8/Detailed+Configuration) . Is it correct? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3680) Port jboss-as-txn_1_5.xsd schema from EAP to WildFly

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-3680?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-3680: -------------------------------- Assignee: Stefano Maestri (was: Tom Jenkinson) > Port jboss-as-txn_1_5.xsd schema from EAP to WildFly > ---------------------------------------------------- > > Key: WFLY-3680 > URL: https://issues.jboss.org/browse/WFLY-3680 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Darran Lofthouse > Assignee: Stefano Maestri > Priority: Blocker > Fix For: 9.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3686) "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final

by Lars Michaelis (JIRA)

Lars Michaelis created WFLY-3686: ------------------------------------ Summary: "Invalid keystore format" IOException when using PKCS12 keystore in Wildfly 8.1.0.Final Key: WFLY-3686 URL: https://issues.jboss.org/browse/WFLY-3686 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 8.1.0.Final Reporter: Lars Michaelis Assignee: Darran Lofthouse Up to now I am using a JKS file to activate SSL. This works {code}<server-identities> <ssl protocol="TLS"> <keystore path="mykeystore.jks" relative-to="jboss.server.config.dir" keystore-password="xxx"/> </ssl> </server-identities>{code} This does not work: {code}<server-identities> <ssl protocol="TLS"> <keystore path="keystore.p12" relative-to="jboss.server.config.dir" keystore-password="xxx"/> </ssl> </server-identities>{code} Exception is {code}Caused by: java.io.IOException: Invalid keystore format at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:650) [rt.jar:1.7.0_55] at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:55) [rt.jar:1.7.0_55] at java.security.KeyStore.load(KeyStore.java:1214) [rt.jar:1.7.0_55] at org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:113) ... 6 more{code} WFLY-2229 says PKCS12 is supported. I found no way to specify a keystore format in documentation (https://docs.jboss.org/author/display/WFLY8/Detailed+Configuration) . Is it correct? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5409) CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5409?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5409: ---------------------------------------------- Dominik Pospisil <dpospisi(a)redhat.com> changed the Status of [bug 900262|https://bugzilla.redhat.com/show_bug.cgi?id=900262] from ASSIGNED to CLOSED > CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf > ----------------------------------------------------------------------------------------------- > > Key: AS7-5409 > URL: https://issues.jboss.org/browse/AS7-5409 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jan Martiska > Assignee: Brian Stansberry > Fix For: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > > > Try running EAP domain mode like this: > {noformat} > bin/domain.sh -Djava.net.preferIPv4Stack=false -bmanagement=::1 > {noformat} > It will fail: > {noformat} > [Host Controller] 09:40:49,647 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management > [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1] > [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > [Host Controller] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > {noformat} > Other interfaces work and can be bound to ipv6, just 'management' does not. (In standalone mode, this issue is not present.) > Blocks testing of Admin console,Native+HTTP interfaces in domain mode in IPv6, not marking as blocker because workaround exists. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2646) Expose patch description through mgmt API

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-2646?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky commented on WFLY-2646: ----------------------------------------- Actually, as part of WFLY-3614 I added patch-info operation which returns a brief info of an applied patch specified with the patch-id parameter. The operation also optionally accepts a boolean parameter 'verbose', which if true will extend the returned info with details about layer/add-on patches included into the patch. > Expose patch description through mgmt API > ----------------------------------------- > > Key: WFLY-2646 > URL: https://issues.jboss.org/browse/WFLY-2646 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Patching > Affects Versions: 8.0.0.CR1 > Reporter: Emanuel Muckenhuber > Fix For: 9.0.0.CR1 > > > It should be possible to view the description of an installed patch through the mgmt API (maybe patch history). The information is stored as part of the backed up patch.xml. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3614) enhance patch command to display applied patch's description

by Alexey Loubyansky (JIRA)

[ https://issues.jboss.org/browse/WFLY-3614?page=com.atlassian.jira.plugin.... ] Alexey Loubyansky updated WFLY-3614: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly-core/pull/63 > enhance patch command to display applied patch's description > ------------------------------------------------------------ > > Key: WFLY-3614 > URL: https://issues.jboss.org/browse/WFLY-3614 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Patching > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > There is a demand to enhance the patch cli command to show descriptions of the patches that have been applied to the identity. E.g. patch info patch-id -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 July 2014