Jconsole with weblogic 10.0 MP1

I am using weblogic 10.0 MP1 (dk150_11) and I need to generate heap dump
I tried JConsole but I couldn't find the HotSpotDiagnostic node where I can generate the heap dump
and there is no jmap.exe whith the jdk version
I know that I can generate heap dump when OutOfMemory error is thrown but that's not what I need
thanks

Re: Installation error: Weblogic Server 10.0 MP2

Similar Messages

Wants to start Jconsole with Weblogic 9.2 on Solaris 10

I wants to start JConsole with weblogic on Solaris 10 machine. I have added the following parameters in the startup script of the weblogic
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=7099 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
But while running "netstat -an" command, found that 7099 port is not listening.
TIA,
Tarun.

Hi Tarun,
A quick Google search on "weblogic jconsole" led me to this article :
http://e-docs.bea.com/wls/docs90/jmxinst/accesscust.html#1107229
It looks like you will need to use JMXServiceURL to connect to WebLogic Server's MBean Server.
Hope this helps
-Prashant

Problem with the NodeManager in Weblogic 10.0 MP1

Hi,
I have a problem starting the Nodemanager successfully. I have currently installed BEA Weblogic 10.0 MP1. The admin server is getting started successfully. When, I start the Nodemanager with the command:
startnodemanager -machine <hostname>, it neither gives the success message nor the error message. It comes to a stand still. Please see the below text, which appears on the Command prompt, when I run the nodemanager command.
Machine PUNITP128166D.ad.infosys.com
Listen Address: PUNITP128166D.ad.infosys.com
Listen Port: 8097
PID for D:\Ariba9r1\shared/bin/startNodeManager.cmd: 5980
D:\Ariba9r1\BuyerDev9r1\Server\bin>
D:\Ariba9r1\BuyerDev9r1\Server>set CLASSPATH=D:\BEA10\wlserver_10.0\server\lib\A
ribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib\tools.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;
D:\Ariba9r1\BuyerDev9r1\Server>chdir /d "D:\Ariba9r1\shared\nodemanager"
D:\Ariba9r1\shared\nodemanager>"D:\BEA10\jdk150_11\bin\java.exe" -client -Xms32m
-Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Xverify:none -classpath "D:\BE
A10\wlserver_10.0\server\lib\AribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib
\tools.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_1
0.0\server\lib\weblogic.jar;" -Dbea.home=D:\BEA10 -Djava.security.policy=D:\BEA1
0\wlserver_10.0\server\lib\weblogic.policy -DSavedLogsDirectory=D:\Ariba9r1\shar
ed\nodemanager\logs -DJavaHome=D:\BEA10\jdk150_11 -DTrustedHosts=D:\BEA10\wlserv
er_10.0\common\nodemanager\config\nodemanager.hosts -DListenAddress=PUNITP128166
D.ad.infosys.com -DListenPort=8097 -DReverseDnsEnabled=true -DLogToStderr=true -
DLogFile=D:\Ariba9r1\shared\nodemanager\nodemanager.log -DNodeManagerHome=D:\Ari
ba9r1\shared\nodemanager weblogic.NodeManager
After this, when I check the nodemanager status in Console, then the status appears as REACHABLE. Assuming, this to be the successfully message, I try to start the managed servers associated with the Machine/Server. But, it fails and there appears a message on the console with the status as 'Force Shutting Down' for this server.
When I check the logs, there seems to be some problem with the Nulll exception. Please see the below logs as it appears, its only a part of the logs
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040306> <JMS service is active now.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281003> <SAF Service has been initialized.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281002> <SAF Service has been started.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226120> <BEA-101128> <Initializing HTTP services.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101135> <buyerserver1 is the default Web server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101052> <[HttpServer (defaultWebserver) name: buyerserver1] Initialized>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101129> <Initializing the Web application container.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226198> <BEA-180046> <INFO: Logging service enabled.>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC license service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Task Manager instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC security service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Transaction service instantiated!>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <JMX> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226604> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://PUNITP128166D.ad.infosys.com:8050/jndi/weblogic.management.mbeanservers.runtime .>
####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226651> <BEA-000287> <Invoking startup class: ariba.j2ee.appserver.weblogic.Startup.startup(directory=D:\Ariba9r1\BuyerDev9r1\Server)>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227229> <BEA-000288> <ariba.j2ee.appserver.weblogic.Startup reports: Changed directory to D:\Ariba9r1\BuyerDev9r1\Server>
####<Jun 28, 2010 4:20:27 PM IST> <Info> <Management> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227244> <BEA-141187> <Java system properties are defined as follows:
ariba.server.home = D:\Ariba9r1\BuyerDev9r1\Server
awt.toolkit = sun.awt.windows.WToolkit
bea.home = D:\BEA10
file.encoding = Cp1252
file.encoding.pkg = sun.io
file.separator = \
java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.awt.windows.WPrinterJob
java.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBOracleJDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBDB2JDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBMssqlJDBC.zip;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes;D:\Ariba9r1\BuyerDev9r1\Server\classes\AribaJ2EE.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions;D:\BEA10\wlserver_10.0\server\lib\wls-api.jar
java.class.version = 49.0
java.endorsed.dirs = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed
java.ext.dirs = D:\BEA10\jdk150_11\jre\lib\ext
java.home = D:\BEA10\jdk150_11\jre
java.io.tmpdir = C:\DOCUME~1\suram_vishal\Local Settings\Temp\
java.library.path = D:\BEA10\jdk150_11\bin;.;C:\SYSROOT\system32;C:\SYSROOT;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\jdk150_11\bin;D:\BEA10\patch_wlw1001\profiles\default\native;D:\BEA10\patch_wls1001\profiles\default\native;D:\BEA10\wlserver_10.0\server\native\win\32;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\modules\org.apache.ant_1.6.5\bin;D:\BEA10\jdk150_11\jre\bin;D:\BEA10\jdk150_11\bin;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:/Ariba9r1/BuyerDev9r1/Server/bin/Win32;D:/Ariba9r1/BuyerDev9r1/Server/bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\Program Files\Java\jre1.5.0_06;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;D:\BEA10\wlserver_10.0\server\native\win\32\oci920_8;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\lib\Win32;D:\Ariba9r1\BuyerDev9r1\Server\internal\lib\Win32
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net
java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version = 1.5.0_11-b03
java.security.policy = D:\BEA10\wlserver_10.0\server\lib\weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.5
java.vendor = Sun Microsystems Inc.
java.vendor.url = http://java.sun.com/
java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
java.version = 1.5.0_11
java.vm.info = mixed mode
java.vm.name = Java HotSpot(TM) Client VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = Sun Microsystems Inc.
java.vm.version = 1.5.0_11-b03
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser
org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
os.arch = x86
os.name = Windows 2003
os.version = 5.2
path.separator = ;
sun.arch.data.model = 32
sun.boot.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\serializer.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xalan.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xercesImpl.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xml-apis.jar;D:\BEA10\jdk150_11\jre\lib\rt.jar;D:\BEA10\jdk150_11\jre\lib\i18n.jar;D:\BEA10\jdk150_11\jre\lib\sunrsasign.jar;D:\BEA10\jdk150_11\jre\lib\jsse.jar;D:\BEA10\jdk150_11\jre\lib\jce.jar;D:\BEA10\jdk150_11\jre\lib\charsets.jar;D:\BEA10\jdk150_11\jre\classes
sun.boot.library.path = D:\BEA10\jdk150_11\jre\bin
sun.cpu.endian = little
sun.desktop = windows
sun.io.unicode.encoding = UnicodeLittle
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = Cp1252
sun.management.compiler = HotSpot Client Compiler
sun.os.patch.level = Service Pack 2
user.country = US
user.dir = D:\Ariba9r1\BuyerDev9r1\Server
user.home = C:\Documents and Settings\suram_vishal
user.language = en
user.name = suram_vishal
user.timezone = Asia/Calcutta
vde.home = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\ldap
weblogic.Name = buyerserver1
weblogic.ReverseDNSAllowed = false
weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
weblogic.management.server = http://PUNITP128166D.ad.infosys.com:8099
weblogic.net.http.URLStreamHandlerFactory = ariba.util.net.URLStreamHandlerFactory
weblogic.nodemanager.ServiceEnabled = true
weblogic.security.SSL.ignoreHostnameVerification = true
weblogic.security.TrustKeyStore = DemoTrust
weblogic.system.BootIdentityFile = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\nodemanager\boot.properties
>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229510> <BEA-000365> <Server state changed to STANDBY>
####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229525> <BEA-000365> <Server state changed to STARTING>
####<Jun 28, 2010 4:20:29 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722229572> <BEA-149209> <Resuming.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230182> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_NEW to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Warning> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-101162> <User defined listener ariba.server.ormsserver.ServletContextListener failed: java.lang.NullPointerException.
java.lang.NullPointerException
     at java.util.Hashtable.put(Hashtable.java:396)
     at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)
     at ariba.j2ee.core.J2EEServer.initialize(J2EEServer.java:77)
     at ariba.j2ee.core.AribaServletContextListener.contextInitialized(AribaServletContextListener.java:25)
     at ariba.server.ormsserver.ServletContextListener.contextInitialized(ServletContextListener.java:26)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
####<Jun 28, 2010 4:20:35 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_ADMIN to STATE_PREPARED on server buyerserver1.>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
####<Jun 28, 2010 4:20:35 PM IST> <Alert> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Kindly help me in getting this resolved.
Thanks,
Vishal.

The error appears to come from the ariba code. I suggest asking them.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)

Need commpress-html-template with in weblogic.xml using Weblogic 10.0 MP1

Hi All,
Is there any way to use compress-html-template with weblogic.xml with in Weblogic 10.0 MP1.
I added this as current xsd reference for weblogic 10.0 MP1 but throws me error that it could unable to identify the library reference.
Here is the following XSD file /
(http://xmlns.oracle.com/weblogic/weblogic-javae/1.0/weblogic-javaee.xsd)
Any suggestion for this would be really great.
Regards,
Kal.
Edited by: kalyan Pasupuleti on Jul 20, 2009 11:07 AM

The error appears to come from the ariba code. I suggest asking them.
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:396)
at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)

JPA 2.0 in Weblogic 10.0 MP1

Hi there,
Is there a way to deploy a JPA 2.0 based application in a Weblogic 10.0 server?
We have an application that uses Spring 3.0.4, Hibernate 3.5.0.Final and Hibernate JPA 2.0.
Our customer is a major telecom operator that uses Weblogic 10.0 MP1 server with several applications already.
We tried the solutions for in http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic#DI_1:_Alternative_3:_Application_Level_Shared_Library_-InUse
All not working for us.
Thank you,
Ioan

Hi everyone,
I'm facing the same problem: Every JPA 2.0 implementation I tried to use doesn't work for me on Weblogic 10.0 and 10.3. It doesn't matter which JAP 2.0 vendor I use (I tried Hibernate and EclipseLink). I've used the tutorial user13348764 has mentioned and I tried to use one the the earfiles distributed here. I always get this error (for Hibernate I get this message with org.hibernate.ejb.HibernatePersistence):
Caused By: weblogic.deployment.EnvironmentException: Error processing persistence unit example of module enterprise: Error instantiating the Persistence Provider class org.eclipse.persistence.jpa.PersistenceProvider of the PersistenceUnit example: java.lang.ClassCastException: org.eclipse.persistence.jpa.PersistenceProvider cannot be cast to javax.persistence.spi.PersistenceProvider
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:344)
     at weblogic.deployment.PersistenceUnitInfoImpl.createEntityManagerFactory(PersistenceUnitInfoImpl.java:332)
     at weblogic.deployment.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:134)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.storeDescriptors(AbstractPersistenceUnitRegistry.java:336)
     at weblogic.deployment.AbstractPersistenceUnitRegistry.loadPersistenceDescriptors(AbstractPersistenceUnitRegistry.java:111)
     at weblogic.deployment.ModulePersistenceUnitRegistry.<init>(ModulePersistenceUnitRegistry.java:58)
     at weblogic.servlet.internal.WebAppModule.setupPersistenceUnitRegistry(WebAppModule.java:1812)
     at weblogic.servlet.internal.WebAppModule.getWebClassLoader(WebAppModule.java:1604)
     at weblogic.servlet.internal.WebAppServletContext.initClassLoader(WebAppServletContext.java:2969)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:438)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:484)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:418)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:976)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:381)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:46)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I hope someone can help me to get it working.
Kind regards
Oliver

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

AIA 2.4 installation on SOA suite 10.1.3.4 with Weblogic 9.2 MP3

Hi
I am trying to install AIA 2.4 on SOA suite 10.1.3.4 with Weblogic 9.2 MP3.
I could successfully install SOA suite 10.1.3.4 with Weblogic 9.2 MP3 and applied MLR # 9 Patch as well.
I am looking for document reference(step by step document) To install AIA 2.4 on weblogic.
When i used AIA 2.4 installer it was asking for OPMN port/OC4J instance name. Is there any other AIA 2.4 Installer for weblogic server?
Thanks

Of course, seeing 2.x I mistakenly thought PIPs as AIA Foundation Pack is now current version of 11gR1. Anybody wishing to install AIA Foundation Pack, especially with WLS should use 11gR1.
Can you elaborate on the reason you are electing to go with an older version of both AIA Foundtion Pack and SOA Suite?

Jconsole with weblogic 10.0 MP1

Similar Messages

Maybe you are looking for