October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1195) Fix tutorial for 2.1.0 series

by Manik Surtani (JIRA)

Fix tutorial for 2.1.0 series ----------------------------- Key: JBCACHE-1195 URL: http://jira.jboss.com/jira/browse/JBCACHE-1195 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA As a part of mavenising, the tutorial has broken. The steps to follow in the tutorial do not produce results expected. Needs to be fixed for CR1. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1619) Multiple maximized windows

by Ovidiu Nichifor (JIRA)

Multiple maximized windows -------------------------- Key: JBPORTAL-1619 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1619 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6 Final Reporter: Ovidiu Nichifor Assigned To: Julien Viet Once you authenticate (admin/admin) you'll be brought to the default page of the user account. Suppose the default page contains the "Greetings" and "User" portlets. I have noticed something strange that i don't know if it is really a bug or a feature. If you follow the next steps: 1. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/JSPPortletWindow?windowstate=maximized 2. with your browser access: http://<hostname>:<port>/portal/auth/portal/default/default/UserPortletWindow?windowstate=maximized without normalize first the previous maximized window. you'll have two windows that are both in the maximized state. Now, the portal should present to you the last maximized window. If you try to normalize/minimize the maximized window, the portal will display the other maximized window instead of bringing you back to the page in the "normal" state (i.e. with all defined portlets on it). Is this the way it should work? I've been digging in the JBoss Portal 2.6.ALPHA1 source code and i found a "ensureSingleMaximizedWindow" method in the "org.jboss.portal.theme.impl.strategy.MaximizingStrategyImpl" file that does nothing - only throws a FixMe exception. Both JBP-2.6.FINAL & JBP-2.6.ALPHA1 have the same behavior on the test case i described so i assume the maximizing strategy hasn't been changed. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4880) TECH REVIEW: Installation Guide - Chapter 1 - Installing JBoss

by Michael Smith (JIRA)

TECH REVIEW: Installation Guide - Chapter 1 - Installing JBoss --------------------------------------------------------------- Key: JBAS-4880 URL: http://jira.jboss.com/jira/browse/JBAS-4880 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Installation Guide Affects Versions: JBossAS-4.2.2.GA Reporter: Michael Smith Attachments: JBAS-422-Installation_Guide-Chapter-1.odt Attached is an Open Office 2.0 Document contain chapter 1 of the Installation Guide. 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Installation_Guide/beta422/html/ch01.html -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Deleted: (JBAS-4894) port-component element not mapped

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4894?page=all ] Thomas Diesler deleted JBAS-4894: --------------------------------- > port-component element not mapped > --------------------------------- > > Key: JBAS-4894 > URL: http://jira.jboss.com/jira/browse/JBAS-4894 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assigned To: Scott M Stark > > I can't find the port-component element mapped to the metadata model. > <xsd:complexType name="generic-beanType"> > <xsd:sequence> > <xsd:group ref="javaee:descriptionGroup"/> > <xsd:element name="ejb-name" type="javaee:ejb-nameType"/> > <xsd:element name="jndi-name" type="javaee:jndi-nameType" minOccurs="0"/> > <xsd:element name="ejb-ref" type="javaee:jboss-ejb-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="ejb-local-ref" type="javaee:jboss-ejb-local-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="service-ref" type="javaee:jboss-service-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="security-identity" type="javaee:security-identityType" minOccurs="0"/> > <xsd:element name="resource-ref" type="javaee:jboss-resource-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="resource-env-ref" type="javaee:jboss-resource-env-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="message-destination-ref" type="javaee:jboss-message-destination-refType" minOccurs="0" maxOccurs="unbounded"/> > <xsd:element name="port-component" type="tns:port-component-type" minOccurs="0" maxOccurs="1"/> >  > <xsd:group ref="javaee:jndiEnvironmentRefsGroup"/> > </xsd:sequence> > </xsd:complexType> -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4894) port-component element not mapped

by Thomas Diesler (JIRA)

port-component element not mapped --------------------------------- Key: JBAS-4894 URL: http://jira.jboss.com/jira/browse/JBAS-4894 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assigned To: Scott M Stark -- 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, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1055) WebServiceContext is not injected before post construct is called

by Carlo de Wolf (JIRA)

WebServiceContext is not injected before post construct is called ----------------------------------------------------------------- Key: EJBTHREE-1055 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1055 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf JAX-WS 2.0 5.2.1: After any injections have been performed and before any requests are dispatched to the implementor, the implementor method which carries a javax.annotation.PostConstruct annotation, if present, MUST be invoked. -- 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, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1032) inconsistent results for CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs

by William DeCoste (JIRA)

inconsistent results for CreateCount, AvailableCount, CurrentSize for StrictMaxPool SLSBs ----------------------------------------------------------------------------------------- Key: EJBTHREE-1032 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1032 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1031) runaway SLSB instance creation with ThreadLocalPool

by William DeCoste (JIRA)

runaway SLSB instance creation with ThreadLocalPool --------------------------------------------------- Key: EJBTHREE-1031 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1031 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA Reporter: William DeCoste Assigned To: William DeCoste Use of WeakThreadLocal vs ThreadLocal is the cause. -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1025) @Local and @Remote on a bean class must have values

by Carlo de Wolf (JIRA)

@Local and @Remote on a bean class must have values --------------------------------------------------- Key: EJBTHREE-1025 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1025 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA Reporter: Carlo de Wolf Fix For: AS 4.2.2.GA, EJB 3.0 RC11 - FD The following is an illegal construct: @Stateless @Local @Remote public class OrderServiceBean implements OrderService {...} -- 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, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-986) EJB3 Remoting cause BindException on load

by Yvan Borgne (JIRA)

EJB3 Remoting cause BindException on load ----------------------------------------- Key: EJBTHREE-986 URL: http://jira.jboss.com/jira/browse/EJBTHREE-986 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 GA Environment: JBoss 4.2.0 GA, JDK 1.5.0_08-b03, Windows XP SP2 Reporter: Yvan Borgne After a lot of call (>3000) to an EJB3 SLSB this exception is throwed : org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://127.0.0.1:3873/] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) 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:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103) at $Proxy0.bar(Unknown Source) at client.Test.main(Test.java:22) Caused by: java.net.BindException: Address already in use: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:516) at org.jboss.remoting.transport.socket.SocketClientInvoker.createSocket(SocketClientInvoker.java:187) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection(MicroSocketClientInvoker.java:801) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:526) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1550) at org.jboss.remoting.Client.invoke(Client.java:530) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) 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:72) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103) at $Proxy0.bar(Unknown Source) at client.Test.main(Test.java:22) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:74) ... 10 more Jboss server and test client are on the same host. For each call, a new TCP connection is opened, with a different local port. So there is also a performance problem. Here is a simple code to reproduce : -- EJB3 remote Interface -- package ejb; import javax.ejb.Remote; @Remote public interface Foo { public void bar(); } -- EJB3 Implementation -- package ejb; import javax.ejb.Stateless; @Stateless public class FooBean implements Foo { public void bar() { } } -- client -- package client; import java.util.Properties; import javax.naming.Context; import javax.naming.InitialContext; import ejb.Foo; public class Test { public static void main(String[] args) { try { Properties env = new Properties(); env.put(Context.PROVIDER_URL, "jnp://localhost:1099"); env.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); env.put("jnp.disableDiscovery", "true"); Context context = new InitialContext(env); Foo foo = (Foo)context.lookup("FooBean/remote"); while(true) { foo.bar(); } } 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, 9 months

4
8
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 October 2007