February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-140) Switch the build to Java 8

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-140?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-140. ---------------------------------- Resolution: Done > Switch the build to Java 8 > -------------------------- > > Key: ELY-140 > URL: https://issues.jboss.org/browse/ELY-140 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-126) Credential verification to realm API

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-126?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-126: ------------------------------------ Assignee: David Lloyd > Credential verification to realm API > ------------------------------------ > > Key: ELY-126 > URL: https://issues.jboss.org/browse/ELY-126 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI, Realms > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Alpha1 > > > Some realms may not be able to acquire credentials. These realms will need a verification API (not like the old verification API though). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-145) Digest-MD5 - missing rspauth and bad encryption key

by Jan Kalina (JIRA)

Jan Kalina created ELY-145: ------------------------------ Summary: Digest-MD5 - missing rspauth and bad encryption key Key: ELY-145 URL: https://issues.jboss.org/browse/ELY-145 Project: WildFly Elytron Issue Type: Bug Reporter: Jan Kalina Assignee: Jan Kalina * In Digest-MD5 implementation is missing last step of authetication - generating and checking of rspauth. * Keys generated for encrypted communication in auth-conf are different from keys generated by JDK implementation - in their generating is bug. (keys are derivated from H(A1) by RFC, so must be identical in all implementations.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

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

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-4324?page=com.atlassian.jira.plugin.... ] Paul Robinson moved DEVELOPER-1219 to WFLY-4324: ------------------------------------------------ Project: WildFly (was: JBoss Developer) Key: WFLY-4324 (was: DEVELOPER-1219) Workflow: GIT Pull Request workflow (was: Agile Simplified Workflow for Project DEVELOPER) > 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)

11 years, 5 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2646?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2646: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1048839|https://bugzilla.redhat.com/show_bug.cgi?id=1048839] from NEW to CLOSED > Expose patch description through mgmt API > ----------------------------------------- > > Key: WFLY-2646 > URL: https://issues.jboss.org/browse/WFLY-2646 > Project: WildFly > Issue Type: Feature Request > Components: Patching > Affects Versions: 8.0.0.CR1 > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Beta1 > > > 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.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4318) Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4318?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-4318: ---------------------------------------- There's definitely a bug in WildFly here. EarInitializationProcessor is relying on the filename of the root of the deployment to decide if it's an ear, instead of relying on the runtime-name value. > Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy > ------------------------------------------------------------------------------------ > > Key: WFLY-4318 > URL: https://issues.jboss.org/browse/WFLY-4318 > Project: WildFly > Issue Type: Bug > Reporter: Geoffrey De Smet > Assignee: Brian Stansberry > > Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ: > https://youtrack.jetbrains.com/issue/IDEA-133729 > https://youtrack.jetbrains.com/issue/IDEA-95695 > "Checked solution in IntelliJ 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :(" > "For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2640) Unable to add cached-connection-manager after removing it once

by Jeff Zhang (JIRA)

[ https://issues.jboss.org/browse/WFLY-2640?page=com.atlassian.jira.plugin.... ] Jeff Zhang reassigned WFLY-2640: -------------------------------- Assignee: (was: Jeff Zhang) > Unable to add cached-connection-manager after removing it once > -------------------------------------------------------------- > > Key: WFLY-2640 > URL: https://issues.jboss.org/browse/WFLY-2640 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Masafumi Miura > > {{<cached-connection-manager>}} is enabled in jca subsystem by default: > {code:xml} > <subsystem xmlns="urn:jboss:domain:jca:1.1"> > ... > <cached-connection-manager /> > </subsystem> > {code} > However, it is unable to re-enable {{<cached-connection-manager>}} once it is disabled. CLI command fails to add it due to duplicate resource. > {code} > [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:remove > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > [standalone@localhost:9990 /] :reload > { > "outcome" => "success", > "result" => undefined > } > [standalone@localhost:9990 /] /subsystem=jca/cached-connection-manager=cached-connection-manager:add > { > "outcome" => "failed", > "failure-description" => "JBAS014803: Duplicate resource [ > (\"subsystem\" => \"jca\"), > (\"cached-connection-manager\" => \"cached-connection-manager\") > ]", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4323) Transaction metrics all zero

by Tim Mickelson (JIRA)

Tim Mickelson created WFLY-4323: ----------------------------------- Summary: Transaction metrics all zero Key: WFLY-4323 URL: https://issues.jboss.org/browse/WFLY-4323 Project: WildFly Issue Type: Bug Components: Transactions Affects Versions: 8.2.0.Final Environment: Linux, JDK 1.7, Spring 4, Hibernate Reporter: Tim Mickelson Assignee: Tom Jenkinson Hello, I have enabled the transactions metrics in standalone.xml on my Wildfly 8.2.0 as below but the transactions metrics are always zero, even though I have many projects deployed using transactions. Probably something trivial is missing, could some one tell me what is wrong? I'm using the Spring Framework 4.1.2 and Hibernate as installed in the Wildfly modules. I started this as a question on the forum but got no answer. Please note that the exact same configuration on the same server gives Transaction statistics with the same deployments on JBoss 7.1.1 Thanks for any help, Tim Mickelson <subsystem xmlns="urn:jboss:domain:transactions:2.0"> <core-environment> <process-id> <uuid/> </process-id> </core-environment> <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> <coordinator-environment default-timeout="300" statistics-enabled="true"/> </subsystem> The datasource is configured as (with jta true): <datasource jta="true" jndi-name="java:/youconnect" pool-name="youconnect_Pool" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:postgresql://127.0.0.1:5432/youconnect</connection-url> <driver-class>org.postgresql.Driver</driver-class> <driver>ps</driver> <pool> <min-pool-size>10</min-pool-size> <max-pool-size>30</max-pool-size> <prefill>true</prefill> <flush-strategy>IdleConnections</flush-strategy> </pool> <security> <user-name>yyyy</user-name> <password>xxxxx</password> </security> </datasource> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4318) Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4318?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-4318: ---------------------------------------- Sure; I'll follow up with Dmitry. > Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy > ------------------------------------------------------------------------------------ > > Key: WFLY-4318 > URL: https://issues.jboss.org/browse/WFLY-4318 > Project: WildFly > Issue Type: Bug > Reporter: Geoffrey De Smet > Assignee: Brian Stansberry > > Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ: > https://youtrack.jetbrains.com/issue/IDEA-133729 > https://youtrack.jetbrains.com/issue/IDEA-95695 > "Checked solution in IntelliJ 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :(" > "For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4318) Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/WFLY-4318?page=com.atlassian.jira.plugin.... ] Geoffrey De Smet commented on WFLY-4318: ---------------------------------------- Brian, would you mind asking Dmitry directly? See the conversation in IntelliJ's youtrack. Personally, I don't care about ear files: I just reported this because they reported in their issue tracker, it's a clear issue and it hadn't made their way into wildfly's issue tracker yet. > Do not force that the exploded directory ends with ".ear" to get the EJB's to deploy > ------------------------------------------------------------------------------------ > > Key: WFLY-4318 > URL: https://issues.jboss.org/browse/WFLY-4318 > Project: WildFly > Issue Type: Bug > Reporter: Geoffrey De Smet > Assignee: Brian Stansberry > > Relates to WFLY-4081 and the IntelliJ issues to make using WildFly less of a pain in IntelliJ: > https://youtrack.jetbrains.com/issue/IDEA-133729 > https://youtrack.jetbrains.com/issue/IDEA-95695 > "Checked solution in IntelliJ 14.1. In general it works. But there is problem with exploded EAR deployments. If I'm trying to deploy exploded EAR which contains some EJB jar with several EJBs beans, this EJBs fails to start in JBoss EAP: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor doesn't even start. But if I try to deploy exploded EAR with ".ear" postfix (just an output folder with ".ear" on the end) it successfully starts EJB beans and I see some JNDI mapping to it from "org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor". Maybe this is a problem of JBoss EAP itself but it seems that we cannot use just a regular folder for exploded EAR output, we have to add ".ear" suffix on the end :(" > "For exploded EAR we should still add ".ear" extension to the exploded directory. Otherwise all EJB beans wouldn't be processed and started after deploy." -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 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