September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3707) HA/Failover RAR Functionality should be implemented in non-HA RARS.

by Weston Price (JIRA)

HA/Failover RAR Functionality should be implemented in non-HA RARS. ------------------------------------------------------------------- Key: JBAS-3707 URL: http://jira.jboss.com/jira/browse/JBAS-3707 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.6.CR1 Reporter: Weston Price Assigned To: Weston Price Priority: Optional The HA/DB failover functionality for JDBC RARs currently exists in seperated deployments (ha/xa rars). This functionality should be put into the regular RARs as a deployment option and not as a standalone configuration which is unnecessary. -- 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

17 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-698) Exception serialization issue when remotely accessing stateless session bean

by David Green (JIRA)

Exception serialization issue when remotely accessing stateless session bean ---------------------------------------------------------------------------- Key: EJBTHREE-698 URL: http://jira.jboss.com/jira/browse/EJBTHREE-698 Project: EJB 3.0 Issue Type: Bug Reporter: David Green Accessing a remote EJB (Session bean) results in exception. Stack trace follows: 13:54:39,546 ERROR [SocketClientInvoker] Got marshalling exception, exiting java.lang.ClassNotFoundException: [Ljava.lang.StackTraceElement; at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:50) at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:139) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496) at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1624) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1323) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1945) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1869) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) 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) 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:55) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102) at $Proxy0.postNotification(Unknown Source) at com.hgea.hch.service.HchClientDelegate.postNotification(HchClientDelegate.java:99) at com.hgea.hch.client.RemoteHchClientTest.testRemotePostNotification(RemoteHchClientTest.java:38) 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:597) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567) -- 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

17 years, 5 months

7
7
0 / 0

[JBoss JIRA] Created: (SECURITY-8) LdapExtLoginModule should detect communication failures midstream

by Anil Saldhana (JIRA)

LdapExtLoginModule should detect communication failures midstream ------------------------------------------------------------------ Key: SECURITY-8 URL: http://jira.jboss.com/jira/browse/SECURITY-8 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 http://jira.jboss.com/jira/browse/JBAS-3661 There is a possibility of the context going stale due to communication exceptions with the ldap server when dealing with references etc. It may be useful for the LdapExtLoginModule to implement the: http://java.sun.com/j2se/1.3/docs/api/javax/naming/ldap/UnsolicitedNotifi... such that it can do graceful processing. -- 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

17 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3596) JNDI static cache

by Clebert Suconic (JIRA)

JNDI static cache ----------------- Key: JBAS-3596 URL: http://jira.jboss.com/jira/browse/JBAS-3596 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Clebert Suconic Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.CR1 Having a JNDI caching would improove performance on applications where JNDI is over used. -- 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

17 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-699) StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy

by Michael Grübsch (JIRA)

StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy ----------------------------------------------------------------------- Key: EJBTHREE-699 URL: http://jira.jboss.com/jira/browse/EJBTHREE-699 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC7 - FD Environment: Windows XP Reporter: Michael Grübsch Priority: Critical I refer to source version $Revision: 1.1.4.2 $ This is an excerpt from the stack trace: at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) You may see, that invoke calls getProxyString which in turn on the proxy calls invoke! -- 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

17 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-129) Modify the schema being used from PHPBB

by Sohil Shah (JIRA)

Modify the schema being used from PHPBB --------------------------------------- Key: JBFORUMS-129 URL: http://jira.jboss.com/jira/browse/JBFORUMS-129 Project: JBoss Forums Issue Type: Sub-task Reporter: Sohil Shah Assigned To: Sohil Shah -- 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

17 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBFORUMS-127) Eliminate all GPL dependencies from the new forums

by Sohil Shah (JIRA)

Eliminate all GPL dependencies from the new forums -------------------------------------------------- Key: JBFORUMS-127 URL: http://jira.jboss.com/jira/browse/JBFORUMS-127 Project: JBoss Forums Issue Type: Task Affects Versions: 1.0.0 Alpha Reporter: Sohil Shah Assigned To: Sohil Shah Fix For: 1.1.0 Alpha Need to identify any GPL dependencies and convert to LGPL -- 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

17 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-3511) JMS ASF integration and JMS Session Pools need resource management improvements

by Weston Price (JIRA)

JMS ASF integration and JMS Session Pools need resource management improvements ------------------------------------------------------------------------------- Key: JBAS-3511 URL: http://jira.jboss.com/jira/browse/JBAS-3511 Project: JBoss Application Server Issue Type: Support Patch Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.3 SP1 Reporter: Weston Price Assigned To: Weston Price Priority: Minor A client has requested that the JMS applications server integration facilities for resource management and JMS session pooling be improved primarily in two areas: 1) The ability to not create all JMS sessions on container startup. 2) The ability to recycle/release JMS sessions based on a configurable timeout. Both these features would need to be added to the existing JMSContainerInvoker as well as carried forward to the JBossJCA adapter prior to production release. -- 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

17 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBAS-3406) JMX Console throws 500 exception on regular expressions

by gregorypierce (JIRA)

JMX Console throws 500 exception on regular expressions ------------------------------------------------------- Key: JBAS-3406 URL: http://jira.jboss.com/jira/browse/JBAS-3406 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: OSX 10.4.7 Reporter: gregorypierce When going through the Getting Started guide there is a note to search for service=JNDIView. After bringing up the JNDIView I entered a regular expression to search for all of the JNDI services and the server threw a 500 exception as opposed to saying that that format was not supported. -- 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

17 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle

by Owen Taylor (JIRA)

Way to set JNDI properties for twiddle -------------------------------------- Key: JBAS-3637 URL: http://jira.jboss.com/jira/browse/JBAS-3637 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Owen Taylor Priority: Minor It is frequently useful to be able to set JDNI properties when running twiddle - for example, you might want to set jnp.disableDiscovery when checking the status of a particular server that might not be running. Right now, this is difficult to do. You can export a JBOSS_CLASSPATH which contains a jndi.properties file before running twiddle.sh, but then you have to include all the standard jars in it, which is quite annoying. A pssible fixes would be one of: A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default construction (also useful for getting a log4j.properties that doesn't drop twiddle.log in the cwd, perhaps) B) A command line option for specifying a particular properties file to load and pass to 'new InitialContext()' (slightly more convenient than A) C) A command line option to define particular properties: twiddle.sh -jnpProperty=jnp.disableDiscovery=true (Or some better syntax) The twiddle code actually does: Properties props = new Properties(System.getProperties()); props.put(Context.PROVIDER_URL, serverURL); ctx = new InitialContext(props); In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take effect, and system properties won't be looked at in the other code path either. -- 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

17 years, 6 months

4
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006