Problems with weblogic clustering setup

Hi all, I'm having problems extending a weblogic 9.2 cluster from vertical to orizontal. The environment is composed by two physical servers A and B. On A it's running the node manager, the admin console and two nodes, on B I've just installed weblogic 9.2, registered the licence.
I'm reading this guide: http://egeneration.beasys.com/wls/docs103/cluster/setup.html#wp742559 but I think this guide is non clear.
1) I added the new machine into the admin console
2) I added the new server to the configuration (environmnent -> cluster)
3) I created a new node on the new server and I associate it to the cluster and machine.
moreover I checked the ports so that it should be set correctly.
After I start the nodemanager into B and after adminconsole from A tries to connect to B I get this into the console
[root@engtest4 bea]# /opt/bea/weblogic92/server/bin/startNodeManager.sh
+ CLASSPATH=/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar:/opt/bea/patch_weblogic922/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/opt/bea/jrockit90_150_10/lib/tools.jar:/opt/bea/weblogic92/server/lib/weblogic_sp.jar:/opt/bea/weblogic92/server/lib/weblogic.jar:/opt/bea/weblogic92/server/lib/webservices.jar::/opt/bea
+ export CLASSPATH
+ export PATH
+ cd /opt/bea/weblogic92/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /opt/bea/jrockit90_150_10/bin/java -jrockit -Xms128m -Xmx256m -Xverify:none -Djava.security.policy=/opt/bea/weblogic92/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/opt/bea/jrockit90_150_10 weblogic.NodeManager -v
<Jan 14, 2009 5:10:22 PM> <INFO> <Loading domains file: /opt/bea/weblogic92/common/nodemanager/nodemanager.domains>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loading identity key store: FileName=/opt/bea/weblogic92/server/lib/DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
<Jan 14, 2009 5:10:23 PM> <INFO> <Loaded node manager configuration properties from '/opt/bea/weblogic92/common/nodemanager/nodemanager.properties'>
Node manager v9.2.2.0
Configuration settings:
NodeManagerHome=/opt/bea/weblogic92/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=true
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/opt/bea/jrockit90_150_10/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/opt/bea/weblogic92/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
Domain name mappings:
wl_server -> /opt/bea/weblogic92/samples/domains/wl_server
base_domain -> /opt/bea/user_projects/domains/base_domain
<Jan 14, 2009 5:10:24 PM> <INFO> <Secure socket listener started on port 5556>
<Jan 14, 2009 5:10:38 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
<Jan 14, 2009 5:11:54 PM> <Warning> <I/O error while reading domain directory: java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)>
java.io.FileNotFoundException: Domain directory '/opt/bea/weblogic92/common/nodemanager' invalid (domain salt file not found)
     at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:80)
     at weblogic.nodemanager.server.DomainManager.<init>(DomainManager.java:52)
     at weblogic.nodemanager.server.NMServer.getDomainManager(NMServer.java:242)
     at weblogic.nodemanager.server.Handler.handleDomain(Handler.java:212)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:105)
     at weblogic.nodemanager.server.Handler.run(Handler.java:66)
     at java.lang.Thread.run(Thread.java:595)
should server A and B have the same domain configuration? (same files)
Regards
Marco

Yes, you must have the same domain configuration on the server B. Usually I copy the domain directory on the server B to have the same configuration. the directory with "salt file" should be the "<domain_dir>/security"...
Hope this helps...
Mariano

Similar Messages

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

  • Problem with Audio MIDI Setup using multiple accounts

    I'm having a problem with Audio MIDI Setup recognizing all of the MIDI devices on a G4 Tower with a non-administrator account. The main administrator account has no problem seeing anything, but the non-admin account won't see anything. Does it all have to be added in manually, or is there a preferences file to copy over that will take care of this. Failing that, is it a problem with file permissions? Any help would be greatly appreciated.

    Don't know whether this of any help, but there's an identifiable issue with AMS and Digital Performer 5 where DP5 simply won't load with AMS setups configured with previous versions of DP. Which is probably irrelevant to your problem, but ...
    What I and other DP users have found we have to do is start with a completely new, blank AMS setup, and reconfigure our devices from scratch, and although this was kind of hit and miss and on the fly (don't really understand what the the issue was, exactly), I think the bottom line was if we used the new AMS setup with DP5 before anything else that might cause its data tables to change, we were ok.
    So if you can do it, it might be worth setting AMS to a new blank template, then connecting your interfaces, see how far you get. And always make sure you've got the latest drivers of course, though I'm sure you've done that.
    Never used Mbox or 410, but I've an Ozonic which I think uses the same M-Audio firewire drivers as the 410, and don't have any problem with that, FWIW.
    G5 Dual 2.7, MacMini, iMac 700; P4/XP Desk & Lap.   Mac OS X (10.4.8)   mLan:01x/i88x; DP 5.1, Cubase SX3, NI Komplete, Melodyne.

  • 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

  • Problems with first time setup

    Hi to all and please be kind to this new applee.  I am vary familar with Windows but not Apple.
    I am having problems with first time setup.  Choice wifi network ZAJ34 has full connectino bars but requires a password to connect with it.  Tried to use "Connect to iTunes" and plugged in the USB cable.  Windows7 ran ok and "MyComputer\Apple iPod" shows up in Explorer.  All I get to is the screen that shows the cable pointing to the music symbol.  I am new to Applie iPod so I am totally lost.  I have the Apple iPod touch 8GB Black (4th Generation) CURRENT MODEL.
    Operating System - iPod touch User Guide (For iOS 5.1 Software) downloaded, not sure.
    Thanks
    Wayne

    I find this,
    Before restoring:
    Verify that you are using the latest version of iTunes. [How?  I am not past selecting a network.]
    Back up your device. [Do not know how, again, I am not past selecting a network.]
    Transfer and sync content to your computer. [Hooked up the USB cable and nothing happens.]
    Restoring your iOS device
    Connect your device to your computer. [Hooked up the USB cable and nothing happens.]
    Select your iPhone, iPad, or iPod touch when it appears in iTunes under Devices. Select the Summary tab, and click the Restore button. [iPod touch when it appears in iTunes under Devices, is it in Control Panel.  I looked in Device Manager and so only drivers etc.

  • 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.
    [root@content 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

  • Passivation errors on Weblogic clustered setup.

              Hi,
              I have a Weblogic 6.0 SP2 clustered setup. If I change the deployment descriptor
              and set the
              max-beans-in-cache to 2 and create 3 instances of a stateful ejb, it gets passivated
              without any exceptions, but if the application runs for a long time, passivation
              errors occur.
              I get the following exceptions:
              ####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2> <ExecuteThread:
              '1' for queue: 'Replication'> <> <> <000118> <Lost 647 replication updates of
              object -7971217480608673154. Re-fetching secondary.>
              ####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2> <ExecuteThread:
              '1' for queue: 'Replication'> <> <> <000118> <Lost 648 replication updates of
              object -7971217480608673154. Re-fetching secondary.>
              ####<Aug 5, 2003 7:06:11 AM GMT> <Warning> <NT Performance Pack> <HQBUSA55> <enrolem2>
              <ExecuteThread: '1' for queue: 'default'> <> <> <000000> <Already cleaned up fd:
              '-1', socket: 'Socket[addr=hq3105.nestle.com/141.122.142.71,port=1534,localport=7778]'>
              ####<Aug 5, 2003 7:51:26 AM GMT> <Error> <EJB> <HQBUSA55> <enrolem2> <ExecuteThread:
              '5' for queue: 'default'> <> <> <010024> <Error during passivation: java.io.NotSerializableException:
              com.sun.jndi.ldap.LdapCtx
                   at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
                   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
                   at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
                   at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
              Is this a known issue? Is there any service pack or fix pack for the same?
              Please give me your suggestions.
              Thanks,
              Bhumika
              

              There are known issues with SFSBs not being serializble in 6.1. see if you can
              upgrade or increase cache size.
              S
              "Bhumika Nagarsekar" <[email protected]> wrote:
              >
              >Hi,
              >
              >I have a Weblogic 6.0 SP2 clustered setup. If I change the deployment
              >descriptor
              >and set the
              >max-beans-in-cache to 2 and create 3 instances of a stateful ejb, it
              >gets passivated
              >without any exceptions, but if the application runs for a long time,
              >passivation
              >errors occur.
              >
              >I get the following exceptions:
              >####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2>
              ><ExecuteThread:
              >'1' for queue: 'Replication'> <> <> <000118> <Lost 647 replication updates
              >of
              >object -7971217480608673154. Re-fetching secondary.>
              >####<Aug 4, 2003 4:04:36 PM GMT> <Info> <Cluster> <HQBUSA55> <enrolem2>
              ><ExecuteThread:
              >'1' for queue: 'Replication'> <> <> <000118> <Lost 648 replication updates
              >of
              >object -7971217480608673154. Re-fetching secondary.>
              >####<Aug 5, 2003 7:06:11 AM GMT> <Warning> <NT Performance Pack> <HQBUSA55>
              ><enrolem2>
              ><ExecuteThread: '1' for queue: 'default'> <> <> <000000> <Already cleaned
              >up fd:
              >'-1', socket: 'Socket[addr=hq3105.nestle.com/141.122.142.71,port=1534,localport=7778]'>
              >
              >####<Aug 5, 2003 7:51:26 AM GMT> <Error> <EJB> <HQBUSA55> <enrolem2>
              ><ExecuteThread:
              >'5' for queue: 'default'> <> <> <010024> <Error during passivation: java.io.NotSerializableException:
              >com.sun.jndi.ldap.LdapCtx
              >     at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1143)
              >     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:361)
              >     at java.io.ObjectOutputStream.outputClassFields(ObjectOutputStream.java:1822)
              >     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:475)
              >
              >Is this a known issue? Is there any service pack or fix pack for the
              >same?
              >Please give me your suggestions.
              >
              >Thanks,
              >Bhumika
              

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

  • Form-based authentication problem with weblogic

    Hi Everyone,
    The following problem related to form-based authentication
    was posted one week ago and no reponse. Can someone give it
    a shot? One more thing is added here. When I try it on J2EE
    server and do the same thing, I didn't encounter this error
    message, and I am redirected to the homeage.
    Thanks.
    -John
    I am using weblogic5.1 and RDBMSRealm as the security realm. I am having the following problem with the form-based authentication login mechanism. Does anyone have an idea what the problem is and how to solve it?
    When I login my application and logout as normal procedure, it is OK. But if I login and use the browser's BACK button to back the login page and try to login as a new user, I got the following error message,
    "Form based authentication failed. Could not find session."
    When I check the LOG file, it gives me the following message,
    "Form based authentication failed. One of the following reasons could cause it: HTTP sessions are disabled. An old session ID was stored in the browser."
    Normally, if you login and want to relogin without logout first, it supposes to direct you to the existing user session. But I don't understand why it gave me this error. I also checked my property file, it appears that the HTTP sessions are enabled as follows,
    weblogic.httpd.session.enable=true

    Hi...
    Hehe... I actually did implement the way you implement it. My login.jsp actually checks if the user is authenticated. If yes, then it will forward it to the home page. On the other hand, I used ServletAuthentication to solve the problem mentioned by Cameron where Form Authentication Failed usually occurs for the first login attempt. I'm also getting this error occasionally. Using ServletAuthentication totally eliminates the occurence of this problem.
    I'm not using j_security_check anymore. ServletAuthentication does all the works. It also uses RDBMSRealm to authenticate the user. I think the biggest disadvantage I can see when using ServletAuthentication is that the requested resource will not be returned after authentication cause the page returned after authenticating the user is actually hard coded (for my case, it's the home.jsp)
    cheers...
    Jerson
    "John Wang" <[email protected]> wrote:
    >
    Hi Jerson,
    I tried your code this weekend, it didn't work in my case. But
    I solved my specific problem other way. The idea behind my problem is that the user tries to relogin when he already logs in. Therefore, I just redirect the user into another page when he is getting the login page by htting the BACK button, rather than reauthenticate the user as the way you did.
    But, I think your idea is very helpful if it could work. Problems such multiple concurrence logins can be solved by pre-processing.
    In your new code, you solved the problem with a new approach. I am just wondering, do you still implement it with your login.jsp file? In other word, your action in login.jsp is still "Authenticate"? Where do you put the URL "j_security_check"?
    Thanks.
    -John
    "Jerson Chua" <[email protected]> wrote:
    I've solved the problem by using ServletAuthentication. So far I'm not getting the error message. One of the side effects is that it doesn't return the requested URI after authentication, it will always return the home page.
    Jerson
    package com.cyberj.catalyst.web;
    import weblogic.servlet.security.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    public class Authenticate extends HttpServlet {
    private ServletAuthentication sa = new ServletAuthentication("j_username", "j_password");
    public void doPost(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, java.io.IOException {
    int authenticated = sa.weak(request, response);
    if (authenticated == ServletAuthentication.NEEDS_CREDENTIALS ||
    authenticated == ServletAuthentication.FAILED_AUTHENTICATION) {
    response.sendRedirect("fail_login.jsp");
    } else {
    response.sendRedirect("Home.jsp");
    public void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, java.io.IOException {
    doPost(request, response);
    "Jerson Chua" <[email protected]> wrote:
    The problem is still there even if I use page redirection. Grrr... My boss wants me to solve this problem so what are the alternatives I can do? Are there any other ways of authenticating the user? In my web tier... I'm using isUserInRole, getRemoteUser and the web tier actually connects to EJBs. If I implement my custom authentication, I wouldn't be able to use this functionalities.
    Has anyone solved this problem? I've tried the example itself and the same problem occurs.
    Jerson
    "Cameron Purdy" <[email protected]> wrote:
    Jerson,
    First try it redirected (raw) to see if that indeed is the problem ... then
    if it works you can "fix" it the way you want.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "Jerson Chua" <[email protected]> wrote in message
    news:[email protected]...
    Hi...
    Thanks for your suggestion... I've actually thought of that solution. Butusing page redirection will expose the user's password. I'm thinking of
    another indirection where I will redirect it to another servlet but the
    password is encrypted.
    What do you think?
    thanks....
    Jerson
    "Cameron Purdy" <[email protected]> wrote:
    Maybe redirect to the current URL after killing the session to let the
    request clean itself up. I don't think that a lot of the request (such
    as
    remote user) will be affected by killing the session until the nextrequest
    comes in.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "Jerson Chua" <[email protected]> wrote in message
    news:[email protected]...
    Hello guys...
    I've a solution but it doesn't work yet so I need your help. Because
    one
    of the reason for getting form base authentication failed is if an
    authenticated user tries to login again. For example, the one mentionedby
    John using the back button to go to the login page and when the user logsin
    again, this error occurs.
    So here's my solution
    Instead of submitting the page to j_security_check, submit it to a
    servlet
    which will check if the user is logged in or not. If yes, invalidates its
    session and forward it to j_security_check. But there's a problem in this
    solution, eventhough the session.invalidate() (which actually logs theuser
    out) is executed before forwarded to j_security_check, the user doesn't
    immediately logged out. How did I know this, because after calling
    session.invalidate, i tried calling request.RemoteUser() and it doesn't
    return null. So I'm still getting the error. What I want to ask you guyis
    how do I force logout before the j_security_check is called.
    here's the code I did which the login.jsp actually submits to
    import javax.servlet.*;
    import javax.servlet.http.*;
    import java.io.*;
    public class Authenticate extends HttpServlet {
    public void doPost(HttpServletRequest request, HttpServletResponseresponse)
    throws ServletException, java.io.IOException {
    if (request.getRemoteUser() != null) {
    HttpSession session = request.getSession(false);
    System.out.println(session.isNew());
    session.invalidate();
    Cookie[] cookies = request.getCookies();
    for (int i = 0; i < cookies.length; i++) {
    cookies.setMaxAge(0);
    getServletContext().getRequestDispatcher("/j_security_check").forward(reques
    t, response);
    public void doGet(HttpServletRequest request, HttpServletResponseresponse)
    throws ServletException, java.io.IOException {
    doPost(request, response);
    let's help each other to solve this problem. thanks.
    Jerson
    "Jerson Chua" <[email protected]> wrote:
    I thought that this problem will be solved on sp6 but to my
    disappointment, the problem is still there. I'm also using RDBMSRealm,same
    as John.
    Jerson
    "Cameron Purdy" <[email protected]> wrote:
    John,
    1. You are using a single WL instance (i.e. not clustered) on that
    NT
    box
    and doing so without a proxy (e.g. specifying http://localhost:7001),
    correct?
    2. BEA will pay more attention to the problem if you upgrade to SP6.If
    you don't have a reason NOT to (e.g. a particular regression), then
    you
    should upgrade. That will save you one go-around with support: "Hi,I
    am
    on SP5 and I have a problem.", "Upgrade to SP6 to see if that fixes
    it.
    Call back if that doesn't work."
    3. Make sure that you are not doing anything special before or after
    J_SECURITY_CHECK ... make sure that you have everything configuredand
    done
    by the book.
    4. Email BEA a bug report at [email protected] ... see what they say.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "John Wang" <[email protected]> wrote in message
    news:[email protected]...
    Cameron,
    It seems to me that the problem I encountered is different a little
    from
    what you have, evrn though the error message is the same eventually.
    Everytime I go through, I always get that error.
    I am using weblogic5.1 and sp5 on NT4.0. Do you have any solutions
    to
    work
    around this problem? If it was a BUG as you
    pointed out, is there a way we can report it to the Weblogic
    technical support and let them take a look?
    Thnaks.
    -John
    "Cameron Purdy" <[email protected]> wrote:
    John,
    I will verify that I have seen this error now (after having read
    about it
    here for a few months) and it had the following characteristics:
    1) It was intermittent, and appeared to be self-curing
    2) It was not predictable, only seemed to occur at the first
    login
    attempt,
    and may have been timing related
    3) This was on Sun Solaris on a cluster of 2 Sparc 2xx's; the
    proxy
    was
    Apache (Stronghold)
    4) After researching the newsgroups, it appears that this "bug"
    may
    have gone away temporarily (?) in SP5 (although Jerson Chua
    <[email protected]> mentioned that he still got it in SP5)
    I was able to reproduce it most often by deleting the tmpwar and
    tmp_deployments directories while the cluster was not running,
    then
    restarting the cluster. The first login attempt would fail(roughly
    90%
    of
    the time?) and that server instance would then be ignored by the
    proxy
    for a
    while (60 seconds?) -- meaning that the proxy would send all
    traffic,
    regardless of the number of "clients", to the other server in thecluster.
    As far as I can tell, it is a bug in WebLogic, and probably has
    been
    there
    for quite a while.
    Peace,
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "John Wang" <[email protected]> wrote in message
    news:[email protected]...
    Hi Everyone,
    The following problem related to form-based authentication
    was posted one week ago and no reponse. Can someone give it
    a shot? One more thing is added here. When I try it on J2EE
    server and do the same thing, I didn't encounter this error
    message, and I am redirected to the homeage.
    Thanks.
    -John
    I am using weblogic5.1 and RDBMSRealm as the security realm. I
    am
    having
    the following problem with the form-based authentication login
    mechanism.
    Does anyone have an idea what the problem is and how to solve it?
    When I login my application and logout as normal procedure, it
    is
    OK.
    But
    if I login and use the browser's BACK button to back the login
    page
    and
    try
    to login as a new user, I got the following error message,
    "Form based authentication failed. Could not find session."
    When I check the LOG file, it gives me the following message,
    "Form based authentication failed. One of the following reasons
    could
    cause it: HTTP sessions are disabled. An old session ID was stored
    in
    the
    browser."
    Normally, if you login and want to relogin without logout first,
    it
    supposes to direct you to the existing user session. But I don'tunderstand
    why it gave me this error. I also checked my property file, it
    appears
    that
    the HTTP sessions are enabled as follows,
    weblogic.httpd.session.enable=true

  • 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

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • 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 :-)
              

Maybe you are looking for