Deploying mdb in weblogic 9.0

i have a simple mdb aplication ..
i have deloyed it in weblogic 9.0..
but it is showing error in connection factory
JNDI Name..like replace the JNdi name ..
pls hel me out to solve the problem
thank u

We discovered that BEA uses a directory named "autodeploy". By dropping our Jackrabbit 1.1 RAR file (resource adapter), BEA would auto-deploy it. No need to deal with the buggy WebLogic Admin console.
Needed to add the weblogic-ra.xml file to the META-INF directory, and set it up properly. Re-jar it all up as a .rar file, then copy it to the autodeploy directory. The other step is to make sure that the target repository directory exists (I pre-created [bea_home]/jackrabbit/ directory), and that the repository.xml file is already there before you deploy your .rar. Then start up the sample portal server, and the rar file will deploy as a resource adapter. To see it, go into the main server console, click on Deployments > Monitoring > Resource Adapters > Outbound Connection Pools. Jackrabbit should show up there.
This was the directory in which we dropped our RAR for testing:
[bea_home]/weblogic92/samples/domains/portal/autodeploy
Start the sample portal server at:
Windows
[bea_home]/weblogic92/samples/domains/portal/bin/startWebLogic.cmd
UNIX
[bea_home]/weblogic92/samples/domains/portal/bin/startWebLogic.sh
NOTE: This didn't end our headaches. Now we're dealing with Jackrabbit creating connections and never releasing them. Hundreds and hundreds of connections, until it runs out of its connection pool. Hideous. But that's a problem for another thread.
Message was edited by:
LanceZechinato

Similar Messages

Deploying MDB on WebLogic server 8.1 (SP2) with Tibco JMS

Hi,
 I am currently facing problems to deploy and run my MDB on weblogic connecting it to Tibco JMS as the foreign jms server.
 
 My ejb-jar.xml:
 
 <message-driven>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <ejb-class>com.db.deam.mdb.DeAMMsgFactors</ejb-class>
 <transaction-type>Container</transaction-type>
 <message-driven-destination>
 <destination-type>javax.jms.Topic</destination-type>
 </message-driven-destination>
 </message-driven>
 </enterprise-beans>
 <assembly-descriptor>
 <security-role>
 <role-name>soiadmin</role-name>
 </security-role>
 </assembly-descriptor>
 
 weblogic-ejb-jar.xml:
 
 <weblogic-enterprise-bean>
 <ejb-name>DeAMMsgFactors</ejb-name>
 <message-driven-descriptor>
 <pool>
 <max-beans-in-free-pool>20</max-beans-in-free-pool>
 <initial-beans-in-free-pool>10</initial-beans-in-free-pool>
 </pool>
 <destination-jndi-name>WLFactorsTopic</destination-jndi-name>
 <connection-factory-jndi-name>WLFactorsCF</connection-factory-jndi-name>
 <jms-polling-interval-seconds>10</jms-polling-interval-seconds>
 </message-driven-descriptor>
 <transaction-descriptor>
 <trans-timeout-seconds>100000</trans-timeout-seconds>
 </transaction-descriptor>
 </weblogic-enterprise-bean>
 <security-role-assignment>
 <role-name>soiadmin</role-name>
 <principal-name>jmsusername</principal-name>
 </security-role-assignment>
 
 Error:
 weblogic.ejb20.WLDeploymentException: [EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The err
 or was:
 javax.jms.JMSSecurityException: invalid name or password.
 javax.jms.JMSSecurityException: invalid name or password
 at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:395)
 at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:581)
 at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1743)
 at com.tibco.tibjms.TibjmsTopicConnection.<init>(TibjmsTopicConnection.java:35)
 at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:92)
 at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:121)
 at com.tibco.tibjms.TibjmsTopicConnectionFactory.createTopicConnection(TibjmsTopicConnectionFactory.java:66)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:607)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 at weblogic.ejb20.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:638)
 at weblogic.ejb20.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1783)
 at weblogic.ejb20.internal.JMSConnectionPoller.connectToJMS(JMSConnectionPoller.java:1087)
 at weblogic.ejb20.internal.JMSConnectionPoller.trigger(JMSConnectionPoller.java:970)
 at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
 at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)
 at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)
 at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
 [JMSConnectionPoller] : ** Connect attempt for: WLFactorsTopic was: unsuccessful
 
 Any help would be appreciated.
 
 Thanks, 
 Kiran Kumar MV.

I was able to use MDB to receive msg from a Tibco JMS queue. This is what you have to do: using WL console,
 - set up a foreign JMS Server. Make sure you specify the following correctly: jndi initial context factory (tibjms class), tibjms server url, username/password
 - create a foreign connection factory (if you are using CMT, make sure you create a XA compliant connection factory in Tibco JMS server). It seems that you have to specify URL again when creating XA connection factory in Tibjms.
 - create a foreign destination (queue/topic)
 In ejb-jar.xml and weblogic-ejb-jar.xml,
 - use resource-ref (wrapper) to specify the foreign connection factory
 - use resource-env-ref to specify the foreign destination.
 - In MDB ejb-jar.xml, specify destination-jndi-name and connection-factory-jndi-name.
 See Message Driven Beans chapter in Programming WebLogic EJB doc.
 Good luck.

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

Deploying EJB 3.0 MDB on Weblogic 10.3

My MDB is as follows:
package test;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.Message;
import javax.jms.MessageListener;
@MessageDriven(mappedName = "mdb01/queue01",
          activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue") })
public class MDB implements MessageListener {
     public void onMessage(Message message) {
          System.out.println("Received Message: " + message);
While deploying it on WebLogic 10.3 I get the below error:
javax.naming.NameNotFoundException: While trying to lookup 'mdb01.queue01' didn't find subcontext 'mdb01'. Resolved ''; remaining name 'mdb01/queue01'
     at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
     at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
     at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
     at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
     at javax.naming.InitialContext.lookup(InitialContext.java:392)
Please advise what configurations I should do in WebLogic in order to deploy this MDB.

on WebLogic console, go to the "general" tab of your server's page, and click on "view JNDI tree". there you can see whether your queue has been deployed to the server.
if not there, verify that the queue has been properly targeted. it can be tricky, and I suggest you to use subdeployments.

AQ - MDB on WebLogic

Hi,
I have written a java startup class to bind the AQ connection factory and AQ queue to the JNDI tree of a WebLogic server and have deployed an MDB on WebLogic to listen to the AQ. The MDB is working fine and is continuously listening to the Oracle AQ hosted on a Solaris box.
But, the problem is that no matter how many instances of the MDB are deployed in the pool, onMessage() method of just one MDB is called repeatedly i.e. only single instance of MDB consumes AQ messages no matter how many instance are in pool or how may threads are available in queue.
The MDB is deployed on WebLogic server 7 sp 4 on a Win 2000 box and has 5 inctances in the pool. I am using OCI driver for the connection to the AQ. Oracle 9.2.0 is on a Solaris box and the IP address and the machine name of the JMS client (i.e. windows machine) is included in the /etc/hosts of the Solaris box.
Any help towards achieving concurrency in consumption of messages from Oracle AQ would be great.
Regards,
Diptanshu

Using Message Bridge between AQ & WLS queue, and making the MDB listen to the WLS queue has solved this issue.
Regards,
Diptanshu

Deploy MDBs in Different WL Instances Subscribed to Same Topic

 Let's say I have MDBs X, Y, and Z, each needing to be deployed to a different Weblogic
 server. All need to subscribe to the same Topic. How is this done? Specifically,
 how is the Topic configured and how are the MBDs deployed?
 Thanks,
 Jim Goodwin


For your reading enjoyment, I'm posting some of my
 internal notes on durable subscriber MDB's. This consolidates
 newsgroup information in one place.
 Jim Goodwin wrote:
 > "Jim Goodwin" <[email protected]> wrote:
 >
 >>Let's say I have MDBs X, Y, and Z, each needing to be deployed to a different
 >>Weblogic
 >>server. All need to subscribe to the same Topic. How is this done? Specifically,
 >>how is the Topic configured and how are the MBDs deployed?
 >>
 >>Thanks,
 >>
 >>Jim Goodwin
 >
 >
 > Bah! Nevermind. I found the information I was looking for in other threads.
 A durable topic subscriber MDB uses its name to generate its client-id.
 Since JMS enforces uniqueness on this client-id, this means that if a durable
 subscriber MDB is deployed to multiple servers only one server will be able
 to connect. Some applications want a different behavior where
 each MDB pool on each server gets its own durable subscription.
 The MDB durable subscription id, which must be unique on its topic, comes from:
 1) <jms-client-id>MyClientID</jms-client-id>
 (the weblogic dtd)
 2) if (1) is not set then the client-id
 comes from the ejb name.
 The durable subscription is uniquely identified within a cluster by a
 combination of "connection-id" and "subscription-id". Only one active
 connection may use a particular "connection-id" within a WebLogic cluster.
 The connection id comes from:
 1) The "ClientId" attribute configured on the WebLogic connection factory.
 This defaults to null. Note that if the ClientId is set on a connection
 factory, only one connection created by the factory
 may be active at a time.
 2) If (1) is not set, then, as with the subscriber-id,
 the connection-id is derived from jms-client-id descriptor attribute:
 <jms-client-id>MyClientID</jms-client-id>
 (the weblogic dtd)
 3) If (1) and (2) are not set, then, as with the subscriber-id,
 the connection-id is derived from the ejb name.
 Work-around:
 A) Create a custom connection-factory for each server:
 1) configure "JNDIName" to the same value across all servers
 ("myMDBCF" in this example)
 2) configure "ClientId" to a unique value per server
 3) enable "UserTransactionsEnabled"
 4) enable "XAConnectionFactoryEnabled"
 5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
 6) target the CF at a single WebLogic server
 (Number 5 is required for non-transactional topic MDBs)
 B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
 factory to the JNDI name of the custom connection factories configured in
 (A). Optionally, also specify the subscriber-id via the jms-client-id
 attribute.
 <weblogic-ejb-jar>
 <weblogic-enterprise-bean>
 <ejb-name>exampleBean</ejb-name>
 <message-driven-descriptor>
 <connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
 <jms-client-id>myClientID</jms-client-id>
 </message-driven-descriptor>
 </weblogic-enterprise-bean>
 </weblogic-ejb-jar>
 C) Target the application at the same servers that have the custom connection
 factories targeted at them.
 Notes/Limitations:
 1) If the MDB is moved from one server to another, the MDB's corresponding
 connection-factory must be moved with it.
 2) This work-around will not work if the destination is not in the same
 cluster as the MDB. (The MDB can not use the local connection factory, which
 contains the connection-id, as connection factories do not work unless they
 are in the same cluster as the destination.)
 3) This work-around will not work for non-WebLogic JMS topics.

Error deploying MDB on weblogic81

Hi,
I am tryin to deploy an MDB on weblogic server. I am getting the following error.
Unable to deploy EJB: C:\bea\weblogic81\server\bin\applications\alert from alert:
weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: com.motorola.tpm.common.alertMgmt.mdb.AlertMDB
I have checked the jar file the path is correct for the MDb class. ejb-jar.xml looks like beloew.
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>AlertMDB</ejb-name>
<ejb-class>com.motorola.tpm.common.alertMgmt.mdb.AlertMDB</ejb-class>
<transaction-type>Container</transaction-type>
<acknowledge-mode>auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
I am placing the MDB.jar under
bea\weblogic81\server\bin\applications\alert.
Do I need to add weblogic-eb-jar.xml to the jar file? or I need to just place it in META-INF folder under alert folder.
Regards
Pallavi

Seems OC4J9.0.2 has some problems with AQ/MDB....
But i have tested a small test case application which uses AQ/MDB in OC4J9.0.3.
It works fine...So if anyone of you want that let me know abt that...
i will send it....:-)
Cheers
--Venky

How to delete the deployed composite in weblogic server 11g

Can someone tell me how to delete the deployed composite in weblogic server 11g ?I'm facing an issue where the weblogic server is getting started and immediately after sometime the server changes to "Force shutdown"..When i checked the logs,there is an error in one of the composite i deployed..So now i wanted to delete the deployed composite?Please help ....
Thanks

Hi
1. Deleting a domain will not hold any references. But make sure that under your user_projects/applications also remove the folder that matches with your domain. Basically under user_projects folder you will see 2 folders named applications and domains. When you create a domain say mySoaDomain, it will crate a folder with the same name under applications folder also with few files like em.ear. If you do this, then you can crate a new soa domain and use the same old name.
2. NOW comes the most important thing. If you create a new SOADomain, at one point, you had to give details for soainfra and mds schemas. If you give your current existing db details (that was used for your old deleted domain), then you may still have the issues. Because the soainfra db may still have the instances for your old process.
3. If you really want to have a full clean soa domain, here is what you do:
a) Run rcu and drop the existing schemas for soainfra and mds.
b) Run rcu again and create above schemas again.
c) Now create SOADomain using config wizard and refer above clean rcu db and you are all set.
3. Under your domain root folder, just searh for files named with your workflow and you should see the .jar location.
Thanks
Ravi Jegga

Pagelets not rendering in Fusion ADF application pages deployed on standalone weblogic server

HI All,
I am creating a Pagelet Producer connection, and dragging a pagelet on the page as iframe, with height auto. When I run the application in the integrated weblogic server, I am able to see the pagelet. However when I deploy the application on the standalone weblogic server, then the pagelet isn't rendered.
I am using fusion ADF application 11.1.1.7 and standalone weblogic server v 10.3.6.
Thanks in advance for yours assistance. Please I need a solution for this uregently. DO let me know, if you need any additonal information.
Regards,
Nikhil Mahto

Sorry for the wrong infromation. The correct scenario is:
I have an ADF application, in which I have a Pagelet producer connection, pages and taskflows. This ADF application is inlcuded in a Webcenter Portal Framework application, as a shared library. When the WCF application is deployed on the Weblogic server, the pagelets don't appear on the pages.
I tried the FRAMEBUSTING context parameter to never but it didn't help.
Regards,
Nikhil Mahto

Deployment Application To Weblogic Server Failed

Hello every body
I need your help in this problem please :
I'm using Oracle JDeveloper 11.1 in my local machine, I Installed Weblogic Server 10.3 on the server and it's works well, I made new JDBC connection in Weblogic Server and it's works well too.
I made new ADF Fusion web Application and I used the same connection that I used in Weblogic server and it's works well.
I made new Application Server Connection from my local machine and It's works well with my user account.
In my project I made new WAR deployment, Also I configured my Application properties to Bind Application to the Weblogic server Instance.
1-when I try to deploy my project to Weblogic server I get this error message :
Deploying Application...
[Deployer:149034]An exception occurred for task [Deployer:149026]deploy application test_webapp on AdminServer.: Failed to load webapp: 'test_webapp.war'.
weblogic.application.ModuleException: Failed to load webapp: 'test_webapp.war'
#### Deployment incomplete. #### Feb 15, 2009 12:18:01 PM
Deployment Failed
2-Another application was deployed before to Weblogic server, it seems running well, whereas Weblogic Server marks my deployment health as OK, but when I try to run it for test using this URL : http://serverIP:Port/Deployment Name, I get this Error : Error 403--Forbidden
What Should I do for both cases ?
Thanks a lot ...

Thanks Timo
But first I don't use any library at my project , this is last log in Weblogic Server logfile :
####<Feb 16, 2009 1:56:58 PM EET> <Warning> <DeploymentService> <D2KR2> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <Osama> <> <> <1234785418343> <BEA-290008> <Deployment service servlet encountered while extracting uploaded file to directory ".\servers\AdminServer\upload\test_webapp". Exception is: "invalid distance code".>
Where D2KR2 is my Server Name
Osama is my user in Weblogic Server
test_webapp is the Application name
My problem didn't solved yet, and I'm new at JDeveloper ADF.
Where I can find clear information about deploying projects to Weblogic server.
Thank's Agin ...
Edited by: user8330337 on 15/02/2009 04:09 ص

Plsql webservices deploy error in weblogic.... Can anybody help me.. Urgent

Could any body look into this exception....
I am stuggling with this for the last one week........
I have generated the webservices from PLSql procedure, deployed and tested in oc4j which is successfull running and I can access the webservice too.....
The same ear file, when i deploy in to weblogic I am getting the follwing error, can anybody look in to this and help me....
<May 20, 2006 2:09:14 PM GMT+05:30> <Error> <Deployer> <BEA-149231> <Unable to s
et the activation state to true for the application 'gtry-gtry-WS'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "gwsSoapHttpPort" fa
iled to preload on startup in Web application: "gtry-gtry-context-root".
java.lang.IllegalStateException: could not find schema type named {{http}//orass
pcon/Gws.wsdl/types/}EmpRecUser
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalTypeNod
e.getSchemaType(AnonymousTypeFinder.java:181)
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getTypeNamed(
AnonymousTypeFinder.java:86)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.create
BindingTypeFrom(Deploytime109MappingHelper.java:888)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.proces
sTypeMappings(Deploytime109MappingHelper.java:466)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBi
ndingFileFrom109dd(Deploytime109MappingHelper.java:246)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>
(Deploytime109MappingHelper.java:162)
at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.create
RuntimeBindings(RuntimeBindingsBuilderImpl.java:80)
at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.jav
a:272)
at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:94)
at weblogic.wsee.ws.WsFactory.createServerService(WsFactory.java:58)
at weblogic.wsee.server.servlet.WebappWSServlet.initRuntime(WebappWSServ
let.java:70)
at weblogic.wsee.server.servlet.WebappWSServlet.initImpl(WebappWSServlet
.java:32)
at weblogic.wsee.server.servlet.BaseWSServlet.init(BaseWSServlet.java:40
at javax.servlet.GenericServlet.init(GenericServlet.java:256)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(St
ubSecurityHelper.java:276)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
121)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecuri
tyHelper.java:68)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubL
ifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHel
per.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
mpl.java:493)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
ervletContext.java:1688)
Thanks in Advance
Jayanthy.

Hi Supriya,
Check the following:
* Whether the Report is locked in the server.
* Are the parameters you pass from the form to report have the similar data types.
Hope your problem is fixed.
Regards.

Error while deploying composite to weblogic

Getting following error while deploying composite to weblogic; As I got some reason from google that, its because of jdk8. If it is a known issue, does oracle released any patch for this?
8:16:43 AM] Server is most likely down. Please check the server status and make sure it is up.
[08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
[08:16:43 AM] HTTP error code returned [-1]
[08:16:43 AM] Error message from server:
Server is most likely down. Please check the server status and make sure it is up.
[08:16:43 AM] Check server log for more details.
[08:16:43 AM] Error deploying archive sca_ValidatePayment_rev1.0.jar to partition "default" on server AdminServer [http://192.168.2.1:7001]
[08:16:43 AM] Deployment cancelled.
[08:16:43 AM] ---- Deployment incomplete ----.
[08:16:43 AM] Error deploying archive file:/C:/JDeveloper/mywork/e2e-1201-composites/ValidatePayment/deploy/sca_ValidatePayment_rev1.0.jar
(oracle.tip.tools.ide.fabric.deploy.common.SOARemoteDeployer)

Hi Priya,
Can you check the server status.It clearly says that the server is down.Check the status of the server and also the disk space .
[08:16:43 AM] Error message from server:
Server is most likely down. Please check the server status and make sure it is up.

While deploying application in weblogic 10.3 getting following eror

while deploying app into weblogic 10.3 getting following taglib errors please any one cane ensure this....
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
Substituted for the exception weblogic.servlet.jsp.CompilationException which lacks a String contructor, original message - footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:5:5: Invalid tag library. <%@ taglib uri="/WEB-INF/tb-tags.tld" prefix="tb"%> ^----^ connection.jsp:5:5

Hi Pratik,
Would suggest you to create a "*wlfullclient.jar*" by going through the below link and add it in your weblogic workshop and then try to deploy your application. Also it is always recommended that you should compile the old application again with the new JDK version your new weblogic sever is using.
Tpoic:*Creating a wlfullclient.jar for JDK 1.6 client applications*
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html#wp1078098
Hope this would help you.
Regards,
Ravish Mody

Deploy EAR to weblogic 10.3.4

I get a war file which works fine on Tomcat.
I create a jdev project based on this war and deploy it as an EAR.
I create weblogic-application.xml for an EAR file and deploy it to weblogic 10.3.4 with EM extension. But I get errors as follow.
If I deploy this jar file to a weblogic without EM, SOA, or BAM extension, it works.
How to solve this problem?
java.lang.ClassCastException: cannot be cast to javax.servlet.Filter
at weblogic.servlet.internal.WebComponentContributor.createFilterInstance(WebComponentContributor.java:257)
at weblogic.servlet.internal.FilterManager.loadFilter(FilterManager.java:94)
at weblogic.servlet.internal.FilterManager.preloadFilters(FilterManager.java:59)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1876)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
--------------weblogic.xml--------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd" xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
<context-root>szmap</context-root>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
-------------------weblogic-application.xml------------------------
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-application http://www.bea.com/ns/weblogic/weblogic-application/1.0/weblogic-application.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-application">
<application-param>
<param-name>webapp.encoding.default</param-name>
<param-value>UTF-8</param-value>
</application-param>
<prefer-application-packages>

<package-name>com.gxjh</package-name>
<package-name>com.gxjh.*</package-name>
<package-name>com.oracle.xmlns.adf.svc.errors.*</package-name>
<package-name>com.oracle.xmlns.adf.svc.errors</package-name>
<package-name>com.oracle.xmlns.adf.svc.types</package-name>
<package-name>com.oracle.xmlns.adf.svc.types.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.am.common.types</package-name>
<package-name>com.sunz.gxjh.model.catalog.am.common.types.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.query.common</package-name>
<package-name>com.sunz.gxjh.model.catalog.query.common.*</package-name>
<package-name>com.sunz.gxjh.model.catalog.vo.common</package-name>
<package-name>com.sunz.gxjh.model.catalog.vo.common.*</package-name>
<package-name>sdo.commonj</package-name>
<package-name>sdo.commonj.*</package-name>
<package-name>sdo.commonj.java</package-name>
<package-name>sdo.commonj.java.*</package-name>
<package-name>sdo.commonj.xml</package-name>
<package-name>sdo.commonj.xml.*</package-name>
</prefer-application-packages>
</weblogic-application>

Where can I know which jars are supported by weblogic (java EE)?
I redeploy the whole WAR file again. This time, I do not delete any jar file. I change the startWebLogic.cmd to
set CLASSPATH=D:\Oracle\Middleware\user_projects\domains\EMdomain_32JDK_20110330\servers\AdminServer\tmp\.appmergegen_1301556726222\szmap.war\fc240w\WEB-INF\lib\wsdl4j-1.6.2.jar;%SAVE_CLASSPATH%
I set <prefer-web-inf-classes>false</prefer-web-inf-classes>.
Then, after deploying WAR file, it works. It seems that wsdl4j.1.6.2.jar conflcts with weblogic.
If I set <prefer-web-inf-classes>true</prefer-web-inf-classes> and
<package-name>com.ibm.wsdl.*</package-name>
<package-name>com.ibm.wsdl.extensions.*</package-name>
<package-name>com.ibm.wsdl.extensions.http.*</package-name>
<package-name>com.ibm.wsdl.extensions.mime.*</package-name>
<package-name>com.ibm.wsdl.extensions.schema.*</package-name>
<package-name>com.ibm.wsdl.extensions.soap.*</package-name>
<package-name>com.ibm.wsdl.extensions.soap12.*</package-name>
<package-name>com.ibm.wsdl.factory.*</package-name>
<package-name>com.ibm.wsdl.util.*</package-name>
<package-name>com.ibm.wsdl.util.xml.*</package-name>
<package-name>com.ibm.wsdl.xml.*</package-name>
<package-name>javax.wsdl.*</package-name>
<package-name>javax.wsdl.extensions.*</package-name>
<package-name>javax.wsdl.extensions.http.*</package-name>
<package-name>javax.wsdl.extensions.mime.*</package-name>
<package-name>javax.wsdl.extensions.schema.*</package-name>
<package-name>javax.wsdl.extensions.soap.*</package-name>
<package-name>javax.wsdl.extensions.soap12.*</package-name>
<package-name>javax.wsdl.factory.*</package-name>
<package-name>javax.wsdl.xml.*</package-name>
Then, I change the weblogic.cmd to set CLASSPATH=SAVE_CLASSPATH%. After deploying the EAR file, it does not wok.

Deployment issue in weblogic 10.3

Hi,
I am facing the below error when am trying to deploy the ear on my weblogic server in Linux Env. I have gone through the posts here for similar problem and tried all the suggestions with no results. Tries changing the permissions on _WL_TEMP_APP_DOWNLOADS folder on admin server too. Please inform if you people have any idea on this.
java.io.IOException: [DeploymentService:290066]Error occurred while downloading files from admin server for deployment request "1,374,489,582,513". Underlying error is: "null"
        at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:86)
        at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
        at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
        at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
        at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:97)
        at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:682)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepareDataUpdate(AbstractOperation.java:890)
        at weblogic.deploy.internal.targetserver.operations.AbstractOperation.stageFilesFromAdminServer(AbstractOperation.java:264)
        at weblogic.deploy.internal.targetserver.DeploymentManager.createOperations(DeploymentManager.java:1375)
        at weblogic.deploy.internal.targetserver.DeploymentManager.handleUpdateDeploymentContext(DeploymentManager.java:160)
        at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.updateDeploymentContext(DeploymentServiceDispatcher.java:155)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doUpdateDeploymentContextCallback(DeploymentReceiverCallbackDeliverer.java:133)
        at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.updateDeploymentContext(DeploymentReceiverCallbackDeliverer.java:27)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.callDeploymentReceivers(ReceivedPrepare.java:203)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.handlePrepare(ReceivedPrepare.java:112)
        at weblogic.deploy.service.internal.statemachines.targetserver.ReceivedPrepare.receivedPrepare(ReceivedPrepare.java:52)
        at weblogic.deploy.service.internal.targetserver.TargetRequestImpl.run(TargetRequestImpl.java:211)
        at weblogic.deploy.service.internal.transport.CommonMessageReceiver$1.run(CommonMessageReceiver.java:410)
        at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I am deploying the application with Deployer utility as below:
java weblogic.Deployer -adminurl t3://localhost:8001 -username weblogic1 -password weblogic1 -targets my_Server -verbose -debug -deploy /var/app/weblogic/user_projects/domains/myDomain/myapp.ear
All advices and pointer are hearty welcome..
Thanks in advance...

We are working on Solaris server and i checked , it looks like we do not have any HIPS services running there.. i got the below output:
bash-3.00$ svcs HIPS
svcs: Pattern 'HIPS' doesn't match any instances
STATE          STIME    FMRI
bash-3.00$ svcs hips
svcs: Pattern 'hips' doesn't match any instances
STATE          STIME    FMRI
Thanks..

Deploying mdb in weblogic 9.0

Similar Messages

Maybe you are looking for