** MQSeries WLS6-sp2 JMSException

          Hello all,
          I was successul in conencting MQSeries 2.5 with WebLogic 6.1-sp2
          following sample (wlsmqsereis.zip) using WLS as JNDI server.
          This was on same host, but when I moved MQSeries on different
          machine and then ran a client that sends messages to queue on
          MQS, I got the JMS Exception below.
          my question is, is it possible to have MQSeries and Weblogic
          on separate hosts and still wlsmqseries.zip would work?
          Any help is greatly appreciated.. thanks all.
          ------- Exception -----------------------------------
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
          'localhost:QM_pc234221123'
          at
          com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
          at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:255)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:142)
          at com.bwe.TextMessageSenderClient.<init>(TextMessageSenderClient.java:43)
          at com.bwe.TextMessageSenderClient.main(TextMessageSenderClient.java:102)
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:QM_pc234221123'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
          at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:255)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:142)
          at com.bwe.TextMessageSenderClient.<init>(TextMessageSenderClient.java:43)
          at com.bwe.TextMessageSenderClient.main(TextMessageSenderClient.java:102)
          Exception in thread "main"

Hi this is mahesh iam also getting same error
          when run standalone jms application with websphere 5.1 inorder to post mesg on to Q.
          javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '192.168.9.16:WAS_MAHESHP_server1'
          at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:556)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1736)
          at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1129)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80)
          at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:145)
          at org.mule.samples.hello.QueueMessageSender.sendMessage(QueueMessageSender.java:40)
          at org.mule.samples.hello.QueueMessageSender.main(QueueMessageSender.java:129)
          plz do reply me
          paddy

Similar Messages

JMSAdapter for MQSeries 6.0 (JMSException)

Hi,
I'm used JMSAdapter for connect to queue MQSeries 6.0.
And i get error : javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:QMTEST'
MQSeries and BPEL PM place on my localhost. I write oc4j-ra.xml from tutorial:
     <connector-factory location="eis/Jms/JmsAdapter" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=QMTEST;HostName=localhost;Channel='G.TO.D';TransportType=1;"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value="MUSR_MQADMIN"/>
          <config-property name="password" value="welcome"/>
     </connector-factory>
Has anybody experience with the IBM MQ Series adapter ?
Evgeniy

We have the following problem connecting Oracle BPEL process to IBM MQ.
Should we re-configure MQ/BPEL process/Oracle BPEL engine configuration?
Any help is greatly appreciated
Environment
Versions:
Oracle BPEL 10.1.2
IBM MQ - v 6.0 trial version installed locally on Windows machine
Oracle BPEL and MQ are on the same machine
We followed tutorial on Oracle BPEL web site:
Tutorial 9 : MQSeries Queue integration through the Oracle AS Adapter for JMS
http://www.oracle.com/technology/products/integration/adapters/pdf/adapter-Tutorial9-MQSeries-QueuetoQueue.pdf
MQ configuration
Created MQ Manager using wizard supplying default values
Created two queues
Problem
When deploying BPEL process the following error occurs:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'tanorw-medveal:MS_BPEL_Queue_Mgr'
Also this problem is seen when process is deployed and BPEL engine starts.
Here is extract from 0ra4j0ra.xml:
     <connector-factory location="eis/mqseries/Queue" connector-name="Jms Adapter">
          <config-property name="connectionFactoryLocation" value="com.ibm.mq.jms.MQQueueConnectionFactory"/>
          <config-property name="factoryProperties" value="QueueManager=MS_BPEL_Queue_Mgr;TransportType=1;HostName=localhost;Port=1414;Channel=sc1"/>
          <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
          <config-property name="isTopic" value="false"/>
          <config-property name="isTransacted" value="true"/>
          <config-property name="username" value="mqtest"/>
          <config-property name="password" value="password"/>
I created MQ Server Connection Channel manually on MQ. TCP Port for that channel 1414

Strange WLS6.sp2 Oracle DB Reconnect issue in a Cluster but ONLY on the Admin server

Any Ideas? ->
I am having a issue when our oracle db server goes down and when we try
to reconnect the Pool via weblogic I am getting this error. This only
happens on the Admin server for the cluster, none of the managed servers get
this and they all seem to be ok. Any ideas?
-Pete
**** Below is the stack trace:
java.sql.SQLException: Io exception: Broken pipe
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at
oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1329
at
oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1
353)
at
oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
at
oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
:1805)
at
oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
ment.java:322)
at
oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.j
ava:366)
at
weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:45)
at
weblogic.jdbc.rmi.internal.PreparedStatementImpl.execute(PreparedStatementIm
pl.java:289)
at
weblogic.jdbc.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.ja
va:398)

Hi,
As i understand is OS is clustered not the db. Better is to manually shutdown the db clean and then start it.
TO start login through sqlplus sys as sysdba
1. startup
2. Once its done, start the listener
3. Start the application
Anand

Re: WLPI 2.0 SP1 MissingResourceException

I got the same Kim (after installing WLPI SP1)
"Kim Bacon" <[email protected]> wrote:
>
I've installed WLAI 2.0 SP1 on WLS6 SP2 and when starting Process Integrator
I
receive the following error. Any ideas?
Error initializing plugin: com.bea.wlaiplugin.common.ejb.WLAIPluginBeanHomeImpl@154145
java.rmi.RemoteException: EJB Exception: ; nested exception is:
java.util.MissingResourceException: Can't find bundle for base name com.bea.wlaiplugin.common.ejb.WLAIPlugin,
locale en_US

same error here

MQSeries and WLS6.1-SP3 integration question

Hello all,
I am trying to have WLS6.1-sp3 MDBs consume messages off
MQSeries 5.2 queues. My quetions are:
1. Do I need to use the JMSBridge60.zip? I assume I don't need it
since it say WLS6.1 has builtin brdige. If so, then what is the
appropriate approach.
2. Is it possible to have WLS and MQSeries 5.2 participate in
two-phase commit based trascations?
your help is greatly appreciated.
Many thanks.

Hello all,
I am trying to have WLS6.1-sp3 MDBs consume messages off
MQSeries 5.2 queues. My quetions are:
1. Do I need to use the JMSBridge60.zip? I assume I don't need it
since it say WLS6.1 has builtin brdige. If so, then what is the
appropriate approach.
2. Is it possible to have WLS and MQSeries 5.2 participate in
two-phase commit based trascations?
your help is greatly appreciated.
Many thanks.

Does WLS6.1-sp2 support J2EE-1.3 spec by default?

hi All,
          Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a simple
          Filter servlet, but it didn't work at all.
          I tried to find some docs related to J2EE spec compliance and they say the
          default is J2EE-1.3. Can anyone tell me the default J2EE spec supported by
          WLS6.1-sp2? And how can I check the currently-used J2EE spec in my running
          WLS? How can I switch between J2EE-1.2 and 1.3?
          Thanks
          Liu Yan


I think it is enabled by default. Note that javax.servlet.Filter which is
          shipped with WebLogic is different from one in final Servlet 2.3. Also you
          can search this newsgroup - there are lots of problems with Filters in 6.1.
          If you think that the problem is with your program, try to deploy it on Resin
          or Tomcat to see if it is actually the case.
          Liu Yan <[email protected]> wrote:
          > Thanks for your reply. I found that WLS6.1 DOES support so-called non-final
          > version of J2EE-1.3 spec. And my downloaded version is J2EE-1.3
          > feature-enabled by default. Seems the problem of my filter program.
          > But do you know how to configure J2EE compatibility in admin console? I mean
          > can I switch back and forth between J2EE-1.2 and 1.3?
          > Thanks
          > Liu Yan
          > "Dimitri Rakitine" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
          > :[email protected]...
          >> 6.1 does not support final Servlet 2.3 spec. You can see release notes
          >> for details: http://e-docs.bea.com/wls/docs61/notes/index.html
          >>
          >> Liu Yan <[email protected]> wrote:
          >> > hi All,
          >>
          >> > Just installed WLS6.1-sp2 30-day evaluation. I tested on it with a
          > simple
          >> > Filter servlet, but it didn't work at all.
          >>
          >> > I tried to find some docs related to J2EE spec compliance and they say
          > the
          >> > default is J2EE-1.3. Can anyone tell me the default J2EE spec supported
          > by
          >> > WLS6.1-sp2? And how can I check the currently-used J2EE spec in my
          > running
          >> > WLS? How can I switch between J2EE-1.2 and 1.3?
          >>
          >> > Thanks
          >>
          >> > Liu Yan
          >>
          >>
          >>
          >>
          >> --
          >> Dimitri
          Dimitri

Apache Plugin in linux for WLS6.0 sp1 and (?sp2?)

This message is a little long,
The following message is arranged in 4 parts where:
1. Conclusion and Sugestions.
2. Tests Environment
3. Simple plugin environment
4. Virtual Hosting with apache
Any comment and help will be welcome
Conclusion
The plug-in has not been tested and documented and therefore does not
work in the described environment. The plugin parameter needs to be :
1. Syntaxly rewieved. The parameters not starting with
WebLogic.... (like PathTrim, PathPrepend, ConnectTimeoutSecs,
ConnectRetrySecs, Debug, DebugConfigInfo, StatPath, ErrorPage,
HungServerRecoverSecs, Idempotent, CookieName,
DefaultFileName, MaxPostSize, MatchExpression, FileCaching,
SecureProxy, TrustedCAFile, RequireSSLHostMatch,
SSLHostMatchOID) are confusing and couyld be bug/problem
generators when adding other non BEA modules in apache. I
would suggest to have all the parameter starting with a common
root like WebLogic or Wls or something else deterministic
2. Better documented. The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Test Environment
The tests described below has been done with the following system
environment.
Operating System:
RedHat 7.0 + glibc updates + network uodates, kernel level 2.2.17-14
RedHat 7.1 + updates, kernel 2.4.2-2
Java Level:
On the RedHat 7.0 system the default Java JVM provided in the BEA
distribution
On the RedHat 7.1 system the Sun JDK 1.3.1 for Linux
Apache: 1.3.19
DNS: one system called cordoba.paris.inetpc.com with 3 cnames added
(w1cordoba, w2cordoba, w3cordoba)
The Weblogic installtion is coming from a single reference system.
This system runs under RedHat 6.2 + latest update levels. The WebLogic
tree directory has been deployed in both systems and the JVM set in the
proper manner. Despite the well known problem with the default webapp
Wls 6.0 works fine and as expected. Default ports are used (7001).
The apache environment works fine too. In a single apache environment
and with the virtual hosting supporting the 3 cnames (w1cordoba,
w2cordoba, w3cordoba)
In both systems the behavior and and problems are equal.
Simple plugin environment
A single default web app runs under wls6.0. calling the wls60 thru the
URI: "http://cordoba:7001" works fines and the Welcome.html default page
is properly displayed. Similar tests have been done with a jsp page and
works fine too.
The httpd.conf file has been set has described in the documentation and
as follow:
LoadModule weblogic_module modules/mod_wl.so
WebLogicHost cordoba
WebLogicPort 7001
Debug ON
DebugConfigInfo ON
<location /wls>
SetHandler weblogic-handler
PathTrin /wls
</location>
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:
Sun Jun 3 16:34:19 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:34:19 2001 The request string is '/wls'
Sun Jun 3 16:34:19 2001 INFO: SSL is not configured
Sun Jun 3 16:34:19 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:34:19 2001 INFO: New NON-SSL URL
Sun Jun 3 16:34:19 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:34:19 2001 Connected to cordoba:7001
Sun Jun 3 16:34:19 2001 INFO: sysSend 343
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 parsed all headers OK
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 r->status=302 returning 0
Sun Jun 3 16:36:08 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:36:08 2001 The request string is '/wls'
Sun Jun 3 16:36:08 2001 INFO: SSL is not configured
Sun Jun 3 16:36:08 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:36:08 2001 INFO: New NON-SSL URL
Sun Jun 3 16:36:08 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:36:08 2001 Connected to cordoba:7001
Sun Jun 3 16:36:08 2001 INFO: sysSend 343
Sun Jun 3 16:36:08 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:36:08 2001 parsed all headers OK
Sun Jun 3 16:36:08 2001 r->status=302 returning 0
Virtual Hosting with Apache
These tests aim to validate a production environment where an entry cell
of apache servers will serve static pages and route dynamic requests to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute by
location or a full reroute has done the same results than stated in
"Simple plugin environment".
[att1.html]

Hi
I am trying to configure the following pattern:
->https->apache->SSL->weblogic
using the apache plugin that you provided from the distribution.
There is no way to let it work.
the apache site trying to connect to weblogic is a virtual host, follows the config
file.
Checking the DEbugDebug config monitor it I discover that SecureProxy it is OFF
istead of ON and checking the debug file I've got this message:
INFO: ssl is not activated..
It means that despite of SecureProxy set to ON, it is still working in clear.
I have the same behaviour using 6.0, SP1, SP2 and 6.1
(If there more documentation about it in 6.1, please let me know where!)
Please, anyone can send me documentation about it or help me???
# <-- Start XXXXX Virtual Host
<VirtualHost XXXXXX>
SSLEngine on
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateKeyFile XXXX
SSLCertificateFile XXXXX
<Location />
AddHandler weblogic-handler .jsp
</Location>
<IfModule mod_weblogic.c>
SecureProxy ON
RequireSSLHostMatch false
TrustedCAFile /ssl/certs/ca.pem
Debug ALL
DebugConfigInfo ON
WebLogicHost XXXXX
WebLogicPort XXXXX
ErrorPage /pm/private/frame_044_error_500.htm
MatchExpression *.jsp
</IfModule>
</VirtualHost>
# <-- End XXXXX Virtual Host
"Jong Lee" <[email protected]> wrote:
>
1. Syntaxly rewieved.
Worth considering for the next major release.
2. Better documented.
Yes, 6.1 release is doing a much better job of documentation!
The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. If apxs is used to update the module, end user should not need
to worry about adding/changing these two lines.
But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin
is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Again, better on 6.1 docs.
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
"DefaultFileName Welcome.html" should be used in your httpd.conf
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:on 6.1, if relative URI is used in sendRedirect(), PathTrim and
PathPrepend should be taken care automatically. i.e:
in httpd.conf:
PathTrim /weblogic
PathPrepend /abc
in a jsp page:
response.sendRedirect("HelloWorld.jsp");
The plugin and wls will be smart enough to set Location header
to the following:
Location: http://apache_host:apache_port/weblogic/HelloWorld.jsp
Then the plugin will trim the /weblogic and prepend /abc to it
i.e:
http://wls_host:wls_port/abc/HelloWorld.jsp
Virtual Hosting with Apache
These tests aim to validate a production environment where an entrycell
of apache servers will serve static pages and route dynamic requests
to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute
by
location or a full reroute has done the same results than stated in
"Simple plugin environment".Absolutely. in 6.1 you can specify different weblogic hosts per
vhost. Even you can use MatchExresspion or <Location> to define
different parameters per mime type and path:
i.e:
MatchExpression *.jsp WebLogicHost=www.bea.com|WebLogicPort=7001|DefaultFileName=/Welcome.html
MatchExpression *.html WebLogicCluster=weblogic1:7001,weblogic2:7002|Debug=ALL
<Location /weblogic>
WebLogicHost thankyou.com
</Location>
Where Location takes the precedence.
Anyway, 6.1 apache plugin should be a much better modules.
We also support apache2.0(beta) in 6.1. Unfortunately,
the apache2.0 binaries were unable to be included in the 6.1
beta installer. There might be a separate down-load for that.
Thank you for your great suggestions/comments.
thanks
Jong

WLS6.1 SP2/JDK1.3.1_03/HTTP 302 Error

Hello,
we use WLS6.1 SP2 with JDK1.3.1_03 and we get sometimes an HTTP 302 error, when
a JSP-page is requested. The error appears in the browser is following:
     This document you requested has moved temporarily.
     It's now at </zv/account/accountOverflow.jsp>.
Normally the generated html should be appear. When I click on the generated link
the html page appears.
When we change the JDK to version JDK1.3.1_01 it works, means the generated html
page appears.
Does anybody knows something of this problem, is this a JDK or a BEA problem ?
Regards
Michael

We are running a WebLogic 6.1 sp2 cluster in production and about          > every two days we start to get errors in the WLS log like this:
          > <Oct 8, 2002 2:17:09 PM CDT> <Info> <Cluster> <dadgsunapp1>
          > <wls1> ExecuteThread: '1' for queue: 'Replication'> <> <> <000117>
          > <Got stale replication request for object -5479642219657940840>
          > Sessions continually attempt to migrate to their secondary server with
          > the result that the cluster spends most of its time thrashing and client
          > HTTP requests time out. At the time this happens we have also noticed
          > that the servers running the WebLogic nodes have a large number of
          > sockets in CLOSE_WAIT status.
          > Has anyone run into this problem? All advice is welcome.
          I've seen it with both 5.x and 6.x, and also in relatively large clusters. I
          believe it is caused when an application changes session data too often,
          which causes the replication to clog up (like a traffic jam) and fail. I
          believe I posted something on this a few (maybe 6) months ago, but to
          alleviate it, try to figure out if you can do less updates to the session
          data. Also, try sp3 (just in case).
          Peace,
          Cameron Purdy
          Tangosol, Inc.
          http://www.tangosol.com/coherence.jsp
          Tangosol Coherence: Clustered Replicated Cache for Weblogic
          "Bob Withers" <[email protected]> wrote in message
          news:[email protected]..
          >

Configuring Default Web Application w/ WLS6.0 SP2

          I have 2 Machines with no shared file system.
          I have identical directory structures on both:
          /usr/local/weblogic/config/qadomain/applications/DefaultWebApp
          I have 2 Servers within the cluster:
          ServerA and ServerB within ClusterA
          I have 1 DefaultWebApp that I have Chosen ClusterA
          When starting ServerA I receive and error:
          <Error deploying application DefaultWebApp: ServerB not deployed on ServerA>
          Can someone tell me the what's missing in this configuration?


You should add it to config.xml by yourself, should be something like:
<Server AdministrationPort="0"
ListenPort="8001" Name="testServer">
<Log FileName="config/mydomain/logs/weblogic-testServer.log"
Name="testServer"/>
<WebServer DefaultWebApp="WebApp_testServer"
LogFileName="config/mydomain/logs/access-testServer.log"
Name="testServer"/>
<KernelDebug Name="testServer"/>
<SSL Name="testServer"/>
<ServerDebug Name="testServer"/>
</Server>
Good luck.
"Ton Bode" <[email protected]> wrote in message
news:[email protected]..
Sorry, wrong group, and it seems to be a bug in the WLS 6.0 sp1 and sp2
versions
"Ton Bode" <[email protected]> wrote in message
news:3b5ec3e3$[email protected]..
I am running WLS6.0 sp2 on Win2K.
When I try to select a Default Web Application (selecting myserver,
Configuration, HTTP, Default Web Application) there is no Application
that
I
can select. I suppose at least the DefaultWebApp_myserver should be
available. This WebApp is deployed and targeted to myserver. But also
Console and Certificate should be available. What do I need to do inorder
to select a Web Application as default?
Ton Bode

Difference between WLS6.1 SP2 and SP3

I have recently tested my application in WLS 6.1 SP3 (who work normally in WLS 6.1 SP2) , I have problem with my jsp page for merging a jsp in another
What need I do to correct it ?

wliu wrote:
When i deploy the database pool,it throw the following exception:could find
ocicore9.dll
and my config.xml is:
<JDBCConnectionPool DriverName="oracle.jdbc.OracleDriver"
InitialCapacity="20" MaxCapacity="20" Name="oracleOciPool"
Password="{3DES}IHsomrZ2hLxZiBrV9VXTlQ=="
PreparedStatementCacheSize="100"
Properties="user=db9i;password=password;server=db9i"
RefreshMinutes="5" Targets="MyCluster,server2,server1"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="dual" URL="jdbc:oracle:oci:@"/>
I am running at w2k and wls6.1 sp2
oracle runnint at Tru64 unix
and classpath has contained classes12.zip which is the lastest version, path
has contain %BEA_HOME%\bin\oci901_8 directoryOcicore.dll may be an Oracle OCI library. Your path (the path list that Tru64 Unix
uses to search for native libraries) must also contain all the standard Oracle client
libraries.
Joe

XA error when starting WLS6.1(SP2) with XA connection pools

I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am using the XA jDriver/Oracle
for my connection pools but when I start the server I get the following error:-
<Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net> <myserver> <main>
<system> <> <001060> <Cannot startup connection pool "test" weblogic.common.ResourceException:
java.s
ql.SQLException: open failed for XAResource 'test' with error XAER_RMERR : A resource
manager error has occured in the transaction branch. Check Oracle XA trace file(s)
(if any) for database
errors. The Oracle XA trace file(s) are located at the directory where you start
the Weblogic Server, and have names like xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
at weblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:200)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnectionEnvFactory.java:209)
at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:57)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
I can create a normal (non-X/A) connection pools without any problems however the
X/A one will just not work at all. I spotted on a goggle newsgroup that someone else
had this exact same problem but running on WINNT but there was no resolution. The
following is the trace from the XA trace file:-
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
181020.21758.1.-662733300:
xaoopen: xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
=.+DbgFl=0x15,rmid=-662733300,flags=0x0
181020.21758.1.-662733300:
ORA-12547: TNS:lost contact
181020.21758.1.-662733300:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
181020.21758.1.-662733300:
xaoopen: return -3
I have the whole application up and running fine on a WIN2000 platform with its own
database on the local machine. Also I can point my WIN2000 application to use the
database on the HPUX11 machine no problem.
This leads me to think this is a TNS related problem as I cant think of anything
else !.
Any help greatly appreciated...!
Martin

Hi Martin,
Using oracles Advanced Security Options can cause this, comment security
related lines out of your "sqlnet.ora" they generally have the words,
ENCRYPTION or CRYPTO in them.
Also try to set ORACLE_SID environment variable, like in the server startup
script.
ORACLE_SID=<SID_NAME>
export ORACLE_SID
Try it and see if it works. This is purely an Oracle issue not WebLogic
related. Try to contact Oracle support if you cannot resolve the issue with
above steps. You may have to reinstall the Client.
hth
sree
"Martin Porter" <[email protected]> wrote in message
news:[email protected]...
>
I am running WLS6.1 on HPUX11 with an Oracle Database 8.1.7. I am usingthe XA jDriver/Oracle
for my connection pools but when I start the server I get the followingerror:-
>
<Apr 25, 2002 6:10:21 PM BST> <Error> <JDBC> <neptune.xenicom.net><myserver> <main>
<system> <> <001060> <Cannot startup connection pool "test"weblogic.common.ResourceException:
java.s
ql.SQLException: open failed for XAResource 'test' with error XAER_RMERR :A resource
manager error has occured in the transaction branch. Check Oracle XA tracefile(s)
(if any) for database
errors. The Oracle XA trace file(s) are located at the directory whereyou start
the Weblogic Server, and have names like xa_<pool_name><MMDDYYYY>.trc.
at weblogic.jdbc.oci.xa.XAConnection.<init>(XAConnection.java:58)
atweblogic.jdbc.oci.xa.XADataSource.getXAConnection(XADataSource.java:601)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:200)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:57)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.updateDeployments(Unknown Source)
atweblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(
ServerMBean_CachingStub.java:2761)
atweblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Appl
icationManager.java:370)
atweblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManage
r.java:160)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:636)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:6
21)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:359)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
atweblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy38.start(Unknown Source)
atweblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(
ApplicationManagerMBean_CachingStub.java:480)
atweblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.makeConnection(XAConnec
tionEnvFactory.java:209)
atweblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnec
tionEnvFactory.java:57)
atweblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.j
ava:698)
atweblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282
atweblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623
atweblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:329)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployment
Target.java:279)
atweblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(D
eploymentTarget.java:233)
atweblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deploym
entTarget.java:193)
>
I can create a normal (non-X/A) connection pools without any problemshowever the
X/A one will just not work at all. I spotted on a goggle newsgroup thatsomeone else
had this exact same problem but running on WINNT but there was noresolution. The
following is the trace from the XA trace file:-
ORACLE XA: Version 8.1.7.0.0. RM name = 'Oracle_XA'.
181020.21758.1.-662733300:
xaoopen:xa_info=Oracle_XA+Acc=P/imsi/imsi+SesTm=100+DB=test+Threads=true+LogDir
=.+DbgFl=0x15,rmid=-662733300,flags=0x0
181020.21758.1.-662733300:
ORA-12547: TNS:lost contact
181020.21758.1.-662733300:
xaolgn_help: XAER_RMERR; OCIServerAttach failed. ORA-12547.
181020.21758.1.-662733300:
xaoopen: return -3
I have the whole application up and running fine on a WIN2000 platformwith its own
database on the local machine. Also I can point my WIN2000 application touse the
database on the HPUX11 machine no problem.
This leads me to think this is a TNS related problem as I cant think ofanything
else !.
Any help greatly appreciated...!
Martin

Possible Memory Leak in WLS6.1-SP2

Hello,
I need your help in getting to the bottom of a memory issue we are facing.
We are running EJB based applications on Web Logic Server (WLS) 6.1 SP2 on Solaris
8 servers using 1.3.1_03 JDK. There are several applications running, but lets
use one of them as example.
I am using the following JDK parameters:
-XX:NewSize=96m -XX:MaxNewSize=96m -Xms384m -Xmx384m -XX:SurvivorRatio=2
The memory values on Solaris, before the application is started, are as follows:
Real memory = 4096M, Free memory = 2415M, Swap in use = 1059M, Swap free = 2322M
When I start the applications, I can see the memory foot print for this application
at around 540 Meg. Since JVM pre-allocates heap space, I expect this number to
remain constant as the application is stressed. But this does not happen, and
it puzzles me. I see the memory footprint of application go up, and that makes
me believe that is a memory leak somewhere. Since heap space remains below the
selected limit (384M), and the application does not over-run heap, it makes me
believe that the memory leak is not happening in application code; rather it is
Web Logic Server that is leaking memory.
As the application runs, the memory footprint increase from 540M to almost 900M,
to the point the system is left with very low free swap space, and the application
(not necessarily this particular one) starts throwing OutOfMemoryError.
At this point, it becomes impossible to recover and the only way out is to bounce
WLS.
Does it sound like a memory leak issue to you ? Do you agree that it look like
a WLS memory leak?
If anybody had similar experience, please help me with your advice. I would be
very interested in knowing how you diagnosed the problem and what solution did
you apply.
Thanks,
Asad Faizi

The native OCI driver is not allocating out of the Java heap, but rather
from the OS (or the c rtl) so the Java heap parameters do not affect it. I
don't know if it is a problem that you see or just normal behavior.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Asad Faizi" <[email protected]> wrote in message
news:[email protected]...
>
Cameron,
We are using Oracle-8.1.7r3 driver. Can you give me some more informationas to
why do you suspect Oracle JDBC driver? Have you had similar experience ?How did
you diagnose this and what did you do to fix it?
Thanks,
Asad Faizi
"Cameron Purdy" <[email protected]> wrote:
Probably a JDBC driver (Oracle OCI?).
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com/coherence.jsp
Tangosol Coherence: Clustered Replicated Cache for Weblogic
"Asad Faizi" <[email protected]> wrote in message
news:[email protected]...
Hello,
I need your help in getting to the bottom of a memory issue we arefacing.
We are running EJB based applications on Web Logic Server (WLS) 6.1SP2 on
Solaris
8 servers using 1.3.1_03 JDK. There are several applications running,but
lets
use one of them as example.
I am using the following JDK parameters:
-XX:NewSize=96m -XX:MaxNewSize=96m -Xms384m -Xmx384m -XX:SurvivorRatio=2
The memory values on Solaris, before the application is started, areas
follows:
Real memory = 4096M, Free memory = 2415M, Swap in use = 1059M, Swapfree =
2322M
When I start the applications, I can see the memory foot print forthis
application
at around 540 Meg. Since JVM pre-allocates heap space, I expect thisnumber to
remain constant as the application is stressed. But this does not
happen,
and
it puzzles me. I see the memory footprint of application go up, andthat
makes
me believe that is a memory leak somewhere. Since heap space remainsbelow
the
selected limit (384M), and the application does not over-run heap,it
makes me
believe that the memory leak is not happening in application code;rather
it is
Web Logic Server that is leaking memory.
As the application runs, the memory footprint increase from 540M toalmost
900M,
to the point the system is left with very low free swap space, andthe
application
(not necessarily this particular one) starts throwing OutOfMemoryError.
At this point, it becomes impossible to recover and the only way outis to
bounce
WLS.
Does it sound like a memory leak issue to you ? Do you agree that itlook
like
a WLS memory leak?
If anybody had similar experience, please help me with your advice.I
would be
very interested in knowing how you diagnosed the problem and what
solution
did
you apply.
Thanks,
Asad Faizi

Using MessagingBridge for WLS6.1-SP3 and MQSeries 5.2

          I am trying to use the MessagingBridge with MQSeries 5.2.
          I have an MDB to consume messages from MQSeries queue. I created
          the MesageingBridge with source (being the MQS queue) and target
          (being WLS queue) but the bridge never channeled the messages from
          MQSeries source queue to WLS destination queue.
          Here are segments from config.xml:
          <JMSServer Name="JMSServer" Targets="myserver">
          <JMSQueue JNDIName="MQ_TARGET_QUEUE" Name="MQS Target Queue" StoreEnabled="default"/>
          </JMSServer>
          <JMSBridgeDestination
          Classpath="c:\MQSeries\ma88\samples\base;c:\MQSeries\ma88\lib\com.ibm.mq.jar;c:\MQSeries\ma88\lib\com.ibm.mqjms.jar;c:\MQSeries\ma88\lib\jms.jar;c:\MQSeries\ma88\lib\jndi.jar;c:\MQSeries\ma88\lib\fscontext.jar;c:\MQSeries\ma88\lib\providerutil.jar;c:\MQSeries\ma88\lib\connector.jar"
          ConnectionFactoryJNDIName="MQSeriesQueueManager"
          ConnectionURL="t3://127.0.0.1:7001"
          DestinationJNDIName="NotifMsgQueue" Name="MQSSourceDestination"/>
          <JMSBridgeDestination
          ConnectionFactoryJNDIName="WLSMQS_Connection_Factory"
          ConnectionURL="t3://127.0.0.1:7001"
          DestinationJNDIName="MQ_TARGET_QUEUE" Name="WLSTargetDestination"/>
          <MessagingBridge AsyncEnabled="true" DurabilityEnabled="true"
          Name="MQSeries Messaging Bridge" QOSDegradationAllowed="false"
          QualityOfService="Duplicate-okay"
          SourceDestination="MQS Source Destination" Started="true"
          TargetDestination="WLSTargetDestination" Targets="myserver"/>
          <StartupClass
          Arguments="QManager=QM_de8u5p,QMJNDIName=MQSeriesQueueManager,QManagerHost=127.0.0.1,
          QManagerPort=1414,NotificationsQueue=AppNotifQueue,NQJNDIName=NotifMsgQueue"
          ClassName="com.wbiex.MQSeriesStartup" FailureIsFatal="false"
          Name="MQSeriesStartup" Targets="myserver"/>
          Note: The MDB was able to access and consume messages off the MQSeries NotifMsgQueue
          queue
          without the bridge .
          Thank you very much for your help.


First of all, CR081414_61sp3.jar is not supposed to be put in
          the CLASSPATH. It contains the adapter files you need to
          run the bridge. You don't need it anyway because CR081511_61sp3.jar
          contains the newer version of the adapter files. You need to put
          CR081414_61sp3.jar to your WLS CLASSPATH, and also extract the a
          adapter files (*.rar) and put them in the directory where your
          config.xml gets the adapters for deployment.
          Did you put all necessary MWSeries stuff in the WLS CLASSPATH
          and PATH. I am sure you have done something there to make
          your startup class work. Just make sure you have all of them.
          Them are listed in "Using Foreign JMS Providers with WebLogic Server".
          By the way, what is the error you got? Did you look at the server
          log?
          You can also turn on bridge debugging.
          -Dweblogic.Debug.DebugMessagingBridgeStartup=true
          -Dweblogic.Debug.DebugMessagignBridgeRuntime=true
          Debugging information will show up in the server log by default.
          Dongbo
          Jim Allen wrote:
          >
          > Thanks Dongbo,
          > I got both patches CR081511_61sp3.jar and CR081404_61sp3.jar
          > and added them to WLS CLASSPATH.
          > The connectionURLs for both source and target destinations are
          > the same because I am using WLS JNDI which is located in same
          > server. I have startup class that creates MQSeries connection
          > factory and a queue and binds them to WLS JNDI tree.
          > I also removed the MQSereis jars from AdapterClassPath but
          > still the Bridge is not working.
          >
          > Please help !! thanks very much again
          >
          > Dongbo Xiao <[email protected]> wrote:
          > >Something in your configuration looks wrong. The connectionURL
          > >you have for both the MQSeries bridge destination and WLS bridge
          > >destination are the same, which cannot be right. Another thing
          > >is that it is not recommended to put MQSeries stuff in AdapterClassPath.
          > >You have to have MQSeries stuff in the CLASSPATH and PATH for
          > >the WLS server that the bridge is running on.
          > >
          > >Take a look at the "Using Foreign JMS Providers with WebLogic Server
          > >"
          > >Tom recommended to you.
          > >
          > >Also you need to get the latest patches for 6.1SP3.
          > >
          > >Hope this helps.
          > >Dongbo
          > >
          > >
          > >Jim Allen wrote:
          > >>
          > >> I am trying to use the MessagingBridge with MQSeries 5.2.
          > >> I have an MDB to consume messages from MQSeries queue. I created
          > >> the MesageingBridge with source (being the MQS queue) and target
          > >> (being WLS queue) but the bridge never channeled the messages from
          > >> MQSeries source queue to WLS destination queue.
          > >> Here are segments from config.xml:
          > >>
          > >> <JMSServer Name="JMSServer" Targets="myserver">
          > >> <JMSQueue JNDIName="MQ_TARGET_QUEUE" Name="MQS Target Queue"
          > >StoreEnabled="default"/>
          > >> </JMSServer>
          > >> <JMSBridgeDestination
          > >> Classpath="c:\MQSeries\ma88\samples\base;c:\MQSeries\ma88\lib\com.ibm.mq.jar;c:\MQSeries\ma88\lib\com.ibm.mqjms.jar;c:\MQSeries\ma88\lib\jms.jar;c:\MQSeries\ma88\lib\jndi.jar;c:\MQSeries\ma88\lib\fscontext.jar;c:\MQSeries\ma88\lib\providerutil.jar;c:\MQSeries\ma88\lib\connector.jar"
          > >> ConnectionFactoryJNDIName="MQSeriesQueueManager"
          > >> ConnectionURL="t3://127.0.0.1:7001"
          > >> DestinationJNDIName="NotifMsgQueue" Name="MQSSourceDestination"/>
          > >> <JMSBridgeDestination
          > >> ConnectionFactoryJNDIName="WLSMQS_Connection_Factory"
          > >> ConnectionURL="t3://127.0.0.1:7001"
          > >> DestinationJNDIName="MQ_TARGET_QUEUE" Name="WLSTargetDestination"/>
          > >> <MessagingBridge AsyncEnabled="true" DurabilityEnabled="true"
          > >> Name="MQSeries Messaging Bridge" QOSDegradationAllowed="false"
          > >> QualityOfService="Duplicate-okay"
          > >> SourceDestination="MQS Source Destination" Started="true"
          > >> TargetDestination="WLSTargetDestination" Targets="myserver"/>
          > >> <StartupClass
          > >> Arguments="QManager=QM_de8u5p,QMJNDIName=MQSeriesQueueManager,QManagerHost=127.0.0.1,
          > >> QManagerPort=1414,NotificationsQueue=AppNotifQueue,NQJNDIName=NotifMsgQueue"
          > >> ClassName="com.wbiex.MQSeriesStartup" FailureIsFatal="false"
          > >> Name="MQSeriesStartup" Targets="myserver"/>
          > >>
          > >> Note: The MDB was able to access and consume messages off the MQSeries
          > >NotifMsgQueue
          > >> queue
          > >> without the bridge .
          > >>
          > >> Thank you very much for your help.

WLS6.1 SP2 - Sorting JMS messages by priority fails to work

          I have an app that uses a QueueSender to send messages of various priorities, 5
          and 9:
          queueSender.send(myMessage, DeliveryMode.PERSISTENT, myMessagePriority, Message.DEFAULT_TIME_TO_LIVE);
          I have configured a JMS Destination Key, JMSPriority(int, sort Descending), and
          bound it to the destination (from config.xml):
          <JMSServer Name="EJBTestServer" PagingStore="EJBTestStore"
          Store="EJBTestStore" Targets="fmlon66039server">
          <JMSQueue DestinationKeys="JMSPriority" JNDIName="EJBTestQueue"
          Name="EJBTestQueue" PriorityOverride="-1" StoreEnabled="default"/>
          </JMSServer>
          <JMSDestinationKey Direction="Descending" KeyType="Int"
          Name="JMSPriority" Property="JMSPriority"/>
          However the single MDB listening on the destination just gets the messages in
          the order they're sent: I would have expected all the priority 9 messages to come
          first.
          Note to simulate a long initialisation process, the MDB sleeps on receipt of the
          first message it receives; this gives the sender time to finish its sending.
          The sender sends one message per txn. The MDB receives one message per txn too.
          To prove my txns are 'good' my app logs the XID and the tx state whenever my app
          sends or receives a message.
          Any ideas anyone? Has anyone else got sorting by JMS priority to work in 6.1 SP2?
          simon.


I've submitted a doc enhancement request. Good idea.
          In general, doc changes are possible, but limited in older releases.
          Tom, BEA
          Simon Spruzen wrote:
          > Thanks, I didn't know about the pipe-line (can this be added to the documentation,
          > if you're still keeping 6.1 docs going? It might be also worth stressing in the
          > docs that even when sorting by priority (or anything else for that matter), it's
          > still only a hint that the server may choose to disregard in the interests of
          > timely message delivery. I 'knew' this, but my brain wasn't in gear.)
          >
          > You can probably guess how many messages my original test app was sending...
          >
          >
          > simon.
          >
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>There is a pipe-line of messages between the JMS server and the MDB.
          >>Messages get sorted on the JMS server but not within the pipe-line.
          >>The default size is 10. To reduce it, define a custom connection
          >>factory on the console for the MDB and modify the MDB descriptor
          >>to point to the custom connection factory's JNDI name.
          >>On the connection factory, reduce "MessagesMaximum"
          >>to 1 (the pipe-line size), and, for purposes of supporting
          >>WL MDBs properly, enable transactions, and set the acknowledge
          >>policy to "acknowledge-before".
          >>
          >>Tom, BEA
          >>
          >>Simon Spruzen wrote:
          >>
          >>>I have an app that uses a QueueSender to send messages of various priorities,
          >>
          >>5
          >>
          >>>and 9:
          >>>
          >>>queueSender.send(myMessage, DeliveryMode.PERSISTENT, myMessagePriority,
          >>
          >>Message.DEFAULT_TIME_TO_LIVE);
          >>
          >>>
          >>>I have configured a JMS Destination Key, JMSPriority(int, sort Descending),
          >>
          >>and
          >>
          >>>bound it to the destination (from config.xml):
          >>>
          >>>
          >>><JMSServer Name="EJBTestServer" PagingStore="EJBTestStore"
          >>> Store="EJBTestStore" Targets="fmlon66039server">
          >>> <JMSQueue DestinationKeys="JMSPriority" JNDIName="EJBTestQueue"
          >>> Name="EJBTestQueue" PriorityOverride="-1" StoreEnabled="default"/>
          >>></JMSServer>
          >>>
          >>>
          >>><JMSDestinationKey Direction="Descending" KeyType="Int"
          >>> Name="JMSPriority" Property="JMSPriority"/>
          >>>
          >>>
          >>>
          >>>
          >>>However the single MDB listening on the destination just gets the
          >>
          >>messages in
          >>
          >>>the order they're sent: I would have expected all the priority 9 messages
          >>
          >>to come
          >>
          >>>first.
          >>>
          >>>Note to simulate a long initialisation process, the MDB sleeps on receipt
          >>
          >>of the
          >>
          >>>first message it receives; this gives the sender time to finish its
          >>
          >>sending.
          >>
          >>>The sender sends one message per txn. The MDB receives one message
          >>
          >>per txn too.
          >>
          >>>To prove my txns are 'good' my app logs the XID and the tx state whenever
          >>
          >>my app
          >>
          >>>sends or receives a message.
          >>>
          >>>Any ideas anyone? Has anyone else got sorting by JMS priority to work
          >>
          >>in 6.1 SP2?
          >>
          >>>simon.
          >>
          >

Can?t Precompile JSP?s on WLS6.0 SP2

Hi,
          I?m trying to Precompile my JSP?s but when I restart I get this error:
          <Jul 30, 2002 4:57:11 PM EDT> <Error> <HTTP> <[WebAppServletContext(5611782,posadasWebApp)] failure pre-compiling JSP's
          weblogic.utils.ParsingException: nested TokenStreamException: antlr.TokenStreamException: Could not include ../../../includes/allHeaders.jsp
          at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:900)
          at weblogic.servlet.jsp.JspParser.doit(JspParser.java:71)
          at weblogic.servlet.jsp.JspParser.parse(JspParser.java:139)
          at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:113)
          at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253)
          Does anybody have an idea on what can be wrong?
          Thanx in Advanced!!!
          Gerardo


may be a known issue. i don't recall.
          i would suggest you to try with the latest 60 SP2 RP3 and see if that
          helps. If not, pls work with supoprt.
          gerardo jimenez wrote:
          > Hi,
          >
          > I?m trying to Precompile my JSP?s but when I restart I get this error:
          >
          > <Jul 30, 2002 4:57:11 PM EDT> <Error> <HTTP> <[WebAppServletContext(5611782,posadasWebApp)] failure pre-compiling JSP's
          > weblogic.utils.ParsingException: nested TokenStreamException: antlr.TokenStreamException: Could not include ../../../includes/allHeaders.jsp
          > at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java:900)
          > at weblogic.servlet.jsp.JspParser.doit(JspParser.java:71)
          > at weblogic.servlet.jsp.JspParser.parse(JspParser.java:139)
          > at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:113)
          > at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:253)
          >
          > Does anybody have an idea on what can be wrong?
          >
          > Thanx in Advanced!!!
          >
          > Gerardo
          >

** MQSeries WLS6-sp2 JMSException

Similar Messages

Maybe you are looking for