[JBoss JIRA] Created: (AS7-757) Provide an operation to distinguish domain & standalone
by Heiko Braun (JIRA)
Provide an operation to distinguish domain & standalone
-------------------------------------------------------
Key: AS7-757
URL: https://issues.jboss.org/browse/AS7-757
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
The console bootstraps form the domain model. It automatically decides to either launch the standalone or domain view. Currently we are checking for a top level "subsystem" element which only exists in standalone mode:
{
[INFO] "operation" => "read-children-names",
[INFO] "child-type" => "subsystem",
[INFO] "address" => []
[INFO] }
However this operation logs an error on the server side when running the domain mode:
[Host Controller] 15:40:15,052 WARN [org.jboss.as.controller] (HttpManagementService-threads - 9) operation ("read-children-names") failed - address: ([]): org.jboss.as.controller.OperationFailedException
[Host Controller] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadChildrenNamesOperationHandler.execute(GlobalOperationHandlers.java:304)
[Host Controller] at org.jboss.as.domain.controller.operations.ReadChildrenNamesHandler.execute(ReadChildrenNamesHandler.java:65)
In order to cleanup this bootstrap procedure and to remove the server side error, a custom operation to distinguish the two execution modes would be helpful.
i.e.
:get-meta-data()
{
"mode" => "standalone",
"api-version" => "1.0",
"some" => "other value"
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBMESSAGING-1849) Byte messages redelivered incorrectly if DefaultRedeliveryDelay=0 used
by Doug Grove (JIRA)
Byte messages redelivered incorrectly if DefaultRedeliveryDelay=0 used
----------------------------------------------------------------------
Key: JBMESSAGING-1849
URL: https://issues.jboss.org/browse/JBMESSAGING-1849
Project: JBoss Messaging
Issue Type: Bug
Components: Messaging Core
Affects Versions: 1.4.7.GA
Reporter: Doug Grove
Priority: Minor
Attachments: test-queue-service.xml
If DefaultRedeliveryDelay is set to 0 in messaging-service.xml (which is the default value) and the first delivery attempt fails, then all subsequent redeliveries (up to DefaultMaxDeliveryAttempts) are wrong. The result in redelivery is that the byte array returned from BytesMessage.readBytes(byte[]) contains only zeros (the length of the array is correct). Setting DefaultRedeliveryDelay to a value of 1 produces the expected behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBSER-126) MetadataSerializationError by StackOverflowError writing Serializable objects that have writeReplace() and readResolve() implemented
by Axel Großmann (JIRA)
MetadataSerializationError by StackOverflowError writing Serializable objects that have writeReplace() and readResolve() implemented
------------------------------------------------------------------------------------------------------------------------------------
Key: JBSER-126
URL: https://issues.jboss.org/browse/JBSER-126
Project: JBoss Serialization
Issue Type: Bug
Affects Versions: 1.0.3 GA
Environment: Mac OS X 10.6.7 Java 1.6.0_24-b07-334
Reporter: Axel Großmann
Assignee: Clebert Suconic
We're experiencing MetadataSerializationError caused by StackOverflowError when we're trying to write objects of classes that
* implement Serializable
* have writeReplace() and readResolve() implemented and use _objects of the same class_ as replacement
* hold member object of private inner class implementing Serializable as well
(!) Please have a look at the attached JUnit test - it replays the problem nicely.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBRULES-1908) updated Drools docs content from SOA 4.2.CP03 Rules Guide
by Darrin Mison (JIRA)
updated Drools docs content from SOA 4.2.CP03 Rules Guide
---------------------------------------------------------
Key: JBRULES-1908
URL: https://jira.jboss.org/jira/browse/JBRULES-1908
Project: JBoss Drools
Issue Type: Task
Security Level: Public (Everyone can see)
Components: drools-docs-expert
Reporter: Darrin Mison
Assignee: Mark Proctor
I revised the language of the "Insertion" section while fixing a couple of reported grammatical errors for the 4.2.CP03 SOA Rules Guide.
The original language is the same in: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/soa_tags/4.3.0.FP01_B... , so these changes would also apply to the most recent docs.
Updated content below, the section ids are different but you get the idea ;-)
<section id="sect-JBoss_Rules_Reference_Manual-WorkingMemory_and_StatefulStateless_Sessions-Insertion">
<title>Insertion</title>
<para>
<firstterm>Insertion</firstterm> is the act of telling the WorkingMemory about the facts.
</para>
<important>
<para>
In many Expert Systems the term used for this concept is
<firstterm>assert</firstterm> or <firstterm>assertion</firstterm>.
However as the keyword <methodname>assert</methodname> is already used
in many languages, Drools uses the keyword & term <methodname>insert</methodname>.
You will often encounter these terms used interchangably in discussion of
Rules Engines.
</para>
</important>
<para>
When inserted, the rule is examined for matches against the rules. The work
of determining what rules to fire is done during insertion, but no rules are
executed at this time. The rules are executed when
<methodname>fireAllRules()</methodname> is called, and it should only be called
after you have inserted all your facts.
</para>
<para>
It is a common misconception that rule matching occurs when
<methodname>fireAllRules()</methodname> is called.
</para>
<para>
When an Object is inserted it returns a FactHandle. This FactHandle is the
token used to represent your inserted Object inside the WorkingMemory, it is
also how you will interact with the Working Memory when you wish to retract
or modify an object.
</para>
<programlisting language="java">Cheese stilton = new Cheese("stilton");
FactHandle stiltonHandle = session.insert( stilton );</programlisting>
<para>
As mentioned in
<xref linkend="sect-JBoss_Rules_Reference_Manual-The_Drools_Rule_Engine-RuleBase" />
a Working Memory can operate in two assertions modes: <firstterm>equality</firstterm>
and <firstterm>identity</firstterm>. Identity is the default mode. The assertion
mode determines how the Working Memory stores the facts and how it compares the
newly inserted fact to previously inserted ones. If the Working Memory
determines the fact to "be the same" as an already inserted one it will ignore
the new fact and return the FactHandle for the previously inserted one.
</para>
<variablelist>
<varlistentry>
<term>Identity</term>
<listitem>
<para>
Identity Mode uses an <classname>IdentityHashMap</classname>to store all
asserted Objects. New facts being inserted are compared to existing facts
"by reference". A new FactHandle will be returned if the object being
inserted is not a reference to an object that has been inserted previously.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Equality</term>
<listitem>
<para>
Equality Mode uses a <classname>HashMap</classname> to store all asserted
Objects. New facts being inserted are compared to existing facts "by value".
A new FactHandle will be returned if the content of the object is not
identical to that of a previously inserted object.
</para>
</listitem>
</varlistentry>
</variablelist>
</section>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBRULES-3025) Regression: parser rebuts multiple bindings in constraint conjunction and disjunction
by Wolfgang Laun (JIRA)
Regression: parser rebuts multiple bindings in constraint conjunction and disjunction
-------------------------------------------------------------------------------------
Key: JBRULES-3025
URL: https://issues.jboss.org/browse/JBRULES-3025
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.2.0.M2
Reporter: Wolfgang Laun
Assignee: Mark Proctor
Priority: Blocker
Fix For: 5.2.0.CR1
The DRL given below compiled in 5.1.1 and executed as expected, i.e., both rules fired, producing
or R=1x2
and R=1x2
Now, a syntax error is flagged at the position of the 2nd binding ($w:). Moreover, the DRL parser is thrown off-track and crashes with sn EmptyStackException as soon as more rules follow.
package binding;
declare Rect
length : int
width : int
end
rule insert
salience 100
when
then
Rect r = new Rect();
r.setLength( 1 );
r.setWidth( 2 );
insert( r );
end
rule "binding and"
when
$r: Rect( $l: length == 1 && $w: width == 2 )
then
System.out.println( "and R=" + $l + "x" + $w );
end
rule "binding or"
when
$r: Rect( $l: length == 1 || $w: width == 1 )
then
System.out.println( "or R=" + $l + "x" + $w );
end
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBAS-9401) unknow protocal:VFS when the EJB 3.0 web service client trying to get the service from the jndiContext
by leon z (JIRA)
unknow protocal:VFS when the EJB 3.0 web service client trying to get the service from the jndiContext
------------------------------------------------------------------------------------------------------
Key: JBAS-9401
URL: https://issues.jboss.org/browse/JBAS-9401
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 6.0.0.Final
Environment: jdk 1.6.0.25 jboss 6.0.0.Final
Reporter: leon z
Assignee: Alessio Soldano
public class Client
{
public static void main(String [] args)
{
try
{
Context jndiContext = getInitialContext();
run.client:
[java] javax.naming.NamingException: Cannot unmarshall service ref meta data [Root exception is java.io.IOException: unknown protocol: vfs]
[java] at org.jboss.ws.core.jaxrpc.client.ServiceObjectFactoryJAXRPC.getObjectInstance(ServiceObjectFactoryJAXRPC.java:120)
[java] at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
[java] at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483)
[java] at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500)
[java] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:824)
[java] at org.jboss.naming.client.java.javaURLContextFactory$EncContextProxy.invoke(javaURLContextFactory.java:153)
[java] at $Proxy0.lookup(Unknown Source)
[java] at javax.naming.InitialContext.lookup(InitialContext.java:392)
[java] at com.titan.clients.Client.main(Client.java:19)
[java] Caused by: java.io.IOException: unknown protocol: vfs
[java] at java.net.URL.readObject(URL.java:1220)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
[java] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848)
[java] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
[java] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
[java] at java.io.ObjectInputStream.access$300(ObjectInputStream.java:187)
[java] at java.io.ObjectInputStream$GetFieldImpl.readFields(ObjectInputStream.java:2108)
[java] at java.io.ObjectInputStream.readFields(ObjectInputStream.java:518)
[java] at org.jboss.metadata.serviceref.VirtualFileAdaptor.readObject(VirtualFileAdaptor.java:217)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
[java] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848)
[java] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
[java] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
[java] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
[java] at org.jboss.wsf.spi.metadata.j2ee.serviceref.UnifiedServiceRefMetaData.readObject(UnifiedServiceRefMetaData.java:477)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
[java] at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1848)
[java] at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1752)
[java] at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1328)
[java] at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
[java] at org.jboss.ws.core.jaxrpc.client.ServiceObjectFactoryJAXRPC.getObjectInstance(ServiceObjectFactoryJAXRPC.java:115)
[java] ... 8 more
BUILD SUCCESSFUL
Total time: 2 seconds
TravelAgentService service = (TravelAgentService) jndiContext.lookup("java:comp/env/service/TravelAgentService");
TravelAgent agent = service.getTravelAgentPort();
Cabin cabin_1 = new Cabin();
cabin_1.setId(1);
cabin_1.setName("Master Suite");
cabin_1.setDeckLevel(1);
cabin_1.setShipId(1);
cabin_1.setBedCount(3);
agent.createCabin(cabin_1);
Cabin cabin_2 = agent.findCabin(1);
System.out.println(cabin_2.getName());
System.out.println(cabin_2.getDeckLevel());
System.out.println(cabin_2.getShipId());
System.out.println(cabin_2.getBedCount());
}
catch (javax.naming.NamingException ne)
{
ne.printStackTrace();
}
catch (java.rmi.RemoteException re)
{
re.printStackTrace();
}
catch (javax.xml.rpc.ServiceException se)
{
se.printStackTrace();
}
}
public static Context getInitialContext()
throws javax.naming.NamingException
{
return new javax.naming.InitialContext();
}
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBNAME-54) Failed to configure RMI + SSL
by Anup Ohal (JIRA)
Failed to configure RMI + SSL
-----------------------------
Key: JBNAME-54
URL: https://issues.jboss.org/browse/JBNAME-54
Project: JBoss Naming
Issue Type: Bug
Components: jnp-client
Affects Versions: 5.1.0.GA
Environment: Windows
Reporter: Anup Ohal
Priority: Critical
Fix For: 5.1.0.GA
Trying the to configure the RMI over SSL.
did following settings for this :
jboss-5.1.0.GA\server\idm\deploy\jbossweb.sar\server.xml
<!-- A AJP 1.3 Connector on port 8009 -->
<Connector address="${jboss.bind.address}" port="8009" protocol="AJP/1.3" redirectPort="8443"/>
<Connector SSLEnabled="true" SSLImplementation="org.jboss.net.ssl.JBossImplementation" URIEncoding="UTF-8" address="${jboss.bind.address}" clientAuth="false" maxSpareThreads="15" maxThreads="100" minSpareThreads="5" port="8084" scheme="https" secure="true" securityDomain="java:/jaas/encrypt-keystore-password" sslProtocol="TLS" truststoreFile="" truststorePass=""/>
-------------------------------------------------------------------
-----------------------------------------------------------
and in %jboss-5.1.0.GA%\server\idm\conf\jboss-service.xml the following settings:
<mbean code="org.jboss.security.plugins.JaasSecurityDomain" name="rmissl.security:name=JaasSecuritydomain,domain=RMI+SSL">
<constructor>
<arg type="java.lang.String" value="RMI+SSL"/>
</constructor>
<attribute name="KeyStoreURL">C:\Program Files (x86)\Suite/security/keystore/jboss.keystore</attribute>
<attribute name="KeyStorePass">{CLASS}org.jboss.security.plugins.FilePassword:${jboss.server.home.dir}/conf/keystore.password</attribute>
<attribute name="Salt">welcometojboss</attribute>
<attribute name="IterationCount">13</attribute>
</mbean>
<mbean code="org.jboss.security.plugins.JaasSecurityDomain" name="jboss.security:service=PBESecurityDomain">
<constructor>
<arg type="java.lang.String" value="encrypt-keystore-password"/>
</constructor>
<attribute name="KeyStoreURL">C:\Program Files (x86)\Suite/security/keystore/jboss.keystore</attribute>
<attribute name="KeyStorePass">{CLASS}org.jboss.security.plugins.FilePassword:${jboss.server.home.dir}/conf/keystore.password</attribute>
<attribute name="Salt">welcometojboss</attribute>
<attribute name="IterationCount">13</attribute>
</mbean>
----------------------------------------------------------------------------------------------
1. But still not able configure RMI over SSL. Are we missing something. do you have any guide mentioning the steps to configure RMI+SSL.
2. please let me know if there is any settings in Jboss server which can enforce client application to use only RMI+SSL?
Waiting for the reply.
Regards,
Anup
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-939) IllegalStateException when deploying a module.
by David Bosschaert (JIRA)
IllegalStateException when deploying a module.
----------------------------------------------
Key: AS7-939
URL: https://issues.jboss.org/browse/AS7-939
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Reporter: David Bosschaert
When deploying an OSGi bundle intermittently an IllegalStateException exception appears.
14:35:18,061 INFO [org.jboss.osgi.framework.internal.BundleManager] (MSC service thread 1-3) Install bundle: cxf-dosgi-ri-samples-greeter-interface:1.2.0
14:35:18,065 ERROR [org.jboss.msc.service] (MSC service thread 1-1) MSC00002: Invocation of listener "org.jboss.as.osgi.deployment.BundleStartTracker$1@196dcb4" failed: java.lang.IllegalStateException: Cannot load module: deployment.cxf-dosgi-ri-samples-greeter-interface:1.2.0
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:261)
at org.jboss.osgi.framework.internal.ResolverPlugin.applyResolverResults(ResolverPlugin.java:229)
at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(ResolverPlugin.java:161)
at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(AbstractBundleState.java:563)
at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:205)
at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:506)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.processService(BundleStartTracker.java:135)
at org.jboss.as.osgi.deployment.BundleStartTracker$1.serviceStarted(BundleStartTracker.java:107)
at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1322)
at org.jboss.msc.service.ServiceControllerImpl.access$2600(ServiceControllerImpl.java:47)
at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:1850)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_25]
Caused by: org.jboss.modules.ModuleNotFoundException: deployment.cxf-dosgi-ri-samples-greeter-interface:1.2.0
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:158) [:1.0.0.CR3]
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:152) [:1.0.0.CR3]
at org.jboss.osgi.framework.internal.ModuleManagerPlugin.loadModule(ModuleManagerPlugin.java:561)
at org.jboss.osgi.framework.internal.ResolverPlugin.loadModules(ResolverPlugin.java:259)
... 13 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (AS7-841) Break WebVirtualHostService into a service w/o ModelNodes, make public
by Bob McWhirter (JIRA)
Break WebVirtualHostService into a service w/o ModelNodes, make public
----------------------------------------------------------------------
Key: AS7-841
URL: https://issues.jboss.org/browse/AS7-841
Project: Application Server 7
Issue Type: Enhancement
Affects Versions: 7.0.0.Beta3
Reporter: Bob McWhirter
Assignee: Jason Greene
WebVirtualHostService is currently pkg-protected and references ModelNodes and other pkg-protected Constants.
TorqueBox has copied this file with modifications into our source-tree, as we allow people to define vhosts outside of the management interface for our use-cases. We do recommend they do it "The Right Way", but to support our users, we also allow in-app definition of vhosts.
This works, but copy/paste is never awesome.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] Created: (JBAS-9400) JBoss AS 6 NullPointerException when deploying an exploded WAR
by rey zalamea (JIRA)
JBoss AS 6 NullPointerException when deploying an exploded WAR
--------------------------------------------------------------
Key: JBAS-9400
URL: https://issues.jboss.org/browse/JBAS-9400
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss 6.0.0, Linux 2.6.24-27-generic
Reporter: rey zalamea
When deploying an exploded WAR, JBoss produces a null pointer exception. After some seconds, the WAR will be deployed (a directory will be created) and will function normally.
Error is:
2011-05-26 11:02:10,693 ERROR [org.rhq.plugins.jbossas5.deploy.LocalDeployer] (ResourceContainer.invoker.nonDaemon-16) Error deploying application for request [CreateResourceReport: ResourceType=[ResourceType[id=0, category=Service, name=Web Application (WAR), plugin=JBossAS5]], ResourceKey=[null]].: java.lang.NullPointerException
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months