October 2014 - arquillian-issues - Jboss List Archives

[JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1874: ----------------------------- Description: It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. Storage should be completely ignored if remoteReusable is not set. was:It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1874?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1874: ----------------------------- Issue Type: Bug (was: Feature Request) > Allow Drone to skip session file creation > ----------------------------------------- > > Key: ARQ-1874 > URL: https://issues.jboss.org/browse/ARQ-1874 > Project: Arquillian > Issue Type: Bug > Components: Extension - Drone > Affects Versions: drone_2.0.0.Alpha2 > Reporter: Karel Piwko > > It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. > Storage should be completely ignored if remoteReusable is not set. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1874) Allow Drone to skip session file creation

by Karel Piwko (JIRA)

Karel Piwko created ARQ-1874: -------------------------------- Summary: Allow Drone to skip session file creation Key: ARQ-1874 URL: https://issues.jboss.org/browse/ARQ-1874 Project: Arquillian Issue Type: Feature Request Components: Extension - Drone Affects Versions: drone_2.0.0.Alpha2 Reporter: Karel Piwko It should be possible not to touch filesystem and avoid creating session file if user wishes to do so. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1873) @ServerSetup annotation is not inherited by JUnit test classes.

by Richard Rattigan (JIRA)

Richard Rattigan created ARQ-1873: ------------------------------------- Summary: @ServerSetup annotation is not inherited by JUnit test classes. Key: ARQ-1873 URL: https://issues.jboss.org/browse/ARQ-1873 Project: Arquillian Issue Type: Bug Affects Versions: 1.1.5.Final Environment: I'm using JUnit. Reporter: Richard Rattigan Code below does not work as expected - {{MySetup}} is not run: {code} @ServerSetup(MySetup.class) public class BaseTest {...} public class MyTest1 extends BaseTest {...} public class MyTest2 extends BaseTest {...} {code} Workaround is to repeat the annotation on every test class: {code} public class BaseTest {...} @ServerSetup(MySetup.class) public class MyTest1 extends BaseTest {...} @ServerSetup(MySetup.class) public class MyTest2 extends BaseTest {...} {code} I haven't tested this with other test frameworks, just JUnit. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1871) Improve documentation in arquillian spock

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1871?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1871: -------------------------------- Fix Version/s: spock_1.0.0.next > Improve documentation in arquillian spock > ----------------------------------------- > > Key: ARQ-1871 > URL: https://issues.jboss.org/browse/ARQ-1871 > Project: Arquillian > Issue Type: Enhancement > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta3 > Reporter: John Ament > Assignee: Bartosz Majsak > Priority: Minor > Fix For: spock_1.0.0.next > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1871) Improve documentation in arquillian spock

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1871?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak reopened ARQ-1871: --------------------------------- > Improve documentation in arquillian spock > ----------------------------------------- > > Key: ARQ-1871 > URL: https://issues.jboss.org/browse/ARQ-1871 > Project: Arquillian > Issue Type: Enhancement > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta3 > Reporter: John Ament > Assignee: Bartosz Majsak > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1871) Improve documentation in arquillian spock

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1871?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak resolved ARQ-1871. --------------------------------- Resolution: Done > Improve documentation in arquillian spock > ----------------------------------------- > > Key: ARQ-1871 > URL: https://issues.jboss.org/browse/ARQ-1871 > Project: Arquillian > Issue Type: Enhancement > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta3 > Reporter: John Ament > Assignee: Bartosz Majsak > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1871) Improve documentation in arquillian spock

by Bartosz Majsak (JIRA)

[ https://issues.jboss.org/browse/ARQ-1871?page=com.atlassian.jira.plugin.s... ] Bartosz Majsak updated ARQ-1871: -------------------------------- Status: Closed (was: Pull Request Sent) Resolution: Done [Pushed upstream|https://github.com/arquillian/arquillian-testrunner-spock/commit...]. > Improve documentation in arquillian spock > ----------------------------------------- > > Key: ARQ-1871 > URL: https://issues.jboss.org/browse/ARQ-1871 > Project: Arquillian > Issue Type: Enhancement > Components: Spock TestRunner > Affects Versions: spock_1.0.0.Beta3 > Reporter: John Ament > Assignee: Bartosz Majsak > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1872) cannot use custom dialect

by Karl Pietrzak (JIRA)

Karl Pietrzak created ARQ-1872: ---------------------------------- Summary: cannot use custom dialect Key: ARQ-1872 URL: https://issues.jboss.org/browse/ARQ-1872 Project: Arquillian Issue Type: Bug Components: JBoss AS Containers Environment: arquillian_core 1.1.5.Final wildfly 8.1.0.Final wildfly-arquillian-container-embedded 8.1.0.Final Reporter: Karl Pietrzak h3. Short Description You can't use a custom dialect because you'll get a {{HibernateException}}: {noformat} org.hibernate.HibernateException: Unable to construct requested dialect [com.mycompany.hibernate.MySQLBitBooleanDialect] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_67] at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:474) [wildfly-security-manager-1.0.0.Final.jar:1.0.0.Final] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.1.Final.jar:2.1.1.Final] Caused by: org.hibernate.HibernateException: Unable to construct requested dialect [com.mycompany.hibernate.MySQLBitBooleanDialect] at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.constructDialect(DialectFactoryImpl.java:88) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:68) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:165) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) [jipijapa-hibernate4-3-1.0.1.Final.jar:] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] ... 8 more Caused by: java.lang.ClassCastException: com.mycompany.hibernate.MySQLBitBooleanDialect cannot be cast to org.hibernate.dialect.Dialect at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.constructDialect(DialectFactoryImpl.java:78) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] ... 21 more {noformat} My WAG is that it's a classloader issue. h3. Longer Version Some more info is in server.log: {noformat} 2014-10-18 18:26:58,736 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 17) MSC000001: Failed to start service jboss.persistenceunit."test.war#myproject_db-pu-web": org.jboss.msc.service.StartException in service jboss.persistenceunit."test.war#myproject_db-pu-web": org.hibernate.boot.registry.selector.spi.StrategySelectionException: Unable to resolve name [com.mycompany.hibernate.MySQLBitBooleanDialect] as strategy [org.hibernate.dialect.Dialect] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_67] at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:474) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: org.hibernate.boot.registry.selector.spi.StrategySelectionException: Unable to resolve name [com.mycompany.hibernate.MySQLBitBooleanDialect] as strategy [org.hibernate.dialect.Dialect] at org.hibernate.boot.registry.selector.internal.StrategySelectorImpl.selectStrategyImplementor(StrategySelectorImpl.java:128) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.selector.internal.StrategySelectorImpl.resolveDefaultableStrategy(StrategySelectorImpl.java:155) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.selector.internal.StrategySelectorImpl.resolveStrategy(StrategySelectorImpl.java:136) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.constructDialect(DialectFactoryImpl.java:78) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:68) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:165) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:111) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:234) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:206) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1885) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1843) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:850) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:843) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:397) [hibernate-core-4.3.5.Final.jar:4.3.5.Final] at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:842) [hibernate-entitymanager-4.3.5.Final.jar:4.3.5.Final] at org.jboss.as.jpa.hibernate4.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) [jipijapa-hibernate4-3-1.0.1.Final.jar:] at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154) [wildfly-jpa-8.1.0.Final.jar:8.1.0.Final] ... 8 more {noformat} h3. Files {code:xml|title=persistence.xml} ?xml version="1.0" encoding="UTF-8"?> <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd"> <persistence-unit name="maars_db-pu" transaction-type="JTA"> <jta-data-source>java:jboss/datasources/mycompany-ds</jta-data-source> <exclude-unlisted-classes>false</exclude-unlisted-classes> <properties> <property name="hibernate.dialect" value="com.mycompany.hibernate.MySQLBitBooleanDialect" /> <property name="hibernate.hbm2ddl.auto" value="validate" /> <property name="hibernate.show_sql" value="false" /> <property name="hibernate.format_sql" value="false" /> </properties> </persistence-unit> </persistence> {code} h3. Related Issues I thought this was because of https://hibernate.atlassian.net/browse/HHH-7084, but it looks like this was resolved a while ago. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ARQ-1867) Recognize Spacelift threads from all others regarding of a thread name

by Karel Piwko (JIRA)

[ https://issues.jboss.org/browse/ARQ-1867?page=com.atlassian.jira.plugin.s... ] Karel Piwko updated ARQ-1867: ----------------------------- Fix Version/s: spacelift_1.0.0.Alpha3 > Recognize Spacelift threads from all others regarding of a thread name > ---------------------------------------------------------------------- > > Key: ARQ-1867 > URL: https://issues.jboss.org/browse/ARQ-1867 > Project: Arquillian > Issue Type: Feature Request > Components: Extension - Spacelift > Affects Versions: spacelift_1.0.0.Alpha2 > Reporter: Stefan Miklosovic > Assignee: Stefan Miklosovic > Fix For: spacelift_1.0.0.Alpha3 > > > It is hard to distinguish between Spacelift threads and all other threads in the system. > ExecutorServiceImpl creates executor services via Executors.newCachedThreadPool and Executors.newScheduledThreadPool(1) which are naming threads like "pool-1-thread-_number" and it is hard to make a difference what is Spacelift related and what is not in tools like jvisualvm or jconsole. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

arquillian-issues October 2014