April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-367) Research using install and site with multi module project.

by Paul Gier (JIRA)

Research using install and site with multi module project. ---------------------------------------------------------- Key: JBBUILD-367 URL: http://jira.jboss.com/jira/browse/JBBUILD-367 Project: JBoss Build System Issue Type: Feature Request Reporter: Paul Gier Assigned To: Paul Gier JBoss rules is having some problems when running install and site:site when there is an empty repository. A small multimodule project should be created to test this behavior. -- 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

15 years, 4 months

1
6
0 / 0

[JBoss JIRA] Created: (JBBUILD-441) Work on maven build for jboss-messaging

by Paul Gier (JIRA)

Work on maven build for jboss-messaging --------------------------------------- Key: JBBUILD-441 URL: http://jira.jboss.com/jira/browse/JBBUILD-441 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server JBoss messaging has an existing pom.xml, but it looks like this file has not been kept up to date. This should be updated, and the project should be moved over to maven. -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-413) Mavenize remoting project

by Paul Gier (JIRA)

Mavenize remoting project ------------------------- Key: JBBUILD-413 URL: http://jira.jboss.com/jira/browse/JBBUILD-413 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Remoting project needs to be properly mavenized so that app server builds can use it. -- 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

15 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-5220) twiddle not displaying info regarding java.lang:* beans when -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl is used .

by Vicky Kak (JIRA)

twiddle not displaying info regarding java.lang:* beans when -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl is used . -------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-5220 URL: http://jira.jboss.com/jira/browse/JBAS-5220 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.2.0.GA Reporter: Vicky Kak Assigned To: Vicky Kak Starting Jboss with these parameters ./run.sh -Djboss.platform.mbeanserver -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl causes twiddle not to display java.lang:* MBeans [vicky@localhost bin]$ ./twiddle.sh query "java.lang:*" 15:02:14,414 ERROR [Twiddle] Command failure org.jboss.console.twiddle.command.CommandException: No MBean matches for query: java.lang:* at org.jboss.console.twiddle.command.MBeanServerCommand.queryMBeans(MBeanServerCommand.java:72) at org.jboss.console.twiddle.command.QueryCommand.execute(QueryCommand.java:138) at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305) If the Jboss is started as ./run.sh -Djboss.platform.mbeanserver twiddle query "java.lang:*" works . -- 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

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-5364) UnifiedInvokerHAProxy can throw NullPointerException under load

by Galder Zamarreno (JIRA)

UnifiedInvokerHAProxy can throw NullPointerException under load --------------------------------------------------------------- Key: JBAS-5364 URL: http://jira.jboss.com/jira/browse/JBAS-5364 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Under heavy load and sharing an EJB proxy between different threads, there's a chance of NullPointerException like the one below being reported, specially when using proxies configured with RoundRobin as load balance policy, such as SLSBs or EJB2 home proxies: java.lang.NullPointerException at org.jboss.invocation.unified.interfaces.UnifiedInvokerHAProxy.invoke(UnifiedInvokerHAProxy.java:186) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.MarshallingInvokerInterceptor.invoke(MarshallingInvokerInterceptor.java:63) at org.jboss.proxy.ejb.RetryInterceptor.invoke(RetryInterceptor.java:176) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:61) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:184) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy1.create(Unknown Source) Whenever a new target for an invocation is chosen, init(InvokerLocator locator) method in UnifiedInvokerProxy is executed: protected void init(InvokerLocator locator) { this.locator = locator; try { client = createClient(locator, getSubSystem()); client.connect(); } catch(Exception e) { log.fatal("Could not initialize UnifiedInvokerProxy.", e); } } This method could be executed in paralell to the following in UnifiedInvokerHAProxy.invoke(Invocation invocation): Client clientInstance = getClient(invocation); log.debug("Making invocation on " + clientInstance.getInvoker().getLocator()); When the new client instance is created, the invoker is null until client.connect() is called, so something like this can happen: 1.- T1 (Thread 1) executes getClient(invocation); and returns client#1 2.- T2 (Thread 2) selects a new target for the invocation and calls init(InvokerLocator locator) 3.- T2 calls createClient() and the instance variable client becomes client#2 4.- T1 now calls clientInstance.getInvoker().getLocator() which is now client#2 but connect() has not been called on this instance, so results on NPE. The simplest of all solutions would be to make assignment of client instance thread safe, something I already did for JBAS-4815 to get around another thread safety issue. I'm gonna take the tests I created for JBAS-4815 and use them to replicate something like this and check whether the fix for that fixes this as well. -- 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

15 years, 4 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1511) Renaissance theme should use em instead of px CSS units anywhere possible and avoid defining absolute font size.

by Chris Laprun (JIRA)

Renaissance theme should use em instead of px CSS units anywhere possible and avoid defining absolute font size. ---------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1511 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1511 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Julien Viet Priority: Minor Fix For: 2.6.1 Final -- 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

15 years, 4 months

5
11
0 / 0

[JBoss JIRA] Created: (EJBTHREE-794) NotSerializableException from LdapLoginModule/AD

by Darren Hartford (JIRA)

NotSerializableException from LdapLoginModule/AD ------------------------------------------------ Key: EJBTHREE-794 URL: http://jira.jboss.com/jira/browse/EJBTHREE-794 Project: EJB 3.0 Issue Type: Bug Environment: jboss 4.0.5.GA/JEMS install, Win2000, ActiveDirectory Reporter: Darren Hartford "java.io.NotSerializableException: com.sun.jndi.ldap.LdapCtx" When incorrect credentials are passed from the client, the server swallows with NotSerializableException and the client does not get correct feedback. Test environment was login-config.xml with org.jboss.security.auth.spi.LdapLoginModule talking to an ActiveDirectory server. Note that when correct credentials are passed, everything works fine. -- 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

15 years, 4 months

4
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1131) Add configuration for Remoting servlet transport

by Ron Sigal (JIRA)

Add configuration for Remoting servlet transport ------------------------------------------------ Key: JBMESSAGING-1131 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131 Project: JBoss Messaging Issue Type: Task Reporter: Ron Sigal Assigned To: Tim Fox Fix For: 2.0.0 Alpha In addition to the "http" transport, Remoting also has the http-based "servlet" transport. The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side. In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads. But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used. In principle, it's the appropriate transport to use when the server is running inside JBossAS. In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet. However, there have been a couple of problems. For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker"). However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. -- 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

15 years, 4 months

8
46
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-266) Provide a mechanism to handle contexts in error

by Ales Justin (JIRA)

Provide a mechanism to handle contexts in error ----------------------------------------------- Key: JBMICROCONT-266 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-266 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Create a mechanism to manage the failing beans/contexts without having to re-install them. -- 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

15 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-265) Concurrent deployments

by Ales Justin (JIRA)

Concurrent deployments ---------------------- Key: JBMICROCONT-265 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-265 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Allow for deployments to be processed in parallel. Enabling this would be set by new Controller Mode - asynchronous. It would still be largely "self-optimizing", depending on the user to worry about possible issues that might result from concurrent usage of resources. -- 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

15 years, 4 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2008