April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6925) ignore CNFE when scanning for entity classes in deployment

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/AS7-6925?page=com.atlassian.jira.plugin.s... ] Scott Marlow commented on AS7-6925: ----------------------------------- I would be guessing if I said what is, without checking the classloading code that probably experienced the OOM and threw the CNFE. I guess I do have an opinion on this after all. ;) This also will help with the case that the deployment contains a class that isn't needed but references other classes that don't exist in the deployment (that is the case that is worth ignoring/logging the CNFE for). > ignore CNFE when scanning for entity classes in deployment > ---------------------------------------------------------- > > Key: AS7-6925 > URL: https://issues.jboss.org/browse/AS7-6925 > Project: Application Server 7 > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 7.1.2.Final (EAP), 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 8.0.0.Alpha1 > > Attachments: cnfe.jar > > > Deployments may contain non-entity classes that can not be loaded (see above forum reference for example). -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-42) execute-commands only executes commands that translate into operations

by James Perkins (JIRA)

James Perkins created JBASMP-42: ----------------------------------- Summary: execute-commands only executes commands that translate into operations Key: JBASMP-42 URL: https://issues.jboss.org/browse/JBASMP-42 Project: JBoss AS Maven Plugins Issue Type: Bug Reporter: James Perkins Assignee: James Perkins Commands like {{module add}} do not work in the {{execute-commands}} goal. See the {{CommandContext.handle()}} on how to execute these commands. Need to look at more details on how this method works and if it will work correctly without a shell. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ] James Perkins commented on JBASMP-41: ------------------------------------- This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command. FWIW the config would look like: {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.6</version> <executions> <execution> <goals> <goal>properties</goal> </goals> </execution> </executions> </plugin>  <plugin> <groupId>org.jboss.as.plugins</groupId> <artifactId>jboss-as-maven-plugin</artifactId> <version>${version.jboss.maven.plugin}</version> <executions> <execution> <id>create-modules</id> <phase>package</phase> <goals> <goal>execute-commands</goal> </goals> <configuration> <execute-commands> <commands> <command>module add --name=oracle.jdbc --resources=${com.oracle:ojdbc6:jar} --dependencies=javax.api,javax.transaction.api </command> </commands> </execute-commands> </configuration> </execution> </executions> </plugin> {code} > Create goals to add modules do Jboss AS > --------------------------------------- > > Key: JBASMP-41 > URL: https://issues.jboss.org/browse/JBASMP-41 > Project: JBoss AS Maven Plugins > Issue Type: Feature Request > Reporter: Gustavo Orair > Assignee: James Perkins > > A command to create modules using Jboss CLI was created > (refer to https://issues.jboss.org/browse/AS7-4265). > It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section. > Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located: > <execution> > <id>create-modules</id> > <phase>install</phase> > <goals> > <goal>execute-commands</goal> > </goals> > <configuration> > <execute-commands> > <commands> > <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command> > </commands> > </execute-commands> > </configuration> > </execution> -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-41) Create goals to add modules do Jboss AS

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBASMP-41?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on JBASMP-41 at 4/18/13 5:55 PM: -------------------------------------------------------------- This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command. FWIW the config would look like if the command worked: {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.6</version> <executions> <execution> <goals> <goal>properties</goal> </goals> </execution> </executions> </plugin>  <plugin> <groupId>org.jboss.as.plugins</groupId> <artifactId>jboss-as-maven-plugin</artifactId> <version>${version.jboss.maven.plugin}</version> <executions> <execution> <id>create-modules</id> <phase>package</phase> <goals> <goal>execute-commands</goal> </goals> <configuration> <execute-commands> <commands> <command>module add --name=oracle.jdbc --resources=${com.oracle:ojdbc6:jar} --dependencies=javax.api,javax.transaction.api </command> </commands> </execute-commands> </configuration> </execution> </executions> </plugin> {code} was (Author: jamezp): This could be done with the {{maven-dependency-plugin}}, but when testing I realized commands are property handled in the plugin. Since the modules command is an actual command and not an operation it fails to create execute. This needs to be fixed first, but it could be more intuitive to have a goal like you suggest rather than relying on the command. FWIW the config would look like: {code:xml} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.6</version> <executions> <execution> <goals> <goal>properties</goal> </goals> </execution> </executions> </plugin>  <plugin> <groupId>org.jboss.as.plugins</groupId> <artifactId>jboss-as-maven-plugin</artifactId> <version>${version.jboss.maven.plugin}</version> <executions> <execution> <id>create-modules</id> <phase>package</phase> <goals> <goal>execute-commands</goal> </goals> <configuration> <execute-commands> <commands> <command>module add --name=oracle.jdbc --resources=${com.oracle:ojdbc6:jar} --dependencies=javax.api,javax.transaction.api </command> </commands> </execute-commands> </configuration> </execution> </executions> </plugin> {code} > Create goals to add modules do Jboss AS > --------------------------------------- > > Key: JBASMP-41 > URL: https://issues.jboss.org/browse/JBASMP-41 > Project: JBoss AS Maven Plugins > Issue Type: Feature Request > Reporter: Gustavo Orair > Assignee: James Perkins > > A command to create modules using Jboss CLI was created > (refer to https://issues.jboss.org/browse/AS7-4265). > It should be nice if one may create these modules on Jboss server referencing a maven dependency similarly to deploy-artifact configuration section. > Maybe a possible workaround for now should be use execute-commands but it would need to locate where the maven depencies are located: > <execution> > <id>create-modules</id> > <phase>install</phase> > <goals> > <goal>execute-commands</goal> > </goals> > <configuration> > <execute-commands> > <commands> > <command>module add --name=oracle.jdbc --resources=ojdbc6.jar --dependencies=javax.api,javax.transaction.api</command> > </commands> > </execute-commands> > </configuration> > </execution> -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6948) Login configuration does not work for custom mail server

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-6948: -------------------------------- Summary: Login configuration does not work for custom mail server Key: AS7-6948 URL: https://issues.jboss.org/browse/AS7-6948 Project: Application Server 7 Issue Type: Bug Components: Mail Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Tomaz Cerar Assignee: Tomaz Cerar You cannot configure and use login configuration when having custom server. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] Thanks. To clarify my last clarification .... ;) If the composite operation mentioned in Michal's comment of Apri 16 works, IMHO there is no blocker, and no remaining "Bug", and at most an RFE for a later release. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] As I stated in [1] on 2013-04-16, the composite operation mentioned _in that comment_ works. My previous error was in using a malformed command. [1] https://bugzilla.redhat.com/show_bug.cgi?id=900801#c11 > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6946) Redesign web session clustering

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6946?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6946: --------------------------------------- Sounds good. Alpha1 is scheduled for May 6. Please reschedule. :) > Redesign web session clustering > ------------------------------- > > Key: AS7-6946 > URL: https://issues.jboss.org/browse/AS7-6946 > Project: Application Server 7 > Issue Type: Task > Components: Clustering > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 8.0.0.Alpha1 > > > The current web session replication code has been around for ages and suffers from a number of issues: > * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing. > * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache. > * Extra logic/locking is required to invalidate the local session map is required per request > * AtomicMaps, on which the currently implementation relies, have proven buggy > * Session access outside of the scope of the replication valve is possible and problematic > * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities. > * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication. > The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6947) Leverage Infinispan async api for clean shutdown

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-6947: --------------------------------- Summary: Leverage Infinispan async api for clean shutdown Key: AS7-6947 URL: https://issues.jboss.org/browse/AS7-6947 Project: Application Server 7 Issue Type: Sub-task Components: Clustering Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha1 Leverage the Infinispan async API to ensure that all sessions have replicated (when using REPL/DIST_ASYNC) prior to shutdown/undeploy. https://docs.jboss.org/author/display/ISPN/Asynchronous+API -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-6946) Redesign web session clustering

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-6946: --------------------------------- Summary: Redesign web session clustering Key: AS7-6946 URL: https://issues.jboss.org/browse/AS7-6946 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 8.0.0.Alpha1 The current web session replication code has been around for ages and suffers from a number of issues: * By maintaining a separate local map of sessions in conjunction with the session data stored in the distributed cache, stale data is inevitable - an number of issues have cropped up in EAP testing. * Extra concurrency measures are required to ensure synchronicity of the local session map with the distributed cache. * Extra logic/locking is required to invalidate the local session map is required per request * AtomicMaps, on which the currently implementation relies, have proven buggy * Session access outside of the scope of the replication valve is possible and problematic * Maintaining sessions locally means that the clustering code needs to implement passivation and expiration manually - instead of leveraging Infinispan full capabilities. * The current code base is tightly coupled to JBoss Web. Migrating the code to support Undertow will inevitably introduce issues and code duplication. The new design will incorporate a proper SPI for the servlet container. Thus the logic to integrate with Undertow vs JBoss Web will be relatively thin. -- 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, 3 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 April 2013