[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Remy Maucherat (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Remy Maucherat resolved JBWEB-279.
----------------------------------
Resolution: Rejected
This code is the implementation for the specification /META-INF/resources mechanism. As a result, it must follow the specification's behavior. I'm sorry, but there is little way around that.
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: fix.proposal.txt
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne updated JBWEB-279:
-------------------------------
Attachment: (was: overlay.patch)
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: fix.proposal.txt
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne edited comment on JBWEB-279 at 9/2/13 8:35 AM:
------------------------------------------------------------
Fix proposal:
Here is how the code *should* look like in my opinion:
src/main/java/org/apache/naming/resources/ProxyDirContext.java
copy/paste of code gets garbled up, will add attachement
was (Author: tfonteyn):
Fix proposal:
Here is how the code *should* look like in my opinion:
src/main/java/org/apache/naming/resources/ProxyDirContext.java
1701 // Retrieve missing info
1702 boolean foundOriginal = false;
1704 // Retrieving attributes
1705 if (entry.attributes == null) {
1706 try {
1707 Attributes attributes = currentContext.getAttributes(entry.name);
1708 if (!(attributes instanceof ResourceAttributes)) {
1709 entry.attributes =
1710 new ResourceAttributes(attributes);
1711 } else {
1712 entry.attributes = (ResourceAttributes) attributes;
1713 }
foundOriginal = true
1714 } catch (NamingException e) {
1715 // Ignore
1716 }
1717 }
1718
boolean foundOverlay = false;
1719 // Check overlays
1720 if (overlays != null) {
1721 for (int i = 0; (i < overlays.length) && !foundOverlay; i++) {
1722 try {
1723 Attributes attributes = overlays[i].getAttributes(entry.name);
1724 if (!(attributes instanceof ResourceAttributes)) {
1725 entry.attributes =
1726 new ResourceAttributes(attributes);
1727 } else {
1728 entry.attributes = (ResourceAttributes) attributes;
1729 }
1730 currentContext = overlays[i];
1731 foundOverlay = true;
1732 } catch (NamingException e) {
1733 // Ignore
1734 }
1735 }
1736 }
1737
boolean exists = foundOriginal || foundOverlay;
1738 // Retriving object
1739 if ((exists) && (entry.resource == null) && (entry.context == null)) {
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: fix.proposal.txt, overlay.patch
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne updated JBWEB-279:
-------------------------------
Attachment: fix.proposal.txt
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: fix.proposal.txt, overlay.patch
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (JGRP-1685) Remove UNICAST(1, 2), NAKACK protocols
by Bela Ban (JIRA)
Bela Ban created JGRP-1685:
------------------------------
Summary: Remove UNICAST(1,2), NAKACK protocols
Key: JGRP-1685
URL: https://issues.jboss.org/browse/JGRP-1685
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 4.0
Remove older versions of some protocols, e.g.
* Remove UNICAST and UNICAST2, and rename UNICAST3 --> UNICAST
* Remove NAKACK and rename NAKACK2 --> NAKACK
* Remove MERGE and rename MERGE2 --> MERGE
What about RELAY2, Timescheduler2, FRAG2 ?
--
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
10 years, 8 months
[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne commented on JBWEB-279:
------------------------------------
Fix proposal:
Here is how the code *should* look like in my opinion:
src/main/java/org/apache/naming/resources/ProxyDirContext.java
1701 // Retrieve missing info
1702 boolean foundOriginal = false;
1704 // Retrieving attributes
1705 if (entry.attributes == null) {
1706 try {
1707 Attributes attributes = currentContext.getAttributes(entry.name);
1708 if (!(attributes instanceof ResourceAttributes)) {
1709 entry.attributes =
1710 new ResourceAttributes(attributes);
1711 } else {
1712 entry.attributes = (ResourceAttributes) attributes;
1713 }
foundOriginal = true
1714 } catch (NamingException e) {
1715 // Ignore
1716 }
1717 }
1718
boolean foundOverlay = false;
1719 // Check overlays
1720 if (overlays != null) {
1721 for (int i = 0; (i < overlays.length) && !foundOverlay; i++) {
1722 try {
1723 Attributes attributes = overlays[i].getAttributes(entry.name);
1724 if (!(attributes instanceof ResourceAttributes)) {
1725 entry.attributes =
1726 new ResourceAttributes(attributes);
1727 } else {
1728 entry.attributes = (ResourceAttributes) attributes;
1729 }
1730 currentContext = overlays[i];
1731 foundOverlay = true;
1732 } catch (NamingException e) {
1733 // Ignore
1734 }
1735 }
1736 }
1737
boolean exists = foundOriginal || foundOverlay;
1738 // Retriving object
1739 if ((exists) && (entry.resource == null) && (entry.context == null)) {
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: overlay.patch
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (JBWEB-279) Overlays do not work as expected
by Tom Fonteyne (JIRA)
[ https://issues.jboss.org/browse/JBWEB-279?page=com.atlassian.jira.plugin.... ]
Tom Fonteyne reopened JBWEB-279:
--------------------------------
The overlay functionality has nothing to do with the servlet spec. The overlay mechanism provides an extra, JBoss specific, feature
Hence re-opening as "overlay" as currently defined and support through jboss-web.xml is not working
> Overlays do not work as expected
> --------------------------------
>
> Key: JBWEB-279
> URL: https://issues.jboss.org/browse/JBWEB-279
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: JBossWeb-7.2.1.GA
> Reporter: Mustafa Musaji
> Assignee: Remy Maucherat
> Attachments: overlay.patch
>
>
> It is expected that the <overlay> element in jboss-web.xml has the same outcome as the overlay feature in the CLI: https://docs.jboss.org/author/display/AS72/Deployment+Overlays
> In jboss-web.xml the overlays element is not used to actually overlay existing files but to add files to a deployment. This is confusing and either this should work the same as the CLI or the documentation around the <overlay> element in jboss-web.xml should clearly state this is not the case and that we do not replace artifacts but rather
> Attached is a proposed patch that fixes this issue.
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1980) Revisit priviledges for /core-service=management/access=authorization
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/WFLY-1980?page=com.atlassian.jira.plugin.... ]
Heiko Braun commented on WFLY-1980:
-----------------------------------
Maybe 'readable=false' is the right priviledge setup
> Revisit priviledges for /core-service=management/access=authorization
> ---------------------------------------------------------------------
>
> Key: WFLY-1980
> URL: https://issues.jboss.org/browse/WFLY-1980
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Brian Stansberry
>
> It seems the access control resources (/core-service=management/access=authorization) are addressable by the monitor role:
> {noformat}
> [standalone@localhost:9990 /] /core-service=management/access=authorization:read-resource(){roles=monitor}
> {
> "outcome" => "success",
> "result" => {
> "provider" => "simple",
> "use-realm-roles" => false,
> "constraint" => {
> "application-classification" => undefined,
> "sensitivity-classification" => undefined,
> "vault-expression" => undefined
> },
> "role-mapping" => {"SuperUser" => undefined}
> }
> }
> {noformat}
> I think it should be 'addressable=false' for anybody except SuperUser and Administrator
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1980) Revisit priviledges for /core-service=management/access=authorization
by Heiko Braun (JIRA)
Heiko Braun created WFLY-1980:
---------------------------------
Summary: Revisit priviledges for /core-service=management/access=authorization
Key: WFLY-1980
URL: https://issues.jboss.org/browse/WFLY-1980
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
It seems the access control resources (/core-service=management/access=authorization) are addressable by the monitor role:
{noformat}
[standalone@localhost:9990 /] /core-service=management/access=authorization:read-resource(){roles=monitor}
{
"outcome" => "success",
"result" => {
"provider" => "simple",
"use-realm-roles" => false,
"constraint" => {
"application-classification" => undefined,
"sensitivity-classification" => undefined,
"vault-expression" => undefined
},
"role-mapping" => {"SuperUser" => undefined}
}
}
{noformat}
I think it should be 'addressable=false' for anybody except SuperUser and Administrator
--
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
10 years, 8 months
[JBoss JIRA] (WFLY-1975) IllegalStateException when invoking ManagedExecutorService.submit()
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-1975?page=com.atlassian.jira.plugin.... ]
Eduardo Martins commented on WFLY-1975:
---------------------------------------
JSR 236 default resources fail at servlets because the interceptor that sets the concurrent context is not used.
> IllegalStateException when invoking ManagedExecutorService.submit()
> -------------------------------------------------------------------
>
> Key: WFLY-1975
> URL: https://issues.jboss.org/browse/WFLY-1975
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 8.0.0.Alpha4
> Reporter: Juergen Zimmermann
> Assignee: Eduardo Martins
>
> I just compiled the latest WildFly master and have this code fragment which produces the stacktrace below.
> {code}
> public class KundeObserver {
> @Resource(mappedName = "java:comp/DefaultManagedExecutorService")
> private ManagedExecutorService managedExecutorService;
>
> public void onCreateKunde(@Observes @NeuerKunde final AbstractKunde kunde) {
> if (kunde == null) {
> return;
> }
> final Runnable sendMail = new Runnable() {
> @Override
> public void run() {
> }
> };
> managedExecutorService.submit(sendMail); // <-- Exception
> }
> }
> {code}
> The same stacktrace occurs when I use Callable<Void> instead of Runnable (and a call method just returning null).
> The stacktrace:
> {code}
> 17:13:57,490 ERROR [io.undertow.request] Servlet request failed HttpServerExchange{ POST /shop2/rest/kunden}: org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalStateException: JBAS016707: No concurrent context currently set, unable to locate the context service to delegate.
> at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:149) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:372) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:179) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:220) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) [resteasy-jaxrs-3.0.3.Final.jar:]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:87) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:130) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.websockets.jsr.JsrWebSocketFilter.doFilter(JsrWebSocketFilter.java:136) [undertow-websockets-jsr-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:93) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:81)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:55) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:65) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:70) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:207) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:194) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:72) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:128) [undertow-servlet-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta11.jar:1.0.0.Beta11]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25]
> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25]
> Caused by: java.lang.IllegalStateException: JBAS016707: No concurrent context currently set, unable to locate the context service to delegate.
> at org.jboss.as.ee.concurrent.DefaultContextSetupProviderImpl.getConcurrentContext(DefaultContextSetupProviderImpl.java:41)
> at org.jboss.as.ee.concurrent.DefaultContextSetupProviderImpl.saveContext(DefaultContextSetupProviderImpl.java:48)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.captureContext(ManagedFutureTask.java:113)
> at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.<init>(ManagedFutureTask.java:83)
> at org.glassfish.enterprise.concurrent.ManagedExecutorServiceImpl.getNewTaskFor(ManagedExecutorServiceImpl.java:164)
> at org.glassfish.enterprise.concurrent.AbstractManagedExecutorService.submit(AbstractManagedExecutorService.java:357)
> at org.glassfish.enterprise.concurrent.ManagedExecutorServiceAdapter.submit(ManagedExecutorServiceAdapter.java:72)
> at de.shop.kundenverwaltung.service.KundeObserver.onCreateKunde(KundeObserver.java:132) [classes:]
> at de.shop.kundenverwaltung.service.KundeObserver$Proxy$_$$_WeldSubclass.onCreateKunde(Unknown Source) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleInterceptionChain.interceptorChainCompleted(SimpleInterceptionChain.java:47) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:80) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:146) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.util.LogInterceptor.log(LogInterceptor.java:73) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:78) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:48) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:41) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.kundenverwaltung.service.KundeObserver$Proxy$_$$_WeldSubclass.onCreateKunde(Unknown Source) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:274) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:261) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:240) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:171) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:167) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.TransactionalObserverNotifier.notifyObserver(TransactionalObserverNotifier.java:44) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:121) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.event.EventImpl.fire(EventImpl.java:84) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.kundenverwaltung.service.KundeService.createKunde(KundeService.java:412) [classes:]
> at de.shop.kundenverwaltung.service.KundeService$Proxy$_$$_WeldSubclass.createKunde(Unknown Source) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleInterceptionChain.interceptorChainCompleted(SimpleInterceptionChain.java:47) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:80) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:146) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.util.LogInterceptor.log(LogInterceptor.java:73) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:78) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:48) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:41) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.kundenverwaltung.service.KundeService$Proxy$_$$_WeldSubclass.createKunde(Unknown Source) [classes:]
> at de.shop.kundenverwaltung.rest.KundeResource.createKunde(KundeResource.java:337) [classes:]
> at de.shop.kundenverwaltung.rest.KundeResource$Proxy$_$$_WeldSubclass.createKunde(Unknown Source) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleInterceptionChain.interceptorChainCompleted(SimpleInterceptionChain.java:47) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:80) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:146) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.util.LogInterceptor.log(LogInterceptor.java:73) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:78) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:146) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.hibernate.validator.internal.cdi.interceptor.ValidationInterceptor.validateMethodInvocation(ValidationInterceptor.java:87) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at sun.reflect.GeneratedMethodAccessor339.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:78) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorInvocationContext.proceed(InterceptorInvocationContext.java:146) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorBase.invokeInOurTx(TransactionalInterceptorBase.java:74) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> at com.arjuna.ats.jta.cdi.transactional.TransactionalInterceptorRequired.intercept(TransactionalInterceptorRequired.java:52) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> at sun.reflect.GeneratedMethodAccessor203.invoke(Unknown Source) [:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.weld.interceptor.proxy.SimpleMethodInvocation.invoke(SimpleMethodInvocation.java:30) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNext(AbstractInterceptionChain.java:93) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.chain.AbstractInterceptionChain.invokeNextInterceptor(AbstractInterceptionChain.java:78) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.executeInterception(InterceptorMethodHandler.java:48) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.interceptor.proxy.InterceptorMethodHandler.invoke(InterceptorMethodHandler.java:41) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at org.jboss.weld.bean.proxy.CombinedInterceptorAndDecoratorStackMethodHandler.invoke(CombinedInterceptorAndDecoratorStackMethodHandler.java:53) [weld-core-impl-2.0.3.Final.jar:2013-07-17 09:29]
> at de.shop.kundenverwaltung.rest.KundeResource$Proxy$_$$_WeldSubclass.createKunde(Unknown Source) [classes:]
> at de.shop.kundenverwaltung.rest.KundeResource$Proxy$_$$_WeldClientProxy.createKunde(Unknown Source) [classes:]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_25]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_25]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_25]
> at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:137) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:280) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:234) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:221) [resteasy-jaxrs-3.0.3.Final.jar:]
> at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356) [resteasy-jaxrs-3.0.3.Final.jar:]
> ... 37 more
> {code}
--
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
10 years, 8 months