[JBoss Cache] - JBoss Cache manager Failed to Start
by Sandesh Satam
Sandesh Satam [http://community.jboss.org/people/sandesh.satam] created the discussion
"JBoss Cache manager Failed to Start"
To view the discussion, visit: http://community.jboss.org/message/541993#541993
--------------------------------------------------------------
Hi,
Today I have upgraded the Jgroup version to JGroups-2.7.0.GA, and after JBoss restart I am getting following error.
My JBoss version is jboss-5.1.0.GA.
2010-05-10 08:12:53,508 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=HAPartition state=Create
java.lang.NoSuchMethodError: org.jgroups.jmx.JmxConfigurator.registerChannel(Lorg/jgroups/JChannel;Ljavax/management/MBeanServer;Ljava/lang/String;Ljava/lang/String;Z)Lorg/jgroups/jmx/JChannel;
at org.jboss.ha.framework.server.JChannelFactory.registerChannel(JChannelFactory.java:1019)
at org.jboss.ha.framework.server.JChannelFactory.createMultiplexerChannel(JChannelFactory.java:279)
at org.jboss.ha.framework.server.ClusterPartition.createChannel(ClusterPartition.java:299)
at org.jboss.ha.framework.server.ClusterPartition.startService(ClusterPartition.java:363)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.pojoStart(ServiceMBeanSupport.java:216)
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.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
Please help me to resolve this problem.
Thanks and Regards,
Sandesh
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541993#541993]
Start a new discussion in JBoss Cache at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months
[Datasource Configuration] - Realm configuration problems using DataSourceRealm
by Patrick Mingard
Patrick Mingard [http://community.jboss.org/people/Lordsephiroth] created the discussion
"Realm configuration problems using DataSourceRealm"
To view the discussion, visit: http://community.jboss.org/message/541991#541991
--------------------------------------------------------------
Hi,
My name is Patrick, from Switzerland, and I'm new on Java EE and JBoss. I started a few weeks ago to learn how to devlop in Java EE and succeeded in much tests. I first tried to make a small servlet in a WAR archive, then having an EJB-JAR archive as well with entities and stateless session beans, together packaged in EAR archive. Everything is going perfectly well and my testing application, a small currency-change application, is working (add currencies, define currencies rates and conversion).
Now, I'm trying to go a bit further by protecting my servlets with username and password.
First, here is my environment :
JBoss 5.1.0
MyEclipse (but packaging everything using ANT)
JPA / EJB 3
Hypersonic Database (for testing and learning, this DB is fine I guess)
My JNDI env contains this entry (in JMX console, service JNDI view) :
h1. java: Namespace
+- DefaultDS (class: org.jboss.resource.adapter.jdbc.WrapperDataSource)
Now, I try to configure the Realm element. I have to say here that I read a lot of time that context.xml should be place in /META-INF/ directory (here : http://docs.jboss.org/jbossweb/en/html/docs/config/context.html).
All my tests asserts that context.xml is never taken into account when I place it in /META-INF/ but is evaluated when placed in /WEB-INF/. I'm not sure if it is important, but for the rest of my question, consider the context.xml is placed in /WEB-INF/ directory.
Here is the code :
<Context>
<Realm className="org.apache.catalina.realm.DataSourceRealm"
dataSourceName="java:DefaultDS"
userTable="users"
userRoleTable="user_roles"
userNameCol="user_name"
userCredCol="user_pass"
roleNameCol="role_name"
localDataSource="true"
/>
</Context>
And here is the security part of web.xml (rest is mostly servlet mapping) :
<security-constraint>
<display-name>Security constraint for all servlets</display-name>
<web-resource-collection>
<web-resource-name>Protected area</web-resource-name>
<url-pattern>/servlet/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>admin</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>CurrencyManager</realm-name>
<form-login-config>
<form-login-page>/login.jsp</form-login-page>
<form-error-page>/loginerror.jsp</form-error-page>
</form-login-config>
</login-config>
<security-role>
<role-name>admin</role-name>
</security-role>
I also tried using dataSourceName="DefaultDS" or jdbc/DefaultDS or java:comp/env/DefaultDS, I always get the same error when I log in
login.jsp file is perfectly standard and contains :
<form action="j_security_check" method="post">
<table>
<tr>
<td>User name : </td>
<td><input type="text" name="j_username" /></td>
</tr>
<tr>
<td>Password : </td>
<td><input type="password" name="j_password" /></td>
</tr>
<tr>
<td> </td>
<td><input type="submit" value="connect" /></td>
</tr>
</table>
</form>
When I try to log in, I always get this error :
javax.naming.NameNotFoundException: Le Nom java:DefaultDS n'est pas lié à ce context.
Well, the exception message is in french, but it means (java:DefaultDS name is not bound to this context) or close to this.
I guess this problem is due to the fact that the security Realm is placed in the web container context, which has by default no access to the database. I have no problem accessign the database through my entities in my EJB-JAR application. Let me know if i'm wrong.
Fine, I guess I have to make a reference to the database in the context of my web container (I have to say I'm really not used to context and this part of java programming is kind of... obscure.. to not say... annoying).
So my web.xml is modified with this additional lines :
<resource-ref>
<description>The default DS</description>
<res-ref-name>java:DefaultDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
Now the only exception I get is during deployment :
java.lang.RuntimeException: mapped-name is required for java:DefaultDS of deployment testEJB-web.war
Well... let me guess I need a mapped-name attribute in my web.xml.
I made this change :
<resource-ref>
<description>The default DS</description>
<res-ref-name>jdbc/DefaultDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<mapped-name>java:DefaultDS</mapped-name>
</resource-ref>
And I'm back with my first exception stating java:DefaultDS is not bound to this context. I tried to place DefaultDS, java:comp/env/DefaultDS or jdbc/DefaultDS and almost any combining of these possibilities in the res-ref-name, mapped-name and realm name attributes in my files. I always get an exception when I try to log in.
So, let me come to my question : what can I do for this realm configuration ? I'm really stuck now ;)
Last precision : I heard about a jboss-web.xml file in the WEB-INF directory that could replace the web.xml resource configuration and tried some things like :
<jboss-web>
<resource-ref>
<res-ref-name>jdbc/DefaultDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<jndi-name>java:DefaultDS</jndi-name>
</resource-ref>
</jboss-web>
But did not see any message of any kind (exception or info or warn or whatever) stating that my file was parsed by the JBoss server.
Any help would be really appreciated, I'm kind of wasting so much time (almost 4 days entirely for this problem) without solving it.
Thanks, and sorry if I made some language mistakes, I guess my english is not bad, but not perfect either ;)
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541991#541991]
Start a new discussion in Datasource Configuration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months
[JBoss Tools] - JBossToolsRoadmap
by Max Andersen
Max Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the document:
"JBossToolsRoadmap"
To view the document, visit: http://community.jboss.org/docs/DOC-10800
--------------------------------------------------------------
h2. JBoss Tools Road map
This page outlines the focus areas we will be working on for the next major version of JBoss Tools.
This is a work in progress and if you think something is missing/incorrect then please raise it on our mailing list or forums or simply adjust the page if it is a minor correction.
Detailed road map with concrete issues and bug fixes is to be found in our http://jira.jboss.com/jira/browse/JBIDE?report=com.atlassian.jira.plugin.... jira
For the moment this roadmap is split up in three sections, "General", "Web 2.0" and "SOA" to group the functionality according to their main target audience. Even though they are split up in different sections it does not mean they do not overlap, e.g. JBoss AS, Project Archives and Hibernate will all be relevant for SOA even though they are in Web 2.0 and the same goes for jBPM and Drools which are also relevant for Web 2.0 even though they are in SOA. The division is merely to group these according to the focus of the teams that are primarily working on these. Collaboration will be needed ;)
h3. General
Java SDK: Java 6
Eclipse Target is Eclipse 3.6 (Helios)
IDE runtimes: Windows XP/Vista, Linux 32-bit, Linux 64-bit and Mac OS X 32-bit. (Limted by what VPE can run on)
Targeted runtimes: dependent on each module, but should at least cover the same as Targeted/supported platforms.
Example of runtimes: hibernate, drools, jbpm, hornetq, teid, maven aka. the "independent" parts that the tooling can work without
having a full platform for editing configuration files, junit testing etc.
Targeted Platforms for new features: AS 5 and AS 6, EAP/SOA-P/EPP 5.x.
Additional supported platforms that shouldn't break: AS 3.x, AS 4, EAP/SOA-P/EPP 4.x
Phone Home - do a google analytics ping when Eclipse starts (tracks real usage vs downloads and updatesite).
h4. Configuration
http://community.jboss.org/docs/DOC-11195 JbtUpgradeTo3x should be filled in with the user visible changes in configuration/installation.*[INCOMPLETE]*
Support installation of Platforms vs runtimes from inside Eclipse, aka. point to an existing EAP and it should automatically configure
AS and Seam runtime, point to existing EPP and should be the same as EAP + Portal, point to existing SOA-P same as EAP + Drools, jbpm, etc.
Share the logic with the installer, maybe move it all to the plugins and make a welcome screen/dialog on new workspaces ? (how do we avoid being intrusive ?)
All users project and workspace metadata used in JBoss Tools 3.x should be usable, but not necessarily backwards compatible.
Make all "runtime" plugins use the Configure menu for their enablement and where it is possible be compatible with Facets.
h3. Web 2.0
Web 2.0 is focusing around Seam, Portal and related functionality. Note: This does not mean that the features depend on Seam, having a good experience in context of Seam is though the overall goal.
p.s. if anyone has a better name than Web 2.0 - please speak up ;)
h4. JBoss AS
[From last roadmap] many users have been having problems with deploying HAR, SAR, etc. archives in JBT. We should make that easier. Suggested solutions is to look into having a WTP module type for these and/or provide a way to control which suffix (.har,.sar,.esb vs. default .jar) will be used when deploying.
JBoss 6 should be a first class AS adapter.
Introduce grouping of servers to allow for grouped stop/start/deploy...
Make SCP/SSH option complete, considerations: start/stop server via ssh, invoke jmx to prevent deployment of partial deployments.
h4. Project Archives
Support "Make Deployable" on folders.
h4. Hibernate
Support Hibernate 3.2,3.3 and 3.5. [3.6 on hold until expected core API changes settles]
[Moved from last roadmap] Multi-Versioned Hibernate - currently we use the bundled Hibernate jars to load the users classes and execute the queries and code generation. Tying us to a very specific version of Hibernate, we should investigate launching as many of these functionalities in an external process.**
Hibernate error reporting should not be done via the main Error log view
Integrate with Dali for Eclipse 3.6
h4. Seam
Monitor Seam 3 development and see if there are changes needed. Probably espcially with respect to Seamgen.
h3. CDI
Add CDI Validators [Needs prioritized list]
h4. Visual Page Editor
Cover any missing JSF 2 features [needs to be identified]
[From old roadmap] Support CDATA
Recreate DnD feature. *[DONE]*
http://jira.jboss.org/jira/browse/JBIDE-1304 http://jira.jboss.org/jira/browse/JBIDE-1304 - Docbook XML editor (please, look at comments)
http://jira.jboss.org/jira/browse/JBIDE-1600 http://jira.jboss.org/jira/browse/JBIDE-1600 - Template Designer (we need at least documentation how to develop templates)
Add more templates of projects.*[?]*
Because: I think we should give more points to start to our users.
Ensure you can actually install Plugins even though VPE xulrunner is not supported (i.e. Windows 64 users should be able to use all functionallity such as code completion but not the Visual part by using optional dependencies and loading)
Split Richfaces/VPE features into subcomponents so we get a smaller dependency set for the remaining features.
h4. JSF
Missing JSF 2 features. [need to identify]
h4. Metawidget
http://community.jboss.org/docs/DOC-14240 JbtMetawidgetSupport *[INCOMPLETE]*
h4. Portal
Ensure JBoss Portal and GateIn continues to work.
h3. "SOA"
h4. ESB
*??*
h4. WebServices
JAX-WS Web Services: Top Down, Bottum Up
JAX-RS: Bottom up
WS and Rest Testing
h4. Drools
Input needed
h2. Guvnor
input needed
h4. jBPM
Ensure jBPM 3 functionallity is stable/complete
h4. Smooks
Direct Source to Target
WSDL/SOAP Source
ESB Service Routing
EDI Templating
h3. BPEL
Rename or reuse BPEL editor ?
WSDL Editor for BPEL ?
h3. Teeid
Integrate Teeid Designer (modeshape?) into JBoss Tools. Look at overlaps.
Integrate/unify deployment with WTP Server view/functionallity ?
h3. Usability
Error messages, logging, defaults.
h3. Continuous build/Quality
unittests, pmd, coverage, publishing the results
Separate builds out for modules
Use Tycho so both Hudson and developers are using the *same* methods
Make mvn drive the build vs Ant (use Maven ant integration where no other option)
h3. Documentation
Context help for JBoss Tools - http://jira.jboss.org/jira/browse/JBDS-264 http://jira.jboss.org/jira/browse/JBDS-264, http://jira.jboss.org/jira/browse/JBIDE-1886 http://jira.jboss.org/jira/browse/JBIDE-1886
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-10800]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
16 years, 2 months
Re: [jboss-user] [jBPM Development] - JBPM-2537
by Maciej Swiderski
Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion
"JBPM-2537"
To view the discussion, visit: http://community.jboss.org/message/541972#541972
--------------------------------------------------------------
Alejandro Guizar wrote:
>
> I reviewed the patch today. It looks OK; however, since timer expiration is mostly a special case of cancel, expiration, cancellation and any other form of premature task termination can be handled through a single cancel(outcome, state) method. I have attached a new patch to https://jira.jboss.org/jira/browse/JBPM-2537 JBPM-2537. Let me know what you all think.
>
> On a different topic, I am not quite happy with the addition of the TimedActivityBehaviour interface and Execution.signal(String, boolean) method just to deliver a timer expiration signal. It should be possible to do it through the existing ExternalActivityBehavior and Execution.signal(String, Map) by passing a special parameter that indicates the cancellation state ("cancelled", "expired" or any other). I'm going to explore this path next week.
Works fine. Like you changes, they simplify it, so that's great.
I would agree if we are talking only about expiration/cancellation of tasks then perhaps we could skip additional interface. But since there could be some custom activities defined I think there will be a need for distinguishing it (I mean cancel and timeout/expired). In some cases it is important to know if activity was executed manually by signalling or automatically on timeout event.
Looking forward to your exploration results.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/541972#541972]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years, 2 months