WLS 6 and MQSeries
we have been successfully using IBMs JMSAdmin with the
weblogic.jndi.WLInitialContextFactory on wls 5.1.8 and MQ 5.2 on w2k,
simply by setting the appropriate parameters in JMSAdmin.config. We
tryied the same with wls 6 and failed bitterly. 2 questions:
1.) does it make sense to try an bind JMSAdmin with a wls jndi
service, or is there a better way, eg. to completely rely on the wls
JMS service for registering MQSeries connections? how would that work?
2.) does anybody have a clou, where i can find that article, i think
it's by steve felts on using foreign JMS providers with wls? i think
the link on dev2dev is broken?
many thanxx
leopold
The JNDI provider in WLS is not persistent. Any data you put in it while the
server is running goes away when the server is shut down. You're better off
using JMSAdmin to store the MQSeries JMS objects in a JNDI "filesystem" or
LDAP provider. Then, WLS can look up the MQSeries objects from there. The
IBM "JMSAdmin" won't even let you put MQSeries JMS objects into the WLS JNDI
provider, and if it did, they would go away when the server is shut down.
greg
"leopld goess" <[email protected]> wrote in message
news:[email protected]..
> we have been successfully using IBMs JMSAdmin with the
> weblogic.jndi.WLInitialContextFactory on wls 5.1.8 and MQ 5.2 on w2k,
> simply by setting the appropriate parameters in JMSAdmin.config. We
> tryied the same with wls 6 and failed bitterly. 2 questions:
> 1.) does it make sense to try an bind JMSAdmin with a wls jndi
> service, or is there a better way, eg. to completely rely on the wls
> JMS service for registering MQSeries connections? how would that work?
>
> 2.) does anybody have a clou, where i can find that article, i think
> it's by steve felts on using foreign JMS providers with wls? i think
> the link on dev2dev is broken?
>
>
> many thanxx
> leopold
Similar Messages
-
Message Bridge between WLS 6.1 sp3 and MQSeries 5.2
Hi,
I'm really struggling with getting the Message Bridge working with Weblogic 6.1
sp3 and MQSeries 5.2. Currently I have both installed on the same Windows 2000
machine. First I'll pose some questions that I have, then I discuss the error
I'm getting. Here are my questions:
1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml. Within the
ra.xml deployment descriptor there are config-properties for ConnectionURL, InitialContextFactory,
ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue is the source
jms destination bridge and my weblogic queue is the target jms destination bridge,
what values do I set for the listed config-properties? I can't seem to find any
documentation on what these values should be. Am I missing something? Do these
values even have to be set?
2. When I go to install a Weblogic instance to a different physical machine what
has to be installed in terms of MQSeries? So I'll have MQSeries on physical machineA
and Weblogic on a different physical machineB. I want machineA to forward all
messages placed on a MQSeries Queue to forward them to machineB where the weblogic
Queue resides. Does machineB also have to contain an MQSeries installation?
Or can I just grab the necessary libraries and jar files and place them on the
Weblogic machineB so they can be included?
3. Is it correct that if I distribute Weblogic onto one physical server and MQSeries
onto a different physical server that I cannot use Exactly-once quality of service?
Other notes:
1. I have the following patches installed for Weblogic 6.1 sp3:
CR081404_610sp3.jar
CR081511_61sp3.jar
2. Here is the commands I used to create my ConnectionFactory and Queue within
MQSeries:
def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
def q(MQTestQueue) qmanager(QM_jeff) queue(default)
Okay...here is my error:
<21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred in bridge
"Messaging Bridge" during transferring messages (java.lang.Exception: java.lang.
reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
javax.resource.ResourceException: Error creating consumer or receiving message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
at $Proxy82.receive(Unknown Source)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
Has anyone see this error before? Here is part of my ra.xml file....I just put
these entries in to see what happens:
<config-property>
<config-property-name>ConnectionURL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
</config-property>
<config-property>
<config-property-name>InitialContextFactory</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
</config-property>
<config-property>
<config-property-name>ConnectionFactoryJNDI</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>MQTestConnectionFactory</config-property-value>
</config-property>
<config-property>
<config-property-name>DestinationJNDI</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>MQTestQueue</config-property-value>
</config-property>
<config-property>
<config-property-name>DestinationType</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<config-property-name>AdapterType</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>XATransaction</config-property-value>
</config-property>
Here is a snip of my config.xml:
<MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
Name="Messaging Bridge" QualityOfService="Atmost-once"
SourceDestination="Source JMS Bridge Destination"
TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
<JMSBridgeDestination
AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
ConnectionFactoryJNDIName="MQTestConnectionFactory"
ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
Name="Source JMS Bridge Destination"/>
<JMSBridgeDestination
AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
ConnectionURL="t3://localhost:7001"
DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
InitialContextFactory="weblogic.jndi.WLInitialContextFactory" Name="Target
JMS Bridge Destination"/>
Any help would be greatly appreciated. Thank you in advance for your help.
Sincerely,
Jeff
I tried your suggestion and it worked!! The only thing is, it
makes the deployment of the resource adapter a little more
complicated. Now my customers are going to have to edit their
config.xml, instead of just dropping in the appropriate rar into
the applications directory. But one nice side affect of placing
the rar's in a different directory is it makes the Message
Bridge a little more stable. I was finding it to be very
unstable. One time I would startup my Application Server and
everything was fine, then I would shutdown. The next time I
started it up, I would get exceptions. I have yet to see that
behavior with this new configuration.
Thanks again for all of your help, it is greatly appreciated!!
Jeff
Dongbo Xiao <[email protected]> wrote:
>Looks like that somehow you have the adapter deployed
>multiple times, may not be intended. The cause is that
>everything in the application directory will be automatically
>deployed and all of them are added to the config.xml. During
>the next boot, those appear in the config.xml will be deployed and
>everything in the application directory too. As a result, the adapters
>are deployed twice. The complain about runtime mbean not found may
>mean the one that is overridden by the new one.
>
>The work around is not to put your adapters in the application
>directory, instead, put them in a different directory and point to
>the directory in your config.xml.
>
>Dongbo
>Jeff wrote:
>>
>> One more thing...
>> I noticed that the exception specified that it couldn't find
>> mydomain:Location=myserver,Name=jms-xa-
>> adp_Pool_1,ServerRuntime=myserver,Type=ConnectorConnectionPoolRun
>> time MBean, but what's interesting that if I run the following
>> java weblogic.Admin GET -type ConnectorConnectionPoolRuntime -
>> property ActiveConnectionsCurrentCount -url
>> http://localhost:7001 -username xxxx -password xxxx I get the
>> following output:
>>
>> {MBeanName="mydomain:Location=myserver,Name=jms-xa-
>> adp_Pool_3,ServerRuntime=myse
>> rver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCurren
>> tCount=0}}
>> {MBeanName="mydomain:Location=myserver,Name=jms-notran-
>> adp_Pool_2,ServerRuntime=
>> myserver,Type=ConnectorConnectionPoolRuntime"{ActiveConnectionsCu
>> rrentCount=0}}
>>
>> So from that...it looks like the MBean is there. Any ideas why it
>is not being
>> found?
>>
>> Thanks,
>>
>> Jeff
>>
>> "Jeff" <[email protected]> wrote:
>> >
>> >
>> >
>> >Thank you very much!!
>> >
>> >I tried your suggestions and created a general Queue Connection Factory
>> >within
>> >MQSeries. Then I setup my MQSeries JMS Bridge Destination to use
>the
>> >jms-notrans-adp.rar
>> >resource adapter. With this configuration, I can send messages to
>MQSeries
>> >and
>> >they get forwarded to Weblogic.
>> >
>> >But, if I create a XAQueueConnectionFactory within MQSeries I cannot
>> >get the bridge
>> >working at all. I realize that MQSeries has a bug with Transactions
>> >and remote
>> >servers, but I have MQSeries and Weblogic running on the same machine.
>> > I thought
>> >I could setup an XAConnectionFactory in MQSeries, set the MQSeries
>JMS
>> >Bridge
>> >Destination to use the jms-xa-adp.rar and specify Exactly-once QOS
>and
>> >it should
>> >work? I tried it and it didn't work. ( see attachment for weblogic.log
>> >showing
>> >exception ).
>> >
>> >Here is my config.xml:
>> > <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
>> > Name="Request Messaging Bridge" QOSDegradationAllowed="true"
>> > QualityOfService="Exactly-once"
>> > SourceDestination="Source JMS Bridge Destination"
>> > TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
>> > <JMSBridgeDestination
>> > ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
>> > ConnectionURL="t3://localhost:7001"
>> > DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
>Name="Target
>> >JMS Bridge Destination"/>
>> > <JMSBridgeDestination
>> > AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> > ConnectionFactoryJNDIName="MQTestConnectionFactory"
>> > ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
>> > DestinationJNDIName="MQTestQueue"
>> > InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
>> >Name="Source
>> >JMS Bridge Destination"/>
>> >
>> >Again, thank you very much for your response. It helped me a great
>deal.
>> > Any
>> >thoughts on the above problem please foward them along.
>> >
>> >Oh...and to answer the question posed to me, yes the CR081511_61sp3.jar
>> >file is
>> >dated 8/13/2002
>> >
>> >
>> >Sincerely,
>> >
>> >Jeff
>> >
>> >Dongbo Xiao <[email protected]> wrote:
>> >>Please see my comments inline.
>> >>
>> >>
>> >>Jeff wrote:
>> >>>
>> >>> Hi,
>> >>> I'm really struggling with getting the Message Bridge working with
>> >>Weblogic 6.1
>> >>> sp3 and MQSeries 5.2. Currently I have both installed on the same
>> >>Windows 2000
>> >>> machine. First I'll pose some questions that I have, then I discuss
>> >>the error
>> >>> I'm getting. Here are my questions:
>> >>>
>> >>> 1. With the jms-xa-adp.rar there is a ra.xml and a weblogic-ra.xml.
>> >> Within the
>> >>> ra.xml deployment descriptor there are config-properties for ConnectionURL,
>> >>InitialContextFactory,
>> >>> ConnectionFactoryJNDI, and DestinationType. If my MQSeries Queue
>> >is
>> >>the source
>> >>> jms destination bridge and my weblogic queue is the target jms
>destination
>> >>bridge,
>> >>> what values do I set for the listed config-properties? I can't
>seem
>> >>to find any
>> >>> documentation on what these values should be. Am I missing something?
>> >> Do these
>> >>> values even have to be set?
>> >>>
>> >>
>> >>You DON'T have to do anything to the adapter deployment descriptor
>> >>files.
>> >>The values given there for the listed config-properties are just
>default
>> >>values.
>> >>The values configured in JMSBridgeDestination instances are the values
>> >>used to
>> >>override the default values in the dd file.
>> >>
>> >>> 2. When I go to install a Weblogic instance to a different physical
>> >>machine what
>> >>> has to be installed in terms of MQSeries? So I'll have MQSeries
>on
>> >>physical machineA
>> >>> and Weblogic on a different physical machineB. I want machineA
>to
>> >>forward all
>> >>> messages placed on a MQSeries Queue to forward them to machineB
>where
>> >>the weblogic
>> >>> Queue resides. Does machineB also have to contain an MQSeries
>installation?
>> >>> Or can I just grab the necessary libraries and jar files and place
>> >>them on the
>> >>> Weblogic machineB so they can be included?
>> >>>
>> >>
>> >>You don't have to install MQSeries on the machine that the WebLogic
>> >>server is running. You need the necessary libraries and jar files
>> >>though.
>> >>
>> >>> 3. Is it correct that if I distribute Weblogic onto one physical
>server
>> >>and MQSeries
>> >>> onto a different physical server that I cannot use Exactly-once
>quality
>> >>of service?
>> >>>
>> >>
>> >>That is correct and it is a MQSeries transaction limitation.
>> >>
>> >>> Other notes:
>> >>> 1. I have the following patches installed for Weblogic 6.1 sp3:
>> >>> CR081404_610sp3.jar
>> >>> CR081511_61sp3.jar
>> >>>
>> >>
>> >>What version of CR081511_61sp3.jar you have? You need the one dated
>> >on
>> >>8/13/2002.
>> >>
>> >>> 2. Here is the commands I used to create my ConnectionFactory
>and
>> >>Queue within
>> >>> MQSeries:
>> >>> def xaqcf(MQTestConnectionFactory) qmanager(QM_jeff)
>> >>> def q(MQTestQueue) qmanager(QM_jeff) queue(default)
>> >>>
>> >>
>> >>The only possible error I see here is that you create a xaqcf while
>> >your
>> >>bridge
>> >>is configured to have "Atmost-once" QOS. The bridge adapter will
>create
>> >>XASession
>> >>if the connection factory is xa because it knows nothing about QOS
>of
>> >>the bridge.
>> >>As I said, there is a limitation in MQSeries transactions, which
>prevent
>> >>the
>> >>transaction to happen between remote servers. Although the bridge
>does
>> >>not
>> >>start the the transaction in your case, but MQSeries xa connection
>> >>factory may
>> >>throw error when it detects the other side is remote. Having said
>that,
>> >>I am not
>> >>completely sure this is the problem caused the bridge to fail. I
>suggest
>> >>you use
>> >>a non-xa connection factory on the MQSeries side and see if the problem
>> >>goes away.
>> >>
>> >>> Okay...here is my error:
>> >>>
>> >>> <21-Aug-02 11:08:34 ADT AM> <Error> <MessagingBridge> <Error occurred
>> >>in bridge
>> >>> "Messaging Bridge" during transferring messages (java.lang.Exception:
>> >>java.lang.
>> >>> reflect.UndeclaredThrowableException: java.lang.reflect.InvocationTargetException:
>> >>> javax.resource.ResourceException: Error creating consumer or receiving
>> >>message
>> >>> at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1086)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveInternal(JMSBaseConnection.java:774)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receiveCommon(JMSBaseConnection.java:656)
>> >>> at weblogic.jms.adapter.JMSBaseConnection.receive(JMSBaseConnection.java:811)
>> >>> at weblogic.jms.adapter.JMSConnectionHandle.receive(JMSConnectionHandle.java:111)
>> >>> at java.lang.reflect.Method.invoke(Native Method)
>> >>> at weblogic.connector.common.internal.ConnectionWrapper.invoke(ConnectionWrapper.java:60)
>> >>> at $Proxy82.receive(Unknown Source)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1215)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:854)
>> >>> at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
>> >>>
>> >>
>> >>The latest patch CR081511_61sp3.jar (dated on 8/13/2002) will expose
>> >>more error
>> >>information.
>> >>
>> >>> Has anyone see this error before? Here is part of my ra.xml file....I
>> >>just put
>> >>> these entries in to see what happens:
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>ConnectionURL</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property value>file:/C:/Develop/app_servers/WebSphere/MQSeries</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>InitialContextFactory</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>com.sun.jndi.fscontext.RefFSContextFactory</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>ConnectionFactoryJNDI</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>MQTestConnectionFactory</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>DestinationJNDI</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>MQTestQueue</config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>DestinationType</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value></config-property-value>
>> >>> </config-property>
>> >>>
>> >>> <config-property>
>> >>> <config-property-name>AdapterType</config-property-name>
>> >>> <config-property-type>java.lang.String</config-property-type>
>> >>> <config-property-value>XATransaction</config-property-value>
>> >>> </config-property>
>> >>>
>> >>
>> >>As I said earlier, you are not supposed to change the adapter dd
>file.
>> >>
>> >>
>> >>> Here is a snip of my config.xml:
>> >>>
>> >>> <MessagingBridge AsyncEnabled="false" DurabilityEnabled="false"
>> >>> Name="Messaging Bridge" QualityOfService="Atmost-once"
>> >>> SourceDestination="Source JMS Bridge Destination"
>> >>> TargetDestination="Target JMS Bridge Destination" Targets="myserver"/>
>> >>> <JMSBridgeDestination
>> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> >>> ConnectionFactoryJNDIName="MQTestConnectionFactory"
>> >>> ConnectionURL="file:/C:/Develop/app_servers/WebSphere/MQSeries"
>> >>> DestinationJNDIName="MQTestQueue" InitialContextFactory="com.sun.jndi.fscontext.RefFSContextFactory"
>> >>> Name="Source JMS Bridge Destination"/>
>> >>>
>> >>> <JMSBridgeDestination
>> >>> AdapterJNDIName="eis.jms.WLSConnectionFactoryJNDIXA"
>> >>> ConnectionFactoryJNDIName="imagictv.platform.ToolkitRequestCF"
>> >>> ConnectionURL="t3://localhost:7001"
>> >>> DestinationJNDIName="imagictv.platform.ToolkitRequestQueue"
>> >>> InitialContextFactory="weblogic.jndi.WLInitialContextFactory"
>Name="Target
>> >>> JMS Bridge Destination"/>
>> >>>
>> >>
>> >>Your configuration of the bridge and bridge destinations look fine.
>> >
>> >>The last thing is that you have to put MQSeries stuff in your CLASSPATH
>> >>and PATH for starting the WebLogic server that the bridge is running
>> >>on.
>> >>
>> >>You can also turn on debug for more information.
>> >>-Dweblogic.Debug.DebugMessagingBridgeStartup=true
>> >>-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
>> >>
>> >>
>> >>Thanks,
>> >>Dongbo
>> >
-
Query regarding the Node manager configuration(WLS and OAM Managed server)
Query regarding the Node manager configuration(WLS and OAM Managed server):
1) In the nodemanager.properties I have added the ListenAddress:myMachineName and ListenPort: 5556
My setup : One physical Linux machine(myMachineName) has : WLS admin server, managed server(OAM 11G) and nodemanager.No clustered environment.
2) nodemanager.log has the following exception when I start the oam_server1 using EM(Enterprise Manager11g):
Mar 23 2012 1:39:55 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:202)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:125)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
Default port on which node manager listen for requests is localhost:5556.I have changed it to point to my machine. The port should be of WLS admin server or it should be the managed server port?
3) I have started the NodeManager using the startNodeManager.sh script.
4) The admin server port is 7001 and the oam managed server port is 14100.
Any inputs on what might be wrong in the setup will be helpful.Thanks !By using netstat -anp|grep 5556 you can check which process on your machine is using the 5556 port.
-
Embedded WLS and JDev 12.1.2: java.lang.OutOfMemoryError: PermGen space
This problem happens after about 10-15 application restarts during development phase. I have read somewhere that this was a known bug in 11g versions of JDev and its integrated WLS (10.3.5 or 10.3.6?). I have then increased memory parameters in configuration file. The only thing I achieved is that this crash now occurs later then sooner. Still very frustrating. When this happens I have to restart WLS and sometimes kill frozen JDeveloper.
Any other idea/workaround?
<Dec 30, 2013 12:37:04 PM CST> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:ADFOracleReports@ADFOracleReports-FwkExtensions-context-root, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
<Dec 30, 2013 12:37:04 PM CST> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:ADFOracleReports@ADFOracleReports-ViewController-context-root, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
<Dec 30, 2013 12:37:22 PM CST> <Warning> <HTTP> <BEA-101162> <User defined listener org.apache.myfaces.trinidadinternal.webapp.TrinidadListenerImpl failed: java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
Truncated. see log file for complete stacktrace
>
<Dec 30, 2013 12:37:33 PM CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1388428621416" for task "10". Error is: "weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space"
weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
Truncated. see log file for complete stacktrace
Caused By: java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
Truncated. see log file for complete stacktrace
>
<Dec 30, 2013 12:37:33 PM CST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application "ADFOracleReports".>
<Dec 30, 2013 12:37:33 PM CST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application "ADFOracleReports".>
<Dec 30, 2013 12:37:33 PM CST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: java.lang.OutOfMemoryError: PermGen space
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:140)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
Truncated. see log file for complete stacktrace
Caused By: java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:385)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:344)
Truncated. see log file for complete stacktrace
>
[12:37:53 PM] Cancel requested
[Application ADFOracleReports stopped and undeployed from IntegratedWebLogicServer]
<Dec 30, 2013 12:37:53 PM CST> <Error> <Deployer> <BEA-149062> <The task containing ID 10 cannot be canceled, since it has already completed execution.>
<Dec 30, 2013 12:37:53 PM CST> <Warning> <RMI> <BEA-080003> <A RuntimeException was generated by the RMI server: javax.management.remote.rmi.RMIConnectionImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution..
javax.management.RuntimeMBeanException: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution.
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:821)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:792)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:375)
Truncated. see log file for complete stacktrace
Caused By: java.lang.UnsupportedOperationException: [Deployer:149062]The task containing ID 10 cannot be canceled, since it has already completed execution.
at weblogic.management.deploy.DeploymentTaskRuntime.prepareToCancel(DeploymentTaskRuntime.java:881)
at weblogic.management.deploy.DeploymentTaskRuntime.cancel(DeploymentTaskRuntime.java:854)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
Truncated. see log file for complete stacktrace
>You can try to change the garbage collector algorithm. Refere to http://bexhuff.com/2012/09/jdeveloper-memory-and-performance
Timo -
Is there any possibility to access MQSeries queues using 8i AQ packages routines? I have to read some data from MQS and insert it into Oracle on Win2k and wonder if I need any additional MQ interfaces.
Best regards,
Tomek.Hi Brajesh,
Have you ever set up communication between Oracle 9i and MQSeries?
Now I'm trying to read MQ messages using Oracle AQ and Messaging Gateway.
When I'm starting MGW agent i get error message: 'bad native queue' in log file.
Agent is still running and reachable.
Is it possible that i need local MQ queue manager?
Could you please help me with this?
Regards,
Tomek. -
Jdeveloper, WLS and Log4j logging
All,
I want to route all the ADF application log messages to a log file using log4j.
I have created a log4j.properties and put in the ViewController/src folder. The application finds that config file, and produces the desired output - so far, so good.
Now I would like to route all the WLS logging using log4j.
To first try it, I've opened the integrated WLS console, and set, under server/logging, that the log implementation uses log4j instead of jdk. I have also checked the "redirect stdout", "redirect stderr", and "logging bridge" check boxes.
I've also:
- included the wllog4j.jar and log4j-1.2.16.jar in the classpath (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file).
- put a copy of log4j.properties also in the WLS path - which is, in my case: /home/semar/Oracle/Middleware/wlserver_10.3/server/bin
- put the path of the log4j.properties in the WLS CLASSPATH (by editing the /home/semar/Oracle/Middleware/wlserver_10.3/common/bin/commEnv.sh file)
I've then re-started the integrated wls, and now what happens is:
- the log appender for my application is no more found (log4j complains that the appender is not configured)
- no log file is produced/updated
Am I missing something obvious here ? Where should I put the log4j.properties then ? Are other extra tasks I should perform, in order to get all the ADF and WLS logging routed through log4j, and configured using a single log4j property file ?
I'm using WLS 10.3.5.0 and Jdeveloper 11g rel 2 11.1.2.1.0, running on a Linux OpenSuse 11.4
Sergio.Still no joy.
I have put the two JARs + log4j.properties into domain_root/lib folder.
I have also modified the startWeblogic.sh by adding the following:
JAVA_VM="${JAVA_VM} -Dlog4j.configuration=${DOMAIN_HOME}/lib/log4j.properties"
export JAVA_VM
Both the .jar files and the log4j.properties are in the classpath and in the java options of the WLS starting log.
In my application I have:
package logging;
import org.apache.log4j.Logger;
import...
public class loggingBean {
/* Get actual class name to be printed on */
Logger log = Logger.getLogger(loggingBean.class.getName());
public loggingBean () {
System.out.println("hello from loggingBean constructor");
//_logger.info("Creating a new instance");
log.debug("Hello this is a debug message");
log.info("Hello this is an info message");
In the log4j.properties I have:
# Define the root logger with appender file
log = /tmp
log4j.rootLogger = DEBUG, FILE
# Define the file appender
log4j.appender.FILE=org.apache.log4j.FileAppender
log4j.appender.FILE.File=${log}/log.out
# Define the layout for file appender
log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
log4j.appender.FILE.layout.conversionPattern=%m%n
# end of the log4j.properties
And in the standard log file (nohup.out since I start the server with it):
<11.04.2012 14:56 Uhr MESZ> <Notice> <Stdout> <BEA-000000> <hello from loggingBean constructor>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN No appenders could be found for logger (logging.loggingBean).>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN Please initialize the log4j system properly.>
<11.04.2012 14:56 Uhr MESZ> <Notice> <StdErr> <BEA-000000> <log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.>
The file /tmp/log.out does not exist.
Any thought ?
Sergio. -
What is difference between WLS and WLE?
Thanks
hardenWLS is the WebLogic Server which is primarily a J2EE compliant APP
Server. Applications can only be written in Java(or shall I say-- can
primarily be written in Java ). WLS comes originally from WebLogic, the
company that BEA bought.
WLE is a CORBA compliant ORB and the TUXEDO TP engine packaged into
one.It has nothing to do with the original company WebLogic-BEA renamed
it from M3 to WLE. BEA bought ObjectBroker from DEC and TUXEDO I think
from AT&T and merged them together. They have made the recent version
J2EE compliant.
WLE enables cross-platform/cross language development.It supports Java,
C++, Active X clients and server currently. (You can have a Java Client
talking to a C++ Server. BEA advertises WLE for medium to large
enterprise systems and WLS for others especially web based applications
Ram Ramesh
[email protected]
www.cicube.com
A BEA Solutions Partner
hzhu wrote:
What is difference between WLS and WLE?
Thanks
harden -
WLS Cluster with Message Driven Beans and MQSeries on more than one Host
With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
a MDB can be
configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
is started at the same Host that runs the WLS Server too.
And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
Queuemanager.
A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
of this Queue.
If one of the two WLS Servers fails the other WLS Server with the corresponding
MDB should get the Messages of the
MQSeries Queue.
If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
and the following Exception is thrown:
<Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
mdb_deployed
weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
exception is:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
'btsun1a:TEST'
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
the same Exception when the MDB is deployed.
The configuration of JMSadmin on both Hosts is the following:
dis qcf(myQCF2)
HOSTNAME(btsun1a)
CCSID(819)
TRANSPORT(CLIENT)
PORT(1414)
TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
QMANAGER(TEST)
CHANNEL(JAVA.CHANNEL)
VERSION(1)
dis q(myQueue)
CCSID(819)
PERSISTENCE(APP)
TARGCLIENT(JMS)
QUEUE(MYQUEUE)
EXPIRY(APP)
QMANAGER(TEST)
ENCODING(NATIVE)
VERSION(1)
PRIORITY(APP)
I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
and a QueueManager on each WLS Server.
Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
With the Examples of http://developer.bea.com/jmsproviders.jsp and http://developer.bea.com/jmsmdb.jsp
a MDB can be
configured to work with MQSeries with one WLS Server. This works only, if a Queuemanager
is started at the same Host that runs the WLS Server too.
And the QueueConnectionFactory (QCF) is configured to TRANSPORT(BIND).
In my configuration should be two WLS Servers and one JMS Queue (MQS) with the
Queuemanager.
A Message Driven Bean is deployed on both WLS Servers wich should get the Messages
of this Queue.
If one of the two WLS Servers fails the other WLS Server with the corresponding
MDB should get the Messages of the
MQSeries Queue.
If the QCF is configured to TRANSPORT(Client) the Message Driven Bean can't start
and the following Exception is thrown:
<Jul 18, 2001 3:52:49 PM CEST> <Error> <J2EE> <Error deploying EJB Component :
mdb_deployed
weblogic.ejb20.EJBDeploymentException: Error deploying Message-Driven EJB:; nested
exception is:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for
'btsun1a:TEST'
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'btsun1a:TEST'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:434)
I'm wondering, because their is a MQQueueManager on btsun1a; all Servers throws
the same Exception when the MDB is deployed.
The configuration of JMSadmin on both Hosts is the following:
dis qcf(myQCF2)
HOSTNAME(btsun1a)
CCSID(819)
TRANSPORT(CLIENT)
PORT(1414)
TEMPMODEL(SYSTEM.DEFAULT.MODEL.QUEUE)
QMANAGER(TEST)
CHANNEL(JAVA.CHANNEL)
VERSION(1)
dis q(myQueue)
CCSID(819)
PERSISTENCE(APP)
TARGCLIENT(JMS)
QUEUE(MYQUEUE)
EXPIRY(APP)
QMANAGER(TEST)
ENCODING(NATIVE)
VERSION(1)
PRIORITY(APP)
I think only TRANSPORT(CLIENT) can be used when i don't wan't to install a Queue
and a QueueManager on each WLS Server.
Does anybody know a problem of WLS 6.0 SP2 to cope with TRANSPORT(CLIENT)?
-
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.
-
JMS bridge and MQSeries. looking for statistics
Hi !
I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
on each instance of the server).
I'm looking for statistics about how often a message can be treated 2 (or more)
times.
Thanks a lot for any help !
Florent
Hi Florent,
Since these are MQ messages, it might be possible to find
such statistics in MQ. Also, I think that MQ stores a
redelivery count in their messages - so you can likely
instrument your application code to get at the count.
Note that 7.0 actually does support exactly once with WL MDBs driven
by MQ. If you use transactions you can infer some stats on redeliveries
by checking the relevant transaction statistics for rollback counts.
I'm attaching some notes on JMS integration for your
convenience.
Tom
florent wrote:
> Hi !
>
> I have to use Weblogic 7 SP4 in cluster with a distant MQSeries queue manager.
> I know I can't have a "exactly once" quality of service. I use a MDB (deplyed
> on each instance of the server).
>
> I'm looking for statistics about how often a message can be treated 2 (or more)
> times.
>
> Thanks a lot for any help !
>
> Florent
JMS Integration of Foreign Vendors with BEA WebLogic Server
The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
JMS Integration Overview
- For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
- For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
- In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
- WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
- WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
- WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
- WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Integration with 8.1 Details
A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
This document refers to helpful new 8.1 features, which simplify integration. These include:
http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
And are also summarized here (under interoperability):
http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
Also read the extensive MDB documentation, which extensively covers integrating foreign vendors:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
The 8.1 features are likely sufficient for most 8.1 integration needs, and you may not need to refer "Using Foreign JMS Providers With WLS" white-paper mentioned below.
Integration with 6.1 and 7.0 Details
Read the "Using Foreign JMS Providers With WLS" white-paper:
http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
Note that this white-paper does not take into account 8.1 features.
For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
http://edocs.bea.com/wls/docs81/ejb/message_beans.html
Non-Java Integration Options
- WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
http://dev2dev.bea.com/technologies/jms/index.jsp
- WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs61/jcom.html
http://e-docs.bea.com/wls/docs70/jcom/
http://e-docs.bea.com/wls/docs81/jcom/
- Similar to JCOM, but more advanced, WL supports IIOP standard based access on multiple platforms. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
http://e-docs.bea.com/wls/docs81/rmi_iiop/
http://e-docs.bea.com/wls/docs70/rmi_iiop/
http://e-docs.bea.com/wls/docs61/rmi_iiop/
Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
- If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
- Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from Windows. These in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
- Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
- Finally, there are .NET/C/C++ integration libraries that not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
Notes on MQ Remote Capable XA Clients
Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
- Required on WLS where MQ objects are bound into JNDI:
com.ibm.mq.jar, com.ibm.mqjms.jar
- Required only if MQ objects are bound into JNDI on a different server:
com.ibm.mq.jar
If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
Notes on Oracle AQ Integration
If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
Caveats:
The solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
The solution doesn't seem to support transactions, it may be possible to extend it to do so.
MDB Thread Pool Notes
WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
(Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
MDB Concurrency Notes
Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
Design Guide-Lines and Performance Tuning Notes
The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp
-
Version compatibility for installing WLS and ADR for ADF 11.1.2.0
Hi,
Can anyone pls let me know what versions of Weblogic server, Application Development Runtime (ADR) is required to install Oracle JDeveloper 11.1.2.0
B'coz currently I am trying to install Weblogic server, ADR and ADF separately and try to deploy and publish an application in ADF 11.1.2.0 verison.
I am trying this for the past 4 days, but still can't deploy an application successfully in ADF 11.1.2.0 version. Pls let me know the version compatibility.
Thanks,
AparnaHi John,
Even I saw the link that u had mentioned. From where can I install these ?
I had downloaded WLS 10.3.5 and ADR 11.1.1.5 separately. But from where do I install the patch ?? I didn't find a proper source to download.
Pls help.
Thanks,
Aparna -
Deployment of same EAR fails on one WLS and succeeds on another!
Hello,
We are migrating from 10g to 11G for our SOA/ADF application.
Step1: We installed Jdev 11G and also weblogic server that is free on OTN, on our machines. We wanted to first test the deployment on this server on our local machines before we did the deployment on our company's WL server. We were able to successfully create an EAR file (after many road blocks) and deploy the application to the free weblogic server (please note I am NOT saying the embedded WLS or the Integrated WLS).
Step2: We used the EAR file created in the step above and used the same Jdev 11g to do the deployment but instead of connecting to the WLS on our machines, we created a server connection pointing to the company's server. We were confident that this will go smoothly but noooooooo!!!!!! We are getting the following error while deployment. The deployment is failing.
Caused By: java.lang.ClassNotFoundException: oracle.adfinternal.view.faces.bi.renderkit.graph.GraphServlet
Why should this happen? We are using the same EAR and the same JDev to do the deployment. ADF domain has been extended on both the servers. After the deployment failed on our company's WLS, we used the same ear and using JDev to do the deployment again but the one on our machine. It went smoothly. What is going on here?
Any help is appreciated.Can being low on system tablespace effect creating indexes in anyway? Yes it can; even if your index (or table, or package) is created in a non-system tablespace, the description of the index is stored in Oracle's dictionary tables, owned by SYS:
OBJ$ (the list of objects)
IND$ (the list of indexes) - or TAB$, etc
ICOL$ (index columns) - or COL$ for tables...
SEG$ (the list of segments)
UET$ (the list of used extents)
etc. These are the tables on which the dictionary views (eg USER_INDEXES) that we all know and love are based.
These tables grow over time; eventually they too need to be extended. And if there isn't enough free space in the SYSTEM tablespace, your DDL operation fails.
With packages/procedures/functions you require space in a plethora of tables that store the code and the compiled forms of your PL/SQL.
HTH
Regards Nigel -
Configure Active directiory and WLS and Human Task form
Hi Guys,
We are using SOA Suite 11.1.6 for the current project and like to configure Active Directory as the identity provider. I know this is not a new question and did several searches in the forum and online, but not all our questions are answered. At this moment, in the WL security realm, we can see users and groups from AD. But there are still outstanding issues:
1. Authentication with AD users
We still cannot configure AD user to login WLS.
2. Email users
AD user is not showing up in the email lookup in jdeveloper. Currently, there are only two users returned: weblogic and oraclesystemuser. I believe that they are the default users.
3. WorkList Application (Human Task)
This is similar to #1, but not all. We like to configure AD users to login to the Worklist application.
Any suggestion are appreciated.
Thanks
Steven
Edited by: sw12345 on Apr 27, 2012 11:49 AMHi Steven
1. What you want is totally possible BUT you can have your Users only in one Security Provider. To access bpm/workspace, all the users will be referred in the first top most security provider. So make sure, your AD Authenticator is in the Top Most and also all these providers should be set to SUFFICIENT / OPTIONAL.
Below these 2 posts should give more details:
Weblogic administrator account is inactive after enabling DB Authenticator
Re: BPM 11g workspace not show user from OVD - top most authentication provider
Thanks
Ravi Jegga -
How to install BPEL on WLS and JDEV 11g/WLS
Can somebody pls point me to a paper "How to install BPEL (Designer, Server, etc.) on WLS" ?!
I downloaded 80 MB BPEL (Orabpel_10133_WebLogic.zip), unzipped it, but it does not container a "read.me"...
I like to install the BPEL part for the JDEV - is that the right one ?
Or do I need to install the whole SOA Suite (incl. BPEL Server) (570 MB) - but this seem to be based on OC4J?
The core question: which (download) components do I need to install BPEL on WLS to make it run and usable ?
TIA
BernhardHere is the readme you may be after
http://download.oracle.com/docs/cd/E10291_01/doc.1013/e12534/toc.htm
This is an old release. There is now 10.1.3.4, but I don't believe the stand alone BPEL is supported. You need to install the full SOA Suite. The doc for this is
http://download.oracle.com/docs/cd/E12524_01/core.1013/e13058/toc.htm
You need to install the Oracle version first then port it. This is all changing in 11g, hopefully due soon.
I recommend the latter as it provides more functionality around patching.
Also SOA Suite or BPEL is on certified against 9.2 not 10.3 so you cannot use it against JDev 11g. Your JDev version must be in sync with your SOA Suite version.
cheers
James -
Distributed ttransaction with Oracle and MQseries
Hi,
I am leveraging a Tuxedo architecture on HP-UX IA64 that utilizes two XA resource managers, MQSeries and Oracle. The use of the resource managers is based on a coordinated 2 phase commit method (TPBEGIN - TPCOMMIT).
The application running on tuxedo has beem migrated from Mainframe environment (z/OS + CICS + DB2 + MQ)
The systems functionally works, , but we continue to experience major performance issues, caused by the fact that in the original application migrated from the CICS environment executes an high number of syncpoint(s).
What is observable is that increasing the number of parallel processes (tuxedo servers), the cost of the single syncpoint is much greater than the cost of an atomic elaboration (atomicity) of that same transaction.
Ex., if the cost of an elaborated transaction is 2 ms, the cost of syncpoint is 30 ms.
Because we were not able to solve the proble just changing configuration parameters, in this specific case, we have simply reduced the number of syncpoints executed by the application so to lower the cost of syncpoint to the same rate as a transaction.
Is it possible to have a reference or information on similar use cases of mission-critical Tuxedo/UNIX environments with high volumes? (Millions of transactions)?
Is it possible to understand if there are parameters that can be set/established at a configuration level in Tuxedo (ubbconfig or others) to deal with the above-stated issue?
Thanks in advance for any helpful feedback
Regards
RobertoThere are a couple of major and minor mistakes in your listener.ora like specifying 2 times the listener name LISTENER. Using 2 different hostnames on the same machine or specifying the ENVS=LD_LIBRARY_PATH for a Windows Gateway as well as the executable you defined.
I tried to summarize it in your original thread bust recommend you to log a service request.
Maybe you are looking for
-
Java.rmi.RemoteException: SOAP Fault:javax.xml.rpc.soap.SOAPFaultException
Hi, I created a webservice using weblogic8.1 sp3 workshop. On my desktop, I tested the webservice with a java client and it worked fine. When I deployed webservice application on UNIX production server, it deployed successfully and it displayed WSDL
-
Biztalk send to WCF-service that is behind a NLB
A while ago a WCF-service that biztalk 2006 r2 sends to was put behind a NLB. I find that since than I sometimes get timeouts although biztalk was able to reach the service. Also in my new test-environment using Bts2013 r2 I find that I sometimes get
-
Separate PurRequisitions as result of BOM explosion
Hello, is there a possibility with customizing or with an exit/enhancement influence that separate Purchase requisitions are created in the following scenario: Sales order BOM is used, same material codes appears twice in this BOM. The material code
-
Building data model using business modeler in demantra
Hello. During this week I've been trying to build a data model using the business modeler but i keep getting an error during the process. My main problem is that I don't really know if i am making the mistake or it is a configuration problem with my
-
Dear all I want to configure SRM to send emails to the approvers and have a link to logon in SRM to approve in SRM (online approval). That is working perfectly if the user connects to SRM. But what I need to put as ITS_DEST attribute or other info t