January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14292) Install Wildfly on IBM Cloud

by Muhammad Arif (Jira)

[ https://issues.redhat.com/browse/WFLY-14292?page=com.atlassian.jira.plugi... ] Muhammad Arif updated WFLY-14292: --------------------------------- Attachment: Kubernetes1.png Kubernetes2.png Kubernetes3.png Kubernetes4.png Kubernetes5.png Kubernetes6.png Kubernetes7.png Storage1.png Storage2.png Wildfly1.png Wildfly2.png WildflyVerify1.png WildflyVerify2.png WildflyVerify3.png WildflyVerify4.png WildflyVerify5.png WildflyVerify6.png > Install Wildfly on IBM Cloud > ---------------------------- > > Key: WFLY-14292 > URL: https://issues.redhat.com/browse/WFLY-14292 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Muhammad Arif > Assignee: Brian Stansberry > Priority: Trivial > Attachments: Kubernetes1.png, Kubernetes2.png, Kubernetes3.png, Kubernetes4.png, Kubernetes5.png, Kubernetes6.png, Kubernetes7.png, Storage1.png, Storage2.png, Wildfly1.png, Wildfly2.png, WildflyVerify1.png, WildflyVerify2.png, WildflyVerify3.png, WildflyVerify4.png, WildflyVerify5.png, WildflyVerify6.png > > > *Installing Wildfly on IBM Cloud* > > This document will describe how to install Wildfly on IBM Cloud using Kubernetes Service. > > *+Contents+* > # Introduction > # Provision Kubernetes Cluster > # Deploy IBM Cloud Block-Storage Plugin > # Deploy Wildfly > # Verifying the Wildfly Installation > *Introduction* > To complete this tutorial, you should have an IBM Cloud account, if you do not have one, please [register/signup|https://cloud.ibm.com/registration] here. > For installing Wildfly, we have used the Kubernetes cluster, and used the IBM Cloud Block-Storage plugin for our persistent volume. Upon the completion of this tutorial, you would have the Wildfly up and running on the Kubernetes cluster. > # Provision the Kubernetes cluster, if you have already setup one, skip to step 2. > # Deploy the IBM Cloud Block-Storage Plugin to the created cluster, if you have already done this, skip to step 3. > # Deploy the Wildfly. > *Provision Kubernetes Cluster* > * Click on the *Catalog* button on top center. Open [Catalog|https://cloud.ibm.com/catalog]. !Kubernetes1.png! > * In search catalog box, search for *Kubernetes Service* and click on it. !Kubernetes2.png! > * You are now at Create Kubernetes Cluster page, there you have the two plans to create the Kubernetes cluster, either using free plan or standard plan. > > *Option1- Using Free Plan:* > * Select Pricing Plan as “*Free*”. > * Click on *Create*. !Kubernetes3.png! > * Wait a few minutes, and then your Cloud would be ready. > > *_Note_*_: Please be careful when choosing free cluster, as your pods could be stuck at pending state due to insufficient compute and memory resources, if you face such kind of issue please increase your resource by creating them choosing the standard plan._ > > *Option2- Using Standard Plan:* > * Select Pricing Plan as “*Standard*” > * Select your Kubernetes Version as latest available or desired one by application. In our example we have set it to be ‘*1.18.14*’. > * !Kubernetes4.png! > * Select Infrastructure as “*Classic*” > * Leave Resource Group to “*Default*” > * Select Geography as “*Asia*” or your desired one. > * Select Availability as “*Single Zone*”. > _This option allows you to create the resources in either single or multi availability zones. Multi availability zone provides you the option to create the resources in more than one availability zones so in case of catastrophe it could sustain the disaster and continues to work._ > * Select Worker Zone as *Chennai 01. !Kubernetes5.png!* > * In Worker Pool, input your desired number of nodes as “*2*” > * Leave the Encrypt Local Disk option to “*On*” > * Select Master Service Endpoint to “*Both private and public endpoints*” !Kubernetes6.png! > * Give your cluster-name as “*Wildfly-Cluster*” > * Provide *tags* to your cluster and click on *Create*. > * Wait a few minutes, and then your Cloud would be ready. !Kubernetes7.png! > *Deploy IBM Cloud Block-Storage Plugin* > * Click on the *Catalog* button on top center. > * In search catalog box, search for *IBM Cloud Block Storage Plug-in* and click on it !Storage1.png! > * Select your cluster as "*Wildfly-Cluster*" > * Provide *Target Namespace* as “*wildfly-storage*”, leave *name* and *resource group* to *default* > * Click on *Install !Storage2.png!* > > *Deploy Wildfly* > * Again go to the *Catalog* and search for Wildfly. !Wildfly1.png! > * Provide the details as below. !Wildfly2.png! > * Target: *IBM Kubernetes Service* > * Method: *Helm chart* > * Kubernetes cluster: *Wildfly-Cluster*(jp-tok) > * Target namespace: *wildfly* > * Workspace: *wildfly-01-13-2021* > * Resource group: *Default* > * Click on *Parameters with Default Values*, you can set the deployment values or use the default ones, we have used the default ones in this example. > * Click on *Install*. > *Verifying the Wildfly Installation* > * Go to the *Resources List* in the Left Navigation Menu and click on ** *Kubernetes* and then *Clusters. !WildflyVerify1.png!* > * Click on your created *Wildfly-Cluster.* > * A screen would come up for your created cluster, click on *Actions,* and then *Web Terminal !WildflyVerify2.png!* > * A warning will appear asking you to install the Web Terminal, click on *Install* > * When the terminal is installed, click on the action button again and click on web terminal and type the following command in below command window. It will show you the workspaces of your cluster, you can see *Wildfly* active. > {code:java} > $ kubectl get ns{code} > !WildflyVerify3.png! > {code:java} > $ kubectl get pod –n Namespace –o wide {code} > !WildflyVerify4.png! > {code:java} > $ kubectl get service –n Namespace {code} > !WildflyVerify5.png! > Note the IP address and put it into your browser and you would see the Wildfly console would open. > !WildflyVerify6.png! > > The installation is done. Enjoy! -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14292) Install Wildfly on IBM Cloud

by Muhammad Arif (Jira)

Muhammad Arif created WFLY-14292: ------------------------------------ Summary: Install Wildfly on IBM Cloud Key: WFLY-14292 URL: https://issues.redhat.com/browse/WFLY-14292 Project: WildFly Issue Type: Component Upgrade Reporter: Muhammad Arif Assignee: Brian Stansberry *Installing Wildfly on IBM Cloud* This document will describe how to install Wildfly on IBM Cloud using Kubernetes Service. *+Contents+* # Introduction # Provision Kubernetes Cluster # Deploy IBM Cloud Block-Storage Plugin # Deploy Wildfly # Verifying the Wildfly Installation *Introduction* To complete this tutorial, you should have an IBM Cloud account, if you do not have one, please [register/signup|https://cloud.ibm.com/registration] here. For installing Wildfly, we have used the Kubernetes cluster, and used the IBM Cloud Block-Storage plugin for our persistent volume. Upon the completion of this tutorial, you would have the Wildfly up and running on the Kubernetes cluster. # Provision the Kubernetes cluster, if you have already setup one, skip to step 2. # Deploy the IBM Cloud Block-Storage Plugin to the created cluster, if you have already done this, skip to step 3. # Deploy the Wildfly. *Provision Kubernetes Cluster* * Click on the *Catalog* button on top center. Open [Catalog|https://cloud.ibm.com/catalog]. !Kubernetes1.png! * In search catalog box, search for *Kubernetes Service* and click on it. !Kubernetes2.png! * You are now at Create Kubernetes Cluster page, there you have the two plans to create the Kubernetes cluster, either using free plan or standard plan. *Option1- Using Free Plan:* * Select Pricing Plan as “*Free*”. * Click on *Create*. !Kubernetes3.png! * Wait a few minutes, and then your Cloud would be ready. *_Note_*_: Please be careful when choosing free cluster, as your pods could be stuck at pending state due to insufficient compute and memory resources, if you face such kind of issue please increase your resource by creating them choosing the standard plan._ *Option2- Using Standard Plan:* * Select Pricing Plan as “*Standard*” * Select your Kubernetes Version as latest available or desired one by application. In our example we have set it to be ‘*1.18.14*’. * !Kubernetes4.png! * Select Infrastructure as “*Classic*” * Leave Resource Group to “*Default*” * Select Geography as “*Asia*” or your desired one. * Select Availability as “*Single Zone*”. _This option allows you to create the resources in either single or multi availability zones. Multi availability zone provides you the option to create the resources in more than one availability zones so in case of catastrophe it could sustain the disaster and continues to work._ * Select Worker Zone as *Chennai 01. !Kubernetes5.png!* * In Worker Pool, input your desired number of nodes as “*2*” * Leave the Encrypt Local Disk option to “*On*” * Select Master Service Endpoint to “*Both private and public endpoints*” !Kubernetes6.png! * Give your cluster-name as “*Wildfly-Cluster*” * Provide *tags* to your cluster and click on *Create*. * Wait a few minutes, and then your Cloud would be ready. !Kubernetes7.png! *Deploy IBM Cloud Block-Storage Plugin* * Click on the *Catalog* button on top center. * In search catalog box, search for *IBM Cloud Block Storage Plug-in* and click on it !Storage1.png! * Select your cluster as "*Wildfly-Cluster*" * Provide *Target Namespace* as “*wildfly-storage*”, leave *name* and *resource group* to *default* * Click on *Install !Storage2.png!* *Deploy Wildfly* * Again go to the *Catalog* and search for Wildfly. !Wildfly1.png! * Provide the details as below. !Wildfly2.png! * Target: *IBM Kubernetes Service* * Method: *Helm chart* * Kubernetes cluster: *Wildfly-Cluster*(jp-tok) * Target namespace: *wildfly* * Workspace: *wildfly-01-13-2021* * Resource group: *Default* * Click on *Parameters with Default Values*, you can set the deployment values or use the default ones, we have used the default ones in this example. * Click on *Install*. *Verifying the Wildfly Installation* * Go to the *Resources List* in the Left Navigation Menu and click on ** *Kubernetes* and then *Clusters. !WildflyVerify1.png!* * Click on your created *Wildfly-Cluster.* * A screen would come up for your created cluster, click on *Actions,* and then *Web Terminal !WildflyVerify2.png!* * A warning will appear asking you to install the Web Terminal, click on *Install* * When the terminal is installed, click on the action button again and click on web terminal and type the following command in below command window. It will show you the workspaces of your cluster, you can see *Wildfly* active. {code:java} $ kubectl get ns{code} !WildflyVerify3.png! {code:java} $ kubectl get pod –n Namespace –o wide {code} !WildflyVerify4.png! {code:java} $ kubectl get service –n Namespace {code} !WildflyVerify5.png! Note the IP address and put it into your browser and you would see the Wildfly console would open. !WildflyVerify6.png! The installation is done. Enjoy! -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Harald Pehl commented on WFLY-14215: ------------------------------------ Looks like a HAL issue. Moving to HAL project. > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2069) JWT token validation uses int instead of long for the dates: exp (expiration) and nbf

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/ELY-2069?page=com.atlassian.jira.plugin.... ] Ilia Vassilev reassigned ELY-2069: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > JWT token validation uses int instead of long for the dates: exp (expiration) and nbf > ------------------------------------------------------------------------------------- > > Key: ELY-2069 > URL: https://issues.redhat.com/browse/ELY-2069 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Chris Dolphy > Assignee: Ilia Vassilev > Priority: Major > > JwtValidator is reading the exp and nbf field as a Java int instead of long: > [https://github.com/wildfly-security/wildfly-elytron/blob/master/auth/real...] > This means the maximum expiration date is ~January 18, 2038. Also, with Javascript a NumericDate this would be a 64-bit value. The JWT spec also leaves open the possibility of a decimal value so that should possibly be accounted for. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Harald Pehl updated WFLY-14215: ------------------------------- Component/s: (was: EJB) > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Harald Pehl reassigned WFLY-14215: ---------------------------------- Assignee: (was: Cheng Fang) > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: EJB, Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Harald Pehl commented on WFLY-14215: ------------------------------------ [~michpetrov] No, feel free to take it. > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: EJB, Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Harald Pehl (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Harald Pehl reassigned WFLY-14215: ---------------------------------- Assignee: Cheng Fang (was: Harald Pehl) > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: EJB, Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Assignee: Cheng Fang > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14215) EJB subsystem configuration page dont open

by Michal Petrov (Jira)

[ https://issues.redhat.com/browse/WFLY-14215?page=com.atlassian.jira.plugi... ] Michal Petrov commented on WFLY-14215: -------------------------------------- [~harald.pehl], are you working on this? > EJB subsystem configuration page dont open > ------------------------------------------ > > Key: WFLY-14215 > URL: https://issues.redhat.com/browse/WFLY-14215 > Project: WildFly > Issue Type: Bug > Components: EJB, Web Console > Affects Versions: 21.0.1.Final > Reporter: Anatoliy Golubev > Assignee: Harald Pehl > Priority: Major > > Internal error: > (TypeError) : this.org_jboss_hal_client_configuration_subsystem_ejb_EjbView_serviceRemoteForm.getFormItem__Ljava_lang_String_2Lorg_jboss_hal_ballroom_form_FormItem_2(...) is null -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14263) Outdated "Remote EJB invocations via JNDI - EJB client API or remote-naming project" document

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-14263?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty reassigned WFLY-14263: ------------------------------------------ Assignee: Ranabir Chakraborty (was: Cheng Fang) > Outdated "Remote EJB invocations via JNDI - EJB client API or remote-naming project" document > --------------------------------------------------------------------------------------------- > > Key: WFLY-14263 > URL: https://issues.redhat.com/browse/WFLY-14263 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Ranabir Chakraborty > Priority: Major > > This doc looks wrong: > https://docs.wildfly.org/21/Developer_Guide.html#Remote_EJB_invocations_v... > AFAICT WildFly no longer ships org.jboss:jboss-remote-naming. > There are also a number of places where that doc refers to WildFly 21 which I believe is a dynamic value that is now incorrect. It's generally better to not include specific WildFly versions in the docs, as the URL for our docs already include a version number. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 3 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 January 2021