Xslt with weblogic 5.1 sp9???

hello,
i can't start wlserver, if i put the xerces.jar on the first position of the
weblogic-classpath. if i don't do it, it runs fine.
the exception message is:
java.lang.NoClassDefFoundError: com/sun/xml/tree/XmlDocument
at
weblogic.ejb.internal.EJBManagerImpl.deploy(EJBManagerImpl.java:309)
at
weblogic.ejb.internal.EJBManagerImpl.deployBeans(EJBManagerImpl.java:644)
at
weblogic.ejb.internal.EJBManagerImpl.<init>(EJBManagerImpl.java:239)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1313)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:832)
at weblogic.Server.startServerDynamically(Server.java:131)
at weblogic.Server.main(Server.java:92)
at weblogic.Server.main(Server.java:58)
i think weblogic can't handle the deployment descriptors.
thx for help kai

i forget to say, that the old lotus xsl processor runs fine, but my problem
is to run the new one.

Similar Messages

Wlconsole with weblogic 5.1 sp9

Hello everyone.
I have installed Weblogic 5.1 SP9. Now wlconsolew doesn't work as it is
looking for the old registry key. How does one make wlconsolew work with a
service packed Weblogic?
Thanks.
Andrew Horton
Open Business Exchange
[email protected]
Tel: +44 (0) 20 7947 2150
Mobile: +44 (0) 7973 737495
Fax: +44 (0) 20 7947 2168
www.obexchange.com

Hi.
Be sure to add the service pack to the console's classpath as well.
Regards,
Michael
Andrew Horton wrote:
Hello everyone.
I have installed Weblogic 5.1 SP9. Now wlconsolew doesn't work as it is
looking for the old registry key. How does one make wlconsolew work with a
service packed Weblogic?
Thanks.
Andrew Horton
Open Business Exchange
[email protected]
Tel: +44 (0) 20 7947 2150
Mobile: +44 (0) 7973 737495
Fax: +44 (0) 20 7947 2168
www.obexchange.com--
Michael Young
Developer Relations Engineer
BEA Support

Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2

Hello everybody,
          I get the error given below when calling a JSP in a WebLogic
          application which seems to work fine in all other (non-JSP) parts:
          java.lang.NullPointerException:
               at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
               at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
               at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
               at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
               at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
               at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
          Compiled Code)
               at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
          Code)
               at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
               at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
               at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
               at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
               at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
               at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
          Code)
          I know that this error has been reported more than once in these
          discussion groups, and all people who solved it say
          - that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
          1.2.2
          - that it may also be caused by bad jsp code
          But in my case, it has to be another reason, because
          - I am using jdk 1.2.2
          - the same JSP file is running withour errors on WebLogic 6
          I wonder if it could have something to do with the operating system:
          the parsing error is produced on a Windows version of WL 5.1, while my
          WL 6 which doesn't cause errors is running with Linux.
          Many thanks in advance for any help,
          Eckhard Beisswenger


Once again me!
          After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
          http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
          The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.

Weblogic 5.1 SP9 problems with MAC OS 9 w/ MRJ 2.2.5 [InterruptedIOException]

Hello all,
We're having a problem with one of the beans running on our WebLogic server.
A quick summary:
The application is a standalone java application that
interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
The clients are a mix of Windows machines and Mac OS 9 (with OS X
coming down the line, but that is not feasible at this time
to consider a massive upgrade). Due to the limitations
of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
Mac and JRE 1.1.9 on the Windows machines.
The general flow of data is a request is made from the client app
to the WebLogic bean. The bean calls another class method which
retrieves data from the the backend database (Sybase or SQL Server 2000).
We've verified that the data comes back from the query, is placed
in an array, and is in the same state when the EJB prepares to 'return'
the data to the client. This works as expected on the Windows machines,
however, every so often, the Macs will give an
InterruptedIOException: send timed out error. Once the server times
out (after 240 seconds), the client can continue until the next
error.
A few additional pieces of info.
The data returned is an array, but there isn't any consistancy to the
size of the data set. Some will be single element arrays while others
will have 8-10 elements. The amount of data in each element is only
a string of a couple hundred characters, so it is not a large data
stream. Systems on the same network segment can go for a while (sometimes
going on 10 minutes) before getting this error, while remote offices
going over slower links will get an immediate InteruptedIOException.
We have a process in place that if it catches an InterruptedIOException
it loops and tries the procedure again, however a 4 minute wait
between loops just isn't acceptable. We tried lowering this by
placing the following lines into our weblogic.properties file:
weblogic.system.periodLength=15
weblogic.system.idlePeriodsUntilTimeout=4
However, this has had zero impact on the timeout. Are there programatic
ways of changings these values? Or to force a blocking connection that
will force the data pipe to stay open? Has anyone had any insight into
any similar problems? Unfortunately, due to the size of the company,
the environment is fixed, and no mass upgrades are a vaiable option.
Thanks all!
Cliff

Hi Cliff,
it seems as if we have a similar problem within WLS51sp13 and a Java
Client (Servlet within Tomcat). We found that an EJB Stub within the
Client App has a 180s timeout, if the server socket didn't close
(Network problem or similar). I friend gave me a hint setting this
parameter on both sides, client and Server: It works. It seems as if the
server takes the bigger value of both values set.
Greetings,
schnaggy:-)
Cliff Wagner wrote:
Hello all,
We're having a problem with one of the beans running on our WebLogic server.
A quick summary:
The application is a standalone java application that
interfaces with a Weblogic 5.1 SP9 running on a Solaris box.
The clients are a mix of Windows machines and Mac OS 9 (with OS X
coming down the line, but that is not feasible at this time
to consider a massive upgrade). Due to the limitations
of the JVM for OS 9, we are forced to run MRJ 2.2.5 on the
Mac and JRE 1.1.9 on the Windows machines.
The general flow of data is a request is made from the client app
to the WebLogic bean. The bean calls another class method which
retrieves data from the the backend database (Sybase or SQL Server 2000).
We've verified that the data comes back from the query, is placed
in an array, and is in the same state when the EJB prepares to 'return'
the data to the client. This works as expected on the Windows machines,
however, every so often, the Macs will give an
InterruptedIOException: send timed out error. Once the server times
out (after 240 seconds), the client can continue until the next
error.
A few additional pieces of info.
The data returned is an array, but there isn't any consistancy to the
size of the data set. Some will be single element arrays while others
will have 8-10 elements. The amount of data in each element is only
a string of a couple hundred characters, so it is not a large data
stream. Systems on the same network segment can go for a while (sometimes
going on 10 minutes) before getting this error, while remote offices
going over slower links will get an immediate InteruptedIOException.
We have a process in place that if it catches an InterruptedIOException
it loops and tries the procedure again, however a 4 minute wait
between loops just isn't acceptable. We tried lowering this by
placing the following lines into our weblogic.properties file:
weblogic.system.periodLength=15
weblogic.system.idlePeriodsUntilTimeout=4
However, this has had zero impact on the timeout. Are there programatic
ways of changings these values? Or to force a blocking connection that
will force the data pipe to stay open? Has anyone had any insight into
any similar problems? Unfortunately, due to the size of the company,
the environment is fixed, and no mass upgrades are a vaiable option.
Thanks all!
Cliff

IPlanet Plug in For WebLogic 5.1 SP9

At the client site we are using PeopleSoft 8.3, Weblogic 5.1 SP9 with iPlanet proxy
servers. The client is using 5.1ps6a plugin. The application does not function
with this plug in. The client has another plugin 6.1sp4 with that WL5.1 Sp 9
gives NASAPI plugin errror that follows:
Message from the NSAPI plugin:
No backend server available for connection: timed out after 10 seconds.
Build date/time: Sep 18 2002 16:55:57
Change Number: 208523
My questions, do BEA has 5.1Sp9 plugin?
Why NSAPI plugin errors while using 6.1sp4 plugin?
What else would fix the problem:
Thanks

A first step will be to enable logging for the proxy plugin. You do
this by adding the line Debug=ON in the obj.conf server directive.
Verify your steps in the following doc:
http://www.weblogic.com/docs51/admindocs/nsapi.html
This Debug creates a file /tmp/wlproxy.log. This file will help you
troubleshoot the issue for proxy-plugin for the 5.1 and 6.1 instances.
Post the log file and lets see what happens...
Good luck,
abdul
[email protected]
"Vidya Sagar" <[email protected]> wrote in message news:<3ea42831$[email protected]>...
At the client site we are using PeopleSoft 8.3, Weblogic 5.1 SP9 with iPlanet proxy
servers. The client is using 5.1ps6a plugin. The application does not function
with this plug in. The client has another plugin 6.1sp4 with that WL5.1 Sp 9
gives NASAPI plugin errror that follows:
Message from the NSAPI plugin:
No backend server available for connection: timed out after 10 seconds.
Build date/time: Sep 18 2002 16:55:57
Change Number: 208523
My questions, do BEA has 5.1Sp9 plugin?
Why NSAPI plugin errors while using 6.1sp4 plugin?
What else would fix the problem:
Thanks

Help needed with weblogic portal and documentum.

hi guys,
i have a project in which i have to use documentum with site caching services with weblogic portal 8.1. the html and xml pages will be stored in documentum and the metadata in oracle 8i and xslt will be used for transformation.
Does anybody have any clue what api or things to use for this thing.
any help , tutorial, links pointing to the solution will be helpful
thanks in advance
rajat

Ok, so it looks like I only need to call a startapplicaiton after the distribute to make this work.

Deploy web application in jbuilder 9 with weblogic 7 problem

when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
where options include:
-help Print this help message.
-version Print version information.
-adminurl <https://<server>:<port>> The URL of the administration server: default
http://localhost:7001
-user <user> A user other than the default of
"installadministrator"
-password <password> Specifies the password on the command line.
If this option is absent the user is
prompted.
-verbose Displays additional status during the
deployment process, including notifications
when the application is prepared and
activated on each target.
-debug Displays debug level messages to the standard
output.
-examples Display example usage of this tool.
-upload Causes the specified source file(s) to be
transferred to the adminstration server. This
is used when the Deployer tools is not being
used on the same machine as the adminstration
server and the user does not otherwise have
access to place the targeted files on the
adminstration server.
-delete_files Causes the server to remove the files that
are specified in the file list and leave the
application activated. This option is valid
only for unarchived web applications.
-remote Signals that the tools is not runnning on the
same machine as the adminstration server and
that the source path should be made passed
through unchanged as it represents the path
on the remote server.
-nostage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged and the
original source is be used.
-external_stage Sets the stagingMethod attribute on the
application mbean when it is created so that
the application will not be staged but the
value of the staging path will be used when
preparing the application.
-stage Sets the stagingMethod staging attribute on
the application when it is created so that
the application will always be staged. This
value will override the stagingMethod
attribute on any targeted servers.
-nowait Once the action is initiated the tool will
print the task id and exit. This is used to
initiate multiple tasks and then monitor them
later using the -list action.
-timeout <seconds> The maximum time in seconds to wait for the
completion of the deployment task. When the
time expires the current status is printed
and the program exits.
-source <archive file or directory> Location of the file or directory that
represents the enterprise component or
application tha is being (re)activated. If
the source file is relative it is relative to
the current directory, unless the -remote
option is used. To specify individual files
within an application for reployment or
addition list them at the end of the command
line.
-name <application name> The name of the application being deployed.
-targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
cluster names. Each target may be qualified
with a J2EE component name. This enables
different components of the archive to
deployed on different servers.
-id <task identifier> Optional client supplied unique identifier
for the deployment task. The id is first
specified to -activate, -deactivate,
-unprepare or -remove. It is then used later
as an argument to -cancel or -list.
-activate (Re)activates the <source> application on the
<targets> with the <name>.
-deactivate Deactivates the application <name> on the
<targets> leaving an staged application files
in a state where the may be quickly
reactivated.
-unprepare Deactivates and unloads classes for the
application <name> on the <targets> leaving
an staged application files in a state where
the may be quickly reloaded.
-remove Deactivates the application <name> on the
<target> and removes any files that were
staged for this application. If there are no
longer any targets for the application, the
associated configuration is completely
removed.
-cancel Atempts to cancel the task <id> if it is has
not yet completed.
-list Lists the target status of each task <id>
-deploy a convenient alias for activate.
-undeploy a convenient alias for unprepare.
Optionally a list of the specific files in the archive that are to be
redeployed may be specified. If a directory is specified the entire subtree is
redeployed.
Full documentation on this tool is available at:
http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
No actions was specified. Please specify one and only one of:
-activate, -deactivate, -cancel, -remove, -unprepare, or -list.
Type java weblogic.Deployer -examples for example usage.

you use "deploy" under DOS-Mode to deploy your web application?
i found some differences between "deploy" and "redeploy" function in jbuilder 9.
when i choose "deploy" ,jbuilder shows me the commond below:
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility
when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
WebLogic Application Deployment Utility

Crystal Report 9 connectivity with WebLogic 10.3.5

Hello,
Is the Crystal Report 9 certified with WebLogic 10.x? Currently WebLogic 8.x is in use. Trying to upgrade the WebLogic.
Thanks

What does this have to do with Database Connectivity?
An I doubt it, CR 9 is about 8 or 9 years old well before 10.3 was released. Check the Platforms PDF's for more info.
Don

Has anyone used JAAS with WebLogic?

Has anyone used JAAS with Weblogic? I was looking at their example, and I have a bunch of questions about it. Here goes:
Basically the problem is this: the plug-in LoginModule model of JAAS used in WebLogic (with EJB Servers) seems to allow clients to falsely authenticate.
Let me give you a little background on what brought me to this. You can find the WebLogic JAAS example (to which I refer below) in the pdf: http://e-docs.bea.com/wls/docs61/pdf/security.pdf . (I believe you want pages 64-74) WebLogic, I believe goes about this all wrong. They allow the client to use their own LoginModules, as well as CallBackHandlers. This is dangerous, as it allows them to get a reference (in the module) to the LoginContext's Subject and authenticate themselves (i.e. associate a Principal with the subject). As we know from JAAS, the way AccessController checks permissions is by looking at the Principal in the Subject and seeing if that Principal is granted the permission in the "policy" file (or by checking with the Policy class). What it does NOT do, is see if that Subject
has the right to hold that Principal. Rather, it assumes the Subject is authenticated.
So a user who is allowed to use their own Module (as WebLogic's example shows) could do something like:
//THEIR LOGIN MODULE (SOME CODE CUT-OUT FOR BREVITY)
public class BasicModule implements LoginModule
private NameCallback strName;
private PasswordCallback strPass;
private CallbackHandler myCB;
private Subject subj;
         //INITIALIZE THIS MODULE
           public void initialize(Subject subject, CallbackHandler callbackHandler, Map sharedState, Map options)
                  try
                       //SET SUBJECT
                         subj = subject; //NOTE: THIS GIVES YOU REFERENCE
TO LOGIN CONTEXT'S SUBJECT
                                                 // AND ALLOWS YOU TO PASS
IT BACK TO THE LOGIN CONTEXT
                       //SET CALLBACKHANDLERS
                         strName = new NameCallback("Your Name: ");
                         strPass = new PasswordCallback("Password:", false);
                         Callback[] cb = { strName, strPass };
                       //HANDLE THE CALLBACKS
                         callbackHandler.handle(cb);
                  } catch (Exception e) { System.out.println(e); }
     //LOG THE USER IN
       public boolean login() throws LoginException
          //TEST TO SEE IF SUBJECT HOLDS ANYTHING YET
          System.out.println( "PRIOR TO AUTHENTICATION, SUBJECT HOLDS: " +
subj.getPrincipals().size() + " Principals");
          //SUBJECT AUTHENTICATED - BECAUSE SUBJECT NOW HOLDS THE PRINCIPAL
           MyPrincipal m = new MyPrincipal("Admin");
           subj.getPrincipals().add(m);
           return true;
         public boolean commit() throws LoginException
               return true;
    }(Sorry for all that code)
I tested the above code, and it fully associates the Subject (and its principal) with the LoginContext. So my question is, where in the process (and code) can we put the LoginContext and Modules so that a client cannot
do this? With the above example, there is no Security. (a call to: myLoginContext.getSubject().doAs(...) will work)
I think the key here is to understand JAAS's plug-in security model to mean:
(Below are my words)
The point of JAAS is to allow an application to use different ways of authenticating without changing the application's code, but NOT to allow the user to authenticate however they want.
In WebLogic's example, they unfortunately seem to have used the latter understanding, i.e. "allow the user to authenticate however they want."
That, as I think I've shown, is not security. So how do we solve this? We need to put JAAS on the server side (with no direct JAAS client-side), and that includes the LoginModules as well as LoginContext. So for an EJB Server this means that the same internal permission
checking code can be used regardless of whether a client connects through
RMI/RMI-IIOP/JEREMIE (etc). It does NOT mean that the client gets to choose
how they authenticate (except by choosing YOUR set ways).
Before we even deal with a serialized subject, we need to see how JAAS can
even be used on the back-end of an RMI (RMI-IIOP/JEREMIE) application.
I think what needs to be done, is the client needs to have the stubs for our
LoginModule, LoginContext, CallBackHandler, CallBacks. Then they can put
their info into those, and everything is handled server-side. So they may
not even need to send a Subject across anyways (but they may want to as
well).
Please let me know if anyone sees this problem too, or if I am just completely
off track with this one. I think figuring out how to do JAAS as though
everything were local, and then putting RMI (or whatever) on top is the
first thing to tackle.

Send this to:
newsgroups.bea.com / security-group.

EJB 3.0 MDB deployment issue with weblogic 10.0

Hi there,
I am new to MDB EJB and right now I am using the EJB 3.0 with weblogic server 10.0. I am using Eclipse 3.4 for development.
After developing the MDB from eclipse I export the EAR from eclipse and deploy it in weblogic. When I try to start the deployed EAR it gives me following error.
weblogic.application.ModuleException: Exception preparing module: EJBModule(Message.jar)
Unable to deploy EJB: MessageBean from Message.jar:
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:399)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     Truncated. see log file for complete stacktrace
[EJB:011113]Error: The Message Driven Bean 'MessageBean(Application: MessageEAR, EJBComponent: Message.jar)', does not have a message destination configured. The message destination must be set using a message-destination-link, destination-resource-link, destination-jndi-name or a resource-adapter-jndi-name.
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.ensureMDBHasDestinationConfigured(MessageDrivenBeanInfoImpl.java:1811)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.prepare(MessageDrivenBeanInfoImpl.java:1011)
     at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:997)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1273)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:372)
     Truncated. see log file for complete stacktrace
>
Any help really appreciated. It's too urgent.
Thanks in advance,
Piyush

here is the code for my bean.
package com.ups;
import java.util.logging.Logger;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.EJBException;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;
* Message-Driven Bean implementation class for: MessageBean
@MessageDriven(
          activationConfig = { @ActivationConfigProperty(
                    propertyName = "destinationType", propertyValue = "javax.jms.Queue"
public class MessageBean implements MessageListener {
     private MessageDrivenContext mdc;
* Default constructor.
public MessageBean() {
// TODO Auto-generated constructor stub
* @see MessageListener#onMessage(Message)
public void onMessage(Message message) {
     TextMessage tmsg = null;
try {
tmsg = (TextMessage) message;
System.out.println("MESSAGE BEAN: Message received: " + tmsg.getText( ));
System.out.println ("The onMessage() is called");
} catch (JMSException e) {
e.printStackTrace( );
mdc.setRollbackOnly( );
catch (Throwable th) {
th.printStackTrace();
public void ejbRemove( )throws EJBException{
     System.out.println("ejbRemove() is executed >>>>>>>");
I have configured my JMS Distributed queue in the Weblogic.
If possible please provide more details so that I can get rid of this error as soon as possible.
Thanks for reply.
Piyush

Security violation exception with Weblogic cluster installation on OIm 9.1

Hi,
I have OIM9.1 installed on weblogic 8.1 SP4 in clustered environment, which more often than not seems to work fine. But some time I get following exception on server console/log file which causes certain provisioning task to be rejected...
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: javax.ejb.AccessLocalException: [EJB:010160]Security Violation: User: 'xelsysad
m' has insufficient permission to access EJB: type=<ejb>, application=Xellerate, module=xl
DataObjectBeans.jar, ejb=tcFormInstanceOperations, method=create, methodInterface=LocalHom
e, signature={}.
at weblogic.ejb20.internal.MethodDescriptor.checkMethodPermissionsLocal(MethodDesc
riptor.java:486)
at weblogic.ejb20.internal.StatelessEJBLocalHome.create(StatelessEJBLocalHome.java
:80)
at com.thortech.xl.ejb.beans.tcFormInstanceOperations_2j82mm_LocalHomeImpl.create(
tcFormInstanceOperations_2j82mm_LocalHomeImpl.java:93)
... 126 more
ERROR,19 Dec 2008 14:20:03,752,[XELLERATE.APIS],Class/Method: tcBaseUtilityClient/getLocal
Interface encounter some problems: {1}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.in
Problem is, I get this exception only 4 out of 6 times (when it is least expected). I have googled, and tried all possible means but have't been able to resolve it. One more thing I am sure of is, it only comes with Weblogic installation not with Jboss. So there should be some configuration issue with weblogic installation.
Any suggestions would be useful...

No Response???
Where are the good guys??

OAM (10.1.4.3) Integration with WebLogic App Server (10.3.0 or below)

Hi All,
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
And
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.

Hi,
This is how the integration goes with different versions of WLS and OAM.
There is oamAuthnProvider.jar available with OAM 10.1.4.3 downloads. So it provides the assertion functionality.
Can I use OAM 10.1.4.3 (Authentication Provider & Identity Asserter) to implement SSO with weblogic App Server 10.3.0 or below?
Mahendra: Yes
OAM 10.1.4.3 Authentication Provider & Identity Asserter is the recommended way to configure SSO with Web Logic App server 10.3.1 ( Oracle Middleware 11g).
Mahendra: Yes, this is the recommended and easy approach.
OAM 10.1.4.2 uses WebLogic SSPI to configure SSO between OAM 10g and WebLogic App Server 10.3.0 or below.
Mahendra: Yes, older version of OAM uses SSPI connector installation.
HTH.
Mahendra.

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

Error while using TXDataSource with Weblogic 6.1 & Oracle 8.1.6

Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver. These are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I am not sure where the problem is as I have configured Connection Pool and TXDataSource as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager error has occured in the transaction branch start() failed on resource 'myXAPool' Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

Hi Sudhir,
If you do not know if upgrade or not, have a look here :
http://e-docs.bea.com/wls/docs61/notes/bugfixes2.html
Note that at the end of June SP3 will be released...
Sergi
"Sudhir Babu" <[email protected]> wrote:
>
Hi Sergi,
Thanks a lot for the class file, I figured out what the problem was. Actually
the
database version I was working with was 8.0.6.0. The Oracle driver doesn't
work with
this but the JDriver worked. This is the output of running CheckDriver..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8 Enterprise Edition Release 8.0.6.0.0 -
Production
With the Partitioning and Objects options
PL/SQL Release 8.0.6.0.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.1.0
Then I tried on using the Oracle Driver on another instance which has the
version
8.1.7.1.0 and it worked. The JDriver and Oracle driver both work with this
database.
The output of CheckDriver for this Oracle instance is..
DatabaseProductName : Oracle
DatabaseProductVersion : Oracle8i Enterprise Edition Release 8.1.7.1.0 -
Production
With the Partitioning option
JServer Release 8.1.7.1.0 - Production
DriverName : Oracle JDBC driver
DriverVersion : 8.1.7.0.0
By the way I am working on WLS 6.1 SP1. What is the advantage of SP2 ? Should
I upgrade
Thanks once again,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir ,
JDriver works well, you can work with it.
Just for curiosity, can you run the class I attached using the "exact"classpath
of your WL instance (with Oracle drivers in front of weblogic.jar) ? What
is the
output ?
On which platform are you running your WLSP2 ?
Thanks
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
I just checked the things you mentioned. The connection pool starts correctly
without
any errors. I also made sure SELECT previlege was granted to DBA_PENDING_TRANSACTIONS.
I do have the JAVA_XA package installed and it has EXECUTE permission
to
PUBLIC.
I actually tried using the Weblogic JDriver (weblogic.jdbc.oci.xa.XADataSource)
and
it works perfect without any issue. The only consideration is that itis
a Type 2
Driver and needs to have the Oracle Client installed. But right now Ido
have it
installed on the same machine.
Do you know any known issues with Weblogic JDriver. Do you think it'sa
good idea
to go with it ?
Thanks,
Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
does your connection pool start correctly ?
Check the setup of your Oracle server too:
1) grant select on DBA_PENDING_TRANSACTIONS table to PUBLIC
2) package JAVA_XA installed (with grant execute to PUBLIC)
Sergi
"Sudhir Babu" <[email protected]> wrote:
Hi Sergi,
Thanks for the response. I downloaded the driver for 8.1.7 from Oraclesite
and put
it in classpath in front of weblogic.jar. I still get the same problem.
Is there
another location where we can download the Oracle driver with the bug
fixed
Regards, Sudhir.
"Sergi Vaz" <[email protected]> wrote:
Hi Sudhir,
I think you are using Oracle JDBC drivers 8.1.6.
They have a bug, they do not accept a foreign XID.
Use 8.1.7 or higher to solve this problem.
Sergi
Sudhir Babu <[email protected]> wrote:
Hi,
I am using Weblogic 6.1 and Oracle 8.1.6.
I have configured JDBC XA Connection Pool with Oracle thin driver.
These
are my settings...
Connection Pool:
Name - myXAPool
URL - jdbc:oracle:thin:@myServer:1521:myDb
DriverClassname - oracle.jdbc.xa.client.OracleXADataSource
TXDataSource:
Name - myXADS
JNDIName - myXADS
PoolName - myXAPool
I get the following error when I try to lookup the datasource. I amnot
sure where the problem is as I have configured Connection Pool and
TXDataSource
as mentioned in the documentation.
java.sql.SQLException: XA error: XAER_RMERR : A resource manager errorhas
occured in the transaction branch start() failed on resource 'myXAPool'
Unexpected error during start for XAResource 'myXAPool': null
It would be really great if you can help me out.
Thanks in Advance,
Sudhir.

How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Xslt with weblogic 5.1 sp9???

Similar Messages

Maybe you are looking for