January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3387) separation of passivation/replication operations for extended persistence context

by Scott Marlow (JIRA)

Scott Marlow created AS7-3387: --------------------------------- Summary: separation of passivation/replication operations for extended persistence context Key: AS7-3387 URL: https://issues.jboss.org/browse/AS7-3387 Project: Application Server 7 Issue Type: Task Components: Clustering, EJB Reporter: Scott Marlow Assignee: Paul Ferraro Fix For: 7.1.0.Final Currently, when the JPA extended persistence context is serializing, it is not known if passivation or cluster replication is occurring. This means that the extended persistence context will stay in memory. When ExtendedEntityManager.writeObject() is invoked, I would like a way to tell that the current thread is passivating versus cluster replicating. If this isn't going to happen, I'll look at alternatives. A quick rejection or response that this makes sense, would be welcome. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-9049) Need way to override the boot.log in start scripts

by Scott Stark (JIRA)

Need way to override the boot.log in start scripts -------------------------------------------------- Key: JBAS-9049 URL: https://issues.jboss.org/browse/JBAS-9049 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Affects Versions: 7.0.0.Beta1 Reporter: Scott Stark Assignee: David Lloyd We need the ability to specify the location of the boot.log. Right now the boot.log location is specified via the org.jboss.boot.log.file java system property, but this is always set to $JBOSS_HOME/standalone/log/boot.log in the server start scripts. This should either not be set and simply default to $JBOSS_HOME/standalone/log/boot.log when unset so that it may be passed into the jvm, or, we need a JBOSS_BOOT_LOG env property that can override this value along the line of: if [ "x$JBOSS_BOOT_LOG" = "x" ]; then JBOSS_BOOT_LOG="$JBOSS_HOME/standalone/log/boot.log" fi while true; do if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then # Execute the JVM in the foreground eval \"$JAVA\" $JAVA_OPTS \ \"-Dorg.jboss.boot.log.file=$JBOSS_BOOT_LOG\" \ ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
9
0 / 0

[JBoss JIRA] Created: (JBEE-22) Add jboss-jaxrs-api_1.1_spec

by Shelly McGowan (JIRA)

Add jboss-jaxrs-api_1.1_spec ---------------------------- Key: JBEE-22 URL: https://jira.jboss.org/jira/browse/JBEE-22 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
9
0 / 0

[JBoss JIRA] (AS7-3291) EnversIntegrator is always detected by default while initializing Serviceregistry using Native Hibernate API causing a MappingException even when Envers is not used

by Madhumita Sadhukhan (JIRA)

Madhumita Sadhukhan created AS7-3291: ---------------------------------------- Summary: EnversIntegrator is always detected by default while initializing Serviceregistry using Native Hibernate API causing a MappingException even when Envers is not used Key: AS7-3291 URL: https://issues.jboss.org/browse/AS7-3291 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate, Test Suite Affects Versions: 7.1.0.CR1 Reporter: Madhumita Sadhukhan Assignee: Strong Liu Please find the hibernate native api tests located at : https://github.com/madhumita12/jboss-as/tree/master/testsuite/integration... The tests are working fine with a workaround I have applied to them,hence I would like to request you to run the HibernateNativeAPITransactionTestCase locally to see the issue I have been mentioning before. Also , please comment the workaround as follows before running the test in order to hit around the issue: In file SFSBHibernateTransaction please comment: // configuration.setProperty("hibernate.listeners.envers.autoRegister", "false"); I am simply initialising BootstrapServiceRegistryBuilder and then passing the configuration properties to it to initialize the ServiceRegistry. I am not using any AuditListner or @Audited anywhere in my configuration/code. However when I initialize ServiceRegistry it by default AUTORegisters/detects the EnversIntegrator which tries to initialise AuditListner via Auditconfiguration and crashes. The workaround to this is to set the AUTO_REGISTER in EnversIntegrator to false as above. Stacktrace: ... 139 more Caused by: org.hibernate.MappingException: Unable to create AuditStrategy[org.hibernate.envers.strategy.DefaultAuditStrategy] instance. at org.hibernate.envers.configuration.AuditConfiguration.initializeAuditStrategy(AuditConfiguration.java:114) at org.hibernate.envers.configuration.AuditConfiguration.<init>(AuditConfiguration.java:101) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:135) at org.hibernate.envers.event.EnversIntegrator.integrate(EnversIntegrator.java:63) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:295) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1737) [hibernate-core-4.0.0.Final.jar:4.0.0.Final] at org.jboss.as.test.integration.hibernate.SFSBHibernateTransaction.setupConfig(SFSBHibernateTransaction.java:81) [beans.jar:] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

3
5
0 / 0

[JBoss JIRA] (AS7-2530) Arquillian in AS7 is missing support for byteman

by Miroslav Novak (Created) (JIRA)

Arquillian in AS7 is missing support for byteman ------------------------------------------------ Key: AS7-2530 URL: https://issues.jboss.org/browse/AS7-2530 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Affects Versions: 7.1.0.Alpha1 Reporter: Miroslav Novak Assignee: Andrew Rubinger Fix For: 7.1.0.Beta1 Hi, I tried to implement test case which is using byteman but without success. It seems that arquillian in AS7 doesn't have support for byteman. There are missing classes. Example test case: https://github.com/aslakknutsen/arquillian/blob/ARQ-348/frameworks/bytema... Missing classes: org.jboss.arquillian.framework.byteman.api.BMRule; org.jboss.arquillian.framework.byteman.api.BMRules; Do we have a way how to make it work? Thank you, Mirek -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

9
11
0 / 0

[JBoss JIRA] (AS7-2189) Revisit the jgroups management configuration

by Heiko Braun (Created) (JIRA)

Revisit the jgroups management configuration -------------------------------------------- Key: AS7-2189 URL: https://issues.jboss.org/browse/AS7-2189 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 This doesn't look very reasonable to me: {noformat} [domain@localhost:9999 /] /profile=ha/subsystem=jgroups/stack=tcp:read-resource { "outcome" => "success", "result" => { "protocol" => [ { "type" => "MPING", "socket-binding" => "jgroups-mping" }, {"type" => "MERGE2"}, { "type" => "FD_SOCK", "socket-binding" => "jgroups-tcp-fd" }, {"type" => "FD"}, {"type" => "VERIFY_SUSPECT"}, {"type" => "BARRIER"}, {"type" => "pbcast.NAKACK"}, {"type" => "UNICAST"}, {"type" => "pbcast.STABLE"}, {"type" => "VIEW_SYNC"}, {"type" => "pbcast.GMS"}, {"type" => "UFC"}, {"type" => "MFC"}, {"type" => "FRAG2"}, {"type" => "pbcast.STREAMING_STATE_TRANSFER"}, {"type" => "pbcast.FLUSH"} ], "transport" => { "type" => "TCP", "socket-binding" => "jgroups-tcp", "diagnostics-socket-binding" => "jgroups-diagnostics" } } } {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

7
7
0 / 0

[JBoss JIRA] (AS7-3294) JSF Exception - Failed to parse the expression [#{cc.attrs.for}]

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created AS7-3294: --------------------------------------- Summary: JSF Exception - Failed to parse the expression [#{cc.attrs.for}] Key: AS7-3294 URL: https://issues.jboss.org/browse/AS7-3294 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.0.CR1b Environment: Ubuntu Linux, Fedora, Java 6 Reporter: Lincoln Baxter III Assignee: Stan Silvert So I've run OCPsoft SocialPM ( https://github.com/ocpsoft/socialpm/ ) on both AS 7.1.0.CR1b and AS7 GitHub head, both of them get the following error when going to the signup page: (From Ken Finnigan) {code}21:53:35,494 WARN [org.jboss.solder.exception.control.log] (http--127.0.0.1-8080-2) No handlers found for exception javax.faces.view.facelets.TagAttributeException: /resources/ocpcommon/message.xhtml @46,61 for="#{cc.attrs.for}" Failed to parse the expression [#{cc.attrs.for}]{code} I've attached the entire server log for AS7 Head for reference. I've confirmed it worked with AS 7.0.2.Final, so it looks like a regression. I've taken a look at the JSF modules provided in AS7, 7.0.2 provides jsf-api-1.2_15-jbossorg-1.jar, whereas 7.1.0.CR1b and Head provides jsf-api-1.2_15-jbossorg-2.jar. I haven't had a chance to delve deeper into what discrepancies there might be between the two JSF versions yet. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (AS7-1787) Fix JGroups description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix JGroups description providers for the improved validation in jboss-as-subsystem-test ---------------------------------------------------------------------------------------- Key: AS7-1787 URL: https://issues.jboss.org/browse/AS7-1787 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Reporter: Kabir Khan Assignee: Thomas Diesler Fix For: 7.1.0.Alpha1 I am adding some more validation of the model. This will be committed to upstream in the next few days. To make the security tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } {code} Returning null basically turns off validation of the providers. These are the errors that happen (this might change a bit before I commit the final version of the validation stuff): {code} VALIDATION ERRORS IN MODEL: Invalid key 'attributes' found for child type 'configuration' @[("subsystem" => "osgi")] No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true,"acces s-type" => "read-only","storage" => "configuration"} for attribute 'entries'[ ("subsystem" => "osgi"), ("configuration" => "*") ] No value-type for type=OBJECT {"description" => "The configuration data associated with the PID.","type" => OBJECT,"required" => true} for o peration parameter 'add.entries' @[ ("subsystem" => "osgi"), ("configuration" => "*") ] Invalid key 'attributes' found for child type 'property' @[("subsystem" => "osgi")] Invalid key 'attributes' found for child type 'module' @[("subsystem" => "osgi")] {code} The work in progress lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
8
0 / 0

[JBoss JIRA] Created: (AS7-1788) Fix Infinispan description providers for the improved validation in jboss-as-subsystem-test

by Kabir Khan (JIRA)

Fix Infinispan description providers for the improved validation in jboss-as-subsystem-test ------------------------------------------------------------------------------------------- Key: AS7-1788 URL: https://issues.jboss.org/browse/AS7-1788 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Kabir Khan Assignee: Paul Ferraro Fix For: 7.1.0.Alpha1 I added a test called JGroupsSubsystemTest which uses our subsystem testing framework which attempts to validate the description providers, this will be committed to upstream in the next few days. To make the tests pass I had to override AdditionalInitialization.getModelValidationConfiguration() as follows: {code} @Override protected ValidationConfiguration getModelValidationConfiguration() { return null; } {code} Returning null basically turns off validation of the providers. What I have added is a minimum of what is required for subsystem testing, the test framework allows you to do a lot of other stuff, see the jmx subsystem test for some examples. The wip lives at https://github.com/kabir/jboss-as/tree/subsystem-test-model-fixes -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

5
8
0 / 0

[JBoss JIRA] Created: (LOGTOOL-24) Better support for Maven logging messages

by James Perkins (JIRA)

Better support for Maven logging messages ----------------------------------------- Key: LOGTOOL-24 URL: https://issues.jboss.org/browse/LOGTOOL-24 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Maven only prints error and warning messages. Check for ways to print informational and possibly debug messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2012