[JBoss JIRA] Created: (JBESB-659) 2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed
by James Williams (JIRA)
2 JBossAS instances cannot share the same JBossMQ service for JMS gateways if JMS is installed
----------------------------------------------------------------------------------------------
Key: JBESB-659
URL: http://jira.jboss.com/jira/browse/JBESB-659
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBossAS 4.2GA, JBossESB - Head as of 07/05.2007.
Reporter: James Williams
Assigned To: Mark Little
I am trying to get 2 JBossAS instances to share the same JMS Server for gateways. There's a lot of moving parts, but I'll try to explain the configurations:
1. JBossAS 4.2.0-GA default config with all .ESB archives, minus the quickstart_helloworld.esb. This server is started using the "-b localhost -c node0" startup parameters.
2. JBossAS 4.2.0-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues. This server is started using the "-b 192.168.200.1 -c node1" startup parameters.
3. JBossAS 4.2-GA default config with "jbossesb.sar" and "quickstart_helloworld.esb". All other .ESB archives are removed and my goal is to use the JMS service in server #1 for gateways/listeners. The quickstart_helloworld.esb archive in this server has its own gateway/listener queues that are different from the gateways/listeners in #2. This server is started using the "-b 192.168.200.2 -c node2" startup parameters.
I'm not having any problems with nodes #2 and #3 sharing the JMS service that's running on #1, so long as JBossMQ isn't installed on node #2 or #3. If JMS is installed, quickstart_helloworld.esb archive fails to deploy on both #2 or #3. It complains that the Gateway queue does not exist, but it most certainly does. Worse yet, when I run the SendJMSMessage test class, it cannot find the queue either. It's as if jbossesb.sar is somehow screwing up all jndi lookups for the queue.
There are a couple things I've done to try to rule out other potential root causes:
1. I tried running #1, #2, #3 w/out any .ESB archives or jbossesb.sar to verify that a JMS client can indeed drop requests into queues on all servers. To me, this validates that 3 unclustered JBossAS instances can each have their own JMS queues that are all accessible on a single machine, like my test environment, just by having the app servers bootstrapped by unique config and ip address. I was worried that the JMS service might be the culprit, but that doesn't appear to be the case.
2. I removed JMS from #2 and #3 to verify that the queues are setup correctly on #1 and to verify that #2 and #3 can indeed share the same JMS service provided they do not have JMS running themselves.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBESB-1531) Sometimes the message delivery fails for the first time
by Jiri Pechanec (JIRA)
Sometimes the message delivery fails for the first time
-------------------------------------------------------
Key: JBESB-1531
URL: http://jira.jboss.com/jira/browse/JBESB-1531
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Adapters, Rosetta
Affects Versions: 4.2.1
Environment: standalone-soa-4.2.0.CR2.zip
Reporter: Jiri Pechanec
Assigned To: Mark Little
Attachments: server.log.gz
Sometimes it happens that message is sent to GW but it goes to RDLQ because of unresponsive EPR.
On the second attempt whel delivery is tried from RDLQ then it succeds. The log says
2008-02-05 11:17:58,037 DEBUG [org.jboss.soa.esb.client.ServiceInvoker] Badly formed EPR [JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ]] for Service [FirstServiceESB:SimpleListener] and Message [header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_jca_bpm_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : jnp://127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jboss.naming:org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : XAConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-37377 ]]. java.lang.NullPointerException
Why there is NullPointerException thrown in the courrier first time bu not on redelivery?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBESB-807) JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
by Tom Fennelly (JIRA)
JBossRemotingGateway doesn't support Http BASIC Auth (and probably more)
------------------------------------------------------------------------
Key: JBESB-807
URL: http://jira.jboss.com/jira/browse/JBESB-807
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.2 Milestone Release 3
Reporter: Tom Fennelly
Assigned To: Tom Fennelly
Fix For: 4.2.1
Talked with Ron Sigal and he thinks we might have to explicitly use the Servlet transport (i.e. the CoyoteInvoker might not be configurable for BASIC auth).
Here's what Ron said exactly.....
"1. HTTPServerInvoker is obsolete. It's been replaced by CoyoteInvoker.
2. According to my O'Reilly Tomcat book, BASIC authorization is configured in the web.xml file by the <login-config> element. But CoyoteInvoker doesn't use the full Tomcat implementation, just the Coyote adapter. I'm really not sure if the Coyote adapter has anything to do with the web.xml file.
3. There is another Remoting transport, the servlet transport, which really does use Tomcat. It uses a servlet as a front end to the server invoker. There's even a web.xml file: src\etc\web\web.xml in the Remoting project directory."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBESB-476) Make action, listener etc configuration setting by setter method the default
by Tom Fennelly (JIRA)
Make action, listener etc configuration setting by setter method the default
----------------------------------------------------------------------------
Key: JBESB-476
URL: http://jira.jboss.com/jira/browse/JBESB-476
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Mark Little
Fix For: 4.2
We currently configure everything by constructor. This is not great for a number of reasons:
1. It can't be compile time validated.
2. Not as "obvious" to someone developing against the API. If in an interface, their IDE (or at least compiler - if using a stone ax) will complain immediately that they're not implementing the interface correctly.
3. Makes our code a little bit more complicated re the reflection code that needs to be implemented.
So I suggest making the interface (that all these things implement) contain a setter method that takes the config. The mandate on the implementation is that they contain a public default constructor.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (JBESB-2077) Missing/broken dependency for Management
by Jiri Pechanec (JIRA)
Missing/broken dependency for Management
----------------------------------------
Key: JBESB-2077
URL: https://jira.jboss.org/jira/browse/JBESB-2077
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.4
Reporter: Jiri Pechanec
Priority: Critical
In version IR4 and previous the log during startup conatined this messages - Note that the message about startup is the last one
2008-09-29 09:20:01,553 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, management.esb
2008-09-29 09:20:01,564 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/DataFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:20:01,571 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/OperationsFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:20:01,582 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/InvokerFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:20:01,934 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2008-09-29 09:20:01,943 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] Initializing java:/ManagementDS from listed sql files
2008-09-29 09:20:01,949 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/jbossesb, warUrl=.../tmp/deploy/tmp3371management.esb-contents/jbossesb-exp.war/
2008-09-29 09:20:02,099 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, slsb.esb
2008-09-29 09:20:02,143 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2008-09-29 09:20:05,033 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, smooks.esb
2008-09-29 09:20:05,048 INFO [org.jboss.jms.server.destination.TopicService] Topic[/topic/org.jboss.soa.esb.transformation.Update] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:20:05,086 INFO [org.jboss.soa.esb.actions.converters.SmooksService] Centralized Smooks Instance (Console Based) instance not started. See the 'console.url' property in '/smooks.esb.properties'
2008-09-29 09:20:05,161 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2008-09-29 09:20:08,209 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
2008-09-29 09:20:08,272 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2008-09-29 09:20:09,492 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, spring.esb
2008-09-29 09:20:09,523 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
2008-09-29 09:20:09,610 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.GA_IR4 (build: SVNTag=SOA_4.3.0.GA_IR4 date=200809041212)] Started in 1m:9s:902ms
In version IR5 there is a message
2008-09-29 09:23:25,425 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.IR5 (build: SVNTag=SOA_4.3.0.IR5 date=200809251150)] Started in 59s:126ms
but the initalization still continues
2008-09-29 09:23:22,307 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, management.esb
2008-09-29 09:23:22,321 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/DataFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:23:22,328 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/OperationsFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:23:22,330 INFO [org.jboss.jms.server.destination.QueueService] Queue[/queue/InvokerFilerQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:23:22,415 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started.
2008-09-29 09:23:23,272 INFO [org.jboss.internal.soa.esb.dependencies.DatabaseInitializer] java:/ManagementDS datasource is already initialized
2008-09-29 09:23:23,274 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/jbossesb, warUrl=.../tmp/deploy/tmp64795management.esb-contents/jbossesb-exp.war/
2008-09-29 09:23:23,333 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, slsb.esb
2008-09-29 09:23:23,375 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started.
2008-09-29 09:23:23,845 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, smooks.esb
2008-09-29 09:23:23,849 INFO [org.jboss.jms.server.destination.TopicService] Topic[/topic/org.jboss.soa.esb.transformation.Update] started, fullSize=200000, pageSize=2000, downCacheSize=2000
2008-09-29 09:23:23,861 INFO [org.jboss.soa.esb.actions.converters.SmooksService] Centralized Smooks Instance (Console Based) instance not started. See the 'console.url' property in '/smooks.esb.properties'
2008-09-29 09:23:23,938 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started.
2008-09-29 09:23:24,046 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
2008-09-29 09:23:24,127 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started.
2008-09-29 09:23:25,274 INFO [org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, spring.esb
2008-09-29 09:23:25,330 INFO [org.quartz.core.QuartzScheduler] Scheduler ScheduleProviderScheduler_$_NON_CLUSTERED started.
2008-09-29 09:23:25,425 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [SOA_4.3.0.IR5 (build: SVNTag=SOA_4.3.0.IR5 date=200809251150)] Started in 59s:126ms
2008-09-29 09:23:34,092 INFO [org.hibernate.cfg.Configuration] configuring from resource: monitoring.cfg.xml
2008-09-29 09:23:34,092 INFO [org.hibernate.cfg.Configuration] Configuration resource: monitoring.cfg.xml
2008-09-29 09:23:34,097 INFO [org.hibernate.cfg.Configuration] Reading mappings from resource : org/jboss/soa/esb/monitoring/monitoring-mappings.hbm.xml
2008-09-29 09:23:34,104 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXPattern -> JMXPATTERN
2008-09-29 09:23:34,105 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXData -> JMXDATA
2008-09-29 09:23:34,108 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperationResult -> JMXOPERATIONRESULT
2008-09-29 09:23:34,119 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXAttribute -> JMXATTRIBUTE
2008-09-29 09:23:34,119 INFO [org.hibernate.cfg.HbmBinder] Mapping class: org.jboss.soa.esb.monitoring.pojo.JMXOperation -> JMXOPERATION
2008-09-29 09:23:34,120 INFO [org.hibernate.cfg.Configuration] Configured SessionFactory: null
2008-09-29 09:23:34,121 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{}
2008-09-29 09:23:34,121 INFO [org.hibernate.connection.DatasourceConnectionProvider] Using datasource: java:/ManagementDS
2008-09-29 09:23:34,129 INFO [org.hibernate.cfg.SettingsFactory] RDBMS: HSQL Database Engine, version: 1.8.0
2008-09-29 09:23:34,129 INFO [org.hibernate.cfg.SettingsFactory] JDBC driver: HSQL Database Engine Driver, version: 1.8.0
2008-09-29 09:23:34,207 INFO [org.hibernate.dialect.Dialect] Using dialect: org.hibernate.dialect.HSQLDialect
2008-09-29 09:23:34,212 INFO [org.hibernate.transaction.TransactionFactoryFactory] Using default transaction strategy (direct JDBC transactions)
2008-09-29 09:23:34,214 INFO [org.hibernate.transaction.TransactionManagerLookupFactory] No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Automatic flush during beforeCompletion(): disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Automatic session close at end of transaction: disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch size: 15
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC batch updates for versioned data: disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Scrollable result sets: enabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] JDBC3 getGeneratedKeys(): disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Connection release mode: auto
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Default batch fetch size: 1
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Generate SQL with comments: disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Order SQL updates by primary key: disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Order SQL inserts for batching: disabled
2008-09-29 09:23:34,214 INFO [org.hibernate.cfg.SettingsFactory] Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
2008-09-29 09:23:34,215 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] Using ASTQueryTranslatorFactory
2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Query language substitutions: {}
2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] JPA-QL strict compliance: disabled
2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Second-level cache: enabled
2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Query cache: disabled
2008-09-29 09:23:34,215 INFO [org.hibernate.cfg.SettingsFactory] Cache provider: org.hibernate.cache.NoCacheProvider
2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Optimize cache for minimal puts: disabled
2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Structured second-level cache entries: disabled
2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Statistics: disabled
2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Deleted entity synthetic identifier rollback: disabled
2008-09-29 09:23:34,216 INFO [org.hibernate.cfg.SettingsFactory] Default entity-mode: pojo
2008-09-29 09:23:34,217 INFO [org.hibernate.cfg.SettingsFactory] Named query checking : enabled
2008-09-29 09:23:34,225 INFO [org.hibernate.impl.SessionFactoryImpl] building session factory
2008-09-29 09:23:34,351 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Factory name: java:/hibernate/MonitoringSessionFactory
2008-09-29 09:23:34,351 INFO [org.hibernate.util.NamingHelper] JNDI InitialContext properties:{}
2008-09-29 09:23:34,352 INFO [org.hibernate.util.NamingHelper] Creating subcontext: hibernate
2008-09-29 09:23:34,352 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Bound factory to JNDI name: java:/hibernate/MonitoringSessionFactory
2008-09-29 09:23:34,352 WARN [org.hibernate.impl.SessionFactoryObjectFactory] InitialContext did not implement EventContext
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months