November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2071) Investigate non-isolation of WSRP tests

by Chris Laprun (JIRA)

Investigate non-isolation of WSRP tests --------------------------------------- Key: JBPORTAL-2071 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2071 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 Alpha1 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.7.0 Beta1 It seems that test set up is not done in complete isolation of the environment. I have lost a day trying to figure out what changed in my code that was causing tests to fail with an NPE related to a null registration policy when it seems that the issue came from the database state of the AS instance... :( Need to find exactly what is causing the problem (seems like RegistrationManager might be the culprit) and use a properly isolated test set up. -- 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

14 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4753) ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.

by Vicky Kak (JIRA)

ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method. ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4753 URL: http://jira.jboss.com/jira/browse/JBAS-4753 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Vicky Kak Fix For: JBossAS-5.0.0.Beta3 In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries . When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception >>java.lang.IllegalArgumentException: repeated interface: -- 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

14 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-983) @EJB injection fails, RuntimeException, IllegalArgumentException

by dpocock (JIRA)

@EJB injection fails, RuntimeException, IllegalArgumentException ---------------------------------------------------------------- Key: EJBTHREE-983 URL: http://jira.jboss.com/jira/browse/EJBTHREE-983 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Environment: Debian Linux, Sun Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Reporter: dpocock Similar to bug EJBTHREE-862. However, setting `Isolated' to false in $JBOSS_HOME/server/XXX/deploy/ear-deployer.xml does not resolve the issue for me. Here is the scenario: There are two applications, app1.ear and app2.ear. app1.ear contains a stateless session bean, App1Bean, with local and remote interface app2.ear contains a stateless session bean, App2Bean, which has a field defined like so: @EJB(mappedName="app1/App1Bean/local") // I've tried local and remote com.app1.ejb.session.App1 app1; app1.ear and app2.ear are loaded successfully by the application server. When App2Bean is activated, JBoss tries to perform the injections. At this point, the RuntimeException (see stack below) occurs. App2Bean can successfully obtain a reference to app1 bean using the traditional JNDI lookup methods. This is a workaround. When inspecting the stack, notice the presence of IllegalArgumentException, even though the interface matches. 16:22:12,155 ERROR [STDERR] java.lang.RuntimeException: Non matching type for inject of field: App1Bean app1 for type: $Proxy79 of jndiName env/App2Bean/app2 intfs: , App1, org.jboss.ejb3.JBossProxy, javax.ejb.EJBObject 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:135) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:104) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:61) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:92) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.ThreadlocalPool.get(ThreadlocalPool.java:48) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.cache.simple.SimpleStatefulCache.create(SimpleStatefulCache.java:209) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:303) 16:22:12,165 ERROR [STDERR] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) 16:22:12,165 ERROR [STDERR] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) 16:22:12,185 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException 16:22:12,185 ERROR [STDERR] at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) 16:22:12,185 ERROR [STDERR] at java.lang.reflect.Field.set(Field.java:656) 16:22:12,185 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:119) 16:22:12,185 ERROR [STDERR] ... 13 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

14 years, 3 months

5
5
0 / 0

[JBoss JIRA] Created: (JBAS-4435) WebAppClassLoader.getResource() fails when the war is deployed as part of an ear

by Thomas Diesler (JIRA)

WebAppClassLoader.getResource() fails when the war is deployed as part of an ear -------------------------------------------------------------------------------- Key: JBAS-4435 URL: http://jira.jboss.com/jira/browse/JBAS-4435 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Reporter: Thomas Diesler Assigned To: Scott M Stark For some reason WebAppClassLoader.getResource("WEB-INF/wsdl/TestEndpoint.wsdl") fails when the war is deployed as part of an ear deployment. I use this workaround in static class VirtualFileClassLoader extends ClassLoader { private UnifiedVirtualFile vFile; public VirtualFileClassLoader(UnifiedVirtualFile file, ClassLoader parent) { super(parent); vFile = file; } @Override public URL getResource(String name) { URL url = super.getResource(name); if (url == null) { try { url = vFile.findChild(name).toURL(); } catch (IOException e) { // ignore } } return url; } } -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3970) NPE in JBossTestCase

by Thomas Diesler (JIRA)

NPE in JBossTestCase -------------------- Key: JBAS-3970 URL: http://jira.jboss.com/jira/browse/JBAS-3970 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Thomas Diesler Assigned To: Scott M Stark getServerHost() throws a NPE, because the delegate is not initialized before setUp() is called public class SimpleJSETestCase extends JBossTestCase { private String WSDL_LOCATION = "http://" + getServerHost() + ":8080/ws4ee-simple?wsdl"; private String NAMESPACE = "http://test.jboss.org/ws4eesimple"; private QName SERVICE_NAME = new QName(NAMESPACE, "HelloService"); .... } This is quite common in the webservice test suite -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-859) Message: add LOOPBACK flag

by Bela Ban (JIRA)

Message: add LOOPBACK flag -------------------------- Key: JGRP-859 URL: https://jira.jboss.org/jira/browse/JGRP-859 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When LOOPBACK is set in a message, the UNICAST.loopback and TP.loopback flags are overridden and a message is looped back up the stack, regardless of the value of the property. This is useful for example for VIEW and SUSPECT messages, where a socket could be disconnected (e.g. cable plugged) and we still need to be able to receive our own messages. -- 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

14 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-5599) Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API

by Andrig Miller (JIRA)

Eliminate build time configuration directories and replace with tool for generating configuration through the profile service API --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-5599 URL: http://jira.jboss.com/jira/browse/JBAS-5599 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System, Getting Started Guide, Installation Guide, Installer, Management services, ProfileService, Server Configuration Guide, Test Suite Reporter: Andrig Miller Assigned To: Paul Gier Fix For: No Release With the addition of the profile service, it seems silly to generate various configurations, like "all", "default" and "minimal" through the build. Instead we should have a tool that generates the configuration through the profile service, with the understanding of the dependencies of the various features. The tool could still have the concepts of "all", "default" and "minimal" embedded in it to make the transition easier, but most times to do the testing that we need to do we customize the configuration. We also add an additional configuration in productizing the EAP, and this would simplify that process as well. This tool would have to be usable at the command-line, in JBoss Tools, and from the installer. -- 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

14 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JASSIST-48) Create a common interface to MethodCall & NewExpr

by Guy Korland (JIRA)

Create a common interface to MethodCall & NewExpr ------------------------------------------------- Key: JASSIST-48 URL: http://jira.jboss.com/jira/browse/JASSIST-48 Project: Javassist Issue Type: Feature Request Reporter: Guy Korland Assigned To: Shigeru Chiba MethodCall & NewExpr both have common methods that are not part of the javassist.expr.Expr interface. public String getClassName() public String getSignature() suggested API: abstract public class Invoke extends Expr{ abstract public String getClassName(); abstract public String getSignature(); } public class MethodCall extends Invoke public class NewExpr extends 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1861) Ruleflow diagram not proprly displayed

by Jaroslaw Kijanowski (JIRA)

Ruleflow diagram not proprly displayed -------------------------------------- Key: JBRULES-1861 URL: https://jira.jboss.org/jira/browse/JBRULES-1861 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.0.0.M3 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Attachments: expected.png, rf.png -- 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

14 years, 4 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-913) java.lang.IllegalStateException in SessionContext::getCallerPrincipal()

by Mihail Druzinin (JIRA)

java.lang.IllegalStateException in SessionContext::getCallerPrincipal() ----------------------------------------------------------------------- Key: EJBTHREE-913 URL: http://jira.jboss.com/jira/browse/EJBTHREE-913 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Environment: AS: jboss-4.0.5 (ejb3 Version EJB 3.0 RC7 - FD and EJB3 RC9 Patch 1) OS: Windows, GentooLinux Reporter: Mihail Druzinin >From HttpServlet I execute methods from stateless been. All methods executed correctly with authorization. When in method I try sessionContext.getCallerPrincipal(), then throws java.lang.IllegalStateException: No valid security context for the caller identity After see in jboss security module I find that in org.jboss.security.SecurityAssociation getCallerPrincipal() when used RunAsIdentity, it getted not from top of RunAsIdentity stack, but "for the active run-as the previous caller has assumed": Principal thePrincipal = peekRunAsIdentity(1); (SecurityAssociation.java:216). After fixed that string to: Principal thePrincipal = peekRunAsIdentity(0), all start work. -- 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

14 years, 4 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008