June 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-761) Not possible to overlay non existing file in WAR

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-761?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-761: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147352 > Not possible to overlay non existing file in WAR > ------------------------------------------------ > > Key: WFCORE-761 > URL: https://issues.jboss.org/browse/WFCORE-761 > Project: WildFly Core > Issue Type: Feature Request > Reporter: Bartosz Baranowski > Priority: Minor > > It is either bug in how deployments are treated or how overlay/vfs work. > Steps to reproduce: > 1. deploy undexploded war with jar inside > 2. add overlay that will add non existing file in jar > Result: exception: > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt > Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}} > at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67) > at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37) > at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76) > at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67) > Expectation: > should work. It actually does work, if war is really exploded or > 'if(exploded)' part in overlay is removed from overlay processor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-761) Not possible to overlay non existing file in WAR

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created WFCORE-761: ----------------------------------------- Summary: Not possible to overlay non existing file in WAR Key: WFCORE-761 URL: https://issues.jboss.org/browse/WFCORE-761 Project: WildFly Core Issue Type: Feature Request Reporter: Bartosz Baranowski Priority: Minor It is either bug in how deployments are treated or how overlay/vfs work. Steps to reproduce: 1. deploy undexploded war with jar inside 2. add overlay that will add non existing file in jar Result: exception: Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018776: Failed to get content for deployment overlay WEB-INF/lib/overlayed.jar//META-INF/x/file.txt at WEB-INF/lib/overlayed.jar//META-INF/x/file.txt Caused by: java.io.FileNotFoundException: /content/shell.war/WEB-INF/lib/overlayed.jar/META-INF/x/file.txt"}} at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:67) at org.jboss.as.test.integration.management.ManagementOperations.executeOperation(ManagementOperations.java:37) at org.jboss.as.test.integration.deployment.deploymentoverlay.jar.OverlayUtils.setupOverlay(OverlayUtils.java:76) at org.jboss.as.test.integration.deployment.deploymentoverlay.war.OverlayNonExistingResourceTestCase.testOverlay(OverlayNonExistingResourceTestCase.java:67) Expectation: should work. It actually does work, if war is really exploded or 'if(exploded)' part in overlay is removed from overlay processor. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4755) datasource:enable() operation lacks reload-requires state

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4755?page=com.atlassian.jira.plugin.... ] Stefano Maestri commented on WFLY-4755: --------------------------------------- Well, I'm going to reject this issue for various reasons: - both operations and attribute are deprecated because it's the RUNTIME stage concepts enabled/disabled to be deprecated and it will be removed from upstrema very soon w/ WFLY-4294 - it's correct to don't require a reload enabling a DS in disabled state. The bug could be on attribute, not in operation. It's in fact deploying a new DS, don't need to kill connections or whatever - it's correct to require a reload on an enabled resource if you don't use {allow-resource-service-restart=true}. It need to kill connections and other things. Feel free to contact me w/ private email/chat if you need any further depp dive on what is changing in DSes w/ WFLY-4294 regards S. > datasource:enable() operation lacks reload-requires state > ---------------------------------------------------------- > > Key: WFLY-4755 > URL: https://issues.jboss.org/browse/WFLY-4755 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Harald Pehl > Assignee: Stefano Maestri > > Executing {{:disable()}} on an enabled datasource sets the {{reload-requires}} state. This is in sync with changing the attribute directly using {{:write-attribute(name=enabled,value=false}} (which is deprecated). > However {{:enable()}} on a disabled datasource does not set the {{reload-requires}} state. Whereas {{:write-attribute(name=enabled,value=true}} does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4755) datasource:enable() operation lacks reload-requires state

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/WFLY-4755?page=com.atlassian.jira.plugin.... ] Stefano Maestri resolved WFLY-4755. ----------------------------------- Resolution: Rejected > datasource:enable() operation lacks reload-requires state > ---------------------------------------------------------- > > Key: WFLY-4755 > URL: https://issues.jboss.org/browse/WFLY-4755 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Harald Pehl > Assignee: Stefano Maestri > > Executing {{:disable()}} on an enabled datasource sets the {{reload-requires}} state. This is in sync with changing the attribute directly using {{:write-attribute(name=enabled,value=false}} (which is deprecated). > However {{:enable()}} on a disabled datasource does not set the {{reload-requires}} state. Whereas {{:write-attribute(name=enabled,value=true}} does. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4785) Cannot start persistence cache: CacheException

by Veli Cris (JIRA)

[ https://issues.jboss.org/browse/WFLY-4785?page=com.atlassian.jira.plugin.... ] Veli Cris updated WFLY-4785: ---------------------------- Description: Hi, I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you. org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl ConfigurationBuilder builder = new ConfigurationBuilder(); Configuration config = builder.persistence() .addStore(JdbcBinaryStoreConfigurationBuilder.class) .fetchPersistentState(false) .ignoreModifications(false) .purgeOnStartup(false) .table() .dropOnExit(true) .createOnStart(true) .tableNamePrefix("bean_session") .idColumnName("id").idColumnType("INT(11)") .dataColumnName("string").dataColumnType("TEXT") .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP") .connectionPool() .connectionUrl("jdbc:mysql://localhost:3306/bean") .username("root").password("1234567") .driverClass("com.mysql.jdbc.Driver").build(); DefaultCacheManager manager = new DefaultCacheManager(); manager.defineConfiguration("mycache", config); Cache cache = manager.getCache("mycache"); cache.put("1", "1"); cache.put("2", "2"); cache.put("3", "3"); cache.start(); was: Hi, I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you. ConfigurationBuilder builder = new ConfigurationBuilder(); Configuration config = builder.persistence() .addStore(JdbcBinaryStoreConfigurationBuilder.class) .fetchPersistentState(false) .ignoreModifications(false) .purgeOnStartup(false) .table() .dropOnExit(true) .createOnStart(true) .tableNamePrefix("bean_session") .idColumnName("id").idColumnType("INT(11)") .dataColumnName("string").dataColumnType("TEXT") .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP") .connectionPool() .connectionUrl("jdbc:mysql://localhost:3306/bean") .username("root").password("1234567") .driverClass("com.mysql.jdbc.Driver").build(); DefaultCacheManager manager = new DefaultCacheManager(); manager.defineConfiguration("mycache", config); Cache cache = manager.getCache("mycache"); cache.put("1", "1"); cache.put("2", "2"); cache.put("3", "3"); cache.start(); > Cannot start persistence cache: CacheException > ---------------------------------------------- > > Key: WFLY-4785 > URL: https://issues.jboss.org/browse/WFLY-4785 > Project: WildFly > Issue Type: Bug > Affects Versions: 8.2.0.Final > Environment: WildFly 8.2.0 Final / Linux > Reporter: Veli Cris > Assignee: Jason Greene > > Hi, > I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you. > org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl > ConfigurationBuilder builder = new ConfigurationBuilder(); > Configuration config = builder.persistence() > .addStore(JdbcBinaryStoreConfigurationBuilder.class) > .fetchPersistentState(false) > .ignoreModifications(false) > .purgeOnStartup(false) > .table() > .dropOnExit(true) > .createOnStart(true) > .tableNamePrefix("bean_session") > .idColumnName("id").idColumnType("INT(11)") > .dataColumnName("string").dataColumnType("TEXT") > .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP") > .connectionPool() > .connectionUrl("jdbc:mysql://localhost:3306/bean") > .username("root").password("1234567") > .driverClass("com.mysql.jdbc.Driver").build(); > DefaultCacheManager manager = new DefaultCacheManager(); > manager.defineConfiguration("mycache", config); > Cache cache = manager.getCache("mycache"); > cache.put("1", "1"); > cache.put("2", "2"); > cache.put("3", "3"); > > cache.start(); -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4785) Cannot start persistence cache: CacheException

by Veli Cris (JIRA)

Veli Cris created WFLY-4785: ------------------------------- Summary: Cannot start persistence cache: CacheException Key: WFLY-4785 URL: https://issues.jboss.org/browse/WFLY-4785 Project: WildFly Issue Type: Bug Affects Versions: 8.2.0.Final Environment: WildFly 8.2.0 Final / Linux Reporter: Veli Cris Assignee: Jason Greene Hi, I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you. ConfigurationBuilder builder = new ConfigurationBuilder(); Configuration config = builder.persistence() .addStore(JdbcBinaryStoreConfigurationBuilder.class) .fetchPersistentState(false) .ignoreModifications(false) .purgeOnStartup(false) .table() .dropOnExit(true) .createOnStart(true) .tableNamePrefix("bean_session") .idColumnName("id").idColumnType("INT(11)") .dataColumnName("string").dataColumnType("TEXT") .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP") .connectionPool() .connectionUrl("jdbc:mysql://localhost:3306/bean") .username("root").password("1234567") .driverClass("com.mysql.jdbc.Driver").build(); DefaultCacheManager manager = new DefaultCacheManager(); manager.defineConfiguration("mycache", config); Cache cache = manager.getCache("mycache"); cache.put("1", "1"); cache.put("2", "2"); cache.put("3", "3"); cache.start(); -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1909) Add an AZURE_PING protocol

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1909?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-1909: -------------------------------- 18 KLOC for AZURE_PING is way too big ! Let's either try to reduce the size or make this protocol a separate project on GitHub, similar to jgroups-raft. That way, it could have dependencies. > Add an AZURE_PING protocol > -------------------------- > > Key: JGRP-1909 > URL: https://issues.jboss.org/browse/JGRP-1909 > Project: JGroups > Issue Type: Feature Request > Reporter: Tristan Tarrant > Assignee: Radoslav Husar > Fix For: 3.6.4 > > > Similar to the existing S3_PING and GOOGLE_PING, add an AZURE_PING which suppors node discovery using Azure's blob storage. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-814) Unable to redeclare classes with more specific, overriding accessors

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-814?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-814. -------------------------------- Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/2c000f251 > Unable to redeclare classes with more specific, overriding accessors > -------------------------------------------------------------------- > > Key: DROOLS-814 > URL: https://issues.jboss.org/browse/DROOLS-814 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Beta1 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.3.0.Beta2 > > > "Declares" do not support the following use case: > {code} > declare A > fld : Object > end > declare B extends A > fld : String // more specific type > end > {code} > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-819) Create patch release for align with Fuse and Fuse-integration versions

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-819: ---------------------------------- Summary: Create patch release for align with Fuse and Fuse-integration versions Key: DROOLS-819 URL: https://issues.jboss.org/browse/DROOLS-819 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-753) When WFCORE is run as a service in linux, the working directory is "/"

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFCORE-753?page=com.atlassian.jira.plugin... ] Carlo de Wolf updated WFCORE-753: --------------------------------- Priority: Major (was: Minor) > When WFCORE is run as a service in linux, the working directory is "/" > ---------------------------------------------------------------------- > > Key: WFCORE-753 > URL: https://issues.jboss.org/browse/WFCORE-753 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Bartosz Baranowski > Assignee: Tomaz Cerar > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2015