So I'm able to run wlshell in the new WLS9 environment now, but my
application domains are not showing up. All I get are these three:

wlsh runtime.com.bea:/> domains
[runtime.JMImplementation, runtime.Security, runtime.com.bea]

I'm expecting to see the app domain itself and two JMX domains. I'm
not sure if it's a problem with the new WLS9 domain, or something with
wlshell. Any ideas?

Erik


--- In wlshell@yahoogroups.com, "Erik Agee" <erik.r.agee@...> wrote:
>
> Thanks, Paco. A fresh install of the new version caused the error to
> go away.
>
> Erik
>
> --- In wlshell@yahoogroups.com, "sfomad" <paco@> wrote:
> >
> > Erik,
> >
> >
> > that should work, but try with the latest beta:
> >
> > http://www.wlshell.net/beta/wlshell-2.1.0.zip
> >
> >
> > connect to the managed server using its address(or name) and port. If
> > you find any issue, start wlshell with -d and send me the wlshell.log
> > file to debug it.
> >
> >
> > The final wlshell 2.1 version should be available in July.
> >
> > cheers,
> > Paco
> >
> >
> >
> >
> > --- In wlshell@yahoogroups.com, "Erik Agee" <erik.r.agee@> wrote:
> > >
> > > We recently upgraded from WebLogic 8.1 to 9.2. We upgraded
wlshell to
> > > the 2.1.0-beta-2 as well to address the compatibility issue, but now
> > > when we try to connect to our managed servers, we get this error:
> > >
> > > connecting to MBeanServer(s) as <user>...failed
> > > couldn't execute all the script, there was an error at line 1:
Unable
> > > to resolve 'weblogic.management.mbeanservers.domainruntime'.
Resolved
> > > 'weblogic.management.mbeanservers'
> > >
> > > Can anyone help?
> > >
> > > Thanks,
> > >
> > > Erik
> > >
> >
>