January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-331) checkMyParms() in CbrListener

by Bernard Tison (JIRA)

checkMyParms() in CbrListener ----------------------------- Key: JBESB-331 URL: http://jira.jboss.com/jira/browse/JBESB-331 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Reporter: Bernard Tison Assigned To: Mark Little checkMyParams() in CbrListener checks for the existence of a child element <cbr> of element <XPathContentBasedRouter> in the generated jbossesb-listener.xml. This child element is not present, giving a ConfigurationException. The attributes ruleSet and ruleLanguage are attributes of <XPathContentBasedRouter>, not of the child element <cbr>. The following code in CbrListener fixes this problem (original code commented out): protected void checkMyParms() throws ConfigurationException { super.checkMyParms(); // if (_config.getFirstChild(ListenerTagNames.CBR_TAG)==null) { // _logger.error("Required child element " + ListenerTagNames.CBR_TAG + " not found in " + _config.getName() + "."); // throw new ConfigurationException("Required child element " + ListenerTagNames.CBR_TAG + " not found."); // } else { // _ruleSet =_config.getFirstChild(ListenerTagNames.CBR_TAG).getAttribute(ListenerTagNames.RULE_SET_TAG); // if (_ruleSet==null) { // throw new ConfigurationException("Required attribute " + ListenerTagNames.RULE_SET_TAG + " not found."); // } // _ruleLanguage =_config.getFirstChild(ListenerTagNames.CBR_TAG).getAttribute(ListenerTagNames.RULE_LANGUAGE_TAG); // } _ruleSet =_config.getAttribute(ListenerTagNames.RULE_SET_TAG); if (_ruleSet==null) { throw new ConfigurationException("Required attribute " + ListenerTagNames.RULE_SET_TAG + " not found."); } _ruleLanguage =_config.getAttribute(ListenerTagNames.RULE_LANGUAGE_TAG); } This fix was tested with the simple_cbr quickstart. -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-812) Container jndi space is named java:comp.ejb3 instead of java:comp

by Carlo de Wolf (JIRA)

Container jndi space is named java:comp.ejb3 instead of java:comp ----------------------------------------------------------------- Key: EJBTHREE-812 URL: http://jira.jboss.com/jira/browse/EJBTHREE-812 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-289) Recovery does not stop warning messages

by Mark Little (JIRA)

Recovery does not stop warning messages --------------------------------------- Key: JBESB-289 URL: http://jira.jboss.com/jira/browse/JBESB-289 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 >From Burr: "While the standalone listener/gateway are up and running (as presently demonstrated by the current quickstarts) and you kill the AS, all sorts of messages are thrown to the console. Which should be expected. However, if you leave the listener running and then restart the AS errors continue to appear on the listener's console even though it appears to "recover" from having it's connected AS killed. In other words, it works but continues to throw stack traces to the console. " -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-271) Over-use of reflection

by Mark Little (JIRA)

Over-use of reflection ---------------------- Key: JBESB-271 URL: http://jira.jboss.com/jira/browse/JBESB-271 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Reporter: Mark Little Assigned To: Mark Little Fix For: 5.0 The ESB core uses reflection a lot. In some situations it is over-used to the degree that critical errors can only be checked at runtime. We should re-evaluate the use of reflection throughout the implementation and only use it where it helps. -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-332) Tidy up formatting in the Configuration section of the Programmers Guide.

by Tom Fennelly (JIRA)

Tidy up formatting in the Configuration section of the Programmers Guide. ------------------------------------------------------------------------- Key: JBESB-332 URL: http://jira.jboss.com/jira/browse/JBESB-332 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 CR1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Priority: Minor Fix For: 4.0 CR2 -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-337) FtpFileHandler assumes no subdirectories in getFileContents, but does not check

by Mark Little (JIRA)

FtpFileHandler assumes no subdirectories in getFileContents, but does not check ------------------------------------------------------------------------------- Key: JBESB-337 URL: http://jira.jboss.com/jira/browse/JBESB-337 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Esteban Schifman Fix For: 4.0 CR2 Unsure whether this is a bug or inadequate documentation. For now I am assuming the former. Have added the following to the method. String name = file.getName(); if (file.toString().length() > name.length()) { _logger.debug("FtpFileHandler.getFileContents on "+file+" will ignore because of directory."); return null; } -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-724) Client managed failover: messages sent to healthy server end up trying to connect to failed node

by Galder Zamarreno (JIRA)

Client managed failover: messages sent to healthy server end up trying to connect to failed node ------------------------------------------------------------------------------------------------ Key: JBMESSAGING-724 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-724 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Affects Versions: 1.2.0.Beta1, 1.0.1.GA Reporter: Galder Zamarreno Assigned To: Ovidiu Feodorov The attached test case creates connections to two standalone messaging AS servers. It initially sends messages to the first of servers until it fails. At this point, it switches to the second one. This works fine, but at some point in the failover, when the client is sending the messages to the second node, it fails because it attempts to send something again to the first server. This fails with java.net.ConnectException: Connection refused: connect because the first server is already down (replicated-1.0.1.GA-jbossmessaging.log: L12869 ). At line 1208, we shut down server 1 and we start trying to send messages to server 2. After sending a few messages successfully to server 2, suddenly, there's an attempt to connect back to server 1 which fails. I have attached a client log with TRACE on org.jboss and TestMultiConnectionMessageProducer.java which is the test case. I was able to replicate this is in 1.0.1.GA and 1.2.0.Beta1 but not 1.2.0.Alpha2. Forum link fix focuses on the message comsumption area (CallbackManager), but does not provide further information on what might have changed in 1.2.0.Alpha2 to indicate that this is trully solved. -- 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, 3 months

1
5
0 / 0

[JBoss JIRA] Updated: (EJBTHREE-402) Remoting proxies are not declaring serialVersionUIDs

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-402?page=all ] Carlo de Wolf updated EJBTHREE-402: ----------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Remoting proxies are not declaring serialVersionUIDs > ---------------------------------------------------- > > Key: EJBTHREE-402 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-402 > Project: EJB 3.0 > Issue Type: Bug > Affects Versions: EJB 3.0 RC3 > Reporter: Scott M Stark > Assigned To: Carlo de Wolf > Priority: Blocker > Fix For: EJB 3.0 RC10 - FD > > Attachments: warnings.txt > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Same old lack of explicit serialVersionUIDs causing major incompatibilities across releases: > java: org.jnp.interfaces.NamingContext@bd0108 > Looking up RemoteCalculator > javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126] > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:707) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) > at javax.naming.InitialContext.lookup(InitialContext.java:351) > at trail.client.RemoteCalculatorClient.main(RemoteCalculatorClient.java:38) > Caused by: java.io.InvalidClassException: org.jboss.ejb3.stateless.StatelessRemoteProxy; local class incompatible: stream classdesc serialVersionUID = 2583299153931800023, local class serialVersionUID = 8144530673853515126 > at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1546) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1460) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1693) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) > at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912) > at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836) > at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339) > at java.rmi.MarshalledObject.get(MarshalledObject.java:135) > at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:57) > at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:637) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-828) getMessageContext Not Implemented

by Thomas Diesler (JIRA)

getMessageContext Not Implemented --------------------------------- Key: EJBTHREE-828 URL: http://jira.jboss.com/jira/browse/EJBTHREE-828 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Thomas Diesler Priority: Critical Fix For: EJB 3.0 RC10 - FD jboss-4.0.4.GA with EJB3-RC9FD thows a NOT IMPLEMENTED Exception when form the SessionContext he method getMessageContext is called. Form this version with the new JbossWS stack as far i know i not anymore possible to retreive a SOAP attachement . With the old ws4ee was possible calling the org.jboss.axis.MessageContext.getCurrentContext(); without calling SessionContext but now all the axis stuff has been removed :( -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (EJBTHREE-592) Deployment of EJB3s using Interceptors fails

by Carlo de Wolf (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-592?page=all ] Carlo de Wolf resolved EJBTHREE-592. ------------------------------------ Resolution: Rejected Interceptors have moved to javax.interceptor.Interceptors. > Deployment of EJB3s using Interceptors fails > -------------------------------------------- > > Key: EJBTHREE-592 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-592 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: J?rg Henne > Assigned To: Carlo de Wolf > > Deployment of EJB3s using Interceptors fails with this Exception > java.lang.TypeNotPresentException: Type javax.ejb.Interceptors not present > at sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:98) > at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:107) > at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:31) > at sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:351) > at sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:175) > at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:69) > at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:52) > at java.lang.Class.initAnnotationsIfNecessary(Class.java:2998) > at java.lang.Class.getAnnotation(Class.java:2958) > at org.jboss.aop.annotation.AnnotationElement.getVisibleAnnotation(AnnotationElement.java:88) > at org.jboss.aop.Advisor.resolveAnnotation(Advisor.java:327) > at org.jboss.ejb3.ProxyDeployer.initializeRemoteBindingMetadata(ProxyDeployer.java:127) > at org.jboss.ejb3.SessionContainer.instantiated(SessionContainer.java:70) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:573) > at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:555) > at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:536) > at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:508) > at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:463) > at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:125) > at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) > at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) > 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) > ... > The exception isn't terribly surprising consindering that the annotation class just isn't there, which one is already told about by the build script referencing $JBOSS_HOME/server/xxx/deploy/ejb3.deployer/*.jar -- 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, 3 months

1
0
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 January 2007