We Keep Coding

Jenkins Weblogic Server Deployment weblogic.management.home.localhome

Scenario:
I try to deploy web services to weblogic server by Jenkins + weblogic deployer.
I successfully get war files after build.
While deploying war files I get below error in console.
Additional descriptions:
This is enterprise environment. Jenkins and Weblogic server are running on different servers but connetions are ok. On weblogic server there 4 applications
my web services running on a cluster.
Question: What is the meaning of this error? How to fix it or at least where should I concentrate? :)
Reason: javax.naming.NameNotFoundException: While trying to lookup
'weblogic.management.home.localhome' didn't find subcontext 'home'.
Resolved 'weblogic.management' [Root exception is
javax.naming.NameNotFoundException: While trying to lookup
'weblogic.management.home.localhome' didn't find subcontext 'home'.
Resolved 'weblogic.management']; remaining name 'home/localhome'

You're getting a NameNotFoundException when trying to lookup a resource (weblogic.management.home.localhome) using JNDI. The exception says that part of the name is resolved (weblogic.management) but that it cannot resolve the remainder (home.localhome).
In the Javadoc for NameNotFoundException, you'll see:
This exception is thrown when a component of the name cannot be resolved because it is not bound.
That means that, either the subcontext information for the JNDI resourcs (home.localhome) is incorrect, or the subcontext (home.localhome) is not registered with the JNDI naming service.
See http://docs.oracle.com/javase/7/docs/api/javax/naming/NamingException.html (superclass of the NameNotFoundException) for the exception and review the JNDI info here for configuration help: http://docs.oracle.com/middleware/1221/wls/WLACH/core/index.html

JBAS011843: Failed instantiate InitialContextFactory com.ibm.websphere.naming.WsnInitialContextFactory

I'm migrating one application from Websphere to jboss EAP 6.0. I've made the Datasources on Jboss console. But in my code I've referring this way:
but while hitting the application from Jboss, it's giving the below error:
FATAL http-/135.155.175.224:8080-1 dbconn.DBAccess - getDatasource():
CRITICAL ERROR: JDBC Naming service exception: JBAS011843: Failed
instantiate InitialContextFactory
com.ibm.websphere.naming.WsnInitialContextFactory from classloader
ModuleClassLoader for Module "deployment.UPMSSSO.ear.UPMSSSO.war:main"
from Service Module Loader
Could anyone please hint the error. Is there any other in for JBoss?

Since you are migrating to Jboss from WebSphere and you are using "com.ibm.websphere.naming.WasInitialContextFactory" class, which is WAS specific class, that's why you are getting this error.
Change that to "org.jboss.naming.remote.client.InitialContextFactory" and then try again. That should resolve your issue.
UPDATE
All you should have to do is new InitialContext(), without any argument. JNDI is pre-configured with the appropriate properties for you by the app server unless you are looking for remote objects on any other server.

EJBConfigurationException: Bean class for EJB not found

I have an java web-project where ejb's (3.1) are configured. When I add (add projects) the ear-project to the local websphere aplication server v8.0 (in eclipse) and start the server I receive the following error:
Error while processing references for EJB-in-WAR: com.ibm.ejs.container.EJBConfigurationException: The bean class "nl.xx.xx.xx.xx.xx.GebruikerFacade" for EJB "xx-xx-ear#xx-xx-web.war#GebruikerFacade" is not found.
Because I couldn't find the problem I deployed the ear-file to the websphere application server via the admin console (new application). The ear-file I created using mvn clean install package.
Then when starting the application from within de admin console the error is not given.
In stead it is reporting that the remote interface of the GebruikerFacade is binded.
What can be the cause of the error when starting the application server where the ear-project is added using add project.
Extra info: Added 20141211
The reason why the bean class cannot be found is the fact that when the ear is deployed to the webspere application server via add project the business interface is empty within the deployed ear.
This is a property in Enterprise Java Bean properties/Bind EJB Business of an Enterprise bean.
The module, bean and uri property are set but the business interface which has to be the full path to the Remote interface class is not.
When de ear is deployed on the application server via new application the business interface contains the Remote interface Class.
Console-output in new answer below.

The first error in the console-output when the ear-project is deployed to the server using "right click server - add/remove project":
[11-12-14 8:14:39:832 CET] 00000030 ComponentData E CWMDF0012E: The bean class nl.company.rvl.facade.GebruikerFacade for EJB
rvl-ear#rvl-web.war#GebruikerFacade is not found.
Somehow the "Starting EJB jar" proces is not initiated at that point.
If the ear-file is added as a new application within the admin console and this application is started that proces is taking place giving the
following output:
[11-12-14 9:01:16:381 CET] 00000047 AbstractEJBRu I WSVR0037I: Starting EJB jar: rvl-web-2015.2.10.00-SNAPSHOT.war
[11-12-14 9:01:16:881 CET] 00000047 EJBContainerI I CNTR0167I: The server is binding the nl.company.rvl.facade.GebruikerFacadeRemote interface of the GebruikerFacade enterprise bean in the rvl-web-2015.2.10.00-SNAPSHOT.war module of the rvl-ear application. The binding location is: ejb/gebruikerFacade-bnd
[11-12-14 9:01:16:897 CET] 00000047 AbstractEJBRu I CNTR0167I: The server is binding the nl.company.rvl.facade.GebruikerFacadeRemote interface of the GebruikerFacade enterprise bean in the rvl-web-2015.2.10.00-SNAPSHOT.war module of the rvl-ear application. The binding location is: java:global/rvl-ear/rvl-web-2015.2.10.00-SNAPSHOT/GegevenspartnerFacade!nl.company.rvl.facade.GebruikerFacadeRemote
[11-12-14 9:01:16:897 CET] 00000047 EJBContainerI I CNTR0167I: The server is binding the nl.company.rvl.facade.GebruikerFacade interface of the GebruikerFacade enterprise bean in the rvl-web-2015.2.10.00-SNAPSHOT.war module of the rvl-ear application. The binding location is: ejblocal:ejb/gebruikerFacade-bnd
[11-12-14 9:01:16:897 CET] 00000047 AbstractEJBRu I CNTR0167I: The server is binding the nl.company.rvl.facade.GebruikerFacade interface of the GebruikerFacade enterprise bean in the rvl-web-2015.2.10.00-SNAPSHOT.war module of the rvl-ear application. The binding location is: java:global/rvl-ear/rvl-web-2015.2.10.00-SNAPSHOT/GebruikerFacade!nl.company.rvl.facade.GebruikerFacade
[11-12-14 9:01:16:912 CET] 00000047 AbstractEJBRu I WSVR0057I: EJB jar started: rvl-web-2015.2.10.00-SNAPSHOT.war

In the tab of Servers, make a full publish of your project. Even if you save it, you have to publish it into your server. It's a bit annoying the fact of having to publish everytime you make a small change, but is the way to deploy the .war into the server.
If that doesn't work, try to delete the server and configure a new one.
Have a nice code!

Deploy war to JBOSS

I tried to deploy a Vaadin hello world application in JBOSS. The application is as simple as it can be.
My development environment is eclipse for java EE + tomcat
java.lang.RuntimeException: Error configuring property: includeWebInfInClasspath for WarClassLoaderDeployer
at org.jboss.kernel.plugins.dependency.ConfigureAction.dispatchSetProperty(ConfigureAction.java:112)
at org.jboss.kernel.plugins.dependency.ConfigureAction.setAttributes(ConfigureAction.java:85)
(...)
Caused by: java.lang.IllegalArgumentException: No such property includeWebInfInClasspath for bean org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer available [java2ClassLoadingCompliance, parentFirst, requiredInputs, filteredPackages, allInputs, deploymentRegistry, class, stage, wantComponents, componentsOnly, input, inputs, relativeOrder, output, useUnitName, outputs, topLevelOnly]
I have tried to google this error with no success.
Does anyone have any clues?
Is it a web server configuration or my *.war is missing something?
EDIT:
This error occur when I start the server after placing my *.war in the folder.
My JBOSS version is 5

I guess, you're using an old JBoss 5.
The WarClassLoaderDeployer is configured in the file server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml. (The 'default' directory should be changed to whatever you passed as -c parameter) Open the file, find the WarClassLoaderDeployer bean and drop the line defining the property with name includeWebInfInClasspath.

java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is: java.rmi.server.ExportException:

I have upgraded my web application from java6 to java7. I have deployed web tier, ejb tier and web service tier on weblogic 10.3 successfully. Everything works fine except stateful ejb. During these ejb invocation , I get following exception on server logs.
java.rmi.UnmarshalException: cannot unmarshaling return; nested exception is:
java.rmi.UnexpectedException: Failed to parse descriptor file; nested exception is:
java.rmi.server.ExportException: Failed to export class SearchAccountSessionBean_qa86w0_EOImpl problem with rmi descriptor signature getFilterCount([Lcom.abc.SearchResultFilterName;)RemoteMethodSet=[setPrimaryKey(Ljava.lang.Object;), ......
Can anyone advice what may be the root cause. my ejb version is 2.0.

Sometimes the EJBCompilerCache in weblogic will have the old bean details resulting in the above said error.
Just clean the weblogic application server tmp and cache folders and try again.