OpenMQ embedded broker in Maven JUnit
I have standalone application wich interacts with OpenMQ through JMS. Maven build tool is used. I want to write JUnit tests checking application interaction with OpenMQ. For this purpose I want to use OpenMQ embedded broker. I found https://mq.dev.java.net/4.4-content/embedded-example.html guide. With minor changes I implemented embedded broker. But it's not work as described in guide.
At first it appear to me that it cann't create necessary directories and I've added
new File("target/openmq/var/instances/imqbroker").mkdirs();
but later I understood that for some reason it's not creating directories and files which should create itself.
I browsed the sources code and found, that Broker.start() method return value ignored during embedded broker creation. It seems to be a bug.
I receive broker event 'READY : Broker has been started' but actually it don't starts and jms port 7676 close.
Please, look at my code and tell me what's wrong with it?
Application can be downloaded from this thread: http://forums.java.net/jive/thread.jspa?messageID=482904񵹘 .
Direct link: http://forums.java.net/jive/servlet/JiveServlet/download/56-153207-482904-13987/openmqtest.zip
To start build process put libraries defined in lib/dir.txt from OpenMQ distribution to project lib directory. Then use
mvn clean package
Here is the output:
Running bulatnig.openmqtest.EmbeddedBrokerTest
[16/сен/2010:09:04:03 MSD] WARNING [B2001]: Unable to load default property file /home/bulat/IdeaProjects/glassjmstest/openmqtest/target/openmq/lib/props/broker/default.properties:
java.io.FileNotFoundException: /home/bulat/IdeaProjects/glassjmstest/openmqtest/target/openmq/lib/props/broker/default.properties (No such file or directory)
[16/сен/2010:09:04:03 MSD] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
[16/сен/2010:09:04:03 MSD]
================================================================================
Open Message Queue 4.5
Oracle
Version: 4.5 (Build 10-f)
Compile: Wed Jun 16 23:23:56 PDT 2010
Copyright (c) 2010 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_20 Sun Microsystems Inc. /usr/lib/jvm/java-6-sun-1.6.0.20/jre
[16/сен/2010:09:04:03 MSD] IMQ_HOME=/home/bulat/IdeaProjects/glassjmstest/openmqtest/target/openmq
[16/сен/2010:09:04:03 MSD] IMQ_VARHOME=/home/bulat/IdeaProjects/glassjmstest/openmqtest/target/openmq/var
[16/сен/2010:09:04:03 MSD] Linux 2.6.32-24-generic amd64 nigmatullin (2 cpu) bulat
[16/сен/2010:09:04:03 MSD] Java Heap Size: max=449664k, current=30336k
[16/сен/2010:09:04:03 MSD] Arguments: -imqhome target/openmq
[16/сен/2010:09:04:03 MSD] Embedded Broker
[16/сен/2010:09:04:03 MSD] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null/instances/imqbroker/lock
java.io.IOException: No such file or directory
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.:
java.io.IOException: No such file or directory
at java.io.UnixFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:883)
at com.sun.messaging.jmq.jmsserver.util.LockFile.getLock(LockFile.java:113)
at com.sun.messaging.jmq.jmsserver.Broker._start(Broker.java:798)
at com.sun.messaging.jmq.jmsserver.Broker.start(Broker.java:412)
at com.sun.messaging.jmq.jmsserver.BrokerProcess.start(BrokerProcess.java:219)
at com.sun.messaging.jmq.jmsserver.DirectBrokerProcess.start(DirectBrokerProcess.java:87)
at com.sun.messaging.jmq.jmsclient.runtime.impl.BrokerInstanceImpl.start(BrokerInstanceImpl.java:144)
at bulatnig.openmqtest.EmbeddedBrokerTest.startServer(EmbeddedBrokerTest.java:50)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Received broker event:READY : Broker has been started
Edited by: bulatka on Sep 15, 2010 10:37 PM
I changed arguments to:
-imqhome target/openmq -libhome /home/bulat/desktop/MessageQueue4_4/mq/lib
Build Failed:
<testcase time="0" classname="bulatnig.openmqtest.EmbeddedBrokerTest" name="bulatnig.openmqtest.EmbeddedBrokerTest">
<error message="com/sun/messaging/jms/management/server/ClusterNotification" type="java.lang.NoClassDefFoundError">java.lang.NoClassDefFoundError: com/sun/messaging/jms/management/server/ClusterNotification
at com.sun.messaging.jmq.jmsserver.management.agent.Agent.loadAllMBeans(Agent.java:671)
at com.sun.messaging.jmq.jmsserver.management.agent.Agent.loadMBeans(Agent.java:628)
at com.sun.messaging.jmq.jmsserver.Broker._start(Broker.java:1385)
at com.sun.messaging.jmq.jmsserver.Broker.start(Broker.java:412)
at com.sun.messaging.jmq.jmsserver.BrokerProcess.start(BrokerProcess.java:219)
at com.sun.messaging.jmq.jmsserver.DirectBrokerProcess.start(DirectBrokerProcess.java:87)
at com.sun.messaging.jmq.jmsclient.runtime.impl.BrokerInstanceImpl.start(BrokerInstanceImpl.java:144)
at bulatnig.openmqtest.EmbeddedBrokerTest.startServer(EmbeddedBrokerTest.java:50)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
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.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345)
at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009)
Caused by: java.lang.ClassNotFoundException: com.sun.messaging.jms.management.server.ClusterNotification
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 28 more
</error>
</testcase>
I added imqjmx to project dependencies: project builds without errors.
The next question: is it possible start embedded broker without OpenMQ locally installed? Which libraries should I put in dependencies to run embedded broker in JUnit tests?
Similar Messages
-
Configuration of embedded broker in 4.4
I'm experimenting with the new embedded broker functionality in the 4.4-09 build, using the example instructions at https://mq.dev.java.net/4.4-content/embedded-example.html
What I'm not liking is the requirement to point the broker at the MQ installation directory. To me, this rather defeats the point of an embedded broker - I don't have an installation, and I don't want to create one. I need to be able to configure the broker entirely within my application.
Is it possible to manually configure the broker programmatically, rather than parsing artifically-constructed command line arguments and sifting through artifically-created configuration files?I'm afraid that at the moment there is no other way of doing it.
Tom -
How to run an embedded broker?
I want to start an embedded OpenMQ broker to use as a destination for messages which are sent as part of a test run by Maven. Essentially I want a broker to be started within the same JVM when the tests are run so I don't have to insure that a broker is available before running the tests. Is this possible, and if so how would I configure it in a Spring application? Now I am starting my broker using a connection factory which uses the port and user/password of a broker which is already running on my local machine. I am not using a broker which runs as part of Glassfish, I want to run OpenMQ broker outside of Glassfish.
Thanks in advance for any suggestions.
--JamesThanks Tom. I used to do this before with ActiveMQ and I was assuming that it could also be done with OpenMQ outside of Glassfish. The approach you have described is what I'm doing now. I guess I could set up my tests to use an embedded ActiveMQ broker for testing and then switch to OpenMQ when deploying the application within Glassfish.
--James -
Service port not remapped after stop and start of embedded broker
Hi everybody,
I started testing embedded OpenMQ 4.4 build yesterday and was wondering if it would be suitable for our test cases. I needed to start and stop a broker almost around every test method. So I intuitively used start() and stop() methods for it. Of course test case failed after second test method :) I did some debugging directly in source code and found out that stop() closes server socket in port mapper. When second start() is invoked it determines whether the server socket is bound and in case it isn't, it stops the broker.
But to the point... is it expected not to rebind the port when start is called after stop or is it classified as a bug that needs to be solved? Because if it would be possible to start and stop the broker repeatedly the instance broker can be reused and no init/shutdown needs to be called...
Thanks for an answer.As I'm sure you know, that's the first promoted build of MQ 4.4 and it will have more testing before the final release.
I would have expected repeated calls to start() and stop() to work, but as you have found, it doesn't, and I can reproduce your error easily.
However it does look as if you can make repeated iterations of the complete init()/start()/stop()/shutdown() cycle, so this might be worth trying as a workaround.
Yes, this is a bug which I have logged internally: we'll investigate before the final 4.4 build.
Thanks for the report,
Nigel -
Fastest way to create a broker instance in GlassFish V3?
Hello,
is there an easy way to launch OpenMQ in GlassFish V3 so that the broker creates the configuration file
glassfish-v3\glassfish\domains\domain1\config\init.conf\imq\instances\imqbroker\props\config.properties
Edit: the first thing I noticed in the console log output of GlassFish was a message that said creation of the server.log is not possible:
java.io.IOException: Couldn't get lock for C:\Program Files\sges-v3\glassfish\do
mains\domain1\logs\server.log
at java.util.logging.FileHandler.openFiles(Unknown Source)
at java.util.logging.FileHandler.<init>(Unknown Source)
at com.sun.enterprise.admin.launcher.GFLauncherLogger.addLogFileHandler(
GFLauncherLogger.java:85)
at com.sun.enterprise.admin.launcher.GFLauncher.setup(GFLauncher.java:14
8)
at com.sun.enterprise.admin.cli.StartDomainCommand.createLauncher(StartD
omainCommand.java:239)
at com.sun.enterprise.admin.cli.StartDomainCommand.runCommandNotEmbedded
(StartDomainCommand.java:122)
at com.sun.enterprise.admin.cli.StartDomainCommand.executeCommand(StartD
omainCommand.java:117)
at com.sun.enterprise.admin.cli.CLICommand.execute(CLICommand.java:257)
at com.sun.enterprise.admin.cli.AsadminMain.executeCommand(AsadminMain.j
ava:229)
at com.sun.enterprise.admin.cli.AsadminMain.main(AsadminMain.java:167)
12.12.2009 10:33:59 com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
C:\Program Files\Java\jdk1.6.0_07\bin\java.exeThis is GlassFish V3 bundled with the NetBeans 6.8 final release, installed in the default location on Windows Vista.
I will test on Windows XP and Ubuntu to see if this is caused by security settings (UAC). Result: works fine there, so it seems to be a Vista / UAC problem.
I tried to deploy imqums.war, which gives this error message (Tested on Vista):
C:\Program Files\sges-v3\glassfish\domains\domain1\applications\imqums\examples\csharp\ReceiveSOAPMsg.exe
(Edit: this was easy to fix by removing the examples from the WAR file - but invoking UMS operations did not have the desired side effect of creating a configuration file)
Many thanks in advance
Edited by: mjustin_de on Dec 12, 2009 1:26 AM
Edited by: mjustin_de on Dec 12, 2009 1:32 AM
Edited by: mjustin_de on Dec 12, 2009 1:37 AM
Edited by: mjustin_de on Dec 12, 2009 9:03 AMHi,
You've obviously been having problems and have been investigating possible solutions, but as a result I'm finding your mail a bit confusing.
You ask
is there an easy way to launch OpenMQ in GlassFish V3 so that the broker creates the configuration file
glassfish-v3\glassfish\domains\domain1\config\init.conf\imq\instances\imqbroker\props\config.propertiesThis file gets created when the broker starts. Are you getting an error on broker startup?
Note that in Glassfish V3 the embedded MQ broker isn't started automatically when the Glassfish instance starts. Instead, the embedded MQ broker is started lazily when you first try to connect to it. You'll see a message in the server log when the embedded broker starts.
the first thing I noticed in the console log output of GlassFish was a message that said creation of the server.log is not possible:
java.io.IOException: Couldn't get lock for C:\Program Files\sges-v3\glassfish\domains\domain1\logs\server.logThat's the Glassfish server log. Were you able to start the Glassfish instance OK? If you're having trouble starting Glassfish itself, or have general questions about Glassfish on Vista, I would suggest asking in the Glassfish user forum: [http://forums.java.net/jive/forum.jspa?forumID=56&start=0|http://forums.java.net/jive/forum.jspa?forumID=56&start=0]
This is GlassFish V3 bundled with the NetBeans 6.8 final release, installed in the default location on Windows Vista.
I will test on Windows XP and Ubuntu to see if this is caused by security settings (UAC).
Result: works fine there, so it seems to be a Vista / UAC problem.I can well imagine that UAC introduces a few challenges! (For what it's worth, I don't have a Vista machine to hand, but I installed NetBeans 6.8 and the bundled Glassfish V3 on Windows 7 (which also has UAC); this creates runtime artefacts such as the server and broker logs under the user's home directory, presumably to avoid UAC issues.)
If any other readers of this forum have experience with NetBeans + Glassfish + Vista please join in.
I tried to deploy imqums.war, which gives this error message (Tested on Vista):
C:\Program Files\sges-v3\glassfish\domains\domain1\applications\imqums\examples\csharp\ReceiveSOAPMsg.exe
(Edit: this was easy to fix by removing the examples from the WAR file - but invoking UMS operations did not have the desired side effect of
creating a configuration file)Was that the complete message? Where was this written? To the console? To the server log?
Nigel -
OpenMQ Unack'ed messages causing Java Heap overflow in STOMP
Hello All,
I am using OpenMQ and STOMP within .Net using C#.
Using OpenMQ's imqcmd.exe command I can see messages being produced for a given consumed topic. I have AutoAcnowledge set and have tried sending messages but still see the UnAck message count grow and grow until my STOMP application runs out of heap space and then the world quickly comes to a grinding halt.
I have tried sending the messages as Non Persistent, have tried limiting the Topic message store size to 1000 messages, and have tried a session.commit after each send but cannot seem to figure out 1) why these messages are UnAck'd in the first place and 2) How to keep the STOMP Java app from getting an overflow and ceasing to function.
Thanks for any help that any of you may be able to offer,
Ted SquilantiWe've logged this as Glassfish issue 11321.
The bug is related to the way in which Glassfish starts the broker lazily when you first try to connect to it.
There is a workaround, which involves changing the lazy-init attribute of the jms-service element in domain.xml to false:
<jms-service default-jms-host="default_JMS_host" type="EMBEDDED">
<jms-host host="localhost" name="default_JMS_host" lazy-init="false" />
</jms-service>This disables the mechanism which starts the embedded broker automatically when a client first tries to connect. Instead, the broker will be started when Glassfish tries to lookup a JMS resource. The simplest way to achieve this is to call "asadmin jms-ping" .
Nigel -
Error while running the command "maven jbi:createArchetype"
Hi all,
I installed maven 1.0.2 and copied the plugin maven-jbi-plugin-1.0.jar into the <maven_home>/plugin directory as said in the url http://docs.codehaus.org/display/SM/Spring+Client+Toolkit
Then when I ran the command maven jbi:createArchetype, I am getting the following error.
=========================================================
Attempting to download dom4j-1.4-dev-8.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/dom4j/jars/dom4j-1.4-dev-8.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download dom4j-1.4-dev-8.jar.
Attempting to download commons-jelly-20030902.160215.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-20030902.160215.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download commons-jelly-20030902.160215.jar.
Attempting to download commons-jelly-tags-jsl-20030211.143151.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-jsl-20030211.143151.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download commons-jelly-tags-jsl-20030211.143151.jar.
Attempting to download commons-jelly-tags-log-20030211.142821.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-log-20030211.142821.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download commons-jelly-tags-log-20030211.142821.jar.
Attempting to download commons-jelly-tags-velocity-20030303.205659.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-velocity-20030303.205659.jar]: java.net.ConnectException: Connection timed out: connec
WARNING: Failed to download commons-jelly-tags-velocity-20030303.205659.jar.
Attempting to download commons-jelly-tags-xml-20040613.030723.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-xml-20040613.030723.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download commons-jelly-tags-xml-20040613.030723.jar.
Attempting to download commons-logging-1.0.3.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-logging/jars/commons-logging-1.0.3.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download commons-logging-1.0.3.jar.
Attempting to download velocity-1.4-dev.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/velocity/jars/velocity-1.4-dev.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download velocity-1.4-dev.jar.
Attempting to download velocity-dvsl-0.45.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/velocity-dvsl/jars/velocity-dvsl-0.45.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download velocity-dvsl-0.45.jar.
Attempting to download xml-apis-1.0.b2.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/xml-apis/jars/xml-apis-1.0.b2.jar]: java.net.ConnectException: Connection timed out: connect
WARNING: Failed to download xml-apis-1.0.b2.jar.
The build cannot continue because of the following unsatisfied dependencies:
dom4j-1.4-dev-8.jar
commons-jelly-20030902.160215.jar
commons-jelly-tags-jsl-20030211.143151.jar
commons-jelly-tags-log-20030211.142821.jar
commons-jelly-tags-velocity-20030303.205659.jar
commons-jelly-tags-xml-20040613.030723.jar (try downloading from http://jakarta.apache.org/commons/jelly/libs/xml/)
commons-logging-1.0.3.jar
velocity-1.4-dev.jar
velocity-dvsl-0.45.jar
xml-apis-1.0.b2.jar
Total time: 3 minutes 35 seconds
Finished at: Thu Aug 25 12:12:38 IST 2005
========================================================
Somebody pls help me out in solving this.
Thanks in advance.
Regards,
VenkatHi there -
I inherited a project that uses Maven to compile a jar file. I have downloaded and installed V1.0.2 and have followed the steps and verified that it was installed correctly. I have even connected it to the existing repository on a share drive. When I attempt to run Maven for the first time, I get an error indicating that it can not download particular jars from www.ibilio.org/maven/***/jar/***.jar
Below is partial output. I have verified that these files do exist already in our central repository and I'm starting to think I need to set the proxy settings. I can not find the file in which I should update. Am I crazy???
Here is the error message:
C:\EPS\resources>maven project.xml
| \/ |__ Apache_ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
Attempting to download log4j-1.2.8.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/log4j/jars/log4j-1.
2.8.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download log4j-1.2.8.jar.
Attempting to download junit-3.8.1.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/junit/jars/junit-3.
8.1.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download junit-3.8.1.jar.
Attempting to download ant-1.5.3-1.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/ant/jars/ant-1.5.3-
1.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download ant-1.5.3-1.jar.
Attempting to download jdbc2_0-stdext.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/jdbc2_0-s
tdext.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download jdbc2_0-stdext.jar.
Attempting to download 8171classes12.zip.
Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/8171class
es12.zip]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download 8171classes12.zip.
Attempting to download pg73jdbc3.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/jdbc/jars/pg73jdbc3
.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download pg73jdbc3.jar.
Attempting to download commons-digester-1.4.1.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-digester/ja
rs/commons-digester-1.4.1.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download commons-digester-1.4.1.jar.
Attempting to download commons-collections-2.1.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-collections
/jars/commons-collections-2.1.jar]: java.net.UnknownHostException: www.ibiblio.o
rg
WARNING: Failed to download commons-collections-2.1.jar.
Attempting to download commons-logging-1.0.3.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-logging/jar
s/commons-logging-1.0.3.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download commons-logging-1.0.3.jar.
Attempting to download commons-beanutils-1.6.1.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/commons-beanutils/j
ars/commons-beanutils-1.6.1.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download commons-beanutils-1.6.1.jar.
Attempting to download ldap.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/novell-ldap/jars/ld
ap.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download ldap.jar.
Attempting to download utilities.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/novell-ldap/jars/ut
ilities.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download utilities.jar.
Attempting to download xerces-1.4.4.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/xerces/jars/xerces-
1.4.4.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download xerces-1.4.4.jar.
Attempting to download servlet-2.3.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/servlet/jars/servle
t-2.3.jar]: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download servlet-2.3.jar.
Attempting to download mail.jar.
Error retrieving artifact from [http://www.ibiblio.org/maven/mail/jars/mail.jar]
: java.net.UnknownHostException: www.ibiblio.org
WARNING: Failed to download mail.jar.
The build cannot continue because of the following unsatisfied dependencies:
log4j-1.2.8.jar
junit-3.8.1.jar
ant-1.5.3-1.jar (try downloading from http://jakarta.apache.org/regexp/)
jdbc2_0-stdext.jar
8171classes12.zip
pg73jdbc3.jar
commons-digester-1.4.1.jar (try downloading from http://jakarta.apache.org/commons/)
commons-collections-2.1.jar (try downloading from http://jakarta.apache.org/commons/)
commons-logging-1.0.3.jar (try downloading from http://jakarta.apache.org/commons/)
commons-beanutils-1.6.1.jar (try downloading from http://jakarta.apache.org/commons/)
ldap.jar
utilities.jar
xerces-1.4.4.jar (try downloading from http://xml.apache.org/xerces2-j/)
servlet-2.3.jar
mail.jar
Total time: 6 seconds
Finished at: Thu Oct 27 09:46:39 EDT 2005 -
Unexpected Broker Internal Error : [transaction failed]:
Currently running glassfish v2.1 with jms broker mode set as LOCAL and remote client message listeners fail to get messages and the following is logged by imqbroker:
[23/Jun/2009:21:45:38 BST] WARNING [B3100]: Unexpected Broker Internal Error : [transaction failed]:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:587)
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:571)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.routeMessage(DataHandler.java:448)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:244)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:97)
at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
at java.lang.Thread.run(Thread.java:595)
[23/Jun/2009:21:45:38 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:46541,jms:39771] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: transaction failed: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
[23/Jun/2009:21:45:38 BST] WARNING [B2189]: Unknown transaction -1(-1), broker will not notify the client. Ignore ROLLBACK_TRANSACTION(48)
Packet: ROLLBACK_TRANSACTION(48):587-10.201.1.142(99:9a:41:23:bb:b7)-46541-1245789938570
Magic/Version: 469754818/301 Size: 112 Type: ROLLBACK_TRANSACTION(48)
Expiration: 0 Timestamp: 1245789938570
Source IP: 10.201.1.142(99:9a:41:23:bb:b7) Port: 46541 Sequence: 587
Property Offset: 76 Property Size: 36
Encryption: 0 Priority: 5
Flags: consumerID: 0
TransactionID: 0
MessageID: 587-10.201.1.142(99:9a:41:23:bb:b7)-46541-1245789938570
Properties: {JMQTransactionID=-1}
Message Body: 0 bytes
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
Any ideas? Clustering is turned off.message broker log
# 1245801254899 Do not modify this line
[24/Jun/2009:00:54:14 BST]
================================================================================
Open Message Queue 4.3
Sun Microsystems, Inc.
Version: 4.3 (Build 7-g)
Compile: Fri Nov 7 18:14:54 PST 2008
Copyright (c) 2007 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.5.0_12 Sun Microsystems Inc. /usr/lib/jdk1.5.0_12/jre
[24/Jun/2009:00:54:14 BST] IMQ_HOME=/opt/our-server/glassfish/imq
[24/Jun/2009:00:54:14 BST] IMQ_VARHOME=/opt/our-server/glassfish/domains/domain1/imq
[24/Jun/2009:00:54:14 BST] Linux 2.6.16 i386 medusa.eng.dolby.net (4 cpu) root
[24/Jun/2009:00:54:14 BST] Java Heap Size: max=193920k, current=193920k
[24/Jun/2009:00:54:14 BST] Arguments: -javahome /usr/lib/jdk1.5.0_12/jre/.. -Dimq.cluster.nowaitForMasterBroker=true -varhome /opt/our-server/glassfish/domains/domain1/imq -startRmiRegistry -rmiRegistryPort 7776 -Dimq.imqcmd.user=admin -passfile /tmp/asmq23784.tmp -save -name imqbroker -port 7676 -bgnd -silent
[24/Jun/2009:00:58:35 BST] [B1065]: Accepting: [email protected]:51368->jms:35424. Count: service=12 broker=13
[24/Jun/2009:00:59:06 BST] WARNING [B3100]: Unexpected Broker Internal Error : [transaction failed]:
com.sun.messaging.jmq.jmsserver.util.BrokerException: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:587)
at com.sun.messaging.jmq.jmsserver.data.TransactionList.addMessage(TransactionList.java:571)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.routeMessage(DataHandler.java:448)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:244)
at com.sun.messaging.jmq.jmsserver.data.handlers.DataHandler.handle(DataHandler.java:97)
at com.sun.messaging.jmq.jmsserver.data.PacketRouter.handleMessage(PacketRouter.java:181)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.readData(IMQIPConnection.java:1489)
at com.sun.messaging.jmq.jmsserver.service.imq.IMQIPConnection.process(IMQIPConnection.java:644)
at com.sun.messaging.jmq.jmsserver.service.imq.OperationRunnable.process(OperationRunnable.java:170)
at com.sun.messaging.jmq.jmsserver.util.pool.BasicRunnable.run(BasicRunnable.java:493)
at java.lang.Thread.run(Thread.java:595)
[24/Jun/2009:00:59:06 BST] WARNING [B2011]: Storing of JMS message from IMQConn[AUTHENTICATED,[email protected]:54965,jms:35424] failed:
com.sun.messaging.jmq.jmsserver.util.BrokerException: transaction failed: Unexpected Broker Exception: [received message with Unknown Transaction ID -1: ignoring message]
[24/Jun/2009:00:59:06 BST] WARNING [B2189]: Unknown transaction -1(-1), broker will not notify the client. Ignore ROLLBACK_TRANSACTION(48)
Packet: ROLLBACK_TRANSACTION(48):113-10.201.1.142(b3:b1:70:67:8e:45)-54965-1245801546716
Magic/Version: 469754818/301 Size: 112 Type: ROLLBACK_TRANSACTION(48)
Expiration: 0 Timestamp: 1245801546716
Source IP: 10.201.1.142(b3:b1:70:67:8e:45) Port: 54965 Sequence: 113
Property Offset: 76 Property Size: 36
Encryption: 0 Priority: 5
Flags: consumerID: 0
TransactionID: 0
MessageID: 113-10.201.1.142(b3:b1:70:67:8e:45)-54965-1245801546716
Properties: {JMQTransactionID=-1}
Message Body: 0 bytes
Internal Buffers (useDirect=false):
Fixed Header Buffer:java.nio.HeapByteBuffer[pos=0 lim=72 cap=72]
[24/Jun/2009:01:09:52 BST] [B1066]: Closing: [email protected]:3031->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=11
[24/Jun/2009:01:09:52 BST] [B1066]: Closing: [email protected]:3033->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=10
[24/Jun/2009:01:09:54 BST] [B1066]: Closing: [email protected]:2930->jms:35424 because "java.net.SocketException: Connection reset". Count: service=0 broker=9
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination workorderStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination workorderStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination wfProfileStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination wfProfileStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination sysMonitorTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination sysMonitorTopic [Topic] has been destroyed
[24/Jun/2009:01:11:52 BST] [B1130]: Destroying auto-created destination reportStatusTopic [Topic] inactive for 120 seconds
[24/Jun/2009:01:11:52 BST] [B1159]: Destination reportStatusTopic [Topic] has been destroyed
[24/Jun/2009:01:14:22 BST] [B1066]: Closing: [email protected]:37062->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=8
[24/Jun/2009:01:14:22 BST] [B1066]: Closing: [email protected]:55527->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=7
[24/Jun/2009:01:19:22 BST] [B1066]: Closing: [email protected]:36246->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=6
[24/Jun/2009:01:19:22 BST] [B1066]: Closing: [email protected]:54965->jms:35424 because "[B0059]: Client closed the connection". Count: service=0 broker=5
[24/Jun/2009:01:19:22 BST] [B1065]: Accepting: [email protected]:59844->jms:35424. Count: service=5 broker=6
glassfish server log snippets
[#|2009-06-24T00:59:13.547+0100|FINER|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=14;_ThreadName=p: thread-pool-1; w: 8;ClassName=com.sun.messaging.jms.ra.SessionAdapter;MethodName=constructor();com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba;BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false;ConnectionID=1429085906906648832, SessionID=1429085906980997632;_RequestID=a8911f36-6814-472b-9d49-a7bac8f6b2d8;|ENTRY com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false ConnectionID=1429085906906648832, SessionID=1429085906980997632|#]
[#|2009-06-24T00:59:13.598+0100|FINER|sun-appserver2.1|javax.resourceadapter.mqjmsra.outbound.connection|_ThreadID=14;_ThreadName=p: thread-pool-1; w: 8;ClassName=com.sun.messaging.jms.ra.SessionAdapter;MethodName=constructor();com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba;BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false;ConnectionID=1429085906906648832, SessionID=1429085906981010432;_RequestID=a8911f36-6814-472b-9d49-a7bac8f6b2d8;|ENTRY com.sun.messaging.jms.ra.ConnectionAdapter@171e8ba BrokerAddress=localhost:7676(35424), ConnectionID=1429085906906648832, ReconnectEnabled: false, IsConnectedToHABroker: false ConnectionID=1429085906906648832, SessionID=1429085906981010432|#]
............. -
The method queueConnection.close() shuts down the broker.
Hi All,
I want to send and recieve messages in the same application. I'm using embedded broker, here's the brokerConfig.xml
<beans>
<broker>
<connector>
<serverTransport uri="vm://localhost" />
</connector>
<persistence>
<vmPersistence/>
</persistence>
</broker>
</beans>I send and receive messages in the separate classes and each one creates its own connection. In the sender class when I call the method queueConnection.close() it shuts down the broker.
How can I keep the broker to recieve messages in the receiver class by it's own connection?
Thanks in advance.Hi James,
I'm guessing you're using ActiveMQ?Yes, ActiveMQ v. 3.2.1.
>
FWIW there's an online forum specifically to discuss
ActiveMQ related issues here...
http://forums.logicblaze.com/forums/show/1.page
10x for link, I'll try it for the next time
Which version are you using?
Unless its a really old version I'm a little in the
dark. The code to close the embedded broker only
fires when there are no more connections open; so
provided each class has its own connection you should
be fine.
Note could this be a timing issue? Are you closing
the connection of the sender before the receiver
creates its connection?You're right. I think the problem is just there. I didn't know that the broker will close when there are no more connections open.
Another option is just to explicitly create a broker
yourself in Java code; then you are in control of its
lifecycle.
There are examples here
http://activemq.org/How+do+I+embed+a+Broker+inside+a+C
onnection?refresh=110x a lot. I'll create the broker myself -
Embedded EJBContainer // No EJBContainer provider available
Hello Friends
Environment :
Weblogic12c
JUnit4
JRockit1.6
Can you please share with me the EJBContainer.PROVIDER value while using weblogic12c.
I created an EJB3.1 stateless session bean, now I'm trying to use embedded ejb container for JUnit test class within the same EJB project.
I'm already followed this link - http://docs.oracle.com/javaee/6/tutorial/doc/gkcrr.html
but no luck.While running JUnit test class, getting following exception you can find at the bottom this post.
I'm using these packages from javax.ejb_3.1.0.jar
import javax.ejb.embeddable.EJBContainer;
import javax.ejb.spi.EJBContainerProvider;
Note : The same test project is running well in glassfish server.
Thanks in advance,
Have more fun with Java.
Justin.
Exception :
javax.ejb.EJBException: No EJBContainer provider available for requested provider:
javax.ejb.spi.EJBContainerProvider: no provider names had been found.
at javax.ejb.embeddable.EJBContainer.reportError(EJBContainer.java:186)
at javax.ejb.embeddable.EJBContainer.createEJBContainer(EJBContainer.java:121)
at com.justin.math.ejb.test.CalculatorEJBJUTest.init(CalculatorEJBJUTest.java:31)
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.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:684)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:391)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Test Class :
package com.justin.math.ejb.test;
import static org.junit.Assert.*;
import java.util.Properties;
import javax.ejb.embeddable.EJBContainer;
//import javax.ejb.spi.EJBContainerProvider;
import javax.naming.NamingException;
import org.junit.AfterClass;
import org.junit.BeforeClass;
import org.junit.Test;
import com.justin.math.ejb.CalculatorEJB;
public class CalculatorEJBJUTest {
static EJBContainer ejbContainer;
static CalculatorEJB calculatorEJB;
@BeforeClass
public static void init() {
String globalJndiName = "java:global/classes/CalculatorEJB";
//String localJndiName = "java:module/CalculatorEJB";
Properties properties = new Properties();
try {
properties.setProperty(EJBContainer.MODULES, "CalculatorEJB");
properties.setProperty(EJBContainer.PROVIDER, "javax.ejb.spi.EJBContainerProvider");
//Also tried without setting properties in WLS12c. Glassfish was fine without properties.
ejbContainer = EJBContainer.createEJBContainer(properties);
//Just trying both global and local jndi names
//calculatorEJB = (CalculatorEJB) ejbContainer.getContext().lookup(localJndiName);
calculatorEJB = (CalculatorEJB) ejbContainer.getContext().lookup(globalJndiName);
} catch (NamingException e) {
e.printStackTrace();
@AfterClass
public static void release() {
if(ejbContainer != null)
ejbContainer.close();
@Test
public void testAdd() {
int result = calculatorEJB.add(1, 2);
assertNotNull(result);
assertEquals(3, result);
@Test
public void testMultiply() {
int result = calculatorEJB.multiply(1, 2);
assertNotNull(result);
assertEquals(2, result);
}Hello gimbal2 - Thank you for advising me to re-post on the right place (WebLogic Server - EJB).
Embedded EJB Container // No EJBContainer provider available
Regards :)
Justin. -
OpenMQ Memory Error - Drop / Ignore messages if Receivers are not listening
Hi,
I am using OpenMQ jms broker. Publishers are publishing data on topic1, topic2 & topic3.
Now if there are no receiver listening on these topics then after couple of hours openmq is crashing by eating all the memory (RAM) available in the system.
How can i configure openmq so that it can drop the messages coming on these topic if there are no receivers listening on them?
Is there any way to drop the messages coming on these topics if no receiver interested in these topics?
Please guide. This is bit urgent.
Thanks & regards,
Pawan ModiPawan,
The term "durable" applies to a TopicSubscription, not a Topic. There are essentially two methods to create a TopicSubscription on a Topic: one to create a durable subscription and one to create a non-durable subscription.
TopicSession.createSubscriber(Topic topic)
TopicSession.createDurableSubscriber(Topic topic, String name) (See [http://java.sun.com/javaee/5/docs/api/javax/jms/TopicSession.html|http://java.sun.com/javaee/5/docs/api/javax/jms/TopicSession.html])
So there isn't really a default.
A durable subscription continues to exist (accumulating messages) even if the client disconnects and goes away, whereas a non-durable subscription disappears the moment the client disconnects.
Nigel -
Stomp bridge not working in GlassFish V3
Hello,
this is a test report for the OpenMQ Stomp Bridge on Windows Vista:
* downloaded http://download.java.net/glassfish/v3/release/glassfish-v3-windows.exe
* installed at C:\glassfishv3-test2
* started GlassFish using startserv.bat
* deployed imqums.war
* verified imqums operation using example ping url (http://localhost:8080/imqums/simple?service=ping&user=admin&password=admin)
* modified imqbroker config.properties: added
imq.bridge.admin.user=admin
imq.bridge.admin.password=admin
imq.bridge.activelist=stomp
imq.bridge.enabled=true
* restarted the broker (stopserv.bat / startserv.bat)
* the imqums ping command now does not get a response
* the broker can not be shut down using stopserv.bat
* Stomp port 7672 is open, telnet connects and accept input, but Stomp client applications can not connect (the CONNECT frame can be sent but the server does not respond)
Here is the message broker log file:
Open Message Queue 4.4
Sun Microsystems, Inc.
Version: 4.4 Update 1 (Build 7-b)
Compile: Wed Nov 18 23:21:05 PST 2009
Copyright (c) 2009 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_07 Sun Microsystems Inc. C:\Program Files\Java\jdk1.6.0_07\jre
[14/Dez/2009:20:16:02 CET] IMQ_HOME=C:\glassfishv3-test2\mq
[14/Dez/2009:20:16:02 CET] IMQ_VARHOME=C:\glassfishv3-test2\glassfish\domains\domain1\imq
[14/Dez/2009:20:16:02 CET] Windows Vista 6.0 x86 mj-PC (2 cpu) mj
[14/Dez/2009:20:16:02 CET] Java Heap Size: max=506816k, current=105356k
[14/Dez/2009:20:16:02 CET] Arguments: -port 7676 -name imqbroker -nobind -imqhome C:\glassfishv3-test2\mq -varhome C:\glassfishv3-test2\glassfish\domains\domain1\imq -libhome C:\glassfishv3-test2\mq\lib -useRmiRegistry -rmiRegistryPort 8686 -save -silent
[14/Dez/2009:20:16:02 CET] Embedded Broker
[14/Dez/2009:20:16:02 CET] [B1060]: Loading persistent data...
[14/Dez/2009:20:16:02 CET] Using built-in file-based persistent store: C:\glassfishv3-test2\glassfish\domains\domain1\imq\instances\imqbroker\
[14/Dez/2009:20:16:02 CET] [B1318]: Initialize bridge service manager
[14/Dez/2009:20:16:02 CET] BridgeManager: Loading bridge stomp
[14/Dez/2009:20:16:02 CET] BridgeManager: Loaded bridge stomp
[14/Dez/2009:20:16:02 CET] [B1041]: Cluster initialization successful.
[14/Dez/2009:20:16:02 CET] [B1004]: Starting the cluster_discovery service using tcp [ 0, 100 ] with min threads 1 and max threads of 1
[14/Dez/2009:20:16:02 CET] [B1136]: Processing stored transactions
[14/Dez/2009:20:16:02 CET] [B1284]: 0 cluster transactions remain in PREPARED state, 0 in COMMITTED state waiting for remote broker completion
[14/Dez/2009:20:16:02 CET] Of 0 remote transactions, 0 in PREPARED state, 0 in COMMITTED state
[14/Dez/2009:20:16:02 CET] [B1013]: Auto Creation of Queues is enabled
[14/Dez/2009:20:16:02 CET] [B1159]: Destination PING_1_1260818007981 [Queue] has been destroyed
[14/Dez/2009:20:16:02 CET] [B1151]: Loading destination PING_1_1260818007981 [Queue] with 0 messages
[14/Dez/2009:20:16:02 CET] [B1152]: Loading of destination PING_1_1260818007981 [Queue] complete
[14/Dez/2009:20:16:02 CET] imq.persist.file.minimizeWrites=false
[14/Dez/2009:20:16:02 CET] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[14/Dez/2009:20:16:02 CET] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[14/Dez/2009:20:16:02 CET] [B1239]: Using platform MBean server
[14/Dez/2009:20:16:02 CET] JESMF classes not present - JESMF support will not be enabled.
[14/Dez/2009:20:16:02 CET] JMX Connector Server jmxrmi started successfully with url service:jmx:rmi://mj-PC/jndi/rmi://mj-PC:8686/mj-PC/7676/jmxrmi
[14/Dez/2009:20:16:02 CET] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
[14/Dez/2009:20:16:02 CET] [B1227]: Using file user repository for admin service connection authentication
[14/Dez/2009:20:16:02 CET] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[14/Dez/2009:20:16:02 CET] [B1227]: Using file user repository for jms service connection authentication
[14/Dez/2009:20:16:02 CET] [B1004]: Starting the mqdirect2 service using in-process connections with min threads 0 and max threads of 0
[14/Dez/2009:20:16:02 CET] [B1227]: Using file user repository for mqdirect2 service connection authentication
[14/Dez/2009:20:16:02 CET] [B1004]: Starting the jmsdirect service using with min threads 0 and max threads of 0
[14/Dez/2009:20:16:02 CET] [B1227]: Using file user repository for jmsdirect service connection authentication
[14/Dez/2009:20:16:03 CET] [B1004]: Starting the cluster service using tcp [ 0.0.0.0/0.0.0.0:50761 ] with min threads 1 and max threads of 1
[14/Dez/2009:20:16:03 CET] [B1228]: Cluster ping interval is 60 seconds
[14/Dez/2009:20:16:03 CET] [B1039]: Broker "imqbroker@mj-PC:7676" ready.
[14/Dez/2009:20:16:03 CET] [B1319]: Start bridge service manager
[14/Dez/2009:20:16:03 CET] BridgeManager: Starting bridge stomp
[14/Dez/2009:20:16:03 CET] BridgeManager: Starting bridge stomp with properties
imq.bridge.stomp.class=com.sun.messaging.bridge.service.stomp.StompBridge
imq.bridge.stomp.type=stomp
imq.bridge.stomp.varhome=C:\glassfishv3-test2\glassfish\domains\domain1\imq\instances\imqbroker\bridges\stomp
imq.bridge.stomp.libhome=C:\glassfishv3-test2\mq\lib
BRIDGE_PROP_PREFIX=imq.bridge.stomp
[14/Dez/2009:20:16:03 CET] BridgeManager: Started bridge stomp
One thing I noticed is that the imqbridgemger.jar is not in C:\glassfishv3-test2\glassfish\lib\install\applications\jmsra - is it necessary to be present here?
I will check Windows XP and add the results here later.
Kind regards,
Michael Justin
Edited by: mjustin_de on Dec 14, 2009 11:38 AM
* Stomp port 7672 is open, telnet connects and accept input, but Stomp client applications can not connect
Edited by: mjustin_de on Dec 14, 2009 2:23 PM
Tested on XP SP with same result. If I remove Stomp support, imqums ping works againWe've logged this as Glassfish issue 11321.
The bug is related to the way in which Glassfish starts the broker lazily when you first try to connect to it.
There is a workaround, which involves changing the lazy-init attribute of the jms-service element in domain.xml to false:
<jms-service default-jms-host="default_JMS_host" type="EMBEDDED">
<jms-host host="localhost" name="default_JMS_host" lazy-init="false" />
</jms-service>This disables the mechanism which starts the embedded broker automatically when a client first tries to connect. Instead, the broker will be started when Glassfish tries to lookup a JMS resource. The simplest way to achieve this is to call "asadmin jms-ping" .
Nigel -
Eclipse/Sun Java Application Server
Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#]Hi,
I'm running MyEclipse 5.5.1 on an XP machine and Java System Application Server on a Win 2003 server in an intranet. I want to deploy directly from MyEclipse, but the server won't start. Have tried Tomcat wich works fine, firewalls are disabled. The log file complains it can't find the path/file specified, although it DOES exist.
An example, this file does exist: C:\Sun\SDK\imq\lib\imqjmsra.rar
Thanks,
Mattias
Here's the complete log file:
[#|2007-06-11T00:07:35.765+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0_01 (build b02-p01) ...|#]
[#|2007-06-11T00:07:36.281+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_11;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_11] from [Sun Microsystems Inc.]|#]
[#|2007-06-11T00:07:36.359+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
[#|2007-06-11T00:07:36.734+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Using MQ RA for Broker lifecycle control|#]
[#|2007-06-11T00:07:42.265+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
[#|2007-06-11T00:07:43.390+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2007-06-11T00:07:43.500+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [AMConfiguratorLifeCycleModule]; [java.lang.ClassNotFoundException: com.sun.am.AMConfiguratorLifeCycleModule]|#]
[#|2007-06-11T00:07:43.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|LCM0101: Exception loading lifecycle module [JBIFramework]; [java.lang.ClassNotFoundException: com.sun.jbi.framework.sun.SunASJBIFramework]|#]
[#|2007-06-11T00:07:44.218+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR7000 : Check for a new version of MQ installation failed : The system cannot find the path specified:C:\Sun\SDK\imq\lib\imqjmsra.rar|#]
[#|2007-06-11T00:07:45.890+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.transaction|_ThreadID=10;_ThreadName=main;3700;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
[#|2007-06-11T00:07:47.703+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.1.100:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]
[#|2007-06-11T00:07:48.031+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;true;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]
[#|2007-06-11T00:07:48.484+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;|JMS Service Connection URL is :mq://p4:7676/|#]
[#|2007-06-11T00:07:48.500+0300|INFO|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...|#]
[#|2007-06-11T00:07:48.625+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}|#]
[#|2007-06-11T00:07:48.671+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
[11/jun/2007:00:07:48 EEST] WARNING [B2001]: Unable to load default property file C:\Sun\SDK\imq\lib\props\broker\default.properties:
java.io.FileNotFoundException: C:\Sun\SDK\imq\lib\props\broker\default.properties (The system cannot find the path specified)
|#]
[#|2007-06-11T00:07:48.687+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3001]: Defaulting to use the fallback properties. The Broker will only run in a minimal configuration using these settings. Fallback properties are being used because the defaults.property files could not be loaded. Please check the value of IMQ_HOME
|#]
[#|2007-06-11T00:07:48.718+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.5.0_11 Sun Microsystems Inc. C:\Program Files\MyEclipse 5.5.1 GA\jre
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_HOME=C:\Sun\SDK\imq
|#]
[#|2007-06-11T00:07:48.734+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] IMQ_VARHOME=Z:\SDK\domains\domain1\imq
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Windows XP 5.1 x86 192.168.1.100 (2 cpu) Administrator
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Java Heap Size: max=506816k, current=21956k
|#]
[#|2007-06-11T00:07:48.750+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] Arguments: -port 7676 -name imqbroker -imqhome C:\Sun\SDK\imq\bin\.. -varhome Z:\SDK\domains\domain1\imq -useRmiRegistry -rmiRegistryPort 8686
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|[11/jun/2007:00:07:48 EEST] ERROR [B3086]: The broker got an exception when trying to acquire the lock file:
null\instances\imqbroker\lock
java.io.IOException: The system cannot find the path specified
The lock file may be corrupted, or there may be a permission problem
with the lock file or the directory that contains the lock file.
If you are certain no other copy of the broker is running with the
instance name "imqbroker" then you may remove the lock file and
try starting the broker again.
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.resource.resourceadapter|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|RAR6035 : Resource adapter start failed : {0}
javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.stream.err|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|
com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.796+0300|INFO|sun-appserver-pe9.0|javax.enterprise.resource.jms|_ThreadID=10;_ThreadName=main;|Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b;com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Service com.sun.enterprise.jms.JmsProviderLifecycle@e5f01b cannot be started! : com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA|#]
[#|2007-06-11T00:07:48.796+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5071: An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Failed to start JMS RA
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:420)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: com.sun.enterprise.connectors.ConnectorRuntimeException: Failed to start resource adapter : MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:142)
at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.<init>(ActiveJmsResourceAdapter.java:215)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:83)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:287)
at com.sun.enterprise.connectors.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:434)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:227)
at com.sun.enterprise.jms.JmsProviderLifecycle.onStartup(JmsProviderLifecycle.java:415)
... 4 more
Caused by: javax.resource.spi.ResourceAdapterInternalException: MQJMSRA_RA4001: start:Aborting:Exception starting EMBEDDED broker=EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:412)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter$1.run(ActiveInboundResourceAdapter.java:120)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.ActiveInboundResourceAdapter.<init>(ActiveInboundResourceAdapter.java:116)
... 10 more
Caused by: java.lang.RuntimeException: EMBEDDED Broker start failure:code = 1
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:199)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:409)
... 13 more
|#]
[#|2007-06-11T00:07:48.828+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server Startup failed. Exiting...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.container.web|_ThreadID=10;_ThreadName=main;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
[#|2007-06-11T00:07:48.828+0300|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|CORE5061: Exception :
com.sun.appserv.server.ServerLifecycleException: WEB0106: An error occurred while stopping the web container
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:754)
at com.sun.enterprise.web.PEWebContainerLifecycle.onShutdown(PEWebContainerLifecycle.java:83)
at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
Caused by: LifecycleException: WEB0103: This web container has not yet been started
at com.sun.enterprise.web.WebContainer.stop(WebContainer.java:834)
at com.sun.enterprise.web.PEWebContainer.stopInstance(PEWebContainer.java:746)
... 5 more
|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 : Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
[#|2007-06-11T00:07:48.828+0300|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
[#|2007-06-11T00:07:49.250+0300|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=5216a006-263a-4cc7-9f1d-607165e4f4c7;|Server stopped due to Server startup failure.|#] -
Help - GlassFish V3 Preview (b55) - Stomp Not Working
Hello,
I'm trying to get Stomp configured and working in a GlassFish V3 Preview build 55 download. I'm running on Vista. I am running a freshly downloaded .zip install. All I have done is unzip the file and start the domain. No other configuration or changes to the install have been done.
Here is what I have done so far to try and get Stomp configured and working:
1. Add the following to the end of /glassfishv3/glassfish/domains/domains1/imq/instances/imqbroker/props/config.properties
imq.bridge.admin.user=admin
imq.bridge.admin.password=admin
imq.bridge.activelist=stomp
imq.bridge.enabled=true
2. After doing the above, I stopped and started the domain. OpenMQ log file showed NoClassDefFoundErrors, unable to initialize... So I added imqbridgemgr.jar and imqstomp.jar to \glassfishv3\glassfish\lib\install\applications\jmsra. This seemed to get rid of the class loading error ... but not sure this was the right place to put these jars.
3. Now I'm getting the following in the OpenMQ log file:
[17/Jul/2009:08:11:57 MDT] [B1319]: Start bridge service manager
[17/Jul/2009:08:11:57 MDT] BridgeManager: Starting bridge stomp
[17/Jul/2009:08:11:57 MDT] BridgeManager: Starting bridge stomp with properties
imq.bridge.stomp.class=com.sun.messaging.bridge.service.stomp.StompBridge
imq.bridge.stomp.type=stomp
imq.bridge.stomp.varhome=C:\glassfishv3\glassfish\domains\domain1\imq\instances\imqbroker\bridges\stomp
imq.bridge.stomp.libhome=C:\glassfishv3\mq\lib
BRIDGE_PROP_PREFIX=imq.bridge.stomp
[17/Jul/2009:08:11:57 MDT] ERROR BridgeManager: Incompatible Grizzly NIO framework major version in no.version, expected 1:
java.lang.UnsupportedOperationException: Incompatible Grizzly NIO framework major version in no.version, expected 1
at com.sun.messaging.bridge.service.stomp.StompServer.init(StompServer.java:158)
at com.sun.messaging.bridge.service.stomp.StompBridge.start(StompBridge.java:86)
at com.sun.messaging.bridge.BridgeServiceManagerImpl.startBridge(BridgeServiceManagerImpl.java:429)
at com.sun.messaging.bridge.BridgeServiceManagerImpl.start(BridgeServiceManagerImpl.java:257)
at com.sun.messaging.jmq.jmsserver.Broker._start(Broker.java:1400)
at com.sun.messaging.jmq.jmsserver.Broker.start(Broker.java:410)
at com.sun.messaging.jmq.jmsserver.BrokerProcess.start(BrokerProcess.java:219)
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:346)
at com.sun.messaging.jms.ra.LifecycleManagedBroker.start(LifecycleManagedBroker.java:334)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:302)
at com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter$1.run(ActiveJmsResourceAdapter.java:332)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter.startResourceAdapter(ActiveJmsResourceAdapter.java:326)
at com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.init(ActiveOutboundResourceAdapter.java:127)
at com.sun.enterprise.connectors.inbound.ActiveInboundResourceAdapterImpl.init(ActiveInboundResourceAdapterImpl.java:85)
at com.sun.enterprise.connectors.ActiveRAFactory.instantiateActiveResourceAdapter(ActiveRAFactory.java:131)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:100)
at com.sun.enterprise.connectors.service.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:213)
at com.sun.enterprise.connectors.service.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:335)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:333)
at com.sun.enterprise.connectors.service.ConnectorService.loadDeferredResourceAdapter(ConnectorService.java:220)
at com.sun.enterprise.connectors.service.ConnectorService.loadResourcesAndItsRar(ConnectorService.java:189)
at com.sun.enterprise.connectors.service.ConnectorService.checkAndLoadPool(ConnectorService.java:364)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:541)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:627)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.testConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:445)
at com.sun.enterprise.connectors.ConnectorRuntime.pingConnectionPool(ConnectorRuntime.java:869)
at org.glassfish.jms.admin.cli.JMSPing.pingConnectionPool(JMSPing.java:172)
at org.glassfish.jms.admin.cli.JMSPing.execute(JMSPing.java:115)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$4.execute(CommandRunnerImpl.java:422)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:437)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:524)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:140)
at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:313)
at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:180)
at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:165)
at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:208)
at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:746)
at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:655)
at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:905)
at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:161)
at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:136)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:103)
at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:89)
at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[17/Jul/2009:08:11:57 MDT] ERROR BridgeManager: [BB3004]: Failed to start bridge stomp: Incompatible Grizzly NIO framework major version in no.version, expected 1
[17/Jul/2009:08:11:57 MDT] BridgeManager: Stopping bridge stomp
I tried copying the grizzly.jar from the imq/lib directory into the jmsra directory... but that didn't seem to help.
Any help would be greatly appreciated.
-DaveHello,
Thanks for taking a look ...
Dave
================================================================================
Open Message Queue 4.4
Sun Microsystems, Inc.
Version: 4.4 (Build 11-e)
Compile: Wed Jul 8 22:37:05 PDT 2009
Copyright (c) 2009 Sun Microsystems, Inc. All rights reserved. Use is
subject to license terms.
================================================================================
Java Runtime: 1.6.0_14 Sun Microsystems Inc. C:\Program Files\Java\jdk1.6.0_14\jre
[17/Jul/2009:09:41:10 MDT] IMQ_HOME=C:\glassfishv3\mq
[17/Jul/2009:09:41:10 MDT] IMQ_VARHOME=C:\glassfishv3\glassfish\domains\domain1\imq
[17/Jul/2009:09:41:10 MDT] Windows Vista 6.0 amd64 Dave-PC.wsi.local (2 cpu) Dave
[17/Jul/2009:09:41:10 MDT] Java Heap Size: max=466048k, current=143424k
[17/Jul/2009:09:41:10 MDT] Arguments: -port 7676 -name imqbroker -imqhome C:\glassfishv3\mq -varhome C:\glassfishv3\glassfish\domains\domain1\imq -libhome C:\glassfishv3\mq\lib -useRmiRegistry -rmiRegistryPort 8686 -save -silent
[17/Jul/2009:09:41:10 MDT] Embedded Broker
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the portmapper service using tcp [ 7676, 50, <strong>] with min threads 1 and max threads of 1
[17/Jul/2009:09:41:10 MDT] [B1060]: Loading persistent data...
[17/Jul/2009:09:41:10 MDT] Using built-in file-based persistent store: C:\glassfishv3\glassfish\domains\domain1\imq\instances\imqbroker\
[17/Jul/2009:09:41:10 MDT] [B1318]: Initialize bridge service manager
[17/Jul/2009:09:41:10 MDT] BridgeManager: Loading bridge stomp
[17/Jul/2009:09:41:10 MDT] BridgeManager: Loaded bridge stomp
[17/Jul/2009:09:41:10 MDT] [B1041]: Cluster initialization successful.
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the cluster_discovery service using tcp [ 0, 100 ] with min threads 1 and max threads of 1
[17/Jul/2009:09:41:10 MDT] [B1136]: Processing stored transactions
[17/Jul/2009:09:41:10 MDT] [B1284]: 0 cluster transactions remain in PREPARED state, 0 in COMMITTED state waiting for remote broker completion
[17/Jul/2009:09:41:10 MDT] Of 0 remote transactions, 0 in PREPARED state, 0 in COMMITTED state
[17/Jul/2009:09:41:10 MDT] [B1013]: Auto Creation of Queues is enabled
[17/Jul/2009:09:41:10 MDT] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
[17/Jul/2009:09:41:10 MDT] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
[17/Jul/2009:09:41:10 MDT] [B1239]: Using platform MBean server
[17/Jul/2009:09:41:10 MDT] JESMF classes not present - JESMF support will not be enabled.
[17/Jul/2009:09:41:10 MDT] JMX Connector Server jmxrmi started successfully with url service:jmx:rmi://Dave-PC/jndi/rmi://Dave-PC.wsi.local:8686/Dave-PC.wsi.local/7676/jmxrmi
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the admin service using tcp(host = </strong>, port=0, mode=dedicated) with min threads 4 and max threads of 10
[17/Jul/2009:09:41:10 MDT] [B1227]: Using file user repository for admin service connection authentication
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
[17/Jul/2009:09:41:10 MDT] [B1227]: Using file user repository for jms service connection authentication
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the jmsdirect service using with min threads 0 and max threads of 0
[17/Jul/2009:09:41:10 MDT] [B1227]: Using file user repository for jmsdirect service connection authentication
[17/Jul/2009:09:41:10 MDT] [B1004]: Starting the cluster service using tcp [ 0.0.0.0/0.0.0.0:51658 ] with min threads 1 and max threads of 1
[17/Jul/2009:09:41:10 MDT] [B1228]: Cluster ping interval is 60 seconds
[17/Jul/2009:09:41:10 MDT] [B1039]: Broker "[email protected]:7676" ready.
[17/Jul/2009:09:41:10 MDT] [B1319]: Start bridge service manager
[17/Jul/2009:09:41:10 MDT] BridgeManager: Starting bridge stomp
[17/Jul/2009:09:41:10 MDT] BridgeManager: Starting bridge stomp with properties
imq.bridge.stomp.class=com.sun.messaging.bridge.service.stomp.StompBridge
imq.bridge.stomp.type=stomp
imq.bridge.stomp.varhome=C:\glassfishv3\glassfish\domains\domain1\imq\instances\imqbroker\bridges\stomp
imq.bridge.stomp.libhome=C:\glassfishv3\mq\lib
BRIDGE_PROP_PREFIX=imq.bridge.stomp
[17/Jul/2009:09:41:10 MDT] ERROR BridgeManager: Incompatible Grizzly NIO framework major version in no.version, expected 1:
java.lang.UnsupportedOperationException: Incompatible Grizzly NIO framework major version in no.version, expected 1
at com.sun.messaging.bridge.service.stomp.StompServer.init(StompServer.java:158)
at com.sun.messaging.bridge.service.stomp.StompBridge.start(StompBridge.java:86)
at com.sun.messaging.bridge.BridgeServiceManagerImpl.startBridge(BridgeServiceManagerImpl.java:429)
at com.sun.messaging.bridge.BridgeServiceManagerImpl.start(BridgeServiceManagerImpl.java:257)
at com.sun.messaging.jmq.jmsserver.Broker._start(Broker.java:1400)
at com.sun.messaging.jmq.jmsserver.Broker.start(Broker.java:410)
at com.sun.messaging.jmq.jmsserver.BrokerProcess.start(BrokerProcess.java:219)
at com.sun.messaging.jms.ra.EmbeddedBrokerRunner.start(EmbeddedBrokerRunner.java:346)
at com.sun.messaging.jms.ra.LifecycleManagedBroker.start(LifecycleManagedBroker.java:334)
at com.sun.messaging.jms.ra.ResourceAdapter.start(ResourceAdapter.java:302)
at com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter$1.run(ActiveJmsResourceAdapter.java:332)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.enterprise.connectors.jms.system.ActiveJmsResourceAdapter.startResourceAdapter(ActiveJmsResourceAdapter.java:326)
at com.sun.enterprise.connectors.ActiveOutboundResourceAdapter.init(ActiveOutboundResourceAdapter.java:127)
at com.sun.enterprise.connectors.inbound.ActiveInboundResourceAdapterImpl.init(ActiveInboundResourceAdapterImpl.java:85)
at com.sun.enterprise.connectors.ActiveRAFactory.instantiateActiveResourceAdapter(ActiveRAFactory.java:131)
at com.sun.enterprise.connectors.ActiveRAFactory.createActiveResourceAdapter(ActiveRAFactory.java:100)
at com.sun.enterprise.connectors.service.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:213)
at com.sun.enterprise.connectors.service.ResourceAdapterAdminServiceImpl.createActiveResourceAdapter(ResourceAdapterAdminServiceImpl.java:335)
at com.sun.enterprise.connectors.ConnectorRuntime.createActiveResourceAdapter(ConnectorRuntime.java:333)
at com.sun.enterprise.connectors.service.ConnectorService.loadDeferredResourceAdapter(ConnectorService.java:220)
at com.sun.enterprise.connectors.service.ConnectorService.loadResourcesAndItsRar(ConnectorService.java:189)
at com.sun.enterprise.connectors.service.ConnectorService.checkAndLoadPool(ConnectorService.java:364)
at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getManagedConnectionFactory
......... -
Problem to send a message with JMS
Hi
I'm doing some tests with the api JMS to know how works. I have got some problems. I have been looking for some information but i don't find so much. I have got too doubts.
I am usinng Netbeans 5.5 with Sun Java System Application Server Platform Edition 9.0_01 (build b14).
I am trying to do it with ejb. Because in the future the application can have got so many connection in the same time.
The server shows me the next errors.
Starting Sun Java System Application Server Platform Edition 9.0_01 (build b14) ...
CORE5098: AS Socket Service Initialization has been completed.
CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.6.0_03] from [Sun Microsystems Inc.]
SEC1002: Security Manager is OFF.
ADM0001:MBeanServer initialized successfully
SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
sgmt.service_initialized
DPL5400:Exception occurred : error in opening zip file.
ADM1079: Initialization of AMX MBeans successful
ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://t1:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
ADM1506: Status of Standard JMX Connector: Active = [true]
JTS5014: Recoverable JTS instance, serverId = [3700]
About to load the system app: MEjbApp
LDR5010: All ejb(s) of [MEjbApp] loaded successfully!
About to load the system app: __ejb_container_timer_app
EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]
LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:198)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 17 more
CORE5021: Application NOT loaded: [Chat-ejb]
WEB0302: Starting Sun-Java-System/Application-Server.
WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]
WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]
WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]
WEB0100: Loading web module [amserver] in virtual server [server] at [/amserver]
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context ''
Initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
Completed initializing Sun's JavaServer Faces implementation (1.2_02-b03-FCS) for context '/asadmin'
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
About to load the system app: __JWSappclients
WEB0100: Loading web module [__JWSappclients:sys.war] in virtual server [server] at [/__JWSappclients]
Using MQ RA for Broker lifecycle control
JMS Service Connection URL is :mq://t1:7676/
MQJMSRA_RA1101: SJSMQ JMS Resource Adapter starting...
EB-start:brokerProps={imq.instancename=imqbroker, imq.jmx.rmiregistry.port=8686, BrokerArgs=-port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686, imq.jmx.rmiregistry.use=true, imq.portmapper.port=7676}
[07/nov/2007:18:35:03 CET]
================================================================================
Sun Java(tm) System Message Queue 4.0
Sun Microsystems, Inc.
Version: 4.0 (Build 27-a)
Compile: Thu 03/02/2006
Copyright (c) 2006 Sun Microsystems, Inc. All rights reserved.
SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
This product includes code licensed from RSA Data Security.
================================================================================
Java Runtime: 1.6.0_03 Sun Microsystems Inc. D:\sun\Java\jdk1.6.0_03\jre
[07/nov/2007:18:35:03 CET] IMQ_HOME=D:\sun\AppServer\imq
[07/nov/2007:18:35:03 CET] IMQ_VARHOME=D:\sun\AppServer\domains\domain1\imq
[07/nov/2007:18:35:03 CET] Windows XP 5.1 x86 t1 (1 cpu) pepepc
[07/nov/2007:18:35:03 CET] Java Heap Size: max=506816k, current=46944k
[07/nov/2007:18:35:03 CET] Arguments: -port 7676 -name imqbroker -imqhome D:\Sun\AppServer\imq\bin\.. -varhome D:/sun/AppServer/domains/domain1\imq -useRmiRegistry -rmiRegistryPort 8686
[07/nov/2007:18:35:04 CET] [B1060]: Loading persistent data...
[07/nov/2007:18:35:04 CET] Using built-in file-based persistent store: D:\sun\AppServer\domains\domain1\imq\instances\imqbroker\
[07/nov/2007:18:35:04 CET] [B1189]: Cluster Service feature is not available
[07/nov/2007:18:35:04 CET] [B1039]: Broker "imqbroker@t1:7676" ready.
MQJMSRA_EB1101: run:EMBEDDED broker started with code =0
MQJMSRA_RA1101: SJSMQ JMS ResourceAdaapter configuration=
raUID =null
brokerType =EMBEDDED
brokerInstanceName =imqbroker
brokerBindAddress =null
brokerPort =7676
brokerHomeDir =D:\Sun\AppServer\imq\bin\..
brokerVarDir =D:/sun/AppServer/domains/domain1\imq
brokerJavaDir =D:/sun/Java/jdk1.6.0_03
brokerArgs =null
brokerStartTimeout =60000
adminUsername =admin
adminPassFile =E:\tempWin\asmq21980.tmp
useJNDIRmiServiceURL =true
rmiRegistryPort =8686
startRmiRegistry =false
useSSLJMXConnector =true
brokerEnableHA =false
clusterId =null
brokerId =null
jmxServiceURL =null
dbType =null
dbProps ={}
dsProps ={}
ConnectionURL =
UserName =guest
ReconnectEnabled =true
ReconnectInterval =5000
ReconnectAttempts =3
AddressListBehavior =RANDOM
AddressListIterations =3
InAppClientContainer =false
InClusteredContainer =false
GroupName =null
MQJMSRA_RA1101: start:SJSMQ JMSRA Connection Factory Config={imqOverrideJMSPriority=false, imqConsumerFlowLimit=1000, imqOverrideJMSExpiration=false, imqAddressListIterations=3, imqLoadMaxToServerSession=true, imqConnectionType=TCP, imqPingInterval=30, imqSetJMSXUserID=false, imqConfiguredClientID=, imqSSLProviderClassname=com.sun.net.ssl.internal.ssl.Provider, imqJMSDeliveryMode=PERSISTENT, imqConnectionFlowLimit=1000, imqConnectionURL=http://localhost/imq/tunnel, imqBrokerServiceName=, imqJMSPriority=4, imqBrokerHostName=localhost, imqJMSExpiration=0, imqAckOnProduce=, imqEnableSharedClientID=false, imqAckTimeout=0, imqAckOnAcknowledge=, imqConsumerFlowThreshold=50, imqDefaultPassword=guest, imqQueueBrowserMaxMessagesPerRetrieve=1000, imqDefaultUsername=guest, imqReconnectEnabled=false, imqConnectionFlowCount=100, imqAddressListBehavior=PRIORITY, imqReconnectAttempts=3, imqSetJMSXAppID=false, imqConnectionHandler=com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler, imqSetJMSXRcvTimestamp=false, imqBrokerServicePort=0, imqDisableSetClientID=false, imqSetJMSXConsumerTXID=false, imqOverrideJMSDeliveryMode=false, imqBrokerHostPort=7676, imqQueueBrowserRetrieveTimeout=60000, imqSetJMSXProducerTXID=false, imqSSLIsHostTrusted=false, imqConnectionFlowLimitEnabled=false, imqReconnectInterval=5000, imqAddressList=localhost:7676, imqOverrideJMSHeadersToTemporaryDestinations=false}
MQJMSRA_RA1101: SJSMQ JMSRA Started
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat moduleName=Chat-ejb_jar ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:184)
at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:113)
at com.sun.enterprise.server.AbstractManager.load(AbstractManager.java:206)
at com.sun.enterprise.server.ApplicationLifecycle.onStartup(ApplicationLifecycle.java:204)
at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
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 com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 18 more
Registering ad hoc servlet: WebPathPath: context root = "/Chat", path = "/Chat-app-client'
Java Web Start services started for application com.sun.enterprise.appclient.jws.ApplicationContentOrigin@aabc2d registration name=Chat
[email protected]56b4 registration name=Chat, context root=/Chat/Chat-app-client, module name=
, parent=Chat
CORE5021: Application NOT loaded: [Chat]
SMGT0007: Self Management Rules service is enabled
Application server startup complete.
JBISE6013: JavaEEServiceEngine : Java EE Service Engine started successfully.
CORE5024: EJB module [Chat-ejb] unloaded successfully!
DeployedItemRef postDeregistration failed. Load Balancer Monitoring MBeans might be lying around if this application is being load balanced
BPEL service engine started
ADM1064:The upload file at [E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar] exists and will be overwritten.
ADM1006:Uploading the file to:[E:\tempWin\s1astempdomain1server-162970426\Chat-ejb.jar]
deployed with moduleid = Chat-ejb
ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable ejb/Chat-ejb]
endpoint.determine.destinationtype
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
appId=Chat-ejb moduleName=D__sun_AppServer_domains_domain1_applications_j2ee-modules_Chat-ejb ejbName=publicarBean
LDR5004: UnExpected error occured while creating ejb container
javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:485)
at com.sun.ejb.containers.BaseContainer.setupEnvironment(BaseContainer.java:2628)
at com.sun.ejb.containers.BaseContainer.<init>(BaseContainer.java:629)
at com.sun.ejb.containers.StatelessSessionContainer.<init>(StatelessSessionContainer.java:163)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:515)
at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:490)
at com.sun.enterprise.server.EJBModuleLoader.load(EJBModuleLoader.java:158)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:219)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:174)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleDeployed(StandAloneEJBModulesManager.java:406)
at com.sun.enterprise.server.StandAloneEJBModulesManager.moduleEnabled(StandAloneEJBModulesManager.java:500)
at com.sun.enterprise.admin.event.AdminEventMulticaster.invokeModuleDeployEventListener(AdminEventMulticaster.java:960)
at com.sun.enterprise.admin.event.AdminEventMulticaster.handleModuleDeployEvent(AdminEventMulticaster.java:941)
at com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:448)
at com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:160)
at com.sun.enterprise.admin.server.core.AdminNotificationHelper.sendNotification(AdminNotificationHelper.java:128)
at com.sun.enterprise.admin.server.core.ConfigInterceptor.postInvoke(ConfigInterceptor.java:109)
at com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:97)
at $Proxy1.invoke(Unknown Source)
at com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at com.sun.enterprise.admin.jmx.remote.server.callers.InvokeCaller.call(InvokeCaller.java:56)
at com.sun.enterprise.admin.jmx.remote.server.MBeanServerRequestHandler.handle(MBeanServerRequestHandler.java:142)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.processRequest(RemoteJmxConnectorServlet.java:109)
at com.sun.enterprise.admin.jmx.remote.server.servlet.RemoteJmxConnectorServlet.doPost(RemoteJmxConnectorServlet.java:180)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
Caused by: javax.naming.NameNotFoundException
at com.sun.enterprise.naming.TransientContext.resolveContext(TransientContext.java:255)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:178)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:61)
at com.sun.enterprise.naming.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:98)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:309)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:469)
... 54 more
CORE5020: Error while loading ejb module
{code}
I know it is very large. I think the error it is in this line.
{code}
NAM0008 : Invalid Destination: jndi/Topic for java:comp/env/jms/Topic
EJB5090: Exception in creating EJB container [javax.naming.NamingException [Root exception is javax.naming.NameNotFoundException]]
{code}
also I am going to put the code.
file PublicarBean.java
{code}
package org.pepes;
import com.sun.tools.ws.processor.model.java.JavaArrayType;
import javax.annotation.Resource;
import javax.ejb.SessionContext;
import javax.ejb.Stateless;
import javax.jms.ConnectionFactory;
import javax.jms.QueueConnectionFactory;
import javax.jms.Topic;
import javax.naming.NamingException;
* @author pepes
@Stateless(mappedName="ejb/publicar")
public class publicarBean implements org.pepes.publicarRemote {
/** Creates a new instance of publicarBean */
@Resource(name="jms/QueueConnectionFactory")
private QueueConnectionFactory connectionFactory;
@Resource(name="jms/Topic", mappedName="jndi/Topic")
private Topic topic;
private javax.naming.InitialContext ctx;
public publicarBean() {
public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException {
try {
javax.naming.InitialContext ctx = new javax.naming.InitialContext();
this.connectionFactory = (javax.jms.QueueConnectionFactory)ctx.lookup("jms/QueueConnectionFactory");
this.topic = (javax.jms.Topic)ctx.lookup("jms/Topic");
javax.jms.Connection connection = this.connectionFactory.createConnection();
javax.jms.TopicSession ts = (javax.jms.TopicSession)connection.createSession(false, javax.jms.Session.AUTO_ACKNOWLEDGE);
javax.jms.TopicPublisher tp = ts.createPublisher(this.topic);
javax.jms.TextMessage msg = ts.createTextMessage();
for (int i = 0; i<3;i++) {
msg.setText("Prueba: " + i);
tp.publish(msg);
catch (javax.jms.JMSException jmex) {
throw jmex;
{code}
the file publicarRemote.java
{code}
package org.pepes;
import javax.ejb.Remote;
* This is the business interface for publicar enterprise bean.
@Remote
public interface publicarRemote {
public void creaMensaje() throws javax.naming.NamingException , javax.jms.JMSException;
{code}
file mensaje.java
{code}
package org.pepes;
import javax.annotation.Resource;
import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.ejb.MessageDrivenContext;
import javax.jms.Message;
import javax.jms.MessageListener;
* Entity class Mensaje
* @author pepes
@MessageDriven(mappedName = "jms/Mensaje", activationConfig = {
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge"),
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
public class Mensaje implements MessageListener {
/** Creates a new instance of Mensaje */
@Resource
private MessageDrivenContext mdc;
public Mensaje() {
public void onMessage(Message message) {
javax.jms.TextMessage msg = null;
try {
if (message instanceof javax.jms.TextMessage) {
msg = (javax.jms.TextMessage) message;
System.out.println(msg.getText());
} else {
System.out.println("Message of wrong type: "
+ message.getClass().getName());
} catch (javax.jms.JMSException e) {
e.printStackTrace();
mdc.setRollbackOnly();
} catch (Throwable te) {
te.printStackTrace();
{code}
the file prueba.jsp
{code}
<%@page contentType="text/html"%>
<%@page pageEncoding="UTF-8"%>
<%--
The taglib directive below imports the JSTL library. If you uncomment it,
you must also add the JSTL library to the project. The Add Library... action
on Libraries node in Projects view can be used to add the JSTL 1.1 library.
--%>
<%--
<%@taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c"%>
--%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JSP Page</title>
</head>
<body>
<h1>JSP Page</h1>
<%--
This example uses JSTL, uncomment the taglib directive above.
To test, display the page like this: index.jsp?sayHello=true&name=Murphy
--%>
<%--
<c:if test="${param.sayHello}">
<!-- Let's welcome the user ${param.name} -->
Hello ${param.name}!
</c:if>
--%>
<%
try {
javax.naming.InitialContext ctx = new javax.naming.InitialContext();
org.pepes.publicarRemote publisher = (org.pepes.publicarRemote)ctx.lookup("ejb/publicar");
if (publisher==null) {
System.out.println("INFO: Es null");
else {
System.out.println("INFO: No es null");
publisher.creaMensaje();
} catch (javax.naming.NamingException ex) {
System.out.println("ERROR naming: " + ex.getMessage());
catch (javax.jms.JMSException jmex) {
System.out.println("ERROR jms: " + jmex.getMessage());
catch (java.lang.NullPointerException nullex) {
System.out.println("ERROR null: " + nullex.getMessage());
%>
</body>
</html>
{code}
I think the problem is because i don't put destination address. if it is so, the true where do I put this address?. if not where is the problem?
I hope your help.
Thanks you in advanced.Hi,
Did you create your destinations in your application server? It seems that the destinations such as topics and queues are not created. First you should create them and then start using them.
For example, in here, it says that jndi/Topic is not valid. To check if the destinations are valid or not; you can do it either through the graphical user interface or the command line console.
Maybe you are looking for
-
I am not able to answer the call from i phone 5 after updating ios7 can u assist me to solve
after updating while ringing call not able to answer i restart and reset but still some call scren is hanging not able to answer can u assist me what to do next please
-
Do anyone know what this exception is or when can it occur, java.lang.SecurityException: Authentication for user system denied in realm wl_realm at weblogic.security.acl.Realm.authenticate(Realm.java:212) at weblogic.security.acl.Realm.getAuthenticat
-
How to install IOS 5 after UDID registration
Hi, I`ve a question. A friend registered my UDID on his developer account. No he isn´t at home (for the weekend) and I dont now how to get the software IOS 5, neither, how to install the software. Please, could someone help me? THX P.S.: sorry for my
-
Modifying the Default Result Set on the Results Tab of the SQLWorksheet
I have found the previous posts indicating that the default result set size is 50, that it is not currently able to be modified and (good news) that an enhancement will be coming to correct this. I thought I would give my two cents on how this option
-
HELP ! A FATAL BUG ! ! ! What`s wrong with the SATA port ? ? ?
My MacBook (MD103) got a serious bug here, PLEASE HELP ME ! I changed my main drive to a Crucial 256GB SSD and memory to Micron 16GB, and I also removed the optical drive. The optical drive has been replaced by the original Toshiba HDD. Then, the que