WLS 10.3.6 Debug

If the DEBUG_PORT in setDomainEnv.cmd is 8473 or if I set the DEBUG_PORT variable to 8473 (in spite of what is in setDomainEnv.cmd) in the debug launch configuration of the WLS in OEPE, I see that the server is getting started accordingly.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8473,server=y,suspend=n
But I do not see a way for the client VM to connect to 8473; It is always trying to connect to 8453.
I am on Eclipse Juno 4.2 and using OEPE 12.1.1.2.0.
Is there a way to specify that the client VM need to connect to 8473 when I start the server with debugging on 8473?

Hi,
can you try this.
When the server is stopped
right click on the server entry in the server view
select properties - WebLogic - Server node
enter the new port number in the debug port field (default is 8453)
select your file and debug on server
this should cause the breakpoints to be hit.
cheers
Raj

Similar Messages

Enabling ALSB debug level logging

Within my proxy services I have added some DEBUG level log statements, however, these do not seem to get logged to either my standard out log or my application log. If I switch them to WARN or ERROR, I get them logged.
I verified in Operational Settings on my proxy service logging is enabled at level DEBUG or above.
I think something maybe within WLS itself might be preventing the logs. If within the WLS console I switch debug logging on for everything (Debug tab on the server screen), I do see my log statements, among other things. Unfortunately I cannot figure out which one of the hundred or so items actually enables the debug logging just for ALSB's debug statements.
Has anybody else figured out the right combination of things to get ALSB to log the proxy service debug statements?

Thanks. That was already enabled but checking it made me think of another thing. I have been watching the console you get when you start up your server from the automatically created shortcuts. Instead, I checked the actual log file for the server and the debug statements do in fact get written there. The console that comes up must be standard error, hence, only the warnings and errors.
Thanks for leading me to the answer.

Trouble with console-extension using struts portlet

hello everyone,
I'm developing a console-extension for wls9.2 but couldn't get is to work despite all the documentation available. The console-ext is a struts portlet which gathers data from custom mbeans via jmx and renders the result with a jsp. What already works is fetching the data from the MBeans in the struts action. What does not work is the display of the results in the admin console. So I removed all the stuff from the jsp to just display "Hello World" which should be displayed on the desktop in the admin console, but even this didn't work (it's just a blank spot). Having a look at the log file I get the following:
e.netui.pageflow.internal.AdapterManager ERROR ServletContainerAdapter manager not initialized correctly.
e.netui.pageflow.internal.AdapterManager INFO No ServletContainerAdapter specified or discovered; using class org.apache.beehive.netui.pageflow.DefaultServletContainerAdapter
tui.util.config.parser.NetUIConfigParser INFO NetUIConfigParser -- load config: /WEB-INF/beehive-netui-config.xml
e.netui.pageflow.internal.AdapterManager INFO No ServletContainerAdapter specified or discovered; using class org.apache.beehive.netui.pageflow.DefaultServletContainerAdapter
netui.pageflow.AutoRegisterActionServlet INFO Dynamically registering module /loggingController, config XML /WEB-INF/struts-auto-config-loggingController.xml
netui.pageflow.AutoRegisterActionServlet INFO Dynamically registering module /loggingController, config XML /WEB-INF/struts-auto-config-loggingController.xml
(...other debug output from my struts action...)
.wls.web.actions.LoggingControllerAction DEBUG Going to /ext_jsp/helloWorld.jsp using module null
flow.scoping.internal.ScopedResponseImpl INFO ScopedResponse error 404:
.netui.pageflow.PageFlowRequestProcessor WARN Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass". Page Flow actions in this module may not be handled correctly.
.netui.pageflow.PageFlowRequestProcessor INFO Attempting to instantiate SharedFlowControllers for request /console/ChangeManagerAction.do
ive.netui.pageflow.FlowControllerFactory INFO No Global.app was found in /console
Despite the errors it seems to find my struts config (struts-auto-config-loggingController.xm) and execute the action, but then it seems to have trouble findingd/displaying the jsp (helloWorld.jsp). I tried to set various controller-elements in the struts config, like this ([url http://edocs.bea.com/wlp/docs92/portals/integrate.html#wp1005659]source):
<controller inputForward="true" processorClass="com.bea.struts.adapter.action.AdapterRequestProcessor" />
but this didn't work either (and results in other errors). The log from above was created with a config without any controller element (since this is never mentioned in the eDocs for console extensions).
Despite spending several hours trying to figure out what goes wrong here I wasn't able to get one step closer to a solution. Does anyone have a clue what I did wrong (please ask if you need further information)? Thanks a lot!
Btw. Sorry if this is the wrong forum, I could't find another one which matches better. Feel free to move the topic to a more appropriate place. thx.
====================================
Struts config:
<struts-config>
     <form-beans>
          <form-bean name="loggingForm" type="...web.forms.LoggingControllerForm" />
     </form-beans>
     <action-mappings>
          <action path="/LoggingControllerAction"
               type="...web.actions.LoggingControllerAction"
               name="loggingForm"
               scope="request"
               validate="false"
               input="/ext_jsp/helloWorld.jsp">
               <forward name="success" contextRelative="true"
                    path="/ext_jsp/helloWorld.jsp" />
          </action>
     </action-mappings>
</struts-config>

The problem could be solved by adding the "handle" property (of type com.bea.console.handles.Handle) to the form bean.
This is stated on page 7-4 in the "Extending the admin console" guide or [url http://e-docs.bea.com/wls/docs92/console_ext/simpleext.html#wp1083856]here
In addition the following controller element must be used in the struts config: <controller inputForward="true" processorClass="com.bea.struts.adapter.action.AdapterRequestProcessor" />
This is not mentioned anywhere and should definitely be added to the guide.
Hope this helps someone encountering the same problem.

Proxy Service giving "Cannot Compute Effective WSDL for: Proxy Service"

Hi,
After updating the wsdl and schema, our proxy service is complaining with error : "Cannot Compute Effective WSDL for: Proxy Service " <ProxyService_Location_Name> when I launch a test console or access the Proxy Endpoint on IE.
Proxy and Business Services are pointing to the same WSDL. From Business Service, I am able to launch the test console. . Before updating the wsdl and schema, it was working fine. We tried to check in JDeveloper to see whether there are any issues with WSDL or Schema, but they are working fine.
Security Settings on Proxy Service are : Basic Authentication, User-Name Token Policy and also applied Transport Access Control. Security worked fine earlier before update.
From log file :
Root cause of ServletException.
java.io.IOException: Can not compute effective WSDL for : ProxyService ********
at com.bea.wli.sb.transports.http.ResourceRequestProcessor.securedInvoke(ResourceRequestProcessor.java:93)
at com.bea.wli.sb.transports.http.ResourceRequestProcessor.process(ResourceRequestProcessor.java:65)
at com.bea.wli.sb.transports.http.generic.RequestHelperBase.handleMetadataRequest(RequestHelperBase.java:181)
at com.bea.wli.sb.transports.http.generic.RequestHelperBase.service(RequestHelperBase.java:83)
at com.bea.wli.sb.transports.http.wls.HttpTransportServlet.service(HttpTransportServlet.java:127)
at weblogic.servlet.FutureResponseServlet.service(FutureResponseServlet.java:24)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
Any suggestions/ideas on why this error is happening is much appreciated.
Thanks,
Srithi

There must be definitely some issue in the Policy Configuration, due to which it is not able to Compute Effective WSDL.
Can you please do the following and capture the logs:
- set the transports debug flag to true in the alsbdebug.xml in your domain directory :
<java:alsb-transports-debug>true</java:alsb-transports-debug>
<java:alsb-service-security-manager-debug>true</java:alsb-service-security-manager-debug>
<java:alsb-service-validation-debug>true</java:alsb-service-validation-debug>
<java:alsb-wspolicy-repository-debug>true</java:alsb-wspolicy-repository-debug>
- set the WLS log level to debug
- Then restart the servers
This should give some additional details on the specific error.
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
https://forums.oracle.com/forums/ann.jspa?annID=893

Bug: export WSDL for proxy service

done under workshop 10.3, rightclick on proxy, then osb/export wsdl contains the wrong location (in my case port 7001 instead of 8001)
done with service bus web console the location is alright.
please report and fix this.
anyway does it belong to here or the workshop or soa forum? I feel free to xpost.
the whole export is annoying because it goes to a zip. why would i want to zip a single wsdl file.
thanks you for you attention,
Barossa

There must be definitely some issue in the Policy Configuration, due to which it is not able to Compute Effective WSDL.
Can you please do the following and capture the logs:
- set the transports debug flag to true in the alsbdebug.xml in your domain directory :
<java:alsb-transports-debug>true</java:alsb-transports-debug>
<java:alsb-service-security-manager-debug>true</java:alsb-service-security-manager-debug>
<java:alsb-service-validation-debug>true</java:alsb-service-validation-debug>
<java:alsb-wspolicy-repository-debug>true</java:alsb-wspolicy-repository-debug>
- set the WLS log level to debug
- Then restart the servers
This should give some additional details on the specific error.
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
https://forums.oracle.com/forums/ann.jspa?annID=893

Trouble with wlappc -- unresolved library references

I'm trying to pre-compile my Portal webapp projects JSPs using the wlappc Ant task. This is the relevent piece of my Ant script:
     <path id="wls.classpath">
          <path refid="java.classpath" />
          <dirset dir="${.java.src.output}" />
     </path>
     <property name="wls.classpath.prop" refid="wls.classpath"/>
     <echo level="debug">Classpath for wlappc (JSP compilation) is ${wls.classpath.prop}</echo>
     <wlappc deprecation="true" source="WebContent" forceGeneration="true" lineNumbers="true">
          <classpath refid="wls.classpath"/>
     </wlappc>
And this is the error I am getting:
[java] There are 1 nested errors:
[java]
[java] weblogic.utils.compiler.ToolFailureException: Error: Unresolved WebApp library references defined in weblogic.xml, of module 'C:\h\project\po
rtal\projectportal\WebContent' [Extension-Name: wls-commonslogging-bridge-war, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false]
, [Extension-Name: wlp-groupspace-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-tools-
visitor-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-collab-portlets-web-lib, Specifi
cation-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-commonui-web-lib, Specification-Version: 9.2, Implementa
tion-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-services-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-matc
h: false], [Extension-Name: wlp-framework-full-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Nam
e: p13n-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: beehive-controls-1.0-war, Specificat
ion-Version: 1, Implementation-Version: 1.0, exact-match: false], [Extension-Name: jstl, Specification-Version: 1.1, Implementation-Version: 1.1.2, ex
act-match: false], [Extension-Name: wlp-lookandfeel-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extensio
n-Name: wlp-light-web-lib, Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-wsrp-producer-web-lib,
Specification-Version: 9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-framework-common-web-lib, Specification-Version:
9.2, Implementation-Version: 9.2.1, exact-match: false], [Extension-Name: wlp-framework-struts-1.2-web-lib, Specification-Version: 9.2, Implementatio
n-Version: 9.2.1, exact-match: false], [Extension-Name: struts-1.2, Specification-Version: 1.2, Implementation-Version: 1.0, exact-match: false], [Ext
ension-Name: beehive-netui-resources-1.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false], [Extension-Name: beehive-netui-1
.0, Specification-Version: 1, Implementation-Version: 1.0, exact-match: false], [Extension-Name: weblogic-controls-1.0-war, Specification-Version: 1,
Implementation-Version: 1.0, exact-match: false]
[java] at weblogic.servlet.utils.WebAppLibraryUtils.initWebAppLibraryManager(WebAppLibraryUtils.java:90)
Thanks in advance for any help!

hi...even i am facing the same problem...can you plsssssss tell me what have you done to resolve the issue...

Commit timed out during oracle 2pc

Hi, all
I have a session bean with container managed transaction. In one of
the business methods, I need to update tables from 2 different Orcale
datasources. I am using the XA driver
oracle.jdbc.xa.client.OracleXADataSource when setting up the 2
connection pools. I have a log statement as the last line in my
method. The message gets logged without any delay. However, control
doesn't return from the method. And eventually, I get a timeout
message.
My guess is that the transaction manager has problem committing the
changes. But I don't know how to resolve this issue. Can someone help?
Thanks in advance.
TS

I suggest you try to start WL with debuffing turned on, that will give you a lot
of messy debug output, but at least you be able to see how resources listed and
delisted by transaction manager and how transaction started and commited.
To turn debugging on add following parameter in WLS startup line:
-Dweblogic.Debug=weblogic.JTAXA,weblogic.JDBCConn,weblogic.JTA2PC,weblogic.JTAJDBC
Hope this helps.
[email protected] (ts) wrote:
Hi, all
I have a session bean with container managed transaction. In one of
the business methods, I need to update tables from 2 different Orcale
datasources. I am using the XA driver
oracle.jdbc.xa.client.OracleXADataSource when setting up the 2
connection pools. I have a log statement as the last line in my
method. The message gets logged without any delay. However, control
doesn't return from the method. And eventually, I get a timeout
message.
My guess is that the transaction manager has problem committing the
changes. But I don't know how to resolve this issue. Can someone help?
Thanks in advance.
TS

DSP - fn:trace not working / CodeChange FAQs

Hi,
I want to use the fn:trace function, but I can't see any output from it. I already set the wls log level to debug, but there is still no output. Google gives a nice result for "fn:trace aldsp" but the website is gone: http://dev2dev.bea.com/wiki/bin/view/CodeShare/Faq_fntrace?skin=print.
Thanks for any help,
Guido

wls log level to debugYou also need to set the ALDSP log level for you dataspace to debug. Trace should appear in the WLS server log file.
but the website is gone: http://dev2dev.bea.com/wiki/bin/view/CodeShare/Faq_fntrace?skin=print.
Ask here about the dev2dev.bea.com content : Community Feedback (No Product Questions)

Proxy plug-in and WAP

Hello
I hava an IIS 5 with WLS proxy plugin configured on a win2000 server.
This machine has a real IP address to be accesed through the internet.
It proxies to a WLS 7 sp3 linux with no problem at all.
But, it does not proxy WAP content (wml). I mean, my webapp JSPs that
write the wml content.
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.3//EN"
"http://www.wapforum.org/DTD/wml13.dtd">
<%@ page contentType="text/vnd.wap.wml" %>
<wml>
</wml>
I have a simple menu on a wml page hosted on IIS. I can browse this menu
with no problem at all on my Nokia 3320..
<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="first" title="Alemana">
<p>
<a title="uno" href="#uno">uno</a>
<a title="Agenda" href="/wls/Login.jsp">Agenda</a>
<a title="dos" href="dos">dos</a>
<a title="tres" href="tres">tres</a>
</p>
</card>
<card id="uno" title="Menu uno">
</card>
</wml>
When I choose the option that references to WLS (proxing by path /wls),
I get the error "Unknown file format" on my cel phone. This does not
happen with Nokia Toolkit Software.
I have full debug log configured and nothing gets registered. Seems like
the proxy plugin is not even reached.
WebLogicHost=200.0.0.12
WebLogicPort=7001
WlForwardPath=/wls
DefaultFileName=Login.jsp
Debug=ALL
WLLogFile=C:\beaproxytest\proxy.log
ConnectTimeoutSecs=5
ConnectRetrySecs=2
If I access an html page on the WLS webapp, proxy plugin works fine. The
IIS and WLS web.xml have all MIME Types correctly set.
Can this be a proxy plugin issue?
Please help
Ricardo

The answer is that yes, in general you can use the same Web Server plug-ins across WLS versions. To answer specific questions, you should refer to our supported configurations documentation, such as:
http://e-docs.bea.com/platform/suppconfigs/configs103/103_over/add-ons.html
Note that over time new versions of Web Servers are released with older versions desupported. As a result newer versions of WebLogic Server may no longer support old Web Servers that were supported in older versions of WebLogic Server. But if you are using a current Web Server plug-in, on a Web server that is supported across your WebLogic Server versions, then yes you should be able to use the same plug-in across the WebLogic Server versions.

Wldeploy : redeployment does not work

Hi,
I would like to redeploy only a specific JSP. So I tried something like this:
<wldeploy name="NS Lookup" verbose="true"
        user="${wls.user}" password="${wls.password}"
        action="redeploy" debug="true"
        adminurl="t3://${wls.host}:${wls.port}"
           targets="${wls.server.name}"
        deltafiles="WebApp/nslookup.jsp">
</wldeploy>However I don't get any error the jsp has not been deployed on the server (Timestamp remains the same).
I use the split directory structure which looks like:
sources/
   WebApp/
         WEB-INF/
         nslookup.jsp
build/
dist/
    myEar/
         WEB-INF/
         nslookup.jspTo deploy I use following task:
<wldeploy name="NS Lookup"
        user="${wls.user}" password="${wls.password}"
        action="deploy" source="${dist}/${ear}"
           upload="true" stage="nostage"
        adminurl="t3://${wls.host}:${wls.port}"
           targets="${wls.server.name}" />           Moreover I would like to know if it is possible to redeploy jsp for example without loosing the http session.
Many thanks in advance
Best regards
Steve
Edited by ze_key at 01/30/2007 6:06 AM

Hi,
I found the solution : I had to remove upload="true" from the deploy task.
Redeploy does not work with a remote server although I didn't find anything in the doc regarding this issue.
Does anyone knows a workaround to be able to redeploy on a remote server ?
Many thanks in advance
Steve

Enabling JNDI Debug messages in WLS 8.1

Hi All,
Someone knows how to enable domain server debug logs for JNDI channel?
We want to see JNDI lifecycle events like bind(...)
regards
Sebastian

Thanks for the reply. It seems that the problem I'm having is due to some changes
in our realm and not local home lookups as I first suspected.
Rob Woollen <[email protected]> wrote:
Brian wrote:
Is there a requirement to look up local home interfaces from the java:/comp/env
namespace on WLS 8.1? No, although it's a good idea...
In WLS 6.2 we just looked up the local-jndi-name from an
initial context, but this doesn't appear to be working on 8.1. Thanks...It should work fine. Can you provide some more info? Are you sure the
bean is deploying?
-- Rob
..Brian

Debugging a custom realm in WLS 6.1

Hi all. I'm trying to find out how to debug my custom realm. I first implemented
the DebuggableRealm and put log.debug calls in my realm. I then set the realm.debug
property to "true" when I start the server. Is that it? The javadocs on debugging
are very sparse. I wasn't able to find a javadoc for weblogic.logging.LogOutputStream.
I also found a DebugSecurityRealm attribute in the ServerDebug element in config.xml
but am thinking this is old (from 5.X?).
Are there any other documents I should be looking at? Thanks!
jeff

Thanks very much, Utpal.
I still can't find the class (or even the package for that matter) at
http://e-docs.beasys.com/wls/docs61/javadocs/index.html
And that sort of mystifies me. Still, your answer solves my current problem.
I still don't fully understand the ConfigurationMBean
stuff as a whole, and how they get bound to a particular realm; i.e. Do I need
to write a MyRealmConfigurationMBean, and if so, how do
I bind it to MyRealm?
Note that the code I originally cited casted a BasicRealm return type to a BasicRealmMBean;
It's not immediately apparent why one is
even castable to the other, since they are two interfaces that
are not on the same inheritance line (I don't think).
Thanks for your time. I appreciate your help.
-chris
Finally,
"Utpal" <[email protected]> wrote:
Check this out
C:\opt\bea\wls61sp2\config\mydomain>javap weblogic.server.Server
Compiled from Server.java
public final class weblogic.server.Server extends java.lang.Object {
public static final java.lang.String DEFAULT_PROTOCOL;
public static final int DEFAULT_PORT;
public static weblogic.management.configuration.ServerMBean getConfig();
public static weblogic.management.configuration.ServerDebugMBean
getDebug();
public static weblogic.management.configuration.SecurityMBean
getSecurityCon
fig();
public static void initialize();
It's weblogic.server.Server class.
-utpal

Debugging WLS 4.5.1 with Symantech VCafe

Hi,
If anybody knows how to debug EJBs running in WLS remotely from Visual
Cafe 3.0, will you please describe how you do it?
Config: WLS 4.5.1, Cafe 3.0, Oracle 8i, NT 4.0 & Solaris
Thanks!!!!
[eytan.vcf]

This was posted in the product support group:
Hi Andrew. You are not alone. Upgrading to 4.5.1 and the multiple
classloaders caused similar problems for everyone. Here's how to get Cafe
and WebLogic 4.5.1 to play nice together.
1. Set the startup class in your project to the class the loads
weblogic. In this class, set -Dclasspath, -Dweblogic.class.path and
-Dweblogic.system.home variables.
2 Compile your entire project.
3. Go to Tools -> Env. options -> Debugging ->Run-Time Editing and check
the radio button that says 'Prompt before compiling ...'
4. Go to Project -> Options ->Directories and uncheck 'Append class path'
and 'Auto-generate class path'
Now you are ready to debug. Try it and let me know if you have any
problems. Hope this helps.
--Vinny
Eytan Ben-Meir wrote:
Hi,
If anybody knows how to debug EJBs running in WLS remotely from Visual
Cafe 3.0, will you please describe how you do it?
Config: WLS 4.5.1, Cafe 3.0, Oracle 8i, NT 4.0 & Solaris
Thanks!!!!

Weblogic.security.cache.debug property for wls 6.1

Hi,
how can I set the weblogic.security.cache.debug property that worked with wls
5.1. with the new 6.1 version ?
Thanks a milion!

With database concurrency, there is one instance per primary key per
transaction.
So if tx-1 calls pk 'Rob' and tx-2 calls pk 'Rob', they'll each have their own
instance.
-- Rob
levi wrote:
From weblogic ejb spec, it is said that for WLS 6.1 the default locking
services is Database locking now. The container will defer locking services
to the underlying database.
My question is in WLS6.1, for a single row of data record stored in the
underlying database, how many entity beans for this specific record in a
single WebLogic container can have? I know that in WLS5.1, there's only 1
entity bean instance for a specific record.
If in WLS6.1 there's still only 1 entity bean instance for a data record,
how does the container deal with the case in which multiple clients try to
update this entity bean concurrently (and at this time the container use
database locking service)?
Thanks,
Levi

Does WLS support Debugging Servlets with JBuilder 3 ?

I have read all the news groups and it appears that WLS 4.5.1 does not
support debugging Servlets with Jbuilder 3.0.
I am using the trial version, does this matter ?
Or should I just buy another web server ?
Joe

I think below documents will be helpful to you.
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/webservices/webservicesecurity/CreateDefaultWSSConfig.html
This document tell you that you can attach a weblogic webservice configuration using weblogic admin console.
After creating this configuration you need to updated this configuration as per the steps given under :
Use X.509 certificates to establish identity
Thanks,
sandeep

WLS 10.3.6 Debug

Similar Messages

Maybe you are looking for