Deploy Hibernate (v 3.6) on Weblogic 11gR1 (patch set 2)

Hello,
Facing issues in deploying hibernate JPA 2.0 project on Weblogic server 10.3.3
The error message being:
Module named 'EJB605EAR' failed to redeploy. See Error Log view for more detail.
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
Exception received from deployment driver.
Entries for persistence.xml and weblogic-application.xml are as below.
I know weblogic doesn't support JPA2.0 out of the box. How to make it work?
Thank you for your help and consideration.
Hiren
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
 <persistence-unit name="ejb605" transaction-type="JTA">
 <provider>org.hibernate.ejb.HibernatePersistence</provider>
 <jta-data-source>jdbc/EJB605DS</jta-data-source>
 <properties>
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.format_sql" value="true" />
 <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
</properties>
 </persistence-unit>
</persistence>
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.1/weblogic-application.xsd">

<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:prefer-application-packages>
 <wls:package-name>javax.persistence.*</wls:package-name>
</wls:prefer-application-packages>
</wls:weblogic-application>

Hiren,
Hi, you will be interested in this recent thread that discusses JPA 2.0 providers (Hibernate and EclipseLink) in the context of Oracle WebLogic Server 11gR1 10.3.4 (ps3)
Re: Deploy Hibernate based EAR file on Weblogic 10.3.3?
thank you
/Michael O'Brien
http://www.eclipselink.org

Similar Messages

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

How to create and deploy a simple jstl applicaton in weblogic 10.3.3

1) Since JSTL libraries are provided as Web application libraries, they must be deployed before the Web application that is using JSTL functionality is deployed. The libraries can be deployed using the Administration Console or with the command-line weblogic.Deployer tool.
Here’s an example of deploying a JSTL 1.2 library using the weblogic.Deployer command-line:
java weblogic.Deployer -adminurl t3://localhost:7001
-user weblogic -password weblogic
-deploy -library
d:/beahome/wlserver_10.3/common/deployable-libraries/jstl-1.2.war
This command deploys the JSTL 1.2 library using the default library-name, specification-version and implementation-version defined by the MANIFEST.MF in the library.
After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console. This information can also be found in the MANIFEST.MF file of the library WAR file.
For more information on deploying a Web module refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/deployment/deployunits.html
2) To reference a JSF or JSTL library, a standard web application can define a <library-ref> descriptor in the application’s weblogic.xml file. Here is an example:
<library-ref>
<library-name>jsf</library-name>
<specification-version>1.2</specification-version>
<implementation-version>1.2.0</implementation-version>
<exact-match>false</exact-match>
</library-ref>
For more information on referencing a Web application library refer below URL
http://docs.oracle.com/cd/E15051_01/wls/docs103/programming/libraries.html
3) Create a sample JSP in your application and JSP should look as shown below
<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<html>
<head>
<title>TestJSTL</title>
</head>
<body>
<c:set var="topic" value="JSTL" />
<c:out value="${topic}" />
</body>
</html>
4) Create WAR and deploy and test.
Edited by: Murali Veligeti on Jul 26, 2012 9:00 AM

How to deploy a JSR-168 Portlet in Weblogic?

I am running WLS 8.1 with the advanced JSR-168 support installed (not yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168 reference
implementation (pluto). Can someone please point me to the instructions on how
to now import my portlet war into Workshop so that I can add it to my Weblogic
portal?
Thanks!
-David

You cannot simply "deploy" a JSR 168 portlet into Weblogic using a WAR file in
my experience. This is what I did to achieve deployment of a JSR 168 portlet in
BEA WLS 8.1SP2:
* File | New | Portlet | Java Portlet
* Just type in the name of your view class name when asked for it.
This creates a "YourAppName.portlet" file, which I believe Bea requires for any
Portlet in order to make it available for use in their portals.
* Add your files (*.jar, *.java *.jsp, etc).
* Modify WEB-INF/portlet.xml to include all required descriptor elements that
you have in your WAR file (keep in mind that there is only one portlet.xml for
all portlets in a single web application)
I was unable to use redirects for some reason, but it worked fine with include.
"David" <[email protected]> wrote:
>
I am running WLS 8.1 with the advanced JSR-168 support installed (not
yet running
SP2). I have a JSR-168 portlet war that I had been testing in the JSR-168
reference
implementation (pluto). Can someone please point me to the instructions
on how
to now import my portlet war into Workshop so that I can add it to my
Weblogic
portal?
Thanks!
-David

Installing WebLogic 11gR1 zip distro on Ubuntu 10.10

Hi. I'm having a problem installing WebLogic 11gR1, the zip distribution of Ubuntu 10.10.
I created this path:
/usr/local/programs/WebLogic11gR1
I put this in .bashrc
export MW_HOME=/usr/local/programs/WebLogic11gR1
I closed that terminal and opened a fresh terminal.
I moved the *zip distribution into
/usr/local/programs/WebLogic11gR1
I unpacked the zip and tried to run the configure.sh script with variations of
sh ./configure.sh
and I get this error message:
=====================================================
./configure.sh: 19: [[: not found
./configure.sh: 19: -d: not found
ERROR: You must set MW_HOME and it must point to a directory.
where an installation of WebLogic exists. Ensure you point
this variable to the extract location of the zip distribution.
=====================================================
I ran echo $MW_HOME and got
/usr/local/programs/WebLogic11gR1
Which is correct.
Any ideas what is going on and how I can fix it?

the config.sh wouldn't pick up my JAVA_HOME either. I opened up the script and found that all it did was call another script, so I ran that script myself with no problems.

Weblogic deployment plan will not override variables (Weblogic 10.3.5).

I am having some trouble trying to adjust the deployment settings of our application in weblogic. I feel what I'm trying to do ought to be quite simple, but it's not working as expected.
I am just trying to override the context-root in weblogic.xml and the JNDI name for the data source, so these can both be configured at deployment time.
I have removed the application.xml from the ear file, so that shouldn't be affecting the overrides.
What I have so far:
weblogic.xml:
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
<context-root>mosaic</context-root>
<resource-description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<jndi-name>LogicalDS</jndi-name>
</resource-description>
web.xml
<?xml version='1.0' encoding='UTF-8'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<resource-ref>
<description>A logical reference to the datasource - mapped in deployment plan</description>
<res-ref-name>jdbc/LogicalDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
plan.xml
<?xml version="1.0" encoding="UTF-8"?>
<wls:deployment-plan xmlns:wls="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/j2ee_1_4.xsd" global-variables="true">

<wls:application-name>mosaic.ear</wls:application-name>
<wls:variable-definition>
<wls:variable>
<wls:name>datasource_name</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>The name of the datasource to map to the mosaic application</wls:description>
</wls:variable>
<wls:variable>
<wls:name>new_context_root</wls:name>
<wls:value xsi:nil="true"></wls:value>
<wls:description>URL to deploy Mosaic at</wls:description>
</wls:variable>
</wls:variable-definition>
<wls:module-override>
<wls:module-name>mosaic.war</wls:module-name>
<wls:module-type>war</wls:module-type>
<wls:module-descriptor>
<wls:root-element>weblogic-web-app</wls:root-element>
<wls:uri>WEB-INF/weblogic.xml</wls:uri>
<wls:variable-assignment>
<wls:name>new_context_root</wls:name>
<wls:xpath>/weblogic-web-app/context-root</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:description>Data source for mosaic application</wls:description>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-env-description/resource-env-ref-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
<wls:variable-assignment>
<wls:name>datasource_name</wls:name>
<wls:xpath>/weblogic-web-app/resource-description/[res-ref-name="jdbc/LogicalDS"]/jndi-name</wls:xpath>
<wls:operation>replace</wls:operation>
</wls:variable-assignment>
</wls:module-descriptor>
</wls:module-override>
</wls:deployment-plan>
Nothing happens when I use the deployment plan, and neither of the variables appear under the Deployment Plan configuration screens in the admin console. From what I understand, I should at least be asked for these variables, since I have specified that they are null in the deployment plan.
When I use WLST to browse the tree, I find that the runtime configuration just stays as the values in the deployment descriptors.
I have verified the deployment plan is being used in the general tab of the admin console.
Can anyone help me find out what I am doing wrong here? If I don't create a data source called LogicalDS, I get errors about this, suggesting it is not correctly overriding. I am puzzled to why I do not see any variables to specify though..

The documentation implies that this is not the case - see:
http://docs.oracle.com/cd/E24329_01/web.1211/e24443/export.htm#autoId13
'Assigning Null Variables to Require Administrator Input'.
However, require administrator input where? My thoughts were that this option would appear in the admin console under 'deployment plan'. However, although I have specified resource dependencies in the deployment descriptors, and the plan, nothing appears under 'resource dependencies' for the application.
Is the only way to change the context-root deployment URL by actually manually editing an XML file?
To me that seems primitive and will cause us support issues when distributing our application - is there any other way I can enable the ability to specify the data source name and context-root through the web console prior to/during deployment?
Edited by: user12032953 on 11-Jun-2012 07:20

How to upload and deploy an EAR to a remote weblogic domain

I can use ant to deploy EAR file to local weblogic. How to deploy ear files to a remote weblogic?

can you give me configuration details how you are deploying EAR remotely...

Deploying Java stand alone application in Weblogic server

Hi All,
We have an java stand alone application which our client uses. Suddenly they came up with a requirement of using this application from web logic server.We have following directory structure for our application
myapp
- config -> contains all configuration files
- logs -> contains log files
- ssl -> ssl related files
- samples ->contians stub's
- myapp.jar
How to deploy our standalone application in to weblogic server?.
We tried putting whole myapp folder in WEB-INF folder , and from the servlet we are able to invoke an method in an class file( in myapp.jar say Test.getInstance()) but it couldnt find configuration files (in config folder ) and it is throwing an error. We have a class called Test in myapp.jar and when we call getInstance of the class it loads all config files - config file location is hardcoded as /config/myconfig.xml , and we are facing problem here because it couldnt find myconfig.xml.
We also tried packaging whole myapp folder in to jar , but with that also we faced the same problem
Please let us know are we proceeding in the right way and how to deploy our application in weblogic server.We dont prefer making changes to our code at this point of time.
Any info on this will be very helpful to us.
Regards,
Suresh

Hi René van Wijk,
Thanks for quick reply. Link you mentioned gave a basic idea of application structure , but still i couldnt get deployment process.
Am very much new to weblogic.Can you please let me know how to deploy our standalone application in to weblogic, with out making any changes to the code.
Below is folder structure of my java stand alone application *( not webapplication)*
myapp
- config -> contains all configuration files , for ex:- myconfig.xml
- logs -> contains log files
- ssl -> ssl related files
- samples ->contians stub's
- myapp.jar
We have logic to load configuration file (config/myconfig.xml) , in an class and we are not allowed to make any changes to this code, so we cant use Thread.currentThread().getContextClassLoader().getResource(...) .
Regards,
Suresh

Error deploying WebCenter Collaboration 10.3 on WebLogic Server

when i deploy webcenter collaboration 10.3 on WebLogic Server in a Suse Linux was failed with this error
[HTTP:101216]Servlet: "cnscallback" failed to preload on startup in Web application: "/collab". java.lang.NullPointerException at com.plumtree.core.util.SpringPropertyConfigurator.resolvePlaceholder(SpringPropertyConfigurator.java:66) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.resolvePlaceholder(PropertyPlaceholderConfigurer.java:336) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer.parseStringValue(PropertyPlaceholderConfigurer.java:286) at org.springframework.beans.factory.config.PropertyPlaceholderConfigurer$PlaceholderResolvingBeanDefinitionVisitor.resolveStringValue(PropertyPlaceholderConfigurer.java:401) at org.springframework.beans.factory.config.BeanDefinitionVisitor.resolveValue(BeanDefinitionVisitor.java:150) at org.springframework.b10.3
any idea please
thanks
i follow all the instruccion of the installation pdf

Regarding this error..... "cnscallback" failed to preload on startup in Web application: "/collab".
CNS stands for common notification service.
Was notification installed, is it up and running, and is collab properly pointing to it?
Just a guess, but it could be collab requires this to be able to start properly.

BOXI R2 deployment of webcompadapter.war failed on WebLogic 8.1 SP6

I'm trying to deploy BOXI r2 SP1 over WebLogic 8.1 SP6.
other .war files get deployed very easily. but webcompadapter.war deployment gives an error.
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0 Module: webcompadapter Error: [HTTP:101179][HTTP] Error occurred while parsing descriptor in Web application "C:\bea\user_projects\domains\bobj\myserver\upload\webcompadapter.war" [Path="C:\bea\user_projects\domains\bobj\myserver\upload", URI="webcompadapter.war" org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.apache.xerces.parsers.DOMParser.parse(DOMParser.java:271) at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201) at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:700) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) --------------- nested within: ------------------ Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:705) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.apache.xerces.parsers.DOMParser.parse(DOMParser.java:271) at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:201) at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:700) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) --------------- nested within: ------------------ Received SAXParseException from Sun Parser at line 69, column 48: org.xml.sax.SAXParseException: Element type "version" must be followed by either attribute specifications, ">" or "/>". at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:705) at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:716) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:295) at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:235) at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:525) at weblogic.j2ee.J2EEApplicationContainer.loadDescriptors(J2EEApplicationContainer.java:1414) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1239) at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1076) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2531) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2481) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2397) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:884) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:592) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:501) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
[Deployer:149033]preparing application webcompadapter on myserver
[Deployer:149033]failed application webcompadapter on myserver
[Deployer:149034]An exception occurred for task [Deployer:149026]
Does anybody has the solution for this?
Thanks in advance.

dkarr, Thanks for your reply. 
here is the constructor I got for the class 'com.corizon.ps.oneview.servlet.OneViewWritebackResultServlet'
 
 public OneViewWritebackResultServlet() 
{ 
senderThread = null; 
jmsConnectionHandler = null; 
closureManager = null; 
mRequestSenderThread = null; 
connected = false; 
} 
 
Is this ok ?
 
Thanks, 
-Ninad

WebLogic 11gR1: Where can I find the docs and the examples

I just installed the Zip Distribution of WebLogic 11gR1 on Ubuntu 10.10. I also installed the supplemental zip, that contained samples.
On the WebLogic 9 installation on a windows box at work, starting up WebLogic causes it to bring up a browser with a web page with very nice documentation on it, including hyperlinks to the examples. How do I find this page with my at home ZIp Distribution?

The README that accompanies the WLS supplemental zip file describes how to create the samples:
http://download.oracle.com/auth/otn/nt/middleware/11g/wls/README_SUPP.txt?e=1311046330&h=9c8a6b93b066372a53ca5d65bafcb9a5
>
WLS Supplemental Zip Distribution for Oracle WebLogic Server @WLS_VERSION@
The WLS supplemental zip distribution is intended for development use. It is
supported on Windows, Linux and Mac OS X systems. It contains the necessary
artifacts to develop and test applications on WebLogic Server.
WLS supplemental zip requires that the primary zip distribution is already set
up and is ready to use. Supplemental zip contains samples, evaluation database
(Derby) and L10N console help files.
The following instructions should help in quickly setting up the extra
components in WLS via the supplemental zip. Please refer to the general WLS
documentation for detailed instructions.
QUICKSTART
1. Ensure that WLS has been installed under MW_HOME (eg: /home/myhome/mywls)
using the zip distribution - wls@WLS_VERSION@_dev.zip
2. Extract the contents of the supplemental zip MW_HOME
3. Setup JAVA_HOME and MW_HOME variables in the current shell.
This should pre-exist.
Linux
$ export JAVA_HOME=/home/myhome/myjavahome
$ export MW_HOME=/home/myhome/mywls
Mac
$ export JAVA_HOME=
/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home
$ export MW_HOME=/home/myhome/mywls
Windows
> set JAVA_HOME=C:\home\myhome\myjavahome
> set MW_HOME=C:\home\myhome\mywls
This version of WLS requires JDK 1.6. Ensure that you have the proper
JDK version installed.
4. Run the installation configuration script in the MW_HOME directory
(This step is required to be run only once. If you move the installation to
another location/machine, you need to rerun this step)
Linux/Mac
*$ ./run_samples.sh*
Windows
> run_samples.cmd
This step creates the sample domains. The sample
domains should be created in MW_HOME/wlserver/samples.
5. WLS can be started from these sample domains by issuing startWebLogic command.
This will also bring up the WLS console in the default browser.
6. Start a browser and open up url - 'http://localhost:7001/console' to
administer the server.
WHAT IS INCLUDED
# Samples
# Derby DB (for use with Samples)
# L10N versions of WLS console help files
CLEANUP
The supplemental zip contents are interleaved with the base zip contents. You
have to delete the MW_HOME directory which will delete both the WLS
installation as well as the supplemental zip contents.

Exception when deploying a JSR 286 portlet into WebLogic+WebCenter

I get the following exception when deploying a JSR 286 portlet into WebLogic:
"<19-ene-2010 13H32' CET> <Error> <oracle.portlet.server.containerimpl.PortletApplicationImpl> <BEA-000000> <Error al procesar el archivo "/WEB-INF/portlet.xml" en la lÝnea 6 columna 68.
org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'portlet-app'"
The error message is in spanish. It means:
"Error processing the file "/WEB-INF/portlet.xml at line 6 column 68"
The portlet.xml of my portlet seems to be correct and I've deployed it in other portal servers. So I don't understand the error message.
This is the portlet.xml of my portlet (eclipse XML validator said it was a valid XML)
{code}
<?xml version="1.0" encoding="UTF-8"?>
<portlet-app version="2.0"
xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd
http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd"
xmlns:dnd="http://www.denodo.com/widget/portlet/portletjsr286">
<portlet>
<description>Test Inter Portlet Communication (JSR286)</description>
<portlet-name>Test IPC</portlet-name>
<display-name>Test IPC</display-name>
<portlet-class>com.denodo.ipc.TestIPCPortlet</portlet-class>
<supports>
<mime-type>text/html</mime-type>
<portlet-mode>VIEW</portlet-mode>
</supports>
<supported-locale>en</supported-locale>
<resource-bundle>PortletMessages</resource-bundle>
<portlet-info>
<title>Test IPC</title>
<short-title>Test IPC</short-title>
<keywords>Test IPC,Denodo</keywords>
</portlet-info>
</portlet>
</portlet-app>
{code}
*How do I deploy my portlet*
<li> I convert my portlet into to a WSRP portlet by executing
+java -jar wsrp-predeploy.jar source EAR target EAR+
as explained in http://download.oracle.com/docs/cd/E12839_01/webcenter.1111/e12405/wcadm_portlet_prod.htm#CHDECJHI)
</li>
<li>I try to deploy it into WebLogic with the WebLogic Console and I get this exception.
</li>
*My Environment*
WebCenter Suite (11.1.1.2.0) + WebLogic Server (10.3.2) downloaded from the oracle.com. Default configuration
S.O: Windows XP SP3
*Thanks in advance for your time.*

Hi,
Are you including the Toplink jars in your EAR?
-Patrick

How to use weblogic api to set jms server and presistance store target?

Hi all,
I can do the following from the weblogic admin console..
1) Can set jmsServer target as ejbserver to ejbserver (migratable)(Example: from ejbnode1 to ejbnode (migratable)
2) can set persistance store target as ejbserver to ejbserver (migratble)(Example: from ejbnode1 to ejbnode (migratable)
Now my question is, how can i use the weblogic api to set those things through the coding?
Pl anyone answer my qn.
Thanks in advance.
-Amal

The following is code which im using now,
Here I added jmsserver's targer as "ejbnode1" ok, How can change it to "ejbnode1 (migratable)". I can do this with admin console, but im not sure to do with api.
Help me to do this.
private void createJMSServer(Node node, String suffix) {
          try {
               ObjectName cfgManager = getConfigurationManager();
               ObjectName srvr = (ObjectName) mbeanServer.invoke(
                         domainConfig, "lookupJMSServer", new Object[] { node
                                   .getName()
                                   + suffix }, new String[] { "java.lang.String" });
               if (null == srvr) {
                    srvr = (ObjectName) mbeanServer.invoke(domainConfig,
                              "createJMSServer",new Object[] { node.getName() + suffix },
                              new String[] { "java.lang.String" });
               ObjectName targetSrvr = (ObjectName) mbeanServer.invoke(domainConfig,
                         "lookupServer", new Object[] { node.getTargetNode()},
                         new String[] { "java.lang.String" });
               mbeanServer.invoke(srvr, "addTarget",
                         new Object[] { targetSrvr },
                         new String[] { "javax.management.ObjectName" });
               saveAndActivateChanges(cfgManager);
               ClusterUtil.print("CL_106", "JMSClusterSetup.createJMSServer()",
                         new Object[] { node.getName() + suffix });
          } catch (Exception e) {
               ClusterUtil.throwEx("CL_3006", "JMSClusterSetup.createJMSServer()",
                         e, new Object[] { node.getName() });
     }

How to use weblogic.Admin to set JMS ErrorDestination property on WLS 7?

This thread is talking about using weblogic.Admin to set the ErrorDestination property.
 http://forums.bea.com/bea/thread.jspa?threadID=200036378&messageID=202187327&start=0
 We run the script against the WLS 7.0 server, script get 'OK' result but it didn't work (property wasn't set). Some error is reported in the admin.log on the server.
 We also run the scipt against the WLS 8 server. It worked perfectly.
 Does anyone know whether this works at all on WLS 7?

The reason we are using weblogic.Admin is that we are using conf2admin to generate the scripts. weblogic.Admin seems to be the only option for WLS7. Thanks for your suggestion and will definitely check out WLST.
 The full error message is:
 ####<Aug 27, 2004 8:55:20 AM NZST> <Emergency> <Management> <rbd1> <admin> <ExecuteThread: '9' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <> <141067> <The value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue specified for the ErrorDestination attribute is not valid. MBean: n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue. Method: setAttributes. Exception: javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
 Target exception: java.lang.NullPointerException
 .>
 javax.management.InvalidAttributeValueException: BeanShell Interpreter threw exception while evaluating (((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value)))) on value n204162:JMSServer=LAS2JMSServer,Name=FailedQueue,Type=JMSQueue, getLegalCheck() for attribute ErrorDestination of MBean "n204162:JMSServer=LAS2JMSServer,Name=FundingQueue,Type=JMSQueue", Sourced file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : Method Invocation weblogic.management.configuration.JMSLegalHelper.legalErrorDestination : at Line: 1 : in file: <Inline eval of: ((value == void)?(true):(weblogic.management.configuration.JMSLegalHelper.legalErrorDestination(self, value))); > : weblogic .management .configuration .JMSLegalHelper .legalErrorDestination ( self , value )
 Target exception: java.lang.NullPointerException
 at weblogic.management.internal.DynamicMBeanImpl.checkAttributeValueIsLegal(DynamicMBeanImpl.java:1517)
 at weblogic.management.internal.DynamicMBeanImpl.prepareForModification(DynamicMBeanImpl.java:1440)
 at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1004)
 at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:353)
 at weblogic.management.internal.DynamicMBeanImpl.setAttributes(DynamicMBeanImpl.java:827)
 at com.sun.management.jmx.MBeanServerImpl.setAttributes(MBeanServerImpl.java:1475)
 at weblogic.management.internal.RemoteMBeanServerImpl.setAttributes(RemoteMBeanServerImpl.java:905)
 at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
 at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
 at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
 at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:785)
 at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
 at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)

FMw 11gR1 Patch 6 Released (11.1.1.7)

For anyone that didn't notice the Annoucement above, FMw 11gR1 Patch 6 (11.1.1.7) has been released. Details in the announcement:
https://forums.oracle.com/forums/ann.jspa?annID=2062

Welcome to the forums !
user4916474 wrote:
Is 11.1.0.6 to 11.1.0.7 a major upgrade or just some bug fixes? someone told me that with 11.1.0.6 is not a Oracle 11g database but 10g database. Is this true? Also is 11.1.0.7 works with Win2003 server?11.1.0.6 to 11.1.0.7 is mostly bug fixes. 11.1.0.6 is not 10g, it is 11gR1. 11.1.0.7 is supported/certified on Win 2003
http://download.oracle.com/docs/cd/B28359_01/install.111/b32006/reqs.htm#CHDHGGFE
MOS Doc 601739.1 - 11.1.0.7 Patch Set - List of Bug Fixes by Problem Type
MOS Doc 756494.1 - Changes introduced in 11.1.0.7 Patchset
HTH
Srini

Problems deploying Spring 2.0.8 and Hibernate 3 web application to Weblogic 10.3.6

My application deploys but when it's accessed this (below) exception is thrown. It appears that it has a problem with my weblogic.xml file. This application was previously deployed on OC4J .
Here's my weblogic.xml. I added the xsd to the classpath /WEB-INF/classes dir thinking that maybe the server can access it's http location. There are no reference to this particualr error on the web (WlsScaSpringNamespaceHandler)
Weblogic.xml
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-web-app
 xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-web-app classpath:weblogic-web-app.xsd
 http://java.sun.com/xml/ns/javaee classpath:web-app_2_4.xsd ">
 <weblogic-version>10.3.6</weblogic-version>
 <description>ChargeCodeDeploymentDescriptor
 </description>
 <context-root>chargecode</context-root>
 <container-descriptor>
 <prefer-web-inf-classes>true</prefer-web-inf-classes>
 </container-descriptor>
</weblogic-web-app>
####<Mar 12, 2015 2:49:09 PM CDT> <Debug> <ServerMigration> <soatest1.cjis.iowa.gov> <WLS_SOA1> <[ACTIVE] ExecuteThread: '2' for q
ueue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0e5d06449b77071c:-70c3a57a:14c0ab4e30e:-8000-0000000000017c8b> <
1426189749780> <BEA-000000> <Query: UPDATE ACTIVE SET TIMEOUT = ( (SYSDATE + (30/86400))) WHERE SERVER IN ('wlsserver.WLS_SOA1') A
ND INSTANCE ='2344369727401629039/WLS_SOA1' AND DOMAINNAME='cjis_test_soa_domain' AND CLUSTERNAME='SOA_Cluster'>
####<Mar 12, 2015 2:49:09 PM CDT> <Debug> <ServerMigration> <soatest1.cjis.iowa.gov> <WLS_SOA1> <[ACTIVE] ExecuteThread: '0' for q
ueue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0e5d06449b77071c:-70c3a57a:14c0ab4e30e:-8000-0000000000017c8d> <
1426189749788> <BEA-000000> <Query: UPDATE ACTIVE SET TIMEOUT = ( (SYSDATE + (30/86400))) WHERE SERVER IN ('wlsserver.WLS_SOA1') A
ND INSTANCE ='2344369727401629039/WLS_SOA1' AND DOMAINNAME='cjis_test_soa_domain' AND CLUSTERNAME='SOA_Cluster'>
####<Mar 12, 2015 2:49:18 PM CDT> <Error> <ServletContext-/chargecode> <soatest1.cjis.iowa.gov> <WLS_SOA1> <[ACTIVE] ExecuteThread
: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <D2gim1K2000000000> <1426189758384> <BEA-000000> <Excep
tion while dispatching incoming RPC call
com.google.gwt.user.server.rpc.UnexpectedException: Service method 'public abstract gov.iowa.dhr.cjis.cca.client.domain.User gov.i
owa.dhr.cjis.cca.client.ChargeCodeAdministrationService.authenticateUser(java.lang.String,java.lang.String) throws gov.iowa.dhr.cj
is.cca.client.InvalidLoginException' threw an unexpected exception: org.springframework.beans.factory.BeanDefinitionStoreException
: Unexpected exception parsing XML document from class path resource [applicationContext.xml]; nested exception is java.lang.Illeg
alArgumentException: Class [weblogic.sca.engine.parse.WlsScaSpringNamespaceHandler] does not implement the NamespaceHandler interf
ace
 at com.google.gwt.user.server.rpc.RPC.encodeResponseForFailure(RPC.java:360)
 at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:546)
 at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:164)
 at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost(RemoteServiceServlet.java:86)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from class pa
th resource [applicationContext.xml]; nested exception is java.lang.IllegalArgumentException: Class [weblogic.sca.engine.parse.Wls
ScaSpringNamespaceHandler] does not implement the NamespaceHandler interface

Hi, Graeme.
Seems there is an existing CR on something related from v10.0: CR353213
* WLS 10.0 - EJB 3.0 deployment fails when parsing class for Stateless annotation
According to http://edocs.bea.com/wls/docs103/issues/known_resolved.html, this is not addressed in 10.3
Closely review your classpath, and then (assuming you have access to the source) review the body of your ejb. If it is related to this CR, you may be able to workaround the issue by shortening the body and split large methods into more sub-methods.
I hope this helps,
-Adrian

Deploy Hibernate (v 3.6) on Weblogic 11gR1 (patch set 2)

Similar Messages

Maybe you are looking for