The OpenEJB2 bits are all ActiveIO related. FYI, Bruce mentioned to
me that the API between 4.0 and 4.1 should be compatible, 4.1 just
has some new features, but the same API.
* * *
It looks like some of the recent Wadi changes in server/trunk, which
included AMQ 4.0.1 as a new dep, may have broken AMQ usage... as now
both Dain and I see failures starting the server related to 2 AMQ
brokers starting.
Something is fishy... notice that 2 brokers are being started...
<snip>
[INFO] Module 8/22 org.apache.geronimo.configs/activemq-broker/1.2-
SNAPSHOT/car 15:26:32,581 INFO [BrokerService] ActiveMQ 4.1-
incubator-SNAPSHOT JMS Message Broker (possibly-unique-broker) is
starting
[INFO] 15:26:32,581 INFO [BrokerService] For help or more
information please see: http://incubator.apache.org/activemq/
[INFO] 15:26:32,603 INFO [ManagementContext] JMX consoles can
connect to service:jmx:rmi://bliss.local/jndi/rmi://localhost:1099/
jmxrmi
[INFO] 15:26:32,806 INFO [JDBCPersistenceAdapter] Database driver
recognized: [apache_derby_embedded_jdbc_driver]
[INFO] 15:26:33,562 INFO [DefaultDatabaseLocker] Attempting to
acquire the exclusive lock to become the Master broker
[INFO] 15:26:33,563 INFO [DefaultDatabaseLocker] Becoming the master
on dataSource: [EMAIL PROTECTED]
[INFO] 15:26:33,641 INFO [JournalPersistenceAdapter] Journal
Recovery Started from: Active Journal: using 2 x 20.0 Megs at: /Users/
jason/ws/geronimo/server/target/geronimo-jetty-j2ee-1.2-SNAPSHOT/
activemq-data/possibly-unique-broker/journal
[INFO] 15:26:33,680 INFO [JournalPersistenceAdapter] Journal
Recovered: 0 message(s) in transactions recovered.
[INFO] 15:26:33,922 INFO [BrokerService] ActiveMQ 4.1-incubator-
SNAPSHOT JMS Message Broker (localhost) is starting
[INFO] 15:26:33,922 INFO [BrokerService] For help or more
information please see: http://incubator.apache.org/activemq/
[INFO] 15:26:33,937 WARN [ManagementContext] Failed to start jmx
connector: javax.naming.NameAlreadyBoundException: jmxrmi [Root
exception is java.rmi.AlreadyBoundException: jmxrmi]
[INFO] 15:26:34,284 INFO [JDBCPersistenceAdapter] Database driver
recognized: [apache_derby_embedded_jdbc_driver]
[INFO] 15:26:34,529 INFO [DefaultDatabaseLocker] Attempting to
acquire the exclusive lock to become the Master broker
[INFO] 15:26:34,529 INFO [DefaultDatabaseLocker] Becoming the master
on dataSource: [EMAIL PROTECTED]
[INFO] 15:26:34,551 INFO [JournalPersistenceAdapter] Journal
Recovery Started from: Active Journal: using 2 x 20.0 Megs at: /Users/
jason/ws/geronimo/server/target/geronimo-jetty-j2ee-1.2-SNAPSHOT/
activemq-data/localhost/journal
[INFO] 15:26:34,560 INFO [JournalPersistenceAdapter] Journal
Recovered: 0 message(s) in transactions recovered.
[INFO] 15:26:34,603 INFO [TransportConnector] Connector vm://
localhost Started
[INFO] 15:26:34,846 INFO [BrokerService] ActiveMQ JMS Message Broker
(localhost, ID:Bliss.local-61347-1162337192319-1:0) started
[INFO] 15:26:34,851 INFO [BrokerService] ActiveMQ JMS Message Broker
(possibly-unique-broker, ID:Bliss.local-61347-1162337192319-1:1) started
[INFO] 15:26:35,028 INFO [TransportServerThreadSupport] Listening
for connections at: stomp://Bliss.local:61613
[INFO] 15:26:35,031 INFO [TransportConnector] Connector stomp://
Bliss.local:61613 Started
[INFO] 15:26:35,034 INFO [TransportServerThreadSupport] Listening
for connections at: tcp://0.0.0.0:61616
[INFO] 15:26:35,035 INFO [TransportConnector] Connector tcp://
0.0.0.0:61616 Started
[INFO] 15:26:35,037 ERROR [GBeanInstanceState] Error while starting;
GBean is now in the FAILED state:
abstractName="org.apache.geronimo.configs/activemq-broker/1.2-
SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/activemq-
broker/1.2-SNAPSHOT/car,j2eeType=JMSConnector,name=ActiveMQ.vm.default"
[INFO] java.io.IOException: VMTransportServer already bound at: vm://
localhost
[INFO] at org.apache.activemq.transport.vm.VMTransportFactory.bind
(VMTransportFactory.java:161)
[INFO] at org.apache.activemq.transport.vm.VMTransportFactory.doBind
(VMTransportFactory.java:147)
[INFO] at org.apache.activemq.transport.TransportFactory.bind
(TransportFactory.java:109)
[INFO] at
org.apache.activemq.broker.BrokerService.createTransportConnector
(BrokerService.java:1348)
</snip>
--jason
On Oct 31, 2006, at 3:31 PM, David Jencks wrote:
On Oct 31, 2006, at 2:31 PM, Jason Dillon wrote:
FYI... I think there are also some issues with Wadi and OpenEJB2
using old deps as well.
Looks like the amq 4.0.1 comes only from the wadi integration in
jetty. I'm experimenting a bit with changing it but gianny will
probably have to be the one to verify wadi still works with 4.1. I
can't find any mention of activemq in openejb2.
thanks
david jencks
--jason
On Oct 31, 2006, at 2:20 PM, Guillaume Nodet wrote:
There has not been much changes between 4.0 and 4.1 afaik
(not incompatible changes in api i mean), so it should be easy
to change the 4.0 version to 4.1.
On 10/31/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
FYI, related to ActiveMQ we need to resolve why there are 2
versions
4.0.x and 4.1.x being included. I sent mail about this last week,
but heard nothing back.
--jason
On Oct 31, 2006, at 1:59 PM, Jacek Laskowski wrote:
> On 10/31/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
>> The upgrade looks non-trivial, I have tried... and failed. Need
>> someone who knows ActiveIO better to port it. Hiram said he
might
>> update it if he has time... but as of yet I guess he has not
found
>> any.
>
> An excerpt from STATUS:
>
> Currently, the biggest concerns for the TCK are ActiveMQ 4 and
> Yoko. Both
> of these are new libraries and may take a considerable amount of
> effort to
> certify. Also, there are few people that understand these new
> libraries,
> the geronimo integrations, and the TCK. In the case of ActiveMQ,
> the one
> person that understands that can certify the code, is unavailable
> for the
> next two weeks.
>
> Isn't it about Hiram? If so, he won't be able to do much wrt this
> soon.
>
> Jacek
>
> --
> Jacek Laskowski
> http://www.jaceklaskowski.pl
--
Cheers,
Guillaume Nodet
