July 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7096) SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup

by Richard Taylor (JIRA)

SLSB with dependency on HASingletonDeployer / Barrier results in error message on second node on startup -------------------------------------------------------------------------------------------------------- Key: JBAS-7096 URL: https://jira.jboss.org/jira/browse/JBAS-7096 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.GA Environment: RHEL 4 Update 7 (and OSX 10.5.7), Sun JRE 1.6.0_12, JBoss 5.1.0 - "all" configuration Reporter: Richard Taylor Assignee: Brian Stansberry Priority: Minor Basic cluster, two JBoss 5.1.0 nodes, "all" configuration. First node starts fine. Second node starts, however at the end of starting, any SLSBs that depend on the barrier result in an error being logged at startup (on the second node). Example: DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3" is missing the following dependencies: Dependency "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" (should be in state "Described", bu t is actually in state "** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **") DEPLOYMENTS IN ERROR: Deployment "<UNKNOWN jboss.j2ee:ear=app-ear.ear,jar=app-ejb.jar,name=BoardPollerMDB,service=EJB3>" is in error due to the following reas on(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' ** The SLSBs on node 2 do properly start in a failover scenario when node 1 goes down. So functionally things seem OK. However the error message is a little concerning and it leaves us wondering if there is more to the problem. -- 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

15 years, 10 months

3
7
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

15 years, 10 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

15 years, 10 months

5
5
0 / 0

[JBoss JIRA] Created: (JBAS-6627) The JMX console /MBean Inspector page doesn't handle org.w3c.dom.Element correctly

by Howard Gao (JIRA)

The JMX console /MBean Inspector page doesn't handle org.w3c.dom.Element correctly ---------------------------------------------------------------------------------- Key: JBAS-6627 URL: https://jira.jboss.org/jira/browse/JBAS-6627 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-4.2.3.GA Reporter: Howard Gao Assignee: Darran Lofthouse When a mbean is opened in the MBeanInspector page, if the mbean has attributes that are of type org.w3c.dom.Element, the corresponding input field cannot display them correctly if the element's value contains special characters like ' (quote). Special characters in this case should be converted to html code in order to be displayed properly on the web browser. See related jira https://jira.jboss.org/jira/browse/JBMESSAGING-1517. -- 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

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-526) Add "all" profile to generate and include javadocs in AS build

by Paul Gier (JIRA)

Add "all" profile to generate and include javadocs in AS build -------------------------------------------------------------- Key: JBBUILD-526 URL: https://jira.jboss.org/jira/browse/JBBUILD-526 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build - App Server (Phase 3) The AS build does not currently have the equivalent of the "all" target in the old ant build. This basically involves setting up a profile to call the javadoc plugin, and then updating build-distr.xml to copy the generated javadocs. -- 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

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7068) Wrong timeout-valiue in OracleValidConnectionChecker

by Christian Daszenies (JIRA)

Wrong timeout-valiue in OracleValidConnectionChecker ---------------------------------------------------- Key: JBAS-7068 URL: https://jira.jboss.org/jira/browse/JBAS-7068 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.1.0.GA Reporter: Christian Daszenies Assignee: Jesper Pedersen OracleValidConnectionChecker calls oracle.jdbc.driver.OracleConnection.pingDatabase(5000) - 5000 is used as timeout in seconds! by pingDatabase furthermore it would be nice if the timeout would be configurable (or at least easy to override) -- 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

15 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-6871) don't create delegate operations for stopped components

by Emanuel Muckenhuber (JIRA)

don't create delegate operations for stopped components ------------------------------------------------------- Key: JBAS-6871 URL: https://jira.jboss.org/jira/browse/JBAS-6871 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Affects Versions: JBossAS-5.1.0.CR1 Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: JBossAS-5.1.0.GA We should not create delegate operations and properties for stopped components. -- 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

15 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6817) Add isNullable attribute to ManagedOperation

by Charles Crouch (JIRA)

Add isNullable attribute to ManagedOperation -------------------------------------------- Key: JBAS-6817 URL: https://jira.jboss.org/jira/browse/JBAS-6817 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: ProfileService Reporter: Charles Crouch -- 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

15 years, 11 months

4
7
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

15 years, 11 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

15 years, 11 months

2
1
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 2009