Problems in jolt 1.2 with weblogic 6.1

Hi,
I am trying configure a jolt pool connection on startup of weblogic server.
I am using weblogic 6.1, tuxedo 6.5 server y jolt 1.2.
JSL is started.
I have copy $WL_HOME/classes/bea/jolt/pool from weblogic 5.1 to weblogic 6.1
I have defined a jolt pool, a startup class and a shutdown class.
I have not any problem on weblogic startup:
<Jan 13, 2003 5:21:06 PM CET> <Info> <WebLogicServer> <Invoking startup class:
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp.startup(poolname=simpapp,appaddrlist=//69.51.23.140:13398,failoverlist=//69.51.23.140:13414,minpoolsize=1,maxpoolsize=15)>
<Jan 13, 2003 5:21:07 PM CET> <Info> <WebLogicServer> <bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
reports: Jolt Session Pool: simpapp initialized>
The problem is when a servlet try:
private SessionPoolManager b_mgr;
Environment env = new Environment();
Context ctx = env.getInitialContext();
b_mgr = (SessionPoolManager) ctx.lookup(SessionPoolManager.POOLMANAGER_NAME);
SessionPool session = (SessionPool) b_mgr.getSessionPool("simpapp");
The object session is always null.
Thx in advance

Shashi,
Tuxedo 6.5 needs a patch to run on later versions of Solaris or else the WSNAT_CAT:1008 or JOLT_CAT:1008 "Error: Could not establish listening address on network +netaddr+" message can occur.
The thread Could not establish listening address on network describes a similar problem with the WSL, and the ULOG in that thread also indicates "TUXEDO Version 6.5 SunOS 5.5.1".
Please obtain the latest rolling patch from Oracle support. (It would be even better to upgrade to a later release of Tuxedo, since Tuxedo 6.5 is past its end of life date on Solaris. Hopefully whatever compilation problems you are having with later Tuxedo releases can be resolved fairly easily.)
Regards,
Ed

Similar Messages

Problem integrating JProbe 4.0 with Weblogic 4.5.1

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

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

Problem while using PrepStmt.executeBach with Weblogic 6.0sp1 and

- I'm getting the same error when I use WLS 6.0 SP1 & thin driver. I'm not
getting this error when I use thin driver without WLS.
- This is definitely a bug in WLS. As a workaround put classes.zip {that
comes with oracle installation} before weblogic.jar in your classpath. This
way, classloader will load the oracle supplied classes & everything will
work smoothly
Manav
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]...
>
>
Ruta wrote:
Hi Joe
I tried using a java standlaone program using prep stmts and oracle thin
driver
and it works just fine.
So is this a bug with Weblogic? Finally connection pooling isapplication server's
responsibility, isnt it..
I am inlcined to conclude this coz connection pooling works fine withStatement.executeBatch()
but not with prepStatement.executeBatch()
How do I resolve this now.
Thanks
Ruta
...Does it not release the connectionOk. Now let me see the JDBC code example. I'll see what's up.
Joe
Joseph Weinstein <[email protected]> wrote:
The first thing you should do is to reduce the problem to the simplest
form.
Write a tiny standalone program that just uses the thin driver
directly,
and repeats the code you are trying to run. This will eliminateWebLogic
from the equation and see if it's an Oracle-only bug.
Joe
Ruta wrote:
Hi,
I am trying to do multiple inserts in a table using the
PreparedStatement
of JDBC2.0.
I am using a TxDataSource of Weblogic server with a thin driver
oracle
pool. I
am using the driver classes that come with the weblogic.jar.
The problem is as follows:
I can manage to succesfully do the executeBatch a few
times..Interestingly
it
executes as many no. of times as the Initial capacity(not even maxcapacity) of
my connection pool.
Then it gives me the following error:
java.sql.SQLException: java.sql.SQLException: Missing IN or OUT
parameter
at index::
1
at
weblogic.jdbc.rmi.SerialStatement.executeBatch(SerialStatement.java:394)
atcom.equitable.acs.common.ACSCtrlBean.saveSDECData(ACSCtrlBean.java:147)
atcom.equitable.acs.common.ACSCtrlBeanImpl.saveSDECData(ACSCtrlBeanImpl.java:1
10)
atcom.equitable.acs.common.ACSCtrlBeanEOImpl.saveSDECData(ACSCtrlBeanEOImpl.ja
va:30)
atcom.equitable.acs.common.ACSCtrlBeanEOImpl_WLSkel.invoke(ACSCtrlBeanEOImpl_W
LSkel.java:133)
atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)
atweblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
:128)
atweblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)
atweblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.
java:118)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
7)
atweblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
This Oracle error has error code 17041.. I could not find more infoon it, even
from the Oracle site.
I conclude that the connections are not getting relesed.
But i ahve written
con.close(); even
con=null; (out of desparation :) )
but still the connection is not released.
I am getting the connection in the saveSDECData method
I need to fix thsi problem ASAP..Any Help/Comments will be
appreciated..
Finally the most interesting part is :
executeBatch works perfectly fine with the Statement object..
so probably the culprit is the PreparedStatement implementation ofOracle..Can
anybody validate this pls
Regards
Ruta--
PS: Folks: BEA WebLogic is expanding rapidly, with both entry andadvanced
positions
for people who want to work with Java, XML, SOAP and E-Commerceinfrastructure
products.
We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and SanJose
CA.
Send resumes to [email protected]
PS: Folks: BEA WebLogic is expanding rapidly, with both entry and advancedpositions
for people who want to work with Java, XML, SOAP and E-Commerceinfrastructure products.
We have jobs at Nashua NH, Liberty Corner NJ, San Francisco and San JoseCA.
Send resumes to [email protected]

Problem in getting Time info with webLogic using Oracle Thin Driver

We have a servlet to store/retrieve date/time data from an Oracle 9i db using use the Oracle thin driver. Everyting is ok when run on JSDK2.1 servlet container or Tomcat. But when run under WebLogic 8.1, we have problem with time portion info, it is lost. After debuging, we found under WebLogic, the returned object type is a java.sql.Date which by definition has no time info, while in other servlet containers, it is a java.sql.Timestamp. Storing date/time data in a Date column is ok under WebLogic because we see the time portion data in the db table. We did not set anything about database/jdbc in WebLogic.
It would be greatly appreciated if someone can explain what effect WebLogic has on a servlet that has its own jdbc connection or how WebLogic could change data type from a jdbc sql statement.

That's a function of the JDBC driver, not the J2EE app server.
Sounds like maybe you're using the WebLogic 8.1 driver when you deploy with WL instead of the Oracle driver. You certainly can deploy with the Oracle driver. Go into the WL config manager and set it up to use the ojdbc14.jar instead.
%

Problem setting up APEX 4 with WebLogic and Oracle XE

I'm am trying to install and test Application Express 4 (latest version) on a brand new installation of Oracle WebLogic Server and Oracle XE.
I have followed the Installation Guide for APEX and have successfully installed all tables and scripts into my Oracle XE schema and am able to connect to the Application Express Workspace login page (http://localhost:8080/apex) but am not able to log in. All styles and images are missing.
I have followed the steps in the Application Express Listener Guide to install the Listener to my WebLogic deployments and have my i.war and apex.war files deployed but these apparently are not working. When I go to my WebLogic server and view the /apex/ListenerConfigure page I can see the page but get an HTTP 404 "Page Not Found" error and appears to be looking for the WLS's apex/apex directory.
Note: My Oracle XE / APEX setup is on a separate server than my WebLogic server.
Also, I see the APEX Listener file (apex-confix.xml) from the install zip file but I don't believe it is being used anywhere, as the documentation never told me what to do with it.
Any help would be awesome. Let me know what I can provide that I haven't. Thanks!

Thank you, I was able to use what you said as well as this information here: Installing Apex 4 on Oracle XE: Almost there, but no cigar yet!
Thank you for the help :)

Problem in web.xml file with weblogic server 8.1

Hi frnds,
I was deployed one Enterprise Application,it deploys successfully. But in server side thows Exeception in web.xml file.
Here the actual Exception
<HTTP> <BEA-101248> <[Application:
'G:\bea\user_projects\domains\mydomain\myserver\upload\jasmine.ear', Module: 'Ja
smine']: Deployment descriptor "web.xml" is malformed. Check against the DTD: or
g.xml.sax.SAXParseException: The content of element type "web-app" must match "(
icon?,display-name?,description?,distributable?,context-param*,filter*,filter-ma
pping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome
-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constra
int*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)". (line 61
, column 11).>
My web.xml file as follws....
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.4//EN"
"http://java.sun.com/dtd/web-app_2_4.dtd">
<web-app>
<display-name>Jasmine Applications</display-name>
<description>
Jasmine Applications
</description>
<servlet>
<servlet-name>LoginServlet</servlet-name>
<servlet-class>examples.LoginServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>ShowQuoteServlet</servlet-name>
<servlet-class>examples.ShowQuoteServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet>
<servlet-name>CatalogServlet</servlet-name>
<servlet-class>examples.CatalogServlet</servlet-class>
<init-param>
<param-name>java.naming.factory.initial</param-name>
<param-value>weblogic.jndi.WLInitialContextFactory</param-value>
</init-param>
<init-param>
<param-name>java.naming.provider.url</param-name>
<param-value>t3://localhost:7001</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>LoginServlet</servlet-name>
<url-pattern>/login/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>ShowQuoteServlet</servlet-name>
<url-pattern>/showQuote/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>CatalogServlet</servlet-name>
<url-pattern>/catalog/*</url-pattern>
</servlet-mapping>
<security-constraint>
<web-resource-collection>
<web-resource-name>My secure resources</web-resource-name>
<description>Resources to be placed under security control.</description>
<url-pattern>/private/*</url-pattern>
<url-pattern>/registered/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>guest</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>WebApp</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/error.jsp</form-error-page>
</form-login-config>
</login-config>

<security-role>
<description>The role allowed to access our content</description>
<role-name>guest</role-name>
</security-role>
</web-app>
pls give me a good solution this exception.. I tried lot..
Thanks in Advance
Regards
Priya

Your DOCTYPE references 2.4, it should be 2.3. WLS 8.1 supports J2EE 1.3 which was servlet 2.3.
Servlet 2.4 is part of J2EE 1.4 and is supported by WLS 9.0/9.1. Also it uses XML Schema not a DTD.
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Problem in Using Log4J with Weblogic 9.2

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

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

Problem with Weblogic Builder SP1

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

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

BIG5 Problem with WebLogic Express 6.1

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


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

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

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

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

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 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.Deployer in 8.1

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

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

Problem with Weblogic Commerce Personalization

We're having problem that we have not been able to pin point yet. Originally
when we started we were fine and our public view and personal view of
portals/portlets was o.k. Somehow within a day, before logging to the
personalization, in public view, all the colors are messed up and we're
missing the borders and titles. One of our developers was missing a portlet
until he logged on.
The problem may have to do with the directories specified in the properties
file. I'm guessing that there maybe loopholes in the instructions. The
folders that need to be specified in the properties, i.e. ../repository or
.../portlet, seems to be mixed up a bit.
Thanks for your help,
Farah

Hello Farah,
All of the problems you describe could have been caused by configuring your
portlets in the Administraton Tool to behave as you have described.
Particulary:
Somehow within a day, before logging to the
personalization, in public view, all the colors are messed up and we're
missing the borders and titles.Missing borders is caused by using the Admin Tool --> Portal Management -->
Colors tool to set "Portlet borders" to "off". Messed up colors could be caused
by someone using the admin tool to change colors for a group associated with
your user.
The JSP page for the titlebar is specified in the portlet definition, using
the Admin Tool --> Portal Management tool. You specify it when you create or
edit the properties for a portlet definition. A default titlebar.jsp is
supplied with WLCS 2.0. If you leave the Titlebar URL field blank, then no
titlebar will show up. If the path to the titlebar is incorrect, then it will
not show up. The path you specify is relative to the portal workingdir or the
portal repositorydir, which are specified in weblogic.properties. The portal
workingdir and repositorydir are relative to the documentRoot, also specified in
weblogic.properties. The server looks for portal files in the workingdir first
and then in the repositorydir.
The exampleportal ships with the titlebar.jsp in the
<install-dir>/server/public_html/portals/repository directory and you would fill
in the Titlebar URL field with "titlebar.jsp" because
documentRoot=<install-dir>/server/public_html and the exampleportal
repositorydir=/portals/repository/ (the exampleportal
workingdir=/portals/example/, and this directory does not come with the
installation)
One of our developers was missing a portlet
until he logged on.Such a portlet is called a "Login Required" portlet and it is specified in the
Admin Tool using the portlet definition tool.
Ture Hoefner
BEA Systems, Inc.
1655 Walnut Street; suite 200
Boulder, CO 80302
www.beasys.com

Problems with default domain with Weblogic 9.1 server

Hi,
Today I've been installing Weblogic 9.1 on our Red Hat (CentOS 4) server. After good experiences with BEA Weblogic local on my Windows machine I'm trying it on the server.
But after installing Weblogic and setting a default domain (automagicly generated) and trying to logon to the Admin Console I run into a problem.
When I login with false ID I it gives me a security alert and doesn't let me in, but if I login with the correct name+password it doesn't say anything but redirects me to the same login-page again...
I'm out of ideas on what it could be, and the biggest problem is that its the default domain it creates when I run the bin. Any ideas on what settings could do this?

Ah, found some more information!
When I try to login with the ip adres it works but not when I use the hostname. Now I have a good indication on where to look to solve the problem.
Edited by Redcodenl at 12/07/2006 3:36 AM

Problems in jolt 1.2 with weblogic 6.1

Similar Messages

Maybe you are looking for