jaxrs subsystem management use cases
by Heiko Braun
What about this one?
[domain@localhost:9999 /] /profile=default/subsystem=jaxrs:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
Ike
15 years
weld & jpa subsystem use cases
by Heiko Braun
You know the drill. These are subject to be exluded as well.
[domain@localhost:9999 /] /profile=default/subsystem=weld:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {},
"compensating-operation" => undefined
}
[domain@localhost:9999 /] /profile=default/subsystem=jpa:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {"default-datasource" => ""},
"compensating-operation" => undefined
}
Ike
15 years
remoting management use cases
by Heiko Braun
If there is no reasonable functionality, I tend to exclude this one for 7.0.Final:
[domain@localhost:9999 /] /profile=default/subsystem=remoting:read-resource(recursive=true)
{
"outcome" => "success",
"result" => {
"thread-pool" => "remoting",
"connector" => {}
},
"compensating-operation" => undefined
}
Ike
15 years
(JDBC) Driver Registry
by Heiko Braun
Following up with some of the discussion we'd been having in the past few weeks,
I would like to call for comments on the idea of a central, domain level driver registry
that can be used to query specific deployments like JDBC drivers.
Creating datasource configuration is currently way to complex for the average user.
Once you've deployed the JDBC driver you need provide the correct driver name, driver class and version
besides the regular data source attributes. Since we are lacking a way to query for installed JDBC drivers
this currently means providing the required attributes as string values.
A more simple and less error prone approach would be to provide a selection of drivers to chose from.
But this would require something like a domain level driver registry.
The same mechanism might be used to query available resource adapters or other specific deployment types
that are typically referenced by applications.
Any reasons why this cannot be done?
Any objections why it shouldn't be?
Other ideas how this situation can be improved?
Ike
15 years
Error in xml question
by Max Rydahl Andersen
Hi,
I was playing with the plug computer today that Jason setup and noticed that he configured it to only bind to one port, i.e.
<interface name="default">
<inet-address value="192.168.3.1"/>
</interface>
in an attempt to fix that quickly I tried to add an extra inet-address:
<interface name="default">
<inet-address value="192.168.3.1"/>
<inet-address value="192.168.2.10"/>
</interface>
When I booted as7 beta4-snapshot up it seem to work fine except it didn't ;)
I found the following IMO confusing message:
23:26:45,856 ERROR [org.jboss.msc.service.fail] MSC00001: Failed to start service jboss.network.default: org.jboss.msc.servic
e.StartException in service jboss.network.default: failed to resolve interface default
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:106)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_18]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_18]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_18]
Didn't see any parsing errors/messages that would lead me to the apparent problem in standalone.xml.
Is this the expected/wanted behavior ?
/max
http://about.me/maxandersen
15 years
Consolidate Arquillian test infrastructure
by Thomas Diesler
Folks,
I created a blocking issue for CR1 that is about a consolidated test
infrastructure that supports the functionality required by the set of
already existing AS7 test cases (including OSGi).
https://issues.jboss.org/browse/AS7-734
Some time ago it was decided that the AS7 release process does not
include a cycle whereby project leads can run their external test suites
against an AS7 release candidate and if needed veto the release. OSGi is
not the only project that has extensive external test coverage against
AS7. Instead, is was agreed that supported functionality must be tested
by a comprehensive test suite that is part of the AS7 code base. For
this to work we need to have a suitable tests infrastructure in place.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
15 years
Feature requests from bof
by Scott Stark
A couple of feature requests from the as7 bof likely require a notion of
the domain topology to be accessible via the management api. Two
requests that stick out are:
1. The knowledge of the "cluster" members in a non-autodiscovery
environment (such as most cloud providers). The request was a little
more specific in that there was a desire to have a cluster aware service
such as infinispan to magically have its membership configuration
handled by the domain when one would typically have to setup a gossip
server, S3_PING or some other non-UDP discovery service. As we discussed
in the bof, there really is no "cluster" notion, but we should expect
that a one or more server-groups would be setup to represent the
services one wants to be clustered, and so, requesting the members of a
server-group from the domain api could be used to build a discovery service.
2. Having stable jndi names across the domain. In a potentially
multi-tier domain, or even a domain that includes singleton or at least
hetergenous service setup, you would like to be able to refer to service
factories via logical jndi names that map to the domain topology. We
could accomplish this by having a jndi ContextFactory binding under
something like "domain:" that would allow for lookups like:
a. "domain:/clusterServerGroup/RemoteConnectionFactory", lookup of
a connection factory that is bound across all nodes in the "cluster"
server-group.
b. "domain:/batchServer/batchGatewayEjb", lookup of the
batchGatewayEjb remote interface on the batchServer server instance.
Another natural api for accessing the domain model would be a jndi
DirContext implementation that would provide effectively the same
information as the cli using the same namespace.
I can create proper feature requests for these once they are vetted as
useful. I assume this will have to be a 7.1 feature.
15 years
Re: [jboss-as7-dev] Oracle datasource missing dependencies
by Marchioni Francesco
Hi Paul,
Watch out, there's an error in your driver class name- when using
ojdbc5.jar the driver name is oracle.jdbc.OracleDriver and NOT
oracle.jdbc.driver.OracleDriver.
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.6.5
Created-By: 1.5.0_24-rev-b08 (Sun Microsystems Inc.)
Implementation-Vendor: Oracle Corporation
Implementation-Title: JDBC
Implementation-Version: 11.2.0.2.0
Repository-Id: JAVAVM_11.2.0.2.0_LINUX_100812.1
Specification-Vendor: Sun Microsystems Inc.
Specification-Title: JDBC
Specification-Version: 4.0
Main-Class: oracle.jdbc.OracleDriver <===========driver
I got it working with ojdbc5.jar.
Hope it helps,
regards
Francesco Marchioni
>Hello Stefano, which .jar have you used for testing connectivity ?
>I've used ojdbc5.jar but I still get the same error.....
>--
>paulwerder(a)fastmail.co.uk
>Oracle 10.2 jdbc driver is type 3 driver and it can't be loaded by
java.util.ServiceLoader using the >META-INF/services directory in the
jar.
>And it's the only way we are supporting jdbc as module or deployment.
IOW we are just supporting type 4 >driver.
>Use Oracle 11g driver, I've tested it and it's working.
On Wed, 04 May 2011 14:54 +0200, "Stefano Maestri" <smaestri(a)redhat.com>
wrote:
> The problem is the driver itself.
> Oracle 10.2 jdbc driver is type 3 driver and it can't be loaded by
java.util.ServiceLoader using the META-INF/services directory in the
jar.
> And it's the only way we are supporting jdbc as module or deployment.
IOW we are just supporting type 4 driver.
>
> Use Oracle 11g driver, I've tested it and it's working.
>
> regards
> S.
>
>
> On 05/04/2011 01:14 PM, Nicklas Karlsson wrote:
>> And the version number is correct for the driver?
>>
>> On Wed, May 4, 2011 at 1:40 PM, <paulwerder(a)fastmail.co.uk> wrote:
>>
>> Hello Ike,
>> >This is just a vague guess, but there used to be an issue with
the OSGI subsystem involved.
>> >What AS version are you using? The problem I am referring to
should be solved in trunk.
>> >But if you a running a previous release, then try commenting out
the osgi subsystem .
>>
>> I'm using Beta3 - no luck :-(
>>
>> --
>>
>> paulwerder(a)fastmail.co.uk
>>
>> On Wed, 04 May 2011 12:23 +0200, "Heiko Braun"
<hbraun(a)redhat.com> wrote:
>>>
>>>
>>>
>>>
>>> This is just a vague guess, but there used to be an issue with
the OSGI subsystem involved.
>>> What AS version are you using? The problem I am referring to
should be solved in trunk.
>>> But if you a running a previous release, then try commenting out
the osgi subsystem .
>>>
>>> Ike
>>>
>>> On May 4, 2011, at 12:02 PM, paulwerder(a)fastmail.co.uk wrote:
>>>
>>>> Hello,
>>>> >do you have a
>>>>
>>>> > <drivers>
>>>> <driver module="oracle.jdbc"/>
>>>> > </drivers>
>>>>
>>>> >in your configuration at datasources subsystem?
>>>>
>>>> yes I have inserted it, exaclty as you typed it. (sorry I
forgot to mention it before.)
>>>>
>>>> might it be a specific issue with this JDBC driver ?
>>>> regards
>>>> Paul
>>>> --
>>>>
>>>> paulwerder(a)fastmail.co.uk
>>>>
>>>> On Wed, 04 May 2011 12:54 +0300, "Nicklas Karlsson"
<nickarls(a)gmail.com> wrote:
>>>>> do you have a
>>>>>
>>>>> <drivers>
>>>>> <driver module="oracle.jdbc"/>
>>>>> </drivers>
>>>>>
>>>>> in your configuration at datasources subsystem?
>>>>>
>>>>> On Wed, May 4, 2011 at 11:39 AM, <paulwerder(a)fastmail.co.uk>
wrote:
>>>>>
>>>>> Hi JBoss devs,
>>>>> I'm testing Oracle connectivity using a 10.2 JDBC Driver
(ojdbc14.jar).
>>>>> Seems there are some issues- has anyone managed to connect
to an Oracle
>>>>> DB ?
>>>>> This is what the server reports:
>>>>>
>>>>> report
>>>>> New missing/unsatisfied dependencies:
>>>>> service
jboss.jdbc-driver."oracle.jdbc.driver.OracleDriver".10.2
>>>>> (missing)
>>>>>
>>>>> And my configuration:
>>>>>
>>>>> <datasource jndi-name="java:/OracleDS"
pool-name="OracleDS"
>>>>> enabled="true" use-java-context="true">
>>>>> <connection-url>
>>>>>
jdbc:oracle:thin:@192.168.1.1:1530:ORACLESID
>>>>> </connection-url>
>>>>> <driver-class>
>>>>> oracle.jdbc.driver.OracleDriver
>>>>> </driver-class>
>>>>> <driver>
>>>>>
oracle.jdbc.driver.OracleDriver#10.2
>>>>> </driver>
>>>>> <pool>
>>>>> <prefill>
>>>>> true
>>>>> </prefill>
>>>>> <use-strict-min>
>>>>> false
>>>>> </use-strict-min>
>>>>> </pool>
>>>>> <security>
>>>>> <user-name>test</user-name>
>>>>> <password>test</password>
>>>>> </security>
>>>>> <validation>
>>>>> <validate-on-match>
>>>>> false
>>>>> </validate-on-match>
>>>>> <background-validation>
>>>>> false
>>>>> </background-validation>
>>>>> <useFastFail>
>>>>> false
>>>>> </useFastFail>
>>>>> </validation>
>>>>> <statement/>
>>>>> </datasource>
>>>>>
>>>>> I've chosen to install the JDBC driver as a module, so
under the
>>>>> "modules" folder I've added:
>>>>> oracle
>>>>> +---jdbc
>>>>> +---main
>>>>> module.xml
>>>>> ojdbc14.jar
>>>>> ojdbc14.jar.index
>>>>>
>>>>> Last thing, the module.xml:
>>>>>
>>>>> <module xmlns="urn:jboss:module:1.0" name="oracle.jdbc">
>>>>> <resources>
>>>>> <resource-root path="ojdbc14.jar"/>
>>>>> <!-- Insert resources here -->
>>>>> </resources>
>>>>> <dependencies>
>>>>> <module name="javax.api"/>
>>>>> </dependencies>
>>>>> </module>
>>>>>
>>>>> Can you find any reason why the driver does not get
deployed ?
>>>>> (I've tried also adding META-INF/services/java.sql.Driver
with the
>>>>> driver class name- it didn't help however).
>>>>> Thanks a lot
>>>>> Paul
>>>>> --
>>>>>
>>>>> paulwerder(a)fastmail.co.uk
>>>>>
>>>>> --
>>>>> http://www.fastmail.fm - IMAP accessible web-mail
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> ---
>>>>> Nik
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>
>>>>
>>>> --
>>>> http://www.fastmail.fm - mmm... Fastmail...
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>> --
>> http://www.fastmail.fm - Does exactly what it says on the tin
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>>
>>
>> --
>> ---
>> Nik
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o societa a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o societa diversi dai destinatari indicati, e proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
15 years
