September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3614) failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase ----------------------------------------------------------------------- Key: JBAS-3614 URL: http://jira.jboss.com/jira/browse/JBAS-3614 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX, Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Scott M Stark Fix For: JBossAS-4.0.5.GA testRMMResourceImplementsMBean Failure testRMMResourceImplementsMBean: javax.management.MBeanException: Operation setpojoAttribute not in ModelMBeanInfo junit.framework.AssertionFailedError: testRMMResourceImplementsMBean: javax.management.MBeanException: Operation setpojoAttribute not in ModelMBeanInfo at org.jboss.test.jbossmx.compliance.modelmbean.ModelMBeanTestCase.testRMMResourceImplementsMBean(ModelMBeanTestCase.java:150) -- 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

19 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-491) add document node type

by Michael Neale (JIRA)

add document node type ---------------------- Key: JBRULES-491 URL: http://jira.jboss.com/jira/browse/JBRULES-491 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-403) add support for observation

by Michael Neale (JIRA)

add support for observation --------------------------- Key: JBRULES-403 URL: http://jira.jboss.com/jira/browse/JBRULES-403 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale For ben. This can be done as "hooks" so that on a resource change, an email could be sent to an interested party (perhaps even when the status changes, to allow simple workflow so when a rule is changed, the approver is notified). -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-405) add support for searching

by Michael Neale (JIRA)

add support for searching ------------------------- Key: JBRULES-405 URL: http://jira.jboss.com/jira/browse/JBRULES-405 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Priority: Minor Generic search -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3616) failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase

by Dimitris Andreadis (JIRA)

failing test org.jboss.test.jmx.test.RMIAdaptorUnitTestCase ----------------------------------------------------------- Key: JBAS-3616 URL: http://jira.jboss.com/jira/browse/JBAS-3616 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_05-b05 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-34.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA testMBeanInfoMarshalling Failure Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL junit.framework.AssertionFailedError: Failed to get MBeanInfo for bean named: jboss.deployment:type=DeploymentScanner,flavor=URL at org.jboss.test.jmx.test.RMIAdaptorUnitTestCase.testMBeanInfoMarshalling(RMIAdaptorUnitTestCase.java:72) -- 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

19 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-527) JBoss Messaging should support JMSXDeliveryCount

by Joel Lindheimer (JIRA)

JBoss Messaging should support JMSXDeliveryCount ------------------------------------------------- Key: JBMESSAGING-527 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-527 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.0.1.CR4 Environment: All Reporter: Joel Lindheimer Assigned To: Ovidiu Feodorov Joel: Here is an excerpt from theserverside which sums up the retry concept within a transaction well: http://www.theserverside.com/tt/articles/content/JMSArchitecture/JMSAppli... For point-to-point messaging, when a transaction reads a message, the message becomes available to the transaction, but does not get physically removed from the destination at that time; instead, the messaging system leaves the message on the destination but does not allow other transactions to see it. When the transaction commits, the message is completely removed from the destination; however, if the transaction rolls back, the message stays on the destination and is now allowed to be read by other transactions. Ovidiu: Right. This is what Messaging does it. Though, to be 100% technically accurate, what it does is actually transacting acknowledgments. The message becomes available to the transaction, and it's the acknowledgment that is sent back to the channel in a transactional context. The acknowledgment is delivered to the channel (and the message removed from the channel) only when transaction commits. This allows for a powerful feature called replay. Replay is the ability to retry the transaction after a rollback. The danger here is you can get caught in an infinite loop trying to replay the transaction. However, JMS systems can make use of the re-delivered count field on the message descriptor. Here, one can determine how many times the message has been re-delivered to a consumer and allow one to stop processing the message. We're actually not supporting JMSXDeliveryCount yet, you're right here. The spec says it's optional. If it's important for you, just log a JIRA feature request, and we'll do it, subject to resource availability :). Joel: Thanks Ovidiu, JMSXDeliveryCount is definitely a very high priority for us. With the rapid growing adoption of MDP use I imagine that I will be something that is also in high demand for the community at large. Furthermore, most JMS vendors support this behavior, so it probably makes sense for JBoss to put it on the roadmap. -- 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

19 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-560) Support all JBossMQ equivalent JMX functionality

by Tim Fox (JIRA)

Support all JBossMQ equivalent JMX functionality ------------------------------------------------ Key: JBMESSAGING-560 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-560 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Fix For: 1.2.0.Beta1 For 1.2 we need to ensure we support the same or equivalent set of management functionality as JBoss MQ. -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-738) Add format of persistent state transfer to CacheLoader API Javadoc

by Brian Stansberry (JIRA)

Add format of persistent state transfer to CacheLoader API Javadoc ------------------------------------------------------------------ Key: JBCACHE-738 URL: http://jira.jboss.com/jira/browse/JBCACHE-738 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0 Persistent state is a serialized series of NodeData objects. All the standard CacheLoader impls use this format. The requirement to use this format should be added to the CacheLoader API Javadoc to make it part of the official API contract. This will ensure interoperability between cache loaders (e.g state generated by a user's CustomCacheLoader can be stored by JDBCCacheLoader, etc.) -- 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

19 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-681) Ejb 3 Deployment separated into different jars that have persistence dependencies cause a jacc initialisation error

by Roland R?z (JIRA)

Ejb 3 Deployment separated into different jars that have persistence dependencies cause a jacc initialisation error ------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-681 URL: http://jira.jboss.com/jira/browse/EJBTHREE-681 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Roland R?z We separated the jboss trails deployment into two different jar's (persistence and stateless session beans). The ear (ejb3-trials-ear.ear) contains two jar modules (ejb3-trials-ejb.jar & ejb3-trials-persistence.jar). The ejb3-trials-ejb.jar is deployed as fist module but it has a dependency to the ejb3-trials-persistence.jar because it uses the EntityManager from ejb3-trials-persistence. Therefore the ejb container of ejb3-trials-ejb.jar is started after the ejb3-trials-ejb.jar modules. This causes an error with the jacc initialisation. The policy is committed before the ejb container could register is permissions. When the stateless ejb containers add the permissions afterwards, the committed policy will be removed and never committed again. Because the ejb module commits the jacc policy, the ejb containers providing the permissions must be stated before the module. Here the steps: Ejb3Deployment.registerEJBContainer() object name : jboss.j2ee:service=EJB3,ear=ejb3-trials-ear.ear,jar=ejb3-trials-ejb.jar,name=EntityCalculator dependencies : persistence.units:ear=ejb3-trials-ear.ear,unitName=ejb3-trials-persistence Ejb3Module.startService() service name : jboss.j2ee:service=EJB3,module=ejb3-trials-ejb.jar - JACC contextID ejb3-trials-ejb.jar is commited -> This is an error because it should be waited until ALL container of this module are started Ejb3Module.startService() service name: jboss.j2ee:service=EJB3,module=ejb3-trials-persistence.jar - dependencie from jar=ejb3-trials-ejb.jar to ejb3-trials-persistence.jar is resolved and the stateless container is started StatelessContainer.start() ejb3-trials-ejb.jar - JACC contextID ejb3-trials-ejb.jar Adds stuff to the policy Ejb3Module.startService() service name: jboss.j2ee:service=EJB3,module=ejb3-trials-persistence.jar 08:36:44,308 INFO [org.jboss.deployment.EARDeployer] Init J2EE application: file:/C:/eplatform/jboss/4.0/server/eplatform-development/deploy/ejb3-trials-ear.ear 08:36:44,428 WARN [org.jboss.deployment.MainDeployer] Found non-jar deployer for ejb3-trials-persistence.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer] 08:36:44,438 WARN [org.jboss.deployment.MainDeployer] Found non-jar deployer for ejb3-trials-persistence.jar: MBeanProxyExt[jboss.ejb3:service=EJB3Deployer] 08:36:44,599 INFO [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 111 08:36:44,689 INFO [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 50 08:36:44,759 INFO [org.jboss.deployment.ClientDeployer] Client ENC bound under: ejb3-trials-client 08:36:44,789 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=ejb3-trials-ear.ear,jar=ejb3-trials-ejb.jar,name=EntityCalculator,service=EJB3 with dependencies: 08:36:44,789 INFO [org.jboss.ejb3.JmxKernelAbstraction] persistence.units:ear=ejb3-trials-ear.ear,unitName=ejb3-trials-persistence 08:36:44,809 DEBUG [com.winterthur.jackpot.security.jacc.JackpotPolicyConfiguration.ejb3-trials-ear.ear] linkConfiguration, linkTo: ejb3-trials-ejb.jar 08:36:44,809 DEBUG [com.winterthur.jackpot.security.jacc.JackpotPolicyConfiguration.ejb3-trials-ejb.jar] commit 08:36:44,809 INFO [org.jboss.ejb3.EJB3Deployer] Deployed: file:/C:/eplatform/jboss/4.0/server/eplatform-development/tmp/deploy/tmp11029ejb3-trials-ear.ear-contents/ejb3-trials-ejb.jar 08:36:44,819 INFO [org.jboss.ejb3.JmxKernelAbstraction] installing MBean: persistence.units:ear=ejb3-trials-ear.ear,unitName=ejb3-trials-persistence with dependencies: 08:36:44,819 INFO [org.jboss.ejb3.JmxKernelAbstraction] jboss.jca:name=DefaultDS,service=ManagedConnectionFactory 08:36:44,849 INFO [org.hibernate.ejb.Ejb3Configuration] Processing PersistenceUnitInfo [ name: ejb3-trials-persistence ...] 08:36:44,859 INFO [org.hibernate.ejb.Ejb3Configuration] found EJB3 Entity bean: trail.entity.beans.Record 08:36:44,869 INFO [org.hibernate.ejb.Ejb3Configuration] found EJB3 Entity bean: trail.entity.beans.TimedRecord 08:36:44,869 INFO [org.hibernate.ejb.Ejb3Configuration] found EJB3 Entity bean: trail.entity.beans.Investor 08:36:44,869 INFO [org.hibernate.ejb.Ejb3Configuration] found EJB3 Entity bean: trail.entity.beans.Fund 08:36:44,869 WARN [org.hibernate.ejb.Ejb3Configuration] Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. 08:36:44,899 INFO [org.hibernate.cfg.Configuration] Reading mappings from resource: META-INF/orm.xml 08:36:44,899 INFO [org.hibernate.ejb.Ejb3Configuration] [PersistenceUnit: ejb3-trials-persistence] no META-INF/orm.xml found 08:36:44,919 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: trail.entity.beans.Record 08:36:44,919 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity trail.entity.beans.Record on table record 08:36:44,959 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: trail.entity.beans.TimedRecord 08:36:44,969 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: trail.entity.beans.Investor 08:36:44,969 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity trail.entity.beans.Investor on table investor 08:36:44,969 INFO [org.hibernate.cfg.AnnotationBinder] Binding entity from annotated class: trail.entity.beans.Fund 08:36:44,979 INFO [org.hibernate.cfg.annotations.EntityBinder] Bind entity trail.entity.beans.Fund on table FUND 08:36:45,089 INFO [org.hibernate.connection.ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider 08:36:45,089 INFO [org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider] Using provided datasource 08:36:45,089 INFO [org.hibernate.cfg.SettingsFactory] RDBMS: DB2/SUN, version: SQL08022 08:36:45,089 INFO [org.hibernate.cfg.SettingsFactory] JDBC driver: IBM DB2 JDBC Universal Driver Architecture, version: 2.8.46 08:36:45,089 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.FirebirdDialect 08:36:45,099 INFO [org.hibernate.transaction.TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory 08:36:45,099 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup 08:36:45,099 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] instantiated TransactionManagerLookup 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Automatic flush during beforeCompletion(): disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Automatic session close at end of transaction: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Scrollable result sets: enabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] JDBC3 getGeneratedKeys(): disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Connection release mode: auto 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Default batch fetch size: 1 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Generate SQL with comments: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Order SQL updates by primary key: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory 08:36:45,099 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Query language substitutions: {} 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Second-level cache: enabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Query cache: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Cache provider: org.hibernate.cache.HashtableCacheProvider 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Optimize cache for minimal puts: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Structured second-level cache entries: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Statistics: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Deleted entity synthetic identifier rollback: disabled 08:36:45,099 INFO [org.hibernate.cfg.SettingsFactory] Default entity-mode: pojo 08:36:45,119 INFO [org.hibernate.impl.SessionFactoryImpl] building session factory 08:36:45,229 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Not binding factory to JNDI, no JNDI name configured 08:36:45,240 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces} 08:36:45,280 DEBUG [com.winterthur.jackpot.jboss.transport.Ejb3SubjectDelegationCheckInterceptor] Ejb3SubjectDelegationCheckInterceptor is enabled. 08:36:45,530 DEBUG [com.winterthur.jackpot.security.jacc.JackpotPolicyConfiguration.ejb3-trials-ejb.jar] addToUncheckedPolicy, p=(javax.security.jacc.EJBMethodPermission EntityCalculator getFunds,,)[*:getFunds()] 08:36:45,530 INFO [org.jboss.ejb3.EJBContainer] STARTED EJB: trail.entity.basic.EntityCalculator ejbName: EntityCalculator -- 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

19 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-154) Change configuration for FTP listeners/actions to avoid need to replicate FTP parameters

by Esteban Schifman (JIRA)

Change configuration for FTP listeners/actions to avoid need to replicate FTP parameters ---------------------------------------------------------------------------------------- Key: JBESB-154 URL: http://jira.jboss.com/jira/browse/JBESB-154 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Esteban Schifman Assigned To: Esteban Schifman Priority: Minor FTP server/username/password are needed both by the RemoteDirectoryPoller, and the FTP classes As it stands now, they need to be replicated in the xml configuration file for listeners and actions. This is not appropriate and we should find ways to avoid this need. -- 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

19 years, 4 months

1
2
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 September 2006