November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5761) EJB2 entity bean CMP collection toArray throws NPE

by Lucas Galfaso (JIRA)

Lucas Galfaso created AS7-5761: ---------------------------------- Summary: EJB2 entity bean CMP collection toArray throws NPE Key: AS7-5761 URL: https://issues.jboss.org/browse/AS7-5761 Project: Application Server 7 Issue Type: Feature Request Components: EJB Affects Versions: 7.1.1.Final Environment: MAC OSX, Java7 Reporter: Lucas Galfaso Assignee: jaikiran pai >From an EJB2 entity bean that has a CMP collection of entities, calling toArray() on the CMP collection throws NullPointerException Caused by: java.lang.NullPointerException at org.jboss.as.cmp.jdbc.bridge.RelationSet.toArray(RelationSet.java:291) [jboss-as-cmp-7.1.1.Final.jar:7.1.1.Final] Normal iteration thru the collection using the iterator works as expected. -- 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

6
5
0 / 0

[JBoss JIRA] (AS7-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-5887: --------------------------------------- The critical problem here is that there is no automatic reconnection if via the process controller the HC can see the server is still alive. The timeout might need tweaking, but the key thing is getting the server reconnected. If the server reconnects, there won't be an issue as long as there were no commands attempting to modify that server in the interim -- with such a poorly timed modification being unlikely. If there were a mod, the HC knows the reconnecting server is out of sync and marks it as requiring restart. > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry moved JBPAPP-10358 to AS7-5887: ------------------------------------------------ Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5887 (was: JBPAPP-10358) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.3.Final (EAP) 7.1.2.Final (EAP) 7.1.1.Final (was: EAP 6.0.0) Security: (was: Public) Fix Version/s: 7.2.0.CR1 7.1.4.Final (EAP) (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.3.Final (EAP), 7.1.2.Final (EAP), 7.1.1.Final > Reporter: Travis Rogers > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5887: ---------------------------------- Component/s: Domain Management > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Brian Stansberry > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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-5887) CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5887?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5887: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > CLONE - Host controller unregisters server after it doesn't respond for 30 seconds; doesn't reconnect > ----------------------------------------------------------------------------------------------------- > > Key: AS7-5887 > URL: https://issues.jboss.org/browse/AS7-5887 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final, 7.1.2.Final (EAP), 7.1.3.Final (EAP) > Reporter: Travis Rogers > Assignee: Emanuel Muckenhuber > Fix For: 7.2.0.CR1, 7.1.4.Final (EAP) > > > Simple test to reproduce: > (kill -STOP <pid>, 30 seconds later, receive "unregistered" message in the host controller. After restarting (kill -CONT <pid>), no longer able to control instance via the host controller. -- 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-3679) drools-compiler's CDI does not work in a war

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3679: ----------------------------------------- Summary: drools-compiler's CDI does not work in a war Key: JBRULES-3679 URL: https://issues.jboss.org/browse/JBRULES-3679 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 6.0.0.Beta1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: 6.0.0.Beta1 KProjectExtension uses weld-se-core, but in a war weld-servlet-core should be used instead. We should aim to make KProjectExtension just use CDI and not depend on weld-se-core or weld-servlet-core, if possible. -- 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

2
3
0 / 0

[JBoss JIRA] (AS7-3694) Allow management client to associate metadata with DeploymentUnit

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3694: ----------------------------------- Summary: Allow management client to associate metadata with DeploymentUnit Key: AS7-3694 URL: https://issues.jboss.org/browse/AS7-3694 Project: Application Server 7 Issue Type: Feature Request Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Currently there is no way to pass some metadata through the deployment API such that they could show up with the DU. As a client I'd like to say autostart=false and in my DUP I'd like to pick that up and not start a deployment (i.e. a bundle) automatically Generally it should be possible for the client to set some properties for the deployment in a generic way such that they get associated with the DeploymentUnit -- 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

13 years, 5 months

3
18
0 / 0

[JBoss JIRA] (AS7-5885) Hibernate NullPointerException while having a MappedSuperclass with @version attribute

by Sai Krish (JIRA)

Sai Krish created AS7-5885: ------------------------------ Summary: Hibernate NullPointerException while having a MappedSuperclass with @version attribute Key: AS7-5885 URL: https://issues.jboss.org/browse/AS7-5885 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.1.Final Environment: Cent O.S. 6.2, JDK1.7.0_05 Reporter: Sai Krish Assignee: Scott Marlow I am planning to have all the Entities in my project extend the common attribute from a BaseEntity. Currently I have only one field named Version in the base entity. I have marked the BaseEntity with the annotation of @MappedSuperclass as per the JPA standard. Everything works fine when I have only one Extended class (say Customer). But when I included an additional extended class, the EJB application's deployment failed with a NullPointerException. Stack trace for the same is given below org.jboss.msc.service.StartException in service jboss.persistenceunit."Test.jar#primary": Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] Caused by: java.lang.NullPointerException at org.hibernate.ejb.metamodel.AttributeFactory$6.resolveMember(AttributeFactory.java:947) at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:423) at org.hibernate.ejb.metamodel.AttributeFactory.buildVersionAttribute(AttributeFactory.java:153) at org.hibernate.ejb.metamodel.MetadataContext.applyVersionAttribute(MetadataContext.java:301) at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:206) at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:64) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:91) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] ... 3 more I could not find any workarounds for it. I have attached the sample code that can be used to reproduce the issue. -- 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-5017) Can't connect using CLI running under JDK7u4

by Chris Jansen (JIRA)

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] (AS7-3472) replacing domain controller

by Matej Lazar (JIRA)

Matej Lazar created AS7-3472: -------------------------------- Summary: replacing domain controller Key: AS7-3472 URL: https://issues.jboss.org/browse/AS7-3472 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Affects Versions: 7.1.0.CR1b Reporter: Matej Lazar Assignee: Brian Stansberry Replacing domain controller using operations: /host=node1:remove-local-domain-controller /host=node1:write-remote-domain-controller(host=172.16.254.128, port=9999) -- 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

13 years, 5 months

5
8
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 November 2012