Re: [pax-jdbc] mysql driver lockup

[Dutch Dude]

Well, 

After a lot of head scratching, I completely rebooted the DB server 
machine, and that solved the problem (at least for now). Even though 
MySQLWorkbench only showed a handful connection it looks like somehow the 
OS or DB engine ran out of 'something'.

Thanks for your attention,

Erwin


On Tuesday, May 23, 2017 at 9:06:23 AM UTC-4, Dutch Dude wrote:
>
> Hi -
>
> I am experiencing a driver lockup with pax-jdbc 1.1.0. It always seems to 
> happen when a new connection is being created (which, BTW shouldn’t happen 
> that often because I should be using a connection pool).
> It does’t happen all the time, but often enough to take the entire 
> application down.
>
> Would anyone have a suggestion how/where to start debugging this?
>
> All the relevant info should be below.
>
> This is the thread dump, starting with the entityTransaction.commit()
> Thread [qtp149708915-159] (Suspended) 
>  owns: ReadAheadInputStream  (id=912) 
>  owns: JDBC4Connection  (id=913) 
>  owns: DatabaseAccessor  (id=914) 
>  owns: SessionRepositoryImpl  (id=718) 
>  owns: PhaseInterceptorChain  (id=915) 
>  SocketInputStream.socketRead0(FileDescriptor, byte[], int, int, int) line
> : not available [native method] 
>  SocketInputStream.socketRead(FileDescriptor, byte[], int, int, int) line: 
> 116 
>  SocketInputStream.read(byte[], int, int, int) line: 170 
>  SocketInputStream.read(byte[], int, int) line: 141 
>  ReadAheadInputStream.fill(int) line: 101 
>  ReadAheadInputStream.readFromUnderlyingStreamIfNecessary(byte[], int, int
> ) line: 144 
>  ReadAheadInputStream.read(byte[], int, int) line: 174 
>  MysqlIO.readFully(InputStream, byte[], int, int) line: 3005 
>  MysqlIO.readPacket() line: 567 
>  MysqlIO.doHandshake(String, String, String) line: 1016 
>  JDBC4Connection(ConnectionImpl).coreConnect(Properties) line: 2253 
>  JDBC4Connection(ConnectionImpl).connectOneTryOnly(boolean, Properties) 
> line: 2284 
>  JDBC4Connection(ConnectionImpl).createNewIO(boolean) line: 2083 
>  JDBC4Connection(ConnectionImpl).(String, int, Properties, String, 
> String) line: 806 
>  JDBC4Connection.(String, int, Properties, String, String) line: 47 
>  NativeConstructorAccessorImpl.newInstance0(Constructor, Object[]) line
> : not available [native method] 
>  NativeConstructorAccessorImpl.newInstance(Object[]) line: 62 
>  DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 45 
>  Constructor.newInstance(Object...) line: 423 
>  Util.handleNewInstance(Constructor, Object[], ExceptionInterceptor) 
> line: 425 
>  ConnectionImpl.getInstance(String, int, Properties, String, String) line: 
> 410 
>  NonRegisteringDriver.connect(String, Properties) line: 328 
>  MysqlDataSource.getConnection(Properties) line: 428 
>  MysqlDataSource.getConnection(String, String) line: 136 
>  MysqlDataSource.getConnection() line: 107 
>  DataSourceConnectionFactory.createConnection() line: 44 
>  PoolableConnectionFactory.makeObject() line: 256 
>  GenericObjectPool.create() line: 868 
>  GenericObjectPool.borrowObject(long) line: 435 
>  GenericObjectPool.borrowObject() line: 363 
>  PoolingDataSource.getConnection() line: 134 
>  JNDIConnector.connect(Properties, Session) line: 135 
>  DatabaseLogin(DatasourceLogin).connectToDatasource(Accessor, Session) 
> line: 162 
>  DatabaseAccessor(DatasourceAccessor).connectInternal(Login, 
> AbstractSession) line: 346 
>  DatabaseAccessor.connectInternal(Login, AbstractSession) line: 309 
>  DatabaseAccessor(DatasourceAccessor).reconnect(AbstractSession) line: 581 
>  DatabaseAccessor.reconnect(AbstractSession) line: 1634 
>  DatabaseAccessor(DatasourceAccessor).incrementCallCount(AbstractSession) 
> line: 321 
>  DatabaseAccessor.basicExecuteCall(Call, AbstractRecord, AbstractSession, 
> boolean) line: 615 
>  DatabaseAccessor.executeCall(Call, AbstractRecord, AbstractSession) line: 
> 560 
>  ServerSession(AbstractSession).basicExecuteCall(Call, AbstractRecord, 
> DatabaseQuery) line: 2055 
>  ServerSession.executeCall(Call, AbstractRecord, DatabaseQuery) line: 570 
>  IsolatedClientSession(ClientSession).executeCall(Call, AbstractRecord, 
> DatabaseQuery) line: 258 
>  ExpressionQueryMechanism(DatasourceCallQueryMechanism).executeCall(
> DatasourceCall) line: 242 
>  ExpressionQueryMechanism(DatasourceCallQueryMechanism).executeCall() line
> : 228 
>  ExpressionQueryMechanism(DatasourceCallQueryMechanism).
> selectRowForDoesExist(DatabaseField) line: 736 
>  DoesExistQuery.executeDatabaseQuery() line: 241 
>  DoesExistQuery(DatabaseQuery).execute(AbstractSession, AbstractRecord) 
> line: 904 
>  DoesExistQuery(DatabaseQuery).executeInUnitOfWork(UnitOfWorkImpl, 
> AbstractRecord) line: 803 
>  RepeatableWriteUnitOfWork(UnitOfWorkImpl).internalExecuteQuery(
> DatabaseQuery, AbstractRecord) line: 2896 
>  RepeatableWriteUnitOfWork(AbstractSession).executeQuery(DatabaseQuery, 
> AbstractRecord, int) line: 1857 
>  RepeatableWriteUnitOfWork(AbstractSession).executeQuery(DatabaseQuery, 
> AbstractRecord) 

Re: PAX Wicket 4 (moving to wicket 8)

[nino martinez wael]

Yes I agree Christoph, thats why I wrote the list..Nothing came out of it
though..

Se here:

https://groups.google.com/forum/?hl=en#!topic/ops4j/ahQOfLYXmAM

All you are asking for are described there. And yes I have tried
cleaning/deleting my local repo and run a clean install.

Thanks for your input.

regards Nino

On Wed, May 24, 2017 at 9:57 AM, 'Christoph Läubrich' via OPS4J <
ops4j@googlegroups.com> wrote:

> Hi nino,
>
> the goal should be to more test per release and not to disable existing
> ones.
>
> It is a little hard to help without exact informations, what is exacly the
> problem with the test:
>
>  - What tests(s) are affected
>  - What fails (e.g. what bundles do not resolve etc.)
>  - Whats your enviroument (java + maven version)
>  - Have you tried to clear your maven-repro + rund a clean install
>
> regards
> Christoph
>
> Am 22.05.2017 06:55, schrieb nino martinez wael:
>
> Hi
>
> Over 2 months ago I made the last changes to the 4.x.y branch[1] to
> support wicket 8. I cannot get the "bare" felix tests to work (I seem to be
> missing some dependency, which I cannot figure out)..
>
> The question is, should I just disable the the test, as there are no
> horison on it getting to work and release what we have..? If not, how
> should we get the broken felix tests to work, i'm pretty sure its some
> dependency thing that's out of sync.
>
> [1]https://github.com/ops4j/org.ops4j.pax.wicket/tree/v4.x.y
>
>
> Regard Nino
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "OPS4J" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/ops4j/A3x7_4ktoqk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> ops4j+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Best regards / Med venlig hilsen
Nino Martinez

-- 
-- 
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups 
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with Whiteboard Resource Servlet Name

['Achim Nierbeck' via OPS4J]

done :)

2017-05-24 0:39 GMT+02:00 Nelson Antunes :

> Hi Achim,
>
>   I'll need a JIRA account, please.
>
>   As for the PR, I can do it as reference, but it was just a quick fix
> I've tried when digging a little bit on the issue.
>   I'm not confident that it doesn't have any bad side effect.
>
>   For instance, if the servlet name can be anything and not necessarily a
> path, why all that trouble ensuring it doesn't end in a forward
> slash unless it is just "/"?
>
> -- Nelson --
>
> On Tuesday, May 23, 2017 at 7:53:51 PM UTC+1, Achim Nierbeck wrote:
>>
>> Hi Nelson,
>>
>> do you care about creating an Issue for this and maybe provide a pull
>> request?
>> if needed, a jira user can be created.
>>
>>
>> regards, Achim
>>
>> 2017-05-23 14:45 GMT+02:00 Nelson Antunes :
>>
>>>   That call to registerResources in [1
>>> ]
>>> is part of the org.osgi.service.http.HttpService interface.
>>>
>>>   I noticed the servlet name (at least the one listed with the http:list
>>> command) is set here [2
>>> ]
>>> (for Jetty).
>>>   So I tried to modify that model name. [3
>>> ]
>>> seemed a good place to try.
>>>
>>>   I changed it to:
>>>
>>> String modelName = "bundle:" + contextModel.getBundle().getBundleId();
>>> if(!"/".equals(name)) {
>>>  modelName += name;
>>> }
>>> final ResourceModel model = new ResourceModel(contextModel, servlet, alias, 
>>> modelName );
>>>
>>>
>>>   Now http:list show all the expected servlets and the resources are
>>> served from different bundles with the same internal resource paths.
>>>   They also get correctly undeployed when stopping the bundles.
>>>
>>>   But I can't be sure of any side-effects.
>>>
>>>   (tested in tag web-3.2.9, but the code is still the same in the master
>>>  branch)
>>>
>>> -- Nelson --
>>>
>>> [1] https://github.com/ops4j/org.ops4j.pax.web/blob/web-3.2.
>>> 9/pax-web-extender-whiteboard/src/main/java/org/ops4j/pax/
>>> web/extender/whiteboard/internal/element/ResourceWebElement.java#L56-L57
>>> [2] https://github.com/ops4j/org.ops4j.pax.web/blob/web-3.2.
>>> 9/pax-web-jetty/src/main/java/org/ops4j/pax/web/service/
>>> jetty/internal/JettyServerImpl.java#L219
>>> [3] https://github.com/ops4j/org.ops4j.pax.web/blob/web-3.2.9/pa
>>> x-web-runtime/src/main/java/org/ops4j/pax/web/service/intern
>>> al/HttpServiceStarted.java#L253-L254
>>>
>>>
>>> On Thursday, February 23, 2017 at 9:14:01 PM UTC, Nick Baker wrote:

 Hello All,

 We're experiencing an issue with bundles supplying Resource mappings.
 It appears that the internal path within the bundle is used as the servlet
 name [1]. Unfortunately, our teams love standards and conventions so
 they're using a "web" folder for all bundles supplying Resources. This was
 discovered on 3.1.4 but I've verified that the situation still exists in
 master.

 PAX-Web appropriately doesn't allow multiple servlets of the same name
 so we're loosing some resources upon startup of Karaf. The short-term
 solution for us was to ensure that each internal bundle path is unique. A
 better solution would be to modify PAX to create a composite key of
 bundle-id + path when creating the resource Servlet names.

 [1] https://github.com/ops4j/org.ops4j.pax.web/blob/master/p
 ax-web-extender-whiteboard/src/main/java/org/ops4j/pax/web/
 extender/whiteboard/internal/element/ResourceWebElement.java#L57-L57

 -Nick Baker

>>> --
>>> --
>>> --
>>> OPS4J - http://www.ops4j.org - op...@googlegroups.com
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "OPS4J" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to ops4j+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>>
>> Apache Member
>> Apache Karaf  Committer & PMC
>> OPS4J Pax Web  Committer
>> & Project Lead
>> blog 
>> Co-Author of Apache Karaf Cookbook 
>>
>> Software Architect / Project Manager / Scrum Master
>>
>> --
> --
> --
> OPS4J - http://www.ops4j.org - ops4j@googlegroups.com
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email 

Re: PAX Wicket 4 (moving to wicket 8)

['Christoph Läubrich' via OPS4J]

Hi nino,

the goal should be to more test per release and not to disable existing 
ones.


It is a little hard to help without exact informations, what is exacly 
the problem with the test:


 - What tests(s) are affected
 - What fails (e.g. what bundles do not resolve etc.)
 - Whats your enviroument (java + maven version)
 - Have you tried to clear your maven-repro + rund a clean install

regards
Christoph

Am 22.05.2017 06:55, schrieb nino martinez wael:

Hi

Over 2 months ago I made the last changes to the 4.x.y branch[1] to 
support wicket 8. I cannot get the "bare" felix tests to work (I seem 
to be missing some dependency, which I cannot figure out)..


The question is, should I just disable the the test, as there are no 
horison on it getting to work and release what we have..? If not, how 
should we get the broken felix tests to work, i'm pretty sure its some 
dependency thing that's out of sync.


[1]https://github.com/ops4j/org.ops4j.pax.wicket/tree/v4.x.y


Regard Nino
--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

---
You received this message because you are subscribed to the Google 
Groups "OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to ops4j+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
--
--
OPS4J - http://www.ops4j.org - ops4j@googlegroups.com

--- 
You received this message because you are subscribed to the Google Groups "OPS4J" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to ops4j+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.