September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMESSAGING-302) Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-302?page=all ] Ovidiu Feodorov closed JBMESSAGING-302. --------------------------------------- Resolution: Done > Invoking Topic management interface's listMessagesDurableSub()/ listMessagesNonDurableSub() with empty params throws exception > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBMESSAGING-302 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-302 > Project: JBoss Messaging > Issue Type: Bug > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > 9:18:53,568 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception > ava.lang.NumberFormatException: For input string: "" > at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) > at java.lang.Long.parseLong(Long.java:424) > at java.lang.Long.valueOf(Long.java:518) > at sun.beans.editors.LongEditor.setAsText(LongEditor.java:24) > at org.jboss.util.propertyeditor.PropertyEditors.convertValue(PropertyEditors.java:260) > at org.jboss.jmx.adaptor.control.Server.invokeOpByName(Server.java:239) > at org.jboss.jmx.adaptor.control.Server.invokeOp(Server.java:223) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.invokeOp(HtmlAdaptorServlet.java:262) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.processRequest(HtmlAdaptorServlet.java:100) > at org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.doPost(HtmlAdaptorServlet.java:82) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:54) > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:173) > at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) > at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > at java.lang.Thread.run(Thread.java:595) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-550) Add JBoss 4.0.5.CR1 (expanded and installer-generated) to the smoke test suite

by Ovidiu Feodorov (JIRA)

Add JBoss 4.0.5.CR1 (expanded and installer-generated) to the smoke test suite ------------------------------------------------------------------------------ Key: JBMESSAGING-550 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-550 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Minor -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-715) complete implementation of interceptor-order in ejb-jar.xml

by William DeCoste (JIRA)

complete implementation of interceptor-order in ejb-jar.xml ----------------------------------------------------------- Key: EJBTHREE-715 URL: http://jira.jboss.com/jira/browse/EJBTHREE-715 Project: EJB 3.0 Issue Type: Task Reporter: William DeCoste Assigned To: William DeCoste -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3684) References to TxManager

by Kevin Conner (JIRA)

References to TxManager ----------------------- Key: JBAS-3684 URL: http://jira.jboss.com/jira/browse/JBAS-3684 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.0.5.CR1 Reporter: Kevin Conner Assigned To: Bill Burke Priority: Critical The following classes contain direct references to org.jboss.tm.TxManager. These references prevent JBossTS being used as a replacement for TxManager. ejb3/src/main/org/jboss/ejb3/tx/TxInterceptorFactory.java ejb3/src/main/org/jboss/ejb3/entity/ManagedEntityManagerFactory.java These should be changed to defer to TxUtil or to use TransactionManagerLocator.getInstance().locate(). -- 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, 10 months

4
3
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-207) HTTP invoker configuration and testing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-207?page=all ] Ovidiu Feodorov updated JBMESSAGING-207: ---------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.0.1.CR5) > HTTP invoker configuration and testing > -------------------------------------- > > Key: JBMESSAGING-207 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-207 > Project: JBoss Messaging > Issue Type: Task > Components: Configuration and Management > Reporter: Ovidiu Feodorov > Assigned To: Ron Sigal > Priority: Blocker > Fix For: 1.2.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Provide a HTTP invoker initial configuration and a working example. > Add the example to docs/examples so it can be used as an integration test. > Reviewed requirements: > 1. The messaging client needs to connect to the server over HTTP > 2. We need it implemented in such a way that there's no socket listening on the client, but the client can still receive messages asynchronously. > 3. When the change is completed, all current Messaging functional tests, stress tests and smoke test must pass. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-526) JMSRedelivered flag not correctly set on true in certain redelivery scenarios

by Ovidiu Feodorov (JIRA)

JMSRedelivered flag not correctly set on true in certain redelivery scenarios ----------------------------------------------------------------------------- Key: JBMESSAGING-526 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-526 Project: JBoss Messaging Issue Type: Bug Components: JMS Facade Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 Added TransactedSessionTest.testRedeliveredQueue2() that currently fails. -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3689) Naming fails to accept a custom client socket

by Scott M Stark (JIRA)

Naming fails to accept a custom client socket --------------------------------------------- Key: JBAS-3689 URL: http://jira.jboss.com/jira/browse/JBAS-3689 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.0.3 SP1 Reporter: Scott M Stark Assigned To: Scott M Stark Attempting to set a custom client socket on the NamingService <mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming" xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">  <attribute name="CallByValue">false</attribute>  <attribute name="Port">1099</attribute> <attribute name="RmiPort">1098</attribute>  <attribute name="BindAddress">${iface.A}</attribute> <attribute name="RmiBindAddress">${iface.A}</attribute>  <depends optional-attribute-name="LookupPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends> <attribute name="ClientSocketFactory">case9179.TimeoutClientSocketFactory</attribute> </mbean> fails with: 2006-09-22 12:46:12,417 WARN [org.jboss.naming.NamingService] Failed to setBindAddress=/192.168.2.107 on socket factory java.lang.NullPointerException: case9179.TimeoutClientSocketFactory.setBindAddress invoked on null object at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;J)Ljava.lang.Object;(Unknown Source) at org.jnp.server.Main.initCustomSocketFactories(Main.java:355) at org.jnp.server.Main.start(Main.java:255) at org.jboss.naming.NamingService.startService(NamingService.java:221) The problem is that there copy/paste error at line 355: protected void initCustomSocketFactories() { // Use either the rmiBindAddress or bindAddress for the RMI service InetAddress addr = rmiBindAddress; if( addr == null ) addr = bindAddress; if( clientSocketFactory != null ) { // See if the client socket supports setBindAddress(String) try { Class csfClass = clientSocketFactory.getClass(); Class[] parameterTypes = {String.class}; Method m = csfClass.getMethod("setBindAddress", parameterTypes); Object[] args = {addr.getHostAddress()}; m.invoke(serverSocketFactory, args); // +++ line 355, This should be clientSocketFactory } catch (NoSuchMethodException e) { log.warn("Socket factory does not support setBindAddress(String)"); // Go with default address } -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-523) implement jmx-name in jboss.xml

by William DeCoste (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-523?page=all ] William DeCoste closed EJBTHREE-523. ------------------------------------ Fix Version/s: EJB 3.0 RC10 - FD Resolution: Done > implement jmx-name in jboss.xml > ------------------------------- > > Key: EJBTHREE-523 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-523 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: William DeCoste > Assigned To: William DeCoste > Priority: Minor > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3683) snmp-adaptor.sar/attributes.mib MIB syntax errors

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3683?page=all ] Dimitris Andreadis updated JBAS-3683: ------------------------------------- Fix Version/s: JBossAS-4.0.5.GA (was: JBossAS-4.0.6.CR1) > snmp-adaptor.sar/attributes.mib MIB syntax errors > ------------------------------------------------- > > Key: JBAS-3683 > URL: http://jira.jboss.com/jira/browse/JBAS-3683 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Environment: Using NET-SNMP 5.2.3 to parse the MIB > Reporter: Gerald Turner > Assigned To: Dimitris Andreadis > Priority: Trivial > Fix For: JBossAS-4.0.5.GA > > Attachments: snmp-adaptor-attributes.mib.patch.gz > > > Trivial patch to fix some syntax errors in attributes.mib. Things like the operator ":: =" cannot include a space and STATUS must be defined in an OBJECT-TYPE. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3683) snmp-adaptor.sar/attributes.mib MIB syntax errors

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3683?page=all ] Dimitris Andreadis reassigned JBAS-3683: ---------------------------------------- Assignee: Dimitris Andreadis > snmp-adaptor.sar/attributes.mib MIB syntax errors > ------------------------------------------------- > > Key: JBAS-3683 > URL: http://jira.jboss.com/jira/browse/JBAS-3683 > Project: JBoss Application Server > Issue Type: Patch > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Environment: Using NET-SNMP 5.2.3 to parse the MIB > Reporter: Gerald Turner > Assigned To: Dimitris Andreadis > Priority: Trivial > Fix For: JBossAS-4.0.6.CR1 > > Attachments: snmp-adaptor-attributes.mib.patch.gz > > > Trivial patch to fix some syntax errors in attributes.mib. Things like the operator ":: =" cannot include a space and STATUS must be defined in an OBJECT-TYPE. -- 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, 10 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 September 2006