July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBASPECT-25) jboss-remoting-aspects POM references tags in SCM

by Andrew Lee Rubinger (JIRA)

jboss-remoting-aspects POM references tags in SCM ------------------------------------------------- Key: JBASPECT-25 URL: https://jira.jboss.org/jira/browse/JBASPECT-25 Project: JBoss Aspects Issue Type: Bug Components: remoting Affects Versions: 1.0.1.CR2 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Should be pointing to trunk -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1011) Release 2.2.2.SP9

by Ron Sigal (JIRA)

Release 2.2.2.SP9 ----------------- Key: JBREM-1011 URL: https://jira.jboss.org/jira/browse/JBREM-1011 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1017) Improve socket timeout log message

by Takayoshi Kimura (JIRA)

Improve socket timeout log message ---------------------------------- Key: JBREM-1017 URL: https://jira.jboss.org/jira/browse/JBREM-1017 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Takayoshi Kimura Fix For: 2.2.2.SP7 Attachments: log.zip, testcase.zip When tesing remoting compatibility between AS 4.0.5 and EAP 4.3.0.GA_CP01, I got the following exception messages: In server: 2008-07-22 22:55:57,281 ERROR [org.jboss.remoting.serialization.impl.java.JavaSerializationManager] java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion1_2(JavaSerializationManager.java:180) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:130) at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:120) at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:59) at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:663) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:533) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166) In client: 2008-07-22 22:55:57,178 ERROR [org.jboss.remoting.transport.socket.SocketClientInvoker] Got marshalling exception, exiting java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:66) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:110) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1647) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1556) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1357) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281) at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:81) at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:84) at org.jboss.invocation.unified.marshall.InvocationMarshaller.write(InvocationMarshaller.java:66) at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:273) 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.invocation.unified.interfaces.UnifiedInvokerProxy.invoke(UnifiedInvokerProxy.java:175) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:112) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy1.remove(Unknown Source) at com.redhat.jboss.support.support192039.TestClient.main(TestClient.java:39) Actually it was just a socket timeout. However, there is information for socket timeout unless we set TRACE log level on org.jboss.remoting. Need more clearer log message at least DEBUG level. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
7
0 / 0

[JBoss JIRA] Created: (JBREM-1014) Support injection of socket factory class name into AbstractInvoker

by Ron Sigal (JIRA)

Support injection of socket factory class name into AbstractInvoker ------------------------------------------------------------------- Key: JBREM-1014 URL: https://jira.jboss.org/jira/browse/JBREM-1014 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP8 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP9 It is intended that org.jboss.remoting.AbstractInvoker can accept the class name of a SocketFactory, using the parameter org.jboss.remoting.Remoting.SOCKET_FACTORY_NAME (actual value "socketFactory"). Unfortunately, the parameter name "socketFactory" conflicts with the bean property of the same name. In particular, the problem is that the method public void setSocketFactory(SocketFactory socketFactory) in AbstractInvoker expects a SocketFactory instead of a String. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
8
0 / 0

[JBoss JIRA] Created: (JBREM-1013) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-1013 URL: https://jira.jboss.org/jira/browse/JBREM-1013 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-83) When mappedName is equal to deploymentScopeBaseName, JNDI Name Collisions occur

by Andrew Lee Rubinger (JIRA)

When mappedName is equal to deploymentScopeBaseName, JNDI Name Collisions occur ------------------------------------------------------------------------------- Key: JBMETA-83 URL: https://jira.jboss.org/jira/browse/JBMETA-83 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta31 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Assuming an EJB with: mappedName = myBase deploymentScopeBaseName = myBase Then the Default Remote Business Interface will be: "myBase" And the base upon which JNDI Names are built will be: "myBase/ejbname/" Because the JNDI Name base starts with the mappedName, which is bound, a subcontext cannot be created and therefore presents a JNDI Collision. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMETA-82) BasicJndiBindingPolicy does not honor explicitly-defined Home JNDI Name

by Andrew Lee Rubinger (JIRA)

BasicJndiBindingPolicy does not honor explicitly-defined Home JNDI Name ----------------------------------------------------------------------- Key: JBMETA-82 URL: https://jira.jboss.org/jira/browse/JBMETA-82 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta31 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger In the case that a Home JNDI name is explicitly-defined, the BasicJnidBindingPolicy is ignoring it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2089) NPE with deleting a file in pending stage

by Prabhat Jha (JIRA)

NPE with deleting a file in pending stage ----------------------------------------- Key: JBPORTAL-2089 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2089 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Reporter: Prabhat Jha Assignee: Sohil Shah Fix For: 2.6.6 Final - Create a file. - Keep it in pending state - Select pending items from drop down menu - Click on the the file you just created - Select Delete file from drop down and confirm deletion - Select pending items from drop down and hit approve. You will get NPE which is expected. Once file is deleted, it should not be in any list. java.lang.NullPointerException at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.internalDoView(CMSAdminPortlet.java:341) at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.doView(CMSAdminPortlet.java:184) at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:257) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:244) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:390) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeRender(PortletContainerImpl.java:483) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:405) at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(PortletContainerInvoker.java:86) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:106) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103964459766407072.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeRequired(TransactionInterceptor.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:72) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:50) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.portlet.aspects.portlet.ProducerCacheInterceptor.invoke(ProducerCacheInterceptor.java:58) at org.jboss.portal.portlet.invocation.PortletInterceptor.invoke(PortletInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2088) uploading a file shows up in list when it's not approved

by Prabhat Jha (JIRA)

uploading a file shows up in list when it's not approved -------------------------------------------------------- Key: JBPORTAL-2088 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2088 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Reporter: Prabhat Jha Assignee: Sohil Shah Fix For: 2.6.6 Final I uploaded a simple text file. When it came to approval, I denied it. But it still shows up file list in that folder. I can delete this from the list but I think that should not have made to the list. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 12 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-742) UNICAST connection trashing during merge

by Vladimir Blagojevic (JIRA)

UNICAST connection trashing during merge ---------------------------------------- Key: JGRP-742 URL: http://jira.jboss.com/jira/browse/JGRP-742 Project: JGroups Issue Type: Bug Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.6.3 JGRP-348 describes an edge case that causes interruption of unicast communication between two separate unmerged JGroups network islands. However, a fix for JGRP-348 introduced even a bigger edge case of the same problem described in JGRP-659. For 2.6.3 release we will revert changes made in JGRP-348. To handle an edge case described in JGRP-348 we recommend use of FD_ALL failure detection protocol. JGRP-659 will be solved properly in 2.7 to handle both edge cases out of the box. -- 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, 12 months

2
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 July 2008