[JBoss Messaging] - Re: JBoss Messaging clustering
by 143564
Hi,
- Queue and Topic examples ran well
- Getting exceptions while trying to run the other(Queue Failover, mdb etc.) examples.
- When I shut down the Node1 server
- Queue and Topic examples ran well
- Getting exceptions while trying to run the other(Queue Failover, mdb etc.) examples.
I get following error when i execution the distributed-queue
compile:
run:
[java] Distributed queue /queue/testDistributedQueue exists
[java] java.lang.RuntimeException: Assertion failed, 2 == 2
[java] at org.jboss.example.jms.common.ExampleSupport.assertNotEquals(ExampleSupport.java:85)
[java] at org.jboss.example.jms.distributedqueue.DistributedQueueExample.example(DistributedQueueExample.java:83)
[java] at org.jboss.example.jms.common.ExampleSupport.run(ExampleSupport.java:147)
[java] at org.jboss.example.jms.distributedqueue.DistributedQueueExample.main(DistributedQueueExample.java:167)
[java]
[java] #####################
[java] ### FAILURE! ###
[java] #####################
BUILD FAILED
/opt/jboss-messaging-1.4.0.SP3/examples/distributed-queue/build.xml:85: Java returned: 1
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133893#4133893
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133893
18 years, 1 month
[JBoss Portal] - How To create fields in a CMS
by kruibal
I was researching the topic of adding content in JBOSS portal. I found that from the option CMS -> Create file, I can add content which has textfields to enter description, title and the file name, plus a textarea, which can use a WYSIWIG editor to fill the body of the content.
While this is useful, I need to create a file like that but with some custom fields, something like creating a template structure with liferay or define one type of content with drupal. What I need is to know how to create a file which contains fields to fill that are defined by me.
For example, I need that in addition to the title and description, the content that is being created has a field where they can enter a date, you have a checkbox and add another textarea to enter comments (in addition to define whether they are required or optional) . Is there any way to accomplish this?
Sorry for my English and already many thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133892#4133892
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133892
18 years, 1 month
[JBossWS] - Problems with multipart/related responses
by boopet
Hi everyone,
we have created a JBossWS Client with version 2.0.1 consuming a Axis2 webservice, that is sending its responses in multipart/related format.
Everything works fine when testing with SoapUi. but when calling a method with the JBoss client, we get this error message:
Caused by: java.lang.IllegalArgumentException: multipart/related stream invalid, no root part was found
| at org.jboss.ws.core.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:164)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:228)
| at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:84)
| at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)
I have already tried with the libraries from 2.0.3. But this causes the same problems.
This is the response received from Axis2 Server:
HTTP/1.1 200 OK
| Date: Tue, 04 Mar 2008 09:41:08 GMT
| Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217; type="application/xop+xml"; start="0.urn:uuid:98BB2CA94931E2B9C21204623668218@apache.org"; start-info="text/xml"
| Server: Apache-Coyote/1.1
| Transfer-Encoding: chunked
|
| --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217
| Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
| Content-Transfer-Encoding: binary
| Content-ID: <0.urn:uuid:98BB2CA94931E2B9C21204623668218@apache.org>
|
| <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns:loadEloFileUrlResponse xmlns:ns="http://eloservice.giag.com"><ns:return>http://some_url_notshown</ns:return></ns:loadEloFileUrlResponse></soapenv:Body></soapenv:Envelope>
| --MIMEBoundaryurn_uuid_98BB2CA94931E2B9C21204623668217--
Did somebody have similar problems?
If this is a known issue please let me know.
Thanks for your help!
Regards,
Norbert
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133887#4133887
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133887
18 years, 1 month
[JBoss Messaging] - Re: messages stuck in queues
by martin.wickus
Tim Fox's reply inline:
anonymous wrote : >
|
| >
| > Just a bit of background.
| >
| > We've been running with EAP 4.2 and JBM 1.4.0.GA for a while. I'm quite
| > aware this is not the environment supported by Red Hat, but this is what
| > we have and we've been on a steady path to becoming 100% compliant: We
| > were running JBoss 4.2.1 GA and ActiveMQ, replaced ActiveMQ with JBM and
| > then took on Red Hat support. At this point we upgraded to JBoss EAP 4.2
| > (but kept JBM in place). I've been working on a branch running JBoss EAP
| > 4.3 and the default configured JBM 1.4.0.SP3, however this is not yet
| > deployed into production. We had a couple of issue with JBM 1.4.0.GA (or
| > really JBoss Remoting I should say) which was sorted out by using a
| > slightly modified version of the remoting-biscoket-service.xml that
| > bundles with JBM 1.4.0.SP3. Please note we were still at this time using
| > the JBM 1.4.0.GA libraries. However, as JBM 1.4.0.SP3 is the stable
| > release, we heeded a suggestion by Red Hat and decided to upgrade.
| > That's when the problem occurred.
| >
| > As already mentioned, I'm going to run a couple of experiments today to
| > see whether I can narrow down the reason for the problem. I'm not yet
| > convinced it is a bug in JBM. My reasons are:
|
| I don't want to speculate too much at this point, but 1.4.0.SP3 is our
| most highly tested JBM release - having gone through rigorous load and
| soak test with our QA department before it was allowed to go in the EAP.
| So a bug of this magnitude slipping through the net would surprise me,
| although, of course we can't rule this out.
|
| >
| > 1. We used the same JBM database schema from 1.4.0.GA.
| > This did not give
| > any problems when we tested in the dev environments. However, after more
| > careful inspection of the SQL in oracle-persistence.sql I noticed a
| > couple of changes were in place (e.g. new index, delete_message sql
| > script switched order of parameters arround ... this could be problem is
| > JBM is not using name parameters, but positional,
| > supports_blob_on_select flag, composite primary key for JBM_MSG_REF
| > changed declaration order for composite columns, etc). I don't know if
| > this could be the cause of our problem and the old schema certainly
| > worked fine for us in the development environment, but I'll try and use
| > the new schema and see whether that makes a difference.
|
| Yes the schema has changed between GA and SP3. It is critical that the
| old database is dropped before installing the new version, otherwise all
| kinds of strange problems might occur.
|
| >
| > 2. The following customisations were dropped from
| > connection-factories-service.xml
| > Setting attribute PrefetchSize to 1000.
| > Setting attribute SlowConsumers to false.
|
| This may cause behavioural differences w.r.t message consumption.
|
| >
| > 3. Were PostOffice was marked as not clustered before, it was deployed
| > as clustered this time round (default from bundled
| > oracle-persistence-service.xml). Do not anticipate this to be a problem
| > since we are running just a single node.
|
| Best to set clustered = false though if you are running a single node.
|
| >
| > 4. Using EAP 4.3 build for JBR 2.2.2.SP4 --- Implementation-Version:
| > 4.3.0.GA (build: VNTag=JBPAPP_4_3_0_GA date=200801031548) instead of the
| > BREW library. I reckoned the EAP 4.3 one would be most stable since
| > tested by Red Hat. However, perhaps there are modifications specific to
| > EAP 4.3.
|
| Yes, that is a possibility. The EAP versions of a product and the
| community version of the product can and do diverge sometimes, this is
| mainly because we can provide bug fixes etc on the EAP version that's
| not available on the free version until a later date. Not sure if this
| applies to those versions of JBR but it's possibility. To be safe, it's
| always wise not to mix and match version from the EAP and community
| versions.
|
| If you want to run JBM 1.4.0.SP3 inside EAP 4.2, you should obtain the
| JBM jar from the download on the labs site:
|
| http://labs.jboss.org/jbossmessaging/downloads/
|
| And the JBoss Remoting version should be obtained from here:
|
| http://repository.jboss.com/jboss/remoting/2.2.2.SP4-brew/lib/
|
| To summarise, in order to upgrade versions, you should follow the
| following steps:
|
| 1) Drop the old database
| 2) Obtains the distro and jars from above urls.
| 3) Replace jboss-messaging.jar in the app server in the
| server/messaging/lib directory with the one inside the distro. (assuming
| you have named your server profile "messaging")
| 4) Replace jboss-remoting.jar in the app server in the
| server/messaging/lib directory with the one download from the above url.
| 5) Replace all *.xml files in
| server/messaging/deploy/jboss-messaging.sar/ with their equivalents from
| the JBM distro you downloaded.
| 6) Re-apply any custom changes (e.g. prefetchSize, slowConsumers etc)
| that you made in your previous installation to those files. (There have
| been config changes between GA and SP3)
| 7) If you are using ServiceBindingManager service in JBoss AS, update
| the JBM remoting configuration section in the SBM config to exactly
| reflect the new JBR config.
| 8) For every client that connects to JBM, need to update make sure the
| new jboss-messaging-client.jar and new jboss-remoting.jar that you
| downloaded are on the client classpath *before* any other jars.
|
| As you can see it's a bit fiddly, but a simple replace the jars almost
| certainly won't work.
|
| Alternatively, If you are willing to recreate your server profile, you
| could just the automated install instructions from the user guide. But
| I'm not sure if you're able to do that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133886#4133886
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133886
18 years, 1 month
[JBoss Messaging] - Re: messages stuck in queues
by martin.wickus
We rolled back to the old libraries and config files and all is working fine. However, for those following this thread, would like to point out I'm not convinced this is a bug in JBM. We might have made a couple of mistakes during out deployment. Email thread posted for public interest:
anonymous wrote : Just a bit of background.
|
| We've been running with EAP 4.2 and JBM 1.4.0.GA for a while. I'm quite aware this is not the environment supported by Red Hat, but this is what we have and we've been on a steady path to becoming 100% compliant: We were running JBoss 4.2.1 GA and ActiveMQ, replaced ActiveMQ with JBM and then took on Red Hat support. At this point we upgraded to JBoss EAP 4.2 (but kept JBM in place). I've been working on a branch running JBoss EAP 4.3 and the default configured JBM 1.4.0.SP3, however this is not yet deployed into production. We had a couple of issue with JBM 1.4.0.GA (or really JBoss Remoting I should say) which was sorted out by using a slightly modified version of the remoting-biscoket-service.xml that bundles with JBM 1.4.0.SP3. Please note we were still at this time using the JBM 1.4.0.GA libraries. However, as JBM 1.4.0.SP3 is the stable release, we heeded a suggestion by Red Hat and decided to upgrade. That's when the problem occurred.
|
| As already mentioned, I'm going to run a couple of experiments today to see whether I can narrow down the reason for the problem. I'm not yet convinced it is a bug in JBM. My reasons are:
|
| 1. We used the same JBM database schema from 1.4.0.GA. This did not give any problems when we tested in the dev environments. However, after more careful inspection of the SQL in oracle-persistence.sql I noticed a couple of changes were in place (e.g. new index, delete_message sql script switched order of parameters arround ... this could be problem is JBM is not using name parameters, but positional, supports_blob_on_select flag, composite primary key for JBM_MSG_REF changed declaration order for composite columns, etc). I don't know if this could be the cause of our problem and the old schema certainly worked fine for us in the development environment, but I'll try and use the new schema and see whether that makes a difference.
|
| 2. The following customisations were dropped from connection-factories-service.xml
| Setting attribute PrefetchSize to 1000.
| Setting attribute SlowConsumers to false.
|
| 3. Were PostOffice was marked as not clustered before, it was deployed as clustered this time round (default from bundled oracle-persistence-service.xml). Do not anticipate this to be a problem since we are running just a single node.
|
| 4. Using EAP 4.3 build for JBR 2.2.2.SP4 --- Implementation-Version: 4.3.0.GA (build: VNTag=JBPAPP_4_3_0_GA date=200801031548) instead of the BREW library. I reckoned the EAP 4.3 one would be most stable since tested by Red Hat. However, perhaps there are modifications specific to EAP 4.3.
|
| PS. Clients were using the following libraries:
| JBM: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548). This taken from EAP 4.3\client
| JBR: Implementation-Version: 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200801031548). This taken from EAP 4.3\client
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4133885#4133885
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4133885
18 years, 1 month