September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBMESSAGING-4) Load balancing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-4?page=all ] Ovidiu Feodorov updated JBMESSAGING-4: -------------------------------------- Assignee: Tim Fox > Load balancing > -------------- > > Key: JBMESSAGING-4 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-4 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Clustering > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-4) Load balancing

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-4?page=all ] Ovidiu Feodorov closed JBMESSAGING-4. ------------------------------------- Resolution: Done Distributed destinations are done. > Load balancing > -------------- > > Key: JBMESSAGING-4 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-4 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Clustering > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha1 > > -- 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, 8 months

1
0
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.Alpha2 (was: 1.2.0.Alpha1) > 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.Alpha2 > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-356) Session bean assertions

by Gavin King (JIRA)

Session bean assertions ----------------------- Key: JBSEAM-356 URL: http://jira.jboss.com/jira/browse/JBSEAM-356 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King For people who like more of a design-by-contract style, we could let you specify Hibernate Validator annotations on the session bean, and check them after @PostConstruct and before and after each business method. eg. @Stateful public class Foo { @NotNull private Bar bar; @Min(0) int count; } -- 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, 8 months

1
1
0 / 0

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

by Andrew Rubinger (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-402?page=comments#action_12344235 ] Andrew Rubinger commented on EJBTHREE-402: ------------------------------------------ Correction, the patch installer does not update $JBOSS_HOME/client/jboss-ejb3-client.jar > 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 > Priority: Critical > Fix For: EJB 3.0 RC10 - FD > > > 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, 8 months

1
0
0 / 0

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

by Andrew Rubinger (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-402?page=comments#action_12344231 ] Andrew Rubinger commented on EJBTHREE-402: ------------------------------------------ EJB3 RC9 Patch Installer for JBoss AS 4.0.4-GA does not update $JBOSS_HOME/client/jboss-ejb3.jar. If you're running a standalone client, and this JAR is in your classpath, you will receive the deserialization errors above. To fix, ensure your client is referencing the version of jboss-ejb3.jar found in $JBOSS_HOME/server/deploy/[instanceName]/ejb3.deployer. S, ALR > 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 > Priority: Critical > Fix For: EJB 3.0 RC10 - FD > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-117) release notes for JTS talk about context interceptor

by Mark Little (JIRA)

release notes for JTS talk about context interceptor ---------------------------------------------------- Key: JBTM-117 URL: http://jira.jboss.com/jira/browse/JBTM-117 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, JTS Implementation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 Should update to talk about interposition interceptor. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Commented: (JBTM-27) Integrate Web Services transactions component with JBoss 4

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-27?page=comments#action_12344226 ] Kevin Conner commented on JBTM-27: ---------------------------------- The web services component was actually integrated in release 4.2.1. > Integrate Web Services transactions component with JBoss 4 > ---------------------------------------------------------- > > Key: JBTM-27 > URL: http://jira.jboss.com/jira/browse/JBTM-27 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2.1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-27) Integrate Web Services transactions component with JBoss 4

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-27?page=all ] Kevin Conner closed JBTM-27. ---------------------------- Fix Version/s: 4.2.1 (was: 4.2.2) Resolution: Done > Integrate Web Services transactions component with JBoss 4 > ---------------------------------------------------------- > > Key: JBTM-27 > URL: http://jira.jboss.com/jira/browse/JBTM-27 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2.1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2299) OutOfMemory error when repetatively deploying and undeploying with 10 minute interval

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2299?page=comments#action_12344221 ] Clebert Suconic commented on JBAS-2299: --------------------------------------- We could update BeanUtils to use SoftReferences on reflection. The easiest way to do this would be to use PersistentReference (a package I created for JBossSerialization) and recreate reflection automatically in case the SoftReference is released earlier than expected. We could contribute PersistentReferences to Apache and use it on BeanUtils. (But I don't know if we want to do this. I know we could since I"m the author of the package) http://fisheye.jboss.org/browse/JBoss/jboss-serialization/src/org/jboss/s... > OutOfMemory error when repetatively deploying and undeploying with 10 minute interval > ------------------------------------------------------------------------------------- > > Key: JBAS-2299 > URL: http://jira.jboss.com/jira/browse/JBAS-2299 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3RC2 > Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07 > Reporter: Amar Syed > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.6.CR1 > > Attachments: Data.txt, SampleApp.ear > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Using a manual copy and delete mechanism with the server\default\deploy folder the sample ear (attached) caused an outofmemory error eventually after 90 repetitions. > The min and max heap settings were configured as : -Xms128m -Xmx512m > The time delay after dropping/deploying the ear at each repetition was set to 10 minutes after which the ear is deleted/undeployed followed by a 10 second sleep till the next deploy cycle. > I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is supposed to have fixed this issue. > The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows: > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50, cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0} > 2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw error > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] StandardWrapper.Throwable > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > The following two jars were added to the server\default\lib folder. > commons-validator.jar --- version 1.1.3 > struts.jar ---- version 1.2.4 -- 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, 8 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