December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2915) Resource adapter pool have to consider transaction support to decide if the pool is xa or not

by Stefano Maestri (Created) (JIRA)

Resource adapter pool have to consider transaction support to decide if the pool is xa or not --------------------------------------------------------------------------------------------- Key: AS7-2915 URL: https://issues.jboss.org/browse/AS7-2915 Project: Application Server 7 Issue Type: Bug Components: JCA Affects Versions: 7.1.0.Beta1 Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.1.0.CR1 -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3297) NPE in BehaviorJobContextTimerOutputMarshaller.write

by Drools User (Created) (JIRA)

NPE in BehaviorJobContextTimerOutputMarshaller.write ---------------------------------------------------- Key: JBRULES-3297 URL: https://issues.jboss.org/browse/JBRULES-3297 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.3.0.Final Reporter: Drools User Assignee: Mark Proctor Priority: Blocker {code} Caused by: java.lang.NullPointerException at org.drools.rule.SlidingTimeWindow$BehaviorJobContextTimerOutputMarshaller.write(SlidingTimeWindow.java:298) at org.drools.marshalling.impl.OutputMarshaller.writeTimers(OutputMarshaller.java:1105) at org.drools.marshalling.impl.OutputMarshaller.writeSession(OutputMarshaller.java:172) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:142) at org.drools.marshalling.impl.DefaultMarshaller.marshall(DefaultMarshaller.java:125) at org.drools.persistence.SessionMarshallingHelper.getSnapshot(SessionMarshallingHelper.java:72) at org.drools.persistence.info.SessionInfo.update(SessionInfo.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.ejb.event.BeanCallback.invoke(BeanCallback.java:23) at org.hibernate.ejb.event.EntityCallbackHandler.callback(EntityCallbackHandler.java:80) at org.hibernate.ejb.event.EntityCallbackHandler.preUpdate(EntityCallbackHandler.java:65) at org.hibernate.ejb.event.EJB3FlushEntityEventListener.invokeInterceptor(EJB3FlushEntityEventListener.java:41) at org.hibernate.event.def.DefaultFlushEntityEventListener.handleInterception(DefaultFlushEntityEventListener.java:330) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:270) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:151) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:219) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:99) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:49) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1028) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:366) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:137) at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:54) ... 34 more {code} -- 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

14 years, 7 months

3
3
0 / 0

[JBoss JIRA] (AS7-2749) Manage JMX subsystem through the console

by Heiko Braun (Created) (JIRA)

Manage JMX subsystem through the console ---------------------------------------- Key: AS7-2749 URL: https://issues.jboss.org/browse/AS7-2749 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun -- 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

14 years, 7 months

4
5
0 / 0

[JBoss JIRA] (AS7-2816) JMX subsystem is immutable

by Heiko Braun (Created) (JIRA)

JMX subsystem is immutable -------------------------- Key: AS7-2816 URL: https://issues.jboss.org/browse/AS7-2816 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 All attributes need to be writable. {noformat} 14:59:22,725 ERROR [org.jboss.as.controller] (HttpManagementService-threads - 70) Operation ("write-attribute") failed - address: ([("subsystem" => "jmx")]) - failure description: "JBAS014639: Attribute registry-binding is not writable" {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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2538) The jboss-javaee6-ear-webapp Maven archetype generates a project that can cause a database duplicate key conflict

by Sande Gilda (Created) (JIRA)

The jboss-javaee6-ear-webapp Maven archetype generates a project that can cause a database duplicate key conflict ----------------------------------------------------------------------------------------------------------------- Key: AS7-2538 URL: https://issues.jboss.org/browse/AS7-2538 Project: Application Server 7 Issue Type: Bug Components: Build System, Documentation Reporter: Sande Gilda Assignee: Pete Muir I created the the kitchensink-ear project using the jboss-javaee6-ear-webapp archetype. I built and deployed the application to a server where the kitchensink quickstart was already deployed. When I restarted my server, I got a JdbcSQLException: org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: "PRIMARY_KEY_8 ON PUBLIC.MEMBER(ID)"; SQL statement: insert into Member (id, name, email, phone_number) values (0, 'John Smith', 'john.smith(a)mailinator.com', '2125551212') Unfortunately there is no way to know if the kitchensink is also deployed to the server so it is easy to run into a conflict with the 'id' column. We need to make the following 2 changes to the archetype: 1. We need to rename the table to avoid conflict. I checked in kitchensink-ear with the table renamed to "Registrant". This required renaming 5 files and changing all "member" references to "registrant". This can be found here: https://github.com/sgilda/quickstart 2. We also need to change the index.xhtml message to say "You have successfully deployed a Java EE 6 Enterprise application on JBoss AS 7". This uses the EAR archetype so it is an Enterprise application and not just a web application. -- 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

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-2913) Failed to remove long running pool config

by Heiko Braun (Created) (JIRA)

Failed to remove long running pool config ----------------------------------------- Key: AS7-2913 URL: https://issues.jboss.org/browse/AS7-2913 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.CR1 Removing a long-running pool config yields a server side exception: {noformat} [INFO] { [INFO] "address" => [ [INFO] ("subsystem" => "jca"), [INFO] ("workmanager" => "custom"), [INFO] ("long-running-threads" => "long-running-pool") [INFO] ], [INFO] "operation" => "remove" [INFO] } {noformat} {noformat} Caused by: java.lang.IllegalArgumentException at org.jboss.dmr.ModelValue.asProperty(ModelValue.java:96) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.dmr.ObjectModelValue.asProperty(ObjectModelValue.java:151) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.dmr.ModelNode.asProperty(ModelNode.java:348) [jboss-dmr-1.1.1.Final.jar:] at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeWorkManagers(JcaExtension.java:242) at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeContent(JcaExtension.java:186) at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.writeContent(JcaExtension.java:173) at org.jboss.as.server.parsing.StandaloneXml.writeServerProfile(StandaloneXml.java:933) at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:851) at org.jboss.as.server.parsing.StandaloneXml.writeContent(StandaloneXml.java:96) at org.jboss.staxmapper.XMLMapperImpl.doDeparse(XMLMapperImpl.java:78) [staxmapper-1.0.0.Final.jar:] at org.jboss.staxmapper.XMLMapperImpl.deparseDocument(XMLMapperImpl.java:73) [staxmapper-1.0.0.Final.jar:] at org.jboss.as.controller.persistence.AbstractConfigurationPersister.marshallAsXml(AbstractConfigurationPersister.java:102) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] {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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2879) Failed to marshal JCA poll config

by Heiko Braun (Created) (JIRA)

Failed to marshal JCA poll config --------------------------------- Key: AS7-2879 URL: https://issues.jboss.org/browse/AS7-2879 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.CR1 {noformat} [INFO] { [INFO] "name" => "custom2", [INFO] "blocking" => false, [INFO] "max-threads" => { [INFO] "count" => 2, [INFO] "per-cpu" => 1 [INFO] }, [INFO] "allow-core-timeout" => false, [INFO] "queue-length" => { [INFO] "count" => 2, [INFO] "per-cpu" => 1 [INFO] }, [INFO] "address" => [ [INFO] ("subsystem" => "jca"), [INFO] ("workmanager" => "default"), [INFO] ("short-running-threads" => "custom2") [INFO] ], [INFO] "operation" => "add" [INFO] } {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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2911) NPE in EJB3 subsystem views

by Heiko Braun (Created) (JIRA)

NPE in EJB3 subsystem views --------------------------- Key: AS7-2911 URL: https://issues.jboss.org/browse/AS7-2911 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Heiko Braun Assignee: David Bosschaert Fix For: 7.1.0.CR1 {noformat} [ERROR] java.lang.NullPointerException [ERROR] at com.google.gwt.view.client.ListDataProvider$ListWrapper.<init>(ListDataProvider.java:202) [ERROR] at com.google.gwt.view.client.ListDataProvider.setList(ListDataProvider.java:517) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EESubsystemView.updateFrom(EESubsystemView.java:156) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EEPresenter$2.onSuccess(EEPresenter.java:200) [ERROR] at org.jboss.as.console.client.shared.subsys.ejb3.EEPresenter$2.onSuccess(EEPresenter.java:1) {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

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2854) JSR88 does not validate deployment descriptors

by Thomas Diesler (Created) (JIRA)

JSR88 does not validate deployment descriptors ---------------------------------------------- Key: AS7-2854 URL: https://issues.jboss.org/browse/AS7-2854 Project: Application Server 7 Issue Type: Bug Components: JSR-88 Reporter: Thomas Diesler Java EE Platform Specification EE8.5: The deployment tools for Java EE containers must validate the deployment descriptors against the Java EE deployment descriptor schemas or DTDs that correspond to the deployment descriptors being processed. The appropriate schema or DTD is chosen by analyzing the deployment descriptor to determine which version it claims to conform to. Validation errors must cause an error to be reported to the Deployer. -- 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

14 years, 7 months

7
12
0 / 0

[JBoss JIRA] (AS7-2539) Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported

by Abhi S (Created) (JIRA)

Class-Path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR are not supported ---------------------------------------------------------------------------------------------------------------------------------------- Key: AS7-2539 URL: https://issues.jboss.org/browse/AS7-2539 Project: Application Server 7 Issue Type: Bug Components: Deployment, Modules Affects Versions: 7.1.0.Alpha1 Environment: Windows 7 64-bit Reporter: Abhi S Assignee: Thomas Diesler Attachments: jee-app.ear According to the JEE 6 specification, section EE.8.2.1 (Bundled Libraries), Class-path entries—in META-INF/MANIFEST.MF of a sub-deployment module—pointing to resources directories within the EAR could be used by the application developer to add these directories to the classpath of the sub-module. However, this functionality has not yet been implemented in the JBoss AS7.1 (alpha-2 nightly build). *Relevant JEE 6 spec, section EE.8.2.1, quotes:* _Class-Path: list-of-jar-files-or-directories-separated-by-spaces_ _Only JAR format files or directories containing class files or resources to be loaded directly by a standard class loader should be the target of a Class-Path reference; such files are always named with a .jar extension._ This support for this functionality is *required* by the specification for the JBoss AS7.1 to be fully JEE 6 compliant. *Side note:* This functionality is supported in JBoss 5.1, Weblogic, and WebSphere. -- 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

14 years, 7 months

4
4
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 December 2011