[JBoss Tools] - Hibernate Tools 4 Alpha @SequenceGenerator unique name ?
by Nicolas Bihan
Nicolas Bihan [https://community.jboss.org/people/nicotexas] created the discussion
"Hibernate Tools 4 Alpha @SequenceGenerator unique name ?"
To view the discussion, visit: https://community.jboss.org/message/760078#760078
--------------------------------------------------------------
Hi, I'm trying to get hbm2java (Eclipse tools 4) to generate my entities with EJB3 annotations to get the @GeneratedValue and @SequenceGenerator for my primary keys. Right now when generating my POJOs I get @SequenceGenerator(name = "generator", sequenceName = "S_CLIENT") @Id @GeneratedValue(strategy = SEQUENCE, generator = "generator") @Column(name = "CLIENT_ID", unique = true, nullable = false, precision = 22, scale = 0) public long getClientId() { return this.clientId; } Look OK but the problem is generator = "generator" that will be the same for every POJO hbm2java generates. I can't find any way to set the name for the SequenceGenerator. Tried with reveng.xml S_CLIENT true true and DelegatingReverseEngineeringStrategy @Override public Properties getTableIdentifierProperties(TableIdentifier identifier) { //@SequenceGenerator(name="APP_DEVDB_APPDEVDBID_GENERATOR", sequenceName="S_APP_DEVDB") Properties properties = new Properties(); properties.put("sequence", "S_"+identifier.getName()); properties.put("name", "Generator"+identifier.getName()); return properties; } public String getTableIdentifierStrategyName(TableIdentifier identifier) { return "sequence"; } Any way to change that behavior? Thanks....
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/760078#760078]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[JBoss Cache] - JBossCache
by shonkylogic
shonkylogic [https://community.jboss.org/people/shonkylogic] modified the document:
"JBossCache"
To view the document, visit: https://community.jboss.org/docs/DOC-10242
--------------------------------------------------------------
> *NOTE:* If you use JBoss Cache, you really should consider migrating to Infinispan (https://www.jboss.org/infinispan), which supercedes JBoss Cache. It does all JBoss Cache does, and much, much more, is more robust, performs better, and has a far more active community.
>
h2. What is JBoss Cache
h5. JBoss Cache consists of two +editions+
* *core* - a replicated, distributed, transactional tree-structured cache
* *pojo* (formerly JBossCacheAop) - a layer on top of the core cache, providing you with an API-less feature set and giving you a more 'pojo' feel to your application with minimal intrusion.
h5. Upcoming editions
* *searchable* - this edition bolts on a search indexer to the cache, allowing you to query the cache using efficient Lucene queries. See the https://community.jboss.org/docs/DOC-10286 JBoss Cache Searchable wiki page for more info.
h2. Versions
The current stable release, recommended for general use, is *JBoss Cache 3.2.2.GA +"Malagueta"+*. Note that this is *not* binary-compatible with *JBoss Cache 1.x* and if you need that level of binary compatibility the recommended version is *JBoss Cache 1.4.1 +"Cayenne"+*. Naga *+is+* compatible with *JBoss Cache 2.x* though.
h2. Learning about JBoss Cache
A https://community.jboss.org/docs/DOC-12843 tutorial and FAQ for both core and pojo editions are provided, along with the https://community.jboss.org/docs/DOC-12843 formal user guide- which should be considered *+required+* reading, +*before*+ asking questions on the users' forum! :)
JBoss Cache can be used either inside JBoss, with a different application server, or as a standalone product.
Here is https://community.jboss.org/docs/DOC-12843 official JBossCache main documentation page. This wiki page will serve for some additional materials.
+Want to help us translate JBoss Cache documentation to a language of your choice? See the https://community.jboss.org/docs/DOC-10261 JBossCacheDocI18n page!+
h2. Troubleshooting
Here is the page for some tips on https://community.jboss.org/docs/DOC-10288 troubleshooting JBoss Cache.
h2. More information
* *Migrating from JBoss Cache 1.x.x to 2.x.x?* Then read https://community.jboss.org/docs/DOC-10246 JBossCache200Migration
* *JBossCache on J2EE servers*:
* JBoss Cache 1.4.x is always available and runs transparently on JBoss AS 4.x.
* JBoss Cache 1.4.x has been tested on J2SE 1.4 and Java SE 5.0. While it +may+ work on Java SE 6, this hasn't been extensively tested.
* JBoss Cache 2.x is always available and runs transparently on the upcoming JBoss AS 5.x.
* JBoss Cache 2.x does not have support for J2SE 1.4 and +requires+ either Java SE 5.0 or Java SE 6, both of which are extensively tested with JBoss Cache 2.x.
* For information on running JBoss Cache 2.x under J2SE 1.4, see this wiki page: https://community.jboss.org/docs/DOC-10263 JBossCacheHabaneroJava1.4
* https://community.jboss.org/docs/DOC-10254 JBossCacheAsCompatibility - a HOWTO for running JBoss Cache 2.x under JBoss AS 4.x safely.
* https://community.jboss.org/docs/DOC-10252 JBossCacheAndWebLogic - for a quick HOWTO on running JBoss Cache under BEA WebLogic 8.1, utilising a startup and shutdown class to initialize the cluster-wide caching service.
* https://community.jboss.org/docs/DOC-10250 JBossCacheAndWAS For a quick overview on how to run JBossCache in WebSphere
* http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAndWAS_6.x JBossCacheAndWAS_6.x - for a quick HOWTO on running JBoss Cache under WebSphere 6.x series
* *Hibernate integration:* See https://community.jboss.org/docs/DOC-10265 JBossCacheHibernate for information and tips on using JBossCache as a 2nd-level cache in http://www.hibernate.org Hibernate
* *Building JBossCache:* Check out the README files in the src distribution or SVN checkout.
* *MVCC:* With JBoss Cache 3 "+Naga+", we have deprecated *optimistic* and *pessimistic* locking in favour of *MVCC*. Read all about it http://jbosscache.blogspot.com/2008/07/mvcc-has-landed.html here.
* *Buddy Replication:* Have trouble replicating a lot of state to many machines in a cluster (whether using JBoss Cache, or other techs that use JBoss Cache such as http state replication)? Read https://community.jboss.org/docs/DOC-10255 JBossCacheBuddyReplication and https://community.jboss.org/docs/DOC-10256 JBossCacheBuddyReplicationDesign!
* *JDBC-based cache loader:* see https://community.jboss.org/docs/DOC-10864 JDBCCacheLoader for information and tips on how to configure JDBCCacheLoader with various DBMS.
* *Accessing and Monitoring JBoss Cache using JMX*: https://community.jboss.org/docs/DOC-10270 JBossCacheMBeans describes how to access JBoss Cache using its JMX MBeans. With JBoss Cache 1.3.0, this is also possible when running in a standalone (e.g., non-server) JDK 5.0 environment.
* *Clustering patterns library*: https://community.jboss.org/docs/DOC-10294 The clustering patterns library contains configuration strategies for high availability using JBoss Cache.
* *Running JBoss Cache with the JGroups Multiplexer* : See https://community.jboss.org/docs/DOC-10274 JBossCacheMultiplexer
* *Monitoring*: See https://community.jboss.org/docs/DOC-12832 Jopr - JBossCache plugin for monitoring JBoss Cache instances within JBoss AS.
* *Groovy*: Want to use JBoss Cache with Groovy and Grails? See this http://grails.org/JBossCache+Plugin plugin.
h2. Upgrading and Compatibility Information
h3. JBoss Cache developer's page
For *Subversion* information, tags and branches, and tips on developing and debugging JBoss Cache, see https://www.jboss.org/community/docs/DOC-10259 JBossCacheDevelopment.
h3. JBoss Cache & JGroups version compatibility
See http://labs.jboss.com/portal/jbosscache/compatibility/index.html http://labs.jboss.com/portal/jbosscache/compatibility/index.html for details
h3. JBoss Cache & JDK Requirements
|| JBoss Cache Version || JDK Compatibility ||
| 1.2, 1.2.1, 1.2.2, 1.2.3 | J2SE 1.3, J2SE 1.4, JavaSE 5.0 |
| 1.2.4.X | J2SE 1.4, JavaSE 5.0 |
| >= 1.3.0 | Runs with J2SE 1.4 and JavaSE 5.0. Needs JavaSE 5.0 to build. |
| >= 2.0.0 | J2SE 5.0, J2SE 6 |
h1. Other editions
Aside from JBoss Cache - Core Edition, we also ship:
* https://community.jboss.org/docs/DOC-11611 JBoss Cache - POJO Edition
* https://community.jboss.org/docs/DOC-10286 JBoss Cache - Searchable Edition
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-10242]
Create a new document in JBoss Cache at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 7 months
[IronJacamar] - Web-app requires a resource-adapter class be included in war
by jleinawe
jleinawe [https://community.jboss.org/people/jleinawe] created the discussion
"Web-app requires a resource-adapter class be included in war"
To view the discussion, visit: https://community.jboss.org/message/760027#760027
--------------------------------------------------------------
Deployed a resource adapter to JBoss AS 7.1.1.Final-SNAPSHOT. The resource adapter integrates WebLogic JMS to the JBoss server.
Deployed a Servlet which will use the JMS resources from the adapter to send/receive JMS messags using WebLogic JMS. Execution of the servlet will fail for classloading issues. The class file noted in the exception is deployed within the resource adapter's rar file. Specifically:
+javax.resource.ResourceException: Error creating naming context instance: JBAS011843: Failed instantiate InitialContextFactory weblogic.jndi.WLInitialContextFactory from classloader ModuleClassLoader for Module "deployment.test.war:main" from Service Module Loader+
The WebLogic JMS server is up and running so the warning message we print is misleading. If we include a copy of the jar file containing 'weblogic.jndi.WLInitialContextFactory' in the war's lib directory, this class loading issue goes away.
Is this a known issue or is there something else that needs to be configured? On other app-servers (Glassfish, WebSphere), we don't see this issue.
01:05:40,734 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (http--0.0.0.0-8080-1) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.spi.EISSystemException: createManagedConnection: javax.jms.JMSException: J2EE GJRA-01003: cause = Error occured when creating a JMS connection.; action = Please verify if JMS provider is up and configuration information for accessing the JMS provider is correctly specified: javax.resource.ResourceException: Error creating naming context instance: JBAS011843: Failed instantiate InitialContextFactory weblogic.jndi.WLInitialContextFactory from classloader ModuleClassLoader for Module "deployment.test.war:main" from Service Module Loader
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_06]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_06]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_06]
at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_06]
at weblogic.jms.ra.RAUtils.make(RAUtils.java:410)
at weblogic.jms.ra.RAUtils.make(RAUtils.java:427)
at weblogic.jms.ra.RAUtils.toResourceException(RAUtils.java:478)
at weblogic.jms.ra.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:144)
at weblogic.jms.ra.ManagedFactoryBase.createManagedConnection(ManagedFactoryBase.java:476)
at weblogic.jms.ra.GenericManagedConnectionFactory.createManagedConnection(Unknown Source)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:761)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:343)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397)
at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:329)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:302)
at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:464)
at weblogic.jms.ra.Provider.allocateConnection(Provider.java:1424)
at weblogic.jms.ra.FactoryBase.localCreateConnection(FactoryBase.java:122)
at weblogic.jms.ra.FactoryBase.createConnectionImpl(FactoryBase.java:145)
at weblogic.jms.ra.ConnectionFactoryBase.createConnection(ConnectionFactoryBase.java:15)
at weblogic.jms.ra.GenericConnectionFactory.createConnection(Unknown Source)
at testJboss.sendMsgToResultTopic(testJboss.java:77) at testJboss.doGet(testJboss.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.12.Final.jar:]
at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.12.Final.jar:]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.12.Final.jar:]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.12.Final.jar:]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:671) [jbossweb-7.0.12.Final.jar:]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:930) [jbossweb-7.0.12.Final.jar:]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06]
Caused by: javax.jms.JMSException: J2EE GJRA-01003: cause = Error occured when creating a JMS connection.; action = Please verify if JMS provider is up and configuration information for accessing the JMS provider is correctly specified: javax.resource.ResourceException: Error creating naming context instance: JBAS011843: Failed instantiate InitialContextFactory weblogic.jndi.WLInitialContextFactory from classloader ModuleClassLoader for Module "deployment.test.war:main" from Service Module Loader
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_06]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_06]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_06]
at java.lang.reflect.Constructor.newInstance(Constructor.java:525) [rt.jar:1.7.0_06]
at weblogic.jms.ra.RAUtils.make(RAUtils.java:410)
at weblogic.jms.ra.RAUtils.make(RAUtils.java:427)
at weblogic.jms.ra.RAUtils.toJMSException(RAUtils.java:115)
at weblogic.jms.ra.ManagedFactoryBase.createRPConnection(ManagedFactoryBase.java:1063)
at weblogic.jms.ra.ManagedConnectionImpl.<init>(ManagedConnectionImpl.java:123)
... 31 more
Caused by: javax.resource.ResourceException: Error creating naming context instance: JBAS011843: Failed instantiate InitialContextFactory weblogic.jndi.WLInitialContextFactory from classloader ModuleClassLoader for Module "deployment.test.war:main" from Service Module Loader
at weblogic.jms.ra.JndiResourceProvider.getResource(JndiResourceProvider.java:97)
at weblogic.jms.ra.RAUtils.lookupUsingConnectorScheme(RAUtils.java:240)
at weblogic.jms.ra.RAUtils.lookupUsingRpResourceLocation(RAUtils.java:181)
at weblogic.jms.ra.ManagedFactoryBase.getFactory(ManagedFactoryBase.java:926)
at weblogic.jms.ra.ManagedFactoryBase.createRPConnection(ManagedFactoryBase.java:1053)
... 32 more
Caused by: javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory weblogic.jndi.WLInitialContextFactory from classloader ModuleClassLoader for Module "deployment.test.war:main" from Service Module Loader
at org.jboss.as.naming.InitialContextFactoryBuilder.createInitialContextFactory(InitialContextFactoryBuilder.java:64)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:681) [rt.jar:1.7.0_06]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) [rt.jar:1.7.0_06]
at javax.naming.InitialContext.init(InitialContext.java:242) [rt.jar:1.7.0_06]
at javax.naming.InitialContext.<init>(InitialContext.java:216) [rt.jar:1.7.0_06]
at weblogic.jms.client.JMSConnectionFactory$1.run(JMSConnectionFactory.java:533)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.client.JMSConnectionFactory.createSubjectByAnonymous(JMSConnectionFactory.java:529)
at weblogic.jms.WrappedInitialContextFactory.getInitialContext(WrappedInitialContextFactory.java:34)
at weblogic.jms.ra.Provider.getInitialContext(Provider.java:1305)
at weblogic.jms.ra.JndiResourceProvider.newInitialContext(JndiResourceProvider.java:80)
at weblogic.jms.ra.JndiResourceProvider.getResource(JndiResourceProvider.java:95)
... 36 more
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/760027#760027]
Start a new discussion in IronJacamar at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[jBPM] - How to define result mapping or exit action that saves task owner
by jemmerling
jemmerling [https://community.jboss.org/people/jemmerling] created the discussion
"How to define result mapping or exit action that saves task owner"
To view the discussion, visit: https://community.jboss.org/message/648536#648536
--------------------------------------------------------------
Hi,
This should be simple for any non-novice, it was suggested before however without an example.
So I have a process variable and I want a particular task to store its owner into that variable (say its name is "task2owner"). Is there an expression for that, for example:
task2owner=#{taskOwner}
So if there is a standard expression for the task owner (the above is just a guess at what it might be) then this result mapping would allow subsequent tasks to determine who owned (and completed) task2.
Failing that, I could try defining an on exit action, using kcontext I can get the node instance which I think has a one-to-one correspondence to the task, however the node instance does not seem to have an attribute that explicitly identifies the owner. Perhaps the owner is a variable?
Any suggestion would be greatly appreciated.
Thanks!
--JE
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/648536#648536]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months
[JBoss Messaging] - JBoss Messaging Bridge NOT handling Network Failure!
by Izaak van Niekerk
Izaak van Niekerk [https://community.jboss.org/people/sakkie6yster] created the discussion
"JBoss Messaging Bridge NOT handling Network Failure!"
To view the discussion, visit: https://community.jboss.org/message/759863#759863
--------------------------------------------------------------
We need a JBoss JMS bridge to facilitate integration to a remote Websphere MQ connection. Essentially we have an application running on JBoss that need to send and receive messages to and from WMQ that is running on a remote server.
We are using JBoss 5.1.0.GA and
Websphere MQ 7.
I have setup the following three configurations (see below) in order to create the "bridge". I am able to send a message to the local JMS queue (TestQ - source) which is successfully picked up by the bridge service and actually sent to the target destination (The remote MQ queue). I have tested this and everything works 100%.
Problem is, as soon as I pull out a network cable to test a typical "network failure" the following exception is thrown (as seen on the JBoss App Console). After plugging the network cable back in, the exception is still thrown every 5 seconds and the message is never sent. Until I physically restart JBoss.
Exception:
+12:24:03,948 ERROR [STDERR] 2012.09.17 12:24:03 MQJMS1023E rollback failed+
+12:24:03,948 WARN [Bridge] jboss.messaging:name=TestBridge,service=Bridge Will retry after a pause of 5000 ms+
+12:24:27,870 WARN [Bridge] jboss.messaging:name=TestBridge,service=Bridge Failed to set up connections+
+javax.naming.NamingException: Unable to retrieve actual object from queue. The exception was: javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.MQCONTEXT.ADMIN.QUEUE [Root exception is javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.MQCONTEXT.ADMIN.QUEUE]+
+ at com.ibm.mq.jms.context.MQContext.lookup(MQContext.java:902)+
+ at com.ibm.mq.jms.context.MQContext.lookup(MQContext.java:840)+
+ at javax.naming.InitialContext.lookup(InitialContext.java:396)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
+ at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:597)+
+ at org.jboss.naming.ExternalContext$CachedContext.invoke(ExternalContext.java:535)+
+ at $Proxy247.lookup(Unknown Source)+
+ at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:833)+
+ at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)+
+ at javax.naming.InitialContext.lookup(InitialContext.java:392)+
+ at org.jboss.jms.server.bridge.JNDIFactorySupport.createObject(JNDIFactorySupport.java:66)+
+ at org.jboss.jms.server.bridge.JNDIDestinationFactory.createDestination(JNDIDestinationFactory.java:45)+
+ at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:956)+
+ at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1223)+
+ at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:68)+
+ at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1569)+
+ at java.lang.Thread.run(Thread.java:619)+
+Caused by: javax.jms.JMSException: MQJMS2008: failed to open MQ queue SYSTEM.MQCONTEXT.ADMIN.QUEUE+
+ at com.ibm.mq.jms.MQQueueServices.getQueueOpenException(MQQueueServices.java:406)+
+ at com.ibm.mq.jms.MQQueueServices.getQueueForBrowse(MQQueueServices.java:269)+
+ at com.ibm.mq.jms.JMSServicesMgr.getQueueForBrowse(JMSServicesMgr.java:156)+
+ at com.ibm.mq.jms.MQQueueBrowser.getEnumeration(MQQueueBrowser.java:269)+
+ at com.ibm.mq.jms.context.MQContext.lookup(MQContext.java:884)+
+ ... 18 more+
Setup:
I have the following jars in server\default\lib folder:
com.ibm.mq.commonservices.jar
com.ibm.mq.headers.jar
com.ibm.mq.jar
com.ibm.mq.jmqi.jar
com.ibm.mq.pcf-6.1.jar
com.ibm.mqetclient.jar
com.ibm.mqjms.jar
dhbcore.jar
mqcontext.jar
TestQ:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<server>
<mbean xmbean-dd="xmdesc/Queue-xmbean.xml" name="jboss.messaging.destination:service=Queue,name=TestIncoming" code="org.jboss.jms.server.destination.QueueService">
<!-- Defining the DLQ for this TestQueue -->
<!-- <attribute name="DLQ"> jboss.messaging.destination:name=DLQ,service=Queue</attribute>-->
<attribute name="JNDIName">queue/TestQ</attribute>
<!-- The number of times, undilivered messages would be resend -->
<attribute name="MaxDeliveryAttempts">-1</attribute>
<depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
</mbean>
</server>
Remote WSMQ JMS Provider:
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>
<!-- The WSMQ JMS provider loader -->
<mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider">
<attribute name="ProviderName">RemoteJMSProvider</attribute>
<attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
<attribute name="FactoryRef">remote/edb2pre1.que.mgr</attribute>
<attribute name="QueueFactoryRef">remote/edb2pre1.que.mgr</attribute>
<attribute name="TopicFactoryRef">remote/edb2pre1.que.mgr</attribute>
<depends>jboss.jndi:service=ExternalContext,jndiName=remote</depends>
</mbean>
<!-- Bind a remote IBM MQ server -->
<mbean code="org.jboss.naming.ExternalContext" name="jboss.jndi:service=ExternalContext,jndiName=remote">
<attribute name="JndiName">remote</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.ibm.mq.jms.context.WMQInitialContextFactory
java.naming.provider.url=edb2pre2.momentum.co.za:1414/SYSTEM.DEF.SVRCONN
java.naming.security.authentication=none
</attribute>
<attribute name="InitialContext">javax.naming.InitialContext</attribute>
</mbean>
Test Bridge:
<?xml version="1.0" encoding="UTF-8"?>
<server>
<mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.messaging:service=Bridge,name=TestBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
<depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
<depends optional-attribute-name="TargetProviderLoader">jboss.messaging:service=JMSProviderLoader,name=RemoteJMSProvider</depends>
<attribute name="SourceDestinationLookup">/queue/TestQ</attribute>
<attribute name="TargetDestinationLookup">/remote/SS.GICSAW.FNBLIFE.REQUEST</attribute>
<attribute name="QualityOfServiceMode">0</attribute>
<attribute name="MaxBatchSize">5</attribute>
<attribute name="MaxBatchTime">1</attribute>
<attribute name="FailureRetryInterval">5000</attribute>
<attribute name="MaxRetries">-1</attribute>
<attribute name="AddMessageIDInHeader">false</attribute>
</mbean>
</server>
I am not sure if anything else is required? Like I said, I am able to send a message and the message gets delivered as long as the network is up; i.e. I can probably assume
that my code is fine? Problem is when the network is down, the server keeps throwing the same exception even after the network is back up again.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/759863#759863]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 7 months