May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-347) TCP bundling with FLUSH not working

by Bela Ban (JIRA)

TCP bundling with FLUSH not working ----------------------------------- Key: JGRP-347 URL: http://jira.jboss.com/jira/browse/JGRP-347 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 We can make TCP with bundling *on* work (timeout 0) if we exchange order of passUp/passDown of the view for a new member in Gms line 509. Since bundler is sending messages in bundles it screws up synchronous step process required for a new member when doing START_FLUSH, view installation, STOP_FLUSH. We have a thread race here on line 509. In order to circumvent that we can *first* pass a view from a join response up to FLUSH and then pass it down. I am not sure how this affects other tests. -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-832) persist annotated classes by using AnnotationConfiguration in HibernateHelper.java

by Chris Russell (JIRA)

persist annotated classes by using AnnotationConfiguration in HibernateHelper.java ---------------------------------------------------------------------------------- Key: JBPM-832 URL: http://jira.jboss.com/jira/browse/JBPM-832 Project: JBoss jBPM Issue Type: Feature Request Components: Core Engine Affects Versions: jBPM 3.2 beta 1 Reporter: Chris Russell Assigned To: Tom Baeyens Fix For: jBPM 3.2 beta 2 Should be able to persist annotated Entitys (classes that dont have a hbm.xml mapping file). To do this is a fairly simple change to HibernateHelper.java. One unresolved question here is why doesnt the hibernate.cfg.xml configuration option <property name="hibernate.ejb.naming_strategy"> get picked up?? HibernateHelper.java .. import org.hibernate.cfg.AnnotationConfiguration; import org.hibernate.cfg.DefaultComponentSafeNamingStrategy; . . public static Configuration createConfiguration(String cfgXmlResource, String propertiesResource) { AnnotationConfiguration configuration = new AnnotationConfiguration(); //NOT SURE WHY BUT configuration not picking up //hibernate.cfg.xml //<property name="hibernate.ejb.naming_strategy"> //org.hibernate.cfg.DefaultComponentSafeNamingStrategy</property> log.debug("NAMING START STRATEGY ["+configuration.getNamingStrategy().getClass().getName()+"]"); log.debug(configuration.setNamingStrategy(new DefaultComponentSafeNamingStrategy())); log.debug("NAMING AFTER STRATEGY ["+configuration.getNamingStrategy().getClass().getName()+"]"); With these changes you can now add mappings to the hibernate.cfg.xml such as <mapping package="foo"/> <mapping class="foo.MyAnnotatedFooClass"/> To pick up annotated classes.... -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4392) Replace j2ee and ejb3x module with javaee module

by Carlo de Wolf (JIRA)

Replace j2ee and ejb3x module with javaee module ------------------------------------------------ Key: JBAS-4392 URL: http://jira.jboss.com/jira/browse/JBAS-4392 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: JBossAS-5.0.0.Beta3 -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-178) Expand the ManagedObject spi to operations/runtime properties

by Scott M Stark (JIRA)

Expand the ManagedObject spi to operations/runtime properties ------------------------------------------------------------- Key: JBMICROCONT-178 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-178 Project: JBoss MicroContainer Issue Type: Feature Request Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0_CR1 Properties that are updatable at runtime as well as operations need to be supported from the ManagedObject spi. -- 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, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch

by Brian Stansberry (JIRA)

Use the JGroups multiplexer in the 4.2 branch --------------------------------------------- Key: JBAS-3940 URL: http://jira.jboss.com/jira/browse/JBAS-3940 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the various channels. Only code change for this is in ClusterPartition; other services use JBoss Cache where it is just a config change. -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-952) Not able to access EJB3 from client running in jre1.6, while it works if client running in jre1.5

by Harsha setty (JIRA)

Not able to access EJB3 from client running in jre1.6, while it works if client running in jre1.5 ------------------------------------------------------------------------------------------------- Key: EJBTHREE-952 URL: http://jira.jboss.com/jira/browse/EJBTHREE-952 Project: EJB 3.0 Issue Type: Bug Environment: JBOSS 4.0.5 GA with EJB3 profile, EJBs - JBOSS running in JRE1.6 and EJBs compiled in JDK1.6. Works well with Client with JRE1.5 but throws "socket corrupted exception" for JRE1.6 This errors appear both on JBOSS installed on Windows XP and Red Hat Linux. Reporter: Harsha setty Priority: Critical Fix For: EJB 3.0 RC9 - FD When my java client runs in JRE1.6, it throws the exception Exception in thread "main" java.lang.reflect.UndeclaredThrowableException at $Proxy0.authenticateUser(Unknown Source) at gui.Test.main(Test.java:40) Caused by: java.rmi.MarshalException: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: java.io.StreamCorruptedException: invalid type code: 00 at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:306) at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143) at org.jboss.remoting.Client.invoke(Client.java:525) at org.jboss.remoting.Client.invoke(Client.java:488) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:53) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) ... 2 more Caused by: java.io.StreamCorruptedException: invalid type code: 00 at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readArray(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:122) at java.io.ObjectInputStream.readExternalData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:128) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:279) ... 14 more -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4377) DataSource deployer needs to take over ConnectionFactoryDeployerManagedObjectBuilder

by Scott M Stark (JIRA)

DataSource deployer needs to take over ConnectionFactoryDeployerManagedObjectBuilder ------------------------------------------------------------------------------------- Key: JBAS-4377 URL: http://jira.jboss.com/jira/browse/JBAS-4377 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Weston Price The org.jboss.profileservice.management.builders.ConnectionFactoryDeployerManagedObjectBuilder override of the data source deployer needs to be moved into the deployers. -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-4125) Move clustering test support classes to test module

by Brian Stansberry (JIRA)

Move clustering test support classes to test module --------------------------------------------------- Key: JBAS-4125 URL: http://jira.jboss.com/jira/browse/JBAS-4125 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Brian Stansberry The org.jboss.test.JBossClusteredTestCase, JBossClusteredTestServices and JBossClusteredTestSetup classes should be moved out of the testsuite module and into test. They are just utility classes to support deployment to more than one AS instance and exposure to test clients of more than one JNDI URL and base HTTP URL. EJB3 uses them as well, so they need to be in a binary to allow EJB3 to decouple from the AS. This should be done on both trunk and Branch_4_2. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-823) Unable to call ejb remotely

by Sureshbabu Thyvalappil (JIRA)

Unable to call ejb remotely --------------------------- Key: EJBTHREE-823 URL: http://jira.jboss.com/jira/browse/EJBTHREE-823 Project: EJB 3.0 Issue Type: Bug Environment: JBOSS 4.0.5 with EJB 3.0 Reporter: Sureshbabu Thyvalappil I'm using JBOSS 4.0.5GA with ejb3. I am running into weird behavior when running java client from remote machine. If I run it from the same machine where the jboss server is running, no problem. So here is the behavior I'm noticing. FOr the jndi lookup of ejb, it is connecting the remote server and gets a reference to the ejb. But when I call a method on the ejb reference, it is trying to call a method on the local machine( I mean the same machine where the client is running). Sounds very weird to me. Any help is appreciated from EJB3 experts. I upgraded to EJB3 RC9 patch1, but same behavior. Here is the client code .. try { Properties p=new Properties(); p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); p.put(Context.PROVIDER_URL,"jnp://remote-host:1099"); InitialContext ctx = new InitialContext(p); IReportService report = (IReportService) ctx.lookup( "ejb3/xxx/ReportService"); System.out.println("Got the ejb remote reference = "+report); System.out.println("report.resubmit.."+report.resubmit(null,0L)); ReportJob reportJob = new ReportJob(); System.out.println("B4 report.submitRequest.."); report.submitRequest(reportJob); System.out.println("After report.submitRequest.."); } catch (Exception e) { e.printStackTrace(); } -- 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, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3572) Fix the NPEs (better error handling) identified by the new ServiceController testsuite

by Adrian Brock (JIRA)

Fix the NPEs (better error handling) identified by the new ServiceController testsuite -------------------------------------------------------------------------------------- Key: JBAS-3572 URL: http://jira.jboss.com/jira/browse/JBAS-3572 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Reporter: Adrian Brock The new testsuite in system[-jmx] has identifies a number of areas where the old Service deployment (including the impl in JBoss4) does not give a reasonable error message, e.g. it throws an NPE These need to be fixed. -- 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, 11 months

3
6
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 May 2007