February 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4359) WSEndpointDeploymentUnit should implement a WS-specific interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4359?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4359: ----------------------------------- Description: WSEndpointDeploymentUnit implements the DeploymentUnit interface, but not really. A bunch of methods throw UnsupportedOperationException. This tells me it's using that interface as a minor short-cut, not because it's truly meant to be a DeploymentUnit impl. This is the only impl of this interface outside of WFCORE, and having it here makes it harder to evolve the interface. The WS subsystem code should use its own interface (e.g. as a param to WSDeploymentBuilder.build()), and for the call paths that want to use the DeploymentUnit from WFCORE, wrap the DU in an impl of this WS interface and delegate to it. was: WSEndpointDeploymentUnit implements the DeploymentUnit interface, but not really. A bunch of methods throw UnsupportedOperationException. This tells me it's using that interface as a minor short-cut, not because it's truly meant to be a DeploymentUnit impl. This is the only impl of this interface outside of WFCORE, and having it here makes it harder to evolve the interface. The WS subsystem code should use its own interface (e.g. as a param to WSDeploymentBuilder.build(), and for the call paths that want to use the DeploymentUnit from WFCORE, wrap the DU in an impl of this WS interface and delegate to it. > WSEndpointDeploymentUnit should implement a WS-specific interface > ----------------------------------------------------------------- > > Key: WFLY-4359 > URL: https://issues.jboss.org/browse/WFLY-4359 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Brian Stansberry > Assignee: Alessio Soldano > > WSEndpointDeploymentUnit implements the DeploymentUnit interface, but not really. A bunch of methods throw UnsupportedOperationException. > This tells me it's using that interface as a minor short-cut, not because it's truly meant to be a DeploymentUnit impl. > This is the only impl of this interface outside of WFCORE, and having it here makes it harder to evolve the interface. > The WS subsystem code should use its own interface (e.g. as a param to WSDeploymentBuilder.build()), and for the call paths that want to use the DeploymentUnit from WFCORE, wrap the DU in an impl of this WS interface and delegate to it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4359) WSEndpointDeploymentUnit should implement a WS-specific interface

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-4359: -------------------------------------- Summary: WSEndpointDeploymentUnit should implement a WS-specific interface Key: WFLY-4359 URL: https://issues.jboss.org/browse/WFLY-4359 Project: WildFly Issue Type: Bug Components: Web Services Reporter: Brian Stansberry Assignee: Alessio Soldano WSEndpointDeploymentUnit implements the DeploymentUnit interface, but not really. A bunch of methods throw UnsupportedOperationException. This tells me it's using that interface as a minor short-cut, not because it's truly meant to be a DeploymentUnit impl. This is the only impl of this interface outside of WFCORE, and having it here makes it harder to evolve the interface. The WS subsystem code should use its own interface (e.g. as a param to WSDeploymentBuilder.build(), and for the call paths that want to use the DeploymentUnit from WFCORE, wrap the DU in an impl of this WS interface and delegate to it. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile updated JGRP-1912: -------------------------------- Attachment: logFile2 Here is another run. This run has a lock timeout of 60 seconds. About 4 seconds into the test (test duration is two minutes), one of the 10 threads tries to get a lock on one of the two items. This attempt gets a timeout 60 seconds later, and the SEVERE message is recorded. During the time that this thread is waiting, the other threads are continuing to acquire and release locks on both items. I don't think it matters how long the timeout is, this blocked thread is never going to succeed on this tryLock() call. After the timeout occurs, the thread continues normally to acquire and release locks on both items. > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, logFile2, runLockServiceTestClient.sh, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1912: -------------------------------- A {{tryLock()}} can always fail (timeout) on high load. So why do you consider this an error ? If you run with {{lock()}} instead, you shouldn't see any errors. But make sure you want until all workers have completed. > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, runLockServiceTestClient.sh, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile updated JGRP-1912: -------------------------------- Attachment: runLockServiceTestClient.sh my tiny run script. > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, runLockServiceTestClient.sh, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile updated JGRP-1912: -------------------------------- Attachment: logFile Here is my log file that shows the issue. > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile updated JGRP-1912: -------------------------------- Attachment: udp.xml Here is my channel config file. > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java, logFile, udp.xml > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1912) LockService can fail under heavy load

by Chris Gentile (JIRA)

[ https://issues.jboss.org/browse/JGRP-1912?page=com.atlassian.jira.plugin.... ] Chris Gentile updated JGRP-1912: -------------------------------- Attachment: LockServiceTestClient.java new version. supports new command line arg: --lock-timeout <seconds> > LockService can fail under heavy load > ------------------------------------- > > Key: JGRP-1912 > URL: https://issues.jboss.org/browse/JGRP-1912 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.1 > Environment: both windows 8.1 and RHEL > java 1.7.0_75 > Reporter: Chris Gentile > Assignee: Bela Ban > Fix For: 3.6.3 > > Attachments: LockServiceTestClient.java, LockServiceTestClient.java > > > Once in awhile, the LockService will get stuck acquiring a lock. > These seems to occur most often when two threads are simultaneously trying to acquire the same lock. (i.e.: exact same millisecond on a server with multiple processors). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4354) EJBs can't inherit a JDK8 default method

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-4354?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-4354: ----------------------------------- Looks like both fixes are needed, The ClassReflectionIndexUtil.findMethod() call will not actually find the method because it's not on the component class, but it still should be in the final list. > EJBs can't inherit a JDK8 default method > ---------------------------------------- > > Key: WFLY-4354 > URL: https://issues.jboss.org/browse/WFLY-4354 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Jan Martiska > Assignee: David Lloyd > Attachments: defaultmethodejb.jar > > > If an EJB bean inherits a default method from an interface and doesn't override it, attempt to call this method fails with: > {noformat} > org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4358) Update to Web Console 2.5.4.Final

by Heiko Braun (JIRA)

Heiko Braun created WFLY-4358: --------------------------------- Summary: Update to Web Console 2.5.4.Final Key: WFLY-4358 URL: https://issues.jboss.org/browse/WFLY-4358 Project: WildFly Issue Type: Component Upgrade Components: Web Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 9.0.0.Beta1 -- 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