JMS server in a cluster
I have a JMS server deployed to one of the instances in my 2 instance cluster.
I have an MDB attached to a queue on the JMS server (NOT a distributed destination).
If I run both weblogic instances on one physical server, both instances can see
and use the JMS server. My MDB correctly finds its destination on both instances.
If I put the instances on separates physical servers, then the server that doesn't
have the JMS server deployed cannot find the JMS destination for its MDB.
Why should the behavior be different if I run the cluster all on one machine or
spread it between 2 machines?
I've attached my config.xml for reference. Thanks for any help,
Colin
I have seen other users as well complaining about the same issue "[Security:090398]Invalid Subject" frequently. You may check with Oracle Support for possible solution for your system version.
Regards,
Anuj
Similar Messages
-
JMS Server deployed to cluster of servers
Hey guys,
I was trying to deploy a JMS server to a cluster of servers and in the target section there wasn't an option for the cluster. They had an option for each individual server and another migratable version of the server. If I target one of the migratable servers in the cluster will it apply to all of the servers?
I read the following passage in the weblogic documents:
Obtain a Clustered JMS Licence
In order to implement JMS clustering, you must have a valid clustered JMS license, which allows a connection factory and a destination to be on different WebLogic Server instances. A clustered JMS license is also required to use the Foreign JMS Providers feature, as described in "Simple Access to Remote or Foreign JMS Providers" in the Administration Console Online Help. If you do not have a valid clustered JMS license, contact your BEA sales representative.
If i'm just building a model does this apply to me?
Thankscontinued reading to clarify. Problem solved, thanks for looking
-
JMS Server on a cluster stores all msgs posted to Distributed Queue on 1 server failure
Hi
I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running its own
JMS server.
Product version in use is Weblogic SP2.
Configured a Distributed Queue and deployed it on both the JMS servers.
Set the load-balancing to round-Robin and Server-Affinity to False on the connection
factory.
The producer is an external client which posts 100 messages to the Distributed
queue.
Consumers are MDBs pinned to the respective physical queues on the respective
JMS servers.
Each server has its own store.
Once 100 messages are posted to the Distributed Queue. The messages are distributed
to
the 2 Physical Destinations equally i.e 50-50 each.
While the MDBs are processing the msgs, server srvr1 is brought down at a point
when it has consumed only 10 of its 50 msgs.
When the srvr1 is brought up again, i am finding that the store for that JMS server
contains the 40 unprocessed msgs in its physical queue + the msgs on the other
queue that were unprocessed at the time this server crashed.
When srvr1 went down, srvr2 was running and it went on to process all its 50 msgs
completly. Why would those processed msgs show up again when srvr1 is brought
up ?
Please provide some input !!
Ravi.
The log message is from the distributed destination
"forwarders". In distributed queues, these forwarders
automatically move messages from queues without
consumers to queues that have them (queue
forwarders are disabled by default). In distributed topics,
the forwarders serve
to replicate a published message from the local
topic member to each of the remote topic members.
"Raviprasad Athivilli" <[email protected]> wrote:
>
>Tom
>
>I think you are right. When the server1 is brought up again, its picking
>up all
>the messages
>that were written to the store.
>
>But as it starts processing them, i get this exception on the server2
>that has
>been running from the beginning.
>
><Oct 10, 2003 6:20:19 PM EDT> <Error> <JMS> <040366> <JMS Distributed
>Destination
>member "MyQueue@JMSServer-02" in "MyQueue"
>unable to accept connection from remote member "MyQueue@JMSServer-01"
>due to exception
>weblogic.jms.common.JMSException: can't find
>queue target jndi table for MyQueue@JMSServer-01 != MyQueue
>weblogic.jms.common.JMSException: can't find queue target jndi table
>for MyQueue@JMSServer-01
>!= MyQueue
> at weblogic.jms.backend.BEDestination.setupSystemSubscription(BEDestination.java:3466)
> at weblogic.jms.backend.BEManager.sessionAndTopicSubscriberCreate(BEManager.java:234)
> at weblogic.jms.backend.BEManager.invoke(BEManager.java:384)
> at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
> at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
> at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsyncFuture(DispatcherImpl.java:396)
> at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown
>Source)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
> at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
> at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
> at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
> at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
>What does this mean ?
>
>Ravi.
>Tom Barnes <[email protected]> wrote:
>>Seems more than odd. Are you sure that q1 got unprocessed
>>messages from q2? How did you confirm?
>>
>>Perhaps q1 got messages its MDB already processed back again -
>>an indication that the MDB is throwing Runtime exceptions
>>or Errors, and the container is rolling back transactions.
>>
>>Raviprasad Athivilli wrote:
>>> Hi
>>>
>>> I have a Cluster setup with 2 managed servers srvr1 & srvr2 each running
>>its own
>>> JMS server.
>>> Product version in use is Weblogic SP2.
>>> Configured a Distributed Queue and deployed it on both the JMS servers.
>>> Set the load-balancing to round-Robin and Server-Affinity to False
>>on the connection
>>> factory.
>>>
>>> The producer is an external client which posts 100 messages to the
>>Distributed
>>> queue.
>>> Consumers are MDBs pinned to the respective physical queues on the
>>respective
>>> JMS servers.
>>> Each server has its own store.
>>>
>>> Once 100 messages are posted to the Distributed Queue. The messages
>>are distributed
>>> to
>>> the 2 Physical Destinations equally i.e 50-50 each.
>>>
>>> While the MDBs are processing the msgs, server srvr1 is brought down
>>at a point
>>> when it has consumed only 10 of its 50 msgs.
>>>
>>> When the srvr1 is brought up again, i am finding that the store for
>>that JMS server
>>> contains the 40 unprocessed msgs in its physical queue + the msgs
>on
>>the other
>>> queue that were unprocessed at the time this server crashed.
>>>
>>> When srvr1 went down, srvr2 was running and it went on to process
>all
>>its 50 msgs
>>> completly. Why would those processed msgs show up again when srvr1
>>is brought
>>> up ?
>>>
>>> Please provide some input !!
>>>
>>> Ravi.
>>
>
-
Best way to determine if JMS server is alive in a cluster
Can anyone give me an idea on the best way to find out if a JMS server
in a cluster
has failed so I can signal migration to another server in the cluster.
Thanks Larry
PS weblogic 7.0 sp1
Hallo Larry,
you can go via JMX and retrieve the according RuntimeMBeans in order to
check the health state of the
JMSServer resp. the server hosting the JMSServer. If they are not available
or failed you can trigger the
migration. At least that's the way I'm doing it...
try
JMSServerMBean jmsServer = null;
ServerMBean candidateServer = null;
MigratableTargetMBean migratableTarget = null;
* Retrieve all JMSServer defined for the current domain
Set jmsServerSet = home.getMBeansByType("JMSServer", domainName);
Object[] jmsServers = jmsServerSet.toArray();
* Just the first one is picked assuming there is only one defined
* within the active FHO domain
if(jmsServers != null && jmsServers.length > 0)
jmsServer = (JMSServerMBean) jmsServers[0];
if(s_logger.isDebugEnabled())
s_logger.debug("JMSServer: " + jmsServer.getName());
* A JMSServer can only be associated with a single target,
* thus pick again the first from the list.
TargetMBean[] targets = jmsServer.getTargets();
if(targets != null && targets.length > 0)
boolean hostingServerRunning = false;
boolean candidateServerRunning = false;
* Check whether the JMSServer is really associated with
* a migratable target. Otherwise the migration must be canceled
* since it cannot be performed!
if(targets[0] instanceof MigratableTargetMBean)
migratableTarget = (MigratableTargetMBean) targets[0];
* Retrieve all available candidates and select a running instance
* if any. First check for constrained candidate servers, than for
* all candidate servers
ServerMBean[] candidates =
migratableTarget.getConstrainedCandidateServers();
if(candidates == null || candidates.length == 0)
candidates = migratableTarget.getAllCandidateServers();
if(candidates != null && candidates.length > 0)
ServerMBean hostingServer = migratableTarget.getHostingServer();
boolean gotHostingServer = false;
boolean gotCandidateServer = false;
boolean runningInstance = false;
* Loop over all candidates as long as hosting server and candidate
* server are visited and there running state has been determined
for(int i=0; i< candidates.length; i++)
ServerRuntimeMBean serverRuntime = null;
* Retrieve the current state from the according runtime MBean
* if available
try
serverRuntime = (ServerRuntimeMBean) home.getMBean(new
WebLogicObjectName(candidates.getName(), "ServerRuntime", domainName,
candidates[i].getName()));
runningInstance =
serverRuntime.getState().equalsIgnoreCase(ServerRuntimeMBean.RUNNING);
catch(InstanceNotFoundException inf)
* When a server instance is not available, an InstanceNotFoundException will
be raised
* by WLS, which can be ignored
if(hostingServer != null && hostingServer.equals(candidates[i]))
hostingServerRunning = runningInstance;
gotHostingServer = true;
else
* A running candidate server will be prefered, thus only if no running
* instance can be detected, another instance is selected
if(!gotCandidateServer)
candidateServerRunning = runningInstance;
candidateServer = candidates[i];
gotCandidateServer = runningInstance;
if(gotCandidateServer && gotHostingServer)
break;
if(s_logger.isDebugEnabled())
s_logger.debug("Migratable Target: " + migratableTarget.getName());
s_logger.debug("Candidate Server: " + candidateServer.getName());
else
throw new Exception("JMSServer not deployed on a migratable target!");
* Retrieve the migration service coordinator for the active domain assuming
* there exists only one and invoke the migration later on
MigratableServiceCoordinatorRuntimeMBean coordinator = null;
Set coordinatorSet =
home.getMBeansByType("MigratableServiceCoordinatorRuntime", domainName);
Object[] coordinators = coordinatorSet.toArray();
if(coordinators.length > 0)
coordinator = (MigratableServiceCoordinatorRuntimeMBean) coordinators[0];
if(enforceMigrationOnInstancesDown)
coordinator.migrate(migratableTarget, candidateServer, hostingServerRunning,
candidateServerRunning);
else
coordinator.migrate(migratableTarget, candidateServer);
s_logger.info("Migration of JMSServer from node "
+ migratableTarget.getName()
+ " to node "
+ candidateServer.getName()
+ " has been started");
else
throw new Exception("MigrationServiceCoordinator cannot be retrieved");
catch(Exception e)
s_logger.error("Could not migrate JMSServer", e);
Regards,
CK
"Larry Presswood" <[email protected]> schrieb im Newsbeitrag
news:[email protected]...
> Can anyone give me an idea on the best way to find out if a JMS server
> in a cluster
> has failed so I can signal migration to another server in the cluster.
>
> Thanks Larry
>
> PS weblogic 7.0 sp1
> -
JMS Server targeted to Server cluster
Hi , Can JMS Server be targeted to Server Cluster? Are there any
architectural best practices for this?Thanks Tom.
<Tom Barnes> wrote in message news:[email protected]...
There's no underlying machinery (code) that supports targeting a JMS server
to a cluster.
The targeting problem can actually get fairly involved - for a variety of
reasons, I tend to recommend the following cookie cutter approach.
This is a cut-and-paste from my notes:
(1) Create a custom WL store on each server, and target it to a migratable
target (most of the time you can use the default migratable target that each
server provides).
(2) Target the JMS servers to a migratable target each, the same MT as the
store (don't worry, the JMS server won't wander to a different server
unless you configure the MT to allow this!)
(3) Target jms configuration system modules to the cluster (that's it! - not
to anything else)
(4) Create one subdeployment per module (and only one), populate the
subdeployment only with JMS servers from step (2) above.
(5) When targeting destinations always use advanced targeting to target
destinations to the subdeployment from above - not the 'default target'.
If you have both non-distributed and distributed destinations, use two
different JMS modules. (The idea is to keep things simple to understand -
each module should yield the same targeting solution for all of its
component resources. Default targetting can be problematic - it is far too
easy for destination members to end up on JMS servers that you don't want
them on.).
(6) When targeting a CF you have two options (A) use advanced targeting to
target it to the subdeployment (for access by applications that are remote
to the cluster) or (B) don't target it all (this will cause it to use the
module target, which if you recall, we just set to the cluster, (for access
by applications that run on a server within the cluster). The choice
actually depends on how you plan to use the CF - use (B) for apps running on
servers within the cluster, and (A) for apps running remote to the cluster.
See the otherwise-largely-outdated JMS Performance Guide for the reasoning.
It may be that you don't have to use migratable targets, as you may not have
a use for "migration" at the moment - but it'll help in the future if you
ever plan to use the migration features.
Tom -
I am trying to deploy a MDBean in my cluster ( two servers). The MDBean requires
the destinestion has to each cluster server. It means that I have to deploy my
JMS server over the cluster. This will result multiple destinations (queue or
topic) are created.
Is there a way to run one JMS server with a clustered MDBean?
Thanks,
Taohe
Check out my posting from 4-3 in this thread.
http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=5&jump=true
I think I may have answered your question before you asked it.
In that example I use the picture control to manipulate a bunch of rectangular images of booleans.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction -
JNDI Names of JMS server's queue not replicating to cluster
Am having some trouble configuring a JMS Server and Queues in a clustered development
environment. It is a simple cluster of 2 servers (Server1 and Server2) both on
a single machine.
The "JobServer" JMS Server is targeted to "Server1 (migratable)". All the JNDI
names for the Queues appear in the JNDI tree of Server1, but not in Server2.
When the sending of a message is attempted on Server2, the following occurs:
javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
This may be a problem with the cluster configuration, but I haven't been able
to see anything wrong with it.
Any and all help will be appreciated.
There is the Config.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
<Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
ListenPort="7001" Name="myserver" NativeIOEnabled="true"
ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
<SSL Enabled="false" HostnameVerificationIgnored="false"
IdentityAndTrustLocations="KeyStores" ListenPort="7002" Name="myserver"/>
<Log Name="myserver" NumberOfFilesLimited="true"/>
</Server>
<Security Name="mydomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm" RealmSetup="true">
<weblogic.security.providers.authentication.DefaultAuthenticator
Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authentication.DefaultIdentityAsserter
ActiveTypes="AuthenticatedUser"
Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultRoleMapper
Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAuthorizer
Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
<weblogic.security.providers.authorization.DefaultAdjudicator
Name="Security:Name=myrealmDefaultAdjudicator"
Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
<weblogic.security.providers.credentials.DefaultCredentialMapper
Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
<weblogic.management.security.authentication.UserLockoutManager
Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
<weblogic.management.security.Realm
Adjudicator="Security:Name=myrealmDefaultAdjudicator"
Auditors="Security:Name=myrealmSTARSIIAuditor"
AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
DefaultRealm="true" DisplayName="myrealm"
FullyDelegateAuthorization="true"
Name="Security:Name=myrealm"
RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
<gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
ControlFlag="SUFFICIENT"
Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
<gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
ExemptUri="/common/,/images/,/warning.do,/login.do"
Name="Security:Name=myrealmSTARSIIAuthorizer"
PolicyDeploymentEnabled="false"
Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
<gov.fns.starsii.common.security.audit.STARSIIAuditor
Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
</Security>
<EmbeddedLDAP
Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI=" Name="mydomain"/>
<SecurityConfiguration
Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
Name="mydomain" RealmBootStrapVersion="1"/>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<FileRealm Name="wl_default_file_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="STARSII BRSB Pool"
Password="{3DES}9pslRpr051lR9/NEKdanag=="
Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
<JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
PoolName="STARSII Store Pool" Targets="MyCluster"/>
<JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
PoolName="STARSII Store Pool" Targets="MyCluster"/>
<!--StartupClass
ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
DeploymentOrder="250" Name="STARS II Properties Startup Class" Targets="myserver,MyCluster"/>
<StartupClass
ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
DeploymentOrder="500"
Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
<StartupClass
ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
DeploymentOrder="750"
Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
-->
<MailSession JNDIName="mail/STARSIIMailSession"
Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj" Targets="myserver"/>
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="STARSII Store Pool"
Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
Targets="MyCluster"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="AffTest" Password=""
Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
<JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
PoolName="AffTest" Targets=""/>
<JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
Name="Spy STARSII BRSB Pool"
Password="{3DES}9pslRpr051lR9/NEKdanag=="
Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="STARSII Store Pool 2"
Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
<JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
PoolName="STARSII Store Pool" Targets=""/>
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="STARSII Stars Pool"
Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
Targets="MyCluster"
TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
<Machine Name="MachineA">
<NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
</Machine>
<Server Cluster="MyCluster" ExpectedToRun="false"
ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
<ServerDebug Name="Server1"/>
<SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
<KernelDebug Name="Server1"/>
<Log Name="Server1"/>
<ServerStart Name="Server1"
OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
<WebServer Name="Server1"/>
<COM Name="Server1"/>
<IIOP Name="Server1"/>
<JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
<JTARecoveryService Name="Server1"/>
</Server>
<Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
MulticastAddress="226.0.0.244" Name="MyCluster"/>
<Server Cluster="MyCluster" ExpectedToRun="false"
ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
ListenPort="7002" Machine="MachineB" Name="Server2"
ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
<ServerDebug Name="Server2"/>
<SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
<KernelDebug Name="Server2"/>
<Log Name="Server2"/>
<ServerStart Name="Server2"
Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
<WebServer Name="Server2"/>
<COM Name="Server2"/>
<IIOP Name="Server2"/>
<JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
<JTARecoveryService Name="Server2"/>
</Server>
<MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
Notes="This is a system generated default migratable target for a server.
Do not delete manually." UserPreferredServer="Server1"/>
<MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
Notes="This is a system generated default migratable target for a server.
Do not delete manually." UserPreferredServer="Server2"/>
<Application Deployed="true" Name="STARSII"
Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
<EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
<EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
<EJBComponent Name="../commonSession" Targets="MyCluster" URI="../commonSession"/>
<EJBComponent Name="../complianceMessage" Targets="MyCluster" URI="../complianceMessage"/>
<EJBComponent Name="../complianceSession" Targets="MyCluster" URI="../complianceSession"/>
<EJBComponent Name="../starsiiEntity" Targets="MyCluster" URI="../starsiiEntity"/>
<EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
<WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
<WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
<WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
<WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
</Application>
<Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
StagingMode="nostage" TwoPhase="true">
<WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
</Application>
<Application Name="activeportal"
Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
StagingMode="nostage" TwoPhase="true">
<WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
</Application>
<JTA Name="mydomain" TimeoutSeconds="300"/>
<JMSServer Name="JobServer" Targets="Server1 (migratable)">
<JMSQueue CreationTime="1072820642598"
JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
<JMSQueue CreationTime="1072820669345"
JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
<JMSQueue CreationTime="1088000795852"
JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
<JMSQueue CreationTime="1072820687125"
JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
<JMSQueue CreationTime="1072820687125"
JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
<JMSQueue CreationTime="1072820687225"
JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
<JMSQueue CreationTime="1072820687325"
JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
<JMSQueue CreationTime="1072820687425"
JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
<JMSQueue CreationTime="1072820687525"
JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
<JMSQueue CreationTime="1072820687625"
JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
<JMSQueue CreationTime="1072820687725"
JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
<JMSQueue CreationTime="1072820687825"
JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
<JMSQueue CreationTime="1072820687925"
JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
<JMSQueue CreationTime="1072820688025"
JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
<JMSQueue CreationTime="1072820688125"
JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
<JMSQueue CreationTime="1072820688225"
JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
<JMSQueue CreationTime="1072820688325"
JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
</JMSServer>
<Machine Name="MachineB">
<NodeManager DebugEnabled="true" Name="MachineB"/>
</Machine>
</Domain>
Internally, many BEA developers and testers use various versions
of XP with clustering on a daily basis. I don't know what
is unique about your machine. I suggest raising the issue
with customer support and/or posting to the clustering newsgroup...
Andy Frank wrote:
> It would seems that my OS and the MultiCast config are to blame. The MultiCast
> test utility worked fine the Win2K machines I tried. Think I will take another
> look at MS KB article 827536 and/or think about another dev OS.
>
> "Andy Frank" <[email protected]> wrote:
>
>>Tom,
>>Thanks for this info.
>>
>>My servers don't look like they are running in different subnets (had
>>a friend
>>look this over and he concurs).
>>
>>My network admin says he hasn't blocked multicast traffic.
>>
>>I think the MultiCast test utility is telling me that I have some kind
>>of multicast
>>config problem. Output follows:
>>
>>------ Begin MultiCast test utility output: ------
>>C:\bea\weblogic81\server\bin>java utils.MulticastTest -N server200 -A
>>237.155.15
>>5.1 -t 15
>>***** WARNING ***** WARNING ***** WARNING *****
>>Do NOT use the same multicast address as a running WLS cluster.
>>
>>
>>Starting test. Hit any key to abort
>>
>>
>>Using multicast address 237.155.155.1:7001
>>Will send messages under the name server200 every 2 seconds
>>Will print warning every 15 seconds if no messages are received
>>
>> I (server200) sent message num 1
>> I (server200) sent message num 2
>> I (server200) sent message num 3
>> I (server200) sent message num 4
>> I (server200) sent message num 5
>> I (server200) sent message num 6
>> I (server200) sent message num 7
>>java.net.SocketTimeoutException: Receive timed out
>> at java.net.PlainDatagramSocketImpl.receive(Native Method)
>> at java.net.DatagramSocket.receive(DatagramSocket.java:680)
>> at utils.MulticastTest$Receiver.run(MulticastTest.java:304)
>> I (server200) sent message num 8
>> I (server200) sent message num 9
>> I (server200) sent message num 10
>> I (server200) sent message num 11
>> I (server200) sent message num 12
>>------ End MultiCast test utility output: ------
>>
>>No "Received message X from server200" messages. I think I need to look
>>into
>>configuring multicast communications on my OK (Windows XP Pro, ver 2002
>>SP1).
>>I did see MS KB article 827536 about "An IP multicast may not be sent
>>correctly
>
>>from Windows XP or from Windows Server 2003" (I do have 2 network adapters),
>
>>but
>>the resolution scared me some.
>>
>>Think I will try some things out on another OS and see what that gets
>>me.
>>
>>Any other thoughts on this will be appreciated.
>>
>>
>>Tom Barnes wrote:
>>
>>>I too suspect something is going wrong with clustering, I wonder
>>>if the servers are running in different subnets (even though
>>>they are on the same box) and/or your network admin has
>>>blocked multicast traffic.
>>>
>>>The MultiCast test utility should help narrow things down:
>>>
>>>http://e-docs.bea.com/wls/docs81/admin_ref/utils.html#1199798
>>>
>>>Tom
>>>
>>>Andy Frank wrote:
>>>
>>>
>>>>Am having some trouble configuring a JMS Server and Queues in a clustered
>>>
>>>development
>>>
>>>>environment. It is a simple cluster of 2 servers (Server1 and Server2)
>>>
>>>both on
>>>
>>>>a single machine.
>>>>
>>>>The "JobServer" JMS Server is targeted to "Server1 (migratable)".
>>
>>>All the JNDI
>>>
>>>>names for the Queues appear in the JNDI tree of Server1, but not in
>>>
>>>Server2.
>>>
>>>>When the sending of a message is attempted on Server2, the following
>>>
>>>occurs:
>>>
>>>>javax.naming.NameNotFoundException: While trying to lookup 'jms.STARSIIPostQueue'
>>>>didn't find subcontext 'jms' Resolved ; remaining name 'jms/STARSIIPostQueue'
>>>> at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:858)
>>>>
>>>>This may be a problem with the cluster configuration, but I haven't
>>>
>>>been able
>>>
>>>>to see anything wrong with it.
>>>>
>>>>Any and all help will be appreciated.
>>>>
>>>>There is the Config.xml file:
>>>><?xml version="1.0" encoding="UTF-8"?>
>>>><Domain ConfigurationVersion="8.1.2.0" Name="mydomain">
>>>> <Server ExtraEjbcOptions="-J-mx512m" ListenAddress=""
>>>> ListenPort="7001" Name="myserver" NativeIOEnabled="true"
>>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
>>>> <SSL Enabled="false" HostnameVerificationIgnored="false"
>>>> IdentityAndTrustLocations="KeyStores" ListenPort="7002"
>>>
>>>Name="myserver"/>
>>>
>>>> <Log Name="myserver" NumberOfFilesLimited="true"/>
>>>> </Server>
>>>> <Security Name="mydomain"
>>>> PasswordPolicy="wl_default_password_policy"
>>>> Realm="wl_default_realm" RealmSetup="true">
>>>> <weblogic.security.providers.authentication.DefaultAuthenticator
>>>> Name="Security:Name=myrealmDefaultAuthenticator" Realm="Security:Name=myrealm"/>
>>>>
>>>> <weblogic.security.providers.authentication.DefaultIdentityAsserter
>>>> ActiveTypes="AuthenticatedUser"
>>>> Name="Security:Name=myrealmDefaultIdentityAsserter" Realm="Security:Name=myrealm"/>
>>>> <weblogic.security.providers.authorization.DefaultRoleMapper
>>>> Name="Security:Name=myrealmDefaultRoleMapper" Realm="Security:Name=myrealm"/>
>>>> <weblogic.security.providers.authorization.DefaultAuthorizer
>>>> Name="Security:Name=myrealmDefaultAuthorizer" Realm="Security:Name=myrealm"/>
>>>> <weblogic.security.providers.authorization.DefaultAdjudicator
>>>> Name="Security:Name=myrealmDefaultAdjudicator"
>>>> Realm="Security:Name=myrealm" RequireUnanimousPermit="false"/>
>>>> <weblogic.security.providers.credentials.DefaultCredentialMapper
>>>> Name="Security:Name=myrealmDefaultCredentialMapper" Realm="Security:Name=myrealm"/>
>>>> <weblogic.management.security.authentication.UserLockoutManager
>>>> Name="Security:Name=myrealmUserLockoutManager" Realm="Security:Name=myrealm"/>
>>>> <weblogic.management.security.Realm
>>>> Adjudicator="Security:Name=myrealmDefaultAdjudicator"
>>>> Auditors="Security:Name=myrealmSTARSIIAuditor"
>>>> AuthenticationProviders="Security:Name=myrealmSTARSIIAuthenticator|Security:Name=myrealmDefaultAuthenticator|Security:Name=myrealmDefaultIdentityAsserter"
>>>> Authorizers="Security:Name=myrealmDefaultAuthorizer|Security:Name=myrealmSTARSIIAuthorizer"
>>>> CredentialMappers="Security:Name=myrealmDefaultCredentialMapper"
>>>> DefaultRealm="true" DisplayName="myrealm"
>>>> FullyDelegateAuthorization="true"
>>>> Name="Security:Name=myrealm"
>>>> RoleMappers="Security:Name=myrealmDefaultRoleMapper" UserLockoutManager="Security:Name=myrealmUserLockoutManager"/>
>>>>
>>>> <gov.fns.starsii.common.security.authentication.STARSIIAuthenticator
>>>> ControlFlag="SUFFICIENT"
>>>> Name="Security:Name=myrealmSTARSIIAuthenticator" Realm="Security:Name=myrealm"/>
>>>> <gov.fns.starsii.common.security.authorization.STARSIIAuthorizer
>>>> ExemptUri="/common/,/images/,/warning.do,/login.do"
>>>> Name="Security:Name=myrealmSTARSIIAuthorizer"
>>>> PolicyDeploymentEnabled="false"
>>>> Realm="Security:Name=myrealm" Verbose="false" denyPermNotFound="true"/>
>>>> <gov.fns.starsii.common.security.audit.STARSIIAuditor
>>>> Name="Security:Name=myrealmSTARSIIAuditor" Realm="Security:Name=myrealm"/>
>>>> </Security>
>>>> <EmbeddedLDAP
>>>> Credential="{3DES}aD+gV9rRggnoShH/kWurILaHTBP/z0jVoZHtp/hU1xI="
>>>
>>>Name="mydomain"/>
>>>
>>>> <SecurityConfiguration
>>>> Credential="{3DES}mhxP4PeuUHmoX6Aggpj5SNB+AX16Gaol8dOfUzXu7xM8CFNASyNdYIOoqtlqPAZvfZgB14KBtY8MkdKGu/iWFq1xQ07walY8"
>>>> Name="mydomain" RealmBootStrapVersion="1"/>
>>>> <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
>>>> <FileRealm Name="wl_default_file_realm"/>
>>>> <PasswordPolicy Name="wl_default_password_policy"/>
>>>> <JDBCConnectionPool
>>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
>>>> Name="STARSII BRSB Pool"
>>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
>>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
>>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
>>>
>>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
>>>
>>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS" Name="StarsIIDS"
>>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
>>>> <JDBCTxDataSource JNDIName="jdbc/TXStarsIIDS" Name="TXStarsIIDS"
>>>> PoolName="STARSII Store Pool" Targets="MyCluster"/>
>>>> <!--StartupClass
>>>> ClassName="gov.fns.starsii.common.common.PropertiesFileLoader"
>>>> DeploymentOrder="250" Name="STARS II Properties Startup Class"
>>>
>>>Targets="myserver,MyCluster"/>
>>>
>>>> <StartupClass
>>>> ClassName="gov.fns.starsii.common.common.ReferenceValuesHelper"
>>>> DeploymentOrder="500"
>>>> Name="STARS II Reference Values Startup Class" Targets="myserver,MyCluster"/>
>>>> <StartupClass
>>>> ClassName="gov.fns.starsii.common.common.ReportCriteriaHelper"
>>>> DeploymentOrder="750"
>>>> Name="STARS II Reports Criteria Startup Class" Targets="myserver,MyCluster"/
>>>>-->
>>>> <MailSession JNDIName="mail/STARSIIMailSession"
>>>> Name="STARSIIMailSession" Properties="mail.host=str2-dev-prj"
>>>
>>>Targets="myserver"/>
>>>
>>>> <JDBCConnectionPool
>>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
>>>> Name="STARSII Store Pool"
>>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
>>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
>>>> Targets="MyCluster"
>>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
>>>> <JDBCConnectionPool
>>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
>>>> Name="AffTest" Password=""
>>>> Properties="user=sa;portNumber=1433;databaseName=affTest;serverName=AFRANK\AFRANK"
>>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
>>>
>>>URL="jdbc:bea:sqlserver://AFRANK\AFRANK:1433"/>
>>>
>>>> <JDBCTxDataSource JNDIName="jdbc/AffTest" Name="AffTest"
>>>> PoolName="AffTest" Targets=""/>
>>>> <JDBCConnectionPool DriverName="weblogic.jdbcspy.SpyDriver"
>>>> Name="Spy STARSII BRSB Pool"
>>>> Password="{3DES}9pslRpr051lR9/NEKdanag=="
>>>> Properties="user=brsbapp;portNumber=1433;databaseName=brsbdev;serverName=str2-dev-db"
>>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
>>>
>>>URL="jdbc:spy:{jdbc:bea:sqlserver://str2-dev-db:1433};log=(file)C:\cvsrepo\sql.log"/>
>>>
>>>> <JDBCConnectionPool
>>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
>>>> Name="STARSII Store Pool 2"
>>>> Password="{3DES}nKggeFT8wZkm0R9H8mXaEQ=="
>>>> Properties="user=storeapp;portNumber=1433;databaseName=storedev;serverName=str2-dev-db"
>>>> Targets="" TestTableName="SQL SELECT COUNT(*) FROM sysobjects"
>>>
>>>URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
>>>
>>>> <JDBCTxDataSource JNDIName="jdbc/StarsIIDS2" Name="StarsIIDS2"
>>>> PoolName="STARSII Store Pool" Targets=""/>
>>>> <JDBCConnectionPool
>>>> DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
>>>> Name="STARSII Stars Pool"
>>>> Password="{3DES}tjstL+8fUvdPQzqhNcCYGA=="
>>>> Properties="user=starsapp;portNumber=1433;databaseName=stars;serverName=str2-dev-db"
>>>> Targets="MyCluster"
>>>> TestTableName="SQL SELECT COUNT(*) FROM sysobjects" URL="jdbc:bea:sqlserver://str2-dev-db:1433"/>
>>>> <Machine Name="MachineA">
>>>> <NodeManager DebugEnabled="true" ListenPort="5555" Name="MachineA"/>
>>>> </Machine>
>>>> <Server Cluster="MyCluster" ExpectedToRun="false"
>>>> ExtraEjbcOptions="-J-mx521m" JDBCLoggingEnabled="true"
>>>> ListenAddress="10.0.0.14" ListenPort="7002" Machine="MachineA"
>>>> Name="Server1" ServerVersion="8.1.2.0" StdoutDebugEnabled="true"
>>>
>>>StdoutSeverityLevel="64">
>>>
>>>> <ServerDebug Name="Server1"/>
>>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server1"/>
>>>> <KernelDebug Name="Server1"/>
>>>> <Log Name="Server1"/>
>>>> <ServerStart Name="Server1"
>>>> OutputFile="C:\bea\user_projects\domains\mydomain\.\NodeManagerClientLogs\mydomain_Server1\startServer_05_05_2004-12_50_56-4.log"
>>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
>>>> <WebServer Name="Server1"/>
>>>> <COM Name="Server1"/>
>>>> <IIOP Name="Server1"/>
>>>> <JTAMigratableTarget Name="Server1" UserPreferredServer="Server1"/>
>>>> <JTARecoveryService Name="Server1"/>
>>>> </Server>
>>>> <Cluster ClusterAddress="10.0.0.14, 10.0.2.15"
>>>> MulticastAddress="226.0.0.244" Name="MyCluster"/>
>>>> <Server Cluster="MyCluster" ExpectedToRun="false"
>>>> ExtraEjbcOptions="-J-mx521m" ListenAddress="10.0.2.15"
>>>> ListenPort="7002" Machine="MachineB" Name="Server2"
>>>> ServerVersion="8.1.2.0" StdoutDebugEnabled="true" StdoutSeverityLevel="64">
>>>> <ServerDebug Name="Server2"/>
>>>> <SSL IdentityAndTrustLocations="KeyStores" Name="Server2"/>
>>>> <KernelDebug Name="Server2"/>
>>>> <Log Name="Server2"/>
>>>> <ServerStart Name="Server2"
>>>> Password="{3DES}js4NnTcuqRE15gEGfNTu4Q==" Username="system"/>
>>>> <WebServer Name="Server2"/>
>>>> <COM Name="Server2"/>
>>>> <IIOP Name="Server2"/>
>>>> <JTAMigratableTarget Name="Server2" UserPreferredServer="Server2"/>
>>>> <JTARecoveryService Name="Server2"/>
>>>> </Server>
>>>> <MigratableTarget Cluster="MyCluster" Name="Server1 (migratable)"
>>>> Notes="This is a system generated default migratable target
>>>
>>>for a server.
>>>
>>>>Do not delete manually." UserPreferredServer="Server1"/>
>>>> <MigratableTarget Cluster="MyCluster" Name="Server2 (migratable)"
>>>> Notes="This is a system generated default migratable target
>>>
>>>for a server.
>>>
>>>>Do not delete manually." UserPreferredServer="Server2"/>
>>>> <Application Deployed="true" Name="STARSII"
>>>> Path="C:\cvsrepo\STARSII\STARSII" StagingMode="nostage" TwoPhase="true">
>>>> <EJBComponent Name="../brsbMessage" Targets="MyCluster" URI="../brsbMessage"/>
>>>> <EJBComponent Name="../brsbSession" Targets="MyCluster" URI="../brsbSession"/>
>>>> <EJBComponent Name="../commonSession" Targets="MyCluster"
>>
>>URI="../commonSession"/>
>>
>>>> <EJBComponent Name="../complianceMessage" Targets="MyCluster"
>>>
>>>URI="../complianceMessage"/>
>>>
>>>> <EJBComponent Name="../complianceSession" Targets="MyCluster"
>>>
>>>URI="../complianceSession"/>
>>>
>>>> <EJBComponent Name="../starsiiEntity" Targets="MyCluster"
>>
>>URI="../starsiiEntity"/>
>>
>>>> <EJBComponent Name="../storeSession" Targets="MyCluster" URI="../storeSession"/>
>>>> <WebAppComponent Name="/brsb" Targets="MyCluster" URI="../brsbWebApp"/>
>>>> <WebAppComponent Name="/compliance" Targets="MyCluster" URI="../complianceWebApp"/>
>>>> <WebAppComponent Name="/common" Targets="MyCluster" URI="../mainWebApp"/>
>>>> <WebAppComponent Name="/store" Targets="MyCluster" URI="../storeWebApp"/>
>>>> </Application>
>>>> <Application Name="AffWebApp" Path="C:\cvsrepo\STARSII"
>>>> StagingMode="nostage" TwoPhase="true">
>>>> <WebAppComponent Name="AffWebApp" Targets="" URI="AffWebApp"/>
>>>> </Application>
>>>> <Application Name="activeportal"
>>>> Path="C:\bea\user_projects\domains\mydomain\myserver\upload"
>>>> StagingMode="nostage" TwoPhase="true">
>>>> <WebAppComponent Name="activeportal" Targets="" URI="activeportal.war"/>
>>>> </Application>
>>>> <JTA Name="mydomain" TimeoutSeconds="300"/>
>>>> <JMSServer Name="JobServer" Targets="Server1 (migratable)">
>>>> <JMSQueue CreationTime="1072820642598"
>>>> JNDIName="jms/STARSIIJobQueue" Name="STARSIIJobQueue"/>
>>>> <JMSQueue CreationTime="1072820669345"
>>>> JNDIName="jms/STARSIIPostQueue" Name="STARSIIPostQueue"/>
>>>> <JMSQueue CreationTime="1088000795852"
>>>> JNDIName="jms/STARSIIValidationQueue" Name="STARSIIValidationQueue"/>
>>>> <JMSQueue CreationTime="1072820687125"
>>>> JNDIName="jms/STARSIIErrorQueue" Name="STARSIIErrorQueue"/>
>>>> <JMSQueue CreationTime="1072820687125"
>>>> JNDIName="jms/STARSIIEmailQueue" Name="STARSIIEmailQueue"/>
>>>> <JMSQueue CreationTime="1072820687225"
>>>> JNDIName="jms/STARSIIEBTStateQueue" Name="STARSIIEBTStateQueue"/>
>>>> <JMSQueue CreationTime="1072820687325"
>>>> JNDIName="jms/STARSIIRFIQueue" Name="STARSIIRFIQueue"/>
>>>> <JMSQueue CreationTime="1072820687425"
>>>> JNDIName="jms/STARSIIRedeQueue" Name="STARSIIRedeQueue"/>
>>>> <JMSQueue CreationTime="1072820687525"
>>>> JNDIName="jms/STARSIIWatchListQueue" Name="STARIIWatchListQueue"/>
>>>> <JMSQueue CreationTime="1072820687625"
>>>> JNDIName="jms/STARSIIDeleteTransFileQueue" Name="STARSIIDeleteTransFileQueue"/>
>>>> <JMSQueue CreationTime="1072820687725"
>>>> JNDIName="jms/STARSIIUpdateAMRQueue" Name="STARSIIUpdateAMRQueue"/>
>>>> <JMSQueue CreationTime="1072820687825"
>>>> JNDIName="jms/STARSIIVPPExtractQueue" Name="STARSIIVPPExtractQueue"/>
>>>> <JMSQueue CreationTime="1072820687925"
>>>> JNDIName="jms/STARSIISIFSUploadQueue" Name="STARSIISIFSUploadQueue"/>
>>>> <JMSQueue CreationTime="1072820688025"
>>>> JNDIName="jms/STARSIIMARSQueue" Name="STARSIIMARSQueue"/>
>>>> <JMSQueue CreationTime="1072820688125"
>>>> JNDIName="jms/STARSIIFRBRichmondExtractQueue" Name="STARSIIFRBRichmondExtractQueue"/>
>>>> <JMSQueue CreationTime="1072820688225"
>>>> JNDIName="jms/STARSIICOTSExtractQueue" Name="STARSIICOTSExtractQueue"/>
>>>> <JMSQueue CreationTime="1072820688325"
>>>> JNDIName="jms/STARSIIVPPUploadQueue" Name="STARSIIVPPUploadQueue"/>
>>>> </JMSServer>
>>>> <Machine Name="MachineB">
>>>> <NodeManager DebugEnabled="true" Name="MachineB"/>
>>>> </Machine>
>>>></Domain>
>>>
>
-
[OSB10.3.1] err creating JMS stuff in OSB cluster from recorded WLS session
Hi all,
I've setup an OSB cluster with 2 managed servers.
From WLS console I created successfully the below JMS resources:
1. new file store, name and directory: MyFileStore_m01, target: bnk01osbm01 migratable
2. new file store, name and directory: MyFileStore_m02, target: bnk01osbm02 migratable
3. new jms server, name: MyJMSServer_m01, persistent store: MyFileStore_m01, target: bnk01osbm01 migratable
4. new jms server, name: MyJMSServer_m02, persistent store: MyFileStore_m02, target: bnk01osbm02 migratable
5. new jms module, name: MyJMSSystemModule, targets: cluster bnk01osbcluster + all servers in the cluster
6. new xa conn factory, name: MyXAConnectionFactory, jndi name: MyXAConnectionFactory
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ XA Connection Factory Enabled: true
7. new Distributed Queue, name: MyDistributedQueue1, jndi name: MyDistributedQueue1, load balancing policy: round-robin
(targets as proposed by WLS itself: cluster bnk01osbcluster + all servers in the cluster)
+ allocate members uniformly: true
and I recorded that into the included recorded_by_wls.py. As said no error has been raised.
Then I removed the above JMS resources and I executed the recorded_by_wls.py from command line getting the error that I reported at the end of the email.
I changed slightly the original py produced by WLS by adding only the below first 5 lines:
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
I included also the recorded_by_wls.py source at the end of the email.
For information I reported also what I saw on WLS console when I created manually my JMS resources.
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?
Any help will be very appreciate.
Thanks in advance.
Regards
ferp
Error:
java weblogic.WLST recorded_by_wls.py Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Starting the script ...
Connecting to t3://wasdv1r3n1.dev.b-source.net:7031 with userid weblogic ...
Successfully connected to Admin Server 'bnk01osbadm' that belongs to domain 'bnk01osb'.
Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Location changed to edit tree. This is a writable tree with
DomainMBean as the root. To make changes you will need to start an edit session via startEdit().
For more help, use help(edit)
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
Activation completed
Starting an edit session ...
Started edit session, please be sure to save and activate your changes once you are done.
Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released once the activation is completed.
This Exception occurred at Mon Sep 07 15:31:33 CEST 2009.
weblogic.application.ModuleException: ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:618)
at weblogic.jms.module.ModuleCoordinator.prepareUpdate(ModuleCoordinator.java:487)
at weblogic.application.internal.flow.DeploymentCallbackFlow$5.next(DeploymentCallbackFlow.java:514)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepareUpdate(DeploymentCallbackFlow.java:280)
at weblogic.application.internal.BaseDeployment$PrepareUpdateStateChange.next(BaseDeployment.java:679)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepareUpdate(BaseDeployment.java:444)
at weblogic.application.internal.SingleModuleDeployment.prepareUpdate(SingleModuleDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepareUpdate(DeploymentStateChecker.java:221)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepareUpdate(AppContainerInvoker.java:149)
at weblogic.deploy.internal.targetserver.operations.DynamicUpdateOperation.doPrepare(DynamicUpdateOperation.java:130)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.jms.common.JMSException: [JMSExceptions:045050]A destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has a jms-create-destination-identifier of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1. However, another destination of name MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 has the same jms-create-destination-identifier. Two destinations with the same jms-create-destination-identifier cannot be co-located on the JMSServer named wlsbJMSServer_auto_2.
at weblogic.jms.backend.BackEnd.addDestination(BackEnd.java:1527)
at weblogic.jms.backend.BEDestinationRuntimeDelegate.prepare(BEDestinationRuntimeDelegate.java:195)
at weblogic.jms.backend.udd.UDDEntity.prepare(UDDEntity.java:444)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1667)
at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1608)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:936)
at weblogic.jms.module.JMSModule.addEntity(JMSModule.java:841)
at weblogic.jms.module.JMSModule.access$1500(JMSModule.java:87)
at weblogic.jms.module.JMSModule$JMSModuleListener.prepareUpdate(JMSModule.java:1485)
at weblogic.descriptor.internal.DescriptorImpl$Update.prepare(DescriptorImpl.java:481)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdateDiff(DescriptorImpl.java:195)
at weblogic.descriptor.internal.DescriptorImpl.prepareUpdate(DescriptorImpl.java:174)
at weblogic.jms.module.JMSModule.prepareUpdate(JMSModule.java:614)
Problem invoking WLST - Traceback (innermost last):
File "/products/software/tmp/recorded_by_wls.py", line 92, in ?
File "<iostream>", line 364, in activate
WLSTException: Error occured while performing activate : Error while Activating changes.ERROR: Unable to add destination MyJMSSystemModule!wlsbJMSServer_auto_2@MyDistributedQueue1 to the back end wlsbJMSServer_auto_2 Use dumpStack() to view the full stacktrace
recorded_by_wls.py source
print "Starting the script ..."
connect("weblogic", "weblogic", "t3://wasdv1r3n1.dev.b-source.net:7031")
edit()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m01')
cd('/FileStores/MyFileStore_m01')
cmo.setDirectory('MyFileStore_m01')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createFileStore('MyFileStore_m02')
cd('/FileStores/MyFileStore_m02')
cmo.setDirectory('MyFileStore_m02')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m01')
cd('/Deployments/MyJMSServer_m01')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m01'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm01 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSServer('MyJMSServer_m02')
cd('/Deployments/MyJMSServer_m02')
cmo.setPersistentStore(getMBean('/FileStores/MyFileStore_m02'))
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbm02 (migratable),Type=MigratableTarget')], ObjectName))
activate()
startEdit()
cd('/')
cmo.createJMSSystemResource('MyJMSSystemModule')
cd('/SystemResources/MyJMSSystemModule')
set('Targets',jarray.array([ObjectName('com.bea:Name=bnk01osbcluster,Type=Cluster')], ObjectName))
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createConnectionFactory('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setJNDIName('MyXAConnectionFactory')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/SecurityParams/MyXAConnectionFactory')
cmo.setAttachJMSXUserId(false)
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/ConnectionFactories/MyXAConnectionFactory/TransactionParams/MyXAConnectionFactory')
cmo.setTransactionTimeout(3600)
cmo.setXAConnectionFactoryEnabled(true)
activate()
startEdit()
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule')
cmo.createUniformDistributedQueue('MyDistributedQueue1')
cd('/JMSSystemResources/MyJMSSystemModule/JMSResource/MyJMSSystemModule/UniformDistributedQueues/MyDistributedQueue1')
cmo.setJNDIName('MyDistributedQueue1')
cmo.setLoadBalancingPolicy('Round-Robin')
cmo.setDefaultTargetingEnabled(true)
activate()
startEdit()
-- source end --
ON WLS console
Name Type Target
MyFileStore_m01 FileStore bnk01osbm01 (migratable)
MyFileStore_m02 FileStore bnk01osbm02 (migratable)
FileStore_auto_1 FileStore bnk01osbm01
FileStore_auto_2 FileStore bnk01osbm02
WseeFileStore_auto_1 FileStore bnk01osbm01
WseeFileStore_auto_2 FileStore bnk01osbm02
Name Persistent Store Target Current Server
MyJMSServer_m01 MyFileStore_m01 bnk01osbm01 (migratable) bnk01osbm01
MyJMSServer_m02 MyFileStore_m02 bnk01osbm02 (migratable) bnk01osbm02
wlsbJMSServer_auto_1 FileStore_auto_1 bnk01osbm01 bnk01osbm01
wlsbJMSServer_auto_2 FileStore_auto_2 bnk01osbm02 bnk01osbm02
WseeJmsServer_auto_1 Wsee FileStore_auto_1 bnk01osbm01 bnk01osbm01
WseeJmsServer_auto_2 Wsee FileStore_auto_2 bnk01osbm02 bnk01osbm02
Name Type
MyJMSSystemModule System
configwiz-jms System
jmsResources System
WseeJmsModule System
Name Type JNDI Name Subdeployment Targets
MyDistributedQueue1 Uniform Distributed Queue MyDistributedQueue1 Default Targetting bnk01osbcluster
MyXAConnectionFactory Connection Factory MyXAConnectionFactory Default Targetting bnk01osbclusterHi Ferp,
Do you have an idea why a successfully recorded WLS session fails when executed from a command line ?It should not fail. Each and every successfully (activation has been done without reporting an error/conflict) recorded session will execute on other servers successfully until a unique name constraint gets violated.
In your case this violation has happened. Your script is trying to create a distributed destination "MyDistributedQueue1" under module "MyJMSSystemModule", targetted to JMS Server "wlsbJMSServer_auto_2" but a Distributed Queue with same JNDI name already exists there.
Please check.
Regards,
Anuj -
JMS server targeted to several clusters
Hello,
I am facing a problem with my JMS configuration in weblogic (version 10.3.4.0). I have two clusters. Following the [JMS best practice|http://forums.oracle.com/forums/message.jspa?messageID=9455261#9455261] I have created a JMS server in each Managed server within the clusters. I have created only one JMS Module with a subdeployment. The JMS Module is targeted to all managed servers within both clusters, and the subdeployment is targeted to all JMS servers within the clusters.
At the JMS module I have created a connection Factory targeted to the subdeployment, till there everything is ok.
Afterwards I try to create a uniform distributed queue (UDQ) targeted to the subdeployment and WebLogic throws the following error:
A UDD must be targeted to servers within a single cluster or a single stand-alone server, rather than Cluster ClusterA and Cluster ClusterB
The only solution that I found is to create one JMS Module-subdeployment per JMS Server. Is there a way to have just a JMS Module and use it in all the managed server in several clusters? or I have to set up the same parameters (ConnectionFactories + queue +quota) in each JMS Module.
Thank you very much in advance.
Cheers,
OscarHi Oscar,
The correct way to step-up a UDQ is something like below
C-1 => MS-1 + MS-2
JMSServer-1 => MS-1
JMSServer-2 => MS-2
JMSModule-1 => C-1
Sub_UDQ => JMSServer-1 + JMSServer-2
UDQ => Sub_UDQ
CF => C-1
Where:
======
MS-x are the managed servers
C-x are the Cluster
UDQ is the Uniform Distributed Queue
Sub_UDQ is the Sub-Deployment for UDQ
CF is the Connection Factory
*=>* mean Targeted.
Also to get more information on it you can have a look at the below link which has the step by step instructions which would surely help you out
Topic: Steps to Configure Uniform Distributed Queue (UDQ) on Weblogic Server
http://middlewaremagic.com/weblogic/?p=3747
Regards,
Ravish Mody -
I'm having a problem getting managed nodes in a cluster to find JMS Queues
and Topics.
The Connection Factory is found, but the destinations are not.
I have targeted the JMS Server to one node in the cluster.
I have targeted the Connection Factories to the cluster.
Is there something else that needs to be done to get the destinations
available to the cluster?
When I view the JNDI tree of the slave nodes, the destinations just are not
there. I wait and wait and they don't show up.
A.M.
I have a question that relates to this discussion.
When I deploy a topic on a cluster I am only allowed to deploy it on one
JMSServer. Trying to deploy it on more than one gives me a JNDI error
(duplicate name). This works fine, however, and messages are delivered to
all members of the cluster. But if I kill off the server where the
destination topic exists, that topic disappears from the cluster and further
messages cannot be delivered. Weblogic tells me that the topic does not
exist. My question is - how do I get the topic to survive the failure of
the server on which it is deployed? Why doesn't replication keep the topic
alive?
"Tom Barnes" <[email protected]> wrote in message
news:[email protected]...
> Note that the admin server does not participate in the cluster so
> it doesn't participate in JNDI replication. If JMS destinations
> exist on the admin server one must use a JNDI context
> that is pinned to the admin server to find them... Same deal
> with connection factories that can talk to the admin server.
>
> Zach wrote:
>
> > Could you please post your config.xml file (the one that doesn't
> > work where the JMS server is deployed to the admin server).
> > _sjz.
> >
> > "Asynch Messaging" <[email protected]> wrote in message
> > news:[email protected]...
> > > I found that we were attempting to deploy the JMS Server to the
'admin'
> > > server, rather than a managed server.
> > > This apparently is not allowed.
> > >
> > > A.M.
> > >
> > > "Asynch Messaging" <[email protected]> wrote in message
> > > news:[email protected]...
> > > > I'm having a problem getting managed nodes in a cluster to find JMS
> > Queues
> > > > and Topics.
> > > > The Connection Factory is found, but the destinations are not.
> > > >
> > > > I have targeted the JMS Server to one node in the cluster.
> > > > I have targeted the Connection Factories to the cluster.
> > > >
> > > > Is there something else that needs to be done to get the
destinations
> > > > available to the cluster?
> > > > When I view the JNDI tree of the slave nodes, the destinations just
are
> > > not
> > > > there. I wait and wait and they don't show up.
> > > >
> > > > A.M.
> > > >
> > > >
> > > >
> > >
> > >
>
-
MDBs failed to connect to remote JMS server
Hi,
We currently have 2 clusters: one is a regular cluster (cluster1) and the other is JMS cluster (cluster2). Our JMS server and filestore are targeted to a migratable server in JMS cluster.
In our weblogic-ejb-jar.xml, we added element <provider-url> to the <message-driven-descriptor> to allow JMS remote connection as follows:
<weblogic-enterprise-bean>
<ejb-name>MyBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>MyTopic</destination-jndi-name>
<provider-url>t3://myhost:19009,myhost:19011</provider-url>
<connection-factory-jndi-name>MyConnectionFactory</connection-factory-jn
di-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
When we deployed our application, the Connection Status of MyBean showed "disconnected". I have tried different values (t3://myhost:19009;t3://myhost:19011) and
(t3://myhost:19009) but got the same result.
When I re-targeted the JMS server and filestore to a regular server (instead of migratable server), I was able to connect remotely. But because we want to be able to migrate our JMS server (auto and manually), I have to target it to a migratable server.
I could not figure out why my MDBs failed to connect to a remote JMS server when it is targeted to a migratable server? Is there a restriction that we have to target to a regular server in order to connect remotely or I'm doing something wrong?
Any help would be greatly appreciated.
Thanks,
ThaoI'm using WL9.2 and my migratable server is actually up and running (is that what you mean about booted?). I meant checking your log files to make sure that the JMS server itself actually booted, not checking that the host WL server was up. (For example you should see INFO messages indicating that the JMS server has loaded "X" records from its persistent store).
>>> Could you elaborate on the known problem?
9.x MDBs have special code for enhanced handling of remote distributed destinations. I'm guessing that this code is somehow causing problems when the remote JMS server is migratable. I don't have enough information to elaborate further than that.
>>> What else I can try?
Beyond contacting customer support, I'm not sure.
Tom -
Load balancing MQ 7.0 Foreign JMS Server and Weblogic 10 MDBs?
We have the following configuration and we are trying to troubleshoot what appears to be a load balancing issue.
We have 3 Solaris servers. Each Solaris server has two Weblogic managed servers running on it. There are a total of 6 managed servers in the Weblogic cluster.
MQ Series 7.0 is also installed on each Solaris server. The MQ queue managers are in a MQ cluster. Each queue manager has the same queues defined.
We have a foreign JMS Server configured on Weblogic that has destinations and a connection factory defined. There aren't many configuration options available for the connection factory. The destinations are bound to the queues defined on MQ using the MQ bindings file.
The MQ bindings file was generated using the TRANSPORT(BIND) mechanism. Each bindings file points to the queue manager running on that machine. So the 2 managed servers running on one machine are accepting messages from the queue manager on that machine.
The MDB's listenning for messages on the MQ queues are configured as follows in the weblogic-ejb-jar.xml:
<max-beans-in-free-pool>16</max-beans-in-free-pool>
We also created a custom work manager with min threads constraint=5 and max threads constraint=16. The dispatch-policy of all the MDBs is set to the custom work manager.
The open input count on each MQ queue managers shows up as 32 which is expected.
The default load algorithm on the cluster is round-robin.
When we run a load test (injecting 40 messages per second on one MQ queue), we notice that one managed server ends up being significantly loaded than the other. Each MQ queue manager in the MQ cluster receives approximately the same number of messages in the load test. But it seems like one managed server is preferred over the other in Weblogic.
What can be done to equally balance the load among the two managed servers on each Solaris server?
Thanks for the help.Load balancing generally applies at determing how many consumer threads has to be created on each of the clustered queue instance. In that sense you have achieved perfect load balancing as your queue instances has the same no of consumer threads.
Once you have set 'x' consumer threads on a queue, it is upto messaging provider to decide which thread to deliver a particular message and you will hardly have any control over this. Since your 32 threads are listening on the same queue, MQ can select any thread for delivering the message and the behaviour could be non deterministic.
One option to change your design is to have a dispacther mdb which picks the messages off the MQ and then routes to a weblogic distributed destination and you can have your core mdb which does all processing listen to this distributed destination. You can enable load balancing when the disaptcher mdb routes the message to the distributed destination. Since dispatcher MDB is nothing more than a router, the unbalanced consumption off the MQ shouldn't seriously affect the server. -
Dealing with failure of JMS server
I'd like to build some fault tolerance into my application using JMS, and I was wondering if a J2EE server with registered topics were to crash, is there the ability to migrate the topics to another J2EE server without the application (publishers/subscribers) knowing?
You can use fault tolerance functionality provided by various JMS vendors.
I have tried out FioranoMQ which contains a dispatcher component to cluster a set of JMS Servers.
Client always sends the connection request to the Dispatcher which forwards it to the Least loaded server in the cluster.
The data on various topics in JMS Servers in the cluster can be synchronised using the Repeater component.
In order to avoid the single point of failure of the Dispatcher, a backup dispatcher can also be configured.
You can find more details and documentation in the developer zone of FioranoMQ on www.fiorano.com -
Communication with JMS server failed
Hi All,
We created the Third Party Product,SWC,TS and Business System in SLD.
While importing S/W component versions from SLD it giving the following error.
Communication with JMS server failed Repeat the last action. If the problem continues to occur after multiple attempts, contact your system administrator to check the availability of the JMS provider service.
Pls help me in this.
Regards,
Goli SridharHi Prateek,
This is the Error log.
#11 10:42:19 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.throwRootCause(PvcTransport.java:448)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:197)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.propagation.XIPropagationException: Communication with JMS server failed
at com.sap.aii.ib.server.propagation.XIPropagationException.createFromException(XIPropagationException.java:48)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:272)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
... 19 more
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:189)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: javax.jms.JMSSecurityException (serialized)
javax.jms.JMSSecurityException: You do not have permissions: action produce and instance jms topic xi PostIntegrate.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
at com.sap.jms.client.session.Session.createProducer(Session.java:2396)
at com.sap.jms.client.session.TopicSession.createPublisher(TopicSession.java:46)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendJMSMessage(MessageReceiverFactory.java:210)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:170)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#10 10:42:19 [Pool-Thread-3] ERROR com.sap.aii.ib.gui.tools.transport.ConcurrentProgressDialog: Execution failed
Thrown:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.throwRootCause(PvcTransport.java:448)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:197)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.propagation.XIPropagationException: Communication with JMS server failed
at com.sap.aii.ib.server.propagation.XIPropagationException.createFromException(XIPropagationException.java:48)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:272)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
... 19 more
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:140)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:189)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: javax.jms.JMSSecurityException (serialized)
javax.jms.JMSSecurityException: You do not have permissions: action produce and instance jms topic xi PostIntegrate.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
at com.sap.jms.client.session.Session.createProducer(Session.java:2396)
at com.sap.jms.client.session.TopicSession.createPublisher(TopicSession.java:46)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendJMSMessage(MessageReceiverFactory.java:210)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendMessage(MessageReceiverFactory.java:170)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:383)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateClosedVersionSet(VersionSetIntegratorImpl.java:133)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateClosedVersionSet(VersionSetIntegrator.java:52)
at com.sap.aii.ib.server.propagation.PropagatorImpl.integrateObjectVersions(PropagatorImpl.java:261)
at com.sap.aii.ib.server.propagation.Propagator.integrateObjectVersions(Propagator.java:174)
at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcIntegrate(PvcTransport.java:191)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.integrateVersionset(InternalTransportServiceImpl.java:480)
at com.sap.aii.ibrep.server.transport.impl.service.InternalRepTransportServiceImpl.autoIntegrate(InternalRepTransportServiceImpl.java:530)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:716)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importFromImportSource(InternalTransportServiceImpl.java:362)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importFromImportSource(TransportServiceImpl.java:151)
at com.sap.aii.ib.sbeans.transport.TransportServiceBean.importFromImportSource(TransportServiceBean.java:75)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0.importFromImportSource(TransportServiceRemoteObjectImpl1_0.java:730)
at com.sap.aii.ib.sbeans.transport.TransportServiceRemoteObjectImpl1_0p4_Skel.dispatch(TransportServiceRemoteObjectImpl1_0p4_Skel.java:100)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#9 10:36:08 [AWT-EventQueue-0] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ibrep.client.swc.ExtSwcServiceException: Communication with JMS server failed
at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:120)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
at java.lang.Thread.run(Unknown Source)
Root cause:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
at com.sap.aii.ib.clsif.extobjects.EOAServiceDelegatorImpl.importExtObject(EOAServiceDelegatorImpl.java:127)
at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:112)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
at java.lang.Thread.run(Unknown Source)
Root cause:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ib.core.extobjects.ExternalOasProcessCSException: Communication with JMS server failed
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:102)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:108)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:272)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed
at com.sap.aii.ib.core.clmgmt.ChangeListMgmtException.createFromException(ChangeListMgmtException.java:35)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:227)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:104)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendSynchronousMessage(MessageReceiverFactory.java:278)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:379)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:86)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: javax.jms.JMSSecurityException (serialized)
javax.jms.JMSSecurityException: You do not have permissions: action consumer and instance jms topic xi PostIntegrate.
at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:231)
at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:2613)
at com.sap.jms.client.session.Session.createConsumer(Session.java:2172)
at com.sap.jms.client.session.TopicSession.createSubscriber(TopicSession.java:39)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.getJmsReceiver(MessageReceiverFactory.java:673)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.startMessageReceivers(MessageReceiverFactory.java:140)
at com.sap.aii.ib.server.notification.MessageReceiverFactory.sendSynchronousMessage(MessageReceiverFactory.java:263)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.sendNotification(VersionSetIntegratorImpl.java:379)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:86)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#8 10:36:08 [Thread-64] ERROR com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog: Unable to import HARISWC, 1.0 of haritest
Thrown:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ibrep.client.swc.ExtSwcServiceException: Communication with JMS server failed
at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:120)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
at java.lang.Thread.run(Unknown Source)
Root cause:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
at com.sap.aii.ib.clsif.extobjects.EOAServiceDelegatorImpl.importExtObject(EOAServiceDelegatorImpl.java:127)
at com.sap.aii.ibrep.client.swc.SwcImporterImpl.importSwc(SwcImporterImpl.java:112)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.importSwcvs(SwcSelectionDialog.java:301)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog.access$200(SwcSelectionDialog.java:51)
at com.sap.aii.ibrep.gui.tools.swcimport.SwcSelectionDialog$3.run(SwcSelectionDialog.java:241)
at java.lang.Thread.run(Unknown Source)
Root cause:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED
com.sap.aii.ib.core.extobjects.ExternalOasProcessCSException: Communication with JMS server failed
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:102)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Serialized server exceptions:
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.extobjects.ExternalOasProcessException: Communication with JMS server failed
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:108)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.utilxi.misc.api.ResourceException: Communication with JMS server failed
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:272)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.clmgmt.ChangeListMgmtException: Communication with JMS server failed
at com.sap.aii.ib.core.clmgmt.ChangeListMgmtException.createFromException(ChangeListMgmtException.java:35)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:227)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException: Communication with JMS server failed
at com.sap.aii.ib.core.versioning.integration.VersionSetIntegrationException.createFromException(VersionSetIntegrationException.java:35)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegratorImpl.integrateOpenChangeList(VersionSetIntegratorImpl.java:104)
at com.sap.aii.ib.server.versioning.integration.VersionSetIntegrator.integrateOpenChangeList(VersionSetIntegrator.java:33)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.releaseChangeList(ChangeListMgmtImpl.java:778)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmtImpl.submitChangeList(ChangeListMgmtImpl.java:217)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:132)
at com.sap.aii.ib.server.clmgmt.ChangeListMgmt.submitChangeList(ChangeListMgmt.java:124)
at com.sap.aii.ibrep.server.persist.swc.SwcManager.storeSldSoftwareComponent(SwcManager.java:264)
at com.sap.aii.ibrep.server.extobjects.SwcAccessor.importExtObject(SwcAccessor.java:105)
at com.sap.aii.ib.server.extobjects.EOAServiceImpl.importExtObject(EOAServiceImpl.java:89)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceBean.importExtObject(EOAServiceBean.java:90)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0.importExtObject(EOAServiceRemoteObjectImpl1_0.java:707)
at com.sap.aii.ib.sbeans.extobjects.EOAServiceRemoteObjectImpl1_0p4_Skel.dispatch(EOAServiceRemoteObjectImpl1_0p4_Skel.java:130)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
MESSAGE ID: com.sap.aii.ib.server.notification.rb_notification.ERR_JMSRESOURCE_CREATION_FAILED (serialized)
com.sap.aii.ib.server.notification.MessageReceiverException: Communication with JMS server failed
at com.sap.aii.ib.server.notification.MessageReceiverException.createFromException(MessageReceiverException.java:31)
at com.sap.aii.ib.server.notification.Mes -
Foreign JMS Server - Weblogic 8.1 - Weblogic 8.1
Hi
I have to weblogic servers running on different ports.
http://server1:port1
http://server2:port2
I have configured JMS store, JMS server, Destination (queue) in port2. I am able to send messages and retrieve messages in port2.
I have written a MDB which was deployed in server1. I want to process the Messages posted to server2 destination. I tried to configure foreign JMS server in server1.
In both servers, i am using default connection factories only.
I am getting the following exceptions.
ForeignMDB is unable to connect to the JMS destination: LocalTestingQueue
LocalTestingQueue is the local jndi name given to the foreign destination.
please find below the weblogic.xml entries for MDB
<weblogic-enterprise-bean>
<ejb-name>ForeignMDB</ejb-name>
<message-driven-descriptor> <destination-jndi-name>LocalTestingQueue</destination-jndi-name> <initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<provider-url>http://myserver:26565</provider-url> <connection-factory-jndi-name>weblogic.jms.ConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
could you please guide me to complete this?
Thanks in advance
Srinivas1 - Ensure that the MDB is configured to reference the remote connection factory AND remote destination.
2 - If using the foreign JMS server facility, ensure that it defines the URL of the remote cluster/server, a connection factory mapping, and a destination mapping. Also ensure that the MDB connection factory and destination descriptor fields reference the local JNDI names for the mappings.
3 - If not using the foreign JMS server facility, ensure that the MDB descriptor has the URL of the remote cluster, and a destination JNDI name that's in the remote cluster. (The connection factory JNDI name is not needed in this case, as the MDB will automatically look for a default connection factory that MDB's use.)
I think the MDB chapter of the EJB programmer's guide will likely be helpful here. The latest documentation for the latest release may be more up-to-date than 8.1 -- the concepts are the same with the newer releases.
Tom
Maybe you are looking for
-
Can't get Epson NX510 to work with new iMac
I am new to Mac, and I apologize if this is the wrong forum to this question, but... Apple threw in an NX510 scanner/printer/copy/fax when I bought my new iMac a couple of months ago. Printer/copy functions works great. But I cannot get the scanner f
-
Blackmagic Intensity Pro Question
I am working on simple tradeshow videos... mostly type and stills. They will be played on Blu Ray. I am building the videos in 1080p. Right now I am viewing the work on the Canvas on my 24" single monitor FCP system. Sure would be nice to better see
-
Good day. Here is my story. I am a noobie. Please be gentle. :-) RAMMap says that AWE is chewing up most of the memory. The machine is a virtual computer (free ESXi) with Windows Server 2008 R2 and SQL Server 2012. The VM has 16GB RAM total with
-
Internet speed cuts in half when running a rule thru the router
Can someone explain to me how it is that I can go from a 80+Mbps upload and 39+Mbps download when I have no rules running via my router, to a 34-38.94Mbps upload and a 37Mbps download speed? I observe the warning of the router that it will utilize s
-
Dual Stepper Motor Controllers on a CAN Bus
Hello All, I hope this is the right forum for this message. If not, please let me know where I should post it. Friends of mine are working on a project involving controlling many dual-stepper motor assemblies, using LabVIEW as the main control code