Porting from JBoss to WebLogic

There's a migration tool on the WebLogic site (wltool.zip) that purports to convert JBoss 4.x deployment descriptors to WebLogic 9.x format. When I run the tool I get the following error:
Exception in thread "main" java.lang.NoClassDefFoundError: weblogic/ejb20/dd/xml/DDUtils
at weblogic.tools.EJBHandler.<init>(EJBHandler.java:25)
at weblogic.tools.WLHandlerFactory.getHandler(WLHandlerFactory.java:11)
at weblogic.tools.jb2wl.convertToWL(jb2wl.java:45)
at weblogic.tools.jb2wl.<init>(jb2wl.java:28)
at weblogic.tools.jb2wl.main(jb2wl.java:62)
I've got every jar in the 9.2 server/lib in the classpath, but from what I can tell the package weblogic.ejb20.dd.xml doesn't exist.
Is there an update for the migration tool, or am I missing something?

It appears that tool is based on WLS 8.1 and hasn't been ported to 9.x. It is using internal classes so it won't just work on multiple WLS versions unchanged.
Unfortunately I don't have any better suggestion than downloading 8.1 and running the tool there to generate the weblogic descriptors.
You could than run the weblogic.DDConverter tool in 9.x to convert the 8.1 descriptors to the 9.x/JEE 5 versions if you wanted. 8.1 descriptors will work fine in 9.x unchanged though.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Similar Messages

Error in deploying entity beans - migration from JBoss to Weblogic 10.3.4

Hi,
I am migrating EJB2.x code from JBoss to Weblogic 10.3.4. As a first step, I am tyring to deploy just Entity beans. I get following error when deploying to server.
'weblogic.application.ModuleException: Exception preparing module: EJBModule(myEJB.jar)
Unable to deploy EJB: CollMetaData from myEJB.jar:
[EJB:011017]Error while reading 'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was:
There are 1 nested errors:
java.lang.NullPointerException
     at weblogic.ejb.container.cmp.rdbms.finders.EjbqlFinder.setMethods(EjbqlFinder.java:288)
     at weblogic.ejb.container.cmp.rdbms.Deployer.processFinders(Deployer.java:744)
     at weblogic.ejb.container.cmp.rdbms.Deployer.readTypeSpecificData(Deployer.java:446)
     at weblogic.ejb.container.persistence.PersistenceType.setTypeSpecificFile(PersistenceType.java:506)
     at weblogic.ejb.container.persistence.PersistenceType.setupDeployer(PersistenceType.java:455)
     at weblogic.ejb.container.deployer.CMPInfoImpl.setup(CMPInfoImpl.java:118)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1214)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:442)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:613)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:184)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Can someone help me fixing the issue?
I changed schema locations of descriptor files as suggested at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13706/overview.htm#i1074199 (see the third category for '*Enterprise Bean 2.1*' in the listing Table 1-1). Alternatively, you may see the schema locations for EJB2.0 directly at http://download.oracle.com/docs/cd/E17904_01/web.1111/e13719/dd_reference.htm#EJBPG481

JRE version in JBoss is 1.6.0_16. JVM in web logic is pointing to jrockit_160_22_D1.1.1-3 which is come in the package. It doesn't seem to be related to JVM version mismatch.
I think it is an issue with definitions in weblogic-cmp-rdbms-jar.xml file. How should be the definition of entity-descriptor appear for entity bean which has finder methods in ejb-jar.xml?
Please see the snippets from corresponding descriptor files below.
ejb-jar.xml
=========
<entity>
<display-name>EmpBean</display-name>
<ejb-name>EmpBean</ejb-name>
<local-home>LocalEmpBeanHome</local-home>
<local>LocalEmpBean</local>
<ejb-class>EmpBeanBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>EmpBean</abstract-schema-name>
<cmp-field>
<field-name>firstName</field-name>
</cmp-field>
<cmp-field>
<field-name>lastName</field-name>
</cmp-field>
<cmp-field>
<field-name>phone</field-name>
</cmp-field>
<cmp-field>
<field-name>address</field-name>
</cmp-field>
<primkey-field>lastName</primkey-field>
<query>
<query-method>
          <method-name>findByPrimaryKey</method-name>
               <method-params>
               <method-param>java.lang.String</method-param>
               </method-params>
          </query-method>
          <ejb-ql>SELECT Object(o) FROM EmpBean o WHERE o.lastName= ?1</ejb-ql>
     </query>
</entity>
weblogic-jar.xml
============
<weblogic-enterprise-bean>
<ejb-name>EmpBean</ejb-name>
<entity-descriptor>
     <pool>
          <max-beans-in-free-pool>20</max-beans-in-free-pool>
          <initial-beans-in-free-pool>5</initial-beans-in-free-pool>
     </pool>
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>6.0</type-version>
<type-storage>meta-inf/weblogic-cmp-rdbms-jar.xml</type-storage>
</persistence-use>
<finders-load-bean>true</finders-load-bean>
</persistence>
</entity-descriptor>
<local-jndi-name>ejb/EmpBean</local-jndi-name>
</weblogic-enterprise-bean>
weblogic-cmp-rdbms-jar.xml
====================
<weblogic-rdbms-bean>
<ejb-name>EmpBean</ejb-name>
<data-source-jndi-name>mysqlDS</data-source-jndi-name>
<table-map>
<table-name>emp</table-name>
<field-map>
<cmp-field>firstName</cmp-field>
<dbms-column>first_namel</dbms-column>
</field-map>
<field-map>
<cmp-field>lastName</cmp-field>
<dbms-column>last_name</dbms-column>
</field-map>
<field-map>
<cmp-field>phone</cmp-field>
<dbms-column>phone</dbms-column>
</field-map>
<field-map>
<cmp-field>address</cmp-field>
<dbms-column>address</dbms-column>
</field-map>
</table-map>
<weblogic-rdbms-bean>
Please ignore any typos that you may notice in above sample descriptions (because I just typed it here changing original names).
When I try to deploy the application, I get error message as posted in my first post above in this thread. Please correct me if I am making any erros in descriptor files.
Edited by: 839281 on Feb 25, 2011 10:55 AM
Edited by: venkatp on Mar 1, 2011 9:31 AM

Migrate EJB 3.0 from JBoss to Weblogic 10.3.5

Hi all,
I need help in deploying my ear file from Jboss to Weblogic, got this error relates to EJB module:
####<Dec 26, 2012 10:45:03 PM PST> <Warning> <Deployer> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1356590703830> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyScheduler'.>
####<Dec 26, 2012 10:45:03 PM PST> <Error> <Console> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <tungpl> <> <> <1356590703869> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Could not setup environment
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
     at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
     at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
     at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.naming.NameNotFoundException: While trying to look up ejb-info in /app/ejb/myEjb.jar#myEjb.; remaining name 'ejb-info'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
     at weblogic.deployment.BaseEnvironmentBuilder.autowireEJBRef(BaseEnvironmentBuilder.java:408)
     at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:513)
     at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
     at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
     at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
>
I have tried some solution in this thread https://kr.forums.oracle.com/forums/thread.jspa?threadID=2174802 but it doesn't help at all.
Could sb give me any idea?
Pretty thanks!
Edited by: user12925202 on Jan 20, 2013 11:33 PM

Frank,
Thanks. The @LOB annotations are missing.
Create table with:
CREATE TABLE TestBlob (id number PRIMARY KEY, xmlCol BLOB);
INSERT INTO TestBlob VALUES(1, EMPTY_BLOB());
The following is the complete listing for the EJB 3 class generated from table TestBlob.
package ejb3;
import java.io.Serializable;
import javax.persistence.Column;
import javax.persistence.Entity;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
@Entity
@NamedQueries({
@NamedQuery(name = "Testblob.findAll", query = "select o from Testblob o")
public class Testblob implements Serializable {
@Id
@Column(nullable = false)
private Long id;
private byte[] xmlCol;
public Testblob() {
public Testblob(Long id) {
this.id = id;
public Long getId() {
return id;
public void setId(Long id) {
this.id = id;
public byte[] getXmlCol() {
return xmlCol;
public void setXmlCol(byte[] xmlCol) {
this.xmlCol = xmlCol;
}

Call one session EJB3 from jboss to weblogic 10

Hi everyone.
I have a big problem. I have a session ejb3 in a weblogic server. I need start this session from jboss server.The code I used is as follows:
Environment env = new Environment();
     env.setInitialContextFactory(weblogic.jndi.Environment.DEFAULT_INITIAL_CONTEXT_FACTORY);
     env.setProviderURL("t3://ip:7001");
     env.setSecurityPrincipal("weblogic");
     env.setSecurityCredentials("cajamar1");
     Hashtable props = env.getProperties();
I copied all the libraries that I have been asking in the JBOSS server. In the end I managed to work but when I do the lookup on my session I get this error message.
++14:51:46,939 ERROR [STDERR] 09-sep-2010 14:51:46 weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport preProcess++
++ADVERTENCIA: Error pre-processing class com.gh.conn.GHBackEndConnectorInterface with weblogic.ejb.container.deployer.RemoteBizIntfClas++
++sPreProcessor@b1c3bc3'++
++java.lang.NoSuchMethodError: <init>++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassPreProcessor.preProcess(RemoteBizIntfClassPreProcessor.java:52)++
++at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPreProcessor.java:102)++
++at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:341)++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.enhanceClass(RemoteBizIntfClassLoader.java:143)++
++at weblogic.ejb.container.deployer.RemoteBizIntfClassLoader.loadClass(RemoteBizIntfClassLoader.java:129)++
++at weblogic.ejb.container.internal.RemoteBusinessIntfGenerator.generateRemoteInterface(RemoteBusinessIntfGenerator.java:67)++
++at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.readObject(RemoteBusinessIntfProxy.java:234)++
++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 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)++
++at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)++
++at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)++
++at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)++
++at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)++
++at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)++
++at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)++
++at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)++
++at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)++
++at weblogic.utils.io.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:197)++
Any help on the issue. Thanks for all.

Hi,
Please make sure that you have generated the Client Side Artifacts of your EJB3.0 App and Placed then at the JBoss side (Client side). Please refert to ": *http://weblogic-wonders.com/weblogic/2010/04/02/generating-ejb3-clientjar/*
Also make sure that you have "weblogic.jar" file at Cleint Application Side.
Thanks
Jay SenSharma

Application Migration from JBOSS to Weblogic Server

Hi,
I am facing lots of issues while deploying an .ear file on Weblogic server. In the JBOSS server the application is working properly but whenever I am trying to deploy it on Weblogic server its throwing me an error stating :
"ERROR: No j2ee modules detected in EAR archive. Deployment aborted. "
I tried to convert the things to .war file and tried to deploy the application, the application got deployed but its throwing 'exception'.
Please revert me back with some solution.
Thanks
Trishul

Is this forum about Jboss?
Is it about Weblogic?
If so, why do you put a question about a non-Oracle non-database product in a forum on Oracle Database?
Sybrand Bakker
Senior Oracle DBA

Urgent: JBOSS to Weblogic OIM applicaiton migration

Hello,
We've OIM 9102 BP15 on JBOSS non-clustered environment. There are customizations over the OIM UI to meet specific business requirement.
Now, we're planning to migrate the OIM application from JBOSS to Weblogic clustered environment (keeping OIM database intact). OIM documents says it supports weblogic release 10.3.0, 10.3.1 and later.
http://download.oracle.com/docs/cd/E14899_01/doc.9102/e14764/toc.htm#insertedID2
What should be the plan of migrating to WLS 11g application server keeping the OIM DB intact? Any document or metalink?
Thanks,
Edited by: oimuser007 on Sep 21, 2011 11:38 AM

Hello Experts,
One problem i see now is -
Few custom JSP are doing DB calls to show some data on the pages (see code snippet below):
============================================
import javax.naming.*;
Context ctx = null;
ctx = new InitialContext();
DataSource DriverManager = (DataSource)ctx.lookup("java:jdbc/xlDS");
conn = DriverManager.getConnection();
stmt = conn.prepareStatement(SQL);
rs = stmt.executeQuery();
while (rs.next()) {
=============================================
Now, in the new environment, an error message is showing instead of real data.
"While trying to look up /jdbc/xlDS in /app/webapp/xlWebApp/378768760".
When i check through Weblogic console for: services -> Data sources -> xlDS. Everything looks good here.
Any clue what is going wrong ?
Thanks,

Migrate EJB from Jboss to WL

Hi all,
I need help in deploying my ear file from Jboss to Weblogic, got this error relates to EJB module:
####<Dec 26, 2012 10:45:03 PM PST> <Warning> <Deployer> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <1356590703830> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyScheduler'.>
####<Dec 26, 2012 10:45:03 PM PST> <Error> <Console> <localhost.localdomain> <AdminServer> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <tungpl> <1356590703869> <BEA-240003> <Console encountered the following error weblogic.application.ModuleException: Could not setup environment
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1495)
at weblogic.servlet.internal.WebAppModule.activate(WebAppModule.java:438)
at weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:375)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:95)
at weblogic.application.internal.flow.ScopedModuleDriver.activate(ScopedModuleDriver.java:194)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:167)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.naming.NameNotFoundException: While trying to look up ejb-info in /app/ejb/myEjb.jar#myEjb.; remaining name 'ejb-info'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:144)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at weblogic.deployment.BaseEnvironmentBuilder.autowireEJBRef(BaseEnvironmentBuilder.java:408)
at weblogic.deployment.EnvironmentBuilder.addEJBReferences(EnvironmentBuilder.java:513)
at weblogic.servlet.internal.CompEnv.activate(CompEnv.java:157)
at weblogic.servlet.internal.WebAppServletContext.activate(WebAppServletContext.java:3144)
at weblogic.servlet.internal.WebAppModule.activateContexts(WebAppModule.java:1493)
I have tried some solution in this thread https://kr.forums.oracle.com/forums/thread.jspa?threadID=2174802 but it doesn't help at all.
Could sb give me any idea?
Pretty thanks!
Edited by: user12925202 on Jan 20, 2013 11:32 PM

Hi
Can you please provide me your application as well as the information such as the version of weblogic server, the configuration, etc, in order that I can reproduce ?
Thanks.
Edited by: 898251 on 2013-1-4 下午7:38

Problem when I tried to change weblogic listen port from 7001 to 80

HI! I have problem when I tried to change weblogic listen port from 7001 to 80. When I changed from 7001 to 7777 then all works ok! But why not on 80? With apache all works ok on 80 too.
I restart my weblogic server and then I have following errors.
<2009.1.4 16:02:13 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state ch
anged to STARTING>
2009.1.4 16:02:14 oracle.as.jmx.framework.PortableMBeanFactory setJMXFrameworkPr
oviderClass
INFO: JMX Portable Framework initialized with platform SPI "class oracle.as.jmx.
framework.wls.spi.JMXFrameworkProviderImpl"
2009.1.4 16:02:15 oracle.adf.share.config.ADFConfigFactory cleanUpApplicationSta
te
INFO: Cleaning up application state
<2009.1.4 16:02:22 EEST> <Notice> <Log Management> <BEA-170027> <The Server has
established connection with the Domain level Diagnostic Service successfully.>
<2009.1.4 16:02:22 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state ch
anged to ADMIN>
<2009.1.4 16:02:22 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state ch
anged to RESUMING>
<2009.1.4 16:02:22 EEST> <Emergency> <Security> <BEA-090087> <Server failed to b
ind to the configured Admin port. The port may already be used by another proces
s.>
<2009.1.4 16:02:22 EEST> <Error> <Server> <BEA-002606> <Unable to create a serve
r socket for listening on channel "Default". The address 85.254.224.235 might be
incorrect or another process is using port 80: java.net.BindException: Address
already in use: JVM_Bind.>
<2009.1.4 16:02:22 EEST> <Critical> <WebLogicServer> <BEA-000362> <Server failed
. Reason: Server failed to bind to any usable port. See preceeding log message f
or details.>
<2009.1.4 16:02:22 EEST> <Error> <Server> <BEA-002606> <Unable to create a serve
r socket for listening on channel "Default[2]". The address 127.0.0.1 might be i
ncorrect or another process is using port 80: java.net.BindException: Address al
ready in use: JVM_Bind.>
<2009.1.4 16:02:22 EEST> <Error> <Server> <BEA-002606> <Unable to create a serve
r socket for listening on channel "Default[1]". The address 192.168.0.102 might
be incorrect or another process is using port 80: java.net.BindException: Addres
s already in use: JVM_Bind.>
<2009.1.4 16:02:22 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state ch
anged to FAILED>
<2009.1.4 16:02:22 EEST> <Error> <WebLogicServer> <BEA-000383> <A critical servi
ce failed. The server will shut itself down>
<2009.1.4 16:02:22 EEST> <Notice> <WebLogicServer> <BEA-000365> <Server state ch
anged to FORCE_SHUTTING_DOWN>
2009.1.4 16:02:22 oracle.adf.share.config.ADFConfigFactory cleanUpApplicationSta
te
INFO: Cleaning up application state
2009.1.4 16:02:22 oracle.adf.share.config.ADFConfigFactory cleanUpApplicationSta
te
INFO: Cleaning up application state
Best regards!

Debuger,
It does not matter which WLS version I am using (although I'm using 10.3, the one that comes with JDev 11g).
The problem is that SOME OTHER PROCESS on your machine is listening on port 80. Guess you need to go to the Microsoft forums to find out how you can tell what that OTHER, NOT WLS process is.
John

Runtime Datasource from Jboss/Weblogic

I have a application running JBoss, which we uses the datasource in the deploy folder.
I have the report viewer working it is using the datasource from within the report file itself. At runtime, i would like to change the datasource in the report to use the datasource from Jboss, or pass a open connection. My only want to have one connection pool managed by the applicaiton server(Jboss/Weblogic).
Thanks. Please let me know if it is unclear.

I understand that I don't have the ability to pass in a connection. However, it is possible to use the Jboss/Weblogic datasource in the deploy folder. If so, could you point in the right direction. So I could share the database connection pool.
I have tried to use the setting JNDI string in the propertyBag for the connectionInfo. However, I am unable to get it to work.
Thanks in advance for your time.

Porting portlets from WebSphere to Weblogic Portal Server

How to Porting portlets from WebSphere to Weblogic Portal Server can any one help
me by providing the suitable steps , or material to know how to go about it.
Thanks in advance

To be in same page, iam running the client program using the IBM jre and using all the websphere client jars set in classpath. This program conatins intial context factory as "com.ibm.websphere.naming.WsnInitialContextFactory" and provider url as "iiop://hostname:portnumber" it contacts the EJB bean method which is hosted on the weblogic server on the "hostname" machine. When it tries to contact i get the errror as
"javax.naming.NameNotFoundException: Context: , name: java.iecc.env.ejb.elf.client_new(My JNDI name): First component in name java.iecc.env.ejb.elf.client_new not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]"

Porting from weblogic.event to JMS

          Hi,
          Has anyone done porting from weblogic.event (pre JMS) to JMS? If so, please share
          your experience and point me to any resources.
          Thanks,
          Tahir


The J2EE reference implementation did not have any such thing as a "startup
class" last time I checked. That is a WebLogic feature.
Cameron Purdy
[email protected]
http://www.tangosol.com
WebLogic Consulting Available
"vamsi" <[email protected]> wrote in message
news:39e47c60$[email protected]..
>
I am trying to port some of java code to J2EE and i am having problemsetting up startup classes in J2EE enterprise server.
Any help would be really appreciated. thanks in advance.

Jboss vs weblogic; expert commets

Hi,
Iam doing some comparison and benchmarking betweeen jboss and weblogic, just for the purpose of looking some cost effective measures. we are currently using wls8,1 in our production servers. ...lot of BEA licenses ... :)
I have a quick question and iam looking for some inputs from you:
1) Do you have some benchmarkings between JBOSS & WEBLOGIC8.1 ?
If you know of any websites, that would be perfect.
Thanks, sangita

If they are from creditable institutions yes, other
wise it is not important enough to spend the week
benchmarking and making sure the test runs with out
problems/tuning,�
---------------------------JBoss is credible. For the price, I'd say it's worth playing around with it but only if you are willing to accept the downsides with the documentation and administration. As far as trhe adminstration stuff goes, they aer doing some cool thinghs with MBeans but it was a little rough around the edges and getting JBoss set up can mean a lot of config file editing and the organization of these config files can be confusing.
For example, trying to get two JBoss instances to run on a single box (only worthwhile on multi-CPU machines) was painful. It was basically trial and error. Try to start the second instance and then search files to references to the port number that was already bound. Change it. Try to start again and look for the next post number. There's no single place to set the port numbers for all the services.

Deploying ear application - migrating from OC4j to Weblogic

I am trying to migrate application from OC4J to weblogic server. Apart from usual differences in descriptors, structure of EAR etc. I came across unusual error:
"both the remote home and remote component interface must be specified. Currently, only one of them is specified"
It is about deploying session bean. Usual EJB3 stateless session bean with local and remote interface, deployed without any problem on OC4J and JBoss. Of course, I know home interfaces are something to do with EJB 2.1, but this is EJB3 application and, I guess, Weblogic has full support for it. Does it? :)
Anyway, is there workaround? Or am I missing something? I don't have to tell you what problems we will be facing if I have to restructure whole application with dozens and hundreds of session beans.
Thanks a lot!

OK. I just want to make sure that there are no problems with the deployment descriptors.
To pin point the problem do the following in JDeveloper:
1. Create a simple EJB 3.0 session bean
2. On that session bean create a Sample Java Client.
3. Run the Session Bean
4. Run the Client
5. If both are running fine, compare the deployment descriptors from the sample and your real application.
--olaf

Changing the port of JBoss Server

Hi All,I want to change the default port of JBoss server from 8080 to some other port.How to do this?Thanks in advance.

There are JBoss forums out there....
But since I know the answer, I'll tell you, at the risk of rewarding your laziness. To change port 8080 to eg. 9090...
Alter server.xml, mine is in
D:\Apps\jboss-4.0.2\server\default\deploy\jbossweb-tomcat55.sar\server.xml
Alter this setting....
      
      <Connector port="8080" address="${jboss.bind.address}"
         maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
         emptySessionPath="true"
         enableLookups="false" redirectPort="8443" acceptCount="100"
         connectionTimeout="20000" disableUploadTimeout="true"/>to this
      
      <Connector port="9090" address="${jboss.bind.address}"
         maxThreads="250" strategy="ms" maxHttpHeaderSize="8192"
         emptySessionPath="true"
         enableLookups="false" redirectPort="8443" acceptCount="100"
         connectionTimeout="20000" disableUploadTimeout="true"/>regards,
Owen

How to upload and download any file from plsql through weblogic server

hi all,
how to upload and download any file from plsql through weblogic server? i am using oracle 10g express edition and jboss.
Thanks and Regards,
MSORA

hi bala ,
for a windown server u can use VNC (virtual network connection) which opens a session on u r desktop later u can drag and drop form there vice versa and for a linux box you can use Win SCP which helps to open a session with interface to u r desktop in both cases you can upload and down load files very easiy just as we drag and drop items in a simple pc .. we use the same technique...
bye
vamshi

Porting from JBoss to WebLogic

Similar Messages

Maybe you are looking for