[Installation, Configuration & DEPLOYMENT] - error deployment jboss
by guilhermefreitas76
Hello!!!
I'm using jpa with JOTM and jboss 4.2.2GA. In the first deploy the application functions normally. When I make a change and I deploy the new, giving the error below. If I restart the server, operating normally. What can be?
thank you. Guilherme Freitas.
org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameNotFoundException: comp)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:384)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: javax.naming.NameNotFoundException: comp
at org.objectweb.carol.jndi.enc.java.CompNamingContext.lookup(CompNamingContext.java:140)
at org.objectweb.carol.jndi.enc.java.JavaURLContext.lookup(JavaURLContext.java:138)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:475)
at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:878)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:159)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
... 67 more
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162671#4162671
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162671
17 years, 9 months
[JBoss Portal] - Configuration of portal window via XML
by stmod
Hello,
I need to configure the association between portlet and window via XML configuration files.
I am able to do this if I put just a portlet (it is an application) in a portal window. To do this I modify the xml configuration files of the war.
Now I need to put three different portlet (they are three different war files) in the same window.
I was not able to perform this task. I tried to modify the XML configuration files in the three war files but it does not work.
According to me, the configuration files should be outside the war(s) because they define which war(s) and where have to stay in a portal window. I was not able to find nothing addressing this problem.
Someone can help me?
Thanks in advance
Stefano
p.s.: jboss portal version is 2.6.1.GA
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162670#4162670
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162670
17 years, 9 months
[JBossWS] - Web service security, how to filter client IP address?
by cardel
I am using basic authentication (username, password) in my web services. So client have to authenticate to endpoint provider. But I would like to know, how to secure my web service endpoint servlet. I would like to allow connection only to clients with specified IP address.
my web.xml
| <!-- START WS authentication -->
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>All webservices</web-resource-name>
| <url-pattern>/ws/*</url-pattern>
| <http-method>POST</http-method>
| </web-resource-collection>
| <auth-constraint>
| <role-name>wsrole</role-name>
| </auth-constraint>
| <user-data-constraint>
| <transport-guarantee>NONE</transport-guarantee>
| </user-data-constraint>
| </security-constraint>
|
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>Security Realm</realm-name>
| </login-config>
|
| <security-role>
| <role-name>wsrole</role-name>
| </security-role>
| <!-- END WS authentication -->
|
| <servlet>
| <servlet-name>BareEndpoint</servlet-name>
| <servlet-class>hcp.service.BareEndpointBean</servlet-class>
| </servlet>
|
| <servlet-mapping>
| <servlet-name>BareEndpoint</servlet-name>
| <url-pattern>/ws/bareservice</url-pattern>
| </servlet-mapping>
|
I would like to use this kind of security to deny access to BareEndpoit servlet and only client(s) with specified IP can read wsdl from /ws/bareservice?wsdl address and call some endpoint actions.
Thank you for some useful tips.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162661#4162661
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162661
17 years, 9 months
[Clustering/JBoss] - Unknown Multiple Jboss Proccesses
by idweiss
Can it be that a JBoss instance will launch other JBoss instances? Can such a behavior be related to JBoss clustering?
We observed JBoss duplicate processes on our system running JBoss 4.2.0.GA on Sun T5220 machines with Solaris 10.
After we run JBoss for several hours we sometime see several JBoss processes running instead of only one, although we launch only one JBoss instance (we made sure by adding logging to the JBoss run.sh launch script). Also the new duplicate JBoss processes have the parent pid of the original JBoss process (the original JBoss process has a parent pid of it's run.sh process). The JBoss processes have the same parameters as the original JBoss process and take the same amount of memory.
Here's an example of running the ps -ef | grep run.sh command:
anauser 16082 1 0 12:45:50 ? 0:00 /bin/sh /export/home/ana41/jboss/bin/run.sh -b 0.0.0.0
anauser 16093 16082 2 12:45:50 ? 960:40 /export/home/ana41/java/bin/java -Dprogram.name=run.sh -server -Xms2048m -Xmx20
anauser 5623 16093 0 00:48:39 ? 0:00 /export/home/ana41/java/bin/java -Dprogram.name=run.sh -server -Xms2048m -Xmx20
anauser 5627 16093 0 00:48:43 ? 0:00 /export/home/ana41/java/bin/java -Dprogram.name=run.sh -server -Xms2048m -Xmx20
anauser 5590 16093 0 00:48:31 ? 0:00 /export/home/ana41/java/bin/java -Dprogram.name=run.sh -server -Xms2048m -Xmx20
We also see that the Total Running time of these duplicate processes are almost always 0. We saw only once a duplicate JBoss process with a running time of 2, and then that process disappeared. I have a theory that maybe these Processes are stuck because their output stream are not read or directed to anywhere. We still have no idea what launched these processes.
Will appreciate any advise.
Thanks,
Ido
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162658#4162658
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162658
17 years, 9 months