November 2011 - jboss-user - Jboss List Archives

[JBoss Microcontainer] - Re: JBOSS 5.1: ignore persistence.xml in jar file

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] created the discussion "Re: JBOSS 5.1: ignore persistence.xml in jar file" To view the discussion, visit: http://community.jboss.org/message/638316#638316 -------------------------------------------------------------- What about if you just copy pasted the ignore logic from 2.0.10? (and then add those new deployers as separate custom jar) I can see that replacing just vfs-deployers-spi might not be enough. But what about if you change all deployers-* jars? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/638316#638316] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

[Beginner's Corner] - JBoss 4.1 to JBoss 5 Migration - Assembly-Descriptor Error

by Elesh Mistry

Elesh Mistry [http://community.jboss.org/people/eleshcmistry] created the document: "JBoss 4.1 to JBoss 5 Migration - Assembly-Descriptor Error" To view the document, visit: http://community.jboss.org/docs/DOC-17370 -------------------------------------------------------------- Hi All, I am in the process from migrating from JBoss 4.1 to JBoss 5 and on starting the server with the deployed ejb, I get the following error in the server.log : org.xml.sax.SAXException: Element type "assembley-descriptor" must be declared. My jboss.xml has <assembley-descriptor> <security-role> <role-name>AdminUser</role-name> <principal-name>${skjgfksfgksjg}</principal-name> </security-role> </assembley-descriptor> I'd appreciate some help as to what I need to change for the migration to work ... Cheers Elesh -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/docs/DOC-17370] Create a new document in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]

14 years, 4 months

1
0
0 / 0

[JNDI and Naming] - JNDI Lookup fails in JBoss AS 7 [java.naming.CommunicationException]

by Kousik Rajendran

Kousik Rajendran [http://community.jboss.org/people/kousikraj] created the discussion "JNDI Lookup fails in JBoss AS 7 [java.naming.CommunicationException]" To view the discussion, visit: http://community.jboss.org/message/637726#637726 -------------------------------------------------------------- Hi, I have successfully created and deployed a datasource in my jboss as 7. I tested with jboss CLI and I got the success message like [standalone@localhost:9999 /] /subsystem=datasources/data-source=java\:jboss\/datasources\/Test:test-connection-in-pool { "outcome" => "success", "result" => [true] } But, when I try to access the same data source using the java code DataSource ds = null; Context ctx = null; String strDSName = "java:jboss/datasources/Test"; try { Properties env = new Properties(); env.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory"); env.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); env.setProperty("java.naming.provider.url", "jnp://localhost:1099"); ctx = new InitialContext(env); ds = (javax.sql.DataSource) ctx.lookup(strDSName); } catch (Exception e) { e.printStackTrace(); } I am getting this error javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) at javax.naming.InitialContext.lookup(InitialContext.java:392) at c om.aayuwiz.clinic.tests.KousikTests.main(KousikTests.java:42) Caused by: java.net.SocketTimeoutException: Receive timed out at java.net.PlainDatagramSocketImpl.receive0(Native Method) at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136) at java.net.DatagramSocket.receive(DatagramSocket.java:712) at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1272) ... 5 more I have not done any changes to my *standalone.xml* under *\JBOSS_HOME\standalone\configuration* directory. Can someone help me out in this regards please. I have tried many forum threads and lot of blogs in and out of jboss.org sites. I am in a very critical situation to fix this issue ASAP. Thanks in Advance. Please let me know if you need more information. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/637726#637726] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

3
5
0 / 0

[jBPM] - A question about rule task in jBPM5

by Jing Zhang

Jing Zhang [http://community.jboss.org/people/zhangjing2000] created the discussion "A question about rule task in jBPM5" To view the discussion, visit: http://community.jboss.org/message/591973#591973 -------------------------------------------------------------- I noticed that when process instance reachs rule task node, application needs to call ksession.fireAllRules to move process instanct forward. I wonder why need to issue such a call. I think it would be better that when process instance arrived, all rules will be fired automatically, just like when process instance reached a script task, the script will be run automatically. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/591973#591973] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

8
19
0 / 0

[JBoss Tools] - JBoss AS 7.1 Beta1 with JBoss Tools - use web port poller!

by Max Rydahl Andersen

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post: "JBoss AS 7.1 Beta1 with JBoss Tools - use web port poller!" To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/24/jboss-as-71-be... -------------------------------------------------------------- Yesterday JBoss AS team http://www.jboss.org/jbossas/downloads/ released JBoss AS 7.1 Beta1 - the best release ever with some great stuff and an out-of-the-box secured server. We knew that the out-of-the-box secured server would require changes to JBoss Tools to handle it, but it also turns out there is an https://issues.jboss.org/browse/AS7-2772 unforseen incompatibility between the AS 7.1 Beta1 and AS 7.0 Final client jars that we use to talk to the AS server. Thus if you use JBoss AS 7.1 Beta1 with JBoss Tools and start it up without changing anything you will see errors similar to this in the console output of the server: 19:40:43,780 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 64726693 to /127.0.0.1:62248 19:40:43,895 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 69123787 to /127.0.0.1:62249 19:40:44,006 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 190a621a to /127.0.0.1:62250 These are caused from the server seeing our "ping" to the server trying to get an answer to if the server is ready and launched but because of the incompatiblity bug it is resulting in these errors instead. Eventually JBoss Tools will give up and report an error about the server startup not being detected. To avoid seeing these errors and to be able to work with the server even though you secure it, there is a workaround for JBoss Tools. You simply need to change the "Startup Poller" from "JBoss 7 Manager Service" to use "Web Port" instead and disable the Automatic detection of the management port. The details on that is described below. h2. How to workaround AS 7.1 not being recognized In the "Servers" view double click on the server and it should open up the server editor: Note that since JBoss Tools only know about "JBoss 7.0" that is what the default server will be called if you haven't typed in something else. http://community.jboss.org/servlet/JiveServlet/showImage/38-4319-17355/jb... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4319-1735... In here are the settings that need to be changed. 1. Change "Startup Poller" to "Web Port" 2. Remove the checkmark from "Automatically detect" under "Server Ports/Management" 3. Type in '9999' into the Management field. 4. Save (Ctrl+S) the configuration Once you have done that it should look something like this: http://community.jboss.org/servlet/JiveServlet/showImage/38-4319-17356/as... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4319-1735... Now when you start this server we will no longer use the management API to check if the server is running but instead just check if http://localhost:8080 http://localhost:8080 is available. I'm sorry for the trouble and we are working hard on getting it fixed and supported in next milestone of JBoss Tools. You can monitor https://issues.jboss.org/browse/JBIDE-10224 JBIDE-10224 to see the progress on the JBoss Tools side. But do try to still Have Fun, Max -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/community/tools/blog/2011/11/24/jboss-as-71-be...]

14 years, 4 months

1
0
0 / 0

[jBPM] - jBPM5.1 : History Information and Reporting using API

by Sandeep Sapra

Sandeep Sapra [http://community.jboss.org/people/sandeepsapra] created the discussion "jBPM5.1 : History Information and Reporting using API" To view the discussion, visit: http://community.jboss.org/message/637459#637459 -------------------------------------------------------------- I have two queries and pointers/references to them will be a great help to me *1.) History Information :* I understand that history can be logged by using JPAWorkingMemoryDbLogger logger = new JPAWorkingMemoryDbLogger(ksession); and the same is working as required. *Ques :* How to retreive the information which is logged using API ? Any example. I read in documentation that it is using the Process Event Listener. But does it work? *2.) Reporting :* Reports for the process can be seen in the jBPM console. But I need to develop mine using APIs *Ques:* Any reference for the same? Regards, Sandeep Sapra -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/637459#637459] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

3
9
0 / 0

[JBoss Tools] - JBoss AS 7.1 Beta1 with JBoss Tools - use web port poller!

by Max Rydahl Andersen

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] created the blog post: "JBoss AS 7.1 Beta1 with JBoss Tools - use web port poller!" To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/24/jboss-as-71-be... -------------------------------------------------------------- Yesterday JBoss AS team http://www.jboss.org/jbossas/downloads/ released JBoss AS 7.1 Beta1 - the best release ever with some great stuff and an out-of-the-box secured server. We knew that the out-of-the-box secured server would require changes to JBoss Tools to handle it, but it also turns out there is an https://issues.jboss.org/browse/AS7-2772 unforseen incompatibility between the AS 7.1 Beta1 and AS 7.0 Final client jars that we use to talk to the AS server. Thus if you use JBoss AS 7.1 Beta1 with JBoss Tools and start it up without changing anything you will see errors similar to this in the console output of the server: 19:40:43,780 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 64726693 to /127.0.0.1:62248 19:40:43,895 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 69123787 to /127.0.0.1:62249 19:40:44,006 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 190a621a to /127.0.0.1:62250 These are caused from the server seeing our "ping" to the server trying to get an answer to if the server is ready and launched but because of the incompatiblity bug it is resulting in these errors instead. Eventually JBoss Tools will give up and report an error about the server startup not being detected. To avoid seeing these errors and to be able to work with the server even though you secure it, there is a workaround for JBoss Tools. You simply need to change the "Startup Poller" from "JBoss 7 Manager Service" to use "Web Port" instead and disable the Automatic detection of the management port. The details on that is described below. h2. How to workaround AS 7.1 not being recognized In the "Servers" view double click on the server and it should open up the server editor: Note that since JBoss Tools only know about "JBoss 7.0" that is what the default server will be called if you haven't typed in something else. http://community.jboss.org/servlet/JiveServlet/showImage/38-4319-17355/jb... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4319-1735... In here are the settings that need to be changed. 1. Change "Startup Poller" to "Web Port" 2. Remove the checkmark from "Automatically detect" under "Server Ports/Management" 3. Type in '9999' into the Management field. Once you have done that it should look something like this: http://community.jboss.org/servlet/JiveServlet/showImage/38-4319-17356/as... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4319-1735... Now when you start this server we will no longer use the management API to check if the server is running but instead just check if http://localhost:8080 http://localhost:8080 is available. I'm sorry for the trouble and we are working hard on getting it fixed and supported in next milestone of JBoss Tools. You can monitor https://issues.jboss.org/browse/JBIDE-10224 JBIDE-10224 to see the progress on the JBoss Tools side. But do try to still Have Fun, Max -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/community/tools/blog/2011/11/24/jboss-as-71-be...]

14 years, 4 months

1
0
0 / 0

[JBoss Microcontainer] - Re: JBOSS 5.1: ignore persistence.xml in jar file

by Ales Justin

Ales Justin [http://community.jboss.org/people/alesj] created the discussion "Re: JBOSS 5.1: ignore persistence.xml in jar file" To view the discussion, visit: http://community.jboss.org/message/607218#607218 -------------------------------------------------------------- Make sure the right "ignore" deployer is present. And then the jboss-ignore.txt should be placed into core.jar/META-INF/. Or you could move core.jar to .ear/lib -- since it's only a lib now, not a real EE sub-deployment, and have it excluded from .ear/META-INF/jboss-ignore.txt. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/607218#607218] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

3
7
0 / 0

Re: [jboss-user] [JBoss Tools] - Will JBoss Tools run on the final Eclipse 3.7 Indigo ?

by Max Rydahl Andersen

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] commented on "Will JBoss Tools run on the final Eclipse 3.7 Indigo ?" To view all comments on this blog post, visit: http://community.jboss.org/community/tools/blog/2011/06/21/will-jboss-too... -------------------------------------------------- p.s. workaround is to use "Web poller" in server configuration instead of management tools. --------------------------------------------------

14 years, 4 months

1
0
0 / 0

Re: [jboss-user] [JBoss Tools] - Will JBoss Tools run on the final Eclipse 3.7 Indigo ?

by Max Rydahl Andersen

Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] commented on "Will JBoss Tools run on the final Eclipse 3.7 Indigo ?" To view all comments on this blog post, visit: http://community.jboss.org/community/tools/blog/2011/06/21/will-jboss-too... -------------------------------------------------- AS 7 Beta 1 client libs are incompatible with AS 7.0 - was discovered earlier today and reported at https://issues.jboss.org/browse/AS7-2772 https://issues.jboss.org/browse/AS7-2772 Thus if we use the beta1 jars we will be incompatible with AS 7.0 - can't work with both in the current setup. We are looking at what options we have. You can track our progress on https://issues.jboss.org/browse/JBIDE-10224 https://issues.jboss.org/browse/JBIDE-10224 --------------------------------------------------

14 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user November 2011