December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7517) Port JBAS-6449 to trunk

by Brian Stansberry (JIRA)

Port JBAS-6449 to trunk ----------------------- Key: JBAS-7517 URL: https://jira.jboss.org/jira/browse/JBAS-7517 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Security Reporter: Brian Stansberry Assignee: Anil Saldhana Fix For: JBossAS-6.0.0.M2 Comparison of org.jboss.jmx.connector.invoker.InvokerAdaptorService between trunk and 6.0.0.M1 shows the JBAS-6449 fix is missing in 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

15 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-7525) Sip injection in an EJB session bean is broken on jb5

by Roberto Vaquerizo (JIRA)

Sip injection in an EJB session bean is broken on jb5 ----------------------------------------------------- Key: JBAS-7525 URL: https://jira.jboss.org/jira/browse/JBAS-7525 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-5.1.0.GA Environment: JBOSS AS 5 + Mobicents 1.2.1 GA (with Sip Servlets 1.1) Reporter: Roberto Vaquerizo Assignee: Carlo de Wolf - EJB3 session bean sends out a SIP Register message - 200 OK comes from the network at the SIP Servlet. - Dependency Injection (@EJB) is not working on servlet. - JNDI works only if D.I. is not done on called EJB. - Even if JNDI is performed, the call into the EJB session bean fails with the trace: ------------------------------------------------------------------------------------------------ at org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:314) at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.dispatchAndHandleExceptions(DispatchTask.java:55) at org.mobicents.servlet.sip.core.dispatchers.DispatchTask.run(DispatchTask.java:50) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: Specified calling class, com.mycompany.TEST.action.SipAction could not be found for org.jboss.bootstrap.NoAnnotationURLClassLoader@471e30 at org.jboss.ejb3.common.lang.SerializableMethod.getClassFromName(SerializableMethod.java:311) at org.jboss.ejb3.common.lang.SerializableMethod.getClassType(SerializableMethod.java:282) at org.jboss.ejb3.common.lang.SerializableMethod.toMethod(SerializableMethod.java:233) at org.jboss.ejb3.common.lang.SerializableMethod.toMethod(SerializableMethod.java:220) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:182) at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) at $Proxy433.imsSuccessResponse(Unknown Source) at com.mycompany.TEST.servlet.TESTSipServlet.doSuccessResponse(TESTSipServlet.java:182) at javax.servlet.sip.SipServlet.doResponse(SipServlet.java:268) at com.mycompany.TEST.servlet.TESTSipServlet.doResponse(TESTSipServlet.java:158) at javax.servlet.sip.SipServlet.service(SipServlet.java:327) at org.mobicents.servlet.sip.core.dispatchers.MessageDispatcher.callServlet(MessageDispatcher.java:281) at org.mobicents.servlet.sip.core.dispatchers.ResponseDispatcher$1.dispatch(ResponseDispatcher.java:302) ... 5 more Caused by: java.lang.ClassNotFoundException: com.mycompany.TEST.action.SipAction at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.ejb3.common.classloader.PrimitiveAwareClassLoader.findClass(PrimitiveAwareClassLoader.java:105) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at org.jboss.ejb3.common.lang.SerializableMethod.getClassFromName(SerializableMethod.java:307) ... 17 more -- 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
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-581) poms related to xdoclet are broken at jboss's maven repo

by Prabhat Jha (JIRA)

poms related to xdoclet are broken at jboss's maven repo -------------------------------------------------------- Key: JBBUILD-581 URL: https://jira.jboss.org/jira/browse/JBBUILD-581 Project: JBoss Build System Issue Type: Bug Components: Maven Builds Reporter: Prabhat Jha Assignee: Paul Gier See the difference: http://repository.jboss.org/maven2/xdoclet/xdoclet-hibernate-module/1.2.3... http://repo2.maven.org/maven2/xdoclet/xdoclet-hibernate-module/1.2.3/xdoc... -- 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

2
3
0 / 0

[JBoss JIRA] Created: (JBJCA-235) Integrate Tattletale into QA environment

by Jesper Pedersen (JIRA)

Integrate Tattletale into QA environment ---------------------------------------- Key: JBJCA-235 URL: https://jira.jboss.org/jira/browse/JBJCA-235 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha7 Integrate Tattletale into the QA environment such any issues found can be fixed or filtered out. -- 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
1
0 / 0

[JBoss JIRA] Created: (JBJCA-234) Tattletale 1.1.0.Beta2

by Jesper Pedersen (JIRA)

Tattletale 1.1.0.Beta2 ---------------------- Key: JBJCA-234 URL: https://jira.jboss.org/jira/browse/JBJCA-234 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha7 -- 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
0
0 / 0

[JBoss JIRA] Created: (JBAS-7504) Upgrade JBoss AOP to 2.1.6.GA

by Brian Stansberry (JIRA)

Upgrade JBoss AOP to 2.1.6.GA ----------------------------- Key: JBAS-7504 URL: https://jira.jboss.org/jira/browse/JBAS-7504 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Kabir Khan Priority: Critical Fix For: JBossAS-6.0.0.M2 Need to move trunk to at least version used in 6.0.0.M1. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7513) Sync jboss-aop-asintegration-jmx handling with 6.0.0.M1

by Brian Stansberry (JIRA)

Sync jboss-aop-asintegration-jmx handling with 6.0.0.M1 ------------------------------------------------------- Key: JBAS-7513 URL: https://jira.jboss.org/jira/browse/JBAS-7513 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: AOP Reporter: Brian Stansberry Assignee: Kabir Khan Priority: Critical Fix For: JBossAS-6.0.0.M2 6.0.0.M1 does not use org.jboss.aop:jboss-aop-asintegration-jmx; trunk still does. So we need to clarify the expected configuration for M2. I came across this when attempting to port JBAS-7298 to trunk. Removing the jar from the build and from conf/bootstrap/aop.xml results in the server not starting properly: 12:26:11,337 ERROR [AbstractKernelController] Error installing to PreInstall: name=AspectManagerJMXRegistrar state=Not Installed: java.lang.ClassNotFoundException: org.jboss.aop.deployers.AspectManagerJMXRegistrar at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:315) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:292) at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1124) at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:805) at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:445) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:398) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.resolveComplexTypeInfo(IntrospectionTypeInfoFactoryImpl.java:419) at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getTypeInfo(IntrospectionTypeInfoFactoryImpl.java:388) at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory.getTypeInfo(IntrospectionTypeInfoFactory.java:54) at org.jboss.classadapter.plugins.BasicClassAdapterFactory.getClassAdapter(BasicClassAdapterFactory.java:61) at org.jboss.config.plugins.AbstractConfiguration.getBeanInfo(AbstractConfiguration.java:86) at org.jboss.kernel.plugins.config.AbstractKernelConfig.getBeanInfo(AbstractKernelConfig.java:80) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:77) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getBeanInfo(AbstractKernelConfigurator.java:96) at org.jboss.kernel.plugins.dependency.PreInstallAction.installActionInternal(PreInstallAction.java:90) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297) at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130) at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76) at org.jboss.bootstrap.impl.mc.deployer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:91) at org.jboss.bootstrap.impl.mc.deployer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:161) at org.jboss.bootstrap.impl.mc.server.AbstractMCServerBase.doStart(AbstractMCServerBase.java:299) at org.jboss.bootstrap.impl.as.server.JBossASServerImpl.doStart(JBossASServerImpl.java:359) at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:425) at java.lang.Thread.run(Thread.java:637) -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-1107) TCP: skip_suspected_members=true prevents merge

by Bela Ban (JIRA)

TCP: skip_suspected_members=true prevents merge ----------------------------------------------- Key: JGRP-1107 URL: https://jira.jboss.org/jira/browse/JGRP-1107 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.8 When we have A and B and both have TCP.skip_suspected_members set to true, then the following happens on a network partition: - A excludes B and adds B to suspected_members. Therefore A won't send any messages to B anymore - B does the same - A and B would remove the sender of a message from suspected_members, but nobody will actually send any messages ! - On a merge, A and B need to talk to each other, but both will discard the message ! ==> A merge will never happen WORKAROUND: set skip_suspected_members to false SOLUTION: before a merge, clear suspected_members (maybe handle MERGE event) -- 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: (JBBOOT-88) ProfileServiceBootstrap: Failed to build ManagedDeployment

by Ondrej Medek (JIRA)

ProfileServiceBootstrap: Failed to build ManagedDeployment ---------------------------------------------------------- Key: JBBOOT-88 URL: https://jira.jboss.org/jira/browse/JBBOOT-88 Project: JBoss Bootstrap Issue Type: Bug Environment: JBoss AS 5.1.0, WinXP, jdk 1.6.0u13 Reporter: Ondrej Medek Assignee: Andrew Lee Rubinger Attachments: boot.log I see two exception in my boot.log: DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: 1) AbstractKernelDeployment@1cd427a{name=file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/vfs.xml installed=true beanFactories=[AbstractBeanMetaData@c791f4{name=VFSCache bean=null properties=[realCache, permanentRoots] constructor=AbstractConstructorMetaData@198defc{parameters=[null] factoryClass=org.jboss.virtual.spi.cache.VFSCacheFactory factoryMethod=getInstance} autowireCandidate=true start=AbstractLifecycleMetaData@1579a30{ whenRequired=ControllerState@3f58bb{Start} parameters= }}, AbstractBeanMetaData@da9067{name=VfsNamesExceptionHandler bean=org.jboss.virtual.plugins.context.helpers.NamesExceptionHandler properties= constructor=AbstractConstructorMetaData(a)13e9934{parameters=[java.lang.String]} autowireCandidate=true}]} org.jboss.deployers.spi.DeploymentException: Error deploying: file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/vfs.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) 2) AbstractKernelDeployment@17044c5{name=file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@1b2e44d{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]} org.jboss.deployers.spi.DeploymentException: Error deploying: file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) -- 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

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-7521) Fix the shutdown.jar assembly

by Andrew Lee Rubinger (JIRA)

Fix the shutdown.jar assembly ----------------------------- Key: JBAS-7521 URL: https://jira.jboss.org/jira/browse/JBAS-7521 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: JBossAS-6.0.0.M2 AS trunk shutdown.sh leads to: Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/Shutdown Caused by: java.lang.ClassNotFoundException: org.jboss.Shutdown at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) Could not find the main class: org.jboss.Shutdown. Program will exit. Fix the assembly to ensure all required classes are accounted for -- 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
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009