Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
xplfxdrtkkuuhzufklc(a)technodom.kz
17 years, 11 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Unable to deliver message to the following recipients, because the message was forwarded more than the maximum allowed times. This could indicate a mail loop.
xa(a)technodom.kz
17 years, 11 months
[JBoss Portal] - Deploying JSF portlet
by rxm
Hi,
I am trying to get the HelloWorldJSFPortlet working. I followed the instructions for removing sun JSF implementation from the server mentioned in jboss wiki page. I am getting the following exception.
javax.faces.FacesException: RequestServletPath is null, cannot determine viewId of current page.
| 14:49:54,093 INFO [STDOUT] 14:49:54,093 ERROR [[Faces Servlet]] Servlet.service
| () for servlet Faces Servlet threw exception
| javax.faces.FacesException: RequestServletPath is null, cannot determine viewId
| of current page.
| at org.apache.myfaces.util.DebugUtils.assertError(DebugUtils.java:89)
| at org.apache.myfaces.lifecycle.RestoreViewExecutor.deriveViewId(Restore
| ViewExecutor.java:116)
| at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewE
| xecutor.java:57)
| at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl
| .java:95)
| at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java
| :70)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:139)
| at org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java:
| 77)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
| icationFilterChain.java:290)
On decompiling the classes in question, I found that this issue is thrown when the default view id is null or the request is not an instance of PortletRequest. On debugging this in my Portlet class , everything seems to be alright. It looks like I am missing something in binding the JSF to the portlet.
Please help me in resolving this issue.
Regards,
Raja
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165052#4165052
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165052
17 years, 11 months
[Installation, Configuration & DEPLOYMENT] - Re: problem deploying witha jar, class not found
by calgacus
I tried changing my web.xml file to look like this:
1 <?xml version="1.0" encoding="UTF-8"?>
2 <web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.su n.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
3 <display-name>BookStore</display-name>
4
5
6 <display-name>BookStore1</display-name>
7 <servlet-name>BookStore1</servlet-name>
8 <servlet-class>ca.BookStore.BookStoreServlet18</servlet-class>
9
10
11 <servlet-mapping>
12 <servlet-name>BookStore1</servlet-name>
13 <url-pattern>/listbooks.servlet</url-pattern>
14 </servlet-mapping>
15
16 </web-app>
~
But still no luck, now I get this message on deploy:
10:06:00,923 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.CR1 (build: SVNTag=JBoss_5_0_0_CR1 date=200806301254)] Started in 58s:957ms
10:06:20,110 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/usr/share/jboss/jboss-5.0.0.CR1/server/default/deploy/BookStore.war state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/usr/share/jboss/jboss-5.0.0.CR1/server/default/deploy/BookStore.war
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:343)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:303)
at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:141)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:275)
at org.jboss.deployment.JBossWebAppParsingDeployer.createMetaData(JBossWebAppParsingDeployer.java:87)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:236)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: context-priority-classloader not found as a child of jboss-web
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:198)
at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:128)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:329)
... 28 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: context-priority-classloader not found as a child of jboss-web
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:396)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 35 more
10:06:20,130 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS IN ERROR: Name -> Error
vfszip:/usr/share/jboss/jboss-5.0.0.CR1/server/default/deploy/BookStore.war -> org.jboss.xb.binding.JBossXBRuntimeException: context-priority-classloader not found as a child of jboss-web
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165051#4165051
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165051
17 years, 11 months
[EJB 3.0] - Re: Session bean lookup fails JBoss 5, worked in 4.0.5
by jaikiran
anonymous wrote : javax.naming.NameNotFoundException: ec20 not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at com.pearson.util.LookupUtil.lookupEJB(LookupUtil.java:59)
| at com.pearson.util.SWStartup.initApp(SWStartup.java:36)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
| at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
| at org.jboss.seam.Component.callComponentMethod(Component.java:2092)
| at org.jboss.seam.Component.callPostConstructMethod(Component.java:2039)
| at org.jboss.seam.intercept.JavaBeanInterceptor$1.proceed(JavaBeanInterceptor.java:126)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
| at org.jboss.seam.intercept.Interceptor.postConstruct(Interceptor.java:184)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:74)
| at org.jboss.seam.intercept.Interceptor.postConstruct(Interceptor.java:184)
| at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:74)
| at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
| at org.jboss.seam.intercept.RootInterceptor.invokeAndHandle(RootInterceptor.java:84)
| at org.jboss.seam.intercept.JavaBeanInterceptor.callPostConstruct(JavaBeanInterceptor.java:131)
| at org.jboss.seam.intercept.JavaBeanInterceptor.postConstruct(JavaBeanInterceptor.java:116)
| at org.jboss.seam.Component.instantiateJavaBean(Component.java:1325)
| at org.jboss.seam.Component.instantiate(Component.java:1271)
| at org.jboss.seam.Component.newInstance(Component.java:1970)
| at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
| at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
| at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95)
| at org.jboss.seam.init.Initialization.init(Initialization.java:596)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3862)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4356)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:346)
| at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:139)
| at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:431)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:112)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:90)
The lookup seems to be happening when the web application (WAR) is being deployed and probably before the EJB is deployed and bound to JNDI. Looks like a deployment ordering issue. Is this EJB and WAR part of an EAR? If yes, then the deployment order is determined by the order in which the "module" are mentioned in the application.xml. What does your application.xml look like? And do you have a jboss-app.xml?
While posting the logs or code or xml content, remember to wrap it in a code block using the Code button in the message editor window and please hit the Preview button to make sure your post is correctly formatted
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165045#4165045
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4165045
17 years, 11 months
