[JBoss JIRA] Reopened: (JBAS-8906) Service in START_FAILED state does not transition when mode is changed to REMOVE
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBAS-8906?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reopened JBAS-8906:
------------------------------------
Assignee: Brian Stansberry
Reopening as a JBAS bug; cause is illegal behavior shown at http://fpaste.org/vcII/
> Service in START_FAILED state does not transition when mode is changed to REMOVE
> --------------------------------------------------------------------------------
>
> Key: JBAS-8906
> URL: https://issues.jboss.org/browse/JBAS-8906
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: David Lloyd
> Assignee: Brian Stansberry
> Attachments: forceNPE.patch, w2.war
>
>
> Here's an example service dump:
> ^C13:22:49,405 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Stopping Coyote HTTP/1.1 on http-8080
> 13:22:49,425 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 13:22:49,431 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped
> ^C
> 13:27:25,270 INFO [stdout] Services for jboss-as:
> 13:27:25,276 INFO [stdout] Service "jboss.as" (class org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED)
> 13:27:25,276 INFO [stdout] Service "jboss.as.external-module-service" (class org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,279 INFO [stdout] Service "jboss.as.server-controller" (class org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) (dependencies: jboss.as.external-module-service, jboss.as.service-module-loader, jboss.deployment-repository)
> 13:27:25,279 INFO [stdout] Service "jboss.as.service-module-loader" (class org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,280 INFO [stdout] Service "jboss.deployment.chains" (class org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller)
> 13:27:25,280 INFO [stdout] Service "jboss.deployment.unit."test3.jar"" (class org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies: jboss.deployment.chains, jboss.deployment-repository)
> 13:27:25,282 INFO [stdout] Service "jboss.deployment.unit."test3.jar".CONFIGURE_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".DEPENDENCIES) (dependencies: jboss.deployment.chains, jboss.deployment.unit."test3.jar".DEPENDENCIES)
> 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".DEPENDENCIES" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".PARSE) (dependencies: jboss.deployment.unit."test3.jar".PARSE, jboss.deployment.chains)
> 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".INSTALL" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state START_FAILED (parent: jboss.deployment.unit."test3.jar".POST_MODULE) (dependencies: jboss.deployment.unit."test3.jar".POST_MODULE, jboss.deployment.chains) (has failed dependency)
> 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".PARSE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".STRUCTURE) (dependencies: jboss.deployment.unit."test3.jar".STRUCTURE, jboss.deployment.chains)
> 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".POST_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: module.service."deployment.test3.jar".main, jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.chains)
> 13:27:25,285 INFO [stdout] Service "jboss.deployment.unit."test3.jar".STRUCTURE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar") (dependencies: jboss.deployment.chains)
> 13:27:25,285 INFO [stdout] Service "jboss.deployment-repository" (class org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,285 INFO [stdout] Service "module.service."deployment.test3.jar".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.as.service-module-loader, module.spec.service."deployment.test3.jar".main)
> 13:27:25,286 INFO [stdout] Service "module.spec.service."deployment.test3.jar".main" (class org.jboss.msc.service.ValueService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.unit."test3.jar")
> 13:27:25,286 INFO [stdout] 15 services displayed
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Moved: (JBAS-8906) Service in START_FAILED state does not transition when mode is changed to REMOVE
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/JBAS-8906?page=com.atlassian.jira.plugin.... ]
Brian Stansberry moved MSC-67 to JBAS-8906:
-------------------------------------------
Project: JBoss Application Server (was: Modular Service Container)
Key: JBAS-8906 (was: MSC-67)
Affects Version/s: (was: 1.0.0.Beta6)
Security: Public
> Service in START_FAILED state does not transition when mode is changed to REMOVE
> --------------------------------------------------------------------------------
>
> Key: JBAS-8906
> URL: https://issues.jboss.org/browse/JBAS-8906
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: David Lloyd
> Attachments: forceNPE.patch, w2.war
>
>
> Here's an example service dump:
> ^C13:22:49,405 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Stopping Coyote HTTP/1.1 on http-8080
> 13:22:49,425 INFO [org.jboss.as.logging] Restored bootstrap log handlers
> 13:22:49,431 INFO [org.hornetq.core.server.impl.HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) stopped
> ^C
> 13:27:25,270 INFO [stdout] Services for jboss-as:
> 13:27:25,276 INFO [stdout] Service "jboss.as" (class org.jboss.as.server.ApplicationServerService) mode REMOVE state UP (STOP_REQUESTED)
> 13:27:25,276 INFO [stdout] Service "jboss.as.external-module-service" (class org.jboss.as.server.moduleservice.ExternalModuleService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,279 INFO [stdout] Service "jboss.as.server-controller" (class org.jboss.as.server.ServerControllerService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as) (dependencies: jboss.as.external-module-service, jboss.as.service-module-loader, jboss.deployment-repository)
> 13:27:25,279 INFO [stdout] Service "jboss.as.service-module-loader" (class org.jboss.as.server.moduleservice.ServiceModuleLoader) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,280 INFO [stdout] Service "jboss.deployment.chains" (class org.jboss.as.server.deployment.DeployerChainsService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller)
> 13:27:25,280 INFO [stdout] Service "jboss.deployment.unit."test3.jar"" (class org.jboss.as.server.deployment.RootDeploymentUnitService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as.server-controller) (dependencies: jboss.deployment.chains, jboss.deployment-repository)
> 13:27:25,282 INFO [stdout] Service "jboss.deployment.unit."test3.jar".CONFIGURE_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".DEPENDENCIES) (dependencies: jboss.deployment.chains, jboss.deployment.unit."test3.jar".DEPENDENCIES)
> 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".DEPENDENCIES" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".PARSE) (dependencies: jboss.deployment.unit."test3.jar".PARSE, jboss.deployment.chains)
> 13:27:25,283 INFO [stdout] Service "jboss.deployment.unit."test3.jar".INSTALL" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state START_FAILED (parent: jboss.deployment.unit."test3.jar".POST_MODULE) (dependencies: jboss.deployment.unit."test3.jar".POST_MODULE, jboss.deployment.chains) (has failed dependency)
> 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".PARSE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".STRUCTURE) (dependencies: jboss.deployment.unit."test3.jar".STRUCTURE, jboss.deployment.chains)
> 13:27:25,284 INFO [stdout] Service "jboss.deployment.unit."test3.jar".POST_MODULE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: module.service."deployment.test3.jar".main, jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.chains)
> 13:27:25,285 INFO [stdout] Service "jboss.deployment.unit."test3.jar".STRUCTURE" (class org.jboss.as.server.deployment.DeploymentUnitPhaseService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar") (dependencies: jboss.deployment.chains)
> 13:27:25,285 INFO [stdout] Service "jboss.deployment-repository" (class org.jboss.as.server.deployment.impl.ServerDeploymentRepositoryImpl) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.as)
> 13:27:25,285 INFO [stdout] Service "module.service."deployment.test3.jar".main" (class org.jboss.as.server.moduleservice.ModuleLoadService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.as.service-module-loader, module.spec.service."deployment.test3.jar".main)
> 13:27:25,286 INFO [stdout] Service "module.spec.service."deployment.test3.jar".main" (class org.jboss.msc.service.ValueService) mode REMOVE state UP (STOP_REQUESTED) (parent: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE) (dependencies: jboss.deployment.unit."test3.jar".CONFIGURE_MODULE, jboss.deployment.unit."test3.jar")
> 13:27:25,286 INFO [stdout] 15 services displayed
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBRULES-2895) Strip all author tags from java files
by Geoffrey De Smet (JIRA)
Strip all author tags from java files
-------------------------------------
Key: JBRULES-2895
URL: https://issues.jboss.org/browse/JBRULES-2895
Project: Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Asked by Mark. Took me a while to accept it, but it's true that we need to do it.
The author tags in the java files are a maintenance nightmare:
- A large percentage is wrong, incomplete or inaccurate.
- Most of the time, it only contains the original author. Many files are completely refactored/expanded by other authors.
- Git is accurate, that is the canonical source to find the correct author.
- To find the correct author of a piece of code, you always have to double check with git, you cannot suppose the author on the author tag alone.
- Author tags promote "code ownership", which is bad in the long run.
- If people work on a piece they perceive as being owned by someone else, they tend to:
-- only fix what they are assigned to fix, not everything that's broken.
-- discard responsibility if that code doesn't work properly.
-- be scared of stepping of the feet of the owner
-- Instead of "code ownership", we need "module leadership" and "peer reviews".
- More info: How to get a healthy open source project? http://video.google.com/videoplay?docid=-4216011961522818645#
Credit to the author of peices of code is given:
- on the team page: http://www.jboss.org/drools/team
-- Please contact Geoffrey (or any of us) if you want to change/expand your entry in the team page. Don't be shy!
- on the blog: http://blog.athico.com
-- Just ask write permission if you don't have them and want to write an article.
- with ohloh: https://www.ohloh.net/p/jboss-drools/contributors
- in the github web interface
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 3 months
[JBoss JIRA] Created: (JBAS-8891) Parse issue with namespaces in web.xml
by Alessio Soldano (JIRA)
Parse issue with namespaces in web.xml
--------------------------------------
Key: JBAS-8891
URL: https://issues.jboss.org/browse/JBAS-8891
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Alessio Soldano
Assignee: Remy Maucherat
Fix For: 7.0.0.Alpha2
When parsing the following web.xml (that used to work on AS 6)
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
<display-name>ServletTestClient</display-name>
<servlet>
<servlet-name>ServletTestClient</servlet-name>
<servlet-class>org.jboss.test.ws.jaxws.jbws3140.ServletTestClient</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ServletTestClient</servlet-name>
<url-pattern>/ServletTest</url-pattern>
</servlet-mapping>
<session-config>
<session-timeout>60</session-timeout>
</session-config>
<service-ref>
<service-ref-name>service/mtomTest</service-ref-name>
<service-interface>org.jboss.test.ws.jaxws.jbws3140.EndpointService</service-interface>
<service-ref-type>org.jboss.test.ws.jaxws.jbws3140.MTOMTest</service-ref-type>
<wsdl-file>WEB-INF/wsdl/TestEndpoint.wsdl</wsdl-file>
<service-qname xmlns:servicens="http://TestEndpoint.org">servicens:TestEndpointService</service-qname>
<port-component-ref>
<service-endpoint-interface>org.jboss.test.ws.jaxws.jbws3140.MTOMTest</service-endpoint-interface>
<enable-mtom>true</enable-mtom>
<mtom-threshold>750</mtom-threshold>
<addressing>
<enabled>true</enabled>
<responses>ANONYMOUS</responses>
</addressing>
</port-component-ref>
</service-ref>
</web-app>
I get a parsing exception:
java.lang.IllegalArgumentException: Invalid QName: servicens:TestEndpointService
at org.jboss.metadata.parser.util.MetaDataElementParser.parseQName(MetaDataElementParser.java:320)
at org.jboss.metadata.parser.ee.ServiceReferenceMetaDataParser.parse(ServiceReferenceMetaDataParser.java:100)
at org.jboss.metadata.parser.ee.EnvironmentRefsGroupMetaDataParser.parse(EnvironmentRefsGroupMetaDataParser.java:81)
at org.jboss.metadata.parser.servlet.WebMetaDataParser.parse(WebMetaDataParser.java:150)
at org.jboss.as.web.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:66)
... 5 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBAS-8897) Web Filter's init() method executed before EJBs are deployed
by Jozef Hartinger (JIRA)
Web Filter's init() method executed before EJBs are deployed
------------------------------------------------------------
Key: JBAS-8897
URL: https://issues.jboss.org/browse/JBAS-8897
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB3
Affects Versions: 6.0.0.Final
Reporter: Jozef Hartinger
Assignee: Carlo de Wolf
Priority: Blocker
Having a singleton (or stateless session) bean
@Singleton
@Startup
@ApplicationScoped
public class Echo
{
public boolean ping()
{
return true;
}
}
and a web filter
@WebFilter(urlPatterns = "/*")
public class Filter implements javax.servlet.Filter
{
private static final Logger log = Logger.getLogger(Filter.class);
@Inject
private Echo echo;
@Override
public void init(FilterConfig filterConfig) throws ServletException
{
log.info("Init starting");
echo.ping();
log.info("Init done");
}
@Override
public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException
{
chain.doFilter(request, response);
}
@Override
public void destroy()
{
}
}
Deployment of the application fails with the following exception:
10:56:57,152 INFO [org.jboss.seam.rest.test.compat.ejb.deployment.Filter] Init starting
10:56:57,153 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/test]] Exception starting filter org.jboss.seam.rest.test.compat.ejb.deployment.Filter: org.jboss.weld.exceptions.CreationException: WELD-000079 Could not find the EJB in JNDI: class org.jboss.seam.rest.test.compat.ejb.deployment.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldProxy
at org.jboss.weld.bean.SessionBean.create(SessionBean.java:348) [:6.0.0.Final]
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:121) [:6.0.0.Final]
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:99) [:6.0.0.Final]
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:87) [:6.0.0.Final]
at org.jboss.seam.rest.test.compat.ejb.deployment.org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldClientProxy.ping(org$jboss$weld$bean-jboss$classloader:id="vfs:$$$home$jharting$jboss$RESTEasy-int-clean$jboss-6$0$0$Final$server$default$deploy$test$war"-SessionBean-Echo_$$_WeldClientProxy.java)
at org.jboss.seam.rest.test.compat.ejb.deployment.Filter.init(Filter.java:29) [:]
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:447) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3246) [:6.0.0.Final]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3843) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:294) [:6.0.0.Final]
at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:146) [:6.0.0.Final]
at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:477) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) [:6.0.0.Final]
at org.jboss.web.deployers.WebModule.start(WebModule.java:95) [:6.0.0.Final]
at sun.reflect.GeneratedMethodAccessor405.invoke(Unknown Source) [:1.6.0_23]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23]
at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23]
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.GA]
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.GA]
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.GA]
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.GA]
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) [:2.2.0.GA]
at $Proxy41.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:53) [:2.2.0.GA]
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:41) [:2.2.0.GA]
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:301) [:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.GA]
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.GA]
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.GA]
at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.Final]
at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:143) [:0.2.2]
at org.jboss.profileservice.plugins.deploy.actions.DeploymentStartAction.doPrepare(DeploymentStartAction.java:98) [:0.2.2]
at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:101) [:0.2.2]
at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.2.2]
at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.2.2]
at org.jboss.profileservice.plugins.deploy.AbstractDeployHandler.startDeployments(AbstractDeployHandler.java:168) [:0.2.2]
at org.jboss.profileservice.management.upload.remoting.DeployHandlerDelegate.startDeployments(DeployHandlerDelegate.java:74) [:6.0.0.Final]
at org.jboss.profileservice.management.upload.remoting.DeployHandler.invoke(DeployHandler.java:156) [:6.0.0.Final]
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:898) [:6.0.0.Final]
at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:791) [:6.0.0.Final]
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:744) [:6.0.0.Final]
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:548) [:6.0.0.Final]
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:234) [:6.0.0.Final]
Caused by: java.lang.RuntimeException: Error retreiving EJB from JNDI Echo (Singleton); BeanClass: class org.jboss.seam.rest.test.compat.ejb.deployment.Echo; Local Business Interfaces: [Business interface: class org.jboss.seam.rest.test.compat.ejb.deployment.Echo]
at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:69) [:6.0.0.Final]
at org.jboss.weld.bean.SessionBean.createReference(SessionBean.java:476) [:6.0.0.Final]
at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.<init>(EnterpriseBeanProxyMethodHandler.java:75) [:6.0.0.Final]
at org.jboss.weld.bean.SessionBean.create(SessionBean.java:331) [:6.0.0.Final]
... 56 more
Caused by: javax.naming.NameNotFoundException: no-interface not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) [:5.0.5.Final]
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) [:5.0.5.Final]
at org.jnp.server.NamingServer.getObject(NamingServer.java:785) [:5.0.5.Final]
at org.jnp.server.NamingServer.lookup(NamingServer.java:443) [:5.0.5.Final]
at org.jnp.server.NamingServer.lookup(NamingServer.java:399) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) [:5.0.5.Final]
at javax.naming.InitialContext.lookup(InitialContext.java:392) [:1.6.0_23]
at org.jboss.weld.integration.ejb.JBossSessionObjectReference.<init>(JBossSessionObjectReference.java:44) [:6.0.0.Final]
at org.jboss.weld.integration.ejb.JBossEjbServices.resolveEjb(JBossEjbServices.java:65) [:6.0.0.Final]
... 59 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months