[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7312?page=com.atlassian.jira.plugin.... ]
Josef Ludvicek updated WFLY-7312:
---------------------------------
Affects Version/s: 10.1.0.Final
> wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
> --------------------------------------------------------------------------------------
>
> Key: WFLY-7312
> URL: https://issues.jboss.org/browse/WFLY-7312
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Josef Ludvicek
> Assignee: Jason Greene
>
> {{wildfly-parent}} BOM is present in maven central,
> but it specifies certain dependencies, which were not published to central and hence breaking the build.
> For example
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.fuse.qa</groupId>
> <artifactId>slf4j-reproducer</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-parent</artifactId>
> <version>10.1.0.Final</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.arquillian.cube</groupId>
> <artifactId>arquillian-cube-docker</artifactId>
> <version>1.0.0.Alpha15</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> fails:
> {code}
> [ERROR] Failed to execute goal on project slf4j-reproducer:
> Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
> The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
> Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR]
> {code}
> There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
> Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7311) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7311:
------------------------------------
Summary: Make the authentication configurable in the eap testsuite
Key: WFLY-7311
URL: https://issues.jboss.org/browse/WFLY-7311
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Filippe Spolti
Assignee: Filippe Spolti
Priority: Optional
Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
In this specific case, EAP 6/7 instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
Example:
org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
return connector.getMBeanServerConnection();
}
{code}
To:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
propEnv.put(JMXConnector.CREDENTIALS, credentials);
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
return connector.getMBeanServerConnection();
}
{code}
Could these kind of authentication being configurable?
It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
Filippe Spolti updated WFLY-7309:
---------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1384542
> Make the authentication configurable in the eap testsuite
> ----------------------------------------------------------
>
> Key: WFLY-7309
> URL: https://issues.jboss.org/browse/WFLY-7309
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
> In this specific case, EAP 6/7 instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example:
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
> return connector.getMBeanServerConnection();
> }
> {code}
> To:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
> String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
> propEnv.put(JMXConnector.CREDENTIALS, credentials);
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
> return connector.getMBeanServerConnection();
> }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7310) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7310:
------------------------------------
Summary: Make the authentication configurable in the eap testsuite
Key: WFLY-7310
URL: https://issues.jboss.org/browse/WFLY-7310
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Filippe Spolti
Assignee: Filippe Spolti
Priority: Optional
Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
In this specific case, EAP 6/7 instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
Example:
org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
return connector.getMBeanServerConnection();
}
{code}
To:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
propEnv.put(JMXConnector.CREDENTIALS, credentials);
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
return connector.getMBeanServerConnection();
}
{code}
Could these kind of authentication being configurable?
It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7310) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7310?page=com.atlassian.jira.plugin.... ]
Filippe Spolti closed WFLY-7310.
--------------------------------
Resolution: Done
> Make the authentication configurable in the eap testsuite
> ----------------------------------------------------------
>
> Key: WFLY-7310
> URL: https://issues.jboss.org/browse/WFLY-7310
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
> In this specific case, EAP 6/7 instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example:
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
> return connector.getMBeanServerConnection();
> }
> {code}
> To:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
> String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
> propEnv.put(JMXConnector.CREDENTIALS, credentials);
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
> return connector.getMBeanServerConnection();
> }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7309:
------------------------------------
Summary: Make the authentication configurable in the eap testsuite
Key: WFLY-7309
URL: https://issues.jboss.org/browse/WFLY-7309
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Filippe Spolti
Priority: Optional
Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
In this specific case, EAP 6/7 instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
Example:
org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
return connector.getMBeanServerConnection();
}
{code}
To:
{code:java}
private MBeanServerConnection getMBeanServerConnection() throws IOException {
HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
propEnv.put(JMXConnector.CREDENTIALS, credentials);
final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
return connector.getMBeanServerConnection();
}
{code}
Could these kind of authentication being configurable?
It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
Filippe Spolti reassigned WFLY-7309:
------------------------------------
Assignee: Filippe Spolti
> Make the authentication configurable in the eap testsuite
> ----------------------------------------------------------
>
> Key: WFLY-7309
> URL: https://issues.jboss.org/browse/WFLY-7309
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> Actually some tests cases of EAP's testsuite failes when running against a remote eap instance.
> In this specific case, EAP 6/7 instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example:
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
> return connector.getMBeanServerConnection();
> }
> {code}
> To:
> {code:java}
> private MBeanServerConnection getMBeanServerConnection() throws IOException {
> HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
> String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
> propEnv.put(JMXConnector.CREDENTIALS, credentials);
> final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
> connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
> return connector.getMBeanServerConnection();
> }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (DROOLS-1327) Drools declared types cannot be references in jBPM Drools expressions due to compilation order.
by Duncan Doyle (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1327?page=com.atlassian.jira.plugi... ]
Duncan Doyle reassigned DROOLS-1327:
------------------------------------
Assignee: Duncan Doyle (was: Mario Fusco)
> Drools declared types cannot be references in jBPM Drools expressions due to compilation order.
> -----------------------------------------------------------------------------------------------
>
> Key: DROOLS-1327
> URL: https://issues.jboss.org/browse/DROOLS-1327
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.4.0.Final
> Environment: JBoss BPM Suite 6.3.3.GA
> Reporter: Duncan Doyle
> Assignee: Duncan Doyle
>
> When you declare a type in a DRL using the "declare" syntax, that type cannot be referenced by Drools LHS expressions in a Sequence Flow (for example in the context of an X-OR Gateway). The DRL and BPMN2 file are in the same project.
> The problem is the order of compilation of CompositeKnowledgeBuilderImpl. The builder compiles the process definitions before the DRLs, which results in a situation where the declared types used in the process are not yet available in the Drools ProjectClassloader when. the process is compiled.
> Easy fix is to compile the process after the rules, which makes sense as the rules will normally not really on processes, but processes can really on rules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (DROOLS-1327) Drools declared types cannot be references in jBPM Drools expressions due to compilation order.
by Duncan Doyle (JIRA)
Duncan Doyle created DROOLS-1327:
------------------------------------
Summary: Drools declared types cannot be references in jBPM Drools expressions due to compilation order.
Key: DROOLS-1327
URL: https://issues.jboss.org/browse/DROOLS-1327
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 6.4.0.Final
Environment: JBoss BPM Suite 6.3.3.GA
Reporter: Duncan Doyle
Assignee: Mario Fusco
When you declare a type in a DRL using the "declare" syntax, that type cannot be referenced by Drools LHS expressions in a Sequence Flow (for example in the context of an X-OR Gateway). The DRL and BPMN2 file are in the same project.
The problem is the order of compilation of CompositeKnowledgeBuilderImpl. The builder compiles the process definitions before the DRLs, which results in a situation where the declared types used in the process are not yet available in the Drools ProjectClassloader when. the process is compiled.
Easy fix is to compile the process after the rules, which makes sense as the rules will normally not really on processes, but processes can really on rules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (WFLY-6960) SFSB concurrent access timeout when the bean defines CDI producer for another SFSB
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/WFLY-6960?page=com.atlassian.jira.plugin.... ]
Tomas Remes commented on WFLY-6960:
-----------------------------------
Ah sorry. Sure
> SFSB concurrent access timeout when the bean defines CDI producer for another SFSB
> ----------------------------------------------------------------------------------
>
> Key: WFLY-6960
> URL: https://issues.jboss.org/browse/WFLY-6960
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final, 10.1.0.CR1
> Reporter: Tomas Remes
> Assignee: Enrique González Martínez
> Attachments: 0001-Use-EJB-as-opposed-to-Inject.patch, test-case.zip
>
>
> In the given scenario there are two calls to {{org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor#processInvocation}} in the same thread. In the first call the {{OwnableReentrantLock}} is obtained but it couldn't be reentered in the second call. This results to:
> {noformat}
> 14:54:21,184 ERROR [org.jboss.as.ejb3.invocation] (pool-2-thread-2) WFLYEJB0034: EJB Invocation failed on component SFBean1 for method public org.jboss.weld.tests.ejb.stateful.producer.Foo org.jboss.weld.tests.ejb.stateful.producer.SFBean1.produceString(): javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0228: EJB 3.1 FR 4.3.14.1 concurrent access timeout on SFBean1 - could not obtain lock within 5000 MILLISECONDS
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:86)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:65)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean1$$$view5.produceString(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436)
> at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127)
> at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean1$Proxy$_$$_Weld$EnterpriseProxy$.produceString(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
> at org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:99)
> at org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:161)
> at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:181)
> at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
> at org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:842)
> at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92)
> at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:378)
> at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:389)
> at org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71)
> at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
> at org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73)
> at org.jboss.weld.injection.producer.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:140)
> at org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39)
> at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.ejb.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.notSupported(CMTTxInterceptor.java:308)
> at org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:62)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.jpa.interceptor.SFSBPreCreateInterceptor.processInvocation(SFSBPreCreateInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:161)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:150)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:75)
> at org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:134)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:145)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.constructComponentInstance(StatefulSessionComponent.java:75)
> at org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:135)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createInstance(StatefulSessionComponent.java:75)
> at org.jboss.as.ejb3.cache.simple.SimpleCache.create(SimpleCache.java:118)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionComponent.createSession(StatefulSessionComponent.java:238)
> at org.jboss.as.weld.ejb.StatefulSessionObjectReferenceImpl.<init>(StatefulSessionObjectReferenceImpl.java:70)
> at org.jboss.as.weld.services.bootstrap.WeldEjbServices.resolveEjb(WeldEjbServices.java:53)
> at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:230)
> at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:83)
> at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:63)
> at org.jboss.weld.injection.producer.ejb.SessionBeanProxyInstantiator.createEnterpriseTargetBeanInstance(SessionBeanProxyInstantiator.java:80)
> at org.jboss.weld.injection.producer.ejb.SessionBeanProxyInstantiator.newInstance(SessionBeanProxyInstantiator.java:61)
> at org.jboss.weld.bean.SessionBean.create(SessionBean.java:149)
> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:96)
> at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
> at org.jboss.weld.bean.ContextualInstanceStrategy$CachingContextualInstanceStrategy.get(ContextualInstanceStrategy.java:178)
> at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:125)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean2$Proxy$_$$_WeldClientProxy.foo(Unknown Source)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean3.ping(SFBean3.java:19)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)
> at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:125)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:65)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
> at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
> at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean3$$$view6.ping(Unknown Source)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436)
> at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127)
> at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean3$Proxy$_$$_Weld$EnterpriseProxy$.ping(Unknown Source)
> at org.jboss.weld.tests.ejb.stateful.producer.SFBean3$Proxy$_$$_WeldClientProxy.ping(Unknown Source)
> at org.jboss.weld.tests.ejb.stateful.producer.ConcurrentAccessTest.test(ConcurrentAccessTest.java:31)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months