JMS Default connection factories

          Hi
          I have a evaluation version of Weblogic Server 7. When I start the examples server
          there are no default connection factories under JMS. The default connection factory
          is enabled. How can I view the default connection factory to use with the given
          examples?
          Thanks

          Hi
          You can look them up in the server's JNDI tree.
          In console, you can goto server (myserver) and click on the "View JNDI tree"
          link at the bottom, to get the JNDI tree, where you can find the default connection
          factories.
          Kats
          BEA
          "diptiman" <[email protected]> wrote:
          >
          >Hi
          >I have a evaluation version of Weblogic Server 7. When I start the examples
          >server
          >there are no default connection factories under JMS. The default connection
          >factory
          >is enabled. How can I view the default connection factory to use with
          >the given
          >examples?
          >
          >Thanks

Similar Messages

Creating connection factories

          Can I create one connection factory for use by queues AND topics?


In BEA WL, you can configure one CF for both purposes and
          cast it to either javax.jms.QueueConnectionFactory or
          javax.jms.TopicConnectionFactory, or use one of the default
          connection factories in the same manner.
          P.S. For a FAQ, and various helpful links, start with
          the JMS technology page on dev2dev:
          http://dev2dev.bea.com/technologies/jms/index.jsp
          P.P.S. The upcoming JMS 1.1 standard provides a javax.jms CF interface
          that works for both topics and queues. See the JMS Programmer's
          guide introduction for info.
          Eric Kaplan wrote:
          > Can I create one connection factory for use by queues AND topics?

Default Connection Factory

The Given Default connection Factory is not working in my MDB.The provided Default is MyJMS Connection Factory under services-jms-connection Factories. if i will give new name then it is working. why default one is not working.
          reply me
          With Regards
          vishwa


1 - Normally an MDB need not configure a connection factory
          unless it is driven by a non-WebLogic JMS provider.
          2 - There is no default connection factory called "MyJMS
          Connection Factory". Default connection factories can't be configured.
          3 - If this doesn't help, please post the full exception and
          relevent log messages...
          vishwanadha reddy wrote:
          > The Given Default connection Factory is not working in my MDB.The provided Default is MyJMS Connection Factory under services-jms-connection Factories. if i will give new name then it is working. why default one is not working.
          > reply me
          > With Regards
          > vishwa

Only the Default JMS Connection Factories Works.

          I can only get transcation working properly when I use the default JMS connection
          factory.
          If I:
          1. Create my own JMS Connection factory and set "User Transaction Enabled" to
          true
          2. Enable container managed transactions on my MDB
          Then WebLogic complains that the MDB cannot connect to the queue since the source
          is not transaction. However as I mentioned if I use the default connection factory
          provided by Weblogic everything works fine and dandy.
          Any ideas.
          Thanks
          Andrew


          Thanks for the reply. I'm using WebLogic 7.0
          Dongbo Xiao <[email protected]> wrote:
          >Which WebLogic Server release you are using?
          >You'll have to set XAConnectionFactoryEnabled too if you use 7.0.
          >If you use 8.1, you only need to set XAConnectionFactoryEnabled.
          >
          >Dongbo
          >
          >
          >Andrew N wrote:
          >
          >> I can only get transcation working properly when I use the default
          >JMS connection
          >> factory.
          >>
          >> If I:
          >> 1. Create my own JMS Connection factory and set "User Transaction Enabled"
          >to
          >> true
          >> 2. Enable container managed transactions on my MDB
          >>
          >> Then WebLogic complains that the MDB cannot connect to the queue since
          >the source
          >> is not transaction. However as I mentioned if I use the default connection
          >factory
          >> provided by Weblogic everything works fine and dandy.
          >>
          >> Any ideas.
          >>
          >> Thanks
          >>
          >> Andrew
          >

Problems in accessing Connection Factories in JMS

Hi
We are porting A J2ee application from weblogic to SAP Web AS.
Primarily in weblogic we always get a Connection Factory Instance from
the Connection Factory and then typecast it to either
QueueConnectionFactory or TopicConnectionFactory.(Pl. see the code
below)
ConnectionFactory factory = null;
QueueConnectionFactory queueFactory = null;
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,
this.initialContextFactory);
env.put(Context.PROVIDER_URL, this.providerUrl);
context = new InitialContext(env);
factory = (ConnectionFactory)context.lookup
(this.JNDINameConnectionFactory);
queueFactory = (QueueConnectionFactory)factory;
this.connection = queueFactory.createQueueConnection();
this.session = this.connection.createQueueSession
(false, Session.AUTO_ACKNOWLEDGE);
this.queue = (Queue)context.lookup(this.queueName);
But in SAP WEB As there is not such facility provided.Is it that always
we need to lookup to the jmsfactory/default/QueueConnectionFactory for
a Queue and jmsfactory/default/TopicConnectionFactory or
jmsfactory/default/QueueConnectionFactory for Topic . Is it poosibel to
get a Connection factory Instance from where on I Could further
Typecast it to TopicConnectionFactory or QueueConnectionFactory
Instance , because this the way we normally do in Weblogic or JMS.
Also this is how the java JMS API accepts . Could you please let me
know as to are there any more configuration to be Done apart from the
JMS provider and JMS Connector in the Visual Admin for Accessing the
Topmost ConnectionFactory JNDI Instance . If no ,are there any other
workarounds , as approach for changing the code for accessing the
individual Connection Factories JNDI is not feasible for us
regards
rajesh kr

Hi Rajesh,
Here it is a code sample, that I was thinking about
RajeshConnectionFactory implements QueueConnectionFactory, TopicConnectionFactory, Serializable {
   //SAP queue and topic factories that will be initialized during deserialization
   private QueueConnectionFactory sapQueueFactory;
   private TopicConnectiojnFactory sapTopicFactory;
   // will be invoked after deserialization, when performing lookup of this object
   private void readObject(ObjectInputStream stream) {
       sapQueueFactory = performLookup(PATH_TO_SAP_QUEUE_FACTORY);
       sapTopicFactory = performLookup(PATH_TO_SAP_TOPIC_FACTORY);
   //from the TopicConnectionFactoriesInterface
   TopicConnection createTopicConnection() {
       return sapTopicFactory.createTopicConnection();
   //from the TopicConnectionFactoriesInterface
   TopicConnection createTopicConnection(String user, String password) {
       return sapTopicFactory.createTopicConnection(user,password);
   //from the QueueConnectionFactoriesInterface
   QueueConnection createQueueConnectrion() {
       return sapQueueFactory.createQueueConnection();
   QueueConnection createQueueConnectrion(String user, String password) {
       return sapQueueFactory.createQueueConnection(user, password);
Then you will bind your RajeshConnectionFactory in the naming on the place your application is looking up, and your application after performing lookup can safely typecast it to whatever you want.
I hope that will solve your problems. If it works, I will not charge you for the code copyright :).
However I think it will be better if you fix the application to make it trully J2EE compatible instead of such magics.
Best Regards
Peter

Oracle JMS AQ connection using Weblogic 10.3.3

Hi All,
I am a newbie with SOA 11g and I am trying to do a simple test case for a use case of connecting Oracle AQ JMS with Weblogic and using it in my SOA 11g process. I am trying to publish something to my queue that I created but I am getting this error in the weblogic / soa log files pasted below :
The steps I followed exactly are this :
1) Created a Database Queue called DemoInqueue using the following scripts :
exec dbms_aqadm.create_queue_table ( queue_table=> 'DemoInQueue', queue_payload_type=> 'SYS.AQ$_JMS_TEXT_MESSAGE', multiple_consumers=> FALSE, compatible=> '8.1');
COMMIT;
exec dbms_aqadm.create_queue(queue_name=> 'DemoInQueue', queue_table=> 'DemoInQueue');
COMMIT;
exec dbms_aqadm.start_queue('DemoInQueue');
COMMIT;
2) Created a Data Source in weblogic server : Called it using the JNDI name : jdbc/oracle/jms Driver Class Name : oracle.jdbc.xa.client.OracleXADataSource (I tested the connection it works fine)
3) Created a JMS Module (JMSTestModule) and then Created a New Summary of Resource for it ( AQServer) and chose option Foregin Server.
Under General Tab, I gave "oracle.jms.AQjmsInitialContextFactory" as the JNDI Initial Context Factory and Under JNDI Properties I put in "datasource=jdbc/oracle/jms" as I created the above datasource.
Under Connection Factores I created a new "ForeignConnectionFactory-0". Under Configuration I gave Local JNDI name as "jms/DemoCF" and remote JNDI Name as "XAQueueConnectionFactory" (I have also tried with
QAConnectionFactory but no difference )
Under Destinations I created a new "ForeignDestination-0" with local JNDI name as "jms/DemoInQ" and Remote JNDI Name as "Queues/DemoInQueue" (Because my Queue name is that)....
4) I restarted the Weblogic Server then went to SOA suite and tried a very simple process Hello world added a JMS adpater....Inside the adpater I selected OEMS (Advanced Queueing), App server my weblogic server,
operation as ProduceMessage and when I hit Browse I was able to see my AQServer ForeignDestination-0 Queue. I selected it and under destination name it populated "jms/DemoInQ" but under JNDI name it also
populated "eis/aqjms/Queue" I left that as is and deployed my process and tried invoking it. It failed with the error message below.....I also tried modifying the JNDI name to something else...in Jdev..but the results
are the same....
Are these steps correct ? Am I missing something here.?
I followed all the blogs and forums in this site and I think I did all the steps...but if anyone can help me I would really appreciate it...
Here is the error stack below :
<BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437281> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
####<Dec 1, 2010 2:07:17 PM EST> <Warning> <Connector> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437296> <BEA-190032> << eis/aqjms/Queue > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
">
SOA LOG.....
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.adapter> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <JCABinding=> [default/HelloWorldComposite!1.0*soa_25f514de-3db3-4bed-9144-44d83dacbe10.Publishmessage]:Produce_Message One-way operation Produce_Message() failed>
####<Dec 1, 2010 2:07:17 PM EST> <Error> <oracle.soa.bpel.engine.ws> <OLRMSPLAP103> <AdminServer> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-57B9592B4D0D4FFD1A5C> <3f3d2d8955322f32:-5d57c961:12ca300b9a3:-7fd3-00000000000002d7> <1291230437359> <BEA-000000> <<WSInvocationManager::invoke> got FabricInvocationException
oracle.fabric.common.FabricInvocationException: BINDING.JCA-12563
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.

I executed your scripts one by one and then tried again. Same Error Message. I think the problem is not in the AQ queue. The issue is with the BPEL / SOA process as the error message below clearly says it's not able to find aqjms/XAQueueConnectionFactory. That's the JNDI name in my Jdeveloper ? Is that JNDI what I should be using or should be match something else ? Please help................
Latest Error LOG...
<<anonymous>> <BEA1-0B06BE09987B4FFD1A5C> <3f3d2d8955322f32:-73cb8b9a:12ca58d835d:-7fd3-0000000000000123> <1291268540004> <BEA-000000> <<CubeEngine::handleWorkItem> This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope. Root cause : com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
HelloWorldComposite:Publishmessage [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12141
ERRJMS_CONN_FAC_NOT_FOUND.
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factory aqjms/XAQueueConnectionFactory neither through JNDI nor instantiate it as a Java class.
Please examine the log file to determine the problem.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>aqjms/XAQueueConnectionFactory</detail>
,code=<code>null</code>}
>

Connection Factories in a Cluster

Hi Folks,
          I'm trying to get to grips with the precise behavior of connection factories
          (CF) in a cluster. Any corrections/additions appreciated...(I've read the
          perf. guide).
          According to the docs, you should look at two scenarios
          a) JMS app located on same server as cluster.
          Imagine I have a JMS app deployed to the cluster, and docs say I should
          deploy CF to cluster as well.
          I have JMS server only on one server in the cluster.
          Here is what I think happens:
          i. As far as I know, connection factories will only load balance
          connections across servers hosting connection factories.
          ii. When the app looks up a CF using the JNDI of the cluster, will it
          always get the a CF collocated
          with the app (ie. on same server), because of collocation optimization?
          iii. When the app uses this CF to create a Connection, will the CF load
          balance the connection?
          ie. Will I get a different connection (round robin) every time I
          create a connection?
          If this does happen, then presumably my JMS application will route
          all JMS traffic through this connection to this other
          server, which may not even host a JMS server, which in turn has to
          route to the JMS server.
          iv. If the CF was looked up using the local JNDI context, then the
          local CF will be returned and presumably if
          I create a connection then a local connection will be returned. ie.
          no load balancing. The JMS application will
          use the "local" connection which will in turn route to the
          appropriate server hosting the JMS server..
          b) Where the JMS client is external
          When I have an external JMS client, the docs say you should deploy the CF
          only to those servers hosting the JMS servers.
          i) The docs say that the CF (new InitialContext("t3://clusteraddres"))
          will load balance across the servers in the cluster.
          ii) The docs also say that createConnection (on the CF) will load balance
          too.
          iii) This means that there are two servers involved right? The CF host
          (the server hosting the CF), and the C host (the
          server hosting the C). Does this mean I have two connections from
          teh client (one to each server), or does traffic
          flow from client to CF host to C host?
          The docs certainly imply that you get these two load balancing
          operations, which seems to lead to one of these
          scenarios.
          iii) Presumably, if my client creates multiple connections (one after the
          other) using the same connection factory,
          then it may at one time have a connection going to "ServerA", and at
          another time one going to "ServerB" (unless
          of course I have affinity enabled).
          Any guidance appreciated,
          Regards,
          Jon


          Jon Mountjoy wrote:
          > Hi Tom,
          >
          > I have inlined some comments on your comments!
          >
          >
          >>>a) JMS app located on same server as cluster.
          >>> Imagine I have a JMS app deployed to the cluster, and docs say I
          >
          > should
          >
          >>>deploy CF to cluster as well.
          >>> I have JMS server only on one server in the cluster.
          >>>
          >>> Here is what I think happens:
          >>> i. As far as I know, connection factories will only load balance
          >>>connections across servers hosting connection factories.
          >>
          >>Yes.
          >>
          >>> ii. When the app looks up a CF using the JNDI of the cluster, will
          >
          > it
          >
          >>>always get the a CF collocated
          >>> with the app (ie. on same server), because of collocation
          >
          > optimization?
          >
          >>Yes.
          >>
          >>> iii. When the app uses this CF to create a Connection, will the CF
          >
          > load
          >
          >>>balance the connection?
          >>
          >>Not if it is collocated.
          >
          >
          > I guess this confuses me a little. My scenario above speaks about the
          > CF+App deployed to a cluster.
          >
          > Are you talking about if the CF+App is collocated with the JMS server whose
          > destination the App is communicating with?
          No.
          > (I'd guess not, cos I wouldn't
          > know the destination until after I create the connection?).
          If the app is co-located with the the CF, the connection
          is always local.
          >
          >
          >>(Note that a producer to a distributed destination,
          >>by default produces to the local physical instance,
          >>and will not round-robin each message to other
          >>physical destination instances, unless the
          >>connection factory is so configured.)
          >>
          >>
          >>> ie. Will I get a different connection (round robin) every time I
          >>>create a connection?
          >>> If this does happen, then presumably my JMS application will
          >
          > route
          >
          >>>all JMS traffic through this connection to this other
          >>> server, which may not even host a JMS server, which in turn has
          >
          > to
          >
          >>>route to the JMS server.
          >>> iv. If the CF was looked up using the local JNDI context, then the
          >>>local CF will be returned and presumably if
          >>> I create a connection then a local connection will be returned.
          >
          > ie.
          >
          >>>no load balancing. The JMS application will
          >>> use the "local" connection which will in turn route to the
          >>>appropriate server hosting the JMS server..
          >>
          >>Yes.
          >>
          >>
          >>>b) Where the JMS client is external
          >
          >
          >
          >>> iii) This means that there are two servers involved right? The CF host
          >>>(the server hosting the CF), and the C host (the
          >>> server hosting the C). Does this mean I have two connections
          >
          > from
          >
          >>>teh client (one to each server),
          Yes. But not for the reason you think.
          The JNDI context that was used to look up
          the CF keeps its connection, and the JMS
          connection generated from the CF.
          >>> or does traffic
          >>> flow from client to CF host to C host?
          Yes.
          >>> The docs certainly imply that you get these two load balancing
          >>>operations, which seems to lead to one of these
          >>> scenarios.
          >
          >
          > Can you perhaps shed some light on the above question?
          >
          >
          >>>Any guidance appreciated,
          >
          >
          >>Just send a portion of your book royalties. ;-)
          >
          >
          > Hehe. Do you think I'd actually make a profit!? What you will earn, is my
          > eternal gratitude of course :)
          >
          > Regards,
          > Jon
          >
          >

Weblogic Server 9.2 Crashes when using the JMS Wrapped Connection Pooling.

===== BEGIN DUMP =============================================================
JRockit dump produced after 0 days, 01:05:05 on Thu Sep 16 18:27:36 2010
Additional information is available in:
E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.dump
E:\obopay\servers\EWP_9.2_Domain\jrockit.4516.mdmp
If you see this dump, please open a support case with BEA and
supply as much information as you can on your system setup and
the program you were running. You can also search for solutions
to your problem at http://forums.bea.com in
the forum jrockit.developer.interest.general.
Error Message: Illegal memory access. [54]
Exception Rec: EXCEPTION_ACCESS_VIOLATION (c0000005) at 0x0095065F - memory at 0x00740060 could not be read.
Minidump : Wrote mdmp. Size is 567MB
SafeDllMode : -1
Version : BEA JRockit(R) R27.2.0-131-78843-1.5.0_10-20070320-1457-windows-ia32
GC Mode : Garbage collection optimized for throughput
GC Strategy : Generational Parallel Mark & Sweep
: Current OC phase is: not running. YC is not running.
: GC strategy for GC 36 was genparpar
: GC strategy for GC 37 was genparpar
: GC strategy for GC 38 was genparpar
: GC strategy for GC 39 was genparpar
: GC strategy for GC 40 was genparpar
: mmHeap->data = 0x00C00000, mmHeap->top = 0x10C00000
: The nurserylist starts at 0x01BE75E8 and ends at 0x0CB52440
: mmStartCompaction = 0x00C00000, mmEndCompaction = 0x01C00000
: References are 32-bit.
CPU : Intel Pentium III/Pentium III Xeon SSE SSE2 SSE3 SSSE3 EM64T
Number CPUs : 2
Tot Phys Mem : 3451408384 (3291 MB)
OS version : Microsoft Windows XP version 5.1 Service Pack 3 (Build 2600) (32-bit)
Thread System: Windows Threads
State : JVM is running
Command Line : -Djava.library.path=E:\bea\jrockit90_150_10\bin;E:\bea\jrockit90_150_10\jre\bin;E:\bea\weblogic92\server\native\win\32;E:\bea\weblogic92\server\bin;E:\bea\weblogic92\server\native\win\32\oci920_8 -Dweblogic.management.discover=false -Dplatform.home=E:\bea\weblogic92 -Dwls.home=E:\bea\weblogic92\server -Dwli.home=E:\bea\weblogic92\integration -Dweblogic.Name=myserver -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic -Dweblogic.ext.dirs=E:\bea\patch_weblogic901\profiles\default\sys_manifest_classpath\weblogic_patch.jar Djava.security.auth.login.config=E://workspace/Bhopal/LoginModulesConfig/ewp_loginmodules.config -Djava.naming.factory.initial.ewp.remote=weblogic.jndi.WLInitialContextFactory -Dcom.ewp.proxy.is_remote=false -Djava.naming.provider.url.ewp.remote=t3://localhost:7001 -Dweblogic.webservice.verbose=true -Dweblogic.log.Log4jLoggingEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true Xdebug -Xnoagent -Dcom.sun.management.jmxremote -Xms256m -Xmx1024m -Dsun.java.launcher=SUN_STANDARD weblogic.Server
java.home : E:\bea\jrockit90_150_10\jre
JAVA_HOME : <not set>
JAVAOPTIONS: <not set>
PATH : E:\bea\jrockit90_150_10\jre\bin;E:\oracle\product\10.2.0\client_1\bin;C:\Program Files\PC Connectivity Solution\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Intel\DMIX;C:\Program Files\TortoiseSVN\bin
C Heap : Good; no memory allocations have failed
StackOverFlow: 0 StackOverFlowErrors have occured
OutOfMemory : 0 OutOfMemoryErrors have occured
Registers (from ThreadContext: 0x4B29E378 / OS context: 0x4B29E764):
eax = 00740060 ecx = 00740060 edx = 45a45ba0 ebx = 08c953b8
esp = 4b29ea30 ebp = 00000000 esi = 4b29ea60 edi = 4b29efb4
es = 00000023 cs = 0000001b ss = 00000023 ds = 00000023
fs = 0000003b gs = 00000000
eip = 0095065f eflags = 00010206
Stack:
(* marks the word pointed to by the stack pointer)
4b29ea30: 00981099* 08c953b8 008ab310 4b29eb34 09e5c308 009810ea
4b29ea48: 4b29ead8 0098ecd2 4b29ea60 4b29ea90 48bd8960 48bd8960
4b29ea60: 00000001 45aa0278 45a45ba0 00000007 00000000 08c953b8
4b29ea78: 08512180 4b29ef60 00000000 09d56368 09d563b0 4b29efb4
Code:
(* marks the word pointed to by the instruction pointer)
0095062c: 5e5f0cc4 c35bc033 01b85e5f 5b000000 ccccccc3 0424448b
00950644: a5f06ca3 ccccc300 cccccccc 04244c8b 01a8018b e0830774
0095065c: 8bc88bfe* 40788301 44408b03 af0f0a75 c0830841 f8e08317
00950674: ccccccc3 cccccccc cccccccc 0424448b 00f4888b 158b0000
Loaded modules:
(* denotes the module causing the exception)
00400000-0040ffff E:\bea\jrockit90_150_10\bin\javaw.exe
7c900000-7c9b1fff C:\WINDOWS\system32\ntdll.dll
7c800000-7c8f5fff C:\WINDOWS\system32\kernel32.dll
7e410000-7e4a0fff C:\WINDOWS\system32\USER32.dll
77f10000-77f58fff C:\WINDOWS\system32\GDI32.dll
77dd0000-77e6afff C:\WINDOWS\system32\ADVAPI32.dll
77e70000-77f02fff C:\WINDOWS\system32\RPCRT4.dll
77fe0000-77ff0fff C:\WINDOWS\system32\Secur32.dll
77c10000-77c67fff C:\WINDOWS\system32\MSVCRT.dll
76390000-763acfff C:\WINDOWS\system32\IMM32.DLL
00820000-00a9cfff *E:\bea\jrockit90_150_10\jre\bin\jrockit\jvm.dll
76b40000-76b6cfff C:\WINDOWS\system32\WINMM.dll
71ab0000-71ac6fff C:\WINDOWS\system32\WS2_32.dll
71aa0000-71aa7fff C:\WINDOWS\system32\WS2HELP.dll
7c340000-7c395fff E:\bea\jrockit90_150_10\bin\MSVCR71.dll
5dac0000-5dac7fff C:\WINDOWS\system32\rdpsnd.dll
76360000-7636ffff C:\WINDOWS\system32\WINSTA.dll
5b860000-5b8b4fff C:\WINDOWS\system32\NETAPI32.dll
76bf0000-76bfafff C:\WINDOWS\system32\PSAPI.DLL
6d700000-6d70bfff E:\bea\jrockit90_150_10\jre\bin\verify.dll
6d370000-6d38cfff E:\bea\jrockit90_150_10\jre\bin\java.dll
6d2f0000-6d2f7fff E:\bea\jrockit90_150_10\jre\bin\hpi.dll
6d720000-6d72efff E:\bea\jrockit90_150_10\jre\bin\zip.dll
6d520000-6d527fff E:\bea\jrockit90_150_10\jre\bin\management.dll
6d530000-6d542fff E:\bea\jrockit90_150_10\jre\bin\net.dll
71a50000-71a8efff C:\WINDOWS\system32\mswsock.dll
662b0000-66307fff C:\WINDOWS\system32\hnetcfg.dll
71a90000-71a97fff C:\WINDOWS\System32\wshtcpip.dll
41c00000-41c26fff C:\WINDOWS\system32\DNSAPI.dll
41c30000-41c37fff C:\WINDOWS\System32\winrnr.dll
41c40000-41c6bfff C:\WINDOWS\system32\WLDAP32.dll
41c80000-41c85fff C:\WINDOWS\system32\rasadhlp.dll
68000000-68035fff C:\WINDOWS\system32\rsaenh.dll
769c0000-76a73fff C:\WINDOWS\system32\USERENV.dll
438b0000-438b8fff E:\bea\jrockit90_150_10\jre\bin\nio.dll
41ba0000-41ba9fff E:\bea\jrockit90_150_10\jre\bin\jmapi.dll
41bb0000-41bbdfff E:\bea\weblogic92\server\native\win\32\wlfileio2.dll
43ce0000-43cf8fff C:\WINDOWS\system32\iphlpapi.dll
43d10000-43d27fff C:\WINDOWS\system32\MPRAPI.dll
77cc0000-77cf1fff C:\WINDOWS\system32\ACTIVEDS.dll
43d30000-43d54fff C:\WINDOWS\system32\adsldpc.dll
43d60000-43d70fff C:\WINDOWS\system32\ATL.DLL
43d80000-43ebcfff C:\WINDOWS\system32\ole32.dll
43ec0000-43f4afff C:\WINDOWS\system32\OLEAUT32.dll
43f50000-43f5dfff C:\WINDOWS\system32\rtutils.dll
71bf0000-71c02fff C:\WINDOWS\system32\SAMLIB.dll
43f60000-44052fff C:\WINDOWS\system32\SETUPAPI.dll
44060000-44064fff E:\bea\weblogic92\server\native\win\32\wlntio.dll
44540000-44545fff E:\bea\jrockit90_150_10\jre\bin\rmi.dll
4d010000-4d122fff E:\bea\jrockit90_150_10\jre\bin\dbghelp.dll
"[STANDBY] ExecuteThread: '21' f" id=87 idx=0xf0 tid=4208 lastJavaFrame=0x4B29EB4C
Stack 0: start=0x4B260000, end=0x4B2A0000, guards=0x4B263000 (ok), forbidden=0x4B261000
Thread Stack Trace:
at _mmGetPossibleMovedObjectSize+15()@0x0095065F
at _refIterInit+393()@0x00981099
at _refIterInit+474()@0x009810EA
at _trProcessLocksForThread+66()@0x0098ECD2
at _javalockCouldBeLock+1047()@0x008AB417
at _javalockConvertThinToFat+42()@0x008AC13A
at RJNIjrockit_vm_Locks_convertThinLockedToFatLocked@8+15()@0x00986B1F
-- Java stack --
at jrockit/vm/Locks.convertThinLockedToFatLocked(Ljava/lang/Object;)V(Native Method)
at jrockit/vm/Locks.createMonitorAndConvert(Ljava/lang/Object;Z)Ljrockit/vm/ObjectMonitor;(Unknown Source)
at java/lang/Object.wait(J)V(Native Method)
at java/lang/Object.wait(Object.java:474)
at weblogic/common/CompletionRequest.getResult(CompletionRequest.java:109)
^-- Holding lock: weblogic/common/CompletionRequest@0x09E5C2A8[thin lock]
at weblogic/store/gxa/internal/GXATransactionImpl.commitStoreIO(GXATransactionImpl.java:99)
at weblogic/store/gxa/internal/GXATransactionImpl.doOperationCallbacks(GXATransactionImpl.java:215)
at weblogic/store/gxa/internal/GXAResourceImpl.commit(GXAResourceImpl.java:1448)
at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:1333)
at weblogic/transaction/internal/XAServerResourceInfo.commit(XAServerResourceInfo.java:577)
at weblogic/transaction/internal/ServerSCInfo.startCommit(ServerSCInfo.java:514)
at weblogic/transaction/internal/ServerTransactionImpl.localCommit(ServerTransactionImpl.java:1993)
at weblogic/transaction/internal/ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2658)
at weblogic/transaction/internal/ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2580)
at weblogic/transaction/internal/ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:278)
at weblogic/transaction/internal/ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
at weblogic/deployment/jms/WrappedTransactionalSession.delistFromTransaction(WrappedTransactionalSession.java:258)
^-- Holding lock: weblogic/deployment/jms/PooledSession_weblogic_jms_client_JMSXASession@0x09D56368[thin lock]
at weblogic/deployment/jms/WrappedMessageProducer.send(WrappedMessageProducer.java:149)
at com/obopay/jms/helper/BaseQueueHelper.sendMessage(BaseQueueHelper.java:107)
The above is the jrockit crash dump file..
I am using the JMS Wrapper Connection Poooling provided by Weblogic. When i use Jmeter and do the load testing for around 10 users, the server gets crashed.
I doubt something is going wrong with the Weblogic JMS Connection Pooling, please help me..

The problem doesn't look like it has anything to do with wappers per se. The stack indicates that the JVM died when the persistent store tried to invoke a standard Java synchronize operation. JVM crashes need to be analyzed by a JVM expert, so I second the suggestion to solicit help from JVM experts and/or filing a case with customer support. In the mean-time, you can probably work-around the issue by either (A) ensuring you have a recent version of the JVM installed, or (B) temporarily switching to the Sun JVM.
Regards,
tom
Edited by: TomB on Sep 17, 2010 2:33 PM

Error of Foreign JMS server connecting to durable subscriber topic

Weblogic server domain is trying to connect to the durable topic configured on the other weblogic domain. (Both domain are running on weblogic 9.2 platform)
WLI 9.2 Event generator is TestPinFJ is the MDB which is trying to listen message from Foreign JMS.
Following error we have got when I did following configuration for connecting to durable topic using foreign JMS.
<EJB> <BEA-010061> <The Message-Driven EJB: TestPinFJ is unable to connect to the JMS destination: TestQueue. The Error was:
java.lang.IllegalArgumentException: port out of range:-16>
Detail configuration is as follows:
Foreign JMS : TestFS
General:
JNDI Connection URL: t3://10.20.65.95:9004 TestClient123 (where TestClient123 is the client id for durable subscriber topic )
Destinations:
Local JNDI Name: TestQueue
Remote JNDI Name: TestTopic
Connection Factories :
Local JNDI Name: TestQCF
Remote JNDI Name: TestTCF
My suspect is the JNDI connection URL is incorrect. Please advice how to configure JNDI conn url while connecting to durable topic with client id?

hi Hussain,
I am the collegue of the person created this thread.
Thaks for the input. can u please suggest me how do we configure connectionfactory and JSM topic to durable subscription with ClientID.Shoudl th eClientID be same for JMSTopic and ConectionFactory?
In Domain "A" I have created JMS topic with durable subscriber wioth client ID "TestClient123" and created a conenctionfacory with same client ID "TestClient123" .
In Domain "B" i created a foreign JMS connecting to topic in Domain A using connection facatory created in Domain "A" configured as as remoteConnectionFActory.
Also the JNDI Connection URL is : t3://10.20.65.95:9004
"weblogic.jms.common.InvalidClientIDException: Client id, Testclient1, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
Nested exception: weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)".
weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)"
IS there any chnage i need to make to get this connectivity between Domain A and B working?
Appreciate your help on this.

Creating multiple connection factories from deployed RAR

Hi
          I'm using WL Server V8.1 sp4 and have successfully deployed my Connector
          Module (RAR) using the Builder tool.
          Within the Builder I can specify default connection properties in the
          deployment descriptor. What I want though is the ability to define
          multiple connection factories with different properties without having
          to deploy/redeploy the RAR for every different connection configuration.
          I can't believe there is a 1-to-1 mapping between the RAR and connection
          factory settings. I've seen that there's a <ra-link-ref> tag available
          in the weblogic-ra.xml but I can't see how to use this?
          Any advice on how to get this working would be greatly appreciated.
          Cheers
          Chris


Hi
          I've had some success but am still confused by the way WLS requires
          second and subsequent connection factories to be created.
          It appears you create a CF within the weblogic-ra.xml deployment
          descriptor using the <map-config-property> tags. All other properties
          are inherited from the settings within ra.xml (we have them set blank).
          If there is no weblogic-ra.xml then a default is created at RAR deploy
          time. We can modify settings and redeploy the resource adapter using the
          supplied Builder tool. There appears to be a limit on what is possible
          with this tool to create CF instances though. It doesn?t seem possible
          to enter config properties here to appear within the weblogic-ra.xml.
          There are fields to allow entry of the CF name and the RA link reference
          though. (This seems strange that it doesn?t provide full flexibility).
          In order to create a CF a certain amount of manual work is required. You
          need to hand modify the weblogic-ra.xml to specify the connection
          properties you want. Then the file has to be added to RAR file for
          deployment using the jar command.
          A second or subsequent CF must also be prepared in a similar way ? the
          properties are defined in weblogic-ra.xml but this time there is no need
          to redeploy a complete RAR file. We can link to the defaults and classes
          provided in the original deployment. This is done using the
          <ra-link-ref> and specifying the connection-factory-name of the original
          RAR. This new RAR only needs ra.xml and weblogic-ra.xml to deploy so we
          can remove any jar files containing code. However, this cannot be done,
          it seems, from the Builder tool.
          I am concerned it seem to be a lot of manual work and, in particular,
          editing of the rar files we provide to our customers. Does anyone know
          of a better way of achieving multiple CF instances without going through
          this process?
          Regards
          Chris
          ChrisWalker wrote:
          > Hi
          >
          > I'm using WL Server V8.1 sp4 and have successfully deployed my Connector
          > Module (RAR) using the Builder tool.
          > Within the Builder I can specify default connection properties in the
          > deployment descriptor. What I want though is the ability to define
          > multiple connection factories with different properties without having
          > to deploy/redeploy the RAR for every different connection configuration.
          >
          > I can't believe there is a 1-to-1 mapping between the RAR and connection
          > factory settings. I've seen that there's a <ra-link-ref> tag available
          > in the weblogic-ra.xml but I can't see how to use this?
          >
          > Any advice on how to get this working would be greatly appreciated.
          >
          > Cheers
          > Chris

Windows RDS - configuring a default connection & desktop

I'm looking at remote desktop options and used terminal services in the past. I'm configuring remote desktop services on a Windows 2008 R2 server. The goal is
to allow users to go to a web page, pull up a remote desktop and access apps & server shares inside the network.
I have it installed, and am able to get a connection using \\server\rdweb. However, that takes me to the RDS default connection page. If I click on remote desktop it asks what computer I want to connect
to.
What I want to do is configure this or another web page to automatically connect to a default profile I've configured with various apps, or to create a new profile based on the user's login name like any PC
does when you login with a new user ID.
I'm sure it's in the documentation somewhere, I haven't run across it yet.

Hi,
Thanks for your posting in Windows Server Forum.
As per your comment, I can say that you can try to change the login web page of RD web where you can place the default domain and user name for that user.
You can make changes on login.aspx file on “%windir%\Web\RDWeb\Pages\<The Language of Your Location>\”path as below:
Change the original code section:
<input id=”DomainUserName” name=”DomainUserName” type=”text” class=”textInputField” runat=”server” size=”25” autocomplete=”off” />
to be:
<input id=”DomainUserName” name=”DomainUserName” type=”text” class=”textInputField” runat=”server” size=”25” autocomplete=”off”
value=”domainname\” />
Please refer below thread for more information.
How to set default logon domain RD Gateway and/or RD
Web
Hope it helps!
Thanks,
Dharmesh

PI7.1 JMS Adapter - connect to NW6.40

Hello,
We are facing following problem on SAP PI:
We have a scenario where PI (version 7.1) is connecting to another SAP NetWeaver system (version 6.40). There is an application that reads/puts messages from/to JMS Queues running on this system. PI has to connect the JMS Provider of 6.40 system and read/put these messages from/to these JMS Queues.
This scenario worked fine till we used XI 3.0 (NW6.40). We configured sender JMS channel with link to remote JMS Server and parameter "force_remote".
After installation of new PI7.1 we noticed some issues:
1.the connection is unstable. Sending JMS messages from PI to NW6.40 queue works a while but then we get error like this:
Adapter Framework caught exception: Unable to write new JMS message body for message: 00237d29-13fc-02ed-ba85-01d046631592: ConnectorException: Connector for ConnectionProfile of channel: EON_CC_jms_rcv_omsmessageon node: 922834950 having object id: 70855b1c6c483e869982ea2fe9787b36 was unable to create a new javax.jms.TextMessage message: javax.jms.IllegalStateException: Session is closed.
2. we cannot read messages from JMS Queue of NW6.40 at all. The messages are there in queue, communication channel is running and succesfully connected to queue but no message is processed and no error shows in communication channel monitoring.
Has anybody solve similar problem with connection between 7.1 and 6.40 NetWeaver?
I think the problem can be backward incompatibility of 7.1 SAP JMS libraries against 6.40. If this is true then the question is whether it is possible to deploy old libraries and run them simultaneously with native 7.1 libraries?
Thanks

problem sorted - factory property settings were not configured correctly in JMS Adapter connection pool

Setting up default connection for accessing emails...

I had a quick look and found similar problems on here, but none that I thought were the same.
I've been able to set up Gmail to be received through my 'Messaging' on my N96. Turns out its quite a handy function. Also figured out that you can get it to automatically check you mail at regular intervals. I want to use this, but I don't want to have to select the connection every time the phone wants to check for new mail. So I need to set up a preferred connection. That's no problem...
The problem occurs when I try to select my WLAN as default. However, every time I select it, the phone freezes up. Not completely, as I can change programs and even exit the messaging settings via the hang up key, but if I do that, it doesn't make any changes.
I have deleted and restored the WLAN connection, I have accessed my inbox manually, so it isn't a problem on Google's end, and I have checked the various connection options to no avail.
So, does anyone know why it my phone would freeze when trying to set up my WLAN connection as the default connection for accessing my e-mails? Any questions about my situation, just ask and I will gladly supply whatever you ask for.
Regards,
Jarvis
Message Edited by jarvis187 on 15-Jan-2009 01:24 AM

No help available out there? If you need it explained clearer just say so and I'll do so. Thanks in advance.

E51 default connections access with WLAN - how ?

Hi.
I just bought a lovely e51, and I love it, but after playing with it for 2 days, I cant seem to set the default connections to WLAN.
For instance, when I click on the WLAN from the front menu, it offers to browse using wifi, thats great.
But if I click on the Web icon, or the Nokia maps, or the Download stuff, it takes me to "Data Package" which I dont want to use, when I have a WLAN at home.
I understand that the WLAN wont be able to "download" every type of contents (like the Radio?) but surely it should work with the Web & Downloads?
Any hint most welcome.
Nik

Hi,
Open browser, click on left soft button, options, scroll to settings,general,access point and set to always ask.
This way you can select each time you log on to browser.
Or tools, settings, connection, packet data, access point and fil in you settings.
Better to have choice at start up that way if you are not in wi fi area you can just select high speed data.
Cheers.

How to change the default connection

I've to change programmatically the default connection of the report (6i).
I thought to use somenthing like LOGOUT/LOGIN (FORMS6i) in the BeforeReport trigger, but I don't find any valid solution yet.
Thanks in advance,
Raffaele

The reports are developed with Report Builder 6.0.8.8.3.
The server is configurated: Oracle HTTP Server/1.3.22 (Win32)
mod_plsql/9.0.2.0.0 DAV/1.0.2 (OraDAV enabled)
mod_oc4j/3.0 mod_ossl/9.0.2.0.0 mod_fastcgi/2.2.10 mod_perl/1.26
From my application I call iexplore and set the url like:
http://<myserver>/dev60cgi/rwcgi60.exe?MY_REPORT+<jobid>
In cgicmd.dat I defined:
MY_REPORT: report=D:\report_path\theREPORT.rep
userid=def_user/pwd@the_db
server=my_repserver...
In the report, in the BEFORE_REPORT or in BEFORE_PARAMETER_FORM trigger I would like to make a query to a table of def_user with the job_id filter and get the job specific connection info.
Then, I've to re-connect to the new user where the tables of the report's data model a re defined.
Our database is structured with a single user for general data, included the info to address the other schema, and more specific users (~100) for job data.
I've used the tecnique in Forms, but I can't replicate it in Reports.
Thank you for any suggestions.
Raffaele

JMS Default connection factories

Similar Messages

Maybe you are looking for