November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1158) Sending messages on deleted temporary topic should throw an Exception

by Clebert Suconic (JIRA)

Sending messages on deleted temporary topic should throw an Exception --------------------------------------------------------------------- Key: JBMESSAGING-1158 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1158 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP1 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.4.0.SP2 -- 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

18 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-4152) Upgrade to hsql 1.8.0.7 causes org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 to fail

by Vivek Lakshmanan (JIRA)

Upgrade to hsql 1.8.0.7 causes org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 to fail ------------------------------------------------------------------------------------------------------------------- Key: JBAS-4152 URL: http://jira.jboss.com/jira/browse/JBAS-4152 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.CR1 Environment: BEA JRockit 1.5.0_08 on Red Hat Enterprise Linux AS release 4 (Nahant Update 4) Reporter: Vivek Lakshmanan Assigned To: Scott M Stark On upgrade of HSQLDB from 1.8.0.2 to 1.8.0.7 the following testcase seems to consistently fail: org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase::testCMRmn2 Error: FKey cmr2_id is indexed The test reports say: junit.framework.AssertionFailedError: Error: FKey cmr2_id is indexed at org.jboss.test.cmp2.idxandusersql.test.IdxAndUsersqlUnitTestCase.testCMRmn2(IdxAndUsersqlUnitTestCase.java:190) at net.sourceforge.junitejb.EJBTestCase.runBare(EJBTestCase.java:133) at net.sourceforge.junitejb.EJBTestRunnerBean.runTestCase(EJBTestRunnerBean.java:102) at net.sourceforge.junitejb.EJBTestRunnerBean.run(EJBTestRunnerBean.java:44) at org.jboss.invocation.Invocation.performCall(Invocation.java:359) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:237) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:158) at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:63) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:121) at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:173) at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:77) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:169) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:168) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:205) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:136) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:648) The sourcefile for the test says: /* * Look for indices on the m:n mapping table * This is for hsql a strange case, at indices are put there * anyway, but it has been told that other databases don't do * it by themselves, so we check if the creation succeeds. */ Would like to get an experts opinion on it -- 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

18 years, 8 months

5
16
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-221) The class scope in the metadata repository doesn't understand classloading

by Adrian Brock (JIRA)

The class scope in the metadata repository doesn't understand classloading -------------------------------------------------------------------------- Key: JBMICROCONT-221 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-221 Project: JBoss MicroContainer Issue Type: Task Affects Versions: JBossMC-2.0.0.Beta6 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.Beta7 The class scope uses a String as the qualifier so two different classes with the same name from different classloaders will clash. -- 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

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBXB-108) Expand DefaultSchemaResolver and SchemaResolverConfig to support namespace to binding class mappings

by Scott M Stark (JIRA)

Expand DefaultSchemaResolver and SchemaResolverConfig to support namespace to binding class mappings ---------------------------------------------------------------------------------------------------- Key: JBXB-108 URL: http://jira.jboss.com/jira/browse/JBXB-108 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-2.0.0.CR4 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossXB-2.0.0.CR5 The org.jboss.xb.builder.JBossXBBuilder class supports the creation of a SchemaBinding from a class annotated with JAXB annotations. The DefaultSchemaResolver and SchemaResolverConfig bean need to be updated to allow specification of a namespace URI to binding class mapping. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBXB-109) Element type causes parse error

by Scott M Stark (JIRA)

Element type causes parse error ------------------------------- Key: JBXB-109 URL: http://jira.jboss.com/jira/browse/JBXB-109 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.0.CR5 Reporter: Scott M Stark Assigned To: Adrian Brock Fix For: JBossXB-2.0.0.CR5 If I uncomment the proxyFactoryConfig property on the InvokerProxyBindingMetaData bean, the JBoss5xEverything.testEverything test starts to fail with a CCE: org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/home/svn/Common/trunks/jbossxb/target/test-classes/org/jboss/test/ejb/metadata/test/JBoss5xEverything_testEverything.xml@2693,38 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:184) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:139) at org.jboss.test.xb.builder.JBossXBTestDelegate.unmarshal(JBossXBTestDelegate.java:121) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:184) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:154) at org.jboss.test.javaee.metadata.AbstractJavaEEMetaDataTest.unmarshal(AbstractJavaEEMetaDataTest.java:120) at org.jboss.test.ejb.metadata.test.JBoss5xEverythingUnitTestCase.unmarshal(JBoss5xEverythingUnitTestCase.java:106) at org.jboss.test.ejb.metadata.test.JBoss5xEverythingUnitTestCase.testEverything(JBoss5xEverythingUnitTestCase.java:113) 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:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.RuntimeException: QName {http://java.sun.com/xml/ns/javaee}description error adding java.util.ArrayList@16e1eea8 to collection org.jboss.javaee.metadata.spec.DescriptionsImpl@4afb6354 at org.jboss.xb.builder.runtime.CollectionPropertyHandler.handle(CollectionPropertyHandler.java:137) at org.jboss.xb.builder.runtime.AbstractPropertyHandler.doHandle(AbstractPropertyHandler.java:98) at org.jboss.xb.builder.runtime.PropertyWildcardHandler.setParent(PropertyWildcardHandler.java:72) at org.jboss.xb.binding.group.ValueListHandler$FACTORY$1.newInstance(ValueListHandler.java:401) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParticle(SundayContentHandler.java:825) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:319) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:180) ... 23 more Caused by: java.lang.ClassCastException: java.util.ArrayList at org.jboss.javaee.metadata.support.MappedAnnotationMetaData.add(MappedAnnotationMetaData.java:1) at org.jboss.xb.builder.runtime.CollectionPropertyHandler.handle(CollectionPropertyHandler.java:133) ... 40 more The JBoss5xEverything_testEverything.xml was updated to include a proxy-factory-config element, but this is not being reached. -- 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

18 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBXB-110) Resolve testcase regressions

by Scott M Stark (JIRA)

Resolve testcase regressions ---------------------------- Key: JBXB-110 URL: http://jira.jboss.com/jira/browse/JBXB-110 Project: JBoss XML Binding (JBossXB) Issue Type: Sub-task Reporter: Scott M Stark Fix For: JBossXB-2.0.0.CR5 We need to resolve issues with conflicting defaults and thirdparty based regressions. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-627) Enabling JMX when using multiplexer.

by Robert Newson (JIRA)

Enabling JMX when using multiplexer. ------------------------------------ Key: JGRP-627 URL: http://jira.jboss.com/jira/browse/JGRP-627 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Robert Newson Assigned To: Bela Ban While debugging other issues (the disparity between cluster views and service views), I attempted to add JMX support. However, having looked at the code, it turns out that ObjectNames are formed incorrectly. Caused by: javax.management.MalformedObjectNameException: Invalid character ':' in value part of property at javax.management.ObjectName.construct(ObjectName.java:602) at javax.management.ObjectName.<init>(ObjectName.java:1394) at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:55) at org.jgroups.jmx.JmxConfigurator.registerChannel(JmxConfigurator.java:41) at org.jgroups.JChannelFactory.registerChannel(JChannelFactory.java:383) at org.jgroups.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:297) at org.jgroups.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:280) It's attempting an ObjectName of the form "jgroups:name=Multiplexer:type=channel,cluster=blah" which is illegal. I enabled JMX by calling; channelFactory.setExposeChannels(true); channelFactory.create(); Am I doing this wrong or does the JMX registration simply not work? I can work around this with; channelFactory.setDomain("jgroups") but this doesn't group the JMX beans in the way the code intends. -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-620) RpcDispatcher.callRemoteMethods() hangs

by P Eger (JIRA)

RpcDispatcher.callRemoteMethods() hangs --------------------------------------- Key: JGRP-620 URL: http://jira.jboss.com/jira/browse/JGRP-620 Project: JGroups Issue Type: Bug Affects Versions: 2.5.1 Environment: RHEL4 64 bit: Linux svr5 2.6.9-42.0.10.ELsmp #1 SMP Fri Feb 16 17:13:42 EST 2007 x86_64 x86_64 x86_64 GNU/Linux SUN JDK 1.5.0_12-b04 64 bit Reporter: P Eger Assigned To: Bela Ban Attachments: stacktrace.txt, tcp-config.xml RpcDispatcher.callRemoteMethods() hangs, while there is a lot of member churn at the time (4 servers starting into a cluster of 4). 1 of the 4 server starting up is hung with the attached stack trace. ------------------------------------------------------------------- channel=new JChannel(jgroups_config_file); channel.setOpt(Channel.AUTO_RECONNECT, Boolean.TRUE); channel.addChannelListener(this); //TODO: verify these startup params //NOTE: deadlock detection leaks memory as of 2.5b2, do not use disp=new RpcDispatcher(channel, null, this, this, false, true); //force connect channel.connect(clusterName); MethodCall mc = new MethodCall("remoteBroadcastAvailability", new Object[]{peer,sequence,serviceStatus,rotationStatus}, new Class[]{Address.class,Long.class,ServiceStatus.class,RotationStatus.class}); disp.callRemoteMethods(channel.getView().getMembers(), mc, GroupRequest.GET_ALL, 0); ------------------------------------------------------------------- Name: main State: WAITING on java.util.HashMap@2d95bbec Total blocked: 53 Total waited: 12 Stack trace: java.lang.Object.wait(Native Method) java.lang.Object.wait(Object.java:474) org.jgroups.blocks.GroupRequest.doExecute(GroupRequest.java:479) org.jgroups.blocks.GroupRequest.execute(GroupRequest.java:190) org.jgroups.blocks.MessageDispatcher.castMessage(MessageDispatcher.java:430) org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:199) org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:167) org.jgroups.blocks.RpcDispatcher.callRemoteMethods(RpcDispatcher.java:163) utils.cluster.PeerClusterManager.broadcastAvailability(PeerClusterManager.java:1110) utils.cluster.PeerClusterManager.broadcastMyAvailability(PeerClusterManager.java:428) init.InitManager.ensureInitialized(InitManager.java:552) init.InitManager.__init(InitManager.java:409) init.InitManager.init(InitManager.java:300) init.ServletListener.contextInitialized(ServletListener.java:23) org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3669) org.apache.catalina.core.StandardContext.start(StandardContext.java:4104) org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) org.apache.catalina.core.StandardHost.start(StandardHost.java:718) org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1012) org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442) org.apache.catalina.core.StandardService.start(StandardService.java:450) org.apache.catalina.core.StandardServer.start(StandardServer.java:683) org.apache.catalina.startup.Catalina.start(Catalina.java:537) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:585) org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:271) org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:409) -- 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

18 years, 8 months

2
17
0 / 0

[JBoss JIRA] Created: (JBAS-4892) WebService ignores java.rmi.server.codebase system property

by Takayoshi Kimura (JIRA)

WebService ignores java.rmi.server.codebase system property ----------------------------------------------------------- Key: JBAS-4892 URL: http://jira.jboss.com/jira/browse/JBAS-4892 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Reporter: Takayoshi Kimura server/src/main/org/jboss/web/WebService.java The trailing semicolon of if statement is a bug. String codebase = getCodebase(); // This returns system property value if (codebase == null); // HERE { codebase = "http://" + getHost() + ":" + getPort() + "/"; System.setProperty("java.rmi.server.codebase", codebase); } log.info("Using RMI server codebase: " + codebase); -- 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

18 years, 8 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-621) JOIN_RSP should interrupt thread blocking down on findInitialMembers

by Vladimir Blagojevic (JIRA)

JOIN_RSP should interrupt thread blocking down on findInitialMembers -------------------------------------------------------------------- Key: JGRP-621 URL: http://jira.jboss.com/jira/browse/JGRP-621 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic When clients attempts to join it loops through: while(!joined){ fetch the initial members determine coordinator send join request to coordinator wait for join response (timeout) if(joinok) joined = installView } Unlucky timing of join response arrival can delay successful view installation and lead to unforeseen problems. If waiting for join response timeouts then joining thread repeats a loop and sends a blocking request to fetch initial members again. If response arrives while joining thread is fetching for the initial members then joining thread has to wait for fetching of the initial members to return in order to proceed with view installation. Fix for this issue should ensure that If successful join response arrives then joining thread should be interrupted and proceed with view installation immediately. -- 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

18 years, 8 months

2
14
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 2007