Castor with Weblogic 8.1 problem

Hi,
I am encountering problem using Castor with Weblogic 8.1.
I unmarshal XML files using Castor. My application works fine outside Weblogic,
but gives incorrect xml content when deployed.
My xml is like this :
<emrRoot>
<emrNode>
</emrNode>
</emrRoot>
When deployed in Weblogic, on parshing this document using Castor API, it shows
that there are 0 'emrNode' inside 'emrRoot'.
This is what the Weblogic parser is misinterpreting it as:
<?xml version="1.0" encoding="UTF-8"?>
<emr-root emr-node-count="0" emr-dynanode-count="0" valid="true"/>
Could someone pls help.
Thanks.
Regards,
Shafique.

Hi,
Generally this type of exception raised by a class or the serialization runtime when a class may not be serialized.The argument should be the name of the class.
You might be forgot to implement the serializable interface for the class in struts frame work.
check it properly.
Regards
Anilkumar kari

Similar Messages

JBuiler5Enterprise integrate with WebLogic 6 sp2 Problem?

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

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

Memory Leak with Weblogic 6.1

Hello everyone.
I need some help with a problem we are having with our application. It consists on Servlets, JMS with MDBs, Xml parsing...
Our application dequeues messages from an Oracle Queue and sends xml-text message to a servlet. It also receives xml-text and enqueues objects in an Oracle Queue.
And it also has access to Oracle Database (context tables, etc).
We are doing everything on Tru64 Unix (and our tests on Win 2000) and we are using WebLogic 6.1.
Our problem is that we have found that it seems that the garbage collector is not running well. I mean, with the time our system is degrading. The memory use increases. It seems to be a memory leak.
We have used a testing tool, OptimizeIt, and we have found that there are
objects that are increasing the use of memory. If we use the option 'java -verbose' we find that it seems to be Hash objects (HashMap, Hashtable) which are increasing the use of memory. In our code we are not using any hashtable nor any class that extends from it (we have deleted everyone).
Can it be due to a problem with WebLogic? A problem with JMS, queues, etc? A problem with JNDI?
Could anybody please help us?
Thanks in advanced.

Yes, we see that there are some entries of the type:
java/util/Hahstable$Entry
java/util/Hahstable
weblogic/jndi/Environment
This entries keep growing and growing with the time.
We have deleted all the Hashtable, Properties and all the kind of Collection objects. I guess WebLogic is using this objects in order to arrange our application runs.
Am I right? Do you know if we can do anything?
Thank you.

Weblogic 10.0 Problems with stripes/struts

When trying to deploy the sample application for the stripes framework on weblogic 10.0 I get the following error when deploying.
<Dec 3, 2009 12:16:51 PM CET> <Error> <HTTP> <BEA-101165>
<Could not load user defined filter in web.xml:
net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
Problem instantiating default configuration objects.I actually had to switch to using the Sun JDK to get this error. JRockit does not report it, and just fails when I try to use the application. The problem appear to be weblogic 10.0 specific. No problems with jetty or tomcat, and I've heard reports that it is resolved in weblogic 10.3. Have ayone come accross similar problems when using stripes/struts on weblogic 10.0, and found a solution to this? Is there a patch available for 10.0 than fix this?
Regards
Morten
PS: I have ommited the complete stack trace, since it is monstrously huge.

Guess I was wrong in thinking that this was an isolated weblogic 10.0 problem. I just downloaded weblogic 10.3 and tried to deploy the same application there, and the same error happened.
<03.des.2009 kl 15.12 CET> <Error> <HTTP> <BEA-101165>
<Could not load user defined filter in web.xml:
net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
Problem instantiating default configuration objects.
 at net.sourceforge.stripes.config.DefaultConfiguration.init(DefaultConfiguration.java:220)
 at net.sourceforge.stripes.config.RuntimeConfiguration.init(RuntimeConfiguration.java:272)
 at net.sourceforge.stripes.controller.StripesFilter.init(StripesFilter.java:125)
 at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:329)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 Truncated. see log file for complete stacktrace
java.lang.NullPointerException
 at java.io.FilterInputStream.read(FilterInputStream.java:116)
 at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
 at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
 at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
 at java.io.InputStreamReader.read(InputStreamReader.java:167)
 Truncated. see log file for complete stacktraceSo is there anyone out there with experience with struts/stripes, that can tell why this does not work? If you need to try this yourself, you can download the stripes sample application here:
http://sourceforge.net/projects/stripes/files/stripes/Stripes%201.5.2/stripes-1.5.2.zip/download
There is an example WAR called "stripes-examples.war" in the zip that is ready to be deployed.
Regards
Morten
PS: you still need to start weblogic with Sun JDK rather than JRockit to get the error. With JRockit the application simply fails when used.

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>
NOTE - The logger.debug() and logger.info() methods are not invoked because of the severity level to 'WARNING' in the console.
I would like to know why the Somehow the logger.isEnabledFor(Priority.DEBUG) is having a value of 'TRUE'.
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

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

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

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

JSP Refresh Problems with Weblogic 8.1

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

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

HOT deployment problem with WebLogic 5.1sp11

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

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

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

Castor with Weblogic 8.1 problem

Similar Messages

Maybe you are looking for