January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-769) Make ConnectionFactoryUpdateMessage encapsulated in a MarshalledMessage object

by Clebert Suconic (JIRA)

Make ConnectionFactoryUpdateMessage encapsulated in a MarshalledMessage object ------------------------------------------------------------------------------ Key: JBMESSAGING-769 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-769 Project: JBoss Messaging Issue Type: Task Reporter: Clebert Suconic Assigned To: Clebert Suconic Priority: Critical Fix For: 1.2.0.Beta2 -- 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: (JBMESSAGING-781) Fix Clustering Tests

by Clebert Suconic (JIRA)

Fix Clustering Tests -------------------- Key: JBMESSAGING-781 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-781 Project: JBoss Messaging Issue Type: Sub-task Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.Beta2 -- 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
1
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-371) MessageListener times out on inactivity, after receiving at least one message

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-371?page=all ] Ovidiu Feodorov updated JBMESSAGING-371: ---------------------------------------- Fix Version/s: 1.2.0.CR1 (was: 1.0.1.CR2) (was: 1.2.0.Beta2) > MessageListener times out on inactivity, after receiving at least one message > ----------------------------------------------------------------------------- > > Key: JBMESSAGING-371 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-371 > Project: JBoss Messaging > Issue Type: Bug > Components: JMS Remoting > Affects Versions: 1.0.1.CR1, 1.2.0.Beta2 > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Blocker > Fix For: 1.2.0.CR1 > > > 15:15:31,530 ERROR [ServerThread] socket timed out > java.net.SocketTimeoutException: Read timed out > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:129) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:183) > at java.io.BufferedInputStream.read(BufferedInputStream.java:201) > at java.io.FilterInputStream.read(FilterInputStream.java:66) > at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140) > at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464) > at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381) > at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498) > at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240) -- 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: (JBESB-380) Custom composer for GatewayListeners not working

by Bernard Tison (JIRA)

Custom composer for GatewayListeners not working ------------------------------------------------ Key: JBESB-380 URL: http://jira.jboss.com/jira/browse/JBESB-380 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Bernard Tison Assigned To: Mark Little The GatewayListeners (FileGatewayListener, JmsGatewayListener, ..) allow for a custom message composer instead of the default one, by attaching an action element to the gateway service definition in jbossesb.xml. But this action element is not picked up by the GatewayGenerator and is not copied into the jbossesb-gateway.xml file. The GatewayListener doesn't find the action definition in its config tree and falls back to the default composer. -- 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

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-782) The number of times a callback client invoker retries a failed invocation should be at least 2

by Ovidiu Feodorov (JIRA)

The number of times a callback client invoker retries a failed invocation should be at least 2 ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-782 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-782 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Affects Versions: 1.2.0.Beta1 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta2 -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-4027) JBoss Server Reporting not enough heap when using newsize jvm parameter

by tony anecito (JIRA)

JBoss Server Reporting not enough heap when using newsize jvm parameter ----------------------------------------------------------------------- Key: JBAS-4027 URL: http://jira.jboss.com/jira/browse/JBAS-4027 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta1 Environment: Windows 2000 Professional jdk 1.6.1 Reporter: tony anecito I get an error message about not enough heap allocated for -XX:newsize when using even 300m. Works fine in 4.0.5GA -- 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: (JBAS-3897) Switch to JSF1.2 RI implementation

by Dimitris Andreadis (JIRA)

Switch to JSF1.2 RI implementation ---------------------------------- Key: JBAS-3897 URL: http://jira.jboss.com/jira/browse/JBAS-3897 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JavaServerFaces Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Replace the MyFaces implementation with the JSF1.2 RI one. This change combined with the update to Tomcat 6 (through JBossWeb) Ideally we should be able to switch between the 2 JSF implementations. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-4026) failing org.jboss.test.web.test.JSFIntegrationUnitTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.web.test.JSFIntegrationUnitTestCase ---------------------------------------------------------- Key: JBAS-4026 URL: http://jira.jboss.com/jira/browse/JBAS-4026 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Server VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.ELsmp OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Stan Silvert Priority: Critical Fix For: JBossAS-4.2.0.CR1 Another one: unknown Error URL file:/services/cruisecontrol/checkout/jboss-4.2-testsuite-sun-1.5/build/output/jboss-4.2.0.CR1/server/all/tmp/deploy/tmp48589jbosstest-jsf-exp.war/ deployment failed org.jboss.deployment.DeploymentException: URL file:/services/cruisecontrol/checkout/jboss-4.2-testsuite-sun-1.5/build/output/jboss-4.2.0.CR1/server/all/tmp/deploy/tmp48589jbosstest-jsf-exp.war/ deployment failed at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:375) at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) 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) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) 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) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy49.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy50.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) 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) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPM-736) constraint violation while deleting process instance

by Alejandro Guizar (JIRA)

constraint violation while deleting process instance ---------------------------------------------------- Key: JBPM-736 URL: http://jira.jboss.com/jira/browse/JBPM-736 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.0.4 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Priority: Critical Methods testDeleteProcessInstanceWithVariables and testDeleteProcessDefinition in GraphSessionDbTest fail with a constraint violation exception. The children of compositeLogs prevent their parent from being deleted. My initial solution is deleting processLogs with a non-null parent first. Afterwards, delete the remaining logs. It seems to work. -- 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: (JBCACHE-952) Remove calls to Exeption.printStackTace

by Elias Ross (JIRA)

Remove calls to Exeption.printStackTace --------------------------------------- Key: JBCACHE-952 URL: http://jira.jboss.com/jira/browse/JBCACHE-952 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Elias Ross Rather than doing e.printStackTrace(), a logger should be called with the appropriate log level and information in all cases. -- 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

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