[JBoss JIRA] (WFLY-2978) Wildfly ignores jboss-ejb-client.xml
by Alan Chung (JIRA)
[ https://issues.jboss.org/browse/WFLY-2978?page=com.atlassian.jira.plugin.... ]
Alan Chung commented on WFLY-2978:
----------------------------------
Stuart,
Thanks for the updates.
I just want to make sure your fix in 8.2.0.final is not about http-remoting
protocol but the problem I
described in the comments.
we have set http-remoting protocol in 8.1.0 but jboss-ejb-client is still
ignored.
Please confirm.
One more quuestion
is jboss-ejb-client version 1.0 correct?
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.0">
Thanks.
Alan
On Mon, Dec 8, 2014 at 3:34 PM, Stuart Douglas (JIRA) <issues(a)jboss.org>
--
Alan
> Wildfly ignores jboss-ejb-client.xml
> ------------------------------------
>
> Key: WFLY-2978
> URL: https://issues.jboss.org/browse/WFLY-2978
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Naming, Remoting
> Affects Versions: 8.0.0.Final
> Environment: Spring 4.0.2, EJB
> Reporter: ofbiz brazil
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 8.2.0.Final
>
>
> Hi all,
> I have a project with remote EJB's running in one Wildfly server and the're some war client projects that invoked those EJB's in another Wildfly server. Even adding the descriptor jboss-ejb-client.xml into war client projects Widlfly always says: "No EJB receiver available for handling....". That seems Wildfly is ignoring the descriptor no matter if the file exists in WEB-INF, by the way in JBoss 7.1.1 it works perfectly.
> I added into client war projects the descripor jboss-ejb-client.xml
> {code:xml}
> <jboss-ejb-client>
> <client-context>
> <ejb-receivers>
> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection" />
> </ejb-receivers>
> </client-context>
> </jboss-ejb-client>
> {code}
> In Wildfly server running EJB's the standalone.xml
> {code:xml}
> <security-realm name="ejb-security-realm">
> <server-identities>
> <secret value="c2Fvb3JhY2xlZGV2cGFzcw=="/>
> </server-identities>
> </security-realm>
> {code}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:remoting:2.0">
> <endpoint worker="default"/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
> <outbound-connections>
> <remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" username="ejbuser" security-realm="ejb-security-realm">
> <properties>
> <property name="SSL_ENABLED" value="false"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="true"/>
> <property name="SASL_POLICY_NOPLAINTEXT" value="false"/>
> </properties>
> </remote-outbound-connection>
> </outbound-connections>
> </subsystem>
> {code}
> {code:xml}
> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:7029}"/>
> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:7030}"/>
> <socket-binding name="http" port="${jboss.http.port:7021}"/>
> <socket-binding name="https" port="${jboss.https.port:7022}"/>
> <socket-binding name="txn-recovery-environment" port="7025"/>
> <socket-binding name="txn-status-manager" port="7026"/>
> <outbound-socket-binding name="remote-ejb">
> <remote-destination host="myserver.com" port="7021"/>
> </outbound-socket-binding>
> </socket-binding-group>
> {code}
> Console exception:
> {noformat}
> 10:41:20,761 INFO [io.undertow.servlet] (MSC service thread 1-9) Initializing Spring root WebApplicationContext
> 10:41:22,540 INFO [org.jboss.ejb.client] (MSC service thread 1-9) JBoss EJB Client version 2.0.0.Final
> 10:41:22,853 INFO [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /orca
> 10:41:22,884 INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "SBBORCA.war" (runtime-name : "SBBORCA.war")
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://0.0.0.0:7029/management
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:7029
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 12312ms - Started 413 of 466 services (93 services are lazy, passive or on-demand)
> 10:41:45,533 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /orca/j_spring_cas_security_check: java.lang.RuntimeException: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:SBBUserAccess, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@19ba64
> at com.sbb.spring.security.CustomUserDetailsService.loadUserByUsername(CustomUserDetailsService.java:63) [utils-1.0.0.jar:]
> at org.springframework.security.core.userdetails.UserDetailsByNameServiceWrapper.loadUserDetails(UserDetailsByNameServiceWrapper.java:51) [spring-security-core-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.loadUserByAssertion(CasAuthenticationProvider.java:185) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticateNow(CasAuthenticationProvider.java:141) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticate(CasAuthenticationProvider.java:126) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156) [spring-security-core-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$AuthenticationManagerDelegator.authenticate(WebSecurityConfigurerAdapter.java:431) [spring-security-config-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.web.CasAuthenticationFilter.attemptAuthentication(CasAuthenticationFilter.java:242) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:211) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:110) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:110) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:50) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:344) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:261) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:177) [spring-orm-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:SBBUserAccess, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@19ba64
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at com.sun.proxy.$Proxy89.findByUserProfile(Unknown Source)
> at com.sbb.spring.security.UserProfileGrantedAuthoritiesLoader.loadAuthorities(UserProfileGrantedAuthoritiesLoader.java:44) [utils-1.0.0.jar:]
> at com.sbb.spring.security.CustomUserDetailsService.loadUserByUsername(CustomUserDetailsService.java:55) [utils-1.0.0.jar:]
> ... 52 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3910) To be added AJP connector connectionTimeout parameter
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3910?page=com.atlassian.jira.plugin.... ]
Stuart Douglas resolved WFLY-3910.
----------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Done
This is called no-request-timeout on the HTTP connector
> To be added AJP connector connectionTimeout parameter
> -----------------------------------------------------
>
> Key: WFLY-3910
> URL: https://issues.jboss.org/browse/WFLY-3910
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final
> Reporter: Angel Ivanov
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
>
> Hi,
> We need configuration parameter for Undertow to manage especially AJP connector connection timeout, because created threads staid alive forever.
> In tomcat such kind of connector parameter was connectionTimeout.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (DROOLS-663) DrlDumper does not output binding for accumulate function
by Bryn Rhodes (JIRA)
Bryn Rhodes created DROOLS-663:
----------------------------------
Summary: DrlDumper does not output binding for accumulate function
Key: DROOLS-663
URL: https://issues.jboss.org/browse/DROOLS-663
Project: Drools
Issue Type: Bug
Affects Versions: 6.2.0.CR2
Environment: Windows 8.1, Eclipse, Java 8.0.25
Reporter: Bryn Rhodes
Assignee: Mark Proctor
Priority: Minor
When building a rule with a single-function accumulate conditional element, I set the binding name for the function call according to the documentation for the function method of the AccumulateDescrBuilder. However, when the function is output by the DrlDumper, the accumulate call is output without the binding.
I've traced the Builder to the Descr and that sets the description correctly. The problem seems to be with the drl.mvel template, line 96, the function output template doesn't have a marker for the binding name. (https://github.com/droolsjbpm/drools/blob/master/drools-compiler/src/main...)
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-4099) NameNotFoundException: clustering/group/ejb
by Frank Langelage (JIRA)
[ https://issues.jboss.org/browse/WFLY-4099?page=com.atlassian.jira.plugin.... ]
Frank Langelage closed WFLY-4099.
---------------------------------
Resolution: Duplicate Issue
Duplicate of WFLY-3994.
> NameNotFoundException: clustering/group/ejb
> -------------------------------------------
>
> Key: WFLY-4099
> URL: https://issues.jboss.org/browse/WFLY-4099
> Project: WildFly
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 9.0.0.Beta1
> Reporter: Frank Langelage
> Assignee: Heiko Braun
>
> Clicking on "JNDI View" in the admin web-console adds this error message to server.log:
> 19.11. 23:30:40,998 ERROR [org.jboss.as.naming#addEntries] WFLYNAM0013: Failed to obtain jndi view value for entry ejb.: javax.naming.NameNotFoundException: clustering/group/ejb [Root exception is java.lang.IllegalStateException]
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:153)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:83)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:132)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:137)
> at org.jboss.as.naming.management.JndiViewOperation.addEntries(JndiViewOperation.java:137)
> at org.jboss.as.naming.management.JndiViewOperation.access$000(JndiViewOperation.java:47)
> at org.jboss.as.naming.management.JndiViewOperation$1.execute(JndiViewOperation.java:72)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:728)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:563)
> at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:336)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:312)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1163)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:356)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:215)
> at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:207)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:72)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$1.run(SubjectDoAsHandler.java:68)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:94)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:68)
> at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:63)
> at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56)
> at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:83)
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:199)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:767)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:138)
> at org.jboss.as.naming.service.BinderService.getValue(BinderService.java:46)
> at org.jboss.msc.service.ServiceControllerImpl.getValue(ServiceControllerImpl.java:1158)
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:131)
> ... 31 more
> Server is running in standalone mode.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-2978) Wildfly ignores jboss-ejb-client.xml
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2978?page=com.atlassian.jira.plugin.... ]
Stuart Douglas updated WFLY-2978:
---------------------------------
Fix Version/s: 8.2.0.Final
> Wildfly ignores jboss-ejb-client.xml
> ------------------------------------
>
> Key: WFLY-2978
> URL: https://issues.jboss.org/browse/WFLY-2978
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Naming, Remoting
> Affects Versions: 8.0.0.Final
> Environment: Spring 4.0.2, EJB
> Reporter: ofbiz brazil
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 8.2.0.Final
>
>
> Hi all,
> I have a project with remote EJB's running in one Wildfly server and the're some war client projects that invoked those EJB's in another Wildfly server. Even adding the descriptor jboss-ejb-client.xml into war client projects Widlfly always says: "No EJB receiver available for handling....". That seems Wildfly is ignoring the descriptor no matter if the file exists in WEB-INF, by the way in JBoss 7.1.1 it works perfectly.
> I added into client war projects the descripor jboss-ejb-client.xml
> {code:xml}
> <jboss-ejb-client>
> <client-context>
> <ejb-receivers>
> <remoting-ejb-receiver outbound-connection-ref="remote-ejb-connection" />
> </ejb-receivers>
> </client-context>
> </jboss-ejb-client>
> {code}
> In Wildfly server running EJB's the standalone.xml
> {code:xml}
> <security-realm name="ejb-security-realm">
> <server-identities>
> <secret value="c2Fvb3JhY2xlZGV2cGFzcw=="/>
> </server-identities>
> </security-realm>
> {code}
> {code:xml}
> <subsystem xmlns="urn:jboss:domain:remoting:2.0">
> <endpoint worker="default"/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
> <outbound-connections>
> <remote-outbound-connection name="remote-ejb-connection" outbound-socket-binding-ref="remote-ejb" username="ejbuser" security-realm="ejb-security-realm">
> <properties>
> <property name="SSL_ENABLED" value="false"/>
> <property name="SASL_POLICY_NOANONYMOUS" value="true"/>
> <property name="SASL_POLICY_NOPLAINTEXT" value="false"/>
> </properties>
> </remote-outbound-connection>
> </outbound-connections>
> </subsystem>
> {code}
> {code:xml}
> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:7029}"/>
> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:7030}"/>
> <socket-binding name="http" port="${jboss.http.port:7021}"/>
> <socket-binding name="https" port="${jboss.https.port:7022}"/>
> <socket-binding name="txn-recovery-environment" port="7025"/>
> <socket-binding name="txn-status-manager" port="7026"/>
> <outbound-socket-binding name="remote-ejb">
> <remote-destination host="myserver.com" port="7021"/>
> </outbound-socket-binding>
> </socket-binding-group>
> {code}
> Console exception:
> {noformat}
> 10:41:20,761 INFO [io.undertow.servlet] (MSC service thread 1-9) Initializing Spring root WebApplicationContext
> 10:41:22,540 INFO [org.jboss.ejb.client] (MSC service thread 1-9) JBoss EJB Client version 2.0.0.Final
> 10:41:22,853 INFO [org.wildfly.extension.undertow] (MSC service thread 1-9) JBAS017534: Registered web context: /orca
> 10:41:22,884 INFO [org.jboss.as.server] (ServerService Thread Pool -- 29) JBAS018559: Deployed "SBBORCA.war" (runtime-name : "SBBORCA.war")
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://0.0.0.0:7029/management
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:7029
> 10:41:22,900 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final "WildFly" started in 12312ms - Started 413 of 466 services (93 services are lazy, passive or on-demand)
> 10:41:45,533 ERROR [io.undertow.request] (default task-2) UT005023: Exception handling request to /orca/j_spring_cas_security_check: java.lang.RuntimeException: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:SBBUserAccess, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@19ba64
> at com.sbb.spring.security.CustomUserDetailsService.loadUserByUsername(CustomUserDetailsService.java:63) [utils-1.0.0.jar:]
> at org.springframework.security.core.userdetails.UserDetailsByNameServiceWrapper.loadUserDetails(UserDetailsByNameServiceWrapper.java:51) [spring-security-core-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.loadUserByAssertion(CasAuthenticationProvider.java:185) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticateNow(CasAuthenticationProvider.java:141) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.authentication.CasAuthenticationProvider.authenticate(CasAuthenticationProvider.java:126) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.authentication.ProviderManager.authenticate(ProviderManager.java:156) [spring-security-core-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.config.annotation.web.configuration.WebSecurityConfigurerAdapter$AuthenticationManagerDelegator.authenticate(WebSecurityConfigurerAdapter.java:431) [spring-security-config-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.cas.web.CasAuthenticationFilter.attemptAuthentication(CasAuthenticationFilter.java:242) [spring-security-cas-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:211) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:110) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:110) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:87) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:50) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:342) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:192) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:160) [spring-security-web-3.2.1.RELEASE.jar:3.2.1.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:344) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:261) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.springframework.orm.jpa.support.OpenEntityManagerInViewFilter.doFilterInternal(OpenEntityManagerInViewFilter.java:177) [spring-orm-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:108) [spring-web-4.0.2.RELEASE.jar:4.0.2.RELEASE]
> at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:56) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:132) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:85) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687) [undertow-core-1.0.0.Final.jar:1.0.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:SBBUserAccess, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@19ba64
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:749) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:116) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:183) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) [jboss-ejb-client-2.0.0.Final.jar:2.0.0.Final]
> at com.sun.proxy.$Proxy89.findByUserProfile(Unknown Source)
> at com.sbb.spring.security.UserProfileGrantedAuthoritiesLoader.loadAuthorities(UserProfileGrantedAuthoritiesLoader.java:44) [utils-1.0.0.jar:]
> at com.sbb.spring.security.CustomUserDetailsService.loadUserByUsername(CustomUserDetailsService.java:55) [utils-1.0.0.jar:]
> ... 52 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-4140) In some case :activare on resource-adapter fails if id != archive_name
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4140?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-4140:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1171863, https://bugzilla.redhat.com/show_bug.cgi?id=1171866 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1171863)
> In some case :activare on resource-adapter fails if id != archive_name
> ----------------------------------------------------------------------
>
> Key: WFLY-4140
> URL: https://issues.jboss.org/browse/WFLY-4140
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Stefano Maestri
> Assignee: Stefano Maestri
>
> deploy /home/jolee/amq.rar
> /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=UseInboundSession:add(value=false)
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=ServerUrl:add(value="vm://localhost")
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=BrokerXmlConfig:add(value="xbean:broker-config.xml")
> /subsystem=resource-adapters/resource-adapter=amq/connection-definitions=ConnectionFactory:add(jndi-name=java:jboss/ConnectionFactory,use-java-context=true,class-name=org.apache.activemq.ra.ActiveMQManagedConnectionFactory,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter:add(jndi-name=java:jboss/queue/EAIProcessStarter,use-java-context=false,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter/config-properties=PhysicalName:add(value=EAIProcessStarter)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER:add(jndi-name=java:/jboss/queue/EAI_TRIGGER,use-java-context=true,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER/config-properties=PhysicalName:add(value=EAI_TRIGGER)
> /subsystem=resource-adapters/resource-adapter=amq:activate
> [4]
> [standalone@localhost:9999 /] run-batch --file=/home/jolee/rar2.cli
> {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-10" => "JBAS010480: RAR 'amq' not yet deployed."}}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-4140) In some case :activare on resource-adapter fails if id != archive_name
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4140?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated WFLY-4140:
------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1171863
> In some case :activare on resource-adapter fails if id != archive_name
> ----------------------------------------------------------------------
>
> Key: WFLY-4140
> URL: https://issues.jboss.org/browse/WFLY-4140
> Project: WildFly
> Issue Type: Feature Request
> Components: JCA
> Reporter: Stefano Maestri
> Assignee: Stefano Maestri
>
> deploy /home/jolee/amq.rar
> /subsystem=resource-adapters/resource-adapter=amq:add(archive=amq.rar,transaction-support=XATransaction)
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=UseInboundSession:add(value=false)
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=ServerUrl:add(value="vm://localhost")
> /subsystem=resource-adapters/resource-adapter=amq/config-properties=BrokerXmlConfig:add(value="xbean:broker-config.xml")
> /subsystem=resource-adapters/resource-adapter=amq/connection-definitions=ConnectionFactory:add(jndi-name=java:jboss/ConnectionFactory,use-java-context=true,class-name=org.apache.activemq.ra.ActiveMQManagedConnectionFactory,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter:add(jndi-name=java:jboss/queue/EAIProcessStarter,use-java-context=false,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAIProcessStarter/config-properties=PhysicalName:add(value=EAIProcessStarter)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER:add(jndi-name=java:/jboss/queue/EAI_TRIGGER,use-java-context=true,class-name=org.apache.activemq.command.ActiveMQQueue,enabled=true)
> /subsystem=resource-adapters/resource-adapter=amq/admin-objects=EAI_TRIGGER/config-properties=PhysicalName:add(value=EAI_TRIGGER)
> /subsystem=resource-adapters/resource-adapter=amq:activate
> [4]
> [standalone@localhost:9999 /] run-batch --file=/home/jolee/rar2.cli
> {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-10" => "JBAS010480: RAR 'amq' not yet deployed."}}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-451) ResolveExpressionHandler is overly simplistic in expression resolution
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-451?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on WFCORE-451:
------------------------------------------------
Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1171809|https://bugzilla.redhat.com/show_bug.cgi?id=1171809] from NEW to POST
> ResolveExpressionHandler is overly simplistic in expression resolution
> ----------------------------------------------------------------------
>
> Key: WFCORE-451
> URL: https://issues.jboss.org/browse/WFCORE-451
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha14
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha15
>
>
> ResolveExpressionHandler deliberately does not make use of the full range of expression resolutions sources, because by design the intent is not to support vault resolution.
> However, the way it implements that limitation is by simply calling ModelNode.resolve(). That is overly restrictive, as DMR alone does not support other valid resolution features, i.e. nested expressions and recursive resolution.
> Fix is to switch the handler to use an ExpressionResolver impl, just one that doesn't plug in the vault resolver.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFCORE-451) ResolveExpressionHandler is overly simplistic in expression resolution
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-451?page=com.atlassian.jira.plugin... ]
Brian Stansberry updated WFCORE-451:
------------------------------------
Fix Version/s: 1.0.0.Alpha15
(was: 1.0.0.Beta1)
> ResolveExpressionHandler is overly simplistic in expression resolution
> ----------------------------------------------------------------------
>
> Key: WFCORE-451
> URL: https://issues.jboss.org/browse/WFCORE-451
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha14
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 1.0.0.Alpha15
>
>
> ResolveExpressionHandler deliberately does not make use of the full range of expression resolutions sources, because by design the intent is not to support vault resolution.
> However, the way it implements that limitation is by simply calling ModelNode.resolve(). That is overly restrictive, as DMR alone does not support other valid resolution features, i.e. nested expressions and recursive resolution.
> Fix is to switch the handler to use an ExpressionResolver impl, just one that doesn't plug in the vault resolver.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months
[JBoss JIRA] (WFLY-3548) JTA synchronization for a distributed transaction called with incorrect TCCL
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3548?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3548:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1098127|https://bugzilla.redhat.com/show_bug.cgi?id=1098127] from POST to MODIFIED
> JTA synchronization for a distributed transaction called with incorrect TCCL
> ----------------------------------------------------------------------------
>
> Key: WFLY-3548
> URL: https://issues.jboss.org/browse/WFLY-3548
> Project: WildFly
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 8.1.0.Final
> Reporter: Martin Kouba
> Assignee: Martin Kouba
> Fix For: 9.0.0.Beta1
>
>
> It seems the RequestProcessor which is processing JTA synchronizations
> does not have the right TCCL set.
> As a result, during synchronization invocation:
> * {{NameNotFoundException}} is thrown for a JNDI lookup of "java:comp/UserTransaction"
> * if we try to acccess {{org.jboss.weld.Container}} by means of {{org.jboss.as.weld.services.ModuleGroupSingletonProvider.TCCLSingleton}}, we get ISE: "Singleton not set....This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment."
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 7 months