[JBoss Tools] - Some Experiences with JBoss Tools, Eclipse Helios and M2E
by Thomas Kriechbaum
Thomas Kriechbaum [http://community.jboss.org/people/Thomas.Kriechbaum] created the discussion
"Some Experiences with JBoss Tools, Eclipse Helios and M2E"
To view the discussion, visit: http://community.jboss.org/message/580245#580245
--------------------------------------------------------------
Hello,
what are your experiences with JBoss Tools (1.1.0..-Beta2 maven-feature, 2.2.0..-beta2 as-feature), Eclipse Helios (3.6.1), JBoss AS 6 Final and M2Eclipse (0.10.2, 0.11.1 wtp-feature)?
At the moment, I'm facing the following problems:
* context root of web-module
* republish after changes
* module name is part of global JNDI name
For testing purposes I have created some maven modules with m2e.
business (root module)
+ business-ear (application.xml is generated)
+ business-core (ejb module containing the EJB implementation)
+ business-services (ejb client view)
+ business-ws (web module containing a WS that references the local EJB)
ticket (root module)
+ ticket-ear (application.xml is generated)
+ ticket-core (ejb module containing the EJB implementation)
+ ticket-services (ejb client view)
*context root of the web-module*
Although business-ear/pom.xml contains a specific context-root, the web-module is only accessible under module-name-version (e.g. business-ws-1.0.0)
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<version>2.4.1</version>
<configuration>
<version>5</version>
<generateApplicationXml>true</generateApplicationXml>
<modules>
<ejbModule>
<groupId>org.foo</groupId>
<artifactId>business-core</artifactId>
</ejbModule>
<webModule>
<groupId>org.foo</groupId>
<artifactId>business-ws</artifactId>
<contextRoot>business-services_v1_0</contextRoot>
</webModule>
</modules>
</configuration>
</plugin>
Do I have to provide some specific settings/configuration in this case?
*republish after changes*
The republishing of JEE modules (e.g. WS-Implementation within the web-module) works only, if I perform a "project > clean" on all maven modules. In this case, all maven modules get redeployed correctly. Otherwise, the server state shortly changes to "republish", but the server does not reload the components (=> service behaviour does not change!).
Do I have to change any Eclipse settings to avoid "project > clean" after any changes?
*module name is part of global JNDI name*
AFAIK, the EAR name is part of the EJBs global JNDI name.
For example:
TicketService - EJB3.x Default Remote Business Interface
ticket-ear/TicketServiceBean/remote-at.logis.was.ticket.TicketService - EJB3.x Remote Business Interface
This global name is used to reference this EJB via injection
@EJB(mappedName="ticket-ear/TicketServiceBean")
private TicketService ticketService;
Within Eclipse, the module's version number is not recognized. But when building the components at command line, the version number is added to the EAR by default (e.g. ticket-ear-1.0.0). Therefore, the mapped-name has to be changed to “ticket-ear-1.0.0/TicketServiceBean” before. From my point of view, it is good to have version numbers to support parallel installation of different versions. But how can I tell Eclipse/M2E/... to use version numbers within my workspace as well?
Thanks,
Thomas
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/580245#580245]
Start a new discussion in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[JBoss Remoting] - LeasePinger, sessionId, jboss messaging
by Mark Torres
Mark Torres [http://community.jboss.org/people/mark_v_torres] created the discussion
"LeasePinger, sessionId, jboss messaging"
To view the discussion, visit: http://community.jboss.org/message/577764#577764
--------------------------------------------------------------
Hi,
We're experiencing intermittent connection issues with jboss messaging.
Client
jboss app server 4.2.3.GA
jboss messaging 1.4.5.GA
jboss remoting 2.2.3.SP3
Server
jboss app server 4.2.3.GA
jboss messaging 1.4.5.GA
jboss remoting 2.2.3.SP3
We've set up an exception listener on the client side that "reconnects" upon failure. However, we do get into situations where the connection becomes dead on the server side, but the exception listener does not fire on the client side.
We're able to recreate the issue locally when we pause the client...
kill -s STOP <pid>
wait till the server detects and disconnects the client, and resume the client
kill -s CONT <pid>
I tried tracing the issue and come across a possible cause...
During the resume, 2 ping threads awake, one for LeasePinger and one for ConnectionValidator
LeasePinger does not set ServerInvoker.INVOKER_SESSION_ID on the requestPayload map, but ConnectionValidator.doCheckConnectionWithLease does.
On the server side, ServerInvoker.invoke, if ServerInvoker.INVOKER_SESSION_ID is not in the requestPayloadMap, the server creates/updates the lease.
I think the issue happens when the LeasePinger thread fires before the ConnectionValidator thread.
Can you please give us insights on how we can overcome this problem.
I attached the remoting-bisocket config on the server side.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/577764#577764]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[jBPM] - JBPM 4.4 - exception recovery
by Yuriy Fuksenko
Yuriy Fuksenko [http://community.jboss.org/people/yfuksenk] created the discussion
"JBPM 4.4 - exception recovery"
To view the discussion, visit: http://community.jboss.org/message/576183#576183
--------------------------------------------------------------
I have a Spring based web application with JBPM embeded.
I defined a workflow, that have a task followed by 3 custom activities:
activity1 - calls webservice
activity2 - sends email
activity3 - sends JMS message
At some point my application calls taskService.finishTask, and those activities will be executed.
What I need, is in a case of error (let say SMTPserver is unreachable or web service is not up):
1. Activity should be retried until it succeed (I understand that a lot of logic could be suggested around this, like retry count, notifications, etc, but I am simplifying this on purpose)
2. Activities that succeeded should not be repeated, i.e. if activity2 fails, activity1 should not be executed again (and this is what happens now if any of those activities throws an exception - I guess it has to do with transaction being rolled back)
So my question is - Is there an easy or at least standard way of doing this in JBPM?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/576183#576183]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months
[Beginner's Corner] - DeploymentExeption in jboss 5.1
by mike tihonchik
mike tihonchik [http://community.jboss.org/people/mike.tihonchik] created the discussion
"DeploymentExeption in jboss 5.1"
To view the discussion, visit: http://community.jboss.org/message/584683#584683
--------------------------------------------------------------
I am getting error on the JBoss 5.1 start up:
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/C:/dev/datatrak/branches/eae_reb
ase/deploy/datatrak.ear/abcfs.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:362)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:322)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:294)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWith
Output.java:234)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53
)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:
403)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileServi
ce.java:308)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://java.sun.com/xml/ns/j2ee}web-a
pp is not bound as a global element.
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:
304)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:
286)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDepl
oyerWithOutput.java:348)
... 34 more
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://java.sun.com/xml/ns/j2ee}web-app is not bound a
s a global element.
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:
401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
... 43 more
I have seen couple of discussions here pertaining to this problem, and most of them suggested changing web.xml file. This is my original web.xml
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee" version="2.3"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http:/java.sun.com/dtd/web-app_2_3.dtd">
<listener>
<listener-class>
org.springframework.web.context.request.RequestContextListener
</listener-class>
</listener>
<servlet>
<servlet-name>springapp</servlet-name>
<servlet-class>com.abcfs.springsupport.ABCDispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet>
<servlet-name>NavServlet</servlet-name>
<servlet-class>com.seqtek.pml.nav.NavServlet</servlet-class>
<init-param>
<param-name>PMLConfigFile</param-name>
<param-value>conf/pml-config.xml</param-value>
</init-param>
<init-param>
<!-- Point back to datatrak dir so that it doesn't default to jboss/server/default/bin -->
<param-name>PMLBaseDir</param-name>
<param-value>C:/dev/datatrak/trunk</param-value>
</init-param>
<init-param>
<param-name>logLevel</param-name>
<param-value>SEVERE</param-value>
</init-param>
<init-param>
<param-name>deleteEventsDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.scheduling.DeleteEventsDaemon</param-value>
</init-param>
<init-param>
<param-name>incrementalServiceDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.pos.IncrementalServiceDaemon</param-value>
</init-param>
<init-param>
<param-name>employeeEventSummaryDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.scheduling.EmployeeEventSummaryDaemon</param-value>
</init-param>
<init-param>
<param-name>autoRunClubAccountDaemon</param-name>
<param-value>com.seqtek.abcfs.dt.pos.AutoRunClubAccountDaemon</param-value>
</init-param>
<init-param>
<param-name>reportDeamon</param-name>
<param-value>com.seqtek.abcfs.dt.reportwizard.ReportDeamon</param-value>
</init-param>
<init-param>
<param-name>reportDeamonThreads</param-name>
<param-value>1</param-value>
</init-param>
<init-param>
<param-name>load-on-startup</param-name>
<param-value>1</param-value>
</init-param>
<load-on-startup>5</load-on-startup>
</servlet>
<servlet>
<servlet-name>SimplePdf</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.common.SimplePdf</servlet-class>
</servlet>
<servlet>
<servlet-name>DatatrakStatus</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.common.DatatrakStatus</servlet-class>
</servlet>
<servlet>
<servlet-name>GatewayListener</servlet-name>
<servlet-class>com.seqtek.abcfs.dt.integration.GatewayListenerServlet</servlet-class>
</servlet>
<servlet>
<servlet-name>dwr-invoker</servlet-name>
<display-name>DWR Servlet</display-name>
<servlet-class>org.directwebremoting.servlet.DwrServlet</servlet-class>
<!--INIT-PARAM = loglevel - The valid values are: FATAL, ERROR, WARN (the default), INFO and DEBUG.-->
<init-param>
<param-name>logLevel</param-name>
<param-value>FATAL</param-value>
</init-param>
<!--INIT-PARAM = debug enables TEST mode should not be used in live deployment (DEVELOPMENT ONLY)
as it could give an attacker a lot of information about the services that you export.-->
<!--
<init-param>
<param-name>debug</param-name>
<param-value>true</param-value>
</init-param>
-->
</servlet>
<servlet-mapping>
<servlet-name>SimplePdf</servlet-name>
<url-pattern>/pdf</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>DatatrakStatus</servlet-name>
<url-pattern>/datatrakstatus</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>GatewayListener</servlet-name>
<url-pattern>/gatewaylistener</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>NavServlet</servlet-name>
<url-pattern>*.pml</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>NavServlet</servlet-name>
<url-pattern>/NavServlet</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>dwr-invoker</servlet-name>
<url-pattern>/dwr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>springapp</servlet-name>
<url-pattern>*.spr</url-pattern>
</servlet-mapping>
<error-page>
<exception-type>java.lang.Throwable</exception-type>
<location>/jsp/errorPage.jsp</location>
</error-page>
<error-page>
<error-code>500</error-code>
<location>/jsp/errorPage.jsp</location>
</error-page>
<taglib>
<taglib-uri>widgets</taglib-uri>
<taglib-location>/jsp/widgets.tld</taglib-location>
</taglib>
</web-app>
I changed it to this:
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
however, problem still exists. Any suggestions????
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/584683#584683]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 3 months