October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2195) add defensive check against EntityManagerFactory/EntityManager already being closed by ill-behaved deployment

by Scott Marlow (JIRA)

Scott Marlow created WFLY-2195: ---------------------------------- Summary: add defensive check against EntityManagerFactory/EntityManager already being closed by ill-behaved deployment Key: WFLY-2195 URL: https://issues.jboss.org/browse/WFLY-2195 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 8.0.0.CR1 When closing container managed entity manager or entity manager factory, check if the entity manager factory was already closed unexpectedly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2194) Difficulty Enabling SSL for Management Interfaces Using CLI

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2194: -------------------------------------- Summary: Difficulty Enabling SSL for Management Interfaces Using CLI Key: WFLY-2194 URL: https://issues.jboss.org/browse/WFLY-2194 Project: WildFly Issue Type: Task Components: CLI, Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.Beta1 Trying to enable the HTTPS port for the HTTP management interface using the CLI results in the following: - {code} [standalone@localhost:9990 /] ./core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https) Communication error: java.util.concurrent.ExecutionException: Operation failed: Operation failed: Channel closed {code} Server side the following is logged: - {code} 17:59:54,193 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015890: Creating http management service using socket-binding (management-http) and secure-socket-binding (management-https) 17:59:54,212 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015888: Creating http management service using socket-binding (management-http) 17:59:54,236 WARN [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014626: Operation was interrupted before stability could be reached {code} i.e. What appears to be happening is that as communication is lost with the client the update is being detected as a failure. As interface updates do result in restarting the services used to make the updates it may be better to switch these to reload required updates instead of being immediate - also the chances are that security realm updates would be made simultaneously and those also require a reload. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2194) Difficulty Enabling SSL for Management Interfaces Using CLI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2194?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2194: ----------------------------------- Affects Version/s: 8.0.0.Alpha4 > Difficulty Enabling SSL for Management Interfaces Using CLI > ----------------------------------------------------------- > > Key: WFLY-2194 > URL: https://issues.jboss.org/browse/WFLY-2194 > Project: WildFly > Issue Type: Task > Components: CLI, Domain Management, Security > Affects Versions: 8.0.0.Alpha4 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Beta1 > > > Trying to enable the HTTPS port for the HTTP management interface using the CLI results in the following: - > {code} > [standalone@localhost:9990 /] ./core-service=management/management-interface=http-interface:write-attribute(name=secure-socket-binding, value=management-https) > Communication error: java.util.concurrent.ExecutionException: Operation failed: Operation failed: Channel closed > {code} > Server side the following is logged: - > {code} > 17:59:54,193 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015890: Creating http management service using socket-binding (management-http) and secure-socket-binding (management-https) > 17:59:54,212 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS015888: Creating http management service using socket-binding (management-http) > 17:59:54,236 WARN [org.jboss.as.controller.management-operation] (management-handler-thread - 4) JBAS014626: Operation was interrupted before stability could be reached > {code} > i.e. What appears to be happening is that as communication is lost with the client the update is being detected as a failure. > As interface updates do result in restarting the services used to make the updates it may be better to switch these to reload required updates instead of being immediate - also the chances are that security realm updates would be made simultaneously and those also require a reload. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-266. -------------------------------- Fix Version/s: 6.0.0.CR5 Resolution: Done > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Fix For: 6.0.0.CR5 > > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-266: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> made a comment on [bug 1014157|https://bugzilla.redhat.com/show_bug.cgi?id=1014157] Fixed by https://github.com/droolsjbpm/drools/commit/bcbfd88b3 Note that this fix works only if you have kie-ci on the classpath. > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-266: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1014157|https://bugzilla.redhat.com/show_bug.cgi?id=1014157] from NEW to MODIFIED > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-266) KIE resolving dependend artifacts issue

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-266?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-266: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1014157 > KIE resolving dependend artifacts issue > --------------------------------------- > > Key: DROOLS-266 > URL: https://issues.jboss.org/browse/DROOLS-266 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 6.0.0.CR3 > Reporter: Kurt Stam > Assignee: Mario Fusco > Attachments: kie-load-from-maven-issue.tgz, kie-load-from-maven-issue.tgz > > > This happens when for a dependency the scope is > - set to 'provided' and > - a parameter (in the case ${jbpm.version}) is used in the version field. > So the relevant entry in the pom is: > <dependency> > <groupId>org.drools</groupId> > <artifactId>drools-core</artifactId> > <version>${drools.version}</version> > <scope>provided</scope> > </dependency> > which leads to > 11:15:02,584 WARN Dependency artifact not found for: org.jbpm:jbpm-bpmn2:${jbpm.version} > and then the NPE. I'm guessing the parameter is not being resolved. > 1. it probably should resolve parameters > 2. if a dependency is scoped as 'provided' I think it is supposed to locate it on the classpath and NOT from maven. However I'm not sure this is the way that works in testing anyway. > 3. if the dependency cannot be found it should probably stop and not even proceed rather then warn? > 4. it should be interesting to see why it gets the NPE. > If you change the dependency from 'provided' to 'test' things work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-928) Starting a server with multiple web apps , causes deploymeent failures

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-928?page=com.atlassian.jira.plugin.s... ] Paul Ferraro closed WFLY-928. ----------------------------- Fix Version/s: 8.0.0.Beta1 Resolution: Done Fixed by introduction of GlobalComponentRegistryService. > Starting a server with multiple web apps , causes deploymeent failures > ----------------------------------------------------------------------- > > Key: WFLY-928 > URL: https://issues.jboss.org/browse/WFLY-928 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Shay Matasaro > Assignee: Paul Ferraro > Fix For: 8.0.0.Beta1 > > > When the server starts with multiple web apps , and each one tries to create its cache , the first one locks all other because of a lock on cache manager see ISPN-2898 > this results in deployment failure , and the apps will not get redeployed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1885) ServiceActivator blocks server startup if more than 8 services - platformspecific

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-1885?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-1885. ------------------------------ Resolution: Done Re-closing. Please read previous comment regarding singleton service creation. > ServiceActivator blocks server startup if more than 8 services - platformspecific > --------------------------------------------------------------------------------- > > Key: WFLY-1885 > URL: https://issues.jboss.org/browse/WFLY-1885 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Server > Affects Versions: 8.0.0.Alpha3 > Reporter: Thomas Frühbeck > Assignee: Paul Ferraro > Priority: Minor > Fix For: 8.0.0.Beta1 > > Attachments: stack.log.gz, wildfly-Beta1_blocked_server_on_8_HASingletons.txt.gz > > > We try to start more than 8 services by ServiceActivator. > We follow hasingleton quickstart. > Server startup is blocked on Linux but not on windows (?!?). > If we introduce a delay of e.g. 1 second, all services start correctly also on Linux: > public void activate(ServiceActivatorContext context) { > ESMSSingletonServiceBase<T> service = getSingletonService(); > log.info("ESMSService will be installed: " + service.getSingletonServiceName()); > SingletonService<String> singleton = new SingletonService<String>(service.getSingletonServiceName(), service); > singleton.build(new DelegatingServiceContainer(context.getServiceTarget(), context.getServiceRegistry())) > .addDependency(ServerEnvironmentService.SERVICE_NAME, ServerEnvironment.class, service.env) > .setInitialMode(ServiceController.Mode.ACTIVE).install(); > // TODO: diesen Workaround evtl mal beheben. > // (Server startet im Moment nicht anders... zumindest nicht auf Linux! Timingproblem?) > try { > Thread.sleep(1000); > } catch (InterruptedException e) {} > Thread dump of Linux blocked server attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2178) exception in distributable webapp leads to infinispan lock contention

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-2178?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-2178. ------------------------------ Resolution: Rejected Fixed by UNDERTOW-107. The lock contention is due to the lock never being released because undertow threw an exception when attempting to trigger the session destroy listener. > exception in distributable webapp leads to infinispan lock contention > ---------------------------------------------------------------------- > > Key: WFLY-2178 > URL: https://issues.jboss.org/browse/WFLY-2178 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Thomas Frühbeck > Assignee: Paul Ferraro > Attachments: lockContention_server.log > > > Exception in session.invalidate leads to: > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (default task-23) ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutExceptio > n: Unable to acquire lock after [15 seconds] on key [FIsDATdNvtWFPLx-x-00_6x0] for requestor [GlobalTransaction:<storage/web>:171:local]! Lock held by [GlobalTransaction:<storage/web>:170:local] > server.log attached -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 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 October 2013