[JBoss AS 7 Development] - Logging Id's
by Andrig Miller
Andrig Miller [https://community.jboss.org/people/andy.miller] modified the document:
"Logging Id's"
To view the document, visit: https://community.jboss.org/docs/DOC-16810
--------------------------------------------------------------
Logging id ranges for JBoss AS7 i18n message interfaces.
|| %1,3% *Status* ||
| C | = | Complete |
| I | = | In Progress |
| P | = | Merged, but not complete |
| W | = | Waiting Merge |
|| *Range* || *Subsystem
* || *Status
* ||
| *10100 - 10199* | *Transaction* | C |
| *10200 - 10399
* | *Clustering**
* | C |
| *10400 - 10499* | *Connector**
* | C |
| *10500 - 10599* | *CLI (not applicable)
* | N/A |
| *10600 - 10699* | *Controller Client* | C |
| *10700 - 10799*, 18500 - 18699, 18800-18999 | *CMP* | C |
| *10800 - 10899* | *Host Controller (domain packages)* | C |
| *10900 - 10999* | *Host Controller (host packages)* | C |
| *11000 - 11099* | *EE* | C |
| *11100 - 11199* | *Embedded* | C |
| *11200 - 11299* | *JAXRS* | C |
| *11300 - 11399* | *JMX* | C |
| *11400 - 11499* | *JPA* | C |
| *11500 - 11599* | *Logging* | C |
| *11600 - 11699* | *Messaging* | C |
| *11700 - 11799* | *mod_cluster* | C |
| *11800 - 11899* | *Naming* | C |
| *11900 - 11999* | *OSGi* | C |
| *12000 - 12099* | *Process Controller* | C |
| *12100 - 12199* | *Protocol* | C |
| *12200 - 12299* | *Management Client Content* | C |
| *12300 - 12399* | *Platform MBeans* | C |
| *12400 - 12499* | *Threads* | C |
| *13100 - 13199* | *Security* | C |
| *13200 - 13299* | *AppClient* | C |
| *13300 - 13399* | *JDR* | C |
| *14000 - 14099* | *JAXR* | W |
| *14100 - 14599* | *Ejb3* | P |
| *14600 - 14899* | *Controller* | C |
| *14900 - 14999* | *Deployment Repository* | C |
| *15000 - 15099* | *Deployment Scanner* | C |
| *15100 - 15199* | *Domain Management HTTP Interface* | C |
| *15200 - 15299* | *Deployment Management* | C |
| *15300 - 15399* | *Network* | C |
| *15400 - 15499* | *Mail* | C |
| *15500 - 15699* | *Web Services* | C |
| *15700 - 15999*, 18700 - 18799 | *Server* | C |
| *1**6000 - 16099* | *Weld* | C |
| *16100 - 16199* | *EE Deployment* | C |
| *16200 - 16299* | *Configadmin* | C |
| *16300 - 16499* | *Jacorb* | C |
| available block(s) |
|
|
| *17000 - 17099* | *POJO* | C |
| *17100 - 17199* | *Remoting* | W |
| *17200 - 17299* | *SAR* | W |
| *18000 - 18399* | *Web* | C |
| *18400 - 18499* | *Xts* | C |
| 10700 - 10799, *18500 - 18699*, 18800-18999 | *CMP* | W |
| 15700 - 15999, *18700 - 18799* | *Server* | C |
| 10700 - 10799, 18500 - 18699, *18800-18999* | *CMP* | W |
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-16810]
Create a new document in JBoss AS 7 Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
12 years, 1 month
[jBPM Development] - Re: JBPM process sends corrupted JMS Messages
by Fady Magdy
Fady Magdy [https://community.jboss.org/people/fmagdy] created the discussion
"Re: JBPM process sends corrupted JMS Messages"
To view the discussion, visit: https://community.jboss.org/message/721329#721329
--------------------------------------------------------------
Dear Mauricio
Thank you for your reply, I changed the title to be more relevant :) , after some more digging, the error was just a size issue, the problem now Is that the message comes corrupted without errors, so the message.getbody().body() is not able to get the message body so it returns the whole JMS message, the strange thing is that this only happens when the workflow is published, any idea what might be the reason, below is a sample of the message
the send() method is called from within an action handler of a node in a bpmn process
<Envelope><Header xmlns:wsa=" http://schemas.xmlsoap.org/ws/2004/08/addressing http://schemas.xmlsoap.org/ws/2004/08/addressing"><wsa:To>jms:127.0.0.1:1099#queue/ourqueue</wsa:To><jbossesb:java.naming.factory.initial xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">org.jnp.interfaces.NamingContextFactory</jbossesb:java.naming.factory.initial><jbossesb:java.naming.provider.url xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">127.0.0.1:1099</jbossesb:java.naming.provider.url><jbossesb:java.naming.factory.url.pkgs xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">org.jnp.interfaces</jbossesb:java.naming.factory.url.pkgs><jbossesb:destination-type xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">queue</jbossesb:destination-type><jbossesb:destination-name xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">queue/ourqueue</jbossesb:destination-name><jbossesb:specification-version xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">1.1</jbossesb:specification-version><jbossesb:connection-factory xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">ConnectionFactory</jbossesb:connection-factory><jbossesb:persistent xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">true</jbossesb:persistent><jbossesb:acknowledge-mode xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">AUTO_ACKNOWLEDGE</jbossesb:acknowledge-mode><jbossesb:transacted xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">false</jbossesb:transacted><jbossesb:type xmlns:jbossesb=" http://schemas.jboss.com/ws/2007/01/jbossesb http://schemas.jboss.com/ws/2007/01/jbossesb">urn:jboss/esb/epr/type/jms</jbossesb:type><wsa:MessageID>d14e36a2-d5a1-44a8-bc9f-d9fab4c84423</wsa:MessageID></Header><Context /><Body><Content><Key>b3JnLmpib3NzLnNvYS5lc2IubWVzc2FnZS5kZWZhdWx0RW50cnk=</Key><Value><marshalunmarshal><plugin-type>urn:xml/marshalunmarshal/plugin/serialization</plugin-type>rO0ABXQAizxUcmFuc2FjdGlvbj48VHJhbnNhY3Rpb25JZD4zMDg8L1RyYW5zYWN0aW9uSWQ+PFRyYW5zYWN0aW9uTmFtZT5OYW1lPC9UcmFuc2FjdGlvbk5hbWU+PFRyYW5zYWN0aW9uRGF0ZT5udWxsPC9UcmFuc2FjdGlvbkRhdGU+PC9UcmFuc2FjdGlvbj4=</marshalunmarshal></Value></Content></Body><Attachment /><Properties><Property><Key>b3JnLmpib3NzLnNvYS5lc2IubWVzc2FnZS50cmFuc3BvcnQudHlwZQ==</Key><Value>rO0ABX5yAC9vcmcuamJvc3Muc29hLmVzYi5jb21tb24uRW52aXJvbm1lbnQkVHJhbnNwb3J0cwAAAAAAAAAAEgAAeHIADmphdmEubGFuZy5FbnVtAAAAAAAAAAASAAB4cHQAA0pNUw==</Value></Property><Property><Key>amF2YXguam1zLm1lc3NhZ2UucmVkZWxpdmVyZWQ=</Key><Value>rO0ABXNyABFqYXZhLmxhbmcuQm9vbGVhbs0gcoDVnPruAgABWgAFdmFsdWV4cAA=</Value></Property><Property><Key>b3JnLmpib3NzLnNvYS5lc2IubWVzc2FnZS5zb3VyY2U=</Key><Value>rO0ABXQANVBvcnRSZWZlcmVuY2UgPCBqbXM6MTI3LjAuMC4xOjEwOTkjcXVldWUvU1BBUktRdWV1ZSA+</Value></Property><Property><Key>b3JnLmpib3NzLnNvYS5lc2IuZ2F0ZXdheS5vcmlnaW5hbC5xdWV1ZS5uYW1l</Key><Value>rO0ABXQAEHF1ZXVlL1NQQVJLUXVldWU=</Value></Property></Properties></Envelope>
thanks,
fmagdy
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/721329#721329]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month
[jBPM Development] - JBPM process sends corrupted JMS Messages
by Fady Magdy
Fady Magdy [https://community.jboss.org/people/fmagdy] created the discussion
"JBPM process sends corrupted JMS Messages"
To view the discussion, visit: https://community.jboss.org/message/721323#721323
--------------------------------------------------------------
Hi,
We are using jboss SOA Platform, we are trying to use a bpmn process to read some data from a database and send a JMS message containing some text to a queue in the ESB, but the ESB randomly fails to de-sterilize some messages, by debugging we found that some messages arrive at the queue corrupted, this happens only when we publish the workflows at the bpmn server (it works perfectly fine with the process running from in the jboss development studio)
this happens randomly to some messages even if these messages were transmitted correctly before. Any idea what could be the cause of this?
This is the code we use to send the messages
*public* *class* SendJMSMessage {
QueueConnection conn;
QueueSession session;
Queue que;
*public* *void* setupConnection() *throws* JMSException, NamingException
{
Properties properties1 = *new* Properties();
properties1.put(Context.+INITIAL_CONTEXT_FACTORY+,
"org.jnp.interfaces.NamingContextFactory");
properties1.put(Context.+URL_PKG_PREFIXES+,
"org.jboss.naming:org.jnp.interfaces");
properties1.put(Context.+PROVIDER_URL+, "jnp://127.0.0.1:1099");
InitialContext iniCtx = *new* InitialContext(properties1);
Object tmp = iniCtx.lookup("ConnectionFactory");
QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;
conn = qcf.createQueueConnection();
que = (Queue) iniCtx.lookup("queue/ourqueue");
session = conn.createQueueSession(*false*, QueueSession.+AUTO_ACKNOWLEDGE+);
conn.start();
System.+out+.println("Connection Started");
}
*public* *void* stop() *throws* JMSException
{
conn.stop();
session.close();
conn.close();
}
*public* *void* sendAMessage(String msg) *throws* JMSException {
QueueSender send = session.createSender(que);
ObjectMessage tm = session.createObjectMessage(msg);
send.send(tm);
send.close();
}
*public* *void* Send(String msg)
{
SendJMSMessage sm = new SendJMSMessage();
* sm.setupConnection(); sm.sendAMessage(msg);*
* sm.stop();*
* *
*}*
*}*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/721323#721323]
Start a new discussion in jBPM Development at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 1 month