Jprofiler with Weblogic Issue

Hi,
I am new to JProfiler. I want to profile my code (.jar) which sits inside a war file. So I added classpath to my jar and filter to only classes in my jar in JProfiler. I have war application deployed in weblogic ManagedServer and I am starting startWebLogic_jprofiler.cmd (AdminServer) from JProfiler. After that I am starting NodeManager and ManagedServer.
But in Jprofiler 'MemoryViews' section I am not able to see my required classes when I run my application. Is it possible to profile the code in ManagedServer or Do I need to deploy my war in AdminServer itself ? or anything missing here.
Please help me regarding this. Thanks in Advance.
-cdhar

I'm having the same problem, and I'm curious how did you resolved your problem.
Thanks in advanced!

Similar Messages

JSTL 1.1 issue with Weblogic 9.2

I am having tough time to make JSTL 1.1 work with Weblogic 9.2.Here the issue goes
When i user JSTL core tags like out,forEach weblogic is unable to understand the EL and throwing a compile time exception saying can't read request time values.
However the same page worked fine when i rolled back to JSTL 1.0 and weblogic 8.1.
I couldnt able to understand why JSTL 1.1 is not working in Weblogic 9.2.I assume weblogic 9.2 comes with servlet 2.4 and JSP 1.2.So JSTL 1.2 should work fine.
Am i ignoring anything involved with new JSP specs and JSTL
OR
Is this a bug with Weblogic 9.2 ?
Any comments highly appreciated.
Thanks,
Mallik

hey check the servlet spec version you're using in your web.xml. I think you want 2.3 not 2.4.

Issue with Weblogic services in Linux OBIEE 11G

Hello All,
I have a OBI 11G set up on a linux OS.I am facing a issue with weblogic service.
Whenever I am trying to start the Admin server from command line using its .sh , it is starting successfully.
But whenever I am closing that Linux session or coming out of the Admin server log , this service is getting stopped on its own.
OBI is working perfectly when that Linux session and Admin server log is intact, but as soon as i close either of them Admin server shut itself down.
Please any help on this will be appreciated.
Thanks,
Bhavnesh

Hi Bhavnesh.
Try this way and let me know the outcome.
nohup ./startWeblogic.sh -Dweblogic.management.username=Username -Dweblogic.management.password=password & tail -f nohup.out
Mark if helps,
Thanks,

Any issues using Apache's SOAP version 2 with Weblogic

Hi,
The Weblogic sever is not one in the list of servers that have been tried
succesfully with Apache's SOAP. This is the list:
Apache Tomcat v3.1
IBM WebSphere v3.02
JRun vx.y.z
Microsoft Internet Information Server
Has anyone tried SOAP with Weblogic?
A recent thread mentions some problems (and solutions) with Weblogic and Xerces 1.1.2.
SOAP requires Xerces 1.1.3. Therefore, I would also like to know if there is any issue
using Weblogic with Xerces 1.1.3. I am using Weblogic 4.5 but I would try 5.1 if necessary
for this.
Thanks in advance,
Javier

In the apache soap binary download, there is a soap web application ( in the
form of an exploded war file ). Just copy and paste this directory in the
domain's "applications" directory. You will need to add a servlet-mapping
element in the web.xml file, which could be something like this
<servlet-mapping>
<servlet-name>rpcrouter</servlet-name>
<url-pattern>/rpcrouter/*</url-pattern>
</servlet-mapping>
Cheers
Sandeep
"Jan-Paul" <[email protected]> wrote in message
news:[email protected]...
Do you have something similar for the BEA Weblogic 6.0?
"Sudhir Kolli" <[email protected]> wrote in message
news:[email protected]...
You might want to take look at this:
David Jian <[email protected]> wrote in message
news:[email protected]...
Gavin:
I did the same thing except for servlet register. soap is webapp to WLS,so
I add:
weblogic.httpd.webApp.soap=D:/foo/soap-2_0/webapps/soap
to weblogic.properties. Because sopa20 has a web.xml file in
/foo/soap-2_0/webapp/soap/web-inf, I can only edit it to registerrpcrouter
and keep the default webapp as the same. Otherwise, how do you add thesoap
to you myserver/public_html? Unfortunately, it does not recognize the
URL
when I click the Visit link on soap admin page.
I edit my web.xml as
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
"http://java.sun.com/j2ee/dtds/web-app_2.2.dtd">
<web-app>
<servlet>
<servlet-name>
rpcrouter
</servlet-name>
<servlet-class>
org.apache.soap.server.http.RPCRouterServlet
</servlet-class>
<init-param>
<param-name>ServicesStore</param-name>
<param-value>DeployedServices.ds</param-value>
</init-param>
</servlet>
</web-app>
Can you try this? How did you add your rpcrouter servlet to the defualt
webapp?
Thanks
DJ
"Gavin Hyde" <[email protected]> wrote in message
news:[email protected]...
After several painstaking hours I finally was able to get Apache Soap
v2.0
to work with weblogic. The version of weblogic I'm using is 4.51.
You
can
get Apaceh soap from http://www.apache.org/soap. This version of Soap
requires xerces v 1.2.1 which you can get from
http://www.apache.org/xerces-j. To make it work with weblogic you
have
to
first place the soap.jar file included with Apache soap and thexerces.jar
file in both the classpath AND WEBLOGIC_CLASSPATH. Don't ask me why
but
I
wasn't able to get it to work without it in both. Next you have to
add
the
directory that your class files reside in to the classpath. Next you
have
to register the RCPRouter servlet in weblogic. The line to do thislooks
like this:
weblogic.httpd.register.rpcrouter=org.apache.soap.server.http.RPCRouterServl
et
where rpcrouter can be any name you want to use to call the routerservlet.
That's all I had to do to set it up to view the stock quote example
and
the
address book. The calculator is giving me a few other probems at the
moment. Don't forget to deploy the different services but the command
for
that is given in the readme file for each example. For the router URL
I
used http://localhost:7001/rpcrouter which is that servlet you
registered
above.
Gavin
"Javier Deniz" <[email protected]> wrote in message
news:[email protected]...
Hi,
The Weblogic sever is not one in the list of servers that have been
tried
succesfully with Apache's SOAP. This is the list:
Apache Tomcat v3.1
IBM WebSphere v3.02
JRun vx.y.z
Microsoft Internet Information Server
Has anyone tried SOAP with Weblogic?
A recent thread mentions some problems (and solutions) with Weblogic
and
Xerces 1.1.2.
SOAP requires Xerces 1.1.3. Therefore, I would also like to know if
there
is any issue
using Weblogic with Xerces 1.1.3. I am using Weblogic 4.5 but I
would
try
5.1 if necessary
for this.
Thanks in advance,
Javier

Issue with Weblogic character encoding

I have struts2 based web application which works fine with tomcat server but when i deployed the application to weblogic 10.3 server it is creating following issue-
1) when i enter data in application forms with £ (pound sign), £ gets converted to ?
My Jsp Page is using ISO-8859-1 charset. please look at the snapshot from jsp page.
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
I have debug the application and came to know that this data (£ sign) is converted to ? before being assigned to corresponding property in action class.
this seems to be issue with encoding of characters with weblogic server.
I have also tried to fix this issue by defining the charset in weblogic.xml file in my application as follows but it does'nt solve this issue. please see the snapshot from weblogic.xml file.
<wls:weblogic-version>10.3</wls:weblogic-version>
<wls:context-root>APMApplication</wls:context-root>
<wls:charset-params>
<wls:input-charset>
<wls:resource-path>/*</wls:resource-path>
<wls:java-charset-name>ISO-8859-1</wls:java-charset-name>
</wls:input-charset>
</wls:charset-params>
Please suggest some solution to fix this issue. thanking you in advance.

"I can not change the charset in jsp pages i.e i have to use ISO-8859-1 in my jsp page which is a must have requirment."
You are right here as the pound sign is not included in UTF-8 (did not know that sorry).
Could you try setting the page directive of the JSP to
<%@ page contentType="text/html;charset=ISO-8859-1" language="java" %>or when you are working with jspx
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" xmlns="http://www.w3.org/1999/xhtml" version="2.0">
<jsp:directive.page contentType="text/html;charset=ISO-8859-1"/>
</jsp:root>

Migration issues we are facing with Weblogic 10.3

Hi All,
We are migrating an enterprise application deployed in Weblogic 6.1 server to Weblogic 10.3 version.
All the EJBs are migrated to EJB 3.0 from EJB 2.0. When deploying the application, we were getting weblogic.utils.AssertionError detailing Class not found for an auto generated Skel class.
We created the auto generated class by calling wlappc task and bundled the same with the EJB jar. Now we are getting ClassFormatError. Please refer to the trace below.
com/myproj/intranet/solicitation/model/xxxfacility/XXXFacilityBean_rik2i_XXXFacilityBIImpl_WLSkel : invalid Code length at 72169
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
Truncated. see log file for complete stacktrace
java.lang.ClassFormatError: com/myproj/intranet/solicitation/model/xxxfacility/XXXFacilityBean_rik2i_XXXFacilityBIImpl_WLSkel : invalid Code length at 72169
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
Does anybody suspect that the problem might be with the JRockit 1.6 (class size) that is bundled with Weblogic server 10.3?
We are struggling with this issue for quite sometime. Any help is highly appreciated. Thanks in advance.
Regards
Dhamo R

Hi Amy,
Thanks for the reply.
I am afraid that I may not be able to paste the code here, since the implementation bean class more than 7000 lines in length.
We have refactored the code and introduced a delegator layer and now it seems to be working fine. I believe the issue was with the code size as it was mentioned in one of the older post related to 10.1 version.
Thank you so much for your support.
Regards
Dhamo R

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

Issue while integrating external LDAP with weblogic

Hi,
i am trying integrating external LDAP (OpenLdap) with weblogic 10.3. I created a provider and provided required credentials and able to see users and group of the LDAP into the weblogic console. I am also able to login in the weblogic console with the users available in the LDAP after assigning the admin role to the ldap group. But i when i see the user's property (by clicking on the user in the admin console) it only shows the tabs for General, Password and Group only. on the other hand if i see the users from DefaultAuthenticator, it shows the Attribute tab apart from the General, Password and Group.
Can anyone let me knwo how can we get the Attribute tab for the Ldap users.
thx,
Ajay

Hi Ajay
By default Weblogic has READ ONLY adapters for any External Security Providers that are configured like any AD Providers. READ ONLY means, you can only read the data from the ldap but not modify it, hence may be its not showing the Attributes tag. For Default Authenticator, see the first paragraph note in Attributes tab, that says the same thing. NOW, may be WLS can atleast show Attributes in READ only format, but it needs some sort of mappings to be defined. Say on Weblogic side, we have like firstName, lastName which on any typical AD will be like sn (surname = lastname), givenname (firstname) etc etc. This mapping is tough to generalize.
One thing for sure is, from Weblogic you cannot modify or edit any attributes for any user in external AD. If you really want to get those attributes, you may need to use some javax.ldap apis or some 3rd party ready to use tools/apis. I remember Weblogic Portal has a facility to configure a xml file that defines attributes mapping and get all attributes for any user. But again thats in Weblogic Portal product and not part of weblogic server.
If you have any SOA Software, they have some utilities for the same.
Thanks
Ravi Jegga

EPMA 11.1.1.3 manual deployment issues with WEBLOGIC in EAS and WEBANALYSIS

Hi all,
As we are working on 64 bit machines, we have to deploy hyperion products manually with WEBLOGIC. other than EAS and WEBANALYSIS, all the products are working fine.
we have followed all the steps related to manual deployment. but still we r getting JAVA related error. so if anything else that we need to perform other than normal manual deployment steps, please let me know.
NOTE: EASDOCS, HBRLAUNCHER, are working but EAS is not been deployed.
Regards

Is your WebLogic 32-bit or 64-bit WebLogic? What specific O/S and version are you using? Some of the products make use of 32-bit native libraries's for JNDI and there are not 64-bit native libraries available unless you are using the AIX or Solaris Platform and even then not all products are supported for 64-bit.
If you were to use 11.1.2 it supports most of the product suite in 64-bit on most platforms.
Refer to support matrices at: http://www.oracle.com/technetwork/middleware/bi-foundation/hyperion-supported-platforms-085957.html
Regards,
John A. Booth
http://www.metavero.com

Security violation exception with Weblogic cluster installation on OIm 9.1

Hi,
I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
e, signature={}.
at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
riptor.java:486)
at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
:80)
at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
... 126 more
ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
Interface encounter some problems: {1}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.in
Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
Any suggestions would be useful...

No Response???
Where are the good guys??

Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

Hi Sudhir,
If you do not know if upgrade or not, have a look here :
http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
Note that at the end of June SP3 will be released...
Sergi
"Sudhir Babu" <[email protected]> wrote:
>
Hi Sergi,
Thanks a lot for the class file, I figured out what the problem was. Actually
the
database version I was working with was 8.0.6.0. The Oracle driver doesn't
work with
this but the JDriver worked. This is the output of running CheckDriver..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
Production
With the Partitioning and Objects options
PL/SQL Release 8.0.6.0.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.1.0
Then I tried on using the Oracle Driver on another instance which has the
version
8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
database.
The output of CheckDriver for this Oracle instance is..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.0.0
By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
I upgrade
Thanks once again,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir ,
JDriver works well, you can work with it.
Just for curiosity, can you run the class I attached using the "exact"classpath
of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
is the
output ?
On which platform are you running your WLSP2 ?
Thanks
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
I just checked the things you mentioned. The connection pool starts correctly
without
any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
I do have the JAVA_XA package installed and it has EXECUTE permission
to
PUBLIC.
I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
and
it works perfect without any issue. The only consideration is that itis
a Type 2
Driver and needs to have the Oracle Client installed. But right now Ido
have it
installed on the same machine.
Do you know any known issues with Weblogic JDriver. Do you think it'sa
good idea
to go with it ?
Thanks,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
does your connection pool start correctly ?
Check the setup of your Oracle server too:
1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
2) package JAVA_XA installed (with grant execute to PUBLIC)
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
and put
it in classpath in front of weblogic.jar. I still get the same problem.
Is there
another location where we can download the Oracle driver with the bug
fixed
Regards, Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
I think you are using Oracle JDBC drivers 8.1.6.
They have a bug, they do not accept a foreign XID.
Use 8.1.7 or higher to solve this problem.
Sergi
Sudhir Babu <[email protected]> wrote:
Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver.
These
are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I amnot
sure where the problem is as I have configured Connection Pool and
TXDataSource
as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured in the transaction branch start() failed on resource 'myXAPool'
Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Error invoking WebService in Eclipse with WebLogic 12c plugin

I am using Eclipse Indigo with WebLogic 12c plugin to create a standalone WebService Client which invokes a simple WebService. The WebService is protected by Security Policies Wssp1.2-2007-Wss1.0-X509-Basic256.xml and Wssp1.2-SignBody.xml.
I get the following exception when I run the standalone client:
h2. Exception in thread "main" java.util.ServiceConfigurationError: javax.xml.ws.spi.Provider: Provider weblogic.wsee.jaxws.spi.WLSProvider could not be instantiated: java.lang.ExceptionInInitializerError
The same program works fine using JDeveloper 11g but not in Eclipse Indigo or in Juno. Has anyone faced this issue?
Thanks,
Madhav

The stand-alone client JAR file does not, however, support invoking Web services that use the following advanced features:
Web services reliable SOAP messaging
Message-level security (WS-Security)
http://docs.oracle.com/cd/E14571_01/web.1111/e13760/client.htm#i229632
Can you try running by adding weblogic.jar. but if you run the client inside the wls Server it should work.
Regards,
Sunil P

Announcing: Developing JSF Portlets with WebLogic Portal Whitepaper

Just Released: Developing JSF Portlets with WebLogic Portal Whitepaper
A supplemental developer's guide has been published to help guide WLP 10.x customers that wish to use JSF as the web framework for building portlets on WebLogic Portal. This is a sizable document (150 pages) that covers a large number of topics. It also coaches developers on best practices and common pitfalls.
Important: It also clarifies the supported configuration of JSF within Portal Web Projects. Workshop for WebLogic by default configures a web project in a configuration that is not supported by WebLogic Portal. The guide explains how to address this:
* Change from the unsupported MyFaces JSF implementation to the supported Sun Reference Implementation (RI)
* Change from the unsupported "client" STATE_SAVING_METHOD to the supported "server"
The guide can be downloaded here:
http://download.oracle.com/technology/products/weblogic/portal/weblogic-portal-jsf-whitepaper.pdf
To help internet searches locate this document, the table of contents is reproduced below:
Introduction
1.1. Prerequisites...................................................................... 8
1.2. Applicable Versions............................................................ 8
1.3. Native Portlet Bridges and Standard Portlet Bridges .......... 8
1.4. JSF Portlet Support Roadmap ........................................... 9
1.5. Whitepaper Structure ....................................................... 10
1.6. Look Before You Leap ..................................................... 10
1.7. For More Information........................................................ 10
Part 1: Converting JSF Applications into Portlets
2. IDE Support for JSF Portlets Chapter ...................................... 12
2.1. Workshop for WebLogic – WebLogic Portal's Supported IDE 12
2.2. Workshop Features for JSF Support in WebLogic Portal.. 12
3. Introduction to JSF Portlets Chapter ........................................ 18
3.1. Creating Your First JSF Portlet......................................... 18
3.2. Essentials of JSF Portlet Views........................................ 21
3.3. WebLogic Portal Artifacts................................................. 22
4. Configuring JSF within WebLogic Portal Chapter..................... 24
4.1. JSF Library Modules in WebLogic Server ........................ 24
4.2. Installing the JSF Libraries into a Portal Web Project ....... 25
4.3. JSF Configuration Settings............................................... 27
4.4. Configuring JSF 1.2 ......................................................... 29
4.5. Building an Unsupported JSF Implementation Library Module 31
4.6. Faces Configuration is Web Application Scoped.............. 31
5. Navigation within a JSF Portlet Chapter................................... 33
5.1. Navigating within a Portlet with the JSF Controller ........... 33
5.2. Redirects.......................................................................... 34
6. Namespacing Chapter ............................................................. 35
6.1. Namespacing Managed Bean Names.............................. 35
6.2. Client ID Namespacing with the View and Subview Components 35
6.3. Client ID Namespacing with the WLP NamingContainer .. 36
7. Logging, Iterative Development, and Debugging Chapter ........ 39
7.1. Logging............................................................................ 39
7.2. Iterative Development ...................................................... 39
7.3. Debugging ....................................................................... 40
8. Custom JavaScript Chapter ..................................................... 42
8.1. DOM Manipulation within a JSF ....................................... 42
8.2. Form Validation within a JSF Portlet ................................ 45
9. Preparing JSF Portlets for Production Chapter ........................ 46
9.1. Configuration.................................................................... 46
9.2. Performance and Scalability............................................. 47
9.3. Security............................................................................ 49
9.4. Localization...................................................................... 50
Part 2: Interacting with the Portal Environment
10. Native Bridge Architecture Chapter ...................................... 54
10.1. Container Architecture Overview.................................. 54
10.2. Container Architecture.................................................. 54
10.3. Container Interactions .................................................. 55
11. Interportlet Communication Chapter .................................... 56
11.1. Using Session and Request Attributes for IPC (Anti-pattern) 56
11.2. Using the WLP Event Facility for IPC with JSF Portlets 56
11.3. Notifications ................................................................. 60
11.4. Comparison of the IPC Approaches ............................. 60
12. Scopes Chapter ................................................................... 62
12.1. Conceptual Scopes for Standard JSF Applications ...... 62
12.2. Conceptual Scopes for Portal Applications................... 63
12.3. Implementation Patterns for Portal Scopes .................. 63
13. State Sharing Patterns Chapter ........................................... 66
13.1. State Sharing Concepts ............................................... 66
13.2. HttpSession Versus HttpServletRequest ...................... 66
13.3. Base Code for HttpSession Patterns ............................ 67
13.4. Single Portlet Pattern ................................................... 68
13.5. Multiple Portlet Patterns ............................................... 69
14. Rendering Lifecycles Chapter .............................................. 77
14.1. WLP and JSF Lifecycles .............................................. 77
14.2. Invocation Order of WLP and JSF Lifecycle Methods... 77
14.3. Accessing WLP Context Objects from JSF Managed Beans 78
15. Portal Navigation Chapter .................................................... 80
15.1. Programmatically Constructing JSF Portlet URLs ........ 80
15.2. Changing the Active Portal Page.................................. 80
15.3. Redirects within a Portal............................................... 83
16. Ajax Enablement Chapter .................................................... 85
16.1. Ajax in JSF Portlets...................................................... 85
16.2. Partial Page Rendering Pattern.................................... 85
16.3. Stateless API Request Pattern ..................................... 86
16.4. Portlet Aware API Request Pattern .............................. 87
16.5. Controlling the WLP Ajax Framework........................... 91
17. Additional WLP Features Chapter........................................ 93
17.2. Portlet Container Features ........................................... 93
17.3. Portal Container Features ............................................ 98
18. Example: Implementing a Login Portlet Chapter .................. 99
18.1. Login Portlet Motivation................................................ 99
18.2. Login Portlet Design..................................................... 99
18.3. Login Portlet Implementation...................................... 101
Part 3: Integrating Third Party Libraries
19. Integration Overview Chapter............................................. 111
19.1. Types of Libraries....................................................... 111
19.2. Roadmap for MyFaces Trinidad and ADF Faces Rich Client 111
20. Using the Facelets View Technology Chapter.................... 113
20.1. Introduction to Facelets .............................................. 113
20.2. Configuring Facelets Support ..................................... 113
21. Using the Apache MyFaces Tomahawk Component Library Chapter 115
21.1. What is Apache MyFaces Tomahawk? ...................... 115
21.2. Support for Tomahawk in WLP................................... 115
21.3. Tomahawk Component List........................................ 116
21.4. Installing and Configuring Tomahawk......................... 119
21.5. Resolving the Duplicate ID Issue................................ 120
21.6. Referring to Resources .............................................. 120
21.7. forceId Attribute.......................................................... 124
21.8. File Upload................................................................. 125
22. Using the Apache Beehive Navigation Controller Chapter . 126
22.1. Apache Beehive Page Flow ....................................... 126
22.2. JSF and Page Flows .................................................. 126
22.3. Configuring the JSF Integration with Page Flows ....... 127
Appendices
23. Appendix 1: Consolidated List of Best Practices ................ 130
24. Appendix 2: Known Issues and Workarounds.................... 132
24.1. CR383659, CR383662 Inconsistent failures with JSF portlets 132
24.2. CR342124: IllegalStateException due to duplicate client-id 132
24.3. CR384916: IllegalStateException due to duplicate client-id when using certain components such as Tomahawk and Trinidad...... 133
24.4. CR361477 Problems with the integration of JSF portlets with Apache Beehive Page Flows.................................................................. 133
24.5. CR377945 JSF 1.2 suffers from a memory leak during iterative development .............................................................................. 134
25. Appendix 3: The JSFPortletHelper Class ........................... 135
26. Appendix 4: The CleanupPhaseListener Class .................. 147

Hi Peter!
First, I wish to thank you for the great work.
We followed your whitepaper and managed to deploy a JSF portlet on WLS.
But we are not able to register it (consume it) as remote portlet in Oracle Portal 10.1.4. The error log is as follows:
An error occurred while trying to refresh the provider. (WWC-43190)
An error occurred during the call to the WSRP Provider:
java.rmi.RemoteException: serialization error: serialization error:
unexpected null value for literal data; nested exception is:
serialization error: serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
serialization error: unexpected null value for literal data
com.sun.xml.rpc.encoding.SerializationException: serialization error:
unexpected null value for literal data
Java stack trace from root exception:
unexpected null value for literal data
at
oracle.webdb.wsrp.RegistrationContext_LiteralSerializer.doSerialize(RegistrationContext_LiteralSerializer.java:107)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
oracle.webdb.wsrp.GetServiceDescription_LiteralSerializer.doSerialize(GetServiceDescription_LiteralSerializer.java:88)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.internalSerialize(LiteralObjectSerializerBase.java:119)
at
com.sun.xml.rpc.encoding.literal.LiteralObjectSerializerBase.serialize(LiteralObjectSerializerBase.java:70)
at
com.sun.xml.rpc.client.StreamingSender._writeRequest(StreamingSender.java:473)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:62)
at
oracle.webdb.wsrp.WSRP_v1_ServiceDescription_PortType_Stub.getServiceDescription(WSRP_v1_ServiceDescription_PortType_Stub.java:63)
at
oracle.webdb.wsrp.client.design.v1.OraWSRP_v1_ServiceDescription_PortType.getServiceDescription(Unknown
Source)Do you have any idea why this happens? Or you can provide some useful links to WLP -Oracle Portal federation?
Thank you and best regards,
PaKo

Regarding weblogic issue

Hi,
I have a problem with weblogic 8.1 server.
when i am trying to insert the fileds in a form and when i give the "clearing date" value as a blank it is displaying the value as '1/1/1900' in jsp.
whereas in Websphere it is not showing.
Ideally it should not show.
Please help me to resolve this issue if there are any settings to be made.
Edited by: user12660326 on Feb 22, 2010 7:07 AM

This is not enough information to help you. Do you have any code snippets and an explanation of what the inputs/outputs are?

Jprofiler with Weblogic Issue

Similar Messages

Maybe you are looking for