April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3730) Use of relative-to in path in domain mode prevents the server from starting up.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3730?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-14552 to WFCORE-3730: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3730 (was: JBEAP-14552) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Server (was: Server) Affects Version/s: (was: 7.1.0.GA) (was: 7.1.1.GA) Fix Version/s: (was: 7.1.3.GA) > Use of relative-to in path in domain mode prevents the server from starting up. > ------------------------------------------------------------------------------- > > Key: WFCORE-3730 > URL: https://issues.jboss.org/browse/WFCORE-3730 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Teresa Miyar > Assignee: Yeray Borges > > Server does not start on domain mode when setting relative-to in the path > {code:java} > <paths> > <path name="apps.log.dir" path="/apps/logs" relative-to="jboss.domain.base.dir"/> > </paths> > {code} > {code:java} > [Host Controller] 13:28:05,730 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/path=apps.log.dir' are not available: > [Host Controller] org.wildfly.management.path.jboss.domain.base.dir in context 'global'; Possible registration points for this capability: > [Host Controller] /host=master/path=* > [Host Controller] /host=master/server-config=*/path=* > [Host Controller] /path=* > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10180) CDI.current() should use the BeanManager from JNDI if available

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10180?page=com.atlassian.jira.plugin... ] Stuart Douglas closed WFLY-10180. --------------------------------- Resolution: Rejected > CDI.current() should use the BeanManager from JNDI if available > ---------------------------------------------------------------- > > Key: WFLY-10180 > URL: https://issues.jboss.org/browse/WFLY-10180 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10179) Glassfish to WildFly throw error while starting application "No ejb found with interface of type"

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-10179?page=com.atlassian.jira.plugin... ] David Lloyd closed WFLY-10179. ------------------------------ Resolution: Rejected Please direct questions such as this to the [user forums|http://wildfly.org/gethelp/]. This bug tracker is for tracking work and bugs in the code itself. Thanks! > Glassfish to WildFly throw error while starting application "No ejb found with interface of type" > -------------------------------------------------------------------------------------------------- > > Key: WFLY-10179 > URL: https://issues.jboss.org/browse/WFLY-10179 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Sana Korejo > Priority: Blocker > > Application was working fine with Glassfish 3+ but on migrating it to WildFly 8 it is throwing following error while running. Application is shown in deployments, and postgressql jar too is existing in deployments. Java 6 is used. > > JBAS014671: Failed services => { jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".INSTALL" JBAS018733: Failed to process phase INSTALL of deployment \"mywar.file.SNAPSHOT.war\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014544: No EJB found with interface of type "my.services.UserFacade" for binding my.package.RefFacade/userService"}, > JBAS014771: Services with missing/ unavailable dependencies => ["jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".weld.weldClassIntrospector is missing ["jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".beanmanager]"]} > > What can be the issue and how to fix it? > Like (0) • Reply • Share -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10180) CDI.current() should use the BeanManager from JNDI if available

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10180?page=com.atlassian.jira.plugin... ] Stuart Douglas reassigned WFLY-10180: ------------------------------------- Assignee: Stuart Douglas > CDI.current() should use the BeanManager from JNDI if available > ---------------------------------------------------------------- > > Key: WFLY-10180 > URL: https://issues.jboss.org/browse/WFLY-10180 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10180) CDI.current() should use the BeanManager from JNDI if available

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10180?page=com.atlassian.jira.plugin... ] Stuart Douglas updated WFLY-10180: ---------------------------------- Component/s: CDI / Weld > CDI.current() should use the BeanManager from JNDI if available > ---------------------------------------------------------------- > > Key: WFLY-10180 > URL: https://issues.jboss.org/browse/WFLY-10180 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10180) CDI.current() should use the BeanManager from JNDI if available

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10180?page=com.atlassian.jira.plugin... ] Stuart Douglas moved WELD-2485 to WFLY-10180: --------------------------------------------- Project: WildFly (was: Weld) Key: WFLY-10180 (was: WELD-2485) > CDI.current() should use the BeanManager from JNDI if available > ---------------------------------------------------------------- > > Key: WFLY-10180 > URL: https://issues.jboss.org/browse/WFLY-10180 > Project: WildFly > Issue Type: Bug > Reporter: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1541) local-kerberos CredentialSource does not work with IBM java

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1541?page=com.atlassian.jira.plugin.s... ] Jan Kalina edited comment on ELY-1541 at 4/5/18 5:01 PM: --------------------------------------------------------- Ok, I was wrong - we dont need any {{<local-kerberos>}} in elytron client. All you need to use kerberos as client is to use: {code} bin/jboss-cli.sh -c --no-local-auth -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.krb5.conf=/path/krb5.conf :whoami {code} When no credential is provided from CredentialSource, GSSContext will obtain it automatically and also correctly. Just need to have KRB5CCNAME env variable set for IBM JDK before: {code} export KRB5CCNAME=FILE:/tmp/krb5cc_1000 {code} This mean {{LocalKerberosCredentialSource}} should be removed (deprecated) from elytron, as it is redundant. was (Author: honza889): Ok, I was wrong - we dont need any {{<local-kerberos>}} in elytron client. All you need to use kerberos as client is to use: {code} bin/jboss-cli.sh -c --no-local-auth -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.krb5.conf=/path/krb5.conf :whoami {code} For IBM it is sufficient to set KRB5CCNAME env variable before: {code} export KRB5CCNAME=FILE:/tmp/krb5cc_1000 {code} This mean {{LocalKerberosCredentialSource}} should be removed (deprecated) from elytron, as it is redundant. > local-kerberos CredentialSource does not work with IBM java > ----------------------------------------------------------- > > Key: ELY-1541 > URL: https://issues.jboss.org/browse/ELY-1541 > Project: WildFly Elytron > Issue Type: Bug > Components: Credentials > Affects Versions: 1.2.3.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: ibm-java > > When trying to connect as with Oracle JDK, following error occure: > {code} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0 > major string: General failure, unspecified at GSSAPI level > minor string: Cannot get credential for principal default principal > {code} > -This is probably related to missing *useDefaultCcache* JAAS config (false by default):- > https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1541) local-kerberos CredentialSource does not work with IBM java

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1541?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1541: --------------------------------- Ok, I was wrong - we dont need any {{<local-kerberos>}} in elytron client. All you need to use kerberos as client is to use: {code} bin/jboss-cli.sh -c --no-local-auth -Djavax.security.auth.useSubjectCredsOnly=false -Djava.security.krb5.conf=/path/krb5.conf :whoami {code} For IBM it is sufficient to set KRB5CCNAME env variable before: {code} export KRB5CCNAME=FILE:/tmp/krb5cc_1000 {code} This mean {{LocalKerberosCredentialSource}} should be removed (deprecated) from elytron, as it is redundant. > local-kerberos CredentialSource does not work with IBM java > ----------------------------------------------------------- > > Key: ELY-1541 > URL: https://issues.jboss.org/browse/ELY-1541 > Project: WildFly Elytron > Issue Type: Bug > Components: Credentials > Affects Versions: 1.2.3.Final > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: ibm-java > > When trying to connect as with Oracle JDK, following error occure: > {code} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9990: ELY05053: Callback handler failed for unknown reason: java.lang.reflect.UndeclaredThrowableException: org.ietf.jgss.GSSException, major code: 11, minor code: 0 > major string: General failure, unspecified at GSSAPI level > minor string: Cannot get credential for principal default principal > {code} > -This is probably related to missing *useDefaultCcache* JAAS config (false by default):- > https://www.ibm.com/support/knowledgecenter/en/SSYKE2_6.0.0/com.ibm.java.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10179) Glassfish to WildFly throw error while starting application "No ejb found with interface of type"

by Sana Korejo (JIRA)

Sana Korejo created WFLY-10179: ---------------------------------- Summary: Glassfish to WildFly throw error while starting application "No ejb found with interface of type" Key: WFLY-10179 URL: https://issues.jboss.org/browse/WFLY-10179 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 8.0.0.Final Reporter: Sana Korejo Priority: Blocker Application was working fine with Glassfish 3+ but on migrating it to WildFly 8 it is throwing following error while running. Application is shown in deployments, and postgressql jar too is existing in deployments. Java 6 is used. JBAS014671: Failed services => { jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".INSTALL" JBAS018733: Failed to process phase INSTALL of deployment \"mywar.file.SNAPSHOT.war\" Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014544: No EJB found with interface of type "my.services.UserFacade" for binding my.package.RefFacade/userService"}, JBAS014771: Services with missing/ unavailable dependencies => ["jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".weld.weldClassIntrospector is missing ["jboss.deployment.unit.\"mywar.file.SNAPSHOT.war\".beanmanager]"]} What can be the issue and how to fix it? Like (0) • Reply • Share -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-63) Reorganize Bladecenter Openshift Cluster

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-63?page=com.atlassian.jira.plugin.s... ] Guilherme Baufaker Rêgo closed SWSQE-63. ---------------------------------------- Resolution: Done > Reorganize Bladecenter Openshift Cluster > ---------------------------------------- > > Key: SWSQE-63 > URL: https://issues.jboss.org/browse/SWSQE-63 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

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 April 2018