[Installation, Configuration & DEPLOYMENT] - Error deploying EJB with JBoss5.0.0.CR1 !
by Nouredine13
i have an error when i try to deploy an EJB that work fine with JBoss5 Beta4.
i have a java.lang.NullPointerException when i try to deploy this EJB :
ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/product/jboss/jboss-5.0.0.CR1/server/default/deploy/mminfra-CR1.ear state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying OTAinfra-ejb.jar: null
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:192)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:95)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
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.doInstallParentFirst(DeployersImpl.java:1023)
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: java.lang.NullPointerException
at org.jboss.ejb3.javaee.JavaEEComponentHelper.createObjectName(JavaEEComponentHelper.java:46)
at org.jboss.ejb3.deployers.JBoss5DeploymentScope.getEjbContainer(JBoss5DeploymentScope.java:167)
at org.jboss.ejb3.Ejb3Deployment.getEjbContainer(Ejb3Deployment.java:384)
at org.jboss.ejb3.EJBContainer.resolveEjbContainer(EJBContainer.java:1324)
at org.jboss.injection.AbstractHandler.addDependency(AbstractHandler.java:50)
at org.jboss.injection.EJBRemoteHandler.ejbRefDependency(EJBRemoteHandler.java:143)
at org.jboss.injection.EJBRemoteHandler.handleFieldAnnotations(EJBRemoteHandler.java:371)
at org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:162)
at org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:199)
at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:563)
at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:392)
at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:505)
at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:185)
... 27 more
some one have any solution?
thank's a lot
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170030#4170030
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170030
17 years, 11 months
[Security & JAAS/JBoss] - org.jboss.security.auth.login.ParseException
by elywagner
Hello everyone
I am trying to migrate my application from JBoss 4.0.3SP1 to the latest stable release JBoss 4.2.3.GA, but a very weird error is happening. During server startup, the following error message is shown:
2008-08-12 09:53:53,877 WARN [org.jboss.system.ServiceController] Problem starting service abc:service=LoginModule
| org.jboss.security.auth.login.ParseException: Encountered "<?xml" at line 1, column 1.
| Was expecting one of:
| <EOF>
| <IDENTIFIER> ...
| at org.jboss.security.auth.login.SunConfigParser.generateParseException(SunConfigParser.java:395)
| at org.jboss.security.auth.login.SunConfigParser.jj_consume_token(SunConfigParser.java:333)
| ...
|
I am sure the cause of this error has nothing to do with XML syntax, since I have been able to deploy my SAR to the old JBoss. I have found some other people facing the same problem with much older versions, and they suggest the removal of special characters from the XML files, but that is not my case. I have recreated all my XML files by using very simple editors such as VI, and copied the content from the JBoss documentation.
This is my META-INF/login-config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE policy PUBLIC
| "-//JBoss//DTD JBOSS Security Config 3.0//EN"
| "http://www.jboss.org/j2ee/dtd/security_config.dtd">
| <policy>
| <application-policy name = "abc">
| <authentication>
| <login-module code = "com.abc.LoginModule" flag = "required">
| <module-option name="password-stacking">no</module-option>
| </login-module>
| </authentication>
| </application-policy>
| </policy>
This is my jboss-service.xml:
<?xml version="1.0" encoding="UTF-8"?>
| <server>
|
| <mbean code="org.jboss.security.auth.login.DynamicLoginConfig" name="abc:service=LoginModule">
|
| <attribute name="AuthConfig">META-INF/login-config.xml</attribute>
|
| <depends optional-attribute-name="LoginConfigService">
| jboss.security:service=XMLLoginConfig
| </depends>
|
| <depends optional-attribute-name="SecurityManagerService">
| jboss.security:service=JaasSecurityManager
| </depends>
|
| <depends>
| jboss.j2ee:module=abc-ejb.jar,service=EjbModule
| </depends>
| </mbean>
|
| </server>
Does anyone know what is causing this error?
Thanks a lot
Ely
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170024#4170024
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170024
17 years, 11 months
[JNDI/Naming/Network] - Re: NameNotBoundException in MDB, but bound in WAR Servlet
by jaikiran
anonymous wrote : In a WAR, I am loading a servlet during application startup to bootstrap some configuration within an object then binding that object to the JNDI java:comp/env namespace.
|
| When I look in the jmx-console, I see that the object is available under the following heading:
|
| java:comp namespace of the my-ear.ear/my-war.war application.
When you add the object to the java:comp/env namespace of the WAR, it becomes available to your WAR component. Each component in your application have their own java:comp/env namespace (environment naming context - ENC). When you try to lookup this object from the MDB (which has a different ENC), the MDB will not be able to find this since it looks in its own ENC. To make the object available in the ENC of the MDB, you will have to add a resource-ref in the ejb-jar.xml of this bean, to point to the object that you have bound in the jndi tree.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170022#4170022
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170022
17 years, 11 months
Automatically rejected mail
by Mail Delivery Subsystem
Your message was automatically rejected by Dovecot Mail Delivery Agent.
The following reason was given:
Quota exceeded
17 years, 11 months
[Installation, Configuration & DEPLOYMENT] - Re: 4.2.2 MBean getClientHost java.rmi.server.ServerNotActiv
by guy_rouillier
Ok, following the post that I reference, I was able to implement a client interceptor to capture the client's IP address and add it to the invocation object using setValue(). Then I was able to create a server interceptor, modeled after the LogInterceptor (i.e., extends from AbstractInterceptor), which can retrieve the IP address from the invocation object using getValue(). So far, so good.
Now, how does that help me? I need to get that value into something that the EJB business method can access, which then needs to pass it on to a corresponding MBean method, again in some transparent fashion. That is, I don't want to modify the 60 business methods in the stateless session EJB or the corresponding 60 business methods in the MBean. Ideally, the MBean could get hold of the invocation object, but I don't know if that is possible.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170018#4170018
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170018
17 years, 11 months
[JBoss Portal] - Portlets on differents wars to same page
by samppaa
Hello,
I'm trying to get two portlets on different wars to be installed on same page in JBP when I deploy them but with no luck.
I'm using JBP 2.6.5-SP1 and JBAS 4.2.2.
I have A.war that has PortletA in it with following portal-object.xml
| <deployments>
| <deployment>
| <parent-ref>default</parent-ref>
| <if-exists>keep</if-exists>
| <page>
| <page-name>Test</page-name>
| <window>
| <window-name>testa</window-name>
| <instance-ref>PortletAInstance</instance-ref>
| <region>left</region>
| <height>1</height>
| </window>
| </page>
| </deployment>
| </deployments>
|
And B.war with that has portletB and following portal-object.xml
| <deployments>
| <deployment>
| <parent-ref>default</parent-ref>
| <if-exists>keep</if-exists>
| <page>
| <page-name>Test</page-name>
| <window>
| <window-name>testb</window-name>
| <instance-ref>PortletBInstance</instance-ref>
| <region>left</region>
| <height>1</height>
| </window>
| </page>
| </deployment>
| </deployments>
|
Both wars are deployed correctly and portlet instances are created but on the "Test" page only one of the portlets is shown. Am I doing something wrong or is this something that cannot be done automatically? (I can get the portlets on the same page using admin console)
Thanks in advance,
Samppa
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170016#4170016
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170016
17 years, 11 months
