January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8503) Depchain should exclude Seam core

by Stan Silvert (JIRA)

Depchain should exclude Seam core --------------------------------- Key: JBAS-8503 URL: https://jira.jboss.org/browse/JBAS-8503 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Build System Affects Versions: 6.0.0.M5 Reporter: Stan Silvert Assignee: Andrew Rubinger See http://community.jboss.org/message/565457 It looks like the depchain needs to exclude Seam core from the seam-int dependency. If the main Seam jar is in the classpath then you can't run non-Seam JSF apps with embedded. But I'm not sure what the ramifications of excluding it might be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8372) Weld deployer should disable EJB support (not fail) if EJB is not present in JBoss AS

by Pete Muir (JIRA)

Weld deployer should disable EJB support (not fail) if EJB is not present in JBoss AS ------------------------------------------------------------------------------------- Key: JBAS-8372 URL: https://jira.jboss.org/browse/JBAS-8372 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Weld/CDI Affects Versions: 6.0.0.M4 Reporter: Pete Muir Assignee: Marius Bogoevici If EJB is removed from JBoss AS, then Weld should continue to function, and simply disable EJB support in the application -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8062) Bug with deploying entity beans in JBoss 5 .....

by Nitesh S (JIRA)

Bug with deploying entity beans in JBoss 5 ..... ------------------------------------------------ Key: JBAS-8062 URL: https://jira.jboss.org/browse/JBAS-8062 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.1.GA Reporter: Nitesh S Assignee: Alexey Loubyansky JBoss version ------------------------------------------------------------------ JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221) jboss.xml ------------------------------------------------------------------ <?xml version="1.0" encoding="UTF-8"?> <jboss> <enterprise-beans> <entity> <ejb-name>MyFramework</ejb-name> <local-jndi-name>JNDI_MyFramework</local-jndi-name> <configuration-name>LEVEL 2</configuration-name> </entity> </enterprise-beans> <container-configurations> <container-configuration extends="Standard CMP 2.x EntityBean"> <container-name>LEVEL 1</container-name> <container-cache-conf> <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy> <cache-policy-conf> <min-capacity>50</min-capacity> <max-capacity>5000</max-capacity> <overager-period>300</overager-period> <max-bean-age>7200</max-bean-age> <resizer-period>400</resizer-period> <max-cache-miss-period>60</max-cache-miss-period> <min-cache-miss-period>1</min-cache-miss-period> <cache-load-factor>0.75</cache-load-factor> </cache-policy-conf> </container-cache-conf> </container-configuration> <container-configuration extends="LEVEL 1"> <container-name>LEVEL 2</container-name> <insert-after-ejb-post-create>true</insert-after-ejb-post-create> </container-configuration> </container-configurations> </jboss> ------------------------------------------------------------------ When I started server with above configurations, it results in... and did not start... 12:41:18,126 INFO [EjbModule] Deploying MyFramework 12:41:18,303 WARN [EjbModule] EJB configured to bypass security. Please verify if this is intended. Bean=MyFramework Deployment=vfszip:/D:/digite/jboss5/server/nitesh/deploy/niteshejbs.jar/ 12:41:18,303 WARN [EjbModule] There are no interceptors configured. Check the standardjboss.xml file ------------------------------------------------------------------ When I changed entity configurations to "LEVEL 1", following way, it worked.... <entity> <ejb-name>MyFramework</ejb-name> <local-jndi-name>JNDI_MyFramework</local-jndi-name> <configuration-name>LEVEL 1</configuration-name> </entity> 12:51:21,881 INFO [EjbModule] Deploying MyFramework 12:51:22,049 WARN [EjbModule] EJB configured to bypass security. Please verify if this is intended. Bean=MyFramework Deployment=vfszip:/D:/digite/jboss5/server/nitesh/deploy/niteshejbs.jar/ When "LEVEL 2" configuration is given to entity, it is not inheriting interceptors from standardjboss.xml It is issue only in JBoss 5 ..... "LEVEL 2" configuration works fine when deployed in JBoss 4.2.3 ...... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8582) Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy

by Tom Ross (JIRA)

Under certain circumstances a wrong locator can be removed from UnifiedInvokerHAProxy -------------------------------------------------------------------------------------- Key: JBAS-8582 URL: https://jira.jboss.org/browse/JBAS-8582 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: JBoss EJB 2.1 Reporter: Tom Ross Assignee: Galder Zamarreño Fix For: TBD Thee is a small window of opportunity that under failure conditions, the locator removed could be the wrong one. Under error condition UnifiedInvokerHAProxy class calls removeDeadTarget(getLocator()) method. Problem is that the getLocator() call might return a locator not associated with current client. This should be changed to removeDeadTarget(client.getInvoker().getLocator()). This way we can be sure that correct locator is aways used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-7969) XB binding of org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList

by Alexey Loubyansky (JIRA)

XB binding of org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList ----------------------------------------------------------------------------- Key: JBAS-7969 URL: https://jira.jboss.org/jira/browse/JBAS-7969 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-6.0.0.M2 Reporter: Alexey Loubyansky Assignee: David Lloyd Property order is not specified for type org.jboss.beans.metadata.spi.PropertyMetaData bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: value preInstantiate type name at org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList at org.jboss.logging.metadata.LoggingMetaData.handlerMetaDataList at org.jboss.logging.metadata.LoggingMetaData @XmlElementWrapper(name="properties") public void setPropertyMetaDataList(final List<PropertyMetaData> propertyMetaDataList) { this.propertyMetaDataList = propertyMetaDataList; } PropertyMetaData is an interface and an implementation class must be specified. It's not actually used, is it? -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-7907) Create a manifest-only JAR to point to all JBAS runtime binaries

by Andrew Lee Rubinger (JIRA)

Create a manifest-only JAR to point to all JBAS runtime binaries ---------------------------------------------------------------- Key: JBAS-7907 URL: https://jira.jboss.org/jira/browse/JBAS-7907 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger A single-JAR dependency to be used primarily by EmbeddedAS, to make everything available on the application classpath in one go. -- 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

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8036) create EntityManager error

by Dave Chen (JIRA)

create EntityManager error -------------------------- Key: JBAS-8036 URL: https://jira.jboss.org/browse/JBAS-8036 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 5.1.0 GA Reporter: Dave Chen create a new persistence unit programmatically and map it to a new datasource without redeploy or server restart. We tried the following in a stateless session bean: Map configOverrides = new HashMap(); EntityManagerFacotry emf = Persistence.createEntityManagerFactory("unit1", configOverrides); But got exception: javax.persistence.PersistenceException: [PersistenceUnit: unit1] Unable to build EntityManagerFactory <persistence-unit name="unit1"> <jta-data-source>java:/dataSource1</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.hbm2ddl.auto" value="update"/> <property name="hibernate.show_sql" value="false"/> </properties> </persistence-unit> 08:17:58,204 ERROR [STDERR] javax.persistence.PersistenceException: [PersistenceUnit: defaultDataSource] Unable to build EntityManagerFactory 08:17:58,205 ERROR [STDERR] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677) 08:17:58,205 ERROR [STDERR] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126) 08:17:58,205 ERROR [STDERR] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8497) Oracle XA datasource settings - PAD

by Wolf-Dieter Fink (JIRA)

Oracle XA datasource settings - PAD ----------------------------------- Key: JBAS-8497 URL: https://jira.jboss.org/browse/JBAS-8497 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Administration and Configuration Guide Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.0.0.GA Reporter: Wolf-Dieter Fink Within the examples docs/examples/jca/oracle-xa-ds.xml is a description that PAD must be set within the transactions-service.xml. But it looks that it must not longer set. The hint should be deleted to avoid confusion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-8078) HornetQ Initialization Takes 25% of AS Boot Time

by Richard Opalka (JIRA)

HornetQ Initialization Takes 25% of AS Boot Time ------------------------------------------------ Key: JBAS-8078 URL: https://jira.jboss.org/browse/JBAS-8078 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (HornetQ) Affects Versions: 6.0.0.M4 Reporter: Richard Opalka Assignee: Tim Fox Fix For: 6.0.0.Final This is the umbrella JIRA for all the future HornetQ boot time optimization fixes. I was measuring AS boot times today. Here are the results. ----------------------- Test Configuration ----------------------- * AS TRUNK (https://svn.jboss.org/repos/jbossas/trunk -r 105792 default configuration) * Sun JDK6 (java version "1.6.0_20") * 64 Bit Linux OS (Linux opalka 2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux) * Intel Processor (Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz) ----------------------- AS trunk (with HornetQ) boot times: ----------------------- Round 01 - 25s:723ms Round 02 - 24s:260ms Round 03 - 24s:626ms Round 04 - 25s:345ms Round 05 - 24s:510ms Round 06 - 24s:458ms Round 07 - 24s:904ms Round 08 - 24s:885ms Round 09 - 24s:367ms Round 10 - 24s:817ms Round 11 - 24s:815ms Round 12 - 25s:174ms Round 13 - 24s:758ms Round 14 - 25s:260ms Round 15 - 24s:692ms ----------------------- Average - 24s:840ms ----------------------- When I removed: $JBOSS_HOME/server/default/deploy/hornetq/ $JBOSS_HOME/server/default/deployers/hornetq-deployers-jboss-beans.xml ----------------------- AS trunk (without HornetQ) boot times: ----------------------- Round 01 - 18s:379ms Round 02 - 18s:399ms Round 03 - 18s:837ms Round 04 - 19s:274ms Round 05 - 18s:506ms Round 06 - 19s:102ms Round 07 - 18s:981ms Round 08 - 19s:138ms Round 09 - 18s:565ms Round 10 - 18s:439ms Round 11 - 18s:586ms Round 12 - 18s:330ms Round 13 - 18s:855ms Round 14 - 18s:545ms Round 15 - 19s:210ms ----------------------- Average - 18s:743ms ----------------------- ----------- Conclusion: ----------- 24s:840ms = 100 % AS trunk boot 18s:743ms ~ 75 % AS trunk without HornetQ boot --- 6s:097ms ~ 25 % HornetQ boot --- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

6
7
0 / 0

[JBoss JIRA] Created: (JBAS-8084) Failures with WrapXAResource set to true

by Jesper Pedersen (JIRA)

Failures with WrapXAResource set to true ---------------------------------------- Key: JBAS-8084 URL: https://jira.jboss.org/browse/JBAS-8084 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (HornetQ) Reporter: Jesper Pedersen Assignee: Clebert Suconic If WrapXAResource is set to true by default there are failures in the messaging tests. See JBAS-8072 for details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2011