JBuiler5Enterprise integrate with WebLogic 6 sp2 Problem?

When I configed finished ,but I cannot use the JBuilder5 to webrum using the WebLogic
as the Server.
The below is the error message:
Problem Unable to open location: Could not connect to: http://192.168.199.200:7001/servlet1
<2001-10-6 041157> <Error> <HTTP> <HttpServer(4051464,null default ctx,appserver)
found no context for "GET /servlet1 HTTP/1.1". This should not happen unless the
default context failed to deploy.>

In the weblogic console, for the server in question, there is an option
called:
WebLogic Plugin Enabled.
That will allow you to retrieve the client's IP.
Eric
"Slater" <[email protected]> wrote in message
news:[email protected]..
>
I am using WebLogic 6.1 with SP4 on Solaris 7 and plugin mod_weblogic +apache
1.3.27.
I need to get client IP during request and when userequest.getRemoteAddr() i
receive loopback ip ( 127.0.0.1 ) and not the original client Ip.
With WebLogic 6.1 SP2 the problem does not occur.
one idea ???

Similar Messages

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Best IDE to develop EJB/Servlet development with WebLogic

    Hi,
    I am prepearing a recommendation for our company's standard Java development
    environment. I would appriciate any comment you guys might have on the best
    IDE that supports J2EE and EJB and Servlet development that integrates with
    WebLogic. I guess the best are Visual Age or Visual Cafe, anybody have any
    experince/comment on any of those ?
    Thanks
    Farhang

    I would recommend the products coming from Webgain. They offer the product
    suite surrounding visual cafe.
    Thanks,
    Michael
    Michael Girdley
    Product Manager, WebLogic Server & Express
    BEA Systems Inc
    Farhang Kassaei <[email protected]> wrote in message
    news:8fs706$643$[email protected]..
    Hi,
    I am prepearing a recommendation for our company's standard Javadevelopment
    environment. I would appriciate any comment you guys might have on thebest
    IDE that supports J2EE and EJB and Servlet development that integrateswith
    WebLogic. I guess the best are Visual Age or Visual Cafe, anybody have any
    experince/comment on any of those ?
    Thanks
    Farhang

  • Integrating Oracle BPM with WebLogic Portal

    Can I integrate Oracle BPM standalone 10g with Weblogic Protal?
    Must I use the BPM for Weblogic to integrate with Weblogic Protal or OSB.
    According to the Configuration Guide, I cannot find the <ORABPM_standalone_HOME>/j2ee/weblogic/deployer

    Hi All,
    I am able to configure Oracle with Weblogic.
    Thx.

  • Problems with weblogic clustering in 6.1 sp3

    We have spent a lot of time trying to get our application deployed to
              a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              when we attempt to start the managed server. This was not a problem
              with weblogic sp1--we got our application to deploy to the cluster
              successfully; although there was another weblogic bug there with
              clients accessing EJB clusters--we won't go into that here...
              We have tried this on both a Windows 2000 machine and an HP machine
              running weblogic sp3. The same error occurs on both platforms.
              The error in deploying our application to the cluster against weblogic
              sp3 looks to have to do with our custom security realm. Inside our
              custom realm we make use of a configurable providerUrl which we set to
              the cluster address/port. The custom realm makes a call where it
              passes in the providerUrl to:
                   weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              When we have our providerUrl set to the cluster address/port--e.g.,
                   t3://clustermember1:7001
              and attempt to start the managed server we get the error:
              Starting WebLogic Server ....
              Connecting to http://adminserver:7117...
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.management.configuration.ConfigurationException:
              clustermember1 not found
                   at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
                   at weblogic.management.Admin.initialize(Admin.java:340)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              When we have our providerUrl set to the admin server address--e.g.,
                   t3://adminserver:7117
              everything starts up fine.
              Does anyone know why this would work on sp1 and not sp3 of weblogic
              6.1?
              We verified that all passwords are correct and everything else we
              could determine--any ideas would be helpful.
              We don't want the providerUrl to point at our admin server, we want it
              to point at the cluster address/port.
              When we get the managed server error, we received this error on the
              AdminServer:
              2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              Caught naming exception null; throwing RuntimeException.
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              unreachable; nested exception is:
                   java.net.ConnectException: Connection refused; No available router to
              destination
                   at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
                   at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
                   at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
                   at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
                   at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
                   at javax.naming.InitialContext.init(InitialContext.java:222)
                   at javax.naming.InitialContext.<init>(InitialContext.java:198)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
                   at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
              Servlet failed with Exception
              java.lang.RuntimeException
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Thanks for any help.
              Rich
              

    Bottom line:
              In our custom realm we were not handling user guest correctly. Even if you
              have guest user disabled, Weblogic seems to have hard-coded guest to
              send messages to the cluster every-so-often. Not sure there--couldn't get
              an answer out of bea as to exactly why we see guest still being used...
              It seems that with sp3, the user guest interaction started happening earlier
              than it did with sp1, consequently making our realm code fail when trying to
              retrieve the guest user like someone we knew about in our system.
              Hence, our getUser and authUserPassword methods now return null for both
              users guest and system, making the secondary realm (file realm) be used to
              authenticate and resolve guest & system. BEA helped get our code fixed;
              however, we still don't have a lot of depth in understanding Weblogic
              server's use of guest...
              Apparently, in 7.x the guest & system user behavior and configuration is
              different also... We'll see when we start digging into that migration.
              Rich
              [email protected] (Rich Koch) wrote in message news:<[email protected]>...
              > Thanks for the responses--we're working with weblogic support now. We
              > think that the custom realm that we have [the developer that wrote it
              > left the company] is the problem.
              >
              > The original developer was told by someone to check:
              > weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
              >
              > In order to determine if the JNDI was available/ready for the whole
              > cluster.
              >
              > It seems that the meaning/setting of THE_ONE changed with this respect
              > from
              > sp1 to sp3--i.e., this is no longer a valid test to tell us if the
              > JNDI is
              > ready for the cluster.
              >
              > We believe this was used because the 'system' user has to be
              > authenticated before the custom realm is up. Originally, before this
              > check was in place, an exception was received when authenticating
              > 'system'. This appears to be a weblogic limitation/issue. Support
              > has told us that this is different in weblogic 7.0. Unfortunately, we
              > can't upgrade from 6.1 yet.
              >
              > We'll post the solution when this gets figured out.
              >
              > Rak
              >
              > "Sabha" <[email protected]> wrote in message news:<[email protected]>...
              > > There was a security restriction enforced from sp2/sp3 onwards in terms of
              > > looking up mbeans from admin server.
              > >
              > > This might cause things to fail if you are attempting to lookup Mbeans with
              > > guest priviliges from admin server. Also, can you try doing the following:
              > >
              > > Run " java weblogic.Admin -url adminServer -username system -password
              > > .... -GET -pretty -type Server" and check whether the named clustermember1
              > > is available in the list or not.
              > >
              > > Also you seem to be getting some security exception - can you check that.
              > >
              > > t3://tomtate.msais.com:7119: Destination
              > > unreachable; nested exception is:
              > >
              > > --- Try running weblogic.Admin PING on this one and see whether you are
              > > able to reach this server upon the error message.
              > >
              > > --Sabha
              > >
              > > "Rich Koch" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > We have spent a lot of time trying to get our application deployed to
              > > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              > > > when we attempt to start the managed server. This was not a problem
              > > > with weblogic sp1--we got our application to deploy to the cluster
              > > > successfully; although there was another weblogic bug there with
              > > > clients accessing EJB clusters--we won't go into that here...
              > > >
              > > > We have tried this on both a Windows 2000 machine and an HP machine
              > > > running weblogic sp3. The same error occurs on both platforms.
              > > >
              > > > The error in deploying our application to the cluster against weblogic
              > > > sp3 looks to have to do with our custom security realm. Inside our
              > > > custom realm we make use of a configurable providerUrl which we set to
              > > > the cluster address/port. The custom realm makes a call where it
              > > > passes in the providerUrl to:
              > > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              > > >
              > > > When we have our providerUrl set to the cluster address/port--e.g.,
              > > > t3://clustermember1:7001
              > > >
              > > > and attempt to start the managed server we get the error:
              > > >
              > > > Starting WebLogic Server ....
              > > > Connecting to http://adminserver:7117...
              > > >
              > ***************************************************************************
              > > > The WebLogic Server did not start up properly.
              > > > Exception raised:
              > > > weblogic.management.configuration.ConfigurationException:
              > > > clustermember1 not found
              > > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
              > > > at weblogic.management.Admin.initialize(Admin.java:340)
              > > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
              > > > at weblogic.Server.main(Server.java:35)
              > > > Reason: Fatal initialization exception
              > > >
              > ***************************************************************************
              > > >
              > > > When we have our providerUrl set to the admin server address--e.g.,
              > > > t3://adminserver:7117
              > > >
              > > > everything starts up fine.
              > > >
              > > > Does anyone know why this would work on sp1 and not sp3 of weblogic
              > > > 6.1?
              > > > We verified that all passwords are correct and everything else we
              > > > could determine--any ideas would be helpful.
              > > >
              > > > We don't want the providerUrl to point at our admin server, we want it
              > > > to point at the cluster address/port.
              > > >
              > > > When we get the managed server error, we received this error on the
              > > > AdminServer:
              > > >
              > > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              > > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              > > > Caught naming exception null; throwing RuntimeException.
              > > > javax.naming.CommunicationException. Root exception is
              > > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              > > > unreachable; nested exception is:
              > > > java.net.ConnectException: Connection refused; No available router to
              > > > destination
              > > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > > at
              > > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > > at
              > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
              > > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
              > > > at javax.naming.InitialContext.init(InitialContext.java:222)
              > > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
              > > Realm.java:416)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
              > > lm.java:347)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
              > > java:51)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
              > > 225)
              > > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
              > > Realm.java:578)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:221)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              > > >
              > > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
              > > al2)]
              > > > Servlet failed with Exception
              > > > java.lang.RuntimeException
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:260)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > >
              > > >
              > > > Thanks for any help.
              > > >
              > > > Rich
              

  • Integrate iPlanet Web server with Weblogic 6.0?

    Hi
    Like to find out if there is any way I can integrate iPlanet Web Server,
    Enterprise Edition to Weblogic 6.0 sp2 . Is there anyway iPlanet could
    intergate with Weblogic security realm? Basicly I need to find you if
    iPlanet could use Webloigc for security authantication?
    thanks
    Tong Kiat

    Refer to Weblogic documentation on iPlanet proxy pluging settings

  • Problem integrating JProbe 4.0 with Weblogic 4.5.1

    I'm trying to integrate JProbe 4.0 with Weblogic 4.5.1. JProbe
    doesn't provide an integration for this version of Weblogic so I have
    to do the set up by hand. We are running Weblogic with a 1.3 JVM on
    Solaris.
    First problem is that the JVM we were using wasn't supported by
    JProbe. So I swapped to a different version. The application,
    consisting of about 150 EJBs plus JSPs and Servlets works fine with
    this JVM. When I run with JProbe, JProbe waits for the console
    connection then Weblogic starts. About half way through deploying all
    the EJBs the application stops. I've done a thread dump and it
    doesn't seem to be a deadlock. Looking at the JProbe console I can
    see that objects are getting allocated and GC'd in the typical saw
    tooth fashion indicating that things are still running. I've waited
    15 minutes but the application does not progress beyond this point.
    Any got any ideas about this or tips as to how I can debug things
    further?
    tia
    David

    Hi David,
    You could try to turn off memory debugging along with
    putting the debug environment into a big fat box. With
    memory debugging on JProbe is slooooow...
    Regards,
    Slava Imeshev
    "David Off" <[email protected]> wrote in message
    news:[email protected]..
    I'm trying to integrate JProbe 4.0 with Weblogic 4.5.1. JProbe
    doesn't provide an integration for this version of Weblogic so I have
    to do the set up by hand. We are running Weblogic with a 1.3 JVM on
    Solaris.
    First problem is that the JVM we were using wasn't supported by
    JProbe. So I swapped to a different version. The application,
    consisting of about 150 EJBs plus JSPs and Servlets works fine with
    this JVM. When I run with JProbe, JProbe waits for the console
    connection then Weblogic starts. About half way through deploying all
    the EJBs the application stops. I've done a thread dump and it
    doesn't seem to be a deadlock. Looking at the JProbe console I can
    see that objects are getting allocated and GC'd in the typical saw
    tooth fashion indicating that things are still running. I've waited
    15 minutes but the application does not progress beyond this point.
    Any got any ideas about this or tips as to how I can debug things
    further?
    tia
    David

  • Problems with Weblogic 8.1

    I've got an exception
    <07.11.2004 18:20:22 MSK> <Error> <HTTP> <BEA-101216> <Servlet: "Faces Servlet"
    failed to preload on startup in Web application: "MyApp".
    javax.servlet.ServletException
    at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubIm
    pl.java:906)
    at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStub
    Impl.java:842)
    at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubI
    mpl.java:782)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppS
    ervletContext.java:3236)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
    ServletContext.java:3193)
    at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebApp
    ServletContext.java:3179)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAp
    pServletContext.java:3154)
    at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java
    :654)
    at weblogic.servlet.internal.WebService.preloadResources(WebService.java
    :483)
    at weblogic.servlet.internal.ServletInitService.resume(ServletInitServic
    e.java:30)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
    at weblogic.Server.main(Server.java:32)
    >
    JSF v.1.1
    Does JSF work with WebLogic?

    Have you already figured it out? I have the same
    problem to deploy a jsf war file to Weblogic 8.1.I got it working on wls 8.1 sp2. This is a work around for some of us who need to work with existing products and any upgrade to a newer version takes its own sweet time. Read below ...
    1.     Work-around for �listener� in web.xml not working
    a.     Create InitFacesContext Servlet
    public class InitFacesContext extends GenericServlet {
         StartupServletContextListener listener;
         public void destroy() {
              super.destroy();
              listener.contextDestroyed(new ServletContextEvent(getServletContext()));
         public void init(ServletConfig arg0) throws ServletException {
              super.init(arg0);
              listener = new StartupServletContextListener();
              listener.contextInitialized(new ServletContextEvent(getServletContext()));
         public void service(ServletRequest arg0, ServletResponse arg1) throws ServletException, IOException {
    }b.     Configure web.xml
    <!--
         <listener>
           <listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
         </listener>
          -->
         <servlet>
              <servlet-name>InitFacesContext</servlet-name>
              <servlet-class>com.gene.volts.servlet.InitFacesContext</servlet-class>
              <load-on-startup>0</load-on-startup>
         </servlet>
         <servlet>
              <servlet-name>FacesServlet</servlet-name>
              <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>2.     JSP 2.0 requirement
    a.     Download jsp-api.jar (like from Tomcat 5.x distribution ;-) ) and include it in web-inf/lib
    3.     Dealing with FacesContext not being initialized error
    a.     web.xml configuration
         <servlet-mapping>
              <servlet-name>FacesServlet</servlet-name>
              <url-pattern>*.faces</url-pattern>
         </servlet-mapping>
         <welcome-file-list>
              <welcome-file>index.jsp</welcome-file>
         </welcome-file-list>b.     Redirect
    <jsp:forward page="/abc.faces"/>

  • Problem in Using Log4J with Weblogic 9.2

    I am using Weblogic 9.2 and Log4j.
    By using Admin console I set the Severity Level to WARNING and inside my java code is given below:
    Logger logger = Log4jLoggingHelper.getLog4jServerLogger();
    if (logger.isEnabledFor(Priority.DEBUG)){
    logger.debug("DEBUG - Test Debug message");
    logger.info("DEBUG - Test Info Message");
    logger.warn("DEBUG - Test Warning Message");
    logger.error("DEBUG - Test Error Message");
    logger.fatal("DEBUG - Test Fatal Message");          
    Somehow the logger.isEnabledFor(Priority.DEBUG) returning 'TRUE' and the follwoing message is displayed.
    <Nov 29, 2006 2:44:04 PM EST> <Warning> org.apache.log4j.Category> <000000> <DEBUG - Test Warning Message>
    <Nov 29, 2006 2:44:04 PM EST> <Error> <org.apache.log4j.Category> <000000> <DEBUG - Test Error Message>
    <Nov 29, 2006 2:44:04 PM EST> <Info> <org.apache.log4j.Category> <000000> <DEBUG - Test Fatal Message>
    <b><i>NOTE - The logger.debug() and logger.info() methods are not invoked because of the severity level to 'WARNING' in the console.</i></b>
    <b>I would like to know why the Somehow the logger.isEnabledFor(Priority.DEBUG) is having a value of 'TRUE'.</b>
    I expected only the Somehow the logger.isEnabledFor(Priority.ERROR) will have the value of 'TRUE'.

    Did you get an answer to your question? I have the same problem with WebLogic 10.0.

  • Problem with Weblogic Builder SP1

    I have a problem with Weblogic Builder SP1. I basically re-used my EJB deployment
    descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loading my EJB
    in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
    I re-attempted by jarring my EJB with WL5.1 descriptors and used my friend's WB
    (not SP1) to export new descriptors which I used to re-jar. This new EJB is again
    not recognised by WB SP1?
    What is wrong?

    The exception is as follows:
    Opening module myproj.jar
    java.lang.NullPointerException
         at java.util.Arrays.sort(Arrays.java:1181)
         at weblogic.marathon.model.EJBJarCMBean.initRelations(EJBJarCMBean.java:1212)
         at weblogic.marathon.model.EJBJarCMBean.initBeans(EJBJarCMBean.java:1098)
         at weblogic.marathon.model.EJBJarCMBean.setup(EJBJarCMBean.java:1144)
         at weblogic.marathon.tasks.OpenModuleTask.getEJBModule(OpenModuleTask.java:156)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:191)
         at weblogic.marathon.tasks.OpenModuleTask.figureOutModule(OpenModuleTask.java:230)
         at weblogic.marathon.tasks.OpenModuleTask.runBackground(OpenModuleTask.java:89)
         at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127)
         at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)
    Module myproj.jar descriptors failed to load
    The EJB has no problem deploying.
    Rob Woollen <[email protected]> wrote:
    You'll have to at least show us the error you get from marathon.
    Does your application deploy to the server?
    -- Rob
    Robin Tan wrote:
    I have a problem with Weblogic Builder SP1. I basically re-used myEJB deployment
    descriptors from WL5.1 in WL8.1. Before SP1, i have no problem loadingmy EJB
    in WB. But with SP1, WB throws weblogic.marathon.model.LoadFailureException.
    I re-attempted by jarring my EJB with WL5.1 descriptors and used myfriend's WB
    (not SP1) to export new descriptors which I used to re-jar. This newEJB is again
    not recognised by WB SP1?
    What is wrong?

  • BIG5 Problem with WebLogic Express 6.1

              Hi,
              I found some problem with Chinese Big5 when using JSP. All big5 code convert in
              a wrong format and can't view by browser.
              My server setting is:
              OS: Solaris 8
              Weblogic: Express 6.1
              JDK 1.3.1
              Anyone know how to solve this problem?
              I have tried different way like creating a new string in different encoding type.
              Actually the BIG5 work fine with Solaris 8, JDK1.2.2_05a and Weblogic 5.1. However
              I WEblogic 6.1 only support JDK1.3 or above. Anyone can help me out. Thanks.
              Pls email me at [email protected]
              

    The download binary is the same for WL Full version and WL Express. It's the
    license that matters. Contact BEA to obtain / buy a WL Express license.
    Ben
    "Rajendra" <[email protected]> wrote in message
    news:[email protected]..
    We have WebLogic 6.1 licensed software. I need to work with WebLogic
    Express.
    I installed on win2K using the installer available with the CD. Now, what
    exactly do I need to do (restricting license..) to work with WebLogic
    Express?
    I need this info urgently. Any help in this regard is greatlyappreciated.
    >
    Thanks
    Rajendra.
    "Michael" <[email protected]> wrote in message
    news:[email protected]..
    Hi.
    WebLogic Express is WebLogic Server with a different license that limits
    some of
    the WebLogic Server features, such as EJB. Downloading WLS effectively
    downloads
    WebLogic Express.
    Regards,
    Michael
    raj wrote:
    Hi,
    does anyone know if it's possible to download weblogic express 6.1 ? icouldn't
    find any link on the bea website.
    thanks
    Raj

  • Problems using 4096 bit SSL certificate with WebLogic Apache 2.2 plug-in

    Hi,
    'm using WebLogic 9.2 MP3 and Apache HTTP Server (version 2.2) Plug-In. For security reasons, I have SSL installed on both Apache and WebLogic. So Apache must communicate with WebLogic via https.
    I get the following error when attempting to access WebLogic via Apache:
    Internet Explorer cannot display the webpage
    These are the last lines in wlproxy log:
    Fri Feb 26 14:08:59 2010 <71212672221392> INFO: SSL is configured
    Fri Feb 26 14:08:59 2010 <71212672221392> SSL Main Context not set. Calling InitSSL
    Fri Feb 26 14:08:59 2010 <71212672221331> INFO: Initializing SSL library
    I've found that the problem is caused by using a 4096 bit intermediate cert. When I include this 4096 bit cert in the file referenced by plugin parameter "TrustedCAFile", it is unable to load it. I've tested 4096 bit certs from a few different certificate authorities, and consistently see this problem, so I know the problem is not related to the specific certificate. If I use a 2048 bit intermediate certificate, everything works perfectly fine.
    Do you know if there are limitations to the certificate length that the plug-in can use?

    Yes 4096 bit Certificates are not supported by the plugin.
    You can use up to 2048 bit.
    There is a Bug which clearly mentions it.
    I dont remember the Bug Number, but an Oracle Support person will be able to tell you.
    Hope this helps.
    Faisal Khan
    Edited by: Faisal Khan on Feb 27, 2010 2:08 PM

  • Problem with weblogic server help me...!

    HI,
    i have developed and application that was deployed successfully in Tomcat 5.0, but it was not with weblogic 8...
    plz help me... thanks in advance..

    In this case, I would call the OP up from asking a stupid question, with no details at all, rather than Soultech for responding to it in humorous manner.
    Hence why I included that link to "How to ask smart questions"
    "It doesn't work on Weblogic" will not get any helpful responses
    WHAT doesn't work?
    Is there an error message?
    What have you tried?
    The onus is on the OP to post a clear and concise description of his problem, along with error messages/stack traces, anything else that may help diagnose the issue.
    I believe Soultechs post was justified, if a little short.

  • Sun Identity Server 6.1 with Weblogic 8.1 sp2

    Hi,
    I've installed the IS 6.1 with WLS 8.1 sp2 and the agent 2.1.1 and followed the agent configuration guide to configure the xml files (web.xml and weblogic.xml) and agent authenticator.
    When I login to the restricted resource, the browser is redirected to the IS server login page. After login, the browser is redirected back to the resource with 403 forbidden.
    Is there any step missing? Should I additional add some policy in the IS console? .....
    Clive

    I have just installed Sun Identity Server 6.2 with WebLogic 8.1 SP3 and am experiencing the same results. Have you resolved this issue in your environment? We are evaluating Portal Server running on a BEA WLS Container and thus do not have Sun Support on the Identity Server Component of this configuration.

  • Problem with weblogic.Deployer in 8.1

    I have a problem with weblogic.Deployer. My application deploys and works fine
    if I manually copy the ear or the exploded form into weblogic's applications\
    directory (hot deployment). But, if I use the weblogic.Deployer tool, it fails
    with the following exception. Does the deployer tool expect something in the ear
    (or exploded form) that I'm missing? Thanks in advance.
    -Vas
    [wldeploy] java.lang.NullPointerException
    [wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
    ator.java:785)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
    r.java:758)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:803)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] --------------- nested within: ------------------
    [wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Failed
    to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub ]
    with nested exception:
    [wldeploy] [java.lang.NullPointerException]
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:807)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] java.lang.reflect.InvocationTargetException
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION FAILED ***
    **[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
    _WLStub ] - with nested exception:
    [wldeploy] [java.lang.NullPointerException]
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:807)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] ... 15 more

    Hi Deepak,
    I didn't understand the suggested resolution. Can you tell me what it means?
    However, I found a similar problem in the archives, so I tried from command line
    (outside ant) using "java weblogic.Delployer ...." and it worked! It doesn't work
    from ant. So, you think there's some conflict between my ant and weblogic's ant
    task "WLDdeploy"?
    Thanks,
    Vas
    "Deepak Vohra" <[email protected]> wrote:
    >
    Refer to
    http://e-docs.bea.com/wls/docs70/notes/resolved.html#1296363
    "vas pulipati" <[email protected]> wrote:
    I have a problem with weblogic.Deployer. My application deploys andworks
    fine
    if I manually copy the ear or the exploded form into weblogic's applications\
    directory (hot deployment). But, if I use the weblogic.Deployer tool,
    it fails
    with the following exception. Does the deployer tool expect something
    in the ear
    (or exploded form) that I'm missing? Thanks in advance.
    -Vas
    [wldeploy] java.lang.NullPointerException
    [wldeploy] at weblogic.rmi.internal.StubGenerator.getStubOnClient(StubGener
    ator.java:785)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.getStubClass(StubGenerato
    r.java:758)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:803)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] --------------- nested within: ------------------
    [wldeploy] weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[
    Failed
    to generate class for weblogic.common.internal.RMIBootServiceImpl_811_WLStub
    with nested exception:
    [wldeploy] [java.lang.NullPointerException]
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:807)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] java.lang.reflect.InvocationTargetException
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
    sorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
    hodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:324)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy
    .java:209)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.ja
    va:170)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.ja
    va:166)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:319)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:309)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1250
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:610)
    [wldeploy] at org.apache.tools.ant.Main.start(Main.java:196)
    [wldeploy] at org.apache.tools.ant.Main.main(Main.java:235)
    [wldeploy] Caused by: weblogic.utils.AssertionError: ***** ASSERTION
    FAILED ***
    **[ Failed to generate class for weblogic.common.internal.RMIBootServiceImpl_811
    _WLStub ] - with nested exception:
    [wldeploy] [java.lang.NullPointerException]
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:807)
    [wldeploy] at weblogic.rmi.internal.StubGenerator.generateStub(StubGenerato
    r.java:790)
    [wldeploy] at weblogic.rmi.extensions.StubFactory.getStub(StubFactory.java:
    79)
    [wldeploy] at weblogic.common.internal.RMIBootServiceStub.getStub(RMIBootSe
    rviceStub.java:50)
    [wldeploy] at weblogic.security.acl.internal.Security.authenticate(Security
    .java:152)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRem
    otely(WLInitialContextFactoryDelegate.java:597)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLI
    nitialContextFactoryDelegate.java:534)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLIn
    itialContextFactoryDelegate.java:336)
    [wldeploy] at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialConte
    xt(WLInitialContextFactoryDelegate.java:308)
    [wldeploy] at weblogic.jndi.Environment.getContext(Environment.java:164)
    [wldeploy] at weblogic.jndi.Environment.getInitialContext(Environment.java:
    143)
    [wldeploy] at weblogic.management.deploy.utils.MBeanHomeTool.getMBeanHome(M
    BeanHomeTool.java:157)
    [wldeploy] at weblogic.Deployer.runBody(Deployer.java:555)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:146)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:103)
    [wldeploy] at weblogic.Deployer.main(Deployer.java:399)
    [wldeploy] ... 15 more

Maybe you are looking for