Problems with WebLogic 5.1 Tour

I'm running the tour on an evaluation copy of WebLogic Server 5.1.
There are three places in the tour that don't seem to work correctly.
1. On the WebLogic Events page, the applet doesn't display anything.
That is, the applet area is totally blank. The status bar does say
"Applet initialized". Changing any problem priorities using the BigTel
App does not cause anything to be displayed.
2. On the WebLogic Enterprise Beans page, the applet area on the right
side of the page is always blank. If I add a new problem as described
on the page, the applet area does not change. In addition, the App
displays "EJB Beeper:Not On Line" on the bottom of the problem tab.
3. If I select the BigTel Console from the WebLogic Tour group, the
console starts running, but I'm not connected to the server. If I
connect using the defaults, I get the "myserver" server which shows no
connections. If I modify the port number on the advanced form to 8008,
then I connect to the bigtel server. The properties for the shortcut do
specify 8008, but it doesn't connect automatically.
For this last problem, I did try changing wlconsolew.exe to
wlconsole.exe in the shortcut as suggested by a message in May, but that
didn't help.
I also installed service pack 3 for WebLogic Server, with no change in
the symptoms.
The system is running NT workstation 4.0 with service pack 6, Internet
Explorer 5.01.
Paul Koerber
Unisys Corporation

Paul:
In article <[email protected]>, [email protected]
says...
I'm running the tour on an evaluation copy of WebLogic Server 5.1.
There are three places in the tour that don't seem to work correctly.
1. On the WebLogic Events page, the applet doesn't display anything.
That is, the applet area is totally blank. The status bar does say
"Applet initialized". Changing any problem priorities using the BigTel
App does not cause anything to be displayed.
This is why we strongly encourage application development other than
applets. There are too many possibilities fo things going wrong. These
are browser/vm issues that appear to have changed out from underneath the
browser your using. Sorry.
2. On the WebLogic Enterprise Beans page, the applet area on the right
side of the page is always blank. If I add a new problem as described
on the page, the applet area does not change. In addition, the App
displays "EJB Beeper:Not On Line" on the bottom of the problem tab.
Again applet problems we have no control over.
3. If I select the BigTel Console from the WebLogic Tour group, the
console starts running, but I'm not connected to the server. If I
connect using the defaults, I get the "myserver" server which shows no
connections. If I modify the port number on the advanced form to 8008,
then I connect to the bigtel server. The properties for the shortcut do
specify 8008, but it doesn't connect automatically.
For this last problem, I did try changing wlconsolew.exe to
wlconsole.exe in the shortcut as suggested by a message in May, but that
didn't help.I would sheepishly suggest that you turn to the examples for a much
better representation of the Server's capabilities. The tour is rather
outdated and will be replaced with a JSP based tour soon.
Sorry
Mark G.
>
I also installed service pack 3 for WebLogic Server, with no change in
the symptoms.
The system is running NT workstation 4.0 with service pack 6, Internet
Explorer 5.01.
Paul Koerber
Unisys Corporation
==================================================
NewsGroup Rant
==================================================
Rant 1.
The less info you provide about your problem means
the less we can help you. Try to look at the
problem from an external perspective and provide
all the data necessary to put your problem in
perspective.

Similar Messages

  • Problems with Verizon Wireless BlackBerry Tour BlackBerry OS 4.7.1.61 update:

    Problems with Verizon Wireless BlackBerry Tour BlackBerry OS 4.7.1.61 update - I was anxious to download the update to see if it addressed the sticky trackball problems and the low volume issue when using a blue tooth device. However, in the process of updating my BB Tour yesterday, the install stopped on the 8th out 12 updates. After a couple of 'retrys', the BB error message on the desktop came up which instructed me to: i) disconnect the device, ii) restart the computer. iii) restart the loading process and, iV) restore my data by loading the loader back-up file using Restore. Unfortunately my Tour was left without any software and the Desktop manager couldn't recognize it. The error message on the Tour was 503. Called Verizon Wireless tech and bottom line, the only fix is a new Tour, which they're sending me. Anyone else having issues with the update? Also, does it address the trackball and blue tooth issues?

    I had issues with the trackball and had to have my Tour replaced.  I was told this model does not have a removable trackball so the entire phone has to be replaced.  My current one is working OK but does stick a bit.  Seems to get worse over time.  My wife's tour is newer and so far she is not experiencing the problem.  Have not experienced a problem with the Blue Tooth volume.
    I have another issue with this upgrade that I am wondering if anyone else has seen.  My wife has the Tour as well.  She was prompted to do the upgrade and went through it.  It appeared to work except it blew out her Contact Alerts.  When we put them back in we can no longer get the sound to play when she receives an SMS message in her holster. Vibration works but doesn't do any good when it is in her purse.  Phones calls, calendar alerts, alarms all work in holster.  As soon as we delete the contact alert the default SMS alert will play in the holster.  If she takes her phone out of the holster the Contact alert will play.  My phone is still running 4.7.1.40 and this function works fine.  I am thinking about trying to put her's back to my version if possible but not sure the best way to go about this 

  • 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?

  • 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
              

  • 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

  • Problem with WebLogic 10.3.3, Apache 2.2.3 and WebLogic Apache proxy plugin

    I have a problem with using Apache 2.2.3 as a WebLogic SSL proxy. I have Apache 2.2 running and successfully configured an SSL cert, config in ssl.conf is...
    <VirtualHost secure.daftdonkey.com>
    # Setup SSL for secure.daftdonkey.com
    ServerName secure.daftdonkey.com
    SSLEngine On
    SSLCertificateFile /oracle/secure/secure.daftdonkey.com.crt
    SSLCertificateKeyFile /oracle/secure/secure.daftdonkey.com.key
    SSLCertificateChainFile /oracle/secure/gd_bundle.crt
    </VirtualHost>
    This works fine
    Now I want Apache to proxy requests to my WebLogic Server and secure them over SSL as well
    e.g. a request to https://secure.daftdonkey.com/service goes to https://weblogic.internal.site/service
    I have downloaded and configured the weblogic module and tested it handling traffic for HTTP and that worked, then I switched the WebLogic module to use SSL.
    LoadModule weblogic_module modules/mod_wl.so
    <IfModule mod_weblogic.c>
    WebLogicHost weblogic.internal.site
    WebLogicPort 16101
    Debug ALL
    SecureProxy ON
    WLSSLWallet /oracle/secure/my-wallet
    WLLogFile /tmp/wl-proxy.log
    </IfModule>
    <Location /service>
    SetHandler weblogic-handler
    </Location>
    Starting Apache throws the error. I think this is my main problem, i've searched support.oracle.com and not found anything.
    [Mon Jun 07 23:00:48 2010] [crit] (20014)Internal error: WL SSL Init failed for server: (null) on 0
    but Apache starts... I get this error when I make a request to https://secure.daftdonkey.com/service
    Failure of server APACHE bridge:
    No backend server available for connection: timed out after 10 seconds or idempotent set to OFF.
    Looking into the log /tmp/wl-proxy.log I see....
    Mon Jun 7 22:30:10 2010 <393212759749971> URLfactory Created
    Mon Jun 7 22:30:10 2010 <393312759750102> ================New Request: [GET /service HTTP/1.1] =================
    Mon Jun 7 22:30:10 2010 <393312759750102> INFO: SSL is configured
    Mon Jun 7 22:30:10 2010 <393312759750102> Using Uri /service
    Mon Jun 7 22:30:10 2010 <393312759750102> After trimming path: '/service'
    Mon Jun 7 22:30:10 2010 <393312759750102> The final request string is '/service'
    Mon Jun 7 22:30:10 2010 <393312759750102> parseServerList: Socket Address hostnames 'weblogic.internal.site:16101'
    Mon Jun 7 22:30:10 2010 <393312759750102> Host extracted from serverlist is [weblogic.internal.site]
    Mon Jun 7 22:30:10 2010 <393312759750102> parseServerList: IP from socket Address [192.168.100.15]
    Mon Jun 7 22:30:10 2010 <393312759750102> Initializing lastIndex=0 for a list of length=1
    Mon Jun 7 22:30:10 2010 <393312759750102> getListNode: created a new server node: id='weblogic.internal.site:16101' server_name='secure.daftdonkey.com', port='443'
    Mon Jun 7 22:30:10 2010 <393312759750102> attempt #0 out of a max of 5
    Mon Jun 7 22:30:10 2010 <393312759750102> Trying a pooled connection for '192.168.100.15/16101/16101'
    Mon Jun 7 22:30:10 2010 <393312759750102> getPooledConn: found a host and port/securePort match
    Mon Jun 7 22:30:10 2010 <393312759750102> getPooledConn: No more connections in the pool for Host[192.168.100.15] Port[16101] SecurePort[16101]
    Mon Jun 7 22:30:10 2010 <393312759750102> general list: trying connect to '192.168.100.15'/16101/16101 at line 3188 for '/service'
    Mon Jun 7 22:30:10 2010 <393312759750102> SSL is not configured for this connection
    Mon Jun 7 22:30:10 2010 <393312759750102> Local Port of the socket is 45580
    Mon Jun 7 22:30:10 2010 <393312759750102> Remote Host 192.168.100.15 Remote Port 16101
    Mon Jun 7 22:30:10 2010 <393312759750102> URL::connect SSLConn for reader is not set as it is NULL
    Mon Jun 7 22:30:10 2010 <393312759750102> general list: created a new connection to '192.168.100.15'/16101 for '/service', Local port:0
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Host]=[secure.daftdonkey.com]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Language]=[en-us,en;q=0.5]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Encoding]=[gzip,deflate]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Keep-Alive]=[300]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs from clnt:[Connection]=[keep-alive]
    Mon Jun 7 22:30:10 2010 <393312759750102> parse_header is done
    Mon Jun 7 22:30:10 2010 <393312759750102> Method is GET
    Mon Jun 7 22:30:10 2010 <393312759750102> About to call parseHeaders
    Mon Jun 7 22:30:10 2010 <393312759750102> URL::parseHeaders: Value of parsedHeaders = [0]
    Mon Jun 7 22:30:10 2010 <393312759750102> URL::sendHeaders(): meth='GET' file='/service' protocol='HTTP/1.1'
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Host]=[secure.daftdonkey.com]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Language]=[en-us,en;q=0.5]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Encoding]=[gzip,deflate]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Keep-Alive]=[300]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Connection]=[Keep-Alive]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [WL-Proxy-SSL]=[true]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [WL-Proxy-Client-IP]=[192.168.100.245]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [Proxy-Client-IP]=[192.168.100.245]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-Forwarded-For]=[192.168.100.245]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-WebLogic-KeepAliveSecs]=[30]
    Mon Jun 7 22:30:10 2010 <393312759750102> Hdrs to WLS: [X-WebLogic-Force-JVMID]=[unset]
    Mon Jun 7 22:30:10 2010 <393312759750102> Reader::fill(): first=0 last=0 toRead=4096
    Mon Jun 7 22:30:10 2010 <393312759750102> Reader::fill(): sysRecv returned -1
    Mon Jun 7 22:30:10 2010 <393312759750102> *******Exception type [READ_ERROR_FROM_SERVER] (socket read failure) raised at line 251 of ../nsapi/Reader.cpp
    Mon Jun 7 22:30:10 2010 <393312759750102> caught exception in readStatus: READ_ERROR_FROM_SERVER [os error=104, line 251 of ../nsapi/Reader.cpp]: socket read failure at line 963
    Mon Jun 7 22:30:10 2010 <393312759750102> PROTOCOL_ERROR: Backend Server not responding - isRecycled:0
    Mon Jun 7 22:30:10 2010 <393312759750102> Marking 192.168.100.15:16101 as bad
    Mon Jun 7 22:30:10 2010 <393312759750102> got exception in sendRequest phase: Backend Server not responding at line 3702
    Mon Jun 7 22:30:10 2010 <393312759750102> Failing over after sendRequest() exception: PROTOCOL_ERROR as Idempotent is set to ON
    Mon Jun 7 22:30:10 2010 <393312759750102> attempt #1 out of a max of 5
    However connecting directly to https://192.168.100.15:16101/irm_rights is successful.
    Ouput from orapki seems to show a valid wallet.
    [[email protected] my-wallet]# /oracle/install/bin/orapki wallet display -wallet /oracle/secure/my-wallet/
    Oracle PKI Tool : Version 11.1.1.2.0
    Copyright (c) 2004, 2009, Oracle and/or its affiliates. All rights reserved.
    Requested Certificates:
    User Certificates:
    Trusted Certificates:
    Subject: OU=Class 2 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: OU=Secure Server Certification Authority,O=RSA Data Security\, Inc.,C=US
    Subject: OU=Class 3 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: OU=Class 1 Public Primary Certification Authority,O=VeriSign\, Inc.,C=US
    Subject: CN=weblogic.internal.site,OU=FOR TESTING ONLY,O=MyOrganization,L=MyTown,ST=MyState,C=US
    Subject: CN=GTE CyberTrust Global Root,OU=GTE CyberTrust Solutions\, Inc.,O=GTE Corporation,C=US
    Also the apache log at /var/log/httpd/ssl_error_log shows.
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    [Mon Jun 07 23:59:03 2010] [error] [client 192.168.100.245] ap_proxy: trying GET /service/ at backend host '192.168.100.15/16101; got exception 'Backend Server not responding'
    Editing the httpd.conf and sending traffic from Apache to WebLogic over regular HTTP works, config is...
    LoadModule weblogic_module modules/mod_wl.so
    <IfModule mod_weblogic.c>
    WebLogicHost weblogic.internal.site
    WebLogicPort 16100
    Debug ALL
    # SecureProxy ON
    # WLSSLWallet /oracle/secure/my-wallet
    WLLogFile /tmp/wl-proxy.log
    </IfModule>
    Resulting detail from /tmp/wl-proxy.log
    Mon Jun 7 23:20:50 2010 <415912759780351> URLfactory Created
    Mon Jun 7 23:20:50 2010 <416012759780502> ================New Request: [GET /service/ HTTP/1.1] =================
    Mon Jun 7 23:20:50 2010 <416012759780502> Using Uri /service/
    Mon Jun 7 23:20:50 2010 <416012759780502> After trimming path: '/service/'
    Mon Jun 7 23:20:50 2010 <416012759780502> The final request string is '/service/'
    Mon Jun 7 23:20:50 2010 <416012759780502> parseServerList: Socket Address hostnames 'weblogic.internal.site:16100'
    Mon Jun 7 23:20:50 2010 <416012759780502> Host extracted from serverlist is [weblogic.internal.site]
    Mon Jun 7 23:20:50 2010 <416012759780502> parseServerList: IP from socket Address [192.168.100.15]
    Mon Jun 7 23:20:50 2010 <416012759780502> Initializing lastIndex=0 for a list of length=1
    Mon Jun 7 23:20:50 2010 <416012759780502> getListNode: created a new server node: id='weblogic.internal.site:16100' server_name='secure.daftdonkey.com', port='443'
    Mon Jun 7 23:20:50 2010 <416012759780502> attempt #0 out of a max of 5
    Mon Jun 7 23:20:50 2010 <416012759780502> Trying a pooled connection for '192.168.100.15/16100/16100'
    Mon Jun 7 23:20:50 2010 <416012759780502> getPooledConn: found a host and port/securePort match
    Mon Jun 7 23:20:50 2010 <416012759780502> getPooledConn: No more connections in the pool for Host[192.168.100.15] Port[16100] SecurePort[16100]
    Mon Jun 7 23:20:50 2010 <416012759780502> general list: trying connect to '192.168.100.15'/16100/16100 at line 3188 for '/service/'
    Mon Jun 7 23:20:50 2010 <416012759780502> SSL is not configured for this connection
    Mon Jun 7 23:20:50 2010 <416012759780502> Local Port of the socket is 56647
    Mon Jun 7 23:20:50 2010 <416012759780502> Remote Host 192.168.100.15 Remote Port 16100
    Mon Jun 7 23:20:50 2010 <416012759780502> URL::connect SSLConn for reader is not set as it is NULL
    Mon Jun 7 23:20:50 2010 <416012759780502> general list: created a new connection to '192.168.100.15'/16100 for '/service/', Local port:0
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Host]=[secure.daftdonkey.com]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Language]=[en-us,en;q=0.5]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Encoding]=[gzip,deflate]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Keep-Alive]=[300]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Connection]=[keep-alive]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from clnt:[Cookie]=[JSESSIONID=YF4nMNfZ3lJ5ZrVV9HGpKwj3hf12yRvlf4zksQf6pkKx2LhJ2ywY!34167467]
    Mon Jun 7 23:20:50 2010 <416012759780502> parse_header is done
    Mon Jun 7 23:20:50 2010 <416012759780502> Method is GET
    Mon Jun 7 23:20:50 2010 <416012759780502> About to call parseHeaders
    Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: Value of parsedHeaders = [0]
    Mon Jun 7 23:20:50 2010 <416012759780502> URL::sendHeaders(): meth='GET' file='/service/' protocol='HTTP/1.1'
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Host]=[secure.daftdonkey.com]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [User-Agent]=[Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100315 Firefox/3.5.9 ( .NET CLR 3.5.30729)]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept]=[text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Language]=[en-us,en;q=0.5]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Encoding]=[gzip,deflate]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Accept-Charset]=[ISO-8859-1,utf-8;q=0.7,*;q=0.7]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Keep-Alive]=[300]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Cookie]=[JSESSIONID=YF4nMNfZ3lJ5ZrVV9HGpKwj3hf12yRvlf4zksQf6pkKx2LhJ2ywY!34167467]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Connection]=[Keep-Alive]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [WL-Proxy-SSL]=[true]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [WL-Proxy-Client-IP]=[192.168.100.245]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [Proxy-Client-IP]=[192.168.100.245]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-Forwarded-For]=[192.168.100.245]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-WebLogic-KeepAliveSecs]=[30]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to WLS: [X-WebLogic-Force-JVMID]=[unset]
    Mon Jun 7 23:20:50 2010 <416012759780502> Reader::fill(): first=0 last=0 toRead=4096
    Mon Jun 7 23:20:50 2010 <416012759780502> Reader::fill(): sysRecv returned 568
    Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 302 Moved Temporarily]
    Mon Jun 7 23:20:50 2010 <416012759780502> URL::parseHeaders: StatusLine set to [302 Moved Temporarily]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Date]=[Tue, 08 Jun 2010 06:20:50 GMT]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Transfer-Encoding]=[chunked]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[Location]=[https://secure.daftdonkey.com/service/faces/LoginPage.jspx]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[X-WebLogic-JVMID]=[34167467]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs from WLS:[X-Powered-By]=[Servlet/2.5 JSP/2.1]
    Mon Jun 7 23:20:50 2010 <416012759780502> parsed all headers OK
    Mon Jun 7 23:20:50 2010 <416012759780502> done with sendRequest
    Mon Jun 7 23:20:50 2010 <416012759780502> sendResponse() : r->status = '302'
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[Date]=[Tue, 08 Jun 2010 06:20:50 GMT]
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[Location]=[https://secure.daftdonkey.com/service/faces/LoginPage.jspx]
    Mon Jun 7 23:20:50 2010 <416012759780502> for 192.168.100.15/16100/16100, updated JVMID: 34167467
    Mon Jun 7 23:20:50 2010 <416012759780502> Hdrs to client (add):[X-Powered-By]=[Servlet/2.5 JSP/2.1]
    Mon Jun 7 23:20:50 2010 <416012759780502> calling closeConn() with non-null URL* at 3826
    Mon Jun 7 23:20:50 2010 <416012759780502> canRecycle: conn=1 status=302 isKA=1 clen=-1 isCTE=1
    Mon Jun 7 23:20:50 2010 <416012759780502> closeConn: pooling for '192.168.100.15/16100'
    Mon Jun 7 23:20:50 2010 <416012759780502> closeConn: pooling '0'
    Mon Jun 7 23:20:50 2010 <416012759780502> request [irm_rights/] processed successfully..................
    Mon Jun 7 23:20:50 2010 <415912759780351> Cleaning up the list node 'weblogic.internal.site:16100'list Length '1'

    I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
    http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

  • Oracle 8.1.5 database connection problem with WebLogic 5.1

    Hello,
    the NSAPI integration works, also the JSP files.
    But I have still problems with the Jdriver for my Oracle 8.1.5.
    I get the message :
    Failed to invoke startup class
    weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
    when the WebLogic Server is started.
    Any ideas or hints about that?
    Thanks in advance
    Armin

    Post the full stacktrace here
    Also you might want to post jdbc related questions to weblogic.developer.
    interest.jdbc
    Kumar
    DreamNEON wrote:
    Hello,
    the NSAPI integration works, also the JSP files.
    But I have still problems with the Jdriver for my Oracle 8.1.5.
    I get the message :
    Failed to invoke startup class
    weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
    when the WebLogic Server is started.
    Any ideas or hints about that?
    Thanks in advance
    Armin

  • 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

  • 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.

  • Problem with weblogic.deploy and cluster

              I'm having some problems with the weblogic.deploy class when trying to refresh
              a jsp file. Using the following command to redeploy the entire application works
              fine:
              java weblogic.deploy -port 9876 -host apptest01 update
              administrator portal c:\portal-site
              However using the following command to refresh just one jsp
              file:
              java weblogic.deploy -url t3://apptest01:9876 -username system
              -jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
              refresh administrator portal
              produces the following stack trace:
              javax.naming.NameNotFoundException: Unable to resolve
              weblogic.management.home.olbcluster.
              Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
              remaining name ''
              at weblogic.rmi.internal.BasicOutboundRequest.
              sendReceive(BasicOutboundRequest.java:85)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              invoke(ReplicaAwareRemoteRef.java:255)
              at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              invoke(ReplicaAwareRemoteRef.java:222)
              at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              at $Proxy0.lookup(Unknown Source)
              at weblogic.jndi.internal.WLContextImpl.
              lookup(WLContextImpl.java:323)
              at weblogic.management.tools.WebAppComponentRefreshTool.
              getMBeanHomeForManagedServer
              WebAppComponentRefreshTool.java:498)
              at weblogic.management.tools.
              WebAppComponentRefreshTool.
              getComponentMBeanForServer
              (WebAppComponentRefreshTool.java:225)
              at weblogic.management.tools.
              WebAppComponentRefreshTool.findInternalPaths
              (WebAppComponentRefreshTool.java:187)
              at weblogic.management.tools.WebAppComponentRefreshTool.
              refresh(WebAppComponentRefreshTool.java:151)
              at weblogic.deploy.refresh(deploy.java:704)
              at weblogic.deploy.runBody(deploy.java:374)
              at weblogic.utils.compiler.Tool.run(Tool.java:79)
              at weblogic.deploy.main(deploy.java:1601)
              Unable to resolve weblogic.management.home.olbcluster.
              Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
              Any ideas?
              

              "John Murphy" <[email protected]> wrote:
              >
              >I'm having some problems with the weblogic.deploy class when trying to
              >refresh
              >a jsp file. Using the following command to redeploy the entire application
              >works
              >fine:
              >
              >java weblogic.deploy -port 9876 -host apptest01 update
              >administrator portal c:\portal-site
              >
              >However using the following command to refresh just one jsp
              >file:
              >
              >java weblogic.deploy -url t3://apptest01:9876 -username system
              >-jspRefreshFiles ./index.jsp -jspRefreshComponentName portal
              >refresh administrator portal
              >
              >produces the following stack trace:
              >
              >javax.naming.NameNotFoundException: Unable to resolve
              >weblogic.management.home.olbcluster.
              >Resolved: 'weblogic.management.home' Unresolved:'olbcluster' ;
              >remaining name ''
              > at weblogic.rmi.internal.BasicOutboundRequest.
              > sendReceive(BasicOutboundRequest.java:85)
              > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              > invoke(ReplicaAwareRemoteRef.java:255)
              > at weblogic.rmi.cluster.ReplicaAwareRemoteRef.
              > invoke(ReplicaAwareRemoteRef.java:222)
              > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
              > at $Proxy0.lookup(Unknown Source)
              > at weblogic.jndi.internal.WLContextImpl.
              > lookup(WLContextImpl.java:323)
              > at weblogic.management.tools.WebAppComponentRefreshTool.
              > getMBeanHomeForManagedServer
              > WebAppComponentRefreshTool.java:498)
              > at weblogic.management.tools.
              > WebAppComponentRefreshTool.
              > getComponentMBeanForServer
              > (WebAppComponentRefreshTool.java:225)
              > at weblogic.management.tools.
              > WebAppComponentRefreshTool.findInternalPaths
              > (WebAppComponentRefreshTool.java:187)
              > at weblogic.management.tools.WebAppComponentRefreshTool.
              > refresh(WebAppComponentRefreshTool.java:151)
              > at weblogic.deploy.refresh(deploy.java:704)
              > at weblogic.deploy.runBody(deploy.java:374)
              > at weblogic.utils.compiler.Tool.run(Tool.java:79)
              > at weblogic.deploy.main(deploy.java:1601)
              >Unable to resolve weblogic.management.home.olbcluster.
              >Resolved: 'weblogic.management.home' Unresolved:'olbcluster'
              >
              >Any ideas?
              >
              Hi John,
              How's tricks?
              It looks to me as though the olbcluster JNDI reference isn't being resolved from
              the tree. A similar error results when a Connection Pool cannot be resolved, the
              JNDI context env.jdbc is resolved but the particlar pool isn't. In my experience
              it often turns out to be an error in the correlation between the deployment descriptors,
              settings applied via the console and references made in the code.
              That's my tuppence worth,
              James :-)
              

  • Problem with Weblogic 9.1 JDBC connection pooling

    Hi,
    We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
    Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
    Any ideas what this could be? Are there known errors?

    Roy van Rijn wrote:
    Hi,
    We are currently in the middle of a migration from JBoss & WAS to BEA Weblogic. Both in JBoss and Websphere there are no problems with the connection but in Weblogic we (quickly) run out of connections.
    Our project uses Hibernate 3.1.3, Spring 1.2.7 and EJB 2.1. Using CMT and Spring to connect to our Oracle database. We tried different using the different drivers Weblogic offers, XA and non-AX, but in all cases we create connections quickly but they are almost never closed... until we run out of connections and get a Exception.
    Any ideas what this could be? Are there known errors?Hi. Please try setting the pool's idle-connection-timeout to 10 seconds or something
    reasonable, and we'll forcibly retract any leaked connections. So you don't write any
    JDBC code yourself, right?
    Joe

  • Heap Problem with weblogic.security.auth.login.PasswordCredential

    Hello,
    I am calling EJB's from a Tomcat 6.0.20. The EJB's are contained on a Weblogic 10 mp2. For getting EJBHome, I'm using the following InitialContext-Call:
    EJBHome home = null;
    try
    Properties initialContextProperties = new Properties();
    initialContextProps.put(InitialContext.INITIAL_CONTEXT_FACTORY, initialContextFactory);
    initialContextProps.put(InitialContext.SECURITY_PRINCIPAL, username);
    initialContextProps.put(InitialContext.SECURITY_CREDENTIALS, password);
    initialContextProps.put(InitialContext.PROVIDER_URL, url);
    initialContext = new InitialContext(initialContextProps);
    Object objref = this.initialContext.lookup(jndiHomeName);
    home = (EJBHome) PortableRemoteObject.narrow(objref, narrowClass);
    finally
    if ( initialContext != null )
    try
    initialContext.close();
    catch(Throwable t)
    return home;
    The Problem is, that after a bulk test on the tomcat (Xmx=256MB), 200MB are filled with 1.500.000 instances of the following class:
    weblogic.security.auth.login.PasswordCredential
    Has somebody an idea how to remove these classes from tomcat heap, because now the result is an OutOfMemory?
    Best regards,
    sebbay

    Hi,
    The authenticate method would take the user and the password details from the environment
    (env) that is passed and after successful authentication would populate the subject with
    the principals (i.e user, group the user belongs to ..)
    It should work with any user that is defined in the WLS not just weblogic/weblogic.
    Do you have any other users defined and which group do they belong to?
    Vimala
    Khalid Rizvi wrote:
    I am playing (learning) with weblogic.security.auth.login.UsernamePasswordLoginModule
    as a LoginModule using JAAS based authentication. Surprisingly, the only userid
    and password combination acceptable is uid=weblogic, pw=weblogic combination.
    I went through and looked at the example code under
    http://e-docs.bea.com/wls/docs70/security/cli_apps.html#1042212. I found that
    the UsernamePasswordLoginModule.login calls into
    if (url != null) {
    Environment env = new Environment();
    env.setProviderUrl(url);
    env.setSecurityPrincipal(username);
    env.setSecurityCredentials(password);
    try {
    Authenticate.authenticate(env, subject);
    Seems like UsernamePasswordLoginModule only is a router, as it instantiates an
    instance of Environemt using the userid and password and passes this Environemtn
    instance (env) to Authenticate.authenticate along with the empty Subject instance.
    I read about that the Subject instance will be filled in with Principals by the
    WL Server.
    My question is that firstly,
    1. As Authenticate.authenticate is not passed in the uid and pw, will it pick
    those from the env?
    2. Secondly, why does it only accept uid=weblogic & pw=weblogic.
    I will appreciate if some one can put me in the right direction.
    Khalid R. Rizvi
    508-641-1192
    [email protected]

  • Serious problem with WebLogic

    We have an application with servlets and tcp servers running in weblogic which receives request, then process requests and then sends the response back the clients.
    This application has been fully tested and put into production. This application is mainly used as a stress test tool which means that hundreds of requests are sent to the application every second.
    Just recently, we are having problems after 1400-1700 something requests. WebLogic would hang up and the application stops responding.
    We did many stress tests with this application before and it was working perfectly fine until now. We used to send it hundreds of thousands of requests to the application for three days without any problems.
    I have tried rebuilding the application, reinstalling WebLogic. Nothing seems to help. Memory usage is not a problem.
    The thing is that no code changes was ever made, nobody touched the application.
    Anybody has any ideas?
    +sometimes the servlet would still receive http request, however, tcp/ip requests stop working.  And there was no problem with the logs.  Our application logs are perfectly fine too.
    Edited by: user11856615 on Sep 2, 2009 4:34 PM
    Edited by: user11856615 on Sep 2, 2009 4:36 PM

    We are running WebLogic 9.2, Windows 2000 Advance Server, and is the info for Java:
    java.version = 1.5.0_04
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 1.5.0_04-b05
    The thing is that this application has been used as stress test tools for months without any problems. We ran it for weeks at a time and it processed hundreds of thousands of requests without any problem. And now suddenly this problem occurs.
    I have noticed that another stuck thread in the logs. I set to ignore stuck thread and will be running another test today and see what happens.

  • JSP Refresh Problems with Weblogic 8.1

    While Integration testing with Weblogic 8.1, when I make any changes in the Java classes (like interface changes), the JSPs are not able to recognize them. If the interface being used by a JSP changes, the JSP starts giving compilation errors. The other Java classes of the project though, run fine with the changes.
    Have wasted a lot of time in this situation . PLEASE ANY1 HELP!!!
    regards,
    SR

    Not sure on the first problem, store-version-in-cache is a valid element. Make sure you are using the same version of the Mapping Workbench and the runtime library. Please attach the XML for the version locking policy that was generated and the error message.
    The abstract method error seems to indicate that the setFetchSize method is missing on your driver.
    setFetchSize has been part of JDBC and JDK since JDBC 2.0/JDK 1.2, how old is the driver that you are trying to use? I noticed the COM is uppercase, so I assume this is a very old driver, can you use the more update version? TopLink requires JDK 1.3 support as a minimum.

  • HOT deployment problem with WebLogic 5.1sp11

    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJB DeployerTool.
    When we registered our jar in the weblogic.properties file - everything is OK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic application server
    (it works on another computer, but tool found our server confidently. Then I opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error message showed below.
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deployment ftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
         java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
         at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
         at sun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.java:108)
         at java.net.URL.openStream(URL.java:798)
         at weblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.java:322)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
         at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
         at weblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
         at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
         at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
         at weblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
         at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAdapter.java:347)
         at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandler.java:96)
         at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:15)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

    Is SP11 jars in the client classpath or not, before launching DeployerTool.
    If yes, then it looks like a bug. You might want to report this problem to
    [email protected]
    Kumar
    "Anton Nazarov" <[email protected]> wrote in message
    news:[email protected]
    >
    Hello!
    We trying to deploy our EJB (jar contains 5 EJB's) with WebLogic EJBDeployerTool.
    When we registered our jar in the weblogic.properties file - everything isOK.
    This ejb cotains correct EJB's which are made in EJB 1.1 standard.
    In the WebLogic EJB DeployerTool I attach proper WeaWeblogic applicationserver
    (it works on another computer, but tool found our server confidently. ThenI opened
    my jar file. Tool parsed file and found all beans.
    After all I'm trying to run Tools/Deploy and I have the error messageshowed below.
    >
    If somebody knows how to manage with this problem, help!
    weblogic.ejb.common.DeploymentException: Problem creating deploymentftp://172.16.2.108:21C:/tmp2/StaffShell.jar
    from ftp://172.16.2.108:21C:/tmp2/StaffShell.jar; nested exception is:
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    java.lang.NullPointerException:
    Start server side stack trace:
    java.lang.NullPointerException
    at sun.net.www.ParseUtil.decode(ParseUtil.java:27)
    atsun.net.www.protocol.ftp.FtpURLConnection.getInputStream(FtpURLConnection.ja
    va:108)
    >
    at java.net.URL.openStream(URL.java:798)
    atweblogic.ejb.internal.EJBJarDeployment.initializeJarFile(EJBJarDeployment.ja
    va:322)
    >
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:191)
    at weblogic.ejb.internal.EJBJarDeployment.setup(EJBJarDeployment.java:166)
    atweblogic.ejb.internal.EJBDeploymentImpl.<init>(EJBDeploymentImpl.java:172)
    >
    atweblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:100)
    >
    at weblogic.ejb.internal.EJBJarDeployment.<init>(EJBJarDeployment.java:94)
    at weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:332)
    atweblogic.ejb.common.EJBManager_WLSkel.invoke(EJBManager_WLSkel.java:144)
    >
    atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
    pter.java:347)
    >
    atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
    r.java:96)
    >
    atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
    5)
    >
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:129)
    End server side stack trace
    Deployment failed.

Maybe you are looking for

  • Accelerators in JPopupMenu

    it is possible to add key-accelerators in the menuitems, these items get printed inside the menuitem (e.g. "Alt+2"). they work in a menubar, but they don't work in a popupmenu. why? i need accelerators from a popupmenu!

  • Is there a template for gst

    I'm using numbers mostly on iPad i could use my iMac if needed,is there a template designed for gst

  • Don't transfer data to SD card or you will ending losing your data if interruption happen

    Hello guys, Don't fall in this trap and let the phone move data from internal memory to SD card to free up space as it can be interrupted for some unkown reasons and end up losing your data. ( Interruption in my case was screen auto lock i believe )

  • Canon 50D raw images seem to get shifted pink

    I got a Canon 50D the day it came out. Realized there was no support for the raw files so I shot RAW+JPEG. When it was finally posted, I installed the raw update and now Apeture (& Preview!) read the image but heavily shift the color towards pink. Th

  • Reading texts on watch screen

    Getting to grips with the SW3 - Previously had a Martian passport which seemed a lot more user firendly. Can read emails I receive from google fine. When I receive a text on the match I receive a notification that  I have received a text but am not a


HashFlare