September 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1318) Release CR1 of EJB3 Core

by Andrew Lee Rubinger (JIRA)

Release CR1 of EJB3 Core ------------------------ Key: EJBTHREE-1318 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1318 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Blocker Fix For: AS 5.0.0.CR1 For AS CR1, we must release a proper EJB3 Core CR1 with no cyclic dependencies. This is a container task to track the dependent issues preventing EJB3 Core CR1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2130) Creation of alrady existing role ends up (fails) with an exception

by Viliam Rockai (JIRA)

Creation of alrady existing role ends up (fails) with an exception ------------------------------------------------------------------ Key: JBPORTAL-2130 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2130 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.6 Final Environment: fedora 9, lenovo t61 Reporter: Viliam Rockai Assignee: Boleslaw Dawidowicz When i try to create already existing role on jboss portal (jboss-portal-2.6.5.SP1-bundled.zip), i get an exception. * http://localhost:8080/portal * login as admin * admin -> members -> role managment * Create new role * Role: User | Display name: everything * submit -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1879) problem accessing a portlet deployed in a cluster

by Prabhat Jha (JIRA)

problem accessing a portlet deployed in a cluster ------------------------------------------------- Key: JBPORTAL-1879 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1879 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.6.4 Final Reporter: Prabhat Jha Assigned To: Thomas Heute Fix For: 2.6.5 Final This is something I had noticed in my scalability test but at that time I thought I may have done something stupid and later, I saw a similar note in support case. I have two portal servers (ports-01, ports-02) configuration where nullPortletPage.war is predeployed before servers are started. If I start both servers simultaneously and access http://localhost:8280/portal/portal/default/NullPortletPage then I get a 404 error with "The requested resource () is not available". I am able to access the page if I hit http://localhost:8180/portal/portal/default/NullPortletPage (notice the port) . What is more interesting is that when I start servers one by one i.e. start second server when first one has already started, then I can access the NullPortletPage in both servers. Since there is a work around, let's fix this by 2.6.5 release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

4
26
0 / 0

[JBoss JIRA] Created: (JBXB-150) Inconsistent jaxb api dependency

by Scott M Stark (JIRA)

Inconsistent jaxb api dependency -------------------------------- Key: JBXB-150 URL: https://jira.jboss.org/jira/browse/JBXB-150 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR11 Reporter: Scott M Stark Fix For: JBossXB-2.0.0.CR13 The jbossxb jaxb api dependency is: <dependency> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <version>2.1</version> <scope>compile</scope> </dependency> but it needs to be updated to be consistent with what we are validating in jbossas as part of the tck: <dependency> <groupId>sun-jaxb</groupId> <artifactId>jaxb-api</artifactId> <version>2.1.4</version> </dependency> -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMETA-63) jboss-metadata imports deprecated jboss-jaxws.jar artifact

by Dimitris Andreadis (JIRA)

jboss-metadata imports deprecated jboss-jaxws.jar artifact ---------------------------------------------------------- Key: JBMETA-63 URL: http://jira.jboss.com/jira/browse/JBMETA-63 Project: JBoss Metadata Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Assigned To: Alexey Loubyansky Fix For: 1.0.0.CR2 jboss-metadata uses: org.jboss:jboss-jaxws:jar:2.0.1.GA But JBossAS imports jboss-jaxws from: jboss.jbossws:jboss-jaxws:3.0.1-native-2.0.4.GA My view is those apis should move into the jboss-javaee project and be imported from there: javax.xml.ws javax.jws. Until a decision is made, AS simply excludes the jboss-jaxws.jar artifact imported through jboss-metadata. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2149) Integrate new JBC/HIb integration library

by Prabhat Jha (JIRA)

Integrate new JBC/HIb integration library ----------------------------------------- Key: JBPORTAL-2149 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2149 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.7.0 Beta1, 2.6.6 Final Reporter: Prabhat Jha Assignee: Prabhat Jha Fix For: 2.7.0 CR1 , 2.6.7 Final -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-2102) cms admin ui testing

by Viliam Rockai (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2102?page=com.atlassian.jira.... ] Viliam Rockai commented on JBPORTAL-2102: ----------------------------------------- some issues for manipulating files were added (similiar to manipulation with directories). exporting of file in explore will be added soon. > cms admin ui testing > -------------------- > > Key: JBPORTAL-2102 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2102 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Viliam Rockai > -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-2101) identity admin ui testing

by Viliam Rockai (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2101?page=com.atlassian.jira.... ] Viliam Rockai commented on JBPORTAL-2101: ----------------------------------------- tests now use my custom selenium extension (i.e. shouldn't be dependent on the order of user names in user table) > identity admin ui testing > ------------------------- > > Key: JBPORTAL-2101 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2101 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Viliam Rockai > -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5923) Weak hash map usage in UnifiedInvokerHAProxy is not thread safe

by Galder Zamarreno (JIRA)

Weak hash map usage in UnifiedInvokerHAProxy is not thread safe --------------------------------------------------------------- Key: JBAS-5923 URL: https://jira.jboss.org/jira/browse/JBAS-5923 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Transaction Manager (JBossTM) Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno txFailoverAuthorizations weak hashmap that is now also used for maintaining transaction stickyness was created as an unsynchronized WeakHashMap and this was causing issues. It was not enough to synchronise on the tpc (key of map) whenever we manipulated it because two threads, trying to store different tpcs could end up trying to resize the map and as a result, key value pairs could easily dissapear from the hash map. This is extremely confusing because we thought the disappearance was due to garbage collection. >From now on, we'll be using a Collections.synchronizedMap(new WeakHashMap()); instead. Thanks to Adrian for the help debugging this. -- 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

16 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (HIBERNATE-104) useless stacktrace

by arne anka (JIRA)

useless stacktrace ------------------ Key: HIBERNATE-104 URL: https://jira.jboss.org/jira/browse/HIBERNATE-104 Project: Hibernate Issue Type: Bug Environment: jboss-4.2.2.GA, linux 32bit Reporter: arne anka Assignee: Steve Ebersole when trying entityManager.merge(myUser); entityManager.flush(); i get a very long list of recurrent stacktraces. it boils down to two messages: Caused by: org.hibernate.PropertyAccessException: IllegalArgumentException occurred calling getter of my.class.roleId at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:171) at org.hibernate.tuple.entity.AbstractEntityTuplizer.getIdentifier(AbstractEntityTuplizer.java:183) at org.hibernate.persister.entity.AbstractEntityPersister.getIdentifier(AbstractEntityPersister.java:3591) at org.hibernate.persister.entity.AbstractEntityPersister.isTransient(AbstractEntityPersister.java:3307) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:181) at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:218) at org.hibernate.type.EntityType.getIdentifier(EntityType.java:397) at org.hibernate.type.EntityType.replace(EntityType.java:253) at org.hibernate.type.CollectionType.replaceElements(CollectionType.java:451) at org.hibernate.type.Collecti 14:46:07,362 INFO [STDOUT] onType.replace(CollectionType.java:518) at org.hibernate.type.TypeFactory.replace(TypeFactory.java:482) at org.hibernate.event.def.DefaultMergeEventListener.copyValues(DefaultMergeEventListener.java:340) at org.hibernate.event.def.DefaultMergeEventListener.entityIsDetached(DefaultMergeEventListener.java:267) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:120) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) at org.hibernate.ejb.AbstractEntityManagerImpl.merge(AbstractEntityManagerImpl.java:227) ... 74 more and Caused by: java.lang.IllegalArgumentException: java.lang.ClassCastException@661744 at sun.reflect.GeneratedMethodAccessor2266.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145) ... 92 more the property my.class.roleId is defined as Integer, setter and getter expect or return an Integer. i can't see, what type hibernate expects as argument and i can't see in what type hibernate tries to cast. - why does the stacktrace not mention the argument type hibernate expects? - why does the stacktrace not mention in which type hibernate tries to cast? with it's current level of null-information ist that _very_ long, confusing and time consuming stacktrace worse then useless. i am completely unable to deduce any way to remedy a possible bug in my code or circumvent a possible bug in hibernate. -- 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

16 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2008