January 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6327) Create JPA service callback for invoking database migration

by Anil Arora (JIRA)

[ https://issues.jboss.org/browse/AS7-6327?page=com.atlassian.jira.plugin.s... ] Anil Arora commented on AS7-6327: --------------------------------- Is there a way to accomplish this with the lifecycle-listener? I've been trying to find documentation on this, but was able to find anything that could help me here. > Create JPA service callback for invoking database migration > ----------------------------------------------------------- > > Key: AS7-6327 > URL: https://issues.jboss.org/browse/AS7-6327 > Project: Application Server 7 > Issue Type: Feature Request > Components: JPA / Hibernate > Affects Versions: 7.1.3.Final (EAP) > Reporter: Anil Arora > Assignee: Scott Marlow > > Looking for a simple callback/listener mechanism so that we can invoke a database migration script before JPA persistent unit starts up and runs the Hibernate schema validation mechanism. > Ideally, there would be a property within the persistence.xml that indicates which class to call. It would also pass in/inject the datasource that is being used for the persistence unit. > Essentially, this would solve the lack of migration support in Hibernate itself. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3722) Ruleflow only executes all ruleflow-groups one time in Stateless session after drools-server restart

by Tim Slonaker (JIRA)

Tim Slonaker created JBRULES-3722: ------------------------------------- Summary: Ruleflow only executes all ruleflow-groups one time in Stateless session after drools-server restart Key: JBRULES-3722 URL: https://issues.jboss.org/browse/JBRULES-3722 Project: JBRULES Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (flow), drools-spring Affects Versions: 5.5.0.Final, 5.4.0.Final Environment: Windows 7 Ultimate 64-bit Service Pack 1 Intel Core 2 Duo CPU 4 GB Ram Java Version 7 Update 11 JBoss 7.1.1 AS Guvnor 5.5.0.Final Drools-server 5.5.0.Final Reporter: Tim Slonaker Assignee: Mark Proctor Given a simple ruleflow: *START --> Step1 --> Step2 --> Step3 --> END* When the drools-server has just been started the rules and ruleflow-groups execute correctly. All ruleflow-groups (Step1, Step2, and Step3) are hit. The second rule execution request does not work correctly. Only ruleflow-group Step1 is hit. From that point on ruleflow-groups Step2 and Step3 are not hit until the drools-server is restarted. I am using the following batch-execution commands in this order: insert, start-process, fire-all-rules, get-objects. If I use the exact same commands in the same order from a Java project instead of using drools-server then it works correctly every time. All ruleflow-group nodes are executed properly every time for a stateless session. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-6379) Intermittent failures in RespawnTestCase

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6379?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6379: --------------------------------------- I changed the test to keep trying for a while after the 1st time it sees that neither server is visibile via lookupServerInModel(MASTER, SERVER_xxx). If servers are re-registering hopefully this will result in a more informative failure that we can then diagnose and address. > Intermittent failures in RespawnTestCase > ---------------------------------------- > > Key: AS7-6379 > URL: https://issues.jboss.org/browse/AS7-6379 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 7.2.0.CR1 > > > Problems like [1] still pop up fairly frequently. It seems the same 3 tests fail. > Failed tests: testReloadHcButNotServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > testReloadHcButNotServersWithFailedServer(org.jboss.as.test.integration.respawn.RespawnTestCase) testHCReloadAbortPreservesServers(org.jboss.as.test.integration.respawn.RespawnTestCase) > [1] http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-ignore/... -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-5711) Add resteasy hibernate-validator-provider

by Mathieu Lachance (JIRA)

[ https://issues.jboss.org/browse/AS7-5711?page=com.atlassian.jira.plugin.s... ] Mathieu Lachance updated AS7-5711: ---------------------------------- Forum Reference: https://community.jboss.org/message/763525, https://community.jboss.org/thread/212055 (was: https://community.jboss.org/message/763525) > Add resteasy hibernate-validator-provider > ----------------------------------------- > > Key: AS7-5711 > URL: https://issues.jboss.org/browse/AS7-5711 > Project: Application Server 7 > Issue Type: Feature Request > Components: REST > Affects Versions: 7.1.3.Final (EAP) > Reporter: Mathieu Lachance > Assignee: Stuart Douglas > Fix For: 7.2.0.Alpha1 > > > the hibernate-validator-provider is not bundled with resteasy. > javax.validation annotations doesn't seem to work as detailed in the forum post. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3721) Accumulate + declared EntryPoint causes NullPointerException

by Mariano De Maio (JIRA)

[ https://issues.jboss.org/browse/JBRULES-3721?page=com.atlassian.jira.plug... ] Mariano De Maio updated JBRULES-3721: ------------------------------------- Attachment: CepBug.tar.gz Test project attached > Accumulate + declared EntryPoint causes NullPointerException > ------------------------------------------------------------ > > Key: JBRULES-3721 > URL: https://issues.jboss.org/browse/JBRULES-3721 > Project: JBRULES > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools-core (fusion) > Affects Versions: 5.5.0.Final > Reporter: Mariano De Maio > Assignee: Mark Proctor > Attachments: CepBug.tar.gz > > > When creating a declared entry point that uses a window, and using it with an Accumulate function in the same rule, this error occurrs: > org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.rule.SlidingTimeWindow$BehaviorExpireWMAction@57e40274 > at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:995) > This error doesn't occurr when removing the Accumulate function or extending the expiration time of the window > A project that reproduces this error will be attached on the next comment. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3721) Accumulate + declared EntryPoint causes NullPointerException

by Mariano De Maio (JIRA)

Mariano De Maio created JBRULES-3721: ---------------------------------------- Summary: Accumulate + declared EntryPoint causes NullPointerException Key: JBRULES-3721 URL: https://issues.jboss.org/browse/JBRULES-3721 Project: JBRULES Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.5.0.Final Reporter: Mariano De Maio Assignee: Mark Proctor When creating a declared entry point that uses a window, and using it with an Accumulate function in the same rule, this error occurrs: org.drools.RuntimeDroolsException: Unexpected exception executing action org.drools.rule.SlidingTimeWindow$BehaviorExpireWMAction@57e40274 at org.drools.common.AbstractWorkingMemory.executeQueuedActions(AbstractWorkingMemory.java:995) This error doesn't occurr when removing the Accumulate function or extending the expiration time of the window A project that reproduces this error will be attached on the next comment. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (AS7-3414) Symbolic links inside deployed ear/war are not followed by web server

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-3414?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-3414: ---------------------------------- Fix Version/s: (was: No Release) > Symbolic links inside deployed ear/war are not followed by web server > --------------------------------------------------------------------- > > Key: AS7-3414 > URL: https://issues.jboss.org/browse/AS7-3414 > Project: Application Server 7 > Issue Type: Bug > Components: Web > Affects Versions: 7.2.0.Alpha1 > Environment: Fedora 16 > Reporter: Ronen Angluster > Assignee: Navin Surtani > > when creating a symbolic link inside a deployed ear/war the symbolic link's target is not followed when > accessing it from a web browser > i.e. > in jboss-as/standalone/deplyoment/somedomain.ear/files we created a symbolic link named "version.js" > which points to /usr/share/something/version.js > the target file (/usr/share/...) is accessible by all (chmod'd to 777) and is readable by the jboss-as user which runs > the Jboss application server. > when accessing http://domain:8080/something/files/version.js we get an 404 error, seems like the file is not found by > the server. > when placing the file instead of symbolic link, the file is accessible and all is well -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1556) Incorrect error log message in RequestCorrelator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1556: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> changed the Status of [bug 888429|https://bugzilla.redhat.com/show_bug.cgi?id=888429] from ON_QA to ASSIGNED > Incorrect error log message in RequestCorrelator > ------------------------------------------------ > > Key: JGRP-1556 > URL: https://issues.jboss.org/browse/JGRP-1556 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.4 > Reporter: Michal Linhard > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2.6, 3.3 > > > I have this when running JDG 6.1.0.ER6 with JGroups 3.2.4 > {code} > 08:31:41,460 ERROR [org.jgroups.blocks.RequestCorrelator] failed sending rsp: return value (SuccessfulResponse{responseValue=null} ) is not serializable > {code} > which is of course not the cause of the error. > This message is logged when any Throwable is caught > https://github.com/belaban/JGroups/blob/26b7c60d511baf199674b45d3d402dfbb... > in my case it was once NullPointerException and once InterruptedException probably caused by caches and externalizers shutting down. > I'd recommend rewording of the message if the exception is not NotSerializableException or the like to avoid confusion. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1556) Incorrect error log message in RequestCorrelator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JGRP-1556: ------------------------------------------ Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=888429) > Incorrect error log message in RequestCorrelator > ------------------------------------------------ > > Key: JGRP-1556 > URL: https://issues.jboss.org/browse/JGRP-1556 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.4 > Reporter: Michal Linhard > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2.6, 3.3 > > > I have this when running JDG 6.1.0.ER6 with JGroups 3.2.4 > {code} > 08:31:41,460 ERROR [org.jgroups.blocks.RequestCorrelator] failed sending rsp: return value (SuccessfulResponse{responseValue=null} ) is not serializable > {code} > which is of course not the cause of the error. > This message is logged when any Throwable is caught > https://github.com/belaban/JGroups/blob/26b7c60d511baf199674b45d3d402dfbb... > in my case it was once NullPointerException and once InterruptedException probably caused by caches and externalizers shutting down. > I'd recommend rewording of the message if the exception is not NotSerializableException or the like to avoid confusion. -- 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

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1556) Incorrect error log message in RequestCorrelator

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JGRP-1556?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JGRP-1556: ----------------------------------------------- Michal Linhard <mlinhard(a)redhat.com> made a comment on [bug 888429|https://bugzilla.redhat.com/show_bug.cgi?id=888429] Resolution of JGRP-1556 only helped to show that the root cause behind this a NPE: http://www.qa.jboss.com/~mlinhard/hyperion3/run0038-startup-ER9/report/lo... the actual NPE cause is ISPN-2751 so this is still present in JDG 6.1.0.ER9, however impact of this bug is near zero. > Incorrect error log message in RequestCorrelator > ------------------------------------------------ > > Key: JGRP-1556 > URL: https://issues.jboss.org/browse/JGRP-1556 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.2.4 > Reporter: Michal Linhard > Assignee: Bela Ban > Priority: Minor > Fix For: 3.2.6, 3.3 > > > I have this when running JDG 6.1.0.ER6 with JGroups 3.2.4 > {code} > 08:31:41,460 ERROR [org.jgroups.blocks.RequestCorrelator] failed sending rsp: return value (SuccessfulResponse{responseValue=null} ) is not serializable > {code} > which is of course not the cause of the error. > This message is logged when any Throwable is caught > https://github.com/belaban/JGroups/blob/26b7c60d511baf199674b45d3d402dfbb... > in my case it was once NullPointerException and once InterruptedException probably caused by caches and externalizers shutting down. > I'd recommend rewording of the message if the exception is not NotSerializableException or the like to avoid confusion. -- 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

13 years, 5 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 January 2013