[JBoss JIRA] (ARQ-1009) ClassNotFoundException when using CLEAN_INSERT
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1009?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-1009:
--------------------------------
Fix Version/s: persistence_1.0.0.next
> ClassNotFoundException when using CLEAN_INSERT
> ----------------------------------------------
>
> Key: ARQ-1009
> URL: https://issues.jboss.org/browse/ARQ-1009
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha4
> Environment: Windows 7, Java 1.6.0_31
> Reporter: Karsten Ohme
> Fix For: persistence_1.0.0.next
>
>
> I set in arquillian.xml the configuration property:
> <property name="dataSeedStrategy">CLEAN_INSERT</property>
> When starting the test I get a ClassNotFoundException in ConfigurationTypeConverter in line 182:
> Object instance = Class.forName(value).newInstance();
--
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, 3 months
[JBoss JIRA] (ARQ-1440) Performance drops > 300%
by Bartosz Majsak (JIRA)
[ https://issues.jboss.org/browse/ARQ-1440?page=com.atlassian.jira.plugin.s... ]
Bartosz Majsak updated ARQ-1440:
--------------------------------
Fix Version/s: persistence_1.0.0.next
> Performance drops > 300%
> ------------------------
>
> Key: ARQ-1440
> URL: https://issues.jboss.org/browse/ARQ-1440
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Persistence
> Affects Versions: transaction_1.0.0.Alpha3, persistence_1.0.0.Alpha6
> Environment: Windows 7 / JDK 1.7.0_25 x64 / Oracle 11gR2 / Oracle ojdbc6 driver / Glassfish 3.1.2 b23 / Arquillian 1.1.0-Final / Arq persistence ext 1.0.0a6 / Arq tx ext 1.0.0a3
> Reporter: Noah White
> Assignee: Bartosz Majsak
> Priority: Critical
> Fix For: persistence_1.0.0.next
>
>
> I updated my Arquillian environment to 1.1.0-Final, Arq persistence ext 1.0.0a6 and Arq 1.0.0a3 FROM Arq 1.0.1, persistence 1.0.0a5 (no tx ext in that env since it was part of the persistence ext) and my Arquillian persistence tests which deploy to a managed Glassfish container take over 3x as long as they did in the old environment.
> For example one test which took 13s to run in the old environment now takes 44s.
> This slow down only seems to affect tests which use the persistence extension.
> Arquillian tests which do not use the persistence extension take the same amount of time as they did in the old environment. If I switch the environment back I see the performance goes back up for persistence extension tests.
--
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, 3 months
[JBoss JIRA] (ARQ-1656) Propogate Contextual operations on HttpFilters
by Aslak Knutsen (JIRA)
Aslak Knutsen created ARQ-1656:
----------------------------------
Summary: Propogate Contextual operations on HttpFilters
Key: ARQ-1656
URL: https://issues.jboss.org/browse/ARQ-1656
Project: Arquillian
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha6
Environment: Arquillian Core 1.1.3
Reporter: Aslak Knutsen
Warp reactivates Context's when creating the client side HttpFilters, but not when executing the actual filtering.
In Arquillian Core 1.1.3 the InheritableThreadLocal were removed which now expose this bug.
--
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, 3 months
[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1654:
------------------------------------
Possible some of the ProcessExecutor could go to container-spi as well. or some managed-container-spi.
> Expose an ExecutorService to help Extension with multithreading
> ---------------------------------------------------------------
>
> Key: ARQ-1654
> URL: https://issues.jboss.org/browse/ARQ-1654
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Base Implementation
> Affects Versions: 1.1.3.Final
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Fix For: 2.0.0.Beta1
>
>
> Expose a Service to execute Callable's and Runnable's within a Inherited context.
> The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread.
> ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely.
> The submit\(\*\) methods should probably be enough.
--
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, 3 months
[JBoss JIRA] (ARQ-1654) Expose an ExecutorService to help Extension with multithreading
by Aslak Knutsen (JIRA)
[ https://issues.jboss.org/browse/ARQ-1654?page=com.atlassian.jira.plugin.s... ]
Aslak Knutsen commented on ARQ-1654:
------------------------------------
The other way around :) But yeah. ProcessExecutor could use the ExecutorService in core.
> Expose an ExecutorService to help Extension with multithreading
> ---------------------------------------------------------------
>
> Key: ARQ-1654
> URL: https://issues.jboss.org/browse/ARQ-1654
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Base Implementation
> Affects Versions: 1.1.3.Final
> Reporter: Aslak Knutsen
> Assignee: Aslak Knutsen
> Fix For: 2.0.0.Beta1
>
>
> Expose a Service to execute Callable's and Runnable's within a Inherited context.
> The general idea is to hide the complexity of reactivating the current Contextual information on the new Thread.
> ExecutorService needs to be a limited view of the java.utl.concurrent.ExecutorService to avoid 'abuse' like shutdown being called prematurely.
> The submit\(\*\) methods should probably be enough.
--
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, 3 months
[JBoss JIRA] (ARQ-1655) NPE in WebDriverFactory.createInstance()
by Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/ARQ-1655?page=com.atlassian.jira.plugin.s... ]
Juergen Zimmermann updated ARQ-1655:
------------------------------------
Attachment: stacktrace.txt
dependency-tree.txt
arquillian.xml
> NPE in WebDriverFactory.createInstance()
> ----------------------------------------
>
> Key: ARQ-1655
> URL: https://issues.jboss.org/browse/ARQ-1655
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Drone
> Affects Versions: 1.1.3.Final
> Reporter: Juergen Zimmermann
> Attachments: arquillian.xml, dependency-tree.txt, stacktrace.txt
>
>
> When I try to run my tests for Firefox (also Chrome and HtmlUnit) I'm getting the attached stacktrace.
> I also attach the output of "mvn dependency:tree" and arquillian.xml.
> My appserver is WildFly 8.0.0.Final.
--
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, 3 months