December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1808) Update transaction API 1.2 to 1.0.0.Beta1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1808?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1808: ----------------------------- Fix Version/s: 9.0.0.Final > Update transaction API 1.2 to 1.0.0.Beta1 > ----------------------------------------- > > Key: WFLY-1808 > URL: https://issues.jboss.org/browse/WFLY-1808 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1739) Certain methods unconditionally invokes itself and may cause infinit loop

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1739?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1739: ----------------------------- Fix Version/s: 9.0.0.Final > Certain methods unconditionally invokes itself and may cause infinit loop > ------------------------------------------------------------------------- > > Key: WFLY-1739 > URL: https://issues.jboss.org/browse/WFLY-1739 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Alpha4 > Reporter: Cheng Fang > Assignee: Paul Ferraro > Fix For: 9.0.0.Final > > > FindBugs found 2 instances of such recursive calls: > {code:title=org.jboss.as.clustering.msc.DelegatingServiceTarget} > @Override > public Set<ServiceListener<Object>> getListeners() { > return this.getListeners(); > } > {code} > {code:title=org.wildfly.clustering.web.catalina.session.SessionFacade} > @Override > public boolean isValidInternal() { > return this.isValidInternal(); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4224) Update all text references from JBoss to Wildfly on kitchensink quickstarts

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4224?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4224: ----------------------------- Fix Version/s: 9.0.0.Final > Update all text references from JBoss to Wildfly on kitchensink quickstarts > --------------------------------------------------------------------------- > > Key: WFLY-4224 > URL: https://issues.jboss.org/browse/WFLY-4224 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Fix For: 9.0.0.Final > > > Kitchensink Quickstarts contains a lot of references to JBossAS7 that needs to be updated to WildFly -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4153: ----------------------------- Fix Version/s: 9.0.0.Final > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 9.0.0.Final > > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1695) Web Console: Principal/Role indication in footer

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1695?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1695: ----------------------------- Fix Version/s: 9.0.0.Final > Web Console: Principal/Role indication in footer > ------------------------------------------------ > > Key: WFLY-1695 > URL: https://issues.jboss.org/browse/WFLY-1695 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 9.0.0.Final > > > it should be possible to see the current principal and the active role in the console footer -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4313) Clean-up tests which use Kerberos in the WildFly testsuite

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4313?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4313: ----------------------------- Fix Version/s: 9.0.0.Final > Clean-up tests which use Kerberos in the WildFly testsuite > ---------------------------------------------------------- > > Key: WFLY-4313 > URL: https://issues.jboss.org/browse/WFLY-4313 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Fix For: 9.0.0.Final > > > Clean up Kerberos tests and add an unified logic for skipping Kerberos test configurations which proved to be unstable/buggy. By a configuration here is meant combination of Java vendor, version and IP stack. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2180) Thread threads pools inherit security context of submitting threads

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2180?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2180: ----------------------------- Fix Version/s: 9.0.0.Final > Thread threads pools inherit security context of submitting threads > ------------------------------------------------------------------- > > Key: WFLY-2180 > URL: https://issues.jboss.org/browse/WFLY-2180 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, Server, Web (Undertow) > Affects Versions: 8.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: David Lloyd > Fix For: 9.0.0.Final > > > Some thread pool implementation will immediately create a new thread if work is submitted and there is not enough threads available to handle it. This newly created thread will inherit the access control context of the thread that is submitting the work, which essentially means that thread pool threads have a random access control context. > This is the root cause of UNDERTOW-102, and likely other security manager related failures as well. > I think that the best way to fix this is in the thread pool itself, as it should create the thread in a privileged block. We obviously cannot do this for JDK thread pools however. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4190) Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4190?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4190: ----------------------------- Fix Version/s: 9.0.0.Final > Provide a Willdfly banner instead of JBossAS7 for Kitchensink quickstarts > -------------------------------------------------------------------------- > > Key: WFLY-4190 > URL: https://issues.jboss.org/browse/WFLY-4190 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Fix For: 9.0.0.Final > > Attachments: wildfly_400x130.jpg > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3404) Major performance degradation from JBoss 7.1 to Wildfly 8.0.0-Final.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3404?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3404: ----------------------------- Fix Version/s: 9.0.0.Final > Major performance degradation from JBoss 7.1 to Wildfly 8.0.0-Final. > -------------------------------------------------------------------- > > Key: WFLY-3404 > URL: https://issues.jboss.org/browse/WFLY-3404 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.0.0.Final > Reporter: Timothy Heider > Assignee: Jason Greene > Fix For: 9.0.0.Final > > > I have deployed my application to Wildfly 8.0.0 Final and it is almost unusable now. We have rolled back to JBoss 7.1 (same application WARs) and it works fine. > Specifically what seems to be slow is our SOAP web services are taking up to 8 to 10 seconds to respond. We have user concurrency of probably 10-30 users at once hitting these services every 10 seconds or so. > On JBoss 7.1 these services all respond sub-second. The database is totally unburdened and the server is 90% idle all the time. > We have one service endpoint that is a Comet queue wait call. Probably 10 users are waiting on that. Did something change between JBoss 7 and Wildfly 8 that might cause that to not work now? (e.g. too small a thread pool that blocks until the 10 second comet call breaks on a timeout?) > We will try 8.1.0CR2 but I wanted to report we're investigating this and see if you can help us. Thanks! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4173) Server side EJB Handler not compression response

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4173?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4173: ----------------------------- Fix Version/s: 9.0.0.Final > Server side EJB Handler not compression response > ------------------------------------------------ > > Key: WFLY-4173 > URL: https://issues.jboss.org/browse/WFLY-4173 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Tomas Hofman > Fix For: 9.0.0.Final > > > When compression is enabled for request/response, the jboss-ejb-client is sending a compressed request, but the application server is responding with an uncompressed response. > On the server enabling TRACE on org.jboss.as.ejb3, we can see the server receives a compressed request > TRACE [org.jboss.as.ejb3] (default task-5) Got message with header 0x1b on channel Channel ID 56b01772 (inbound) of Remoting connection TRACE [org.jboss.as.ejb3.invocation] (default task-5) Received a compressed message stream > Client side, Enabling TRACE on the client side for org.jboss.ejb.client we see it is 0x5 where it should be 0x1b > TRACE org.jboss.ejb.client.remoting.ChannelAssociation - Received message with header 0x5 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 December 2017