February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1914) S3_PING doesn't work with S3 buckets created in Frankfurt region

by Gleb Leonov (JIRA)

Gleb Leonov created JGRP-1914: --------------------------------- Summary: S3_PING doesn't work with S3 buckets created in Frankfurt region Key: JGRP-1914 URL: https://issues.jboss.org/browse/JGRP-1914 Project: JGroups Issue Type: Bug Reporter: Gleb Leonov Assignee: Bela Ban I tried to use S3_PING with access and secret key pair. However, I got 400 (Bad Request) error. After some investigation, I found that modern S3 buckets created in Frankfurt needs amazon v4 authentication, which needs hmac-sha256. But now S3_PING supports only hmac-sha1, so I see no way to use S3_PING with buckets in Frankfurt region. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4324) While starting Jboss AS getting IllegalStateException.

by ANKUSH NIKHAR (JIRA)

[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ] ANKUSH NIKHAR commented on WFLY-4324: ------------------------------------- Any one can comment on this? > While starting Jboss AS getting IllegalStateException. > ------------------------------------------------------ > > Key: WFLY-4324 > URL: https://issues.jboss.org/browse/WFLY-4324 > Project: WildFly > Issue Type: Bug > Environment: Java with 1.8 v and JBOS 7 > Reporter: ANKUSH NIKHAR > > Hi, > I am facing issue when I am trying to deploy web service on Jboss 7 and using jdk 1.8 version. Below are the sample log : > This issue does not impact the processing of my code execution. Is this just warning or will it harm in future. > I am migrating my project from jdk1.7 to 1.8. > When I try to deploy WS with jdk1.7, I didn't get such error. > 18:56:01,032 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015852: Could not index class sun/applet/AppletPanel.class at /D:/Test Eclipse/Migration Eclipse/Mig Workspace/CDLibrary/CDLibrary-test/content/InMemory.war/WEB-INF/lib/tools.jar: java.lang.IllegalStateException: Unknown tag! pos=1006 poolCount = 1018 > at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:606) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.jandex.Indexer.index(Indexer.java:640) [jandex-1.0.3.Final-redhat-2.jar:1.0.3.Final-redhat-2] > at org.jboss.as.server.deployment.annotation.ResourceRootIndexer.indexResourceRoot(ResourceRootIndexer.java:100) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.annotation.AnnotationIndexProcessor.deploy(AnnotationIndexProcessor.java:51) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_31] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_31] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path

by SBS JIRA Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ] SBS JIRA Integration updated WFLY-4338: --------------------------------------- Forum Reference: https://developer.jboss.org/message/919701#919701 > JConsole script builds wrong path > --------------------------------- > > Key: WFLY-4338 > URL: https://issues.jboss.org/browse/WFLY-4338 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 8.2.0.Final > Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2) > Reporter: André Lemos > Assignee: Kabir Khan > Priority: Trivial > Labels: bash, jconsole, wildfly > Attachments: jconsole.patch > > > The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done. > The path, under mac is: > {{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}} > So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4338) JConsole script builds wrong path

by Abhijit Sarkar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4338?page=com.atlassian.jira.plugin.... ] Abhijit Sarkar commented on WFLY-4338: -------------------------------------- Same issue discussed here, I was going to create a JIRA, then saw this one already opened: https://developer.jboss.org/message/919724 > JConsole script builds wrong path > --------------------------------- > > Key: WFLY-4338 > URL: https://issues.jboss.org/browse/WFLY-4338 > Project: WildFly > Issue Type: Bug > Components: JMX > Affects Versions: 8.2.0.Final > Environment: Linux (Ubuntu 14.10) and Mac OS X Yosemite (10.10.2) > Reporter: André Lemos > Assignee: Kabir Khan > Priority: Trivial > Labels: bash, jconsole, wildfly > Attachments: jconsole.patch > > > The path built by the jconsole.sh script is incorrect, and as a result, when calling {{service:jmx:http-remoting-jmx://{insert server ip here}:9990}} is probably never recognized and the connection is never done. > The path, under mac is: > {{/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/bin/jconsole -J-Djava.class.path=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/jconsole.jar:/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/lib/tools.jar:"/Users/user/Documents/playground/wild/wildfly-8.2.0.Final"/bin/client/jboss-cli-client.jar}} > So, there are " on the path for the jboss-cli-client.jar. which breaks things. This problem happens with both Linux and Mac. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4381) Update JBeret to 1.1.0.Beta1

by Cheng Fang (JIRA)

Cheng Fang created WFLY-4381: -------------------------------- Summary: Update JBeret to 1.1.0.Beta1 Key: WFLY-4381 URL: https://issues.jboss.org/browse/WFLY-4381 Project: WildFly Issue Type: Component Upgrade Components: Batch Affects Versions: 9.0.0.Alpha1 Reporter: Cheng Fang Assignee: James Perkins Need to update to jberet-core 1.1.0.Beta1, which was released on 2/23/2015: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12314557&versi... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-103) Add Full Kerberos Support

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-103?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-103: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Add Full Kerberos Support > ------------------------- > > Key: WFCORE-103 > URL: https://issues.jboss.org/browse/WFCORE-103 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Labels: management_security, > Fix For: 1.0.0.Beta1 > > > There are a number of steps required to full add Kerberos support - this is a top level tracking task to be resolved once all steps are complete. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-54) Add Keycloak authentication/authorization to http management endpoint

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-54?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-54: ----------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Add Keycloak authentication/authorization to http management endpoint > --------------------------------------------------------------------- > > Key: WFCORE-54 > URL: https://issues.jboss.org/browse/WFCORE-54 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Stan Silvert > Assignee: Stan Silvert > Fix For: 1.0.0.Beta1 > > > This is here to track the core changes needed for WFLY-3591. See that jira for details. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-25) Windows PowerShell scripts in bin

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-25?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFCORE-25: ----------------------------------- Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Windows PowerShell scripts in bin > --------------------------------- > > Key: WFCORE-25 > URL: https://issues.jboss.org/browse/WFCORE-25 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > Add .psh scripts that match the functionality of our .sh scripts. Leave the .bat scripts in their current limited-functionality form for people still on XP, but use PowerShell as the recommended Windows scripting language. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-240) We need something similar to StandardConfigsXMLValidationUnitTestCase in Core

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-240?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-240: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > We need something similar to StandardConfigsXMLValidationUnitTestCase in Core > ----------------------------------------------------------------------------- > > Key: WFCORE-240 > URL: https://issues.jboss.org/browse/WFCORE-240 > Project: WildFly Core > Issue Type: Feature Request > Components: Test Suite > Reporter: Darran Lofthouse > Assignee: Tomaz Cerar > Fix For: 1.0.0.Beta1 > > > One feature of this test is that it validates that schemas are correct according to the schema schema, presently we only find out about errors in schemas when the wildfly testsuite is executed. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-137) Add Kerberos tests to domain-management module

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-137?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-137: ------------------------------------ Fix Version/s: 1.0.0.Beta1 (was: 1.0.0.Alpha19) > Add Kerberos tests to domain-management module > ---------------------------------------------- > > Key: WFCORE-137 > URL: https://issues.jboss.org/browse/WFCORE-137 > Project: WildFly Core > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 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 February 2015